Carbon tokens: a guide to tokenized carbon credits in 2026
Tokenized carbon credits in 2026: what Verra and Gold Standard require today, why the first bridges were banned and how retirement is reconciled.

Between the forestry project or biochar plant that generates a carbon credit and the company that retires it to support a climate claim there is usually a registry, one or more intermediaries and bilateral purchase agreements. The crediting program's registry is the piece that gives the rest its meaning: it records each unit with its serial number, project, methodology and vintage, and it records the retirement, the moment the unit can no longer be sold because someone has used its environmental benefit. Tokenization proposes representing those units with tokens that circulate on a network, so that transferring them, splitting them or proving their retirement no longer depends on emails, spreadsheets and PDF certificates.
For a project developer who wants to sell credits this way, or a company considering buying them already tokenized, the deciding question in 2026 is not a technical one. Verra and Gold Standard prohibit, in their current terms of use, creating tokens on their units without their express written consent, so a tokenized credit is only reliable if its issuer holds that authorization and keeps each token reconciled with a unit locked in the registry until it is retired. That link makes it possible to verify that the token corresponds to a real, unused credit; the credit's environmental quality still depends on the project, its methodology and its verification, and no network changes it.
What a credit represents and what a token can represent
Under Verra's Verified Carbon Standard, each unit, called a VCU, represents one metric tonne of CO₂ equivalent reduced or removed and verified under an approved methodology. The figure only makes sense in context: whether the project reduces emissions that would otherwise have occurred, such as a plant that captures methane from a landfill, or removes CO₂ from the atmosphere, such as a reforestation project; whether the result is additional, meaning it would not have happened without the credit revenue; and what its reversal risk is, the possibility that stored carbon returns to the atmosphere, for example in a fire. These are questions of methodology and verification, and recording the unit on-chain answers none of them.
The token, for its part, can represent three different things, and the buyer needs to know which one it holds. It can correspond to a unit identified by its serial number and locked in a registry account while the token circulates. It can be a share in a pool of units from different projects, where the holder does not choose which specific credit backs its position, as with the BCT token discussed in the next section. Or it can be a contractual right against an intermediary that undertakes to deliver or retire credits, in which case the backing depends on that intermediary's solvency and bookkeeping. All three structures are sold under the same name of "carbon token" and do not give the holder the same rights.
Why Verra prohibited the first bridges
In 2021, the Toucan protocol opened a bridge between the Verra registry and the Polygon network. The holder retired VCUs in the registry, entering a Toucan batch identifier in the retirement details; the protocol checked the serial number and minted TCO2 tokens in exchange, one per tonne, which could be deposited into a shared pool and swapped for the BCT (Base Carbon Tonne) token. The credit appeared in the registry as retired, that is, used up, while its representation kept circulating and changing hands on-chain.
Verra warned on November 25, 2021 that those tokens were not VCUs and did not carry their environmental benefit, and on May 25, 2022 it prohibited, with immediate effect, creating instruments or tokens based on retired credits, because retirement is understood as using up that benefit. In the same statement it proposed exploring the alternative: immobilizing live credits in registry accounts for as long as the token exists. It put the idea to public consultation from August 3 to November 1, 2022 and received input from 71 stakeholders. Since then, according to Toucan's documentation, VCUs that had not already been tokenized can no longer pass through its bridge.
What registries require today
Verra has not published a general tokenization framework since that consultation, and what applies today are its registry terms of use, in the July 2026 version. Clause 1.9 bars an account holder from creating, marketing or transacting in "Related Instruments", or facilitating others to do so, without Verra's express written consent, granted at its sole discretion. The document defines a Related Instrument as a product legally distinct from the unit that has the unit as its underlying, a description that covers any VCU-backed token. Anyone who obtains consent must also demonstrate to Verra its technical competence, financial standing and regulatory permissions.
Gold Standard reaches the same point with more explicit wording. Its registry terms, version 2.0 of December 2024, prohibit in clause 13.1 creating, directly or by consenting to another person doing so, utility tokens, NFTs, cryptocurrencies or similar digital assets that have its units as their underlying without its express written consent, also at its discretion. Clause 13.4 allows it to suspend the account or require the units to be canceled if it discovers a token created without that consent. Its own 2022 consultation drew feedback from more than 35 organizations, and in its latest published update, from June 2024, Gold Standard had still not decided whether it will issue guidelines for digital assets.
The model that works today is the one Verra floated in 2022: the unit stays immobilized in the registry for as long as the token exists. That is the design of Toucan's bridge with Puro.earth, a registry of carbon removal certificates known as CORCs. Tokenized certificates remain locked in an omnibus account in the Puro registry while their on-chain version exists, and the bridge supports tokenizing them, returning them to the registry and retiring them. For anyone building a platform, the practical consequence is that the first conversation in a carbon tokenization project is with the registry, not with the development team: without its written consent for the specific arrangement, the token has no recognized backing, and neither the token's ticker nor a commercial reference to the standard makes up for it.
Issuance, circulation and retirement are separate operations
Once the arrangement is authorized, the platform has to govern three moments with different owners. Issuing the unit belongs to the program, after it validates the project and verifies its results. Minting the token belongs to the platform, and should only happen once the registry confirms that the identified unit is locked in the designated account: minting without that confirmation creates a token with no right behind it.
While the token circulates, the platform must be able to show at any time which units back it and prevent the same unit from being used twice, for example sold in the registry and on the network at once. That requires regularly reconciling the locked serial numbers with the issued supply and planning what happens to the units if the platform stops operating: who controls the registry account and how the units are returned to token holders.
Retirement is the most frequently confused operation. Retiring is a registry status, recorded in the name of a beneficiary and for a stated use; burning a token is a contract operation. Claiming that the second produced the first requires the request to the registry, its confirmation and evidence that the retired serial number is the one that backed the token. If any of those pieces is missing, the interface should show a pending retirement, not a completed offset.
An example: a company retiring 10 tonnes
The case is hypothetical. A platform holds a program's written consent to represent 100 units from a reforestation project, all of the same vintage and locked in a registry account, and has issued 100 tokens, one per unit, with each unit's serial number linked in the contract. A distribution company buys 10 tokens to back the offset it will report in its annual report and asks for them to be retired in its name.
The platform reserves the 10 tokens so they cannot be transferred, identifies the matching serial numbers and asks the registry to retire them with the company as beneficiary. Until the registry confirms, the status is pending and the tokens stay reserved; if it rejects the request, they are released. Once confirmation arrives, the platform burns the 10 tokens, stores the retirement reference and gives the company the proof with serial numbers, project and date. The exact order is set by the program's rules, but two conditions do not change: no token is burned without a confirmed retirement and no credit is retired twice.
If the platform pooled credits from several projects in a single token, it would need an extra step: deciding and disclosing which units it retires for each buyer. A figure of "10 tonnes offset" without serial numbers does not let the company check the provenance of what it bought, or its auditor verify the claim.
Voluntary credits, the EU ETS and token classification
A voluntary market credit is not an allowance under the EU Emissions Trading System (EU ETS) and cannot be used to meet its obligations. International credits under the Kyoto Protocol are a different matter. Certified Emission Reductions (CERs) from the Clean Development Mechanism, for instance, were accepted by the EU ETS in its phases 2 and 3: according to the European Commission, they could be used until April 30, 2021, and phase 4, which began that year, no longer allows them. Tokenizing either one does not change that.
A token's legal classification depends on the rights it confers and the activities around it. The MiCA Regulation does not apply automatically to anything called a "carbon token": its Article 2(4) excludes crypto-assets that are financial instruments, which are assessed under securities rules. MiFID II classifies EU ETS emission allowances as financial instruments (Annex I, Section C, point 11), so their tokenized representation falls outside MiCA. A token on a voluntary credit may fall under MiCA if it is offered to the public as a crypto-asset, or under securities rules if it entitles the holder to the project's future revenue. Each issuance's law firm makes that call, and the analysis of MiFID II and tokenization explains the framework.
Tokenizing carbon credits improves accounting, not credit quality
The value of tokenizing carbon credits lies mainly in record-keeping, not in the market. A shared ledger in which each token points to a locked serial number, and each burn to a confirmed retirement, makes it possible to rebuild the history of every tonne, apply transfer rules such as selling only to verified buyers, and give the buyer proof of retirement that its auditor can check against the registry. For a developer selling to different buyers in small lots, that traceability replaces manual reconciliation of contracts, deliveries and certificates.
What it does not solve is just as concrete. The network's transparency does not detect double counting that happens outside it, such as the same reduction claimed by the host country and by the buying company, which is a coordination problem between registries and contracts. Nor does it filter quality: in a pool that accepts credits from different projects, depositors have an incentive to contribute the cheapest credits its rules allow, and Toucan itself had to block HFC-23 destruction credits, whose support Verra had withdrawn, after approving batches of about 600,000 tonnes. And a token being transferable does not create buyers or a price.
Before building or buying, the file should answer five questions: which program and methodology back the units, who holds the registry's written consent and for which arrangement, exactly what right the token holder has, how the issued supply is reconciled with the locked units, and what happens to those units if the platform disappears. Metlabs designs its carbon credit tokenization platform from those answers, and the guide to carbon tokenization companies covers which registries, protocols and marketplaces work with tokenized credits today.
- Verra Registry, Terms of Use (July 2026), clause 1.9 (2026)
- Gold Standard, Impact Registry Terms of Use v2.0 (December 2024), clause 13 (2024)
- Verra, Verra Addresses Crypto Instruments and Tokens (2022)
- Verra, Statement on Crypto (2021)
- Verra, Summary of Public Comments: Verra's Approach to Third-Party Crypto Instruments and Tokens (2023)
- Gold Standard, Tokenisation consultation feedback and next steps (updated June 21, 2024)
- Verra, Verified Carbon Standard
- Toucan documentation, Verra bridge (deprecated)
- Toucan documentation, FAQ for transition to Open Source
- Toucan documentation, Puro Carbon Bridge: how bridging works
- European Commission, Updated information on exchange and international credit use in the EU ETS (2021)
- MiCA: Article 2, scope
- MiFID II: Annex I
Frequently asked questions
Got a blockchain project in mind?
From idea to product, strategy and technology must move forward together.







