Skip to main content

Treasury management policy

Status: PROPOSED v0.1. This is the working draft of BitView's treasury policy. It is public by design — partners, auditors, regulators, and BTV holders should be able to read exactly how BitView manages capital. Final policy is ratified by the BitView board (and, in Phase 5+, by BTV-weighted governance vote).

Purpose and principles

BitView's treasury exists to fund operations and bootstrap network liquidity — nothing else. We are not a fund, not a market maker, and not a yield product. The treasury policy below is designed so that anyone reading it can predict our actions in any given scenario.

The four governing principles:

  1. Operational solvency first. Cash reserves cover ≥ 12 months of operating expenses at all times. Any treasury action that would compromise this floor is automatically rejected.
  2. Transparency over privacy. Treasury wallet addresses are public. Every quarter we publish composition, inflows, outflows, and decisions taken.
  3. Conservative posture by default. No leverage. No third-party yield farming with operating reserves. No counterparty exposure beyond our explicit LP positions.
  4. Aligned, not extractive. Treasury accumulates BTV slowly from protocol fees and matches USDC operating spend; we do not target indefinite USD-denominated growth of the treasury, which would imply over-extraction from users.

Wallet structure

Six wallet types, each with documented purpose, signing requirements, and balance bounds. All addresses are published in the quarterly transparency report.

1. Cold treasury

FieldValue
PurposeLong-term BTV / SOL / USDC reserves
Signers3-of-5 multi-sig
Signer composition2 BitView leadership, 1 BitView ops, 1 external advisor, 1 community-elected (Phase 5+)
Typical balance6+ months operating expenses + treasury BTV emission allocation
Movement frequencyMonthly or less
Out-of-band confirmationEvery withdrawal requires Slack + email confirmation by 2 of 3 leadership signers

2. Hot operating

FieldValue
PurposeDaily operating expenses, gas reserves, emergency response
Signers2-of-3 multi-sig
Signer compositionAll internal ops
Typical balance≤ 2 weeks operating expenses
Refill cadenceWeekly from cold, automated via signed proposal

3. Fee collection

FieldValue
PurposeAtomically receives 0.10% protocol fees from swap router
Signers2-of-3 multi-sig
Typical balanceWhatever has accumulated since last sweep
Sweep cadenceWeekly to cold treasury (BTV) and USDC operating wallet (USDC fees)

4. LP positions

FieldValue
PurposeHold LP tokens for treasury-seeded BTV/SOL, BTV/USDC, STREAM/BTV pools
Signers2-of-3 multi-sig
Movement frequencyQuarterly review only; intra-quarter only on emergency

5. Airdrop dispenser

FieldValue
Purpose100 BTV onboarding airdrops to new viewers
SignersHot wallet (single signer or 1-of-2) for low-friction operation
Typical balance≤ 1 week of airdrop demand
Refill cadenceWeekly from cold treasury

6. Stripe payout

FieldValue
PurposeReceives USDC from Stripe subscription payouts
Signers2-of-3 multi-sig
Movement frequencyMonthly sweep to cold or operating

Operating reserves policy

ReserveTargetFloor (triggers action)
Operating runway (USDC + SOL)12 months at current burn6 months
BTV emission backingPer-published curve(immutable)
LP positionsPer Liquidity policy(immutable initial seeds)
Bug bounty reserve$200K USDC$100K
Audit reserve$250K USDC$100K
Insurance premium reserve12 months when active (Phase 4+)6 months

When any reserve hits its floor, an emergency review is triggered (48-hour SLA) and one of three actions is taken:

  1. Rebalance from another reserve (if surplus exists elsewhere).
  2. Activate the contingent operating-cost-reduction plan (pre-defined: pause non-essential marketing spend, defer non-critical hires, etc.).
  3. Initiate fundraise / bridge round (last resort).

The emergency review and chosen action are publicly disclosed within 30 days.

Revenue allocation

How fee revenue flows once collected. This is the published plan; deviations require board (Phase 1–4) or governance (Phase 5+) approval and are disclosed.

SourceDefault allocation
Subscription revenue (USDC)100% to operating expenses
Swap protocol fees (BTV)Held in treasury BTV until dedicated operational need; not auto-converted
Sponsorship marketplace (USDC)100% to operating expenses
Token launch fees (SOL)100% to operating expenses
Distribution creation fees (USDC)100% to operating expenses
LP fee incomeCompounded into LP positions
Slashing income (BTV)Held in treasury BTV; can be redistributed in supplemental distributions
Streamer-token protocol allocationHeld vested per token's schedule; not actively traded

