DEMO DATA— Fictional procurement records are used to demonstrate the OpenContract workflow.
Explore
Find procurement records, organizations and contracts.
Understand
Follow the lifecycle from tender through award, contract, amendments and payments.
Verify
Check published document fingerprints against registered records.
Investigate
Review explainable signals when procurement data deserves closer attention.
Ask
Use the AI analyst to ask questions about the available evidence.
5
Procurement processes
1
Active tenders
₵131.2M
Tracked contract value
4
Signals requiring review
Follow the full lifecycle
Every public procurement creates a chain of events. OpenContract makes that chain visible and verifiable.
Verify any public document
Upload a document and check whether it matches the cryptographic fingerprint registered for an OpenContract record. If even a single byte changed, verification will show a mismatch.
A matching fingerprint confirms the file is identical to the registered version. It does not verify the contents are truthful.
The uploaded file matches the registered document fingerprint.
- SHA-256
- a3f2…8c1d
- Registered
- 18 May 2026
- Blockchain
- ✓ Confirmed
The uploaded file does not match the registered fingerprint. This may mean the file has been modified.
- Network
- Base Sepolia
- Transaction
- 0x8a4f…3c2d (Demo)
- Block
- 14,893,241
- Anchored
- 24 Sep 2026
Simulated demo anchor on Base Sepolia. Demonstrates how cryptographic SHA-256 fingerprints are anchored to OpenContractRegistry.sol at the time of publication.
Independent verification layer
Key procurement events and document fingerprints are anchored to an EVM blockchain. This creates a tamper-evident public record that can be independently verified without relying on OpenContract servers.
- Events are anchored, not full documents
- Document hashes are anchored — not document contents
- Blockchain does not verify truthfulness of submitted data
- Anyone can independently verify the anchored events
Structured review signals
OpenContract's integrity engine applies deterministic rules to surface procurement records that may warrant additional attention. These are signals for review — not findings of wrongdoing.
Single bidder
A tender received only one recorded bid, which may reduce competitive pressure.
Significant amendment
Contract value changed by more than 15% from the original awarded amount.
Delayed implementation
Recorded milestone dates indicate the project is significantly behind schedule.
Missing update
An expected procurement stage has no corresponding public record.
Supplier concentration
A supplier appears across an unusually high proportion of recorded procurements.