BSC · BNCB · Three venues

One build.
Three lanes.

BUILD brings Flap, Four and Genius into one visible story. Each launch keeps its own identity; the shared reserve loop makes every route easy to follow.

LIVE monitor · formal BSC contract addresses are recorded below
BUILD mascot holding the green, purple and pink platform symbols
Three platforms. One reserve.Flap · Four · Genius on BSC
LIVE MONITOR
The three lanes

Same project. Different energy.

The colors follow the official platform language: purple for Flap, green for Four, pink for Genius. The crystal-hand visual keeps the family recognizable.

BOF purple Flap avatar
FlapCA recorded
BOFpurple lane

Build on Flap · the butterfly lane in the BUILD family.

Target tax3% / 3%
Market capSYNCING
BO4 green Four avatar
FourCA recorded
BO4green lane

Build on Four · the hand-and-crystal lane for the shared story.

Target tax3% / 3%
Market capSYNCING
BOG pink Genius avatar
GeniusCA recorded
BOGpink lane

Build on Genius · the G crystal lane with its platform fee shown plainly.

Platform feefixed by venue
Market capSYNCING
Data layer

Live monitor, route aware.

The page reads the controller overview API and refreshes every minute. Market-cap values and route status come from the controller.

LIVE MONITORBSC · source snapshot · last refresh
live BNCB balance
configured floor
poll · cap cache
lowest market-cap lane
BOF · Flap
SYNCING
purple lanemarket cap
BO4 · Four
SYNCING
green lanemarket cap
BOG · Genius
SYNCING
pink lanemarket cap
allocation preview: 20% operations · 80% support · pending 0 BNCBlatest: ·
Genius creator fee

Claim, then route.

Genius fees first sit in the platform escrow. A claim sends the credited BNCB to the Dev wallet, where the shared reserve controller can continue the 20/80 flow.

Controller claim panel
Turn a manual step into a visible action.

Anyone can request the action. The server checks the escrow balance, gas floor and cooldown before the Dev wallet signs. The destination remains the project Dev wallet.

Claimable BNCB Threshold Dev BNB
The reserve loop

Simple rules. Visible movement.

Incoming BNCB is measured first. The controller then records the split, reads the three caps, and routes the support amount to the lowest-cap lane.

One reserve, three destinations

The public page describes the route. Historical TEST receipts stay labeled separately from current production monitoring.

BOFFlap · purple
BO4Four · green
BOGGenius · pink
20%operations wallet
80%lowest-cap support route

What the controller checks

These are the visible rules for the current implementation.

01
Read the Dev walletwait for the configured BNCB trigger
02
Keep the gas floormaintain the configured BNB operating floor
03
Route and recordbuy the lowest-cap lane and publish the receipt hash
Public record

Receipts before promises.

Formal CA cards are shown above. Historical TEST receipts remain labeled separately from current production monitoring.

TEST DATA · no production contract address is implied by these rows.