Skip to main content

BitView Checkpoint

Watch streams. Earn tokens. Win all three sides.

BitView is the watch-to-earn layer for live streaming. Twitch streamers create a Solana-backed distribution event in two clicks; viewers who actually show up earn tokens claimable to a self-custody wallet; BitView captures small fees on swaps, launches, and brand sponsorships and runs the infrastructure that makes the loop liquid.

This site is the canonical documentation: technical reference, operational guides, business strategy, tokenomics, and roadmap.

Read in this order​

SectionWhat you'll find
Business overviewWhy this is profitable, the three-way win, the elevator pitch
Funding modelWhere viewer rewards come from, the four funding paths, streamer SaaS vs reward-pool split
TokenomicsBTV native token, streamer-token mechanics, pool design choices
Streamer-token economicsIdentity-tier deep dive: mint, burn, vesting, royalties, 24-month lifecycle
Cross-token swapThe AMM strategy and fee economics
NFT dropsStreamer-issued NFT drops for special events, royalties, holder utility
Revenue streamsConcrete fee schedule, unit economics, path to profit
Three-way winsWhat viewer / streamer / BitView each get
Competitor landscapeLessons from Rally, Roll, Friend.tech
Risk and complianceSecurities, KYC, sanctions, smart-contract risk
Anti-fraudSybil resistance and slashing economics
MetricsNorth star, growth metrics, health metrics, MRR
Participant flowsViewer / streamer / BitView lifecycles end-to-end
Investor pitchOne-page elevator pitch with raise structure
BTV white paperMiCA Annex I-aligned utility-token doc
ArchitectureModules, data flow, deployment shape
Technical overviewPer-component deep dives across the four components — public-web, admin-web, bot, distributor — plus the identity (Keycloak) supporting infrastructure
API referenceLive REST surface served by the backend
On-chain programDistributor program, PDAs, IDL
OperationsRun locally, env vars, production deployment
SecurityDisclosure policy, bug bounty, audit reports
Treasury managementWallet structure, multi-sig, reserves, reporting
LegalTerms of Service, Privacy Policy, Content Policy
GlossarySpecialized terms — Solana, DeFi, NFT, compliance, BitView-native
FAQViewer / streamer / brand questions
RoadmapPhases 1–6, exit gates, what's not on the roadmap

The 30-second pitch​

  • Streamers reward viewers who stick around — measurable, on-chain.
  • Viewers earn tokens they can actually spend (via the integrated swap router) instead of points trapped on one platform.
  • BitView earns recurring revenue from value-flow (swap fees, launchpad fees, sponsorships, subscriptions) — never by extracting from one side.
  • BTV native token aligns viewer, streamer, and platform incentives without being an investment vehicle: it's a utility stake against sybil farming and a fee-discount mechanism.
  • Built on the audited Jito/Jupiter merkle distributor on Solana mainnet. No custodial sidechain, no custom AMM, no inflationary subsidies.

What's running today​

The product is implemented across four components, all in code:

  • bot — a Rust backend (actix-web 4, tokio, MongoDB) that joins Twitch IRC, tracks presence, runs the accrual loop, builds the merkle tree on finalize, and serves a Swagger-documented REST API on port 4477. It exposes unsigned transaction builders for every on-chain action (claims, vaults, Meteora pool init + liquidity, streamer-token mint, Streamflow vesting, sponsorship acceptance) so user wallets sign and submit; the backend never holds keys.
  • public-web — a Next.js 16 / React 19 app for streamers (the /studio/* surface — distribution wizard, 8-phase resumable streamer-token launch, NFT collection creation, sponsorship acceptance) and viewers (dashboard, SPL + NFT claim, public swap). i18n via next-intl. Integrates Solana wallet-adapter, Metaplex Core / Bubblegum / Token Metadata, and Meteora @meteora-ag/cp-amm-sdk for DLMM and DAMM v2 pools.
  • admin-web — a separate Next.js 16 operator console behind Keycloak's bitview-ops realm. KPI dashboard, distribution / pool / treasury / sponsorship / fraud monitors, publish wizard, KYC review, network config, audit log, launchpad-vault allowlist editor.
  • distributor — a Cargo workspace with three Anchor programs (merkle-distributor, streamer-vault, launchpad-vault) on Anchor 1.0.2 + solana-program 3.0, plus the axum proof server, the Rust CLI tree builder, and the off-chain merkle library. Bitmap claim status (~$9 rent vs ~$16K at 100K claimants), SPL + NFT claim paths, dual purpose-gating on both vaults.

Supporting infrastructure:

  • identity (Keycloak) — single sign-on at identity.bitview.club (two realms: bitview for users / streamers, bitview-ops for staff). All three web/bot components verify Keycloak bearer tokens; admin-web uses Authorization Code + PKCE.

What's still in flight: NFT Layer 2 mint CPI (mpl-core::CreateV2 + Bubblegum), the anti-fraud detection engine (admin routes are stubbed today), admin audit-log persistence, re-audit after the Anchor 1.0 / Solana 3.0 bump. See Roadmap.

Going deeper​