3D view unavailable in this browser. The panel shows every layer.
Drag to turn · select a layer for details
Checked, goodAttention or aged
Failed a checkNot running or not checked
Each layer's state comes from a signed snapshot. While the CELA services run, a new one is published when they start, when their state or the hardware changes, and at least every 5 minutes, and a last one when they stop. It reaches this page within about a minute, without a site update. Each snapshot made while running says when the next is due; if that time passes with nothing new, the host layers read "last seen". The system does not yet run around the clock, so when it is stopped the banner says how old the last snapshot is.
Your browser checks the snapshot itself. It must match this site's signed manifest, or a signed live manifest made with the same site keys (ECDSA-P256 + ML-DSA-44), and every Bitcoin anchor proof is re-checked against block headers from public Bitcoin explorers. A layer that cannot be checked is shown as not checked, never as good.
Every hour while the system is live end to end, the newest signed history is anchored in Bitcoin through OpenTimestamps. Each anchor is a short statement of what it pins, plus a standard OpenTimestamps proof, and both are published: the anchor index lists every one by its SHA-256 at /live/assurance/<sha256>.anchor and .ots. Each statement names the SHA-256 of the one before it, so a verified newest anchor vouches for the whole chain. The check does not depend on this site's keys or servers. It shows when each pinned history existed, not that the host recorded it honestly.
With the CELA anchor verifier. The open-source cela-anchor-verifier (Apache-2.0, Python 3.8+, no other packages) downloads every statement and proof, checks each object against its hash, the chain of statements, each proof against Bitcoin block headers and how recent the anchors are, and reports each as verified, rejected or not yet checkable:
git clone https://github.com/Monart-Studio-Ventures/cela-anchor-verifier
cd cela-anchor-verifier
python3 cela-anchor-verify --site https://monartcity.xyz --bitcoinThe newest anchor usually waits 1 to 6 hours for Bitcoin, so "not yet checkable" is normal for it. Use your own Bitcoin node for the headers if you prefer; the repository's README shows how. Each run is counted when it fetches the index, like any visit; its result stays on your machine.
With the reference client. Download a statement and its proof and run ots verify with the OpenTimestamps client, or any other verifier you trust.