by Unity Nodes
Proposals

NEARCLIPS — Clip-Making Marketplace for NEAR Ecosystem Distribution (Funding Proposal)

3 posts50 views1 likesLast activity 1d ago

Open on Forum
  1. WizbrainOP 1

    Abstract

    NEARCLIPS is a two-sided marketplace where creators post short clips (TikTok, Reels, Shorts, X) about NEAR ecosystem projects and earn per verified view, while projects fund budgets and pay only for results. We request $45,000 (~9,150 NEAR at ~$4.92/NEAR): $21,000 to build and operate the platform for 6 months, plus a $24,000 incentive pool to attract ecosystem projects and reward creators. Working preview: https://nearclips.vercel.app

    Context & Alignment

    • Proven model elsewhere: the reference platform vues.app states it has driven 25B+ views via 301K+ clips for 60+ funded brands (platform’s own figures).
    • NEAR already holds significant value in DeFi (Rhea Lend ~$195M, NEAR Intents ~$118M, Meta Pool ~$104M TVL — DeFiLlama, Oct 23 2026) but lacks a performance-based organic distribution channel.
    • Aligns with HoS values: measurable public-good distribution; every payout creates a NEAR account and circulates NEAR as the settlement asset.

    Situation

    • Problem: NEAR projects spend on marketing with weak attribution; creators making NEAR content earn nothing.
    • Without action: ecosystem launches keep competing for the same thin organic attention with no shared infrastructure.

    Mission

    Objectives: Launch a production marketplace connecting NEAR projects and creators; make it the default organic distribution channel for ecosystem launches.

    Outcomes (6 mo, targets): ≥10 projects funding campaigns, ≥5,000 creators, ≥50M verified views, ≥$150K of third-party campaign budgets run through the platform.

    Approach

    Escrowed campaign budgets with per-view payouts, auto-verified via platform APIs; anomaly detection and manual review before payout. Risks: view fraud (mitigated by API tracking + review), weak initial demand (matching pool de-risks first campaigns), thin creator supply (first-clip bounties). Limitation: 6-month KPI-gated pilot; continuation requires a new proposal.

    Technical Specification

    Build: creator auth, campaign engine (CPM, budgets, escrow), view-verification service, payouts in NEAR/USDC. Preview already deployed on Vercel. Hosting: Vercel Pro, DB, monitoring, domains.

    Backwards Compatibility

    No backwards compatibility issues.

    Milestones

    Milestone Target Date Deliverable
    M1 — Production launch Month 1 Live app (auth, campaigns, view tracking, NEAR payouts); ≥2 funded campaigns
    M2 — First traction Month 3 ≥5 funded campaigns, ≥1,000 creators, ≥5M verified views
    M3 — Self-sustaining loop Month 6 ≥10 projects, ≥5,000 creators, ≥50M views, ≥$150K third-party budgets

    Budget & Resources

    Item Amount Notes
    Engineering $12,000 Auth, campaign engine, view verification, payouts
    Hosting & infra $3,600 Vercel Pro, DB, monitoring, domains (6 months)
    Creator ops $5,400 Support, content QA, moderation (6 months)
    Ecosystem incentive pool $24,000 Matching project campaign budgets + first-clip creator bounties
    Total $45,000 (~9,150 NEAR) Paid in NEAR at execution

    Source: Treasury (in-kind alternative equally welcomed: ecosystem intros, listings, co-marketing)

    Reporting: Monthly public updates in this thread (campaigns, views, payouts, funds spent).

    Team & Accountability

    • Responsible: Independent team building on NEAR (backgrounds to be posted in this thread)
    • Accountable to: House of Stake — monthly KPI/spend reports; KPI miss at M2 → reduced or suspended tranches

    Security Considerations

    Escrowed funds, milestone-based tranches (ideally via Sputnik DAO); payout fraud controls (API tracking, anomaly detection, rate caps, manual review).

    Conflict of Interest

    Team holds NEAR; not affiliated with NEAR Foundation/Pagoda. Demo data on the preview site is illustrative (labeled on the page).

    Copyright

    Copyright and related rights waived via CC0.

  2. Wizbrain

    up, Will anyone pay attention to me?

  3. fiatisabubble

    gm @Wizbrain

    I don’t have any strong opinions in favor or against this proposal but if you want to push this through HoS you should submit it via the HoS website: NEAR Proposals

    I’d also recommend familiarising yourself with the HoS proposal guide that’s available in docs: NEAR House of Stake Proposals and Voting Procedures

Back to Discussions