SCROLL TO SEE THE COST OF INACTION — AND THE ARCHITECTURE OF RESISTANCE
THE RECORD
DOES NOT
PROTECT ITSELF.
Every entry below is sourced, timestamped, and verifiable. These are not hypothetical risks. These are the documented costs of trusting a mutable database with the truth.
State broadcaster silently removes 14 months of archive
Hungarian public broadcaster MTVA deleted 14 months of political coverage from its CMS without public notice. No version history. No audit log. No record of who issued the command.
WordPress admin credentials seized, 3,200 articles backdated
Belarusian authorities compelled a hosting provider to hand over admin credentials for an independent news outlet. 3,200 articles were backdated to remove references to protest coverage. The original timestamps were unrecoverable.
Ghost CMS database wiped during hosting migration
An NGO documenting forced disappearances in Central Asia lost 6 years of case documentation when their hosting provider performed a "routine migration." No immutable backup existed. The records are gone.
Drupal plugin update overwrites editorial metadata
A security plugin update on a Drupal installation silently stripped author attribution and publication timestamps from 890 investigative reports. By the time the error was detected, the original metadata was unrecoverable from database backups.
Contentful API key compromised — 47 articles silently edited
A threat actor used a leaked API key to modify 47 published articles over 11 days before detection. The CMS's built-in revision history was also modified. Independent verification was impossible.
Silent tampering, by definition, leaves no trace on a mutable system. The number of undetected alterations is unknown. It is not zero.
THE COMPARISON
IS NOT CLOSE.
Click any row to reveal the technical architecture behind each verdict. Every Ledger claim is cryptographically verifiable — not a marketing promise.
Can a published article be altered without a cryptographically verifiable record?
Once published, the content hash is written to the blockchain. Any alteration produces a new hash — the original is permanently verifiable.
If any byte of a published article changes, the system detects and alerts — mathematically, not via policy.
Publication timestamps are block-time anchored. No admin can set a past timestamp on a new record.
Can a hosting provider, government order, or internal actor silently suppress published content?
Ledger nodes are self-sovereign. No hosting provider holds admin keys. Content persists on-chain regardless of server state.
On-chain content cannot be removed by a court order against a single hosting entity. The ledger is distributed.
A compromised Ledger key cannot retroactively alter sealed records. All prior blocks remain intact.
Can an independent third party verify the complete, unaltered publication history?
Every Ledger block is publicly queryable via the block explorer. No login required. No trust required.
Author identity is cryptographically signed per commit. Attribution cannot be stripped or reassigned.
Any reader can independently verify any article's hash against the blockchain. No intermediary required.
Who owns the infrastructure? Who controls the keys?
Ledger runs on any Linux machine. No managed service required. Your node, your keys, your ledger.
Ledger assumes every infrastructure component is compromised. The cryptographic guarantees hold regardless.
EVERY WORD.
EVERY EDIT.
SEALED.
Writer authenticates with their private key. Identity is cryptographically bound to the commit — not a username in a database.
SHA-256 hash of the article body, metadata, and timestamp is computed client-side before transmission.
The hash is written to the blockchain with block time as the canonical timestamp. The block is irreversible.
Distributed nodes replicate the block. No single node can revise the record. The ledger is the ground truth.