ERC-8040 ESG asset tokenization protocol (ESG Tokenization Protocol)
Draft · Names & metadata · created 2025-09-06
An overlay interface that attaches standardized metadata, external certification records, and an issuance-audit-retirement lifecycle to ESG (environmental, social, governance) assets such as carbon credits. It is implemented in addition to ERC-20/721/1155, preserving existing transfer functionality.
Why it is needed
For tokenized ESG assets like carbon credits, metadata formats, audit report storage methods, and retirement handling differ from project to project. Without a standard, wallets and exchanges cannot consistently read an asset's region, carbon amount, or audit status, and verification results from auditors and certification bodies cannot remain in a trustworthy on-chain form. As a result, it becomes hard to prevent the same credit from being traded multiple times or double-counted, and asset credibility ends up resting on an unverifiable off-chain claim of 'it was verified.' This standard reduces these problems by combining a metadata schema, audit/certification digests, and state transitions from issuance to retirement into a single interface.
What to implement
function mintESGToken(Metadata memory metadata) external returns (uint256 tokenId);: Mints a new token with ESG metadata and returns the token ID. The initial state is issued.function auditESGToken(uint256 tokenId, bytes memory auditDigest) external;: Records the SHA3-512 digest of an audit report on an existing token and changes its state to audited.function retireESGToken(uint256 tokenId, string memory reason) external;: Permanently retires a token. A retired token cannot be reactivated.function esgURI(uint256 tokenId) external view returns (string memory);: Returns a URI pointing to the token's metadata JSON document.function getMetadata(uint256 tokenId) external view returns (Metadata memory);: Returns the token's full metadata struct on-chain.event Minted(uint256 indexed tokenId, string category, string geo);: Announces the token ID, category, and region information when a new ESG token is minted.event Audited(uint256 indexed tokenId, bytes auditDigest);: Announces the audit report digest when an ESG token is audited.event Attested(uint256 indexed tokenId, bytes atfDigest, string esgURI);: Announces the certification digest and metadata URI when a token receives external certification.event Retired(uint256 indexed tokenId, uint256 timestamp, string reason);: Announces the retirement time and reason when a token is permanently retired.
In depth
Metadata structure
A token must have a JSON metadata document retrievable via esgURI(tokenId). `standard` indicates the metadata version, `category` the ESG asset classification (e.g. carbon), `geo` the region (e.g. an ISO 3166-2 code), `carbon_value` the carbon asset value, and `cycle` the occurrence cycle. `digest` and `evidence` point to the original document or supporting evidence, and `physical_id` is a physical seal identifier. The `attestation` field consists of `atf_digest` (the digest of the certification record) and `signer` (e.g. in the format did:atf:ai:...). `status` is one of issued, audited, or retired. Implementations that store this on-chain may also return the same values via getMetadata(tokenId).
Lifecycle state transitions
A token's lifecycle consists of only three states, issued, audited, and retired, followed in that order. mintESGToken mints the token and sets its state to issued. auditESGToken records the SHA3-512 digest of an audit report and changes the state to audited. retireESGToken permanently retires the token, and the specification explicitly states that a retired token cannot be reactivated. This deterministic state transition is a design goal stated in the source text, and it does not allow arbitrary ordering or reversal.
Call authorization
The authority requirements differ for each of the three functions. mintESGToken can only be executed by callers that the implementation authorizes to issue ESG assets. auditESGToken is likewise restricted to callers with authority to perform audits. retireESGToken can only be called by the token owner, an approved operator, or another party separately authorized by the implementation. The specific authorization logic is left to the implementation and is not fixed in the specification.
Why the digest uses bytes
The specification requires all hash fields, including digest, atf_digest, and auditDigest, to use the bytes type rather than bytes32. A SHA3-512 hash is 64 bytes (512 bits) long, but bytes32 can only hold 32 bytes, which would force truncation of the hash. The Security Considerations section notes that such truncation weakens cryptographic security, and explains that using the bytes type preserves the full digest so that the preimage resistance of long-retained audit records is maintained.
How it combines with base token standards
This ERC does not replace ERC-20, ERC-721, or ERC-1155; it is an overlay implemented on top of them. Combined with ERC-20, each unit represents a standardized fraction, for example 1e18 units could represent 1 metric ton of CO2 (1 tCO2e). Combined with ERC-721, each token becomes a single credit with a unique esgURI and immutable metadata. Combined with ERC-1155, it represents homogeneous batches and fungible quantities that share a common URI and metadata.
Standard status
This standard is currently in Draft status, a proposal that may still change or stall as it goes through community review.
Things to watch out for
- Metadata sealing: After minting, all metadata fields must be cryptographically sealed and unchangeable.
- Verification independence: The standard must not rely on unauthenticated off-chain claims; authentication must be expressed through verifiable digests and events.
- Digest integrity: The full SHA3-512 (64-byte) digest must be stored as a bytes type to prevent truncation.
- Irreversibility of retirement: Once a token is retired, it cannot be reactivated.
- Physical seal verification: The on-chain digest must match the cryptographic hash of the physical seal.