All services

06 · Blockchain and Web3

Most businesses do not need a blockchain. Some genuinely do.

Ownership that has to be provable, payouts split between many parties, provenance that must survive the company that recorded it — these are ledger problems. Almost everything else that gets pitched as Web3 is a database with worse ergonomics.

Start a Conversation

How it works

We build the on-chain parts of products where the ledger is doing real work: wallet authentication, token and payout mechanics, and the accounting that has to reconcile between what happened on chain and what the business records off it.

On Zirkels that meant treating monetisation as a first-class object rather than a feature added late — earnings, articles and authors modelled together, so a payout is a consequence of the content model instead of a separate system reconciling against it. That reconciliation is where most Web3 products quietly fall over.

Dennis wrote a book about the space in 2019, which mostly taught us how much of it is theatre. We will say plainly when a conventional system would serve you better, and we would rather lose the work than build a chain you do not need.

What you get

Concrete things, not a retainer.

  • Wallet-based sign-in

    Authentication that works for people who have never held a wallet before.

  • Payout mechanics

    Splitting revenue between many parties, correctly and repeatedly.

  • Contract integration

    Your application talking to chain state without trusting it blindly.

  • Reconciliation

    On-chain events and off-chain records that agree at the end of the month.

  • Creator and marketplace models

    Ownership, royalties and earnings that hold up as volume grows.

  • A feasibility answer

    Including whether the chain is load-bearing or decorative.

How we run it

  1. 01Test the premiseWhat the ledger is actually solving, and whether a conventional system would solve it better.
  2. 02Build both halvesThe on-chain mechanics and the ordinary application people will spend their time in.
  3. 03ReconcileChain state and business records agreeing, monitored, before real money depends on it.

This is for you if

  • Ownership or provenance has to be independently verifiable
  • Revenue is split between many parties on every transaction
  • You are building for a community that already holds wallets
  • A Web3 product stalled between the contract and the application
  • You have been pitched a blockchain and want a second opinion

What this is not

  • A token because the round needs a narrative
  • Putting a database on a chain to say it is on a chain
  • Anything whose business model depends on the next buyer

Where we have done this

One shipped system that used it.

Questions we get

Will you tell us not to do it?
Regularly. The feasibility answer is part of the service, and for most businesses that ask, the honest answer is that a conventional system is cheaper, faster and easier to hire for.
Which chains do you work with?
The choice follows the users and the cost of a transaction, not our preference. It is worth deciding late, after the mechanics are clear.
Do you write smart contracts?
We build the application around them and integrate with them. For contracts holding significant value we work with audited implementations rather than writing novel ones — that is the responsible answer, not the impressive one.
Here earnings, articles and authors were modelled together from the start, so a payout is a consequence of the content model rather than a separate system reconciling against it.
Zirkels — Web3 publishing platform

Tell us what is slowing the business down. We will tell you whether this is the right place to start.

Start a Conversation