Coherence Energy Labs

Check our homework

Every company publishes numbers about itself. Almost none of them can be checked, which is why a traffic figure in a pitch deck means so little. Ours are committed to an append-only signed log. This page re-derives that log from scratch, in your browser, using none of our code. Then it hands you the tools to try to make it lie.

1. Verify the live log

Fetches the published log, rebuilds its Merkle root here, and checks the signature against a key it looks up in public DNS rather than reading from our files.

2. Now try to make it lie

These are not mock-ups. Each button really tampers with the data in memory and re-runs the identical verifier. Nothing is hard-coded to fail; the checks simply stop passing.

What this proves, and what it does not

It proves the published history is intact and authored by the holder of the key in DNS: that these are the numbers we committed to, and that no past epoch has been quietly revised. It does not prove the raw counts were real. Somebody has to observe the traffic, and that observer is our edge collector, which remains the trust root. Restatement is the fraud this closes. Fabrication at the point of collection stays open, and we would rather name that than let you assume it away.

The rule that fixes this log's tree shape is written in Coherence Language and compiled to WebAssembly by our own compiler, which ships it only after certifying that five backends agree on its output. That module is what computes the root above; the JavaScript on this page is kept as an independent second implementation and the two are compared on twenty thousand inputs before either is trusted. SHA-256 and Ed25519 come from your browser's WebCrypto on purpose: in a verifier you want the primitives to be the platform's audited code, not ours.

The same verification runs from a command line with no browser involved. Download log.json and head.json from coherenceenergylabs.com/transparency/ and run our Python verifier, which also imports none of the producer's code. Four independent implementations of RFC-6962 now agree on the root: the producer's, the Python verifier's, this page's JavaScript, and the .cl core compiled to WASM. One implementation agreeing with itself would prove nothing.