The chain
Nebula records trustworthy state on two chains: Polygon (a public
EVM chain) and nebulad (Nebula's own private chain). Every anchored
event appears on both, so neither chain can rewrite history alone.
Why dual-anchor
A single chain is a single point of authority. By writing the same
hash to two independent ledgers, Nebula makes the proof robust to
the failure or capture of either. A counterparty verifying a proof
checks both chains; if either disagrees, the proof is rejected.
What "verified" means
When you see "verified" on a Nebula surface it means:
- The atom exists with the documented hash on both chains
- The chain timestamps are within tolerance
- The signing key chain checks out (org -> user)
If any of those fail, the surface reads "unverified" or "invalid".
How to read a proof
Open the anchor detail page (/anchors/[id]). You'll see:
- The dual hash (Polygon transaction hash + nebulad sequence)
- The signing key fingerprint
- The atom payload that was anchored
- Both chain timestamps
Download the full proof bundle to verify yourself with the CLI:
/docs/chain/verifier.