Streamer flow

A creator with a Twitch channel, traced from first hearing about BitView through running their first distribution, scaling into tier upgrades, launching their own Identity-tier token, and eventually running brand sponsorship campaigns. Every phase has explicit decision points and concrete value flowing in both directions.

Timeline at a glance

T0          Discovery — peer mentions BitView, BD email, or organic find
T+1day      Sign-up — wallet + Twitch OAuth + free tier active
T+1day      Reward-budget decision — pick recycle rate, monthly outlay
T+1day      First distribution setup — pick tier, fund pool, register
T+1day      First stream with active distribution
T+stream-end  Distribution ends, snapshot, finalize, viewers claim
T+1week     Second distribution. Retention checkpoint.
T+30days    Free-tier cap hit (3 distributions/mo) — Pro upgrade nudge
T+60days    Pro tier active — unlimited distributions, custom branding,
            analytics, NFT drops at full feature set
T+90days    First NFT drop event for top supporters
T+90days+   Identity tier eligibility unlocked (avg viewers ≥ 1000)
T+120days   Identity-tier token launch — STREAM/BTV pool seeded
T+150days+  Plus tier — sponsorship marketplace open
T+180days   First brand sponsorship campaign
T+1yr       Reserve allocation begins to vest; royalty stream compounding
T+2yr       Concierge alumni tier (if Tier A); strategic partner status

Total from cold to first stream with rewards: about 24 hours if they're motivated, less for Tier-A concierge.

Phase 1 — Discovery

Three entry paths, in order of credibility:

Peer referral (highest credibility, highest conversion). Another streamer running BitView mentions it on stream, in their Discord, or in private streamer group chats. The streamer hears it from someone who already runs it.
Concierge outreach (Tier A only). BitView BD lead identifies them, sends a personalized cold email, books a 30-min demo call. Conversion rate ~30% on Tier A targeting.
Inbound (long tail). They Google "Twitch creator coin" or "watch-to-earn streamer" and land on the BitView site.

What they do: read the streamer guide, watch the demo video, possibly DM another BitView streamer they know to ask "is this legit". The fact that BitView is on Solana with audited contracts and public docs (this site) is what closes the credibility gap on cold introduction.

No commitment yet. No KYC, no contracts, no fees. The funnel goal at this phase is to get them to the wallet-connect screen.

1. Streamer connects wallet on bitview.club
   → Wallet adapter prompts; they pick Phantom / Solflare / Backpack
   → Approve

2. Sign in with Twitch
   → OAuth flow
   → User-access token authorizes BitView to read their channel info

3. Sign nonce with wallet
   → Same ed25519 signature flow as viewers, with an additional
     "I am the streamer of channel X" claim binding the wallet to
     the Twitch account

4. Backend records:
   - users collection: streamer_login → wallet (same shape as viewers)
   - streamer_profile collection (Phase 2+): tier=Free, channel_login,
     wallet, created_at, twitch_user_id

Cost: zero. Time: ~3 minutes.

They walk away with: a free-tier BitView account, ready to create their first distribution.

Phase 2.5 — How the distribution gets funded

Before the wizard, the streamer needs an answer to a question the product cannot answer for them: where is the money for the viewer rewards coming from? This is independent of any BitView subscription fee — the subscription pays for the SaaS layer (analytics, branding, unlimited events, marketplace seat), not for viewer rewards.

The full economics, including streamer-tier × budget combinations and the four funding paths, are in Funding model. The compressed version below is what the streamer actually decides in the 5 minutes before opening the wizard.

Two budgets, not one

Budget A — paid to BitView                Budget B — paid to viewers
  Stripe, monthly USD                       on-chain, per distribution
  Free       $0                             Native    funded by streamer USDC/SOL → BTV
  Pro        $99 / mo                       Identity  funded by streamer STREAM + BTV match-fund
  Plus       $499 / mo                      Sponsored funded by brand USDC

  Free billing → Native only.
  Pro / Plus   → Native or Identity. Plus also unlocks Sponsored.

Budget A is fixed and depends only on tier; Budget B is the streamer's number and is sized from their reward strategy.

Where Budget B comes from

The streamer picks a recycle rate against their existing channel revenue and turns the result into a monthly reward budget:

existing channel revenue (Twitch subs, bits, ads, sponsors)
        × recycle rate (typically 10–30%)
        = monthly reward budget for viewers

