Skip to content

Service · Blockchain

Blockchain Development Services

Commission us to decide whether a shared ledger genuinely solves your problem, choose the chain that fits, and build the system that records to it. You get a working product with a clear line between what lives on-chain and what stays in an ordinary database.

Chain selection argued in writing

On-chain and off-chain split documented

Node, indexer and key setup handed over

Deliverables

What a blockchain development engagement delivers.

01Delivered

A needs-a-chain assessment

A written answer to the first question: which parties must trust a shared record they do not individually control, and whether a signed audit log or a plain database would serve them just as well.

02Delivered

Network and architecture choice

A reasoned pick between a public layer 1, an Ethereum rollup, an app-specific chain or a permissioned network, covering fees, finality, data availability and who can read the records.

03Delivered

The on-chain core

The contracts or chaincode that hold state which must be tamper-evident, kept as small as the use case allows so that less code sits in an environment where fixes are expensive.

04Delivered

Off-chain services

APIs, event listeners, an indexed read model and the conventional database that store everything which does not need consensus, from user profiles to search indexes.

05Delivered

Operational runbook

RPC provider setup with a fallback, key custody for the deployer and admin roles, monitoring of chain events, and the steps for handling a reorg, a stuck transaction or an upgrade.

Early decisions

Technical decisions we settle early in blockchain development.

01Decided

Public, rollup or permissioned

Open settlement and composability point to a public chain or rollup; confidentiality between known members points to a permissioned network. We settle this before anyone writes a line of contract code.

02Decided

What data goes on-chain

Personal data does not belong on an immutable ledger. We usually anchor hashes or commitments on-chain and keep the underlying records off-chain where they can be corrected or erased.

03Decided

Who pays gas

Users holding native tokens, a relayer sponsoring transactions, or account abstraction with a paymaster. The answer shapes onboarding more than almost any other choice.

04Decided

Finality and confirmations

How many blocks, or which finality signal, the system waits for before treating an event as settled, and how downstream services behave while a transaction is still pending.

05Decided

Upgrade and admin powers

Immutable contracts, proxies behind a multisig, or upgrades gated by a timelock. Each option trades flexibility against how much users must trust the operator.

06Decided

Indexing approach

A hosted subgraph, a self-run indexer, or direct log processing into Postgres, chosen by query complexity and how quickly the read model must catch up after a block.

Engagement

How a blockchain development engagement runs.

  1. 01Phase 1

    Trust and threat mapping

    We list every party, what each must be able to verify, and who might try to cheat. This produces the case for or against a chain and the first draft of the trust model.

  2. 02Phase 2

    Chain and boundary design

    We choose the network, sketch state and events, and draw the line between contract logic and backend logic, then test the design against fee and throughput estimates on a testnet.

  3. 03Phase 3

    Contract and service build

    Contracts, indexer and APIs are built together against a local fork, so the read model, the transaction flow and the failure handling are exercised before any public deployment.

  4. 04Phase 4

    Staged mainnet rollout

    A testnet pilot, an external review where risk calls for one, then mainnet deployment with caps or allowlists that are lifted once monitoring shows the system behaving as designed.

Fit

When a blockchain build is the right choice.

01Good fit

Several organisations share one record

Suppliers, auditors or partners need the same history and none of them should be able to rewrite it alone.

02Good fit

Assets must move without your servers

Users should be able to hold or transfer value directly, even if your company changes its terms or goes offline.

03Good fit

You want independent verifiability

Regulators, customers or counterparties should be able to check a claim against public data rather than take your word for it.

Start with the trust problem, not the technology

Most blockchain proposals fail a simple test: if one company already runs the system and everyone accepts its records, a chain adds cost without adding trust. The useful cases involve parties who do not want to depend on one operator, or assets that must remain under their owners’ control.

That is why the first deliverable is an argument, not code. We write down who needs to verify what, and only then choose a network.

Keep the chain small

Every line deployed to a contract is hard to patch and costs fees to execute. Good architecture pushes search, display logic, notifications and personal data into ordinary services, and leaves the ledger with the few state transitions that genuinely need consensus.

The off-chain half decides the user experience

Users never query a node directly. They see an API backed by an indexer that has turned contract events into tables, and they wait on transactions that a backend is tracking through pending, included and final states. Getting that pipeline right, including reorg handling, is most of the engineering effort.

We treat RPC providers as unreliable dependencies, run at least two, and alert when the indexer falls behind the chain head.

Operating keys is an ongoing job

Admin and deployer keys are the most valuable secrets in the system. We put them behind multisig wallets or hardware-backed signing, separate them by role, and document who can rotate them and how.

FAQ

Questions to resolve before the build.

01Will you tell us if we do not need a blockchain?

Yes. The opening assessment exists for exactly that reason. If a single trusted operator is acceptable to everyone involved, a signed, append-only database is usually simpler and we will say so in writing.

02Which chains do you build on?

Mostly Ethereum and EVM-compatible rollups and sidechains, plus permissioned networks such as Hyperledger Fabric and Besu. We will discuss other ecosystems where the use case points to them, and say plainly where our depth is thinner.

03How do you handle personal data on an immutable ledger?

We keep it off the chain. The ledger stores a hash, a reference or a commitment, and the personal record lives in a store that supports correction and deletion, which matters for data protection obligations.

04Do you issue tokens as part of this service?

We can build token contracts, but the decision to issue one has legal and tax consequences in most jurisdictions. We expect you to take your own legal advice on that before launch.

Primary sources

References behind this page

Dated official documentation, standards, and research that support the factual claims on this page.

  1. 01
  2. 02

How to read this page

Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.

Next decision

Turn the brief into an accepted product scope.

Define outcomes, constraints, evidence, rights and handover before delivery begins.

Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.