See What You Sign.
Before The Nonce Fires.

Four Stages. One Report.

Every transaction passes through a deterministic pipeline. No heuristics, no ML, no guessing. The engine fetches, simulates, decodes, and classifies in a single pass.

$285M. Twelve Minutes.
Two Signatures.

On April 1, 2026 a North-Korea-linked group drained 285 million USD from Drift Protocol's Squads multisig. They did not exploit a bug. They did not steal a key. They spent six months posing as a quant firm, then got two council members to pre-sign a routine-looking transaction whose payload was a config_transaction_execute. The pre-signed tx was wrapped in a durable nonce, so it did not expire. The attacker sat on it for a week, then fired. Twelve minutes later the treasury was on Ethereum.

The Report Drift Never Got.

Below is the verbatim terminal output of the engine consuming a synthesized versioned-transaction whose shape matches the April 2026 Drift exploit. Reproduce it with cargo run --example drift_attack.

sle simulate --tx $ATTACK_B64 --offline
================================================================
 SOLANA TRANSACTION LEGIBILITY REPORT
================================================================
 Signature:    4dLPchZ8d2eCX2eobPtT9eN4DHwxmWZZomvPiqQkdwg...
 Fee payer:    4kfEfEk7HrCLpdqo3vtrMYYF9ehzCAm7i4wZeK5f6syi
 Simulation:   success
 Overall risk: CRITICAL
 ! DURABLE NONCE: yes - this transaction has no expiry
----------------------------------------------------------------
 Human-readable summary:

   [System Program] AdvanceNonceAccount
      ! Durable nonce advance — tx was prepared earlier and kept valid via nonce

   [Squads v4] config_transaction_execute
      ! Governance change being applied — may add/remove signers, lower threshold, or drop timelock
      ! This is the class of instruction used in the April 2026 Drift exploit

   [X] CRITICAL — this transaction matches the APRIL 2026 DRIFT EXPLOIT PATTERN: durable nonce + multisig admin execute. the attacker that drained $285M from Drift used exactly this shape — pre-signed governance actions that stay valid indefinitely. DO NOT SIGN without verifying the inner instructions AND the nonce account lifecycle.
----------------------------------------------------------------
 Instructions (2):
  #0 System Program :: AdvanceNonceAccount      [MEDIUM]
  #1 Squads v4      :: config_transaction_execute [CRITICAL]
================================================================

Eight Programs.
Eighty-Plus Instructions.

Every decoder lands in the same registry and emits the same LegibilityReport shape. Anchor programs go through a generic discriminator matcher; native programs (System, SPL Token, Token-2022) have custom decoders.

Four Levels. No Ambiguity.

Every instruction receives a risk level. The engine merges them upward — if any single instruction is CRITICAL, the entire transaction is CRITICAL. No averaging, no weighting, no probability scores.

Not a Wallet. Not a Bridge.
A Lens.

A non-custodial pre-sign defense layer built for one specific job: showing you the ground truth of a transaction before your signature commits to it. Your keys never touch our code. Zero runtime panics, zero telemetry, zero network dependency in offline mode.

Questions. Answered.