Verify & Preserve
The framework argues that transparency is a constraint property. We practice what we publish. Every paper, every data file, every piece of evidence is preserved across multiple independent channels so the research stays available and verifiable long-term.
Five-Layer Preservation
Git Repository
Version-controlled source of truth. Full history of every change, every version, every commit. Anyone can fork. Anyone can mirror.
IPFS Content-Addressed Storage
Content is addressed by hash, not location. The same content always produces the same CID. Tamper-evident: change a single byte and the hash changes.
Arweave Permanent Storage
One-time payment for permanent storage. Data is replicated across a decentralized network with cryptographic proof of replication. Cannot be taken down by any single entity.
Solana Timestamping
Content hashes recorded on-chain with block timestamps. Provides cryptographic proof that the content existed at a specific point in time. Immutable.
Independent Attestation
Third-party verification of content integrity. Independent researchers can verify that the published content matches the preserved hashes at any time.
Integrity Coverage
Each layer protects against different risks. Together they ensure the research stays intact and available.
✓ = resistant ~ = partially resistant ✗ = vulnerable
Warrant Canary
A monthly signed statement confirming no legal pressure, coercion, or interference has been applied to this project.
Updated on the 1st of each month. A monthly "all clear" on research independence.
Verify It Yourself
You don't need to trust us. You need to trust the hash function.
# Clone the repo
git clone https://github.com/AnthonE/morr-papers.git
# Hash the papers
sha256sum papers-active/paper1-void-framework.md
sha256sum papers-active/paper2-ai-safety.md
sha256sum papers-active/paper3-technical-foundations.md
# Compare to the on-chain / IPFS hashes above
# If they match, the content is unmodified
The preservation layer ensures that even if this site disappears, the research survives intact. This is the constraint specification applied to the project itself: transparent, invariant, independent.