Start
How it works
Eight stages between a message appearing in Discord and a position being managed on chain. Each one can refuse, and refusing is always cheaper than guessing.
A call is posted
Only the nominated channel is monitored — chosen explicitly by the owner, not inferred.
The address is found
Two addresses and no indication which is the token: refused rather than guessed.
The token is verified
A string that merely looks like an address never becomes a call.
The call is journalled
The same message can never be recorded twice, however many times it is delivered.
Subscribers are matched
A rule that fails stops that subscriber only. One trader's limits never affect another's.
Capital is committed
Ten calls in one second cannot each be told the full balance is free.
The trade is executed
A failed submission releases its capital. A confirmed one is never sent twice.
The position is managed
Pausing a bot stops new entries and keeps managing exits on what is already open.
Why it is built to refuse
An automated trading system fails in two directions. It can miss a trade it should have taken, or it can take one it should not have. The first costs an opportunity. The second costs money, and it costs it silently — a system that guesses when the evidence is ambiguous will keep guessing, and the losses accumulate faster than anyone notices.
Every stage above therefore has a refusal condition, and every refusal is recorded rather than swallowed. A safety filter that is switched on but cannot be evaluated blocks the trade instead of waving it through. A quote that has gone stale is discarded instead of submitted at whatever the market has become. Ambiguity stops the call.