Blockchain

Blockchain

Verification you cannot quietly alter — for certificates, identity, provenance and any record where trust between parties is the actual problem.

When does blockchain actually make sense?

Blockchain is worth using when multiple parties who do not fully trust each other need to share a record, and when the ability to prove a record was not altered has real value. Certificate verification, supply-chain provenance and credential issuance fit. Most internal business problems do not — a database is simpler and better.

The honest version of the pitch

Most blockchain projects should have been databases. If one organisation controls the data and everyone trusts them to hold it, a database is faster, cheaper and easier to fix. Saying so costs us work, and it is the single most useful thing a consultant can tell you in this category.

The genuine cases are specific and valuable. Certificates that can be verified by anyone without contacting the issuer. Provenance records spanning organisations that compete. Credentials that survive the issuing body's systems being unavailable. In those situations the tamper-evidence is the product, and it is worth the added complexity.

Frequently asked

Questions we get about this

Do we need cryptocurrency to use blockchain?

No. Certificate verification, credentialing and provenance systems can run on permissioned chains or public chains with fees paid by the issuer, with users never touching a token or wallet. Conflating blockchain with speculation has caused a lot of otherwise sensible organisations to dismiss it.

Is it expensive to run?

It depends on the chain and how much you write on it. The usual pattern is storing a cryptographic hash on-chain while the document stays in normal storage, which keeps costs low and privacy intact. Writing large data on-chain is expensive and usually a design mistake.

What about data privacy under the DPDP Act?

Personal data should not be written to an immutable ledger, because the right to erasure cannot then be honoured. We design so only hashes and non-personal metadata go on-chain, with personal data held conventionally where it can be corrected and deleted.

Talk it through before you commit

A discovery call is a working session on your constraint, not a sales pitch.

Quick inquiry

Tell us what you're trying to build

A short note is enough. You'll hear back from the team, not a bot — usually within one working day.

Captcha challenge