Deep diveCertificates & Carbon Credits

Double counting in digital carbon credit registries, and how to design it out

Double counting means one tonne of reduction or removal supports more than one claim. It happens in three ways: the same activity is credited twice, the same credit is sold or retired twice, or two parties claim the same tonne. Digital registries and tokens can close some of these gaps and open new ones. This deep dive explains each form, the controls that address it, and what a ledger cannot prove.

Reviewed 8 min read

On this page
  1. The vocabulary of double counting, defined
  2. Why tokenisation can create new routes to double counting
  3. Double issuance across programmes and registries
  4. Keeping a token and its immobilised registry unit in step
  5. Fields a carbon credit retirement record should carry
  6. Authorised and non-authorised credits under Article 6
  7. Integrity frameworks buyers lean on, and their limits
  8. Reconciling a tokenised credit inventory against registries
  9. A hypothetical marketplace listing credits from two registries
  10. What an immutable record cannot prove about a credit
  11. Questions and answers
  12. Sources

The vocabulary of double counting, defined

These terms are used loosely. Pinning them down shows which control addresses which problem.

Double issuance
More than one credit is issued for the same reduction or removal, for example because a project is registered with two programmes or overlaps another project's area.
Double use
One issued credit is sold, transferred or retired more than once. Bridged tokens that keep circulating after the registry unit is retired are a modern variant.
Double claiming
The same tonne counts towards two parties' targets, typically a company's voluntary claim and a country's national emissions total.
Retirement
Permanent removal of a credit from circulation so its benefit can be claimed once, recorded with a beneficiary and purpose. Some programmes call this cancellation.
Immobilisation
Locking a registry unit in a dedicated account so it cannot move or be retired while a linked digital representation exists.
Corresponding adjustment
An accounting entry by a host country under Article 6 of the Paris Agreement that removes an internationally transferred reduction from its own total, so it is counted only once.

Why tokenisation can create new routes to double counting

A conventional registry controls double use by design: a credit has one serial, sits in one account and is retired once. Tokenisation adds a second representation outside that registry. Unless the two are tied together, a credit can be retired in the registry while its token keeps trading.

Standard-setters have responded to exactly this risk. Verra stopped the creation of instruments or tokens from retired credits and consulted on a model in which units are immobilised in registry accounts while a linked token exists1. Gold Standard's terms require its express written consent before anyone creates tokens representing its credits, and it consulted on the conditions for granting that consent2. Policies in this area have moved more than once, so check each programme's current terms before designing a bridge.

A tokenised credit is therefore only as sound as its link to a locked registry unit. A token that merely references a serial, without the registry stopping that serial from moving, is a promise rather than a control.

Double issuance across programmes and registries

Double issuance is the hardest form to catch from inside one system, because the duplicate lives somewhere else. A forestry project might be listed with a voluntary programme while the same land falls inside a jurisdictional programme, or two project developers might claim overlapping areas. A ledger records what it is given; it cannot see a registry it is not connected to.

The controls are procedural and data-driven. Programmes ask proponents to attest that the activity is not registered elsewhere, and registries can compare project identifiers, boundaries and monitoring periods with other public registries. For land-based projects, comparing geospatial boundaries catches overlaps that names miss. A digital platform helps by holding these identifiers in a form that can be compared automatically, but only across the data it can reach.

Keeping a token and its immobilised registry unit in step

Request lockConfirm locked serialsMint linked tokenTransfer tokenRequest retirementBurn tokenRetire serialsRetirement record01Credit holder02Officialregistry03Tokenisationplatform04Ledger05Buyer
  1. Credit holder

    Owns the units in the official registry and asks for a digital representation.

  2. Official registry

    Locks the serials, publishes the link and performs the final retirement.

  3. Tokenisation platform

    Mints and burns tokens only against confirmed locked serials.

  4. Ledger

    Holds the token and its transfer and burn history.

  5. Buyer

    Acquires the token and requests retirement for a named claim.

  1. Credit holder to Official registryRequest lock
  2. Official registry to Tokenisation platformConfirm locked serials
  3. Tokenisation platform to LedgerMint linked token
  4. Ledger to BuyerTransfer token
  5. Buyer to Tokenisation platformRequest retirement
  6. Tokenisation platform to LedgerBurn token
  7. Tokenisation platform to Official registryRetire serials
  8. Official registry to BuyerRetirement record
Conceptual message sequence for a lock-and-mint model. Order and names vary by programme; it is not any registry's actual interface.

Fields a carbon credit retirement record should carry

A retirement recorded with only a serial and a date cannot show who may claim the tonne, or for what.

0 of 8 checked

Authorised and non-authorised credits under Article 6

Article 6 of the Paris Agreement lets countries cooperate on mitigation and transfer outcomes between them3. Whether a credit is authorised for that use changes what its buyer can say about it.

AspectAuthorised, with a corresponding adjustmentNot authorised, no adjustment
Host country accountingThe host country adjusts its own total so the tonne is counted by the user, not by the hostThe reduction also stays in the host country's national total
Claims typically supportedUse towards another country's target or in compliance schemes that require authorisationContribution-style claims that support climate action without offsetting the buyer's own emissions
Evidence to keepThe authorisation letter, the purpose it covers and the host country's reporting of the adjustmentA clear statement that no adjustment applies, so the credit is not later presented as adjusted
Typical failureThe adjustment is promised but not reported, leaving the tonne counted twice in practiceThe credit is marketed as offsetting emissions in a way the buyer's claims framework does not support

Rules on authorisation and adjustments continue to be developed under the Paris Agreement; check the current decisions and the host country's own authorisation process.

Integrity frameworks buyers lean on, and their limits

Two frameworks shape how buyers judge credits and claims. The Integrity Council for the Voluntary Carbon Market sets out ten Core Carbon Principles; programmes assessed as CCP-Eligible can label credits from approved categories that meet them4. The Voluntary Carbon Markets Integrity Initiative publishes a Claims Code of Practice describing how companies can use high-quality credits in claims alongside their own emissions reductions5. Both are revised periodically, so cite the version you rely on.

Neither framework replaces registry controls. A CCP label describes the programme and credit category; it does not stop a specific unit being sold twice, and a well-formed claim still depends on a correct retirement record. Store the label and claim basis next to the serial in the tracking layer, not in a separate spreadsheet.

Reconciling a tokenised credit inventory against registries

  1. Snapshot registry holdings

    Pull locked and retired serials for each registry through its API or published exports on a fixed schedule.

    Output
    Dated registry snapshot

  2. Map serials to tokens

    Join every live token to the serial range it represents, and every serial range to at most one token.

    Output
    Serial-to-token map

  3. Compare supply and status

    Check that live token supply equals locked units and that no burned token's serials are still locked or tradable.

    Output
    Break report

  4. Resolve breaks with an owner

    Route each mismatch to a named person with a deadline, and freeze affected tokens until it is closed.

    Owner
    Registry operations lead

  5. Publish an attestation

    Share the reconciliation result with participants, and have it reviewed independently where buyers rely on it.

    Output
    Signed reconciliation statement

A hypothetical marketplace listing credits from two registries

What an immutable record cannot prove about a credit

Questions and answers

Can a retired carbon credit be tokenised?

It should not be. Retirement means the credit's benefit has been used for a claim, so a token representing it would suggest the benefit is still available. Major programmes have taken this position explicitly. A token can represent a retirement as a receipt or certificate of the claim, provided it cannot be traded as if it were a live credit.

Who records a corresponding adjustment?

The host country does, through its reporting under the Paris Agreement. A project developer, registry or buyer cannot apply one themselves. What they can do is keep the authorisation letter and track whether the host country has reported the adjustment, so the credit's status in the tracking record reflects what has actually happened rather than what was promised.

Does an on-chain retirement count for corporate reporting?

Only if it corresponds to a retirement in the programme's authoritative registry. Reviewers and assurance providers look for the registry's retirement reference, beneficiary and purpose. An on-chain burn is useful supporting evidence and can make the claim easier to check, but on its own it is a record on a ledger, not a retirement recognised by the programme.

Can two registries detect double issuance between them automatically?

Partly. Where both publish project identifiers, locations, boundaries and monitoring periods in machine-readable form, overlaps can be flagged automatically and then investigated by people. Where data is published only as documents, detection still depends on proponent attestations and manual review.

Sources

  1. Verra's approach to third-party crypto instruments and tokens — Verra · checked 10 October 2026
  2. Tokenisation consultation: feedback and next steps — Gold Standard · checked 10 October 2026
  3. Paris Agreement — United Nations Framework Convention on Climate Change · checked 10 October 2026
  4. The Core Carbon Principles — Integrity Council for the Voluntary Carbon Market · checked 10 October 2026
  5. VCMI Claims Code of Practice — Voluntary Carbon Markets Integrity Initiative · checked 10 October 2026
  6. Certificates & Carbon Credits: scope and boundaries of lifecycle tracking — ColdAI

More in Certificates & Carbon Credits

Back to Certificates & Carbon Credits

Next step

Check your retirement and reconciliation design for double counting

Send us the programmes you list or buy from and how tokens or mirrors link to registry units. We will point out where double use or double claiming could slip through and what to fix first.

Review my registry design