What this looks like
Voluntary and compliance credits issued under the tradeable pattern (Pattern A); the underlying attestation — measurement, reporting, and verification (MRV) — carried as a verifiable credential (Pattern C) anchored to the project, the auditor, and the methodology. The credit is the tradeable surface; the credential is the audit trail.
Continuous MRV under agent mandates
Agentic asset operations run continuous MRV verification under AP2 mandates, with cryptographic provenance from sensor to credit to retirement. Field devices sign readings with TEE-held keys bound to machine DIDs; Tenzro's network verifies the streams before they reach the credential chain; methodology calculations and auditor sign-offs land as verifiable claims, not as PDFs.
This is the digital-MRV posture the registries themselves are moving to — continuous measurement, high-frequency issuance cycles, and data-lineage requirements aligned with the ICVCM Core Carbon Principles — carried down to the hardware root of trust rather than stopping at the reporting platform.
Double-issuance and double-retirement are prevented at the chain level — the same project cannot mint the same vintage twice, and a retired credit cannot be resurrected. These are protocol-level guarantees, not registry policy.
Buyer surfaces
Buyers — corporates, sovereigns, retail — settle into the credit on Canton; mirrors on EVM and Solana support secondary distribution where it exists. Retirement is canonical on Canton with verifiable proof emitted to the mirror surfaces.
Standards used
BSP-0001 (Tradeable Base, draft) for the credit. BSP-0003 (Credential Base, draft) for the MRV attestation chain. Together they give the buyer a single on-chain object that carries both the tradeable property and the full provenance.
The parties on this rail.
- Voluntary registry operators
- Compliance-market participants
- Project developers
- MRV verifiers
- Methodology bodies
- Sovereign environmental authorities
Have a use case in environmental markets?
We scope the integration with you and ship the adapter alongside the anchor program. Neutral infrastructure, on open standards.