ERC-7929 PermaLink Asset-Bound Token (ABT) (PermaLink Asset Bound Token)
Draft · NFTs & multi-token · created 2025-04-01
An asset-bound token standard that permanently binds one token to another, so that when the bound token (the binding token) moves, the dependent PermaLink-ABTs move together with it.
Why it is needed
On Ethereum, assets have traditionally only been owned by EOAs or smart contracts, and once a contract is deployed it is difficult to adapt it to new uses. However, cases where multiple tokens need to stay linked and move together are increasing, such as on-chain identity, real-world asset (RWA) tokenization, supply-chain stage assets, and NFT follow-up collections. Building such structures without a standard forces manual synchronization through separate transfers and approvals for each asset, creating inefficiencies such as identity-related tokens scattered across multiple registries or duplicate creation of supply-chain stage tokens. It can also cause an NFT project's follow-up collection to compete with the existing collection, splitting value and attention. PermaLink-ABT solves this fragmentation problem by permanently binding one token to another.
What to implement
event AssetBoundContractSet(address assetBoundContract);: Emitted when the contract is deployed and bound to assetBoundContract.function ownerOf(uint256 tokenId) external view returns (address);: Reads and returns the owner of the given tokenId from assetBoundContract.function tokenExists(uint256 tokenId) external view returns (bool);: Returns whether the token read from assetBoundContract exists (i.e., whether the owner is not the zero address).function totalSupply() external view returns (uint256);: Returns the total number of tokens stored in assetBoundContract.function balanceOf(address owner) external view returns (uint256);: Returns the number of NFTs held by the given owner, as read from assetBoundContract.event TokenRevealed(uint256 tokenId);: Emitted when a tokenId is revealed.function reveal(uint256[] calldata tokenIds) external payable;: Activates (reveals) pre-allocated tokenIds.
In depth
Token Interface (IERC7929) and State Mirroring
IERC7929 must implement four functions: ownerOf, tokenExists, totalSupply, and balanceOf. These functions do not reflect the state of the PermaLink-ABT contract itself; instead, they read and return the values of the assetBoundContract specified in the constructor as is. tokenExists is implemented to return true if assetBoundContract.ownerOf(tokenId) is not address(0); a token generally begins to exist when minted and ceases to exist when burned.
AssetBoundContractSet Event
The AssetBoundContractSet(address assetBoundContract) event is emitted when the contract is deployed and bound to assetBoundContract. In the reference implementation, this event is emitted immediately after the constructor stores assetBoundContract as an ERC721Enumerable.
Removing transfer and approve to Enforce Permanent Binding
approve, setApprovalForAll, transferFrom, and both safeTransferFrom variants are all overridden to revert in the reference implementation. This design ensures that once a PermaLink-ABT is revealed, it can never be separated from its bound asset, producing the effect that dependent PermaLink-ABTs move together whenever the binding token moves.
Pre-Allocated Activation via reveal (IERC7929Reveal, Optional)
Instead of mint, the reveal(uint256[] calldata tokenIds) function activates tokens already stored in an array or mapping on demand. The reference implementation's modifier requires that a token already exist (tokenExists) and not yet be revealed; for each token it sets isRevealed to true and emits a TokenRevealed(tokenId) event. This extension is optional and is described as costing less gas than dynamic token creation.
Interface ID and ERC-165
In the reference implementation, the interface ID of IERC7929 is specified as 0x0b76916c and that of IERC7929Reveal as 0xb93f208a. supportsInterface is overridden to add checks for each interface ID on top of the ERC721Enumerable implementation.
Design Rationale: Why Mirroring and Permanence Were Chosen
The original text also considered more flexible transfer approaches such as opt-in transfer or whitelisting, but discarded them because they increase complexity and raise the risk of token desynchronization, fragmentation, and security vulnerabilities. Instead, it explains that the current design, which mirrors the state of assetBoundContract as is and removes transfer and approve, provides a simpler and more robust foundation.
A proposal that has not yet been finalized
ERC-7929 is currently in Draft status. The function composition of the specification and the detailed behavior of the reveal extension may change or be discontinued through further discussion.
Things to watch out for
- Risk of Losing Access to the Binding Token: Since a PermaLink-ABT is bound to a binding token, if a user loses access to the binding token, they also lose access to every PermaLink-ABT bound to it. The value of the entire bound asset set depends on the security and availability of a single binding token.
- Recommended Combination with 2FA/Recovery Mechanisms Such as ERC-6809: The original text strongly recommends applying a standard such as ERC-6809 (Non-Fungible Key Bound Token), which provides on-chain two-factor authentication and a safe recovery path (safeFallback), to the binding token. The security guarantees of ERC-6809 extend as is to every PermaLink-ABT bound to it, providing a basis for recovery even in cases of lost wallets or interaction with malicious contracts.