Platform overview

The institutional carbon-credit infrastructure.

Tokenized at the source registry, settled on-chain, retired with cryptographic proof, and reconciled continuously against off-chain holdings. Built for the firms that take carbon seriously.

The problem

Registries don't talk to each other.

Verra credits live in Verra's database. Gold Standard credits live in Gold Standard's. Puro's in Puro's. Moving credits between them, retiring against a CSRD report, or proving ownership to an auditor still means portals, screenshots, and PDFs.

Retirement is manual: log into the registry, fill a form, receive a confirmation email, attach it to your sustainability report. Hope the auditor accepts the screenshot.

Trading desks can't even price these instruments meaningfully because there's no settlement layer they trust. The market clears in OTC voice trades and trust relationships.

The solution

One settlement layer. Every registry.

Credits are locked at the source registry, mirrored on-chain as ERC-1155 batches with 1:1 backing, and continuously reconciled via a Chainlink Proof-of-Reserve oracle. If the on-chain supply ever drifts from registry holdings, the bridge auto-pauses before anyone can mint another token.

Retirement burns the ERC-1155 and mints a soulbound ERC-721 certificate. An off-chain worker closes the loop at the registry and writes the proof URL back to the certificate. One on-chain action. Full audit trail. Permanent.

Trading happens on top — CLOB, RFQ, pools (ERC-20 wrappers around eligibility rules), forwards (ERC-3525 pre-issuance offtake). Compliance-gated tokenized funds (ERC-3643) distribute to qualified institutional investors only.

Built for

Five tenants. One infrastructure.

Every action below is role-gated. A buyer sees a portfolio. A developer sees their projects. A trader sees a book. An auditor sees the world but can't change it. The platform operator (PGIM / AssetX) sits at the center and runs the whole thing.

Institutional Buyer

Banks, insurers, pensions, family offices, corporate treasuries — anyone retiring carbon at scale.

  • Hold tokenized credits as ERC-1155 batches in custody (Fireblocks / Anchorage)
  • Retire on-chain → get a soulbound certificate carrying the upstream registry proof
  • Generate CSRD / ESRS E1-7 reports straight from on-chain data
What you'll see in the demo

Retire 1,000 tCO2e from your portfolio. Watch the certificate appear, then click into it — the registry proof URL is right there.

Open this tenant's demo

Project Developer

Project SPVs and developers — the people producing the credits at the registry.

  • Submit projects through a vetted intake pipeline (PDD, methodology, geographic boundary, MRV)
  • Request tokenization once credits are issued at the registry
  • Sell tranches via forwards (ERC-3525) — pre-issuance offtake against future deliveries
What you'll see in the demo

Submit a new project, request 5,000 tonnes for tokenization, watch it move into the operator's queue.

Open this tenant's demo

Trading Desk

Buy-side and sell-side institutional traders — the people moving credits in real time.

  • CLOB + RFQ workflows over tokenized credits, with hotkeys + cancel-all panic buttons
  • Cross-pool subscriptions and redemptions (ERC-20 wrappers around eligibility-rule baskets)
  • Forward-market participation with split / merge / transfer of ERC-3525 tranches
What you'll see in the demo

Place a limit order on the Atlantic Forest REDD+ book. Fills against a maker. ERC-1155 transfers settle.

Open this tenant's demo

Auditor / Regulator

Internal audit, external assurance firms, regulators (ADGM FSRA, MAS, SEC).

  • Read-only access to reconciliation, retirements, mints, role assignments, and event log
  • Cryptographic verification of audit packs (SHA-256 hash recompute)
  • Annotate records during investigation (internal-only)
What you'll see in the demo

Pull up the daily reconciliation dashboard. Verify the audit pack integrity hash. Drill into any retirement.

Open this tenant's demo

PGIM / AssetX (Platform Operator)

The master tenant. Bridge ops, compliance, smart-contract admin, treasury, distribution.

  • Bridge ops: verify registry locks, sign attestations, submit mints via multi-sig
  • Compliance: KYC review, freezes, force-transfers, sanctions-hit response
  • Smart-contract admin: upgrades, role grants, emergency pauses — all timelock-gated
What you'll see in the demo

Inject drift through the admin panel. Watch the bridge auto-pause. Unpause via the multi-sig flow.

Open this tenant's demo
The flow

From registry, to chain, to retirement.

Every credit on the platform makes the same trip. The infrastructure doesn't care which registry it came from — every adapter speaks the same EAS attestation schema.

01

Lock at registry

Credits move into the platform's account at Verra / Gold Standard / Puro. The off-chain registry holds them in immobilization.

02

Attest + mint

Our trusted attestor signs an EAS attestation. The bridge mints a 1:1 ERC-1155 batch to the buyer's wallet.

03

Trade or pool

Buyers hold, trade on the CLOB / RFQ desk, or deposit into eligibility-rule pools (ERC-20 wrappers).

04

Retire and certify

Retirement burns the ERC-1155 and mints a soulbound ERC-721 certificate. The registry-sync worker retires the upstream credits and writes the proof URL back.

About this demo

What's real, and what's simulated.

Real
  • The chain. Polygon mainnet. Every transaction you see is verifiable on Polygonscan.
  • The contracts. All 11 contracts (registry, bridge, batch token, retirement, certificate, oracle, pools, forwards, compliance wrapper) deployed and operational.
  • The attestations. Signed against the canonical Ethereum Attestation Service contract. The trusted attestor key is held by the platform.
  • The retirements + certificates. On-chain ERC-1155 burn → soulbound ERC-721 mint → registry-sync close-loop. End-to-end.
Simulated
  • The registries. A “Sandbox Registry” service stands in for Verra / Gold Standard / Puro. Same API shape; mock inventory of fake projects. The on-chain stack genuinely can't tell the difference — the bridge only verifies the attestation, not the registry behind it.
  • The payment token. A platform-deployed mock USDC contract. Mintable freely by demo accounts.
  • The KYC / compliance approvals. Pre-approved for the demo wallet. Real onboarding lives behind the wizard at /onboarding.
  • Time. Daily reconciliation runs every 60 seconds. Multi-sig timelocks compressed for demo cadence.
The point. Everything the platform itself does is real. The pieces being simulated are the ones that need partnership signatures, not engineering — and the moment those partnerships close, the same code points at real Verra instead of mock Verra. No rewrite.
Ready

Open the demo.

Five tenants. One infrastructure. About nine minutes start to finish. Every transaction lives on Polygon mainnet.

Demo build · Polygon mainnet · Sandbox Registry mode