Execution model
How a sniper's transactions are signed, tipped and sent, and what each choice does and doesn't guarantee. Every line is from Rout's spec; none of it is measured yet.
Status
rout-next/src/domain/capabilities.ts:44-45 · rout-automation-ui@61469bfDurable nonce or recent blockhash
execution.nonce: true | execution.nonce: false | |
|---|---|---|
| Signing | Against a durable nonce, one copy per provider | Once, against a recent blockhash |
| Duplicates | Copies share one nonce, so at most one can land | One signature |
| On chain | A nonce account linked to the wallet, which can fingerprint it | Nothing extra |
| Caveat | A sender's docs say nonce transactions can land worse on some paths; E0 measures this as its primary comparison | — |
Required, no default: null and a missing key are both refused (NoNonce). Treat nonce as idempotency for exits that must never run twice, not as a speed setting. Source: sniper-definition.d.ts:945-951, errors.md NoNonce.
Tips and host floors
execution.tip_lamports is exact: it is what is costed, built and recorded, paid to the host's tip provider, 0 for none. A sell rule may set its own tip, for an exit that has to land ahead of everyone else leaving.
Each host has a floor. A tip below it is refused (TipBelowFloor, which names the floor to offer). A host with no untipped route refuses 0 (NoUntippedRoute).
The only independent study we found shows tips barely move time to inclusion. Treat tips as cost control and state them exactly. Source: d.ts:949-951, :1763; an independent validator study of tips vs inclusion.
Executed or pre-execution detection
seen | What it means | Trade-off |
|---|---|---|
executed | The creating transaction ran in a replayed block. The coin exists. | A buy decided now lands a block after the launch at best. |
pre_execution | Read from shreds while the block was still being assembled. | Arrives a block earlier, which makes a same-block buy possible, but it may fail or never land. Needs runtime.venue_shreds on the host. |
There's no default: you choose which fact to act on. No false-event rate for pre-execution detection is published yet (engine ask E6). Source: d.ts:1773-1787.
What is and isn't guaranteed
| Property | Status |
|---|---|
| At most one landed copy per nonce intent | Documented only Measured by E0 (double-landed must be 0) |
| A buy that didn't land counts against no limit | Documented only |
| A firing on a slot that forks out is taken back | Documented only |
| Landing in any particular slot | Never guaranteed: the leader orders the block |