If public money is committed to a project, an interested citizen should be able to follow what happened next. What was approved? What changed? Who authorised the change? Was the work delivered?
Those are reasonable questions. Answering them can still require moving between documents that use different names, cover different periods and explain only part of the process. Better public information would make that work easier for everyone, including the people administering the programme.
This is one of the blockchain use cases I find most worthwhile. A well-designed shared ledger could give spending decisions a durable, traceable history. The ambition should be practical: help people inspect the record without asking them to take the latest version entirely on trust.
Canada has already explored the idea
The National Research Council’s 2018–19 results report describes a public-blockchain prototype for proactive disclosure of contract agreements through NRC IRAP. That was an experiment, not proof that Canada’s public spending already operates on a blockchain. It is nevertheless a useful Canadian precedent for testing the technology against a concrete administrative need.
The broader interest extends beyond Canada. An August 2026 report in the Philippine Daily Tribune describes advocacy for a blockchain-based national budget system. A proposed system and a successful implementation are different things, but the underlying public-interest question travels well.
Make the spending journey legible
I would begin with a limited programme and a plain-language public interface. Give each project a consistent identifier. Connect the original approval, the contract, later amendments and published delivery milestones. Make it possible to see a change without losing sight of the version that came before it.
A blockchain could help make later alteration detectable by anchoring records or their cryptographic fingerprints in a shared history. That does not require every invoice, personal detail or commercially sensitive document to be placed permanently on a public network. Disclosure rules and access controls need to be designed deliberately.
The Open Contracting Data Standard already provides a common model for disclosing information across the contracting process. That kind of structured, usable information is essential. A ledger adds little value if the records remain impossible to interpret or compare.
The record still needs responsible people
A blockchain can help show that a recorded entry has not been quietly rewritten. It cannot establish that a road was built properly, that an invoice was honest or that an original claim was accurate. Those questions still need evidence, inspection and accountable institutions.
This distinction makes the case for the technology stronger. It gives a pilot a defined job instead of asking it to solve every problem in public administration. A team can evaluate whether the new record makes reconciliation easier, exposes missing information sooner or reduces the effort required for an independent review.
I would want corrections to remain possible and understandable. Mistakes should be amended through a visible process, with a reason and an authorised person attached. A dependable history includes the explanation of a correction; it does not depend on pretending the first entry was perfect.
A public-service use case worth developing
For Canada, a sensible starting point might be one grants programme or a defined category of procurement. Measure the cost of publishing and maintaining the information. Ask auditors, public servants and citizens whether the result helps them answer their questions. Compare it with a well-run conventional database rather than a deliberately weak alternative.
That is an ambitious Web3 project in a useful sense. It connects technical infrastructure to an ordinary democratic expectation: public decisions should be open to informed scrutiny. If the technology makes that expectation easier to meet, the value will be visible in the work, long after the novelty of the terminology has passed.