Overview
Digital vouchers enable households to receive benefits for verified emission reductions through a secure blockchain-based system. These vouchers (CARBON credit tokens) can be used to purchase approved products from authorized suppliers.Digital vouchers are issued as CARBON credit tokens using the EIP1155 standard, with embedded attributes linking them to verified emission reduction certificates.


Key Actors
Household Beneficiaries
Receive and spend CARBON credit tokens for emission reductions
Suppliers
Accept vouchers and submit verifiable claims
Implementers
Manage emission reduction projects and ITMO conversions
Regulators
Monitor and approve mitigation activities
Voucher Lifecycle
1. Issuance
2. Redemption
3. Claim Submission
Token Conversion Flow
1
CARBON → USDC
Suppliers make claims to convert received CARBON tokens to USDC through the liquidity pool
2
USDC → Local Currency
Suppliers convert USDC to local currency via payment processors
3
USDC → CARBON
Implementers swap USDC for CARBON tokens through the liquidity pool
4
CARBON → ITMO
Implementers convert CARBON tokens to ITMO claims with on-chain transfer proofs
5
ITMO → Fiat
Implementers convert ITMO claims and transfer prooofs to ITMO Certificates through National Registy
Implementers receive fiat payments for ITMO certificates through Mitigation Outcome Purchase Agreements (MOPA)
6
Fiat → USDC
Implementers convert fiat payments to USDC through a regulated exchange operator (Circle)
Validation Rules
Issuance Rules
Issuance Rules
- Must have valid emission reduction certificate
- Recipient must be registered household
- Value must match verified reduction amount
Redemption Rules
Redemption Rules
- Voucher must be active and non-expired
- Supplier must be authorized
- Amount must not exceed available balance
- Product must be approved for scheme
Claim Rules
Claim Rules
- Must include verifiable delivery proof
- Must align with monitoring plan
- Must be submitted within time limit
Response Format
Error Codes
Invalid parameters or validation failure
Unauthorized access or invalid credentials
Forbidden operation (e.g., unauthorized supplier)
Resource not found
Conflict with existing state
Security Considerations
Never expose API keys or private keys in client-side code. Always use secure server-side implementations for token conversions and claims processing.
- All transactions are recorded on the Impact Hub blockchain
- Multi-party controls govern the liquidity pool
- Strong authentication required for supplier applications
- Compliance with Article 6.2 ITMO regulations