example:
  $2,150 / month gross streaming revenue
  × 20%  recycle rate
  = $430 / month reward budget

A single distribution typically draws against this monthly budget. A streamer running 4 distributions a month at $100 each is recycling $400 / month into viewer rewards regardless of whether they're on Free, Pro, or Plus.

Picking the funding path

Three options, picked once per distribution at the wizard's first step. Availability depends on billing tier:

Tier	Available to	Who funds the pool	Viewer claims	When to pick
Native	Free / Pro / Plus	Streamer's USDC or SOL (swapped to BTV in the wizard)	BTV	Default. Only option on Free billing.
Identity	Pro / Plus	Streamer's own SPL token (from launchpad pool) + per-event BTV match-fund	STREAM (with swap path)	Streamers with a fan community willing to hold
Sponsored	Plus	Brand sponsor's USDC	USDC or BTV	Brand campaigns

For the first distribution, the wizard recommends Native unless the streamer has a specific reason (Identity-tier fan community already proven, brand campaign already lined up).

The handoff into Phase 3

By the time the streamer opens the wizard they've already decided:

Their monthly reward budget (Budget B).
The size of this individual distribution (a slice of Budget B).
Which assets to distribute — BTV (every plan), their own streamer token (Pro/Plus only), and/or NFTs from a collection they own (Pro/Plus only). Sponsorships are brand-initiated and never originate from this wizard.
Their BitView tier (Budget A).

The wizard turns those answers into a funded distributor vault.

Tier matrix

Plan	BTV	Identity token	NFT collection / airdrop	Sponsorship
Free	✓	✗	✗	✗
Pro	✓	✓	✓	✗
Plus	✓	✓	✓	✓

Tier is a hard gate, not a paywall preview — Free streamers don't see the Token or NFT pages in the studio at all. The asset selector in the wizard only renders the rows the streamer's plan allows.

Phase 3 — First distribution setup

The streamer's most important moment. If this works, retention is high. If it goes badly, they churn permanently and tell other streamers. Tier-A streamers get white-glove setup; Tier-B/C use the self-service wizard.

The 4-step wizard

The wizard auto-infers the funding model from the streamer's billing tier and which assets they pick — no separate "tier picker" screen. Total surface area is four steps (or three when the streamer already holds enough BTV for a Native-only event).

Step 1 — Configure the event
   → channel + title
   → periodicity, duration, max_per_viewer, optional start_at
   → Asset selector (multi-select, per-asset amount):
       • BTV                    (default-on, every plan)
       • Streamer token         (Pro/Plus, only when launched at /studio/token)
       • NFT collection(s)      (Pro/Plus, listed from /studio/nft)

Step 2 — Acquire BTV (only when BTV is in the asset set)
   → Frontend shows: "you need N BTV ≈ X USDC"
   → One-click swap via Jupiter router (USDC/SOL → BTV)
   → BitView captures 0.10% of the swap

Step 3 — Fund vault + register
   → Backend builds the unsigned `init_distributor` tx + the vault
     funding transfer in one signature bundle (or N if multi-asset).
   → Streamer signs from the browser; the bot holds no keys.
   → POST /distributions-api/register persists the row with
     `event_id` grouping all assets in the same logical event.

Step 4 — Backend joins channel
   → Bot confirms registration, ensures Twitch listener is up.
   → "Your distribution is live."

The tier is inferred:

Free streamer → only BTV is selectable in step 1, so the event is implicitly Native.
Pro / Plus streamer → Identity / NFT rows appear and become selectable; picking the streamer token = Identity, picking an NFT collection = NFT airdrop. Multi-select is supported — N siblings share an event_id.
Sponsored events don't originate here. The brand initiates them via /sponsor and the streamer accepts at /studio/sponsorships/[id]/accept.

Studio entry points

Path	Purpose	Gate
`/studio`	Dashboard — tier badge, stats, quick actions	Streamer role
`/studio/token`	One-off Identity-token launchpad (10/5/85 vesting)	Pro / Plus
`/studio/nft`	NFT collections + on-chain `init_nft_distributor`	Pro / Plus
`/studio/distributions/new`	The 4-step wizard	Streamer role
`/studio/sponsorships/[id]/accept`	Accept a brand sponsorship	Plus

What can go wrong

Insufficient SOL for fees. "You need ~0.05 SOL for transaction fees" with a one-click on-ramp link.
Twitch chat listener fails to attach. Backend retries; if it fails repeatedly, the distribution is created in pending status and an alert fires for ops. The streamer is told "we'll be live in the chat within 5 minutes — your distribution will start accruing then."
Wallet rejects the signature. Often a Phantom cache issue; refreshing the wallet extension fixes it.

