Aretia Carbon Infrastructure
Carbon credits on-chain, under the registry’s control.
We are building software that would let a carbon registry put credits it has authorised onto a blockchain, with every step checked and recorded. Today it is a working sandbox. It is not live.
This is early-stage software running on simulated data. No carbon registry is a customer, partner or approver of this work, and nothing here is a live carbon credit. It has not been independently audited. ACT is a separate token and is not a carbon credit.
The registry stays in charge.
A carbon registry owns its standard and its decisions about which credits exist and who may do what with them. We do not replace that. We build the connection: authorised credits go onto a chain with controlled issuance, matching records on both sides, and a clear history.
A token on a chain is not proof that a credit is real, sound or owned by anyone. In this design the registry’s record is always the one that counts, and the software’s job is to keep the chain from drifting away from it.
Six steps, each one checked.
- 1
The registry authorises
A carbon registry decides which of its credits may go on a chain, how many, and where. Nothing happens without that authorisation.
- 2
A signed request
The organisation asks for those exact serial numbers to be tokenised, signed with its own key, once only, with an expiry.
- 3
A second person approves
The person who asked cannot approve. A different reviewer does, and large amounts can need more than one.
- 4
The registry is asked again
Just before anything is created, the registry is checked again. If the credit has changed status, the process stops.
- 5
Mint, then reconcile
The token is created on the chain. The registry, the ledger and the chain are then compared, and any difference is flagged.
- 6
Retirement needs the registry
Burning a token is not a retirement. A retirement counts only when the registry itself confirms it.
Built around the ways this can go wrong.
No credit counted twice
Serial numbers cannot overlap across any organisation. The same credit cannot be put on two chains or requested twice, and a replayed request is refused.
No quantity beyond what the registry authorised
The total is capped by the registry’s own authorisation, across every chain together. Burning does not make room to create more.
When unsure, it stops
If a chain gives no clear answer, the item is held and never repeated until the chain proves what happened. It does not guess and mint again.
Every action leaves a trail
Each privileged step is written to a tamper-evident log, so an edit or a removal can be detected.
One organisation never sees another
Records are separated by organisation. Asking for another organisation’s record gets the same answer as asking for one that does not exist.
What exists, and what does not.
Built, sandbox only
- A simulated registry and two simulated chains, so every failure path can be shown without touching anything real.
- The issuance, approval, reconciliation, retirement and cancellation workflow, with the protections above, covered by automated tests.
- An EVM token contract, written and tested on a local test chain, and adapters for Solana and EVM tested against simulations.
- A console for operators, a developer API with documentation, and a public explorer with signed asset passports.
- A database design with the double-counting rules enforced by the database itself.
Not done
- No connection to any real registry. Each one needs its own documentation, credentials and written approval.
- The contract is not deployed on any network and has not been audited.
- No institutional key custody, no multi-factor sign-in, no independent security review, no penetration test.
- No live credits. Every record in the demo is made up and labelled as sandbox.
Tokenisation of carbon credits is being designed for these registries
These are the registries' own marks, shown only to name them. None of them is a partner, customer or approver of this work.
If you run a registry or an institution.
We would like to talk. Any real use needs the registry’s cooperation and technical access, legal and data-protection review, independent security assurance, and approval of the issuance and retirement workflows. A first pilot would run on simulated data until the registry authorises anything real.
We can share the architecture, the security and key-management design, the double-counting method, the reconciliation specification, and a walkthrough of the sandbox.
Everything Aretia does.
See all features →The future of money
should fund the future.
ACT is live on Solana today, automatically funding a Climate Treasury on every transfer. The wallet brings self-custody across six chains as it ships.
The wallet's browser extension is in development and not yet on the Web Store.