Blockchain and Web3
Permissioned ledgers, smart contracts and identity systems for organisations that need shared records, provable history and rules nobody can quietly rewrite.
A record several organisations share, that none of them can quietly change afterwards.
That is the whole proposition, and it is worth a great deal in supply chains, certificate registries, escrow arrangements and any process where the audit currently consists of asking each party for their version. Acaiberry builds permissioned ledgers, smart contracts and identity systems for organisations that need provable history, not a token.
Try it - edit any record below
Change one line and every block after it fails
Simplified hash, for illustration.
Trust that does not depend on trusting anyone
In most systems, a record is true because the organisation holding the database says so. That works until the parties disagree, the auditor arrives, or the organisation that holds the database is one of the parties with something to gain. A shared ledger changes the question from who do we believe to what can be proved.
History that cannot be edited
Every entry is linked to the one before it. Altering an old record invalidates everything that followed, which is why disputes get shorter and audits get cheaper.
Rules that execute themselves
Payment on delivery, release from escrow, expiry of a licence. Conditions written into the contract run the same way for every participant, without a coordinator.
Proof without exposure
A counterparty can verify a certificate, a shipment or an entitlement without being handed the underlying records, which is often the whole reason a process is slow today.
Four families of solution
Different problems, one underlying property: a record that several parties can rely on without relying on each other.
Digital identity
Credentials that can be checked in seconds and cannot be forged, held by the person they belong to.
- Identity management
- Credential verification
- Verifiable certificates
- Self-sovereign identity
- Access control
- Consent and revocation
Asset tokenisation
Ownership and entitlement represented digitally, transferable under rules that hold whoever is holding it.
- Real estate and fractional ownership
- Supply chain instruments
- Loyalty and reward programmes
- Digital assets
- Certificates and licences
- Intellectual property rights
Supply chain transparency
A shared record of what happened to a product, contributed by each party as it passes through their hands.
- Product tracking
- Provenance and origin
- Compliance evidence
- Food safety and cold chain
- Logistics handover
- Anti-counterfeiting
Web3 development
For products that need to work with public networks and the wallets your users already hold.
- Decentralised applications
- Wallet integration
- DAO and governance platforms
- NFT infrastructure
- Web3 APIs and indexing
- Cross-chain interoperability
Code that moves money should be written like it
A deployed contract is difficult to change and public in its effects. We treat contract development the way a payments team treats settlement code: specified, tested against adversarial cases, reviewed line by line and audited before anything holds value.
What we engineer into the contract layer
Business process automation
Multi-party workflows where each step releases the next automatically, replacing the emails and reconciliation that currently hold the process together.
Contract logic
Commercial terms translated into deterministic rules, with the ambiguous clauses flagged back to legal before they become code.
Escrow and settlement
Value held until agreed conditions are met, with defined release, refund and dispute paths rather than a single irreversible transfer.
Compliance automation
Participant checks, transfer restrictions and reporting obligations enforced by the contract itself, so a non-compliant transaction cannot execute.
Auditable transactions
Every action timestamped, attributed and permanent, giving auditors a single source they can verify independently instead of a report you prepared.
Upgrade paths
Proxy patterns, migration plans and emergency controls designed up front, because the alternative to a plan is a redeployment under pressure.
There is no support line for a lost key
Most of what goes wrong in this field is not cryptography failing. It is a contract with an unchecked assumption, a private key on someone's laptop, or an integration that trusted the wrong input. Those are the failures we design against.
Smart contract audits
Line-by-line review against known attack classes, with automated analysis, adversarial testing and a written report you can show a counterparty.
Security reviews
Threat modelling across the whole system: nodes, APIs, front ends and the integrations either side, because the ledger is rarely the weakest part.
Key management
Hardware security modules, multi-signature approval, recovery procedures and a custody model your board can actually sign off on.
Identity protection
Personal data kept off the ledger, with proofs and references stored on-chain so privacy law and permanence stop being in conflict.
Regulatory compliance
Designs that account for data protection, financial regulation and the rules your sector reports under, including the right to erase what cannot be deleted.
Operational monitoring
Node health, transaction anomalies and contract activity watched continuously, with an incident path defined before you need it.
Networks with a membership list
Public chains are open to anyone and priced accordingly. Almost every enterprise problem is better served by a network where participants are known, permissions are explicit and the data stays among the organisations it concerns.
Step 01
Private blockchain
A ledger operated by one organisation across its own divisions, systems or jurisdictions, with tamper-evident history and no external dependency.
- Internal network
- Tamper-evident history
- No external dependency
Sectors where the record is the product
Finance
Trade finance documentation, settlement, escrow, syndicated lending records, audit-ready transaction history.
Healthcare
Consent management, credential verification for practitioners, pharmaceutical provenance, clinical trial records.
Education
Tamper-proof degrees and transcripts that employers can verify instantly, without contacting the institution.
Government
Land and title registries, licence issuance, procurement transparency, benefit distribution with an auditable trail.
Supply chain
Multi-party handover records, origin claims that survive scrutiny, customs documentation, recall traceability.
Retail
Authenticity for premium goods, loyalty points that move between partners, warranty and returns history.
NGOs
Donor fund traceability from pledge to disbursement, beneficiary records without duplication, verifiable impact reporting.
Agriculture
Origin and organic certification, cooperative payment records, export documentation for buyers who demand proof.
Your use case. Not listed?
Bring the problem. We start with a readiness assessment before promising anything.
Tell us moreHow we deliver
Seven stages, and the first one can end the project
Deployed contracts are hard to unwind and consortium agreements are harder. We front-load the decisions that are expensive to reverse.
Use case validation
Who the parties are, what they disagree about, and whether a shared ledger solves it better than a database. A short, honest report either way.
PARTY MAP • HONEST REPORT
WHAT CHANGES
The argument about whose record is right ends
Common questions
Before you get in touch
Bring the process that keeps going to arbitration
Tell us which record gets disputed, who the parties are and what verification currently costs you in time. We will come back with a design, a cost, and an honest answer about whether this technology is the right one for it.
Book a use case review