<?xml version='1.0' encoding='utf-8'?>
<rfc version="3" ipr="trust200902" category="info" consensus="false" docName="draft-reilly-rem-protocol-00">
  <front>
    <title abbrev="REM Protocol">Reilly EternaMark (REM) Protocol - Dual-Layer Digital Permanence Using DOI Archiving and Blockchain Timestamping</title>
    <seriesInfo name="Internet-Draft" value="draft-reilly-rem-protocol-00" />
    <author initials="L.J." surname="Reilly" fullname="Lawrence John Reilly Jr.">
      <organization>Independent</organization>
      <address>
        <email>lawrencejohnreilly@gmail.com</email>
      </address>
    </author>
    <date year="2025" month="September" />
    <abstract>
      <t>The Reilly EternaMark (REM) Protocol defines a dual-layer method for digital permanence through the
      integration of Digital Object Identifiers (DOIs) and blockchain timestamping. The protocol ensures digital
      artifacts are permanently identifiable, immutable, and verifiable for both present and future use.</t>
    </abstract>
</front>
    <middle>

    <section anchor="introduction">
      <name>Introduction</name>
      <t>Existing digital preservation methods are centralized and vulnerable to alteration, corruption, or loss.
      The REM Protocol addresses these issues by combining DOI persistence with blockchain immutability.</t>
      <t>DOI ensures discoverability, persistence, and interoperability. Blockchain timestamping ensures
      immutability and tamper-proof verification. This creates a dual-layer permanence system suitable for
      academia, compliance, intellectual property, and AI data governance.</t>
    </section>

    <section anchor="terminology">
      <name>Terminology</name>
      <t>DOI: Digital Object Identifier, a globally unique and resolvable identifier.</t>
      <t>Timestamp: A blockchain-anchored proof of existence and creation time.</t>
      <t>Artifact: Any digital object (paper, dataset, contract, etc.) preserved via REM Protocol.</t>
    </section>

    <section anchor="overview">
      <name>Protocol Overview</name>
      <t>The REM Protocol consists of four steps:</t>
      <t>1. Hashing — Compute SHA-256 hash of the digital artifact. Example: 02439f01ba0b805ba3011aaeb2783ffb096c1c6ad847876e75...</t>
      <t>2. Blockchain Timestamping — Submit the hash to a blockchain timestamping service. Example: Bitcoin block 914168 attests existence as of 2025-09-10 EST.</t>
      <t>3. DOI Assignment — Register the artifact with a DOI system (e.g., Zenodo). Example: https://zenodo.org/records/17096230</t>
      <t>4. Archival Integration — Publish DOI, blockchain TXID, and hash together as the permanent record.</t>
    </section>

    <section anchor="spec">
      <name>Specification</name>
      <t>Inputs: Digital artifact.</t>
      <t>Process: SHA-256 hash -&gt; Blockchain timestamp -&gt; DOI registration -&gt; Publication.</t>
      <t>Outputs: A permanent, verifiable record consisting of: DOI (discoverability), Blockchain TXID (immutability), Hash (integrity proof).</t>
    </section>

    <section anchor="security">
      <name>Security Considerations</name>
      <t>Integrity: Provided by SHA-256 hashing.</t>
      <t>Immutability: Guaranteed by blockchain consensus.</t>
      <t>Persistence: Ensured by DOI federation and global resolution.</t>
    </section>

    <section anchor="iana">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>

    <section anchor="applications">
      <name>Applications</name>
      <t>Academic publishing and research archiving.</t>
      <t>Compliance (finance, healthcare, logistics).</t>
      <t>Intellectual property (true prior art, permanent alternative to patents).</t>
      <t>AI and ML datasets (trustworthy sources).</t>
    </section>
  </middle>

  <back>
    <references>
      <name>Informative References</name>
      <reference anchor="ISO-26324" target="https://www.doi.org/doi_handbook/">
        <front>
          <title>DOI Handbook (ISO 26324)</title>
          <author>
            <organization>International DOI Foundation</organization>
          </author>
          <date year="2012" />
        </front>
      </reference>
      <reference anchor="RFC9162" target="https://www.rfc-editor.org/rfc/rfc9162.html">
        <front>
          <title>OpenTimestamps Proofs</title>
          <author fullname="Peter Todd" />
          <date year="2021" />
          </front>
      <seriesInfo name="RFC" value="9162" />
        </reference>
      <reference anchor="ZenodoStandards" target="https://about.zenodo.org/">
        <front>
          <title>Zenodo Archiving Standards</title>
          <author>
            <organization>CERN/Zenodo</organization>
          </author>
          <date year="2025" />
        </front>
      </reference>
    </references>

    <section anchor="address" numbered="false">
      <name>Author's Address</name>
      <t>Lawrence John Reilly Jr.</t>
      <t>Email: lawrencejohnreilly@gmail.com</t>
    </section>
  </back>
</rfc>