Inspect / The evidence behind a plan

Check the record yourself.

Reproduce a saved calculation from its downloaded bundle. Inspect each evidence layer separately, with a clear view of what can and cannot be established.

  1. Choose the exported bundle

    Load a CarbonShift JSON proof file. It is processed locally in this browser; selecting it does not upload it.

  2. Read the individual checks

    Inspect the method, calculation, revision history and disclosures. A missing source of evidence remains unavailable.

  3. Add chain context if you choose

    Look up operator RPC observations or supply your own trusted observation file. Chain trust is separate from local arithmetic.

Start with a proof file.

Use the JSON bundle exported from a saved plan or public receipt. The file contains the inputs needed to reproduce the record.

Your bundle is processed locally in this browser. Choosing a file does not upload it. Version 1 and household version 2 are supported.

Load a bundle to inspect its format, method, calculations, commitment timing and result history. A missing RPC does not become a failed arithmetic check.

Read every state in context.

The verifier does not combine different kinds of evidence into a single certification badge.

Matches

The available inputs satisfy this specific check. A matching digest means the checked content agrees with its commitment; it does not measure device use.

Does not match

The available evidence conflicts with this check. Inspect the reported detail rather than treating a different, passing check as a replacement.

Unavailable

Required evidence is missing, such as trusted chain observations. This state is different from an arithmetic mismatch.

Unsupported

The record uses a method or format the verifier cannot evaluate. It does not guess how to reproduce a different calculation.