Skip to content

Update ERC-8325: Move to Last Call #2019

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eip-review-bot merged 3 commits into from
Oct 2, 2026
+29 −27
Merged

Update ERC-8325: Move to Last Call #2019

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0d28ebe
Move ERC-8325 to Last Call
david-hay Sep 21, 2026
ee52055
docs(erc-8325): address final review feedback
david-hay Sep 30, 2026
6fc895f
Update ERC-8325: Extend Last Call deadline
david-hay Oct 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 10 additions & 7 deletions ERCS/erc-8325.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,8 @@ title: Asset Anchor Registry
description: A registry interface for registry-scoped token-to-anchor bindings for off-chain asset claims
author: Chris Turner <c.turner@kula.com>, David Hay (@david-hay), Reagan Simpson (@krumg111), Collins Musyimi (@Musyimi97)
discussions-to: https://ethereum-magicians.org/t/erc-8325-asset-anchor-registry/28934
status: Review
status: Last Call
last-call-deadline: 2026-10-05

@jochem-brouwer jochem-brouwer Oct 2, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you update the set of these ERCs to have a last-call-deadline longer than two weeks from now?

type: Standards Track
category: ERC
created: 2026-07-04
Expand Down Expand Up @@ -556,8 +557,9 @@ global one-token-to-one-asset uniqueness.

### Prior Art

[ERC-6956](./eip-6956.md) defines ERC-721 tokens bound one-to-one to physical
or digital assets, with operations authorized by oracle attestations of control.
The *Asset-bound Non-Fungible Tokens* proposal extends [ERC-721](./eip-721.md)
with tokens bound one-to-one to physical or digital assets, with operations
authorized by oracle attestations of control.
This ERC is token-standard-neutral and standardizes a registry record binding,
not proof-of-control authorization.

Expand All @@ -566,9 +568,9 @@ to another and mirrors ownership behavior. This ERC binds token contracts or
token IDs to records representing off-chain claims and does not define
token-to-token ownership hierarchies.

[ERC-6065](./eip-6065.md) defines an ERC-721 extension for tokenized real estate
with property identifiers and operating-agreement data. This ERC is not limited
to real estate or ERC-721 and does not prescribe asset-specific operations.
The *Real Estate Token* proposal extends [ERC-721](./eip-721.md) with property
identifiers and operating-agreement data. This ERC is not limited to real estate
or ERC-721 and does not prescribe asset-specific operations.

[ERC-3643](./eip-3643.md) and [ERC-7943](./eip-7943.md) define token behavior and
compliance-related interfaces. They do not define the registry-scoped
Expand Down Expand Up @@ -656,7 +658,8 @@ governance, timelock, or equivalent controls. Consumers should monitor

Releasing an invalidated tuple does not change an immutable token-side anchor
declaration. A replacement can be mutually declared only when the token already
declares the replacement anchor or does not expose a token-side interface.
declares the replacement anchor. A replacement binding recorded for a token that
does not expose a token-side interface is registry-side only.

### Document Canonicalization

Expand Down
Loading