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

Regional cost ledger

Shared service costs every municipality can check.

When several municipalities share a water system, transit or mutual aid, each depends on figures the others record. A ledger that each runs a node of keeps one record nobody can quietly change. It is a narrow case, and we will tell you when a shared database run by the regional district is enough.

Start a project See the example projects

// what matters here

What is different in this industry.

One record of usage

Each participant records its usage and call-outs, and every other participant sees the same entries as they are made.

The formula applied once

The agreed cost allocation is applied by the system, the same way for everyone, with the inputs visible.

A node for each municipality

Each municipality holds a copy, and auditors can be given read access to all of it.

When a database is enough

If the regional district already keeps the books and everyone trusts them, a well-audited database is cheaper. The ledger helps when trust is the problem.

// 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

Regional shared cost ledger

Hypothetical. Not a client, not a result.

// The problem

Several municipalities share the cost of a regional water system, transit and fire mutual aid, and each year they argue over whose figures are right.

// What we would build

A shared record of usage and cost allocations on a private permissioned ledger, with a node for each participating municipality, so the numbers behind each invoice are the same for all. If one municipality or the regional district is trusted by all to keep the books, a shared database is cheaper, and we will say so.

// What is in it

Usage, call-outs and costs recorded by each participant
The agreed allocation formula applied the same way for everyone
A node for each municipality, with read access for auditors
Invoices built from the record and sent to each finance system
Records kept to each municipality's retention schedule

// Stack

Next.js
Hyperledger Besu (private, permissioned)
PostgreSQL
AWS Canada

// estimate

Build: ≈ US$114,000 to US$174,000, delivered within 27 weeksCAD 161,700 to 247,400
Hosting: ≈ US$176 a monthCAD 250 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 4.9 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.9 weeks
Devnet: 2.9 to 4.9 weeks
Testing and fixes: 0.4 weeks
Testnet: 2.9 to 3.4 weeks
Retention rules checked with your records manager: 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

Finance system access from your vendor: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 32,340 to 49,480
Discovery 2.2%: CAD 3,557.40 to 5,442.80
Architecture 5.9%: CAD 9,540.30 to 14,596.60
Design approved 2.2%: CAD 3,557.40 to 5,442.80
Core features 6.6%: CAD 10,672.20 to 16,328.40
Full build 4.4%: CAD 7,114.80 to 10,885.60
Devnet 17.7%: CAD 28,620.90 to 43,789.80
Testing and fixes 2.2%: CAD 3,557.40 to 5,442.80
Testnet 11.8%: CAD 19,080.60 to 29,193.20
Retention rules checked with your records manager 8.7%: CAD 14,067.90 to 21,523.80
Launch 2.2%: CAD 3,557.40 to 5,442.80
Mainnet 6.1%: CAD 9,863.70 to 15,091.40
Holdback, 30 days after launch (10%): CAD 16,170 to 24,740

Start from this example

// questions

Questions we get about this.

Is there a cryptocurrency involved?

No. It is a private, permissioned network run by the municipalities, with no token and no public fees.

Who runs the network if a municipality leaves?

The remaining participants keep their nodes and the full record. A departing municipality keeps its own copy for its retention schedule.

Does it replace our finance system?

No. Invoices built from the shared record are sent to each municipality's finance system as they are today.

Back to the industry: Municipalities 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