Phase 4 — During the stream

While they stream, the streamer can:

Show an OBS overlay of live accrual leaderboard. Comes as a simple URL the streamer can browser-source into OBS. Shows top-10 viewers ranked by accrued amount in real time. Dramatically increases viewer engagement (publicly visible competition).
Use chat commands. !bitview → BitView bot posts the wallet-link URL in chat (rate-limited to 1 message per 5 minutes). !earned <login> → bot posts how much that viewer has accrued.
Check the dashboard live. Per-second view of: linked viewers present, total credited so far, sybil-flag count (informational), retention curve.
Trigger boost periods (Phase 3+). One-click "next 30 minutes earn at 3× rate" announcement.

No required action during stream. The accrual loop runs autonomously. The streamer can ignore BitView entirely while streaming and viewers still earn correctly.

Phase 5 — Distribution end + finalize

When end_at passes (or the streamer manually triggers stop), the distribution stops accruing.

24-hour grace window. Any viewer who appears in chat in the final hour but somehow misses the snapshot gets caught up. After that, an operator (Tier-A: BitView ops; Tier-B/C: streamer with admin permission) calls POST /distributions-api/{id}/finalize.

Backend on finalize:
Status flips: active → snapshotting
Reads all accruals for this distribution from MongoDB
Builds merkle tree (CSV-compatible with the existing distributor
     CLI's create-merkle-tree format)
Stores tree to disk + merkle_snapshots document
Operator calls set_enable_slot on the distributor program
     → publishes the merkle root on-chain
Status flips: snapshotting → claimable
Notifies viewers + streamer

The streamer doesn't need to do anything technical here. For Tier-A concierge, the BitView ops team handles every snapshot. For Tier-B/C, it's a one-click "finalize and publish" button on their dashboard, requiring a single signature.

Phase 6 — Post-stream review

The streamer's dashboard now shows:

Metric	Value
Total credited	198,500 BTV (1.5K BTV unallocated due to chat dead spots)
Unique viewers credited	1,247
Average accrued per viewer	159 BTV
Top 10 viewers	(leaderboard)
Retention curve	minute-by-minute viewer count over the stream
Cohort breakdown	new vs returning, sub vs non-sub, by region
Sybil-flagged	14 wallets, 1.1% (within healthy band)

The streamer can:

Tweet a result template. "Just paid out $1K to 1,247 viewers via @bitview — link your wallet at bitview.club to earn next time"
Review viewer cohort segmentation. Pro/Plus tier feature.
Plan the next distribution. The same wizard, parameters pre-filled from this one.

Phase 7 — Optional NFT drop

Around special events (milestone streams, charity events, anniversaries), the streamer creates an NFT drop to thank their most valuable viewers.

1. Open NFT drop wizard
2. Pick drop type: Premium (≤500) or Mass (everyone present)
3. Pick eligibility predicates from the menu:
   → top_n_by_accrual (e.g., top 100)
   → present_at_timestamp (e.g., the moment they hit a milestone)
   → subscribed_to_channel (e.g., tier 2+ subs only)
   → has_badge (e.g., founders only)
   → AND-ed together
4. Upload artwork
5. Set royalty percentage (default 5%)
6. Set holder utility (Discord role, future-drop priority, etc.)
7. Review eligible wallet count: "247 wallets qualify"
8. Pay $5 (Free tier) or $0 (Pro/Plus)
9. Sign the merkle-root-publishing transaction

The drop is now live. Viewers see a notification, claim their NFT, trade it on Magic Eden / Tensor. Streamer earns 4.5% royalty on every secondary sale (BitView keeps 0.5% as platform take).

Phase 8 — Tier upgrades

This is where SaaS revenue compounds for BitView.

Free → Pro ($99/mo)

Trigger: the streamer hits 3 distributions in a calendar month (the free-tier cap), OR wants any of: custom branding on distribution pages, full analytics dashboard, unlimited NFT drops, Identity-tier launchpad access.

Conversion event: typically the third or fourth distribution in a month. The free tier surface tells them "you've used 3/3 free distributions; upgrade to Pro for unlimited."

The decision: $99/mo divided by ~4 distributions = $25 per distribution, vs $5/event on free tier. They pay more on Pro once they're running 5+ distributions a month OR they need any of the locked features. Most streamers running BitView seriously want the analytics or branding regardless, so the upgrade math is conservative.

Conversion rate target: 25% of active streamers within 90 days.

Pro → Plus ($499/mo)

Trigger: access to the sponsorship marketplace + brand-sponsor NFT co-mints + cohort export + dedicated support.

Gated audience: streamers above some audience threshold (TBD, likely 5K avg viewers). Below that, the marketplace doesn't get value from listing them so we don't sell Plus.

The decision: $499/mo is fully justified by a single $5K+ brand campaign per month that they otherwise couldn't have closed. Top-tier streamers do many of those.

Conversion rate target: 15% of Pro streamers within 180 days.

Phase 9 — Identity-tier token launch

For Pro+ streamers above the 1000-avg-viewer threshold who want their own token. The full mint mechanics, supply allocation, burn paths, anti-rug protections, and 24-month lifecycle are in Streamer-token economics. The broad context lives in Tokenomics §Streamer-token mechanics.

1. Streamer opens the Identity-tier launchpad
2. Picks token name, symbol (e.g., "PEWPIE", "PEW"), decimals (default 6)
3. Uploads token logo
4. Sets launch price (Approach A audience-anchored, B target market
   cap, or C manual). Audience-anchored default: market cap =
   max(avg_viewers × $5, $5,000). See [Streamer-token §Initial
   price determination](/docs/business/streamer-token#initial-price-determination).
5. Decides seeding path:
   - Path A — Match-funded (recommended): streamer puts up 25K BTV,
     BitView puts up 25K BTV. Total BTV side = 50K BTV. Standard
     0.10% / 0.10% fee split.
   - Path B — BitView-only: BitView puts up the full 50K BTV side
     alone; streamer puts up 0. BitView protocol fee rises from
     0.10% to 0.20% to compensate; streamer royalty stays 0.10%.
6. Pays launch fee: 1 SOL (~$140) OR stakes 10K BTV for waiver
   (waiver stake unlocks 30 days post-launch).
7. Signs the bundle of transactions:
   a. Create SPL mint (decimals=6, mint_authority=launchpad_pda,
      freeze_authority=None)
   b. Mint 100M PEWPIE → launchpad distribution PDA
   c. Disable mint (mint authority → None; supply hard-capped at 100M)
   d. Create Metaplex metadata
   e. Allocate 10M PEWPIE → streamer reserve vesting PDA (24mo linear,
      no cliff)
   f. Allocate 5M PEWPIE → BitView protocol vesting PDA (48mo linear,
      1yr cliff)
   g. Initialize Meteora DLMM PEWPIE/BTV pool with seed liquidity
      (BTV side per chosen path; STREAM side = 50K BTV / launch_price,
      drawn from the 85M distribution rewards pool)
   h. List in BitView discovery + swap router

What the streamer walks away with:

A live SPL token mint they own (mint authority revoked at launch; total supply hard-capped at 100M forever).
A vested reserve of 10M STREAM — notional value depends on launch price (~$1,200 at audience-anchored 0.024 BTV/STREAM for a 2,400- viewer streamer; up to ~$50K at higher Approach B/C launch prices for top-tier streamers).
A live trading market where every swap pays them 0.10% creator royalty.
The ability to fund Identity-tier distributions with their own token (drawing from the 85M rewards pool) paired with per-event BTV match-funding to back the value distributed.
A discovery listing on BitView.

Concrete revenue scenarios:

Scenario	Daily volume	Annual royalty
Small but active	$1K/day	$365
Mid-tier	$10K/day	$3,650
Top tier	$100K/day	$36,500
Viral moment / mainstream attention	$1M/day during the moment	$3,650/day

These compound with the reserve allocation unlock and any sponsorship revenue.

Phase 10 — Brand sponsorships (Plus tier, Phase 4+)

The streamer's audience reach is now a marketable asset.

1. Brand creates a campaign in the marketplace:
   "$10K USDC, looking for 5 streamers in Just Chatting category,
   18-34 audience, English"

2. Streamer (Plus tier only) sees it in their inbox
3. Reviews terms in standardized format (one-pager: budget, expected
   reach, brand requirements, BitView take rate)
4. Accepts in one click → signs commitment

5. Brand deposits $10K USDC into BitView marketplace escrow

6. Streamer runs the distribution as a Sponsored-tier event
   → Brand co-branded landing page
   → Optional NFT drop with brand logo (Plus tier)
   → Distribution pool funded with brand's USDC

7. Stream ends, distribution finalized:
   → BitView keeps $500 (5% take rate)
   → Streamer keeps $500 (5% co-share, on top of any other revenue)
   → $9,000 → viewer pool

8. Brand gets a campaign report:
   → unique wallets credited
   → claim rate
   → cohort overlap with brand's existing audience
   → on-chain proof of distribution (auditable forever)

The streamer's economics: $500 cash + audience engagement proof + NFT drop holders who carry the brand campaign for years afterward. This is the highest-margin revenue line for top-tier streamers, often $5K-$50K/month at maturity.

Phase 11 — Long-term

A streamer who's been on BitView for 18+ months is:

Earning streamer-token reserve allocation (vesting over 2 years).
Earning streamer-token swap royalties (passive, recurring).
Earning NFT royalty stream (passive, growing with collection size).
Running 1-2 brand campaigns per month (Plus tier).
Hosting a Discord with multiple BitView-bot-managed token-gated rooms.
Possibly a Tier-A concierge alumnus with a dedicated point of contact at BitView.

Monthly revenue from BitView channels for a top streamer at this stage:

Line	Indicative
Distribution accrual cost (paid out, not received)	-$2,000
Streamer-token swap royalties (0.10% × $300K monthly volume)	+$300
NFT royalty stream	+$200
Brand sponsorship co-share (5% of $20K avg)	+$1,000
Reserve allocation (vesting tranche, valued at current price)	+$2,000
Net monthly	~+$1,500

Plus whatever they pay for Plus tier ($499) and the secondary effects: better audience retention on Twitch, Discord engagement uplift, mainstream press coverage of their on-chain community.

What can go wrong over the long term

Failure	What happens	Mitigation
Streamer takes 6 months off	Distributions stop, accruals are zero, but their account stays linked. Returning is a one-step thing.	Re-engagement email at month 3 and 6.
Streamer-token price collapses	Their reserve becomes worthless. Royalty stream shrinks.	Public; both sides accept this risk at launch.
Streamer rugs / endorses scam	Delisting from BitView router and discovery. Identity-tier permanently revoked.	Content policy at sign-up. Public delist log.
BitView platform fee schedule changes	Phase 5+ governance vote. Streamers (as BTV holders) participate.	Documented in Tokenomics §Governance.
Twitch suspends streamer's account	Distributions can't run for that channel. Past royalties continue.	Streamer can re-link a different channel after Twitch ban lifts.

What the streamer never has to do

Never custodially deposit funds with BitView. Their wallet, their keys.
Never pay BitView in advance beyond the optional Pro/Plus subscription via Stripe. Distribution pools are funded by themselves and stay theirs until viewers claim.
Never confuse the Pro/Plus subscription with viewer rewards. The subscription pays for SaaS features (analytics, branding, unlimited events, marketplace seat). Viewer rewards are funded separately, per distribution, by the streamer's own reward budget — or by a brand sponsor in Sponsored-tier events. See Funding model for the full breakdown.
Never share their Twitch credentials. OAuth flow only.
Never run a custom client. Web app only.
Never approve unlimited token allowances. Every transaction is explicit-amount.

Cross-references

Funding model — where the reward budget comes from and who pays viewers in each tier
Tokenomics — what currencies are involved at each phase
NFT drops — non-fungible loyalty layer
Revenue streams — what BitView captures from the streamer's flow
Streamer guide — the streamlined how-to for end users
API reference — endpoints touched at each phase

Timeline at a glance​

Phase 1 — Discovery​

Phase 2 — Sign-up​

Phase 2.5 — How the distribution gets funded​

Two budgets, not one​

Where Budget B comes from​

Picking the funding path​

The handoff into Phase 3​

Tier matrix​

Phase 3 — First distribution setup​

The 4-step wizard​

Studio entry points​

What can go wrong​

Phase 4 — During the stream​

Phase 5 — Distribution end + finalize​

Phase 6 — Post-stream review​

Phase 7 — Optional NFT drop​

Phase 8 — Tier upgrades​

Free → Pro ($99/mo)​

Pro → Plus ($499/mo)​

Phase 9 — Identity-tier token launch​

Phase 10 — Brand sponsorships (Plus tier, Phase 4+)​

Phase 11 — Long-term​

What can go wrong over the long term​

What the streamer never has to do​

Cross-references​