Vol. 1 · No. 1 The Bags Hackathon · Apr 26, 2026 For internal team review

BAGGED

A build brief — the two products, the strategy, the plan.

// Brief — read top to bottom

One fee economy. Two products. Eight tracks. The pair that wins because nobody else is in either room.

We are not building another launchpad. The field has nine of those already, four trading bots, and four fee aggregators. We are building the audience-side acquisition tool and the holder-side redemption layer that nobody has shipped — and binding them with the same coin economy underneath.

§ 1 — The field

Of 25+ submissions, ~18 are the same shape.

Spend an hour reading the existing hackathon submissions and a pattern emerges with embarrassing clarity. Nine of them are launchpad wizards with different paint jobs. Five are AI trading bots and risk dashboards. Four are fee-claim automation tools. The remaining handful are scattered: an RWA play, a WhatsApp wallet, a few ambitious AI-agent infras. Most fail the only test that matters in a thousand-submission stack: could a judge open Bags right now and replicate this in five minutes by clicking around?

For the launchpads, the answer is yes. For the trading bots, also yes — they wrap public price data. For the fee aggregators, mostly yes. These are products that took a Bags primitive and put a UI on it. That is not enough.

The empty zones — the rooms nobody has walked into — are the only viable places to set up shop. Browser extensions and external surfaces (zero submissions). Burn-on-claim redemption layers (zero). Discord-activity-driven mechanics (zero). AI training-data royalty rails (zero). Coin merger primitives (zero). Genesis-tier composability (zero). We are picking two of those rooms and building deep in both.

§ 2 — The strategy

Park in empty zones. Bind two products with one coin economy.

The two products are TIP and REDEEM. They are the front door and the back door of the same house. TIP brings creators onto Bags by force — every YouTube, Spotify, X, and Substack page becomes a launch surface, and the first tipper mints the coin. REDEEM gives those coins something to do — holders burn tokens to claim signed merch, backstage QRs, Zoom calls, and rare 1-of-1 perks.

One product is acquisition. The other is retention. Both are in empty zones. Both build new code rather than skinning a primitive. Both produce demos that screenshot themselves.

The strategy is not "find the most novel idea." It is park in a room nobody else is in — defensibility is automatic when there is nobody to compete against on day one. Project lead
// Product No. 1

TIP

A browser extension that turns every web page into a Bags launchpad. The first tipper mints the coin and is bag #1 forever.

Bags API Payments Social Finance Fee Sharing Other

How it works

A floating "tip" pill appears on every YouTube, Spotify, TikTok, X, and Substack page. Click it. If the creator already has a Bags coin, your tip is a buy. If not, your tip is the launch — TIP resolves the creator's social handle from page metadata, configures the fee-share, mints the coin, and routes your initial buy. The creator finds out they have a coin when they wake up to a notification.

Why it's defensible

It is not a UI on a primitive. It is a new surface for Bags — every creator's existing platform page becomes a launch attribute that Bags itself can never reach from inside its own app. A judge cannot replicate this by clicking around bags.fm. The product is a manifest-V3 extension with per-platform parsers, embedded wallet onboarding, and partner-fee plumbing — real engineering, not a wizard.

Virality hooks (engineered, not bolted on)

01
The "You Have a Bag" moment

When TIP auto-mints for an unsuspecting creator, the system DMs them: "You have an unclaimed bag worth 2.4 SOL. 47 fans tipped you. Claim →." The creator's surprise tweet thread is the marketing. Same mechanism that made Cash App's $cashtag viral.

02
The First-Tipper Receipt

Every mint produces a sharable artifact: "I scouted @creator on Apr 26. Bag #1 forever." Solscan link as proof. Pre-formatted for Twitter. Every screenshot is an install.

03
The Genesis 50

First 50 tippers per creator are auto-written into a permanent Genesis fee-share at micro-BPS. Once Genesis fills, the slots are publicly visible. People install TIP specifically to find Genesis spots in unsigned creators. Race + status + composability in one mechanic.

04
The Wake-Up Dashboard

When a creator finally claims, they see: "47 fans tipped you · 2.3 SOL accumulated · @scout was first." Pre-filled tweet ready to send. The creator amplifies on launch day automatically.

05
The Cascade Feed

