ZECH
Discuss an AI project
View all AI services →
View all services →
Automation & Data
Software
Specialist Services
View all solutions →
Knowledge work
Operations
Growth
Decision support
View all industries →
View all insights →
About ZECH →
Company
Get in touch
Contact
Specialist Services · Specialist

Blockchain engineering for the specific cases where a shared ledger is the right tool.

We build and review smart contracts, permissioned ledgers and the applications around them — and we start by checking whether a conventional database would serve you better.

Discuss a ledger project
What we deliver
  • Fit assessment
  • Smart contract development
  • Permissioned ledger setup
  • Application and wallet integration
  • Pre-audit review support
Tools & platforms
SolidityHardhat and FoundryOpenZeppelin ContractsHyperledger FabricEthers.js

Where this helps

Several organizations, no shared record
Suppliers, partners or members each keep their own copy of the same transactions and reconcile by spreadsheet. Disputes come down to whose records are right.
A smart contract that cannot be changed later
Code deployed on a public chain handles real value and cannot simply be patched. Logic errors and missing access controls are expensive once live.
A blockchain project without a reason for one
The idea started with the technology rather than the problem, and nobody has written down which party needs to trust which record, or why.

What we deliver

01
Fit assessment
A short written analysis of who writes to the record, who needs to verify it, and whether a ledger, a signed audit log or an ordinary database meets the need.
02
Smart contract development
Contracts written with established libraries, full test coverage, documented upgrade and pause mechanisms, and gas cost analysis.
03
Permissioned ledger setup
Network design, node roles, identity and access for private networks shared between known organizations.
04
Application and wallet integration
The web or back-end application that reads and writes to the chain, handles keys safely and indexes events for search and reporting.
05
Pre-audit review support
Internal review, static analysis and test hardening before an independent audit, and help resolving the auditor's findings.

How it works

  1. 01

    Problem framing

    We identify the parties, the record they share and the trust problem, and agree whether a ledger is justified before any design.

  2. 02

    Architecture

    Public or permissioned network, on-chain versus off-chain data, key custody and upgrade approach are decided and documented.

  3. 03

    Build and test

    Contracts and application are developed with unit, integration and property-based tests on a test network.

  4. 04

    Review and audit

    Code goes through internal review and static analysis, then to an independent auditor you choose, with fixes tracked to closure.

  5. 05

    Deploy and monitor

    Staged deployment with monitoring of contract events, key operations and failed transactions.

Design decisions we make with you

  • Public or permissioned

    A public chain suits open participation and settlement in digital assets; a permissioned network suits known organizations that need a shared record and privacy.

  • What goes on-chain

    Personal and commercially sensitive data stays off-chain. We usually store hashes or references on the ledger and keep the data in systems that support deletion.

  • Key management

    Who holds signing keys, how they are stored, and how they are rotated or recovered is designed up front — lost keys cannot be reset.

  • Upgradeability

    Upgradeable contracts are more flexible but add trust assumptions. We document who can upgrade, under what process, and how users are told.

Applications

Supply chain provenance
Recording custody handoffs and certificates between suppliers, carriers and buyers, so each party can verify a shipment's history.
Tokenized asset and settlement records
Issuance, transfer restrictions and settlement records for digital assets, built around the institution's own compliance checks.
Tamper-evident audit logs
Anchoring hashes of internal records to a ledger so later changes can be detected without publishing the records themselves.

Related capabilities

Services

Questions buyers ask

Often not. If one organization controls the data and others trust it, a conventional database with audit logging is simpler and cheaper. A ledger earns its place when several parties write to the same record and none should control it alone.

We do internal review and prepare code for audit, but we recommend an independent audit firm for any contract that will hold significant value. See our approach to trust and security.

We build the technical components for asset and settlement use cases. We do not advise on or run token sales, and legal and regulatory questions stay with your counsel.

Discuss this capability with an engineer.

Tell us about the workflow or product. We reply with questions, a suggested first step and who would work on it.

Discuss a ledger project