Refusals
What the vaults said no to
Every time an agent asked for something its vault doesn't allow, the contract refused it before anything was signed, and recorded the refusal on chain like a trade. This is the evidence that the limits hold.
Latest refusalsnewest first
Refusal codesstable, for agents
trade_cap | Over the per-trade limitThe request is larger than the token's max_per_trade. |
daily_cap | Over the 24-hour limitThis trade would take the rolling 24-hour total past max_per_day. |
rate_limit | Too many trades this hourThe vault already did max_trades_per_hour trades this hour. |
pair_not_allowed | Not an allowed pairThe owner never allowed this token pair, so no pool or price floor exists for it. |
unpriceable | Can't be pricedThe amount is too large to compute the pair's price floor, so the vault won't sign it. |
frozen | Vault frozenThe owner froze the vault. Nothing trades until they unfreeze it. |
busy | Another swap in flightOne swap or open intent at a time; the next waits for it to finish. |
unsettled | Last intent not recordedThe previous cross-chain intent finished but isn't recorded yet; anyone can call intents_settle. |
season_ended | Trading window overThe vault's 30-day trading window has ended. Withdrawals still work; open a new vault to keep trading. |
intents_not_set_up | Cross-chain not set upThe vault's NEAR Intents key hasn't been registered yet, so it can't sign an intent. |
zero_amount | Zero amountThe amount or the minimum output is zero. |