A public, write-once ledger of sealed events.

What it is. chain.epochcoreqcs.com is a read-only HTTP endpoint that lets anyone — opposing counsel, a regulator, an IT auditor, or a curious member of the public — verify a sealed event without contacting EpochCore. Each sealed event is a JSON record carrying a 64-character hash, a UTC timestamp, dual cryptographic signatures (one classical, one post-quantum), and a link back to the prior sealed event in the chain.

Why it's public. The whole point of cryptographic chain of custody is that the verification path does not depend on the issuer staying online or staying trustworthy. A receipt that only EpochCore can verify is not a receipt — it's a promise. By publishing the chain, we make every seal independently checkable with standard tools (curl, Python stdlib, and the cryptography / pqcrypto packages). No EpochCore SDK is required at any step.

Why no login. Anyone holding a watermarked document has the hash they need to verify it. Adding a login would gate verification behind an EpochCore account, which would defeat the chain's purpose and introduce a single point of failure. The chain is a public utility on the read side; the write side (issuing new seals) is the only path that requires authentication.