OpenGovChain: An Open National Blockchain for Fiscal Transparency

1.Executive Summary

OpenGovChain is a free, open-source, tokenless blockchain designed to make government fiscal data a permanent public good. Built on the Cosmos SDK with CometBFT consensus, the network is operated by volunteer validators and requires no tokens to participate.

The platform implements three complementary modules that, together, provide end-to-end traceability of public money:

By anchoring fiscal data to an immutable, decentralized ledger, OpenGovChain eliminates the possibility of retroactive alteration, provides cryptographic proof of publication, and makes government spending verifiable by any citizen with an internet connection.

2.The Transparency Gap

The Philippines ranks 15th globally and 1st in Asia on the Open Budget Index (OBI score: 75/100, 2023). The foundations for transparency exist — the Transparency Seal, PhilGEPS, Open Data Philippines, and the Unified Account Code Structure (UACS) are all operational. Yet significant gaps remain:

• Fragmented systems. Budget preparation (eBudget), treasury operations (eMDS), accounting (eNGAS), and procurement (PhilGEPS) run as isolated silos. Tracing a single peso from appropriation through procurement to physical delivery requires manually cross-referencing multiple databases.
• Mutable records. Government portals are controlled by the agencies they report on. Data can be updated, unpublished, or quietly corrected without a public audit trail.
• Delayed accountability. COA Annual Audit Reports are typically published 12–18 months after the fiscal year closes, limiting the ability of citizens and oversight bodies to intervene in real time.
• No machine-readable lifecycle. While individual budget documents (NEP, GAA) are published as PDFs and spreadsheets, there is no structured, machine-readable data format that tracks a budget line from proposal through legislation, allotment, obligation, and disbursement.
• Opacity in the bicameral process. The Bicameral Conference Committee stage of budget legislation — where the House and Senate versions of the General Appropriations Bill are reconciled — has historically operated with limited public visibility.

OpenGovChain addresses these gaps not by replacing existing government systems, but by providing an independent, immutable layer that anchors their outputs. Agencies continue to use their existing tools; the blockchain serves as a permanent public record of what was published, when, and by whom.

3.Vision: A True National Blockchain Infrastructure

OpenGovChain is not a portal, a dashboard, or a reporting tool. It is infrastructure — a shared, neutral, append-only ledger that any government agency, civil society organization, media outlet, or citizen can read from and, with proper authorization, write to.

The end-state is a system where:

4.Design Principles

5.Architecture

OpenGovChain is built on the Cosmos SDK, an open-source framework for building application-specific blockchains. The key components are:

6.Module I: Public Procurement (OCDS)

The procurement module records the full public procurement lifecycle on-chain, following the OCDS schema. Every state transition is published as an immutable release, tagged with the lifecycle stage.

Key Data Structures

• Release — An immutable snapshot at a point in time, tagged with one or more lifecycle stages (planning, tender, award, contract, implementation).
• Contracting Process — The compiled view aggregating all releases for a single OCID. Updated automatically on each new release.
• Entity Registry — On-chain registration of organizations (buyers, procuring entities, suppliers) with org-id.guide identifiers.

Authorization

The creator of a contracting process becomes its owner. Only the owner or addresses explicitly added to the authorized_publishers list can publish subsequent releases. This ensures that only authorized agency personnel can update procurement records, while the public can freely read all data.

OCDS Compliance

The module produces standard OCDS Release Packages and Record Packages via dedicated REST endpoints, ensuring compatibility with the global ecosystem of OCDS tools, validators, and analytics platforms.

7.Module II: Infrastructure Projects (OC4IDS)

The infrastructure module tracks physical infrastructure projects from identification through completion, linking them to the procurement processes that fund them.

Key Capabilities

• Geographic location with GeoJSON geometry (Point, LineString, Polygon) and Philippine Standard Geographic Code (PSGC) gazetteer references.
• Quantitative metrics with timestamped observations for tracking physical and financial progress over time.
• Document attachments with optional IPFS storage for EIAs, progress reports, and completion certificates.
• Procurement linkage — each project can reference one or more OCDS contracting processes by OCID, with embedded tender and contract summaries.
• Filterable queries by sector, status, and region for public monitoring dashboards.

8.Module III: National Budget (NEP → GAA)

The proposed National Budget Module closes the most critical gap in Philippine fiscal transparency: a structured, machine-readable, immutable record of how public money moves through the four phases of the budget cycle.

The Philippine Budget Cycle

The national budget follows four overlapping phases, each producing key documents that the module aims to anchor on-chain:

UACS as the Classification Backbone

The Unified Account Code Structure (UACS) is the Philippine government's harmonized classification system across budgeting, treasury, and accounting. Every financial transaction is encoded using five code segments:

UACS codes are the natural bridge between the budget module and the procurement module. A UACS-coded budget line in the GAA can be traced to the SARO that releases it, the procurement process that spends it (via OCDS planning.budget), and the infrastructure project that delivers it (via OC4IDS).

Proposed On-Chain Data Model

The budget module would introduce the following on-chain record types, each published as immutable, timestamped entries:

The Data Flow On-Chain

Each transition is a separate on-chain transaction, signed by the authorized publisher (DBM for allotments, the implementing agency for obligations, COA for audit findings). The chain records who published what, when, at which block height, and with which transaction hash.

9.End-to-End Traceability

The three modules are designed to interconnect. A single infrastructure project can be traced across all three:

This end-to-end chain means that any citizen, journalist, or oversight body can start from a GAA line item and follow the money all the way to the physical road being built — or start from a construction site and trace backward to the legislative appropriation that funded it. Every link in the chain is on-chain, timestamped, and immutable.

10.Network Governance & Participation

OpenGovChain is operated by a volunteer validator network with no economic prerequisites. Governance follows the Cosmos SDK x/gov module pattern:

• Parameter changes (e.g., adjusting OCID prefixes, maximum release sizes, or budget module thresholds) require a governance proposal approved by validators.
• Module upgrades follow the standard Cosmos SDK upgrade mechanism with coordinated halt-height across validators.
• Validator admission is open. Any individual or organization can join by running a node and creating a validator transaction. There are no minimum stake requirements on the tokenless network.
• Data publishing is permissioned by module. Each module defines who can write (e.g., registered entities for procurement, project owners for infrastructure, designated agencies for budget). Reading is always public and free.

Tiered Participation

11.Roadmap

12.Get Involved

OpenGovChain is built by volunteers who believe government data should be a permanent, verifiable public good. There are several ways to contribute: