Permission ran out
The approval was used up or lowered. The simulated call reverts with the token's own reason.
Product · Preflight
Find out before the wallet opens
A prompt is expensive: it costs attention, and a reverted transaction costs gas too. Mutiq runs your rules and a simulated call first, so a request that would fail stops at a readable reason.
Illustration
RequestRuleseth_call
A clear yes or noMutiq
Execution Policy
Say what may run, per namespace
A namespace has rules: which target, which function, how many per time window. The same rules are evaluated in the browser and, when you register an action, by the contract. An exact rule wins over a rule for the whole target, and strict mode refuses anything without an allow rule.
Target + functionallow, 5 per hour
Whole targetdeny
Not listedstrict: refused
Pausednothing new
Illustration: how a request meets the rules
Why it matters
A failed transaction is a paid answer
The moment passed
The contract would refuse it now, and you can see that without paying for the refusal.
Wrong signer
The connected account lacks the role. The call runs from that address, so the answer is the true one.
Too many, too fast
A per-window count stops a loop in a script before it spends anything.
What a simulation is
A good guess, honestly labelled
eth_call runs your transaction against the chain as it is right now, from the signer's address, and nothing is sent. The real transaction runs later and can still end differently if state changes in between. Preflight reduces surprises; it does not rule them out.
Preflight toolkit
Every check, in order
Parameter checks
Address shapes, hex data, a selector that is really a selector, a value that makes sense.
Network check
The read really came from the chain you are about to use.
Target code
Call data sent to an address with no contract does nothing. You get told.
Simulated call
eth_call from the signer, with revert reasons decoded where the error is known.
Gas estimate
eth_estimateGas, plus the fee at the current gas price.
Funds check
Balance against value plus fee, before the wallet says so.
Allow and deny rules
By target, by function, or both.
Window counts
A fixed window with a limit, shared by what the rule covers.
- 01
Simulations
Any target, gas capped at 3,000,000, no state overrides.
- 02
Local rules
In your browser, with no server involved.
- 03
On-chain rules
Enforced by the contract when an action is registered, not on your other transactions.
The relay only reads. It never forwards a signed transaction.
Ready to coordinate?
Click one button twice and watch one action land in the queue. Then read exactly what it holds and what it cannot.
Not a trading bot · Not a wallet · Not a chain · Your wallet signs every transaction