CurveBlock
Platforms prevent the same renewable generation from being claimed by multiple shareholders or sold twice by assigning each unit of generation a unique certificate recorded in a recognised registry, linking that certificate to a specific digital share allocation on a shared ledger, and marking it as retired when claimed so it cannot be transferred again.
Why accurate tracking matters
Double counting of renewable generation undermines environmental integrity and investor confidence. When the same megawatt hour is sold to more than one buyer or claimed against multiple owners the result is misleading carbon accounting and weak incentives for further investment in clean generation. Platforms that manage pooled ownership must therefore treat certificates and generation credits as discrete scarce assets with strict controls on transfer and retirement.
Transparent tracking protects environmental integrity and investor confidence.
How certificates and credits are defined and issued
Environmental certificates and generation credits are records issued by recognised authorities or registries to represent the production of a defined quantity of renewable electricity. Each certificate typically corresponds to one unit of energy and carries metadata such as generation date site location and technology type. Registries issue unique identifiers for each certificate so that digital systems can reference the same single record when attributing ownership.
Unique identifiers from registries turn physical generation into accountable digital records.
Role of central registries and unique identifiers
Central registries are the authoritative source for whether a certificate exists who owns it and whether it has been retired. Platforms integrate with these registries to check certificate status during allocation transfer and retirement. Using the registry unique identifier as the common key means the platform and registry are always talking about the same certificate rather than separate internal records that could drift.
Where registries allow it the platform can request push notifications of changes so the shared record stays synchronised without manual reconciliation. If the registry supports certificates that must be retired at the point of claim the platform marks the certificate as retired in the registry and in its internal ledger so no further claims are possible.
Integration with an authoritative registry is the linchpin of single claim assurance.
Shared ledger accounting at the shareholder level
Within a pooled fund each digital share represents a proportionate claim on the fund assets including the environmental attributes allocated to the fund. To prevent double claims the platform maintains a ledger entry per certificate showing whether it is unallocated allocated or retired. When a certificate is allocated to a specific share or tranche of shares that allocation is recorded with a timestamp and an audit reference.
Because CurveBlock operates within a regulated environment and is approved for Gate 1 of the Bank of England and FCA Digital Securities Sandbox the platform aligns ledger records with registry records so that ownership on the platform mirrors ownership in the certificate registry. Sandbox approval is not full FCA authorisation.
Share level allocations recorded on a shared ledger keep claims tied to specific holdings.
Immutable audit trails and reconciliations
Immutable audit trails show who changed what and when. The platform writes a record of each allocation transfer retirement and reconciliation run. Regular reconciliation jobs compare platform records to registry records to surface discrepancies. Any mismatch triggers a hold on transfers for the certificates involved until human review resolves the issue.
Audit logs are essential in disputes and in compliance reviews because they show the chain of custody from issuance to retirement. External auditors can be given read only access to the audit trail to validate that certificates were not double sold or double claimed across shareholders.
Regular reconciliation and immutable audit logs are central to preventing accidental double counting.
Operational controls and transfer rules
Operational controls are applied at the moment of transfer or claim. Typical controls include a registry status check a platform side ownership check conflict detection and conditional holds while cross checks run. Transfers are rejected if the certificate is already retired or if the registry shows it belongs to another account.
The platform also enforces retirement on claim so that when an investor exercises a claim for environmental reporting the system retires the relevant certificate in the registry and flags the corresponding ledger entry to prevent any further transfers.
Operational rules at time of transfer reduce the risk of human error leading to double claims.
Third party verification and audit by independent bodies
Independent verification provides confidence that the platform controls are working. Auditors can attest that a sample of certificates were correctly allocated and retired and that reconciliations are performed on schedule. Independent attestation often references both registry entries and platform audit trails to provide a full picture.
Where the platform supports third party audits the results and remediation plans are summarised for investors so they can see how any issues were addressed. This strengthens both environmental credibility and trust in the ownership accounting process.
Independent verification links registry reality to platform records and builds investor trust.
Architectural choices that support reliable tracking
Technical design matters. Systems that separate the authoritative registry record from the platform ledger create a clear single source of truth for certificate existence and status. The platform can then use the registry unique identifier as a primary key in its ledger and maintain a running history of changes. For insights into the underlying client infrastructure see What is Hyperledger Besu and why CurveBlock uses it for digital shares which explains how an enterprise grade ledger supports reliable audit trails.
Integration patterns include synchronous checks at transfer asynchronous reconciliation and event driven updates from the registry. Where environmental claims support building level measurement see How environmental claims for energy positive buildings are measured and verified for the measurement frameworks that often feed certificate systems.
Architectural alignment between registry and platform is the technical basis for single claim assurance.
Practical example in a pooled fund
Imagine a solar farm issuing 100 certificates for a month of generation. The registry creates 100 unique identifiers. The platform receives those identifiers and records them in its ledger as available. When shares are allocated to investors the platform assigns specific certificates to those share allocations and records the assignment. If an investor wants to use their certificate in corporate reporting the platform retires the certificate at the registry and marks it retired in the ledger so no further investor can claim the same generation.
Assign allocate and retire is the practical sequence that prevents duplicate claims.
Governance controls and investor transparency
Good governance sets the rules for how certificates are allocated how disputes are handled and who can authorise retirements. Transparent reporting to investors summarises certificate holdings retirements and reconciliations. Clear procedures for exceptions help resolve problems without exposing the rest of the system to risk.
Clear governance and transparent reporting complete the technical and operational controls.
Frequently asked questions
How does the platform know a certificate is unique?
Registries issue unique identifiers for each certificate and the platform uses those identifiers as the single reference so duplication is detected by checking the identifier against registry records.
Can a certificate be sold more than once?
Not when the platform and registry integration is working correctly because a certificate is marked as allocated or retired and cannot be transferred again once retired.
What happens if registry and platform records disagree?
Reconciliation processes flag the discrepancy and the involved certificates are placed on hold until an investigation resolves the mismatch.
Who can audit certificate allocations and retirements?
Independent auditors and authorised compliance teams can review both registry entries and platform audit trails to verify the chain of custody and retirement actions.
Frequent questions focus on identifiers reconciliation and audit access.
General information about the CurveBlock platform. Not financial, legal or tax advice. Capital is at risk. The value of digital shares can fall as well as rise. Past performance is not a guide to future returns.
