ERC-8393 proposes retirement standard for tokenized carbon credits

The ERC-8393 proposal classifies carbon credits as semi-fungible tokens built on ERC-1155.

That choice means the credit’s identity travels with the token. Each ERC-8393 token encodes a(projectId, creditId) pair inside a singleuint256 identifier, keeping the project and the specific credit record bound together at the token level.

The proposal also locks down the metadata schema rather than leaving each deployment to invent its own fields.

The accounting change worth watching is retirement.

Under ERC-8393, retiring a credit means using it to offset emissions. The holder’s transferable balance drops by the retired amount; an equal balance is recorded as retired, permanently, and cannot move. Retire 100 units and the ledger shows 100 fewer transferable units plus 100 retired units that stay attached to the record forever. They don’t come back.

That split does two things at once. Transferable balances keep representing credits available for sale or movement. Retired balances preserve an auditable record of what was actually used for offsetting.

For anyone holding or integrating ERC-8393 credits, the practical effect is immediate: a retirement transaction permanently reduces what can be sold, and the retired amount cannot return to circulation under the balance model as written. Implementers also inherit the fixed data schema, including expiry and issuance volume fields. The proposal doesn’t set an implementation deadline, and the published record doesn’t address interoperability with existing registry conventions like Verra or Gold Standard — an unresolved question that will matter to anyone trying to bridge this standard to incumbent infrastructure.

Ethereum’s price is incidental context here.

What the document actually claims is narrower: tokenized carbon credits can share an ERC-1155-based identity structure and a ledger that distinguishes live inventory from permanently retired credits. Whether implementations follow depends on builders and on those open registry-compatibility questions no one has answered yet.