Skip to Content
LearnEcosystem map
Learn · Ecosystem

A small protocol surface with several ways in.

The dashboard, swap, liquidity, and earn pages share one wallet and one BNB Smart Chain connection, but each action settles through a different contract path.

Non-custodialComposable LP tokensBEP-20 compatible

Product map

SurfaceWhat it readsWhat it can write
DashboardProtocol metrics, token prices, wallet balancesNothing by default
SwapQuotes, balances, allowances, pool reservesApproval, permit, wrap/unwrap, or swap
LiquidityPair address, reserves, wallet LP positionsApproval, add liquidity, remove liquidity
EarnMasterChef and SmartChef pool stateApproval, deposit, withdraw, harvest
TokensCurated identity plus market endpointsOpens prefilled swap or liquidity flows
GovernanceInformational roadmapNo live proposal action in the main app

Protocol layers

Interface layer

Next.js, wagmi, viem and RainbowKit connect the browser to BNB Smart Chain. A fallback list of BSC RPC endpoints is configured for reads and transaction tracking.

Routing layer

The quote engine probes candidate paths through base assets such as WBNB, BUSD, USDT, ETH, BBKFI and WBBK, then compares eligible providers.

AMM layer

The BitBlocks Router calls the BitBlocks Factory and V2 pair contracts. Pairs hold reserves, apply the constant-product invariant, and mint LP tokens.

Reward layer

One MasterChef manages many BBKFI pools. Separate SmartChef contracts each manage one pre-funded reward schedule over a defined block range.

The Finance app is one product in the broader BitBlocks ecosystem:

The bridge and vote site are separate applications. Their contracts and behavior are not inferred from the BitBlocks Finance frontend; verify their own prompts and documentation before signing.

Design boundaries

  • The Finance app is configured for BNB Smart Chain only.
  • Native BNB is represented as WBNB inside AMM paths; direct BNB ↔ WBNB actions use wrap/unwrap logic.
  • WBBK V2 is the curated active WBBK asset. WBBK V1 remains searchable but is labeled deprecated in the interface configuration.
  • 1inch is optional and only participates when its provider flag and server credential are configured.
  • Protocol routes and external routes have different spender addresses. The app derives the approval target from the selected quote.
Last updated on