Participant flows
The same product, traced from three different angles. Each page below walks one actor through their full lifecycle — first contact, activation, day-to-day, long-term — with concrete actions, system touchpoints, decision points, and the value flowing in each direction.
| Page | Audience | What it covers |
|---|---|---|
| Viewer flow | A real person who watches streams | Wallet setup, Twitch link, accrual, NFT drops, claim, cash-out vs hold, returning week-on-week |
| Streamer flow | A creator with a Twitch channel | Sign-up, first distribution, NFT drops, tier upgrades, Identity-tier token launch, brand sponsorships |
| BitView flow | The platform operator (us) | Daily ops, per-distribution lifecycle, treasury management, sybil detection, incident response, weekly / monthly / quarterly cadence |
How to read these
Each flow starts with a single timeline diagram to give you the shape. Then it walks each phase in detail. Where actions touch a specific document or API surface, they link out. Where there are optional decisions, the choices are explicit.
If you only have time for one: read the actor most relevant to you. If you're evaluating BitView as a partner or investor, read all three in order — viewer → streamer → BitView — because every fee BitView captures is a value event in the viewer or streamer flow above it.
Cross-references
These flows pull together the work in:
- Architecture — what services exist
- Business overview — the strategy
- Tokenomics — what currencies move
- NFT drops — non-fungible loyalty layer
- Anti-fraud — sybil resistance
- Revenue streams — how BitView earns
- Operations — running locally / production
The flows themselves are the integration view — what each actor actually does, in order, across all of those.