Diff two on-chain versions

Load upgrade history for a program, select Version A and Version B, then reconstruct and compare bytecode. Artifacts are not marked verified unless independently proven.

Tip

Prefer programs with distinct buffers per upgrade and complete Write history on your RPC. Large binaries can take several minutes. Start with Token-2022 (~1.35 MB); use Kamino for stress; use the reused-buffer Token-2022 pair for adversarial reconstruction.

Curated mainnet pairs

Program

Program ID *

Label (optional)

Version A — before

Upgrade transaction signature *

Version B — after

Upgrade transaction signature *

Reconstruction requires complete buffer Write history and a bounded deployment cycle. Results include full SHA-256 provenance — not verified-build attestation.

No report yet

Select a curated pair or enter upgrade signatures, then run diff to open a live reconstruction report.

Reports are produced by live reconstruction — never from fabricated findings.