FREE · SYNTHETIC FIXTURE · WORKS OFFLINE

Follow a Merkle proof

Trace one sample record from its leaf hash through sibling hashes to a root. Then change the evidence and see why the result changes.

Generic Merkle proof workflow: encode a synthetic record, hash a leaf, combine its ordered sibling hashes, and compare the calculated root with a selected fixture root. A separate panel shows that production Bubblegum data needs versioned SDK and current DAS evidence.
The worked example demonstrates tree inclusion only. It cannot replace issuer, exam, wallet, or authority checks.

INTERACTIVE EXERCISE · UNGRADED

What does this proof actually show?

Choose a scenario, inspect its synthetic evidence, and run the hash path. You can edit the record, but the proof and expected root will stay fixed.

Index bits choose left or right at each level.
Changing one character creates a different leaf hash. This text is fictional and is not saved.

Sibling proof supplied by the fixture

    Root selected for comparison

    Loading synthetic tree…

    Root comes from the selected local fixture.

    Result

    Preparing the synthetic tree…

      What this result does not establish

      A Merkle inclusion calculation is one part of real cNFT evidence. It does not authenticate the service that returned data, show that the tree root is current on a selected cluster, validate Bubblegum’s version-specific leaf bytes, prove an issuer’s identity, establish exam eligibility, or check collection authorities.

      BRIDGE TO THE REAL PROTOCOL

      Use the Bubblegum V2 SDK for real assets

      Metaplex’s V2 JavaScript SDK exports hashLeafV2 for the versioned leaf and getAssetWithProof to fetch and shape DAS asset and proof data for supported write instructions. Keep the asset response, proof, root, cluster, and source context together; fetch fresh proof data before a write.

      Documentation checked 2026-10-03. SDK names and behavior may change; check the current official reference and pinned package before building.