From c4e91472a24aa90f1c923412163e9c917280ad9a Mon Sep 17 00:00:00 2001 From: David Hay <3615726+david-hay@users.noreply.github.com> Date: Mon, 21 Sep 2026 12:38:00 -0400 Subject: [PATCH 1/3] Move ERC-8326 to Last Call --- ERCS/erc-8326.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/ERCS/erc-8326.md b/ERCS/erc-8326.md index ec15822e897..39b480e7259 100644 --- a/ERCS/erc-8326.md +++ b/ERCS/erc-8326.md @@ -4,7 +4,8 @@ title: Canonical Document Bundle Anchor description: A deterministic document-entry bundle hash and subject-scoped anchoring interface with supersession history author: Chris Turner , David Hay (@david-hay), Reagan Simpson (@krumg111), Collins Musyimi (@Musyimi97) discussions-to: https://ethereum-magicians.org/t/erc-8326-canonical-document-bundle-anchor/28935 -status: Review +status: Last Call +last-call-deadline: 2026-10-05 type: Standards Track category: ERC created: 2026-07-05 @@ -530,9 +531,9 @@ those files. The Document Management proposal numbered 1643 defines document references for security tokens. It stores individual named documents rather than a deterministic, schema-versioned bundle manifest. -[ERC-5289](./eip-5289.md) defines document signing and verification. This ERC -defines deterministic bundle commitments and supersession rather than a signing -workflow. +The *Ethereum Notary Interface* proposal defines document signing and +verification. This ERC defines deterministic bundle commitments and +supersession rather than a signing workflow. [ERC-5732](./eip-5732.md) defines a generic commit-reveal mechanism. It can be used as a privacy layer around publication but does not define document entries From bcb76e5d4527b51e6bddec75fcc22dd0b7c34139 Mon Sep 17 00:00:00 2001 From: David Hay <3615726+david-hay@users.noreply.github.com> Date: Wed, 30 Sep 2026 12:26:25 -0400 Subject: [PATCH 2/3] docs(erc-8326): address final review feedback --- ERCS/erc-8326.md | 34 ++++++++-------------------------- 1 file changed, 8 insertions(+), 26 deletions(-) diff --git a/ERCS/erc-8326.md b/ERCS/erc-8326.md index 39b480e7259..d5877b210b4 100644 --- a/ERCS/erc-8326.md +++ b/ERCS/erc-8326.md @@ -14,8 +14,9 @@ requires: 165 ## Abstract -This ERC defines a deterministic manifest and anchoring interface for -commitments to bundles of off-chain documents. Each document is represented by +This Ethereum Request for Comments (ERC) defines a deterministic manifest and +anchoring interface for commitments to bundles of off-chain documents. Each +document is represented by a fixed-width entry containing a content hash, document role, media-type hash, filename hash, and normalization-profile identifier. Entries are placed in a total order and hashed under a schema-version prefix to produce one `bytes32` @@ -246,6 +247,8 @@ total order. ### Anchor Interface ```solidity +pragma solidity ^0.8.20; + interface IDocumentBundleAnchor { struct AnchorRecord { bytes32 bundleHash; @@ -385,6 +388,8 @@ Administrative slot recovery is OPTIONAL. A registry that supports principal reassignment MUST implement: ```solidity +pragma solidity ^0.8.20; + interface IDocumentBundleAnchorRecovery { event SlotPrincipalAssigned( bytes32 indexed subjectId, @@ -528,13 +533,6 @@ those files. ### Prior Art -The Document Management proposal numbered 1643 defines document references for security tokens. It stores individual -named documents rather than a deterministic, schema-versioned bundle manifest. - -The *Ethereum Notary Interface* proposal defines document signing and -verification. This ERC defines deterministic bundle commitments and -supersession rather than a signing workflow. - [ERC-5732](./eip-5732.md) defines a generic commit-reveal mechanism. It can be used as a privacy layer around publication but does not define document entries or bundle hashing. @@ -549,22 +547,6 @@ redemption flow but does not define deterministic bundle manifesting. flow. It can retrieve material referenced by an anchor but does not determine how a document bundle commitment is derived. -The Ethereum Attestation Service provides generic schema-based attestations. -Such attestations can reference a bundle hash, but they do not define this -manifest or supersession model. - -[RFC 8785](https://www.rfc-editor.org/rfc/rfc8785) defines deterministic JSON -serialization and is used directly by `PROFILE_JSON_RFC8785`. - -[Canonical XML 1.1](https://www.w3.org/TR/2008/REC-xml-c14n11-20080502/) -defines deterministic XML serialization and is used directly by -`PROFILE_XML_C14N11`. - -W3C Verifiable Credential Data Integrity defines proof transformation, -canonicalization, hashing, and verification pipelines for verifiable -credentials. This ERC applies a document-entry manifest and Ethereum anchoring -interface to arbitrary document commitments rather than credential proofs. - ## Backwards Compatibility This ERC introduces new interfaces and does not change existing token or @@ -718,7 +700,7 @@ profile and reproduce the exact transformation. ### Canonicalization Boundary The Solidity hashing library receives document-entry fields and does not parse -or canonicalize JSON, XML, PDF, images, filenames, or MIME types. A caller can +or canonicalize JSON, XML, PDF, images, filenames, or media types. A caller can submit a hash while falsely claiming that a profile was followed. Consumers must reproduce normalization and entry derivation off-chain. From 2524829c64055b5a2a1c533b86defb3efb6ab11b Mon Sep 17 00:00:00 2001 From: David Hay <3615726+david-hay@users.noreply.github.com> Date: Fri, 2 Oct 2026 10:15:42 -0400 Subject: [PATCH 3/3] Update ERC-8326: Extend Last Call deadline --- ERCS/erc-8326.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ERCS/erc-8326.md b/ERCS/erc-8326.md index d5877b210b4..08ec3595a3e 100644 --- a/ERCS/erc-8326.md +++ b/ERCS/erc-8326.md @@ -5,7 +5,7 @@ description: A deterministic document-entry bundle hash and subject-scoped ancho author: Chris Turner , David Hay (@david-hay), Reagan Simpson (@krumg111), Collins Musyimi (@Musyimi97) discussions-to: https://ethereum-magicians.org/t/erc-8326-canonical-document-bundle-anchor/28935 status: Last Call -last-call-deadline: 2026-10-05 +last-call-deadline: 2026-10-19 type: Standards Track category: ERC created: 2026-07-05