Your Twitter followers see "[friend] just minted @creator's bag." One tip introduces TIP to your social graph. Robinhood's "your friend bought AAPL" applied to creator discovery.

06
TIP Wrapped

Year-end personalized stats card: "47 creators scouted, biggest find @rapper_xyz (+18 SOL), longest streak 31 days." Spotify Wrapped energy, deployed on creator finance. One annual viral spike, perfectly timed.

Demo (60 seconds)

0:00 YouTube. Indie creator at 14k views. 0:08 Mouse hovers. TIP pill appears. "Mint @creator's bag — be first." 0:15 Click. "0.05 SOL → mints. You'll be Genesis #1." Sign. 0:22 "Done. Receipt copied. Tweet it →" 0:30 Cut to creator's Twitter. Auto-DM appears: "47 fans tipped. Claim →" 0:40 3 weeks later. Coin chart climbs. Genesis 50 wall fills. 0:50 Tipper's wallet: +18 SOL accrued. Posts thread. Demo ends.

Architecture, briefly

  • Manifest V3 Chrome extension; content scripts per platform; metadata parsers extract handles.
  • Next.js + Supabase backend on Vercel.
  • Privy or Dynamic for embedded wallets so non-crypto users sign up with email.
  • Bags TS SDK for fee-share config, launch, swap, and partner-key plumbing.
// Product No. 2

REDEEM

Holders burn tokens to claim real perks — signed merch, backstage QRs, 1-on-1 Zooms, named-in-credits, voice memos. Coins become deflationary coupons.

Bags API Fee Sharing Payments Social Finance Other

How it works

A creator opens REDEEM and defines perks. Each perk has a token cost, a supply (e.g., 5 backstage passes), and a fulfillment method — manual, or auto via Discord, Calendly, Shopify, email. A holder browses the coin's perk catalog, clicks redeem, signs the burn transaction, and receives the perk. The supply of the creator's coin compresses on every burn; remaining holders' positions appreciate.

Why it's defensible

Burn-on-claim is a new mechanic. Bags's standard launch flow has nothing equivalent. The contract layer is real Solana program code (verify holding → burn → record event → trigger fulfillment webhook). Every successful redemption produces a public on-chain record that becomes a leaderboard, a bragging right, and a tweetable artifact.

Virality hooks (engineered, not bolted on)

01
The Live Burn Counter

Every coin has a giant public counter — "BURNED: 48,392" — ticking up in real time. Low burn = coin nobody believes in. High burn = engagement metric that beats anything Spotify shows. A new status indicator that didn't exist before.

02
The Redeemer Wall

Every redemption is publicly logged: "@vinnyx_99 redeemed Backstage Pass #3 — burned 1,200 — Cleveland." Each row is a tweet. Some perks are 1-of-1; those redeemers are forever bound to them on-chain.

03
Race-to-Redeem Drops

Creator schedules a milestone-locked perk: "5 signed vinyls unlock at $100K mcap." When the milestone fires, redemption opens to all holders simultaneously. Fastest 5 click win. 30-second resolution. Stream-able, broadcast-able event.

04
The Receipt Card

Every redemption auto-generates a beautiful PDF/JPG: creator's signature, perk number, burn amount, date, Solscan proof. Designed for Instagram Story dimensions. The artifact is the share button.

05
The Fan Pyramid

Tiered status by lifetime burns: Bronze ≥100, Silver ≥1K, Gold ≥10K, Platinum ≥100K, Diamond (1-of-1 perks). Status that ascends with destruction — fans compete to burn more than the next fan to climb the pyramid.

06
Composable Redemption Memes

Creators design redemptions that themselves go viral: "Burn 10K to be in my next music video crowd shot," "Burn 100K — I'll write a song about your name." Every creator joining REDEEM brings their own marketing through these tweets.

07
REDEEM Wrapped (fan + creator)

Fan year-end: "You burned 12K, claimed 3 1-of-1 perks, top creator @x." Creator year-end: "Your fans burned 4.2M tokens. Top redeemer @bestfan with 89 redemptions." Two complementary virals each December.

Demo (60 seconds)

0:00 Coin page. Big counter: "BURNED 47,392" 0:10 Click perk: "Backstage Pass — Cleveland — 3 of 5 left — 1,200 BAGS_X" 0:20 Connect wallet. "You hold 4,800. Redeem?" Sign. 0:28 Tokens burn live. Counter ticks: 48,592. Receipt card slides in. 0:38 Receipt: "Backstage Pass #3/5 · @vinnyx_99 · signed by @creator" 0:48 Cut to fan at venue door. Shows QR. Bouncer waves them through. 0:58 Card: "REDEEM — burn coins, claim moments."

Architecture, briefly

  • Solana program: verify holdings → burn → record event → fire fulfillment webhook.
  • Next.js dashboard for creators (perk catalog) + holder coin pages.
  • Webhooks to Discord (auto-role), Calendly (auto-book), Shopify (auto-checkout).
  • Receipt-card image generator using Vercel OG.
§ 5 — Why the pair compounds

The flywheel.

Each product is strong alone. Together they are a closed loop that feeds itself. TIP brings new creators to Bags. REDEEM gives their coins something to do. Burns compress supply. Compressed supply rewards top holders. Top holders tweet. New users install TIP. Cycle restarts.

┌──────────────────────────────────────────────────┐ │ │ │ TIP — every web page is a launchpad │ │ ↓ │ │ First-tipper auto-mints creator's coin │ │ ↓ │ │ Auto-DM wakes creator up │ │ ↓ │ │ Creator opens REDEEM, defines perks │ │ ↓ │ │ Holders burn-to-redeem (supply compresses) │ │ ↓ │ │ Top holders auto-dividend, post receipts │ │ ↓ │ │ New users install TIP │ │ ↓ │ └──────────────────────────────────────────────────┘ each loop expands the next

The strategic insight is that each product makes the other more valuable. TIP without REDEEM mints coins that have no utility past speculation. REDEEM without TIP requires creators to come to Bags voluntarily — slow growth. Bound together, they close the loop on creator economics with no leakage.

§ 6 — Our own coin

$BAGGED — the meta-demo.

The hackathon requires our project to have a linked token. We turn the rule into the demo.

The product is its own most active customer. Judges open the demo and see $BAGGED's revenue chart climbing in real time, not as a narrative — as a live fact. The linked-token requirement becomes our most credible proof of traction.

§ 7 — The plan

Six weeks. Three submissions. Eight tracks.

Week 1
Bags primitives spike.

Mint a coin end-to-end via the SDK. Wire fee-share-by-handle for 5 collaborators. Trigger an auto-dividend in dev. By end of week, a CLI script can launch any coin from a JSON spec.

Week 2
TIP extension MVP.

Manifest V3 scaffold. Content scripts for YouTube + X + Spotify. Metadata parsers + handle resolution. Embedded wallet via Privy. Mint-on-tip flow live for one platform end-to-end.

Week 3
TIP virality layer + Genesis 50.

Auto-DM bot. Wake-up dashboard. Genesis tier composability built into the launch flow. Public leaderboards. Receipt-card generator. First viral test on 50 real creators.

Week 4
REDEEM contract + creator dashboard.

Solana program for verify-burn-record-fire. Creator perk catalog UI. Discord webhook. Calendly integration. Live burn counter. First end-to-end redemption on a test coin.

Week 5
REDEEM virality layer + integration with TIP.

Redeemer wall. Receipt cards. Fan pyramid tiers. Race-to-redeem drops. $BAGGED coin live. Demo with one real creator (DM-recruit during weeks 3–4).

Week 6
Submission triple play.

File TIP across Bags API + Payments + Social Finance + Fee Sharing + Other. File REDEEM across Bags API + Fee Sharing + Payments + Social Finance + Other. File $BAGGED itself as a meta-Bags-API entry. Eight tracks of coverage. Polish, film, ship.

§ 8 — Who does what

Roles.

Adjust counts to team size. If we have fewer than four people, the lead absorbs the design role and the hustler role splits across the team.

// role 01
Lead / Architect

Owns Bags SDK integration, the partner-key + fee-share plumbing, and the linked-token coin design. Approves merges. Files submissions.

// role 02
Extension Engineer

Owns TIP. Manifest V3, content scripts, per-platform parsers, wallet adapter, mint flow. Single most load-bearing role for demo quality.

// role 03
Contract + Backend

Owns REDEEM. Solana program, webhook router, perk catalog API, receipt-card generator, fulfillment integrations (Discord/Calendly/Shopify).

// role 04
Frontend + Design

Owns the screenshot moments — wake-up dashboard, receipt cards, redeemer wall, leaderboards, Wrapped year-end cards. The artifacts must be beautiful or virality dies.

// role 05
Hustler / Creator Outreach

DMs 50 unsigned creators in weeks 3–4 to recruit one for the demo. Films the demo on real YouTube traffic. Drafts the launch tweets. Owns submission narrative.

// role 06
QA + Devrel

Tests the rate-limit edge cases (Bags is 1k req/hr shared). Documents the public API. Writes the README and the submission video script. Catches things the rest of us miss.

§ 9 — What kills us

Honest threats.

Creators reject auto-mints
Build an opt-out from day one — creator tweets @TipExt remove and the coin is paused, fees frozen, no further mints under their handle. Make this prominent in marketing — "creators control their bag."
Handle-to-wallet resolution wrong
Cache only verified mappings (creator's own page metadata, "Twitter:" link in description, manual review for top 1000). Genuine mismatches → coin paused + manual reroute, no fees lost.
Embedded wallet UX too complex for normies
Privy or Dynamic — email sign-in, Solana wallet auto-provisioned, Moonpay credit-card SOL purchase. The first tip should never require the word "wallet" to appear on screen.
Burn rate collapses liquidity
Per-perk supply caps — redemption may use no more than 5% of circulating supply per drop. Soft-fail with retry banner if the cap is hit.
Creator promises a perk, doesn't deliver
30-day automatic refund-and-mint: tokens get re-minted to the redeemer's wallet if the creator doesn't confirm fulfillment. Public burn counter rolls back, redemption row annotated "unfulfilled."
Bags rate limit (1k/hr) hit during demo
Aggressive caching layer in front of all read endpoints. Server-side request budget per IP. Document this gracefully — if Bags rate-limits us, queue and retry transparently.
No real creator for the demo
Hustler role's #1 deliverable in weeks 3–4. DM 50 unsigned creators. Offer the first 5 a free coin launch + Genesis tier seed + a percentage of TIP's partner fees. One bites = demo is real.
§ 10 — Appendix

Tech and endpoints.

Stack

Frontend (web)Next.js 14 App Router · React · TypeScript · Tailwind
Frontend (extension)Manifest V3 · vanilla TS + React content scripts · Vite
BackendNext.js API routes on Vercel · Supabase (Postgres + auth)
On-chainSolana · Anchor for the REDEEM program · @solana/web3.js
WalletsPrivy (preferred) or Dynamic — embedded + external
Bags@bagsfm/bags-sdk · API base public-api-v2.bags.fm · x-api-key header
WebhooksDiscord bot · Calendly · Shopify · SendGrid
Image genVercel OG for receipt cards

Bags endpoints we touch

EndpointUsed by
POST /fee-share/configTIP — per-creator fee-share on first tip
POST /token-launch/create-token-infoTIP — token metadata + image
POST /token-launch/create-launch-transactionTIP — launch tx
POST /solana/send-transactionTIP / REDEEM — broadcast
POST /trade/swapTIP — buy into existing coin
GET /trade/quoteTIP — pre-quote for slippage
GET /fee-share/wallet/{provider}/{username}TIP — handle → wallet resolution
POST /fee-share/partner-config/creation-tx$BAGGED — partner key for TIP fees
GET /fee-share/partner-config/stats$BAGGED — own-revenue dashboard
GET /token-launch/lifetime-feesREDEEM — coin health metrics
GET /token-launch/feedREDEEM — discover all REDEEM-enabled coins
GET /solana/bags/pools/token-mintREDEEM — pool keys for swap routing

Track filing plan

SubmissionTracks filed
TIPBags API · Payments · Social Finance · Fee Sharing · Other
REDEEMBags API · Fee Sharing · Payments · Social Finance · Other
$BAGGED meta-appBags API · Other

Combined unique track coverage: Bags API · Payments · Social Finance · Fee Sharing · Other — 5 of 9 tracks with three submissions. Add Privacy via REDEEM stealth-claim option = 6. Add AI Agents via TIP creator-detection bot = 7. Realistic ceiling 7 of 9.