Defense bots leak their trigger. Keel's can't be found.
Watch any liquidation-protection bot act and you can locate its trigger, then hunt it. Keel's trigger is impossible to locate from its behavior, and it proves on-chain that its policy never changed.
The idea, in three moves.
A bot's actions are public, so a fixed trigger is a secret that leaks one bit at every price level. Keel removes the leak, then proves it played fair.
The trigger moves
Keel re-draws its trigger at every price level from a secret salt, shifted only upward. Randomness can make it act earlier, never later. Watching it fire tells you nothing about where it fires next.
The policy is sealed first
Before the market moves, a hash of the whole defense policy goes on-chain. A sealed envelope, handed to the referee before the match. It cannot be swapped later.
Everything is provable after
Every defense carries a signed receipt. At the end, Keel opens the envelope and anyone can re-check every round against the sealed policy. Secrecy, audited.
See it for yourself.
Three pages, in order: watch the defense, run the attack, check the proof. Each one explains itself as you go; the docs cover every term.
Watch the same crash hit two defenders. The starter bot's trigger gets found; Keel's doesn't.
Watch it survive →A real Bayesian attacker hunts both bots, then drains the one it can predict.
Attack it →The on-chain proof, reconstructed live from Sepolia events. Every claim links to Etherscan.
Check the proof →Who needs this? Anyone whose position is public.
On-chain, your collateral, your debt, and your defender's behavior are all visible. The only thing that can stay secret is when you'll act, and only if it's built to stay secret under observation.
Billions in looped staked-ETH debt sits near HF 1.05 on Aave. Any bot defending those positions telegraphs its level today. Keel defends without handing hunters a price target.
A treasury's positions are public by address. Keel lets it run a private defense and still prove to token holders, after the fact, that the committed policy ran unchanged.
Position-automation services run fully public triggers. Keel is the confidential trigger with per-action receipts: the service proves execution honesty without exposing customers.