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 Flap · the butterfly lane in the BUILD family.
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.
A live monitor, test first.
The interface is already wired to a single overview schema. It currently reads a clearly labeled test snapshot and refreshes every 10 seconds; the controller API can replace it later.
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 intended route. The execution record below keeps TEST receipts separate from future production data.
What the controller checks
These are the visible rules for the current implementation.
Receipts before promises.
The entries below are TEST evidence from the current BSC adapter checks. Official CA entries will replace the placeholders after the three launches.
TEST DATA · no production contract address is implied by these rows.