A wrapped carbon token and a retired-backed carbon token can look identical on an exchange: same ticker format, same promise of one token per tonne. Technically they are opposite instruments, and the difference decides whether your purchase creates a double counting problem or solves one. This article defines both models precisely, then walks through the one case that settled the argument in practice: Toucan Protocol’s retired-backed BCT and NCT pools, banned by Verra in May 2022 and still visible on-chain today, versus the locked-credit bridge Toucan operates now with the Puro.earth registry. Everything below was re-verified against official documentation and live explorer data on 20 August 2026.

The Two Models, Defined by One Question

The only question that matters: when the token is minted, what happens to the underlying credit in the registry?

In the retired-backed model, the credit is retired in the off-chain registry first, and the token is minted against that completed retirement. The environmental benefit is consumed before the token exists. The token is therefore a receipt, not a live credit: it can circulate, but it can never go back to the registry, and the underlying tonne can never be sold again off-chain. The double counting protection is structural.

In the wrapped model, the credit stays active in the registry and the token circulates as a claim on it. This is only safe if the registry cooperates by locking the credit in place. Without that lock, nothing stops the same tonne from being sold off-chain while its token trades on-chain: that is the classic double counting scenario, and no smart contract can prevent it, because the failure happens off-chain.

The Case That Settled It: Toucan and Verra

The original Toucan bridge, documented in Toucan’s now-archived Verra bridge guide, was strictly retired-backed. A user retired a batch of VCUs in the Verra registry with a Toucan batch NFT identifier written into the public retirement detail, submitted the resulting Verra serial number on-chain, and only then could mint TCO2 tokens, which could be pooled into BCT or NCT. The one-to-one serial linkage made double bridging impossible.

On 25 May 2022, Verra prohibited exactly this: its official statement bans creating instruments or tokens based on retired credits, on the grounds that retirement means the credit’s environmental benefit is consumed. In the same statement, Verra proposed the alternative it considered acceptable: immobilizing credits in registry accounts so they can be tokenized without being retired. The largest tokenization experiment in the market was frozen mid-flight, and its legacy pools never recovered.

What Toucan runs today is the model Verra pointed to. The current bridge works with the Puro.earth registry: the holder’s CORCs are transferred into Toucan’s Sales Channel inside the Puro registry, locked in an omnibus account for as long as the tokenized version exists, and only then minted as a batch NFT and fractionalized into TCO2 tokens. Toucan’s bridge documentation is explicit that the credits enter a tokenized, locked state in the off-chain registry, and that they stay there until the tokens are either retired on-chain or detokenized, which unlocks the credit off-chain. The bridge is two-way: the detokenization guide describes a “Bring off-chain” function in the Toucan app. A retired-backed token can never offer that; a wrapped token with registry cooperation can.

What the Legacy Pools Look Like Today

The retired-backed era is still fully auditable on-chain. As of August 2026, the BCT contract at 0x2F800Db0fdb5223b3C3f354886d907A671414A7F shows a supply of about 15.68 million tokens across roughly 4,050 holders, priced near $0.0009; the NCT contract at 0xD838290e877E0188a4A44700463419ED96c16107 shows about 1.42 million tokens, 509 holders, near $0.23. Toucan’s current contracts page lists only the Toucan 2.0 deployment; BCT and NCT survive in the archived documentation. Over 17 million tonnes of retired-backed tokens sit stranded: retired in Verra, untradeable under Verra’s rules, and too cheap to matter. This is what a model change looks like when it hits immutable infrastructure.

Where the ICVCM Stands

As of August 2026, the ICVCM has no tokenization-specific standard. What it has is directly relevant though. Core Carbon Principle 2, Tracking, requires programs to run a registry that uniquely identifies and tracks credits. Principle 8, No double-counting, explicitly covers double issuance, double claiming and double use. And the ICVCM’s Tagging Manual for CCP-Eligible Programs makes clear that the CCP label is applied to credits inside the program’s registry, by the program: the label lives on the registry record, not on any derivative instrument. ICVCM has also put platforms on notice, in June 2024, that listing contracts referencing CCP-labelled credits requires agreeing trademark terms with the ICVCM. Read together: a token that drifts away from the registry record drifts away from the label. For a buyer, the CCP status of the underlying credit is only as good as the live link between token and registry entry.

What a Buyer Should Actually Check

  • Ask which model the token uses. If retired-backed: under which registry’s rules was the retirement made, and does that registry permit instruments based on retired credits? Verra does not.
  • If wrapped: find the lock. Ask for the registry account or omnibus record showing the underlying credits immobilized, and verify it in the source registry, not in the issuer’s dashboard.
  • Ask whether the bridge is two-way. Detokenization capability, like Toucan’s “Bring off-chain”, is the fingerprint of a true wrapped structure with registry cooperation.
  • Check the pool composition and vintage on the explorer. The legacy pools show why: acceptance criteria that admitted 2008-vintage credits filled BCT with tonnes the market now prices at nearly zero.
  • Verify quality flags separately. Neither model says anything about additionality or permanence of the underlying credit.

The Bottom Line

Retired-backed tokens prevent double counting by construction but died against registry rules; wrapped tokens are what registries will tolerate, and their safety depends entirely on a lock you cannot see on-chain. The token contract tells you which standard and vintage you hold. Only the registry tells you whether the tonne behind it is locked, consumed, or quietly sold twice.