No buybacks of BTV are committed in Phase 1–4. Buybacks become a governance-vote option in Phase 5+. Until then, treasury BTV accumulates from fees and is held.

Investment policy (what we do NOT do)

Encoded in policy and enforced by multi-sig veto:

  • No leveraged positions on any treasury asset.
  • No third-party yield farming with operating reserves. The USDC /SOL operating runway is held in spot, not deployed to Kamino / MarginFi / Drift / any other yield product.
  • No counterparty exposure — no lending of treasury BTV to market makers against their inventory, no unsecured loans to anyone.
  • No POL bonding (Olympus-style buyout-of-LP-tokens).
  • No private deals on BTV outside the published allocation table.
  • No discretionary BTV minting — supply is fixed at 1B.
  • No vesting acceleration — on-chain enforced.
  • No marketing-paid promotion of BTV as an investment.
  • No staking BTV through the treasury for yield — treasury BTV is held passive.

Decision authority

Per BitView flow §Decision authority.

DecisionAuthorityProcess
Hot wallet refill2-of-3 ops multi-sigDocumented in monthly report
Cold-storage withdrawal3-of-5 multi-sigOut-of-band confirmation, documented in quarterly report
LP rebalanceTreasury committeeQuarterly, public decision
Emergency operating cost reductionLeadership + ops lead48h SLA; public within 30 days
Revenue allocation deviationBoard (Phase 1–4) / governance vote (Phase 5+)Public proposal + comment window
Treasury policy changesSame as aboveSame as above

Conflicts of interest

The following are explicit conflict-of-interest disclosures:

  • Team members hold BTV per the published 12% team allocation. This aligns with platform success but means treasury decisions affecting BTV price affect their personal positions.
  • Investors hold BTV per the published 8% investor allocation. Investor seats on the board (if any) recuse from votes on treasury actions that materially affect BTV market price within 90 days of the action.
  • External advisors disclose any pre-existing positions in BTV, streamer tokens, or competing platforms before assuming a board / multi-sig role.
  • No team member personally trades BTV during the 14 days before any quarterly transparency report publication.

Reporting cadence

CadenceWhat's published
MonthlyInternal: full ledger; reconciled on the 1st of next month
QuarterlyPublic transparency report with: wallet composition (USD-equivalent + native), inflows/outflows by category, BTV emission progress, slashing events, bug bounty payouts, decisions taken
AnnuallyFull P&L, audit summary, strategy refresh, treasury policy review (any proposed amendments)

The quarterly transparency report is published to the checkpoint site under a dedicated Transparency section once production launches. Format follows the template that ships alongside the first report.

Audit rights

The treasury is auditable by:

  • External auditor appointed annually for the audit summary.
  • BTV holders (Phase 5+) via a community-funded audit triggered by a governance vote with quorum.
  • Investors with information rights per their term sheet.
  • Counsel in any jurisdiction where regulatory inquiry is initiated.

Public on-chain visibility means anyone can independently reconstruct treasury composition from the published wallet addresses without our cooperation.

Annual treasury policy review

This document is reviewed and ratified annually. Each annual review considers:

  • Whether reserve targets still match scale (e.g., bug bounty reserve needs raising as TVL grows).
  • Whether new revenue lines need explicit allocation rules.
  • Whether the wallet structure has held up against operational experience (e.g., do we need a separate sanctions-quarantine wallet for slashed-but-appealable funds).
  • Whether the no-do list needs additions (e.g., new DeFi product categories that are tempting but inconsistent with the principles).

Amendments require board (Phase 1–4) or governance (Phase 5+) approval and are disclosed in the next quarterly transparency report.

Open questions

  • Should swap-fee BTV be auto-converted to USDC to better fund operations? Default no (held in BTV) — gives us optionality and doesn't reflexively pressure the BTV/USDC pool. Revisit if revenue outpaces USDC operating spend significantly.
  • What's the right reserve sizing for a future insurance premium (Sherlock / Neptune Mutual cover)? Defer until Phase 4 with $5M+ TVL trigger.
  • Should we publish per-wallet balances or only category totals? Default: category totals (less doxxing risk for individual signers, same auditability). Revisit annually.