Bitcoin-anchored data persistence, built in the open.
Engram is an open protocol that composes data publication, settlement anchoring, and erasure-coded storage in one stack: files become Reed–Solomon shards held by commodity operators, providers prove custody with recurring zero-knowledge proofs, and checkpoint commitments are anchored to Bitcoin as the external root of settlement truth.
The architecture is documented in a manuscript under review at ACM Transactions on Internet Technology, developed at Hanoi University of Science and Technology with A-Star Group and the University of Massachusetts Boston. Evidence today spans three levels: a working publication-path prototype (7-validator WAN across four continents, payloads up to 32 MiB), a 500-node simulation of coded persistence and adversarial retrieval (reconstruction succeeded in all six adversarial scenarios, including eclipse), and a measured zk proof-of-spacetime micro-benchmark (724-byte proofs, ~21 ms verification).
| Repository | What it is |
|---|---|
| engram-paper-artifact | Citable archival entry for the paper · DOI 10.5281/zenodo.19879674 |
| engram-anchor-bridge | Checkpoint anchoring bridge: Merkle-batched block commitments submitted to the settlement backend |
| engram-simulation-benchmark | Evaluation suite reproducing the paper's measured results, module by module |
Application-layer and infrastructure repositories remain private; everything on the protocol and research track is developed here in public.
- Direct Bitcoin anchoring module — OP_RETURN / Taproot checkpoint commitments, removing the current third-party settlement intermediary.
- Standalone zk proof-of-spacetime library — productionizing the benchmarked construction.
- Verifiable retrieval — a reference implementation of the protocol's V-DHT design, with an adversarial test suite reproducing the paper's eclipse and withholding scenarios.
All of it ships under Apache-2.0, with public commits and public documentation.
The maintainers run a research group at HUST and mentor 2–3 students each semester into open-source development on this codebase. Documentation and tutorials for every module are part of the roadmap, not an afterthought.
Open an issue on the relevant repository, or reach the team via the paper's corresponding author.
