Whitepaper v2.0

Bittybot · $BITTYBOT · BNB Smart Chain

§ 1

Abstract

Bittybot is an on-chain GameFi protocol where players burn $BITTYBOT to mint autonomous mining bots. Every bot contributes Mining Power (MP) to the vault and earns a proportional share of the BTCB (Bitcoin on BSC) tax reward pool — a dynamic pool funded by real trading volume of $BITTYBOT on DEX.

§ 2

Token Overview

  • ▸ Ticker: $BITTYBOT
  • ▸ Chain: BNB Smart Chain (BEP-20)
  • ▸ Total Supply: 1,000,000,000 (1 Billion)
  • ▸ Launch Platform: flap.sh (fair launch)
  • ▸ Tax Token: BTCB (Binance-Peg BTCB, BEP-20)
  • ▸ Vault Contract: 0xf58324208f9582105dC5dC77aC5DEce6a9D81f4F
§ 3

Launch via flap.sh

$BITTYBOT launches as a fair-launch token on flap.sh. The Bittybot Vault is registered as the official tax recipient during token deployment. All buy/sell tax is collected in BTCB and streamed directly to the Vault — no manual bridging, no team wallet in between.

After launch, the vault owner calls setTokens() on the Vault to bind the $BITTYBOT and BTCB addresses. From that moment on, the vault is fully autonomous.

§ 4

Mint & Burn Mechanics

Users mint bots by spending $BITTYBOT. 100% of the mint cost is burned (sent to 0x…dEaD), permanently reducing supply. Each rarity contributes a fixed Mining Power weight:

  • Common20,000 $BITTYBOT · +1 MP
  • Rare50,000 $BITTYBOT · +3 MP
  • Epic100,000 $BITTYBOT · +7 MP
  • Legendary500,000 $BITTYBOT · +40 MP
§ 5

BTCB Reward Pool (Dynamic)

Every trade of $BITTYBOT on DEX generates tax collected in BTCB and forwarded to the Vault. When syncTax() runs, 20% of newly received BTCB is allocated to the mining reward pool and distributed proportionally to each miner's Mining Power share:

userReward = userMP / totalMP × rewardPool

The pool size is fully dynamic — it grows with trading volume. No emissions schedule, no inflation. Rewards come exclusively from real trading activity.

§ 6

Vault Architecture

  • buyBot(rarity) — burn $BITTYBOT, mint MP
  • syncTax() — pull BTCB tax, allocate 20% to reward pool
  • claim() — user withdraws accrued BTCB
  • pendingReward(user) — live BTCB owed to user
  • flap.sh compatible — implements VaultBaseV2 spec
  • ▸ flap.sh compatible: implements VaultBaseV2 spec
§ 7

Roadmap

  • ▸ Phase 1 — Fair launch on flap.sh, vault bind, first mints
  • ▸ Phase 2 — Leaderboards, live analytics, marketing push
  • ▸ Phase 3 — Bot fusion & upgrade paths (MP boosters)
  • ▸ Phase 4 — Guild raids, cross-chain BTCB bridge, mobile client
§ 8

Contracts

  • ▸ Vault: 0xf58324208f9582105dC5dC77aC5DEce6a9D81f4F
  • ▸ BTCB: 0x7130d2A12B9BCbFAe4f2634d864A1Ee1Ce3Ead9c
  • ▸ $BITTYBOT: set on-chain via setTokens()
  • ▸ $BITTYBOT: TBA at launch