Reference implementation of the REM Protocol (DOI + Blockchain Permanence) – Internet-Draft draft-reilly-rem-protocol-00
This repository provides a minimal demonstration of the Reilly EternaMark (REM) Protocol, an Internet-Draft submitted to the IETF:
🔗 draft-reilly-rem-protocol-00
REM defines a dual-layer method for digital permanence:
- Blockchain timestamping → immutability
- DOI assignment → discoverability and persistence
Unlike most Internet-Drafts that use placeholders, REM includes live artifacts (real DOIs, blockchain TXIDs, and SHA-256 hashes) that can be verified today.
-
Upload to Zenodo
- Deposit a document or dataset.
- Zenodo mints a permanent DOI.
-
Generate a SHA-256 hash
shasum -a 256 mydocument.pdf
-
Timestamp with OpenTimestamps ots stamp mydocument.pdf ots info mydocument.ots Produces a blockchain transaction ID (TXID) on Bitcoin.
-
Record the Pair
Combine the DOI + TXID + SHA-256 hash as a dual-layer permanence record.
Example Proof Artifact { "sha256": "02439f01ba0b805ba3011aaeb2783ffb096c1c6ad847876e75d7d8b6c5c40d9b", "doi": "10.5281/zenodo.17096230", "txid": "Bitcoin block 914168 (attesting existence as of 2025-09-10 EST)" }
Why This Matters
Verifiable today: anyone can check the DOI and TXID independently.
Immutable + discoverable: permanence guaranteed by blockchain + scholarly infrastructure.
Reference implementation: small, reproducible steps that prove the REM Protocol works.
🔗 References
IETF Internet-Draft: REM Protocol https://www.ietf.org/archive/id/draft-reilly-rem-protocol-00.html
Zenodo https://zenodo.org/
OpenTimestamps https://opentimestamps.org/
Reilly EternaMark (REM)
Use the full name on first mention. The short form REM is acceptable thereafter.
REM — ledger-agnostic permanence: blockchain timestamping + DOI registration for verifiable, citable artifacts.
- IETF Internet-Draft: Reilly EternaMark (REM) Protocol — draft-reilly-rem-protocol-00. DOI snapshot:
https://zenodo.org/records/17185285(use this DOI when citing). - GitHub (canonical repo):
https://github.com/lawrencejohnreilly-creator/rem-protocol - Contact / maintainer: Lawrence John Reilly — lawrencejohnreilly@gmail.com
Reilly, L. J. (2025). REM (Reilly EternaMark) — DOI: 10.xxxx/rem.xxxxx — IETF Internet-Draft: draft-reilly-rem-protocol-00. Archived and timestamped (Zenodo + OpenTimestamps).
- Capitalization: use Reilly EternaMark on formal documents and REM for short references.
- Do not use only the token
remin contexts where it could be ambiguous (e.g., repo names or package names) — preferrem-protocolorreilly-eternamark. - Add the DOI and OTS proof references to any release notes or publication metadata.
- Logo: (placeholder)
logo.svg— add when available. - Colors / fonts: TBD — keep a clean, minimal aesthetic for docs.
- GitHub repo:
lawrencejohnreilly-creator/rem-protocol(current) — consider creating arem-protocolorganization for governance if project grows. - Domain (optional):
reillyeternamark.orgorrem-protocol.org(reserve if you want independent landing page). - Social/X handle: consider
@REMprotocolor@ReillyEMark(check availability before committing).
- Default to MIT for demo artifacts; include
LICENSEat repo root. - Add
CONTRIBUTING.mdwith short notes: how to open issues, PR conventions, contact for sketches.
Include a short verification recipe in docs:
- Download DOI archive (PDF).
- Verify SHA256 hash matches
sha256:...in draft appendix. - Verify OpenTimestamps proof (
ots verify REM_package.pdf). - Verify DOI metadata contains anchor fields (
ledger_root,anchor_proof) per REM schema.
(End of BRAND.md)
This README itself serves as a reference implementation: simple, transparent, and reproducible.