Build on Flap · the butterfly lane in the BUILD family.
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.

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.
Build on Four · the hand-and-crystal lane for the shared story.
Build on Genius · the G crystal lane with its platform fee shown plainly.
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.
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.
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.
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.
What the controller checks
These are the visible rules for the current implementation.
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.