Open Contracting Data Standard (OCDS) on Blockchain
OpenGovChain's procurement module implements the Open Contracting Data Standard — the global benchmark for publishing structured, comparable procurement data — directly on an immutable blockchain ledger.
Every stage of the contracting process, from planning through implementation, is captured as on-chain transactions that anyone can query and verify. No data can be retroactively altered, ensuring the highest level of accountability for public spending.
The Open Contracting Data Standard (OCDS) provides a structured schema for publishing data about every stage of the public contracting process. Developed by the Open Contracting Partnership, it is used by governments and organizations in over 30 countries to make procurement data accessible, comparable, and actionable.
OCDS defines a common vocabulary for procurement data — including planning, tender, award, contract, and implementation stages — enabling cross-border analysis, anti-corruption monitoring, and better value for money in public spending.
The Full Contracting Lifecycle On-Chain
Each stage of the contracting process is captured as a blockchain transaction, creating an immutable record from start to finish.
Budget allocation, rationale, and procurement planning documents are published on-chain.
Msg/CreateProcessTender details including items, submission deadlines, and eligibility criteria are recorded.
Msg/PublishTenderAward decisions with supplier details, evaluation results, and contract values.
Msg/SubmitAwardSigned contract details, terms, milestones, and delivery schedules committed to the chain.
Msg/SignContractMilestones, transactions, and delivery updates tracked through to completion.
Msg/UpdateImplementationEvery stage is linked by a single identifier
OCID: ocds-abc123-procurement-001
Planning
- Budget allocation
- Procurement rationale
- Timeline estimates
Tender
- Items & quantities
- Submission deadline
- Procurement method
- Eligibility criteria
Award
- Selected supplier(s)
- Evaluation results
- Award value
Contract
- Signed terms
- Milestones
- Delivery schedule
- Contract value
Implementation
- Milestone progress
- Financial transactions
- Delivery documents
Each stage generates an immutable OCDS release stored on-chain. Releases are compiled into a single record per contracting process, providing a complete audit trail that can never be altered or deleted.
Contracting Process
The core unit of OCDS data. Each process is identified by a unique OCID (Open Contracting Identifier) and contains the compiled release that aggregates all stages.
Release
An individual update to a contracting process. Each release captures one or more changes (planning, tender, award, contract, implementation) and is tagged accordingly.
Entity Registry
Organizations participating in procurement can be registered on-chain with verified identifiers. This creates a reusable registry of procuring entities and suppliers.
Document Verification
Procurement documents (bid notices, evaluation reports, contracts) are stored on IPFS with content hashes recorded on-chain for tamper-proof verification.
/govchain/procurement/v1/processList all contracting processes
/govchain/procurement/v1/process/{ocid}Get a specific contracting process by its OCID
/govchain/procurement/v1/releases/{ocid}Get all releases for a contracting process
/govchain/procurement/v1/ocds/records/{ocid}Get OCDS-compliant record package for a process
/govchain/procurement/v1/ocds/releases/{ocid}Get OCDS-compliant release package for a process
/govchain/procurement/v1/tendersList all published tenders
/govchain/procurement/v1/entityList all registered entities
/govchain/procurement/v1/entity/{entity_id}Get a specific registered entity
Initiate a new contracting process with planning data, buyer information, and a unique OCID.
Publish tender details including items, submission method, value, and procurement method.
Record an award decision with selected suppliers, evaluation details, and award value.
Commit a signed contract with terms, milestones, value, and delivery schedule.
Update contract implementation with milestones, transactions, and delivery documents.
Submit a full OCDS release for any stage, enabling maximum flexibility.
Register a new organization (buyer, supplier, etc.) on the on-chain entity registry.
Update an existing registered entity's organization details.
allowed_ocid_prefixesApproved OCID prefixes (e.g., ocds-abc123) that can be used for contracting processes. See OCDS identifier guidance.
default_currencyDefault currency code (e.g., PHP) used for monetary values when not specified.
public_bidding_thresholdMinimum value requiring public competitive bidding procedures.
alternative_method_thresholdMaximum value allowed for alternative procurement methods.
min_tenderers_openMinimum number of tenderers required for open procurement methods.
require_entity_verificationWhether entities must be verified before they can participate in processes.
OCDS Schema Reference
Complete schema documentation including release, record, and all component schemas.
OCDS Release Schema
The release schema — the primary unit of OCDS data describing one update to a contracting process.
OCDS Codelists
Standardized code values for procurement methods, tender statuses, award criteria, and more.
OCDS Identifiers
Guidance on OCIDs (Open Contracting Identifiers) and organization identifier schemes.
Contracting Process Overview
How OCDS maps to the five stages of the contracting process: planning through implementation.
OCDS Guidance & Best Practices
Implementation guidance, mapping templates, and best practices for publishers.
Open Contracting Partnership
The global organization that stewards OCDS and supports open contracting reforms worldwide.
Organization Identifier Guide
The reference list of organization identifier schemes used in OCDS for buyer and supplier IDs.