What Verderer cannot do
Every claim on this site has a matching entry here. If a limitation is missing from this page it is because we have not found it yet, not because we decided it read badly.
- 01
No ordering priority. None, at any price.
The sequencer orders strictly by arrival. There is no builder, no auction, and eth_maxPriorityFeePerGas returns 0x0 — measured, not assumed. Timeboost is not enabled. Nothing in this product moves a transaction ahead of another. Someone who submits one millisecond earlier is sequenced first regardless of what they paid or which API they used.
- 02
No protection from a faster participant.
Bundles do not hide you; the absence of a public mempool does that already, for everyone equally. Lower latency wins. We can reduce your latency — and we sell the same service to your competitor. It is a race, not an entitlement.
- 03
Atomicity is per transaction, and nothing else.
Anything spanning two or more transactions cannot be made atomic on this chain, by us or by anyone. That is why the atomic path collapses your actions into one transaction against an executor contract. burst mode is explicitly and unavoidably non-atomic, and its response payload says so.
- 04
Burst contiguity is measured, never promised.
Sequential nonces from one sender written back-to-back usually land together under first-come-first-served. Usually. A foreign transaction can land between them and a block boundary can split them. We publish the observed rate on the relay stats endpoint and you should price the failure case in.
- 05
Guards prevent bad execution. They do not produce good execution.
A guarded bundle that would fill badly does not fill. You get nothing, and somebody else may get the trade. Conditional submission makes that outcome free instead of costly — which is the best available result, not a win.
- 06
Conditions are checked at admission, not at execution.
A residual window remains between the sequencer accepting your transaction and executing it. On-chain guards inside the executor close that window authoritatively, at the cost of gas when they fire. Use both layers, and understand that the cheap one is the weaker one.
- 07
Timestamp guards cannot separate adjacent blocks.
Blocks arrive about every 100 ms while timestamps advance in whole seconds. Any execution-window logic must use block.number. A timestamp bound that looks tight is not.
- 08
Simulation is a forecast.
It runs against the freshest state we hold, which is fresher than the public RPC will serve — and state still changes between the simulation and the execution. There is no indemnity attached to a simulation result.
- 09
The relay is a trusted intermediary. So is the sequencer.
Submitting through us reveals your intent before it is on-chain. What we offer against that: published latency telemetry, signed ingress receipts, and the documented option to bypass us entirely and use the public RPC. What we cannot offer: a cryptographic guarantee against relay or sequencer misbehaviour. That needs an encrypted mempool, and none is deployed.
- 10
Censorship resistance exists, but it is not an execution path.
Force inclusion through the delayed inbox takes a flat 4 days (delaySeconds = 345,600). Against a 100 ms block time that is worthless for trading. We monitor it as a censorship backstop and we will never present it as a fallback route.
- 11
Gas is charged when an on-chain guard fires.
If a bundle passes the sequencer’s admission check but its executor guards fail, it reverts and consumes gas, with no auction to compensate you. That is exactly why simulation is on by default and why conditions are auto-derived from what the simulation read.
- 12
Multi-party bundles need every party to have signed already.
The settlement contract can atomically fill several people’s orders in one transaction, but only orders they signed. There is no mechanism, here or anywhere, to include an unwilling or unaware counterparty.
- 13
Verderer is not a validator and cannot become one by wanting to.
validatorWhitelistDisabled() is false on the rollup, and the challenge manager gates on it. 2 addresses may propose or challenge state roots; 1 is active. We cannot stake, cannot post a rival assertion and cannot open a challenge. The Bond Vault holds a reserve against the day that changes, and it is labelled as a reserve because that is what it is.
The reason this page exists in this form: a latency product on a first-come-first-served chain is unusually easy to lie about, because the customer cannot tell a real millisecond from a claimed one. Publishing the boundary is the only way to make the numbers inside it worth anything.