labs@atheron:~/industries/energy/blockchains$ launch chain --validators

Renewable certificates

A private ledger so no megawatt-hour is counted twice.

Renewable attributes are a classic double-counting risk: several companies, one megawatt-hour and a spreadsheet each. A private ledger fits when generators, a retailer and a verifier all write to the record. Where an official registry is the record of title, we build alongside it, not instead of it.

Start a project See the example projects

// what matters here

What is different in this industry.

Issued from the meter, not a form

Certificates are created from revenue meter data the verifier confirms, so what is issued matches what was generated.

Assigned or retired once

A certificate cannot be assigned to two customers or retired twice; the ledger refuses the second attempt.

Statements customers can check

Each customer statement lists certificate numbers, generators and periods that can be checked against the ledger.

Alongside the official registry

Where a tracking registry applies, the ledger reconciles with it rather than competing with it.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb appBlockchain

Renewable certificate ledger

Hypothetical. Not a client, not a result.

// The problem

An energy retailer buys renewable output from several independent generators and resells the attributes to corporate customers, and tracking it in spreadsheets means nobody can prove a certificate was not sold twice.

// What we would build

A private permissioned ledger where generators, the retailer and an independent verifier each run a node: metered output becomes certificates, each certificate is assigned or retired once, and customers get a statement they can check. Where an official tracking registry covers your market it stays the record of title, and this ledger handles the contracts and matching around it; if one party is trusted by all, a database does the same for less.

// What is in it

Metered generation imported from revenue meters and turned into certificates
Each certificate assigned or retired once, with its history kept
A verifier node that confirms meter data before certificates are issued
Customer statements with generator, period and certificate numbers
Reconciliation with the official registry where one applies
Reports for customers' emissions disclosures

// Stack

Hyperledger Besu (private, permissioned)
Solidity
Next.js
PostgreSQL
Microsoft Azure

// estimate

Build: ≈ US$108,000 to US$165,000, delivered within 23 weeksCAD 153,300 to 234,400
Hosting: ≈ US$751 a monthCAD 1,070 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Architecture: 0.4 weeks
Design approved: 2.9 to 5.4 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.4 weeks
Devnet: 2.4 to 3.9 weeks
Testing and fixes: 0.4 weeks
Testnet: 2.9 to 3.4 weeks
Launch: 0.9 to 1.4 weeks
Mainnet: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

Read-only access approved by your OT team: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 30,660 to 46,880
Discovery 2.5%: CAD 3,832.50 to 5,860.00
Architecture 6.7%: CAD 10,271.10 to 15,704.80
Design approved 2.5%: CAD 3,832.50 to 5,860.00
Core features 7.5%: CAD 11,497.50 to 17,580.00
Full build 5%: CAD 7,665 to 11,720
Devnet 20.2%: CAD 30,966.60 to 47,348.80
Testing and fixes 2.5%: CAD 3,832.50 to 5,860.00
Testnet 13.4%: CAD 20,542.20 to 31,409.60
Launch 2.5%: CAD 3,832.50 to 5,860.00
Mainnet 7.2%: CAD 11,037.60 to 16,876.80
Holdback, 30 days after launch (10%): CAD 15,330 to 23,440

Start from this example

// questions

Questions we get about this.

Does this replace an official registry?

No. Where an official registry, such as M-RETS or the North American Renewables Registry, is the record of title for your market, it stays so. This ledger manages the contracts and matching around it and reconciles with the registry.

Who runs the nodes of a certificate ledger?

Each generator, the retailer and the verifier run one, or use a node hosted for them with the trade-off explained.

Is there a token to buy?

No. Certificates are records on a permissioned chain with no tradable token and no public fees.

Back to the industry: Energy and utilities About the service: Private and public blockchains

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call