gabchess/kageb

KageB is a prototype built on Solana that lets traders submit orders without exposing their individual choices to the public. Four real orders go into a pool, opposing orders cancel each other out internally, and only the net aggregate result reaches the market. The public settlement trace shows the group outcome, not which participant chose to buy or sell. The name comes from a Naruto technique called Kage Bunshin. The idea is that each encrypted order is like a sealed scroll in a crowd. The blockchain sees the crowd move but cannot read the choice inside each scroll. Unlike the anime technique, KageB does not create fake or decoy trades. It only pools real orders and sends the net result onward. Each participant funds both sides of a possible trade before submitting an encrypted order. This two-sided funding prevents the public funding step from revealing whether the trader intends to buy or sell. The system requires at least four valid participants before it will lock the group. Three designated approvers called keypers must reach a two-of-three threshold to authorize the lock and later the settlement. Opposing orders cancel inside the pool, and only the residual aggregate moves to a fixed venue. The prototype runs on Solana's Devnet using synthetic, zero-decimal assets. It is custodial, upgradeable, and explicitly not safe for real funds. It has no deposit, withdrawal, or refund mechanism. Each order is limited to exactly one lot at one operator-set price. The project provides a local proof script that builds the programs, starts a local validator, and checks the full flow, plus a separate script to verify published Devnet evidence. The workspace exposes Rust protocol building blocks and a reference implementation, not a hosted service or complete trading SDK. The proof does not establish unique humans, production anonymity, private funding, protection from the operator, or safe use with real assets. If an observer already knows every other participant's order, the aggregate can reveal the remaining one. Crowd size is a demo condition, not an anonymity guarantee. The full README is longer than what was shown.