Skip to main content
CarbonBlaze
All learning lessons

05Follow the record

How carbon registries work

Learn what a registry can show about issuance, ownership, transfer, retirement, and the public record behind a unit.

Last reviewed

01CarbonBlaze explainer

Registries help create an identifiable record.

A registry can assign a unique identity to a project and to issued units, then record transactions and retirement. This creates an evidence trail that helps prevent confusion about which credits exist and how they have been used.

02CarbonBlaze explainer

A registry record is one important layer of diligence.

A public record can help readers locate project documents, issuance information, and retirement details. It does not replace understanding the assumptions, methodology, or context used to quantify an outcome.

03CarbonBlaze explainer

Traceability supports clearer claims.

When a public claim involves credit use, being able to identify the relevant credit, registry, and retirement record makes the claim easier for others to understand and scrutinize.

Registry-record trail diagram: project and program record, issued units with identifiers, registry status and transactions, transfer or account movement, retirement or end-use record, and a specific public statement. A note says registry traceability does not replace wider diligence or decide every claim question.
Registry records can make an evidence trail easier to follow, while methodology, monitoring, project documents, and claim context remain separate questions.

Related field paths

These local guides explore adjacent parts of the same evidence trail. They are starting points for learning, not project ratings or recommendations.

Common questions

What does retirement mean?

Retirement typically records that a unit has been removed from circulation for a stated use, so it should not be transferred or claimed again within that registry system.

Do all registries work identically?

No. Readers should review the relevant program rules, public interfaces, documentation, and project-level information.