Software · Developer and integration
Blockchain and ledgers
Shared, tamper-evident records for organisations that must trust the same data without one owner.
Most problems do not need a blockchain, and we will say so when a database with signed audit logs would do. Where several organisations must share one record that none of them controls, we build permissioned ledgers on Hyperledger Fabric or smart contracts on Ethereum-compatible networks. Contracts are kept small, tested thoroughly and designed to fail safely.
What we build
- Supply chain provenance records shared between producers, carriers and buyers
- Permissioned ledgers on Hyperledger Fabric with private channels per partner
- Smart contracts in Solidity, tested with Foundry and built on OpenZeppelin libraries
- Document anchoring that proves a certificate or contract existed unchanged
- Key custody integrations with hardware-backed signing and multi-signature approval
- Indexers and dashboards that turn on-chain events into readable reports
DemoInteractive · sample data
Try it live.
A working sample with made-up data. It runs in your browser; nothing is sent anywhere.
| Batch | Product | Current holder | Anchored | Stage |
|---|---|---|---|---|
| CF-0412 | Arabica, washed | Hillview Estate | 2026-10-02 | Verified |
| CF-0413 | Arabica, natural | Bluegate Roasters | 2026-10-04 | Received |
| CF-0419 | Robusta cherry | Coastline Freight | 2026-10-09 | Shipped |
| CF-0421 | Arabica, washed | Coastline Freight | 2026-10-12 | Shipped |
What it does well
Honest fit check
We test the idea against a plain database first and recommend it when it wins.
Tested contracts
Unit, fuzz and invariant tests run on every change with Foundry.
Upgrade plans
Contract upgrades and pauses follow written, multi-signature procedures.
Private by design
Personal data stays off-chain; the ledger holds only hashes and references.
Readable history
Indexers turn raw events into reports that auditors and partners can follow.
Key safety
Signing keys live in HSMs or custody services, never on a developer laptop.
Questions
Do we actually need a blockchain?
Often not. If one organisation runs the system and the others trust it, a database with signed, append-only audit logs is cheaper and faster. A shared ledger helps when several parties write to the same record, none should control it alone, and each needs to verify the history independently.
Public or permissioned chain?
Permissioned ledgers such as Hyperledger Fabric suit consortiums that know their members and need private data. Public networks suit records anyone should be able to verify, such as certificate anchoring. Many designs anchor hashes publicly while keeping the data itself private.
How do you make smart contracts safe?
We keep contracts small, reuse audited OpenZeppelin components, and test with unit, fuzz and invariant tests. Before launch we recommend an independent review by a separate security firm, plus pause controls and multi-signature administration so any problem can be contained.