6/6
public transactions succeeded
The deploy and a five-step test of the brake, 30 Sep 2026.
DRIFT is a trading bot with a public referee. If a recorded loss reaches 20%, a contract on BNB Chain halts the bot by itself. Restarting it takes the owner's key, in public.
Reading the contract on BNB Chain…
The live read needs JavaScript. The contract is public on BscScan.
Contract 0x8b09…a83D ↗01 / 03
Each time the bot decides, its loss at that moment goes on the public record.
02 / 03
No owner to ask, no settings page, no delay. The rule is in the contract.
03 / 03
The halt was tested in public on BNB Chain on 30 Sep 2026. Restarting takes the owner's key, also in public.
Bot's loss
0%
Halted by the contract
DRIFT's engine reads the market and proposes: buy, sell, or stay out.
A public contract on BNB Chain checks the market mood and the 20% loss limit. Anyone can ask it the same question.
On BNB Chain
If the answer is no, or no answer comes back, the bot stays out. Trading runs on an exchange testnet: no real money moves.
The decision, the loss at that moment and the contract's yes or no are written to BNB Chain, where anyone can open them.
On BNB Chain
Ask why the bot stayed out and get a plain answer. The rules decide; the AI only explains.
Step 01 / 05

6/6
public transactions succeeded
The deploy and a five-step test of the brake, 30 Sep 2026.
30/30
contract tests pass
Including random sequences from the bot and from strangers.
100%
of the contract covered
Every line, branch and function. Source verified on Sourcify.
The contract, in public
0x8b09ebB85Be8Ed55Bb5132d29eABc567c42aa83D
The bot wants to
?
The contract's answer appears here, with the block it was read at.
No. DRIFT runs on BNB Smart Chain Testnet and an exchange testnet, so no real money moves. We make no profit claims; backtests are research.
It stores two public rules: the current market mood and a 20% loss limit. Before each trade the bot writes its decision and its current loss to the contract, and acts on the yes or no in that same public receipt. An exit at the 20% stop never waits: it happens first and is recorded right after. If a recorded loss reaches 20%, the contract halts the bot and only exits are allowed.
The bot takes no new risk. Without a confirmed answer from the contract, only exits pass (fail-closed), and its own built-in 20% stop keeps running underneath.
Three trust points remain, and we name them: the bot has to ask the contract (DRIFT's own runner does whenever it is connected to it; a changed bot could skip it), it reports its own loss, and its key can lift a halt. Every answer, loss and restart that does happen is public and permanent on BNB Chain. Next: losses confirmed by the exchange, and lifting a halt only through a multisig or a time delay.
No. The strategies and the risk check are fixed rules. The AI analyst only explains what the system sees, in plain words.
Open the live guard page: it reads the contract from your browser, with no login or wallet. From there you can open every receipt on BscScan, read the verified source on Sourcify, or ask the contract a what-if.