W VIBE Moments — sharing and clipping program
Updated: 2026-09-08. Current page implementation and program proposal. The Moments page and sample sharing are implemented. Member enrollment, paid campaigns and payouts are not open. Three AI concept clips and an exploratory watch Look Shift now appear in a separate, unlinked /reel playback page.
Purpose and confirmed direction
The standalone /reel sequence is accepted as a good first pass. Keep it standalone and unlinked for now while its content is refined. The current sequence ends with a watch beat showing sealed, open/active and evolved states; future integration into Moments/clipping or the homepage remains open.
The promo destination should also be the clipping-program hub. Visitors see what makes W VIBE interesting; creators get material they can turn into social posts. The vocabulary is explicit: public visitors share moments; program members clip moments for campaigns. Joining belongs to the clipping program; public sharing does not require it. A moment is an event worth sharing: a discovery, a meaningful Look change, a large trade or a significant price move. Its story says who was involved, what changed, the before/after state and why it matters. The Dub or Stash is the subject; the event is the moment. Dollar figures can be the central event, not just supporting metadata. Production event-driven clips still require asset, program and story decisions; the standalone promo is an illustrative media test that now includes a watch Look Shift. The homepage remains The Flex.
Current navigation label and page name: Moments, at /moments. Public action: Share a moment. Member action: Clip a moment. Clipping enrollment is not open. The page appears in the main navigation alongside the existing sections.
Implemented page and sharing
The Moments page shares /api/vibe/data with The Flex and Moves. The 100-record generation contributes dynamically scheduled Look/price Shifts plus two individual test sales, an atomic five-item mystery-Stash sale, a gift, a claim and two application ask changes. Hidden-item events and concealed member art stay excluded.
Recent events are paginated, with kind filters and amount sorting across the full eligible set. Amounts are test SOL. Scheduled Moments display only previous/current Look and platform price, with issuance provenance. They are calculated by the deployed program and do not have a separate Shift transaction. Fixture claims are labelled separately. A claim of a designated Chase prize becomes a discovery Moment only with a verified claim instruction, game memo and issuer/claimant signatures. Receipt event art is reconstructed for its event time, so later Looks do not rewrite historical sales.
Each detail opens a fixed snapshot with before/after states, source-event time, generation, context and receipt link when applicable. Browser PNG generation and caption copying preserve the Devnet Test label and controlled-activity context. Posters use the same hue/rotation/scale recipe as the page. Sealed events have no hidden-member media. Public visitors share; member enrollment, rewards and event-driven video remain unavailable.
Event and export rules
Keep sales, gifts, claims, scheduled Shifts and asks distinct. An ask is not money paid; a gift has no sale price; a visual Shift does not imply appreciation. Controlled back-and-forth test sales are not evidence of demand. Missing receipts are omitted and flagged. A selected/exported snapshot stays fixed. New scheduled Shifts receive new state-index IDs; current ownership/Look must not rewrite historical receipt events. Apply reveal rights to cards, details, captions, media URLs and exports.
The final selection thresholds, campaign rules, public rights and video formats remain open. A future event index must record actual source facts and stable ordering. No D1 or inventory snapshot cache is added for this phase; the committed test event catalog is explicitly a fixture history, not a production index.
Joining and reward program — decisions still open
Recommendation: start with an application-based, free pilot and a small funded campaign. Use email or social identity for entry; verify the posting account before accepting a submission. Choose supported ages, countries and platforms before recruitment. Define acceptance, rights, disclosure and payment terms before participants create compensated work. Payout details can be collected when needed; a crypto wallet need not be the onboarding method.
| Reward option | Benefit | Tradeoff |
|---|---|---|
| Fixed fee for an approved deliverable | Clear effort/reward; practical for an initial controlled pilot | Requires acceptance criteria and quality review |
| Payment per qualified 1,000 views | Rewards distribution | Requires reliable view evidence, fraud review, counting window and spend controls |
| Fixed fee plus performance bonus | Supports creation and reach | More accounting and rules to explain |
Recommended first discussion: a fixed-fee pilot, with performance rewards considered when view verification is reliable. No reward amount, budget, fee, approval period or payment schedule is selected. W VIBE's “No cap” promise means honest communication; it does not mean unlimited campaign spending.
Every paid campaign needs an actual funding source, total budget, individual limits, eligible content/platforms, start/end dates, attribution rules, counting window, duplicate/repost policy, review/rejection/appeal process and payment timing. Show remaining funds before participation and define how funds are reserved; acceptance must not create unfunded obligations. Referral or purchase commissions are separate possible models, not implied by clipping.
Submission states should distinguish received, in review, needs changes, rejected, approved, payment processing and paid. Estimated rewards are never displayed as paid. Buying views, repeated claims on the same post and unauthorized footage are not eligible. Creators need a usable reason for rejection. Program membership and copyright permission are separate: the asset pack must actually grant the intended editing/posting rights and cover any owner identity or audio used.
What research supports
Whop's own Content Rewards documentation describes campaign budgets, per-1,000-view rates, minimum and maximum payouts, optional fixed bonuses, platform restrictions, supplied source material and submission review. This supports making the campaign terms and asset supply explicit. It does not establish W VIBE's rate or guarantee returns. Whop campaign documentation.
The exact $960,000 N3on figure was not verified. Business Insider reported on April 26, 2026 that his team documented over $1.4 million paid to 303 clippers over five weeks. This is a scale example from one operation, not a W VIBE budget or expected earnings benchmark. Business Insider reporting.
Clipping is not inherently membership-based: Twitch gives streamers settings to allow viewers to create clips. Paid campaign participation is a separate relationship. Vyro's current clipper terms require registration and linked/verified social accounts; its onboarding instructs creators to join, choose a campaign, post and submit. This research did not establish automatic payments to anonymous clippers or universal acceptance of pre-enrollment posts. Twitch clip settings, Vyro clipper terms, Vyro onboarding.
For US-facing compensated promotion, FTC guidance calls for an obvious disclosure of the brand relationship, including within an endorsement video itself. Asset templates and submission instructions should make this easy; “No cap” is not an advertising disclosure. Final market-specific requirements depend on where the program operates. FTC disclosure guidance.
Technical scope and sequencing
Current API and display behavior is in HOMEPAGE-V1.md. Hybrid decoding/evolution is selected; ASSET-SYSTEM.md records asset and production issuance decisions still open. D1 may eventually hold authoritative listing, reveal and event history data, with explicitly designed consistency; it is not an automatic cache for RPC.
Next, settle the actual asset/output format and production reveal/Shift rules. Iterate the playable discovery pilot. Review member/reward rules and choose the first video story afterward. Preserve truthful test/source labels in all sharing.