Where proof anchoring is enabled, an eligible item status change can create up to two proof records: one for Polygon and one for Nebulad. The two paths run separately, and Nebula reports every available result on its own.
Other supported proof events use the Polygon path without creating a Nebulad record. If Polygon submission is unavailable, Nebula can keep a local proof sample. A local sample is not chain confirmation.
How the records differ
A confirmed Polygon record contains a SHA-256 hash in its transaction data. A Nebulad item record uses different event data and a separate hash, so the two hashes are not expected to match.
A Nebulad item event can include item and status details and stored hashes for evidence files still attached to the item. It does not include the evidence files.
Nebula stores the exact event data used to calculate each new proof hash. Older records may not include that saved data.
What the states mean
A local proof sample has no chain transaction. A pending record is awaiting chain confirmation. Nebula marks a record confirmed after a successful chain response.
For a record with saved event data, the public verifier recalculates its hash before checking the selected network. Older records without that data receive a network-only check.
When Polygon and Nebulad records are both available for an event, the verifier shows both results separately. The pair is fully verified only when both results verify. One result does not change the other.
Verification checks whether the expected hash matches the chain commitment. It does not establish the truth, fairness or authority of the business statement.
Reading a proof
An authorised project member can open a proof record to see its hash, network, recorded time, status and available transaction details. Members with export access can also download a proof bundle containing saved event data when available.
Anyone with an anchor ID can use the public verifier without a Nebula account. It shows the selected network result and, when present, the other network's result. It does not expose saved event data or engagement details.