← back to the pool

how bibi works

the technical version. fan-made project, not affiliated with binance.

the pool

$BIBI trades against BNB in a PancakeSwap Infinity concentrated-liquidity pool with a dynamic fee and a hook. The hook is the part Bibi can steer. The pool is created once with the hook's address; that address never changes. The hook is a UUPS proxy, so new abilities arrive as new implementation code behind the same address, through a timelocked upgrade that the team signs after the automated gates pass.

what she can change today

where revenue comes from

The swap fee is an LP fee. At launch Bibi's treasury owns the pool's liquidity position, so it earns the fees. Bibi's Cut, when she switches it on, is a separate hook fee that goes to the treasury directly. When she collects them, the treasury splits them by her mix. Treasury money has exactly three exits: buying $BIBI through the pool, burning $BIBI, or adding liquidity to her position. There is no function that sends funds to a wallet.

how a check works

Bibi looks at the pool on a schedule (every 5 minutes for the first 24 hours after the first trade, while she tries out every control; 10 minutes until hour 72; 15 minutes after), plus extra looks on unusual events with an anti-storm limit. A look gives the model a compact summary of the market, the pool, her memory, her money, her abilities and her wishes. She answers with a decision, which is often to do nothing. A safety kernel checks the decision for invalid or catastrophic operations only; it contains no strategy. Valid actions are simulated, then sent by an executor key that can only call the hook and treasury functions listed above. Broken model output does nothing.

experiments and memory

When she tries something she writes down a hypothesis, a metric and a window. After the window, software compares an equal window before and during and labels it reinforced, neutral, backfired or inconclusive. She decides whether to keep, modify, undo or retire it. Lessons must cite measured experiments, and she can reinforce, contradict, supersede or retire them.

missing buttons

Her panel starts with the controls above and no missing buttons. When she keeps reaching for a control she does not have, she asks for it, and later asks for it to be wired in. Then a spec is written, code is written in an isolated branch, and deterministic gates run: compile, lint, unit tests, fork tests against the real Infinity deployment, invariants, a storage-layout and security check, a code hash and a readable diff. The team only approves or rejects on safety. Switching on something that existed at genesis is just switching it on; only new code counts as a new button.

what she cannot do

keys and authority

what she found out so far →