Read the status
| Status | Meaning and next step |
|---|---|
| Anchoring… | Processing. Check the existing submission or record. |
| Confirmed | For current Base records, the service observed a successful Base L2 transaction receipt with the required record evidence. Open the available proof actions. |
| Failed | Read Technical details and use the recovery action offered. |
| Evidence pending | Success evidence is incomplete or unavailable. This is not an integrity hold and is not a positive proof. |
| Quarantined | An authoritative integrity-review hold is active. The service withholds current positive proof, report and explorer actions. The hold alone does not prove the chain evidence is invalid. |
| Archived | Historical information, not a current positive verification result. |
For current Base records, the internal word finalized means successful Base L2 receipt observation. It does not mean Ethereum L1 settlement. The service does not monitor a confirmation-depth threshold. See
the technical reference.
Retained records from retired networks keep their original chain's status and finality semantics and can also display Confirmed. Choose All time to find older records, and check the chain in the record's details before interpreting its status or verifying its evidence. Direct verification requires access to that original network's history.
Recover without creating a duplicate
A timeout, browser error, lost connection or unknown outcome is not definite chain failure and does not prove that credits were refunded. Keep the original submission open if possible.
- Check for an update now checks pending acceptance. Try this same submission again retains the original submission identity when that action is offered.
- Retry live updates reconnects updates; it does not create another record.
- Check original submission or Find original submission resolves an uncertain original.
- Review details lets you address a reported request conflict. Retry file applies to a local hashing failure.
- Use Try a new submission only when the page offers it after a definite terminal failure. Records may offer Retry notarization (1 credit) only when the server marks it retryable.
Do not infer permission to retry from an empty Records search or an unavailable proof. If the status remains unclear, email support with the action, approximate time and displayed status. Omit passwords, private receipt links and checkout-session tokens.
When proof is unavailable
Evidence pending and Quarantined do not offer current explorer, proof or report actions. Wait for the existing record to resolve or contact support. Preserve earlier exports and check verification guidance; a service outage cannot establish that an independently retained fingerprint differs from the file.