Live today

What we verify

Four passes over the exact transaction. Any one of them can refuse.

1. The transaction itself

It decodes, resolves its address lookup tables and simulates on independently operated nodes at the same slot. Nodes that disagree, a blockhash that cannot be confirmed, or a fee payer that cannot pay: refused.

2. The accounts and the token

Every account belongs to the program it claims to, and the pool’s vaults are what they should be. Token-2022 extensions that can freeze, pause, hook or block a transfer are read, not assumed.

3. What the swap really does

The pool, the direction, the output token and the minimum out in the bytes must match what the agent declared. A substituted token or a lower minimum is refused.

4. What should never be there

Approvals, authority changes, mints, burns, closes that send rent elsewhere, program upgrades. None of them belong in a swap, and each is refused on sight.

How sure is each read?

• single_source: one read that passed its checks, labelled as exactly that.
• consensus: independent nodes agreed at the same slot. Disagreement returns nothing.
• anchored: tied to an on-chain or oracle reference that does not depend on Metera.

What the verdict does not cover

• MEV and sandwich risk between the check and landing. That is what execution through Jito, Astrolane and Nozomi is for.
• Whether the transaction lands at all.
• Market risk: a clean trade can still be a bad one.