Holesh PriyankarDoes your business need blockchain? The short answer
Only when several parties who do not fully trust each other need to write to the same records, and no single one of them should control those records. If one organisation owns the data, or everyone already trusts one operator, a conventional database is cheaper, faster and simpler. Blockchain earns its place for assets, payments and proofs that move between independent parties.
Many blockchain projects that disappoint were solving a database problem with a ledger. The useful question is not “could we use blockchain?” but “what would go wrong if one party kept these records?” NIST put it plainly when it published its overview of the technology: “you shouldn’t use it if it’s not necessary” (NIST, 2018).
Key takeaways
- Blockchain fits records shared across organisations, digital assets and proofs that outsiders must be able to check.
- A database fits when one organisation owns the data, or when privacy, speed and frequent corrections matter most.
- Regulation is now concrete: MiCA in the EU and the GENIUS Act in the US set rules for crypto-assets and stablecoins.
Blockchain and digital assets by the numbers
- 91% of the 93 central banks surveyed were exploring a central bank digital currency – retail, wholesale or both (BIS Papers No 159).
- The EU’s Markets in Crypto-Assets Regulation (MiCA) has applied in full since 30 December 2024, and its rules for stablecoins – asset-referenced and e-money tokens – since 30 June 2024 (ESMA).
- The US GENIUS Act, signed on 18 July 2025, requires payment stablecoins to be fully backed by liquid assets such as US dollars or short-term Treasuries, with the reserves disclosed every month (The White House, 2025).
- The Bank for International Settlements argues that stablecoins fail three tests for sound money – singleness, elasticity and integrity – while tokenised central bank reserves on a shared ledger could underpin the next-generation financial system (BIS Annual Economic Report, 2025).
What a blockchain adds – and what a database already does
A blockchain is a shared ledger: several parties keep copies of the same records, agree on new entries through a consensus process, and can check that nothing was changed afterwards. That gives you three things a single database cannot: no single owner who can rewrite history, independent verification by anyone with access, and the ability to move digital assets between parties without a central clearing house.
A modern database already gives you a great deal: access control, audit logs, backups, encryption, fast queries and easy corrections. If those are enough – and for most internal systems they are – a ledger adds cost and complexity without adding trust.
Six questions to decide
- Do several organisations need to write to the same records? If only you write to them, use a database.
- Is there a party everyone already trusts to run it? If a regulator, an industry body or one of the partners can run it for everyone, a database run by that party is simpler.
- Must outsiders be able to verify records without asking you? Tamper-evident, independently checkable records point to a ledger.
- Do assets or payments move between parties? Tokens and smart contracts can settle transfers directly between them.
- Is the data private, high-volume or often corrected? Keep it off-chain; at most, anchor proofs such as hashes on-chain.
- Can you meet the rules? Crypto-assets and stablecoins now fall under MiCA in the EU and the GENIUS Act in the US, and personal data on a ledger that cannot be edited is hard to reconcile with the right to erasure under the GDPR.
If the answer is yes: what a sound blockchain project needs
- The right network. A public chain for open assets and payments; a permissioned network when the participants are known companies.
- A small on-chain footprint. Keep business and personal data off-chain, and put only what must be shared or proven on the ledger.
- Audited smart contracts. Code on a ledger is hard to change once deployed, so contracts need tests, an independent audit and a plan for upgrades.
- Key management. Whoever holds the keys controls the assets. Decide early who holds them, how they are stored and how they can be recovered.
- Trusted inputs. A ledger records data faithfully, but it cannot check that the data was true when it was entered. Partners, sensors and data feeds that write to it need their own controls.
- A conventional system around it. Users still need apps, sign-in, support and reporting. Done well, the chain is a small, carefully secured part of a larger system.
Where blockchain fits – and where it doesn’t
| Use case | Good fit? | Why |
|---|---|---|
| Payments and digital-asset transfers between companies | Yes | Parties settle directly, without a central clearing house |
| Tokenised assets such as funds, bonds or loyalty points shared with partners | Often | One shared record of who owns what |
| Certificates and credentials checked by third parties | Often | Anyone can verify them without contacting the issuer |
| Supply-chain records shared by several companies | Sometimes | Only if no single partner should control the data, and the data entered can be trusted |
| Internal records, CRM or inventory within one company | No | One owner, so a database is simpler and faster |
| Personal or health data | No – keep it off-chain | Privacy and the right to erasure |
| High-frequency, low-value transactions | Only on fast networks or layer 2 | Cost and speed per transaction |
Two projects, two answers
When Whaleworks wanted technical analysis for crypto traders and a secure wallet in one platform, the chain was the point: its users hold crypto, so the wallet had to work with it directly. We built the analysis tools and the wallet as one web application, with security designed in from the start.
When Empire Industries needed one register for the equipment, machinery and stock of every division, the answer was the opposite. All the records belonged to one enterprise, so one central register was the right design – no ledger required.
Frequently asked questions
Is blockchain only for cryptocurrency?
No. Cryptocurrencies are the best-known use, but businesses also use shared ledgers for tokenised assets, settlement between partners, credentials and records that several organisations rely on.
What is the difference between a public and a private blockchain?
Anyone can read and join a public blockchain. A private, or permissioned, blockchain limits who can take part, which suits a group of companies that know each other.
Can data on a blockchain be changed or deleted?
Not without the agreement of the network – that is the point. It is also why personal data and anything that may need correcting should stay off-chain.
Is a blockchain more secure than a database?
It protects records from being rewritten by one party, but smart contracts and wallets bring risks of their own. As with any system, security depends on design, audits and how keys are managed.
How should we start?
Write down who needs to read and write the records, who should control them and what would go wrong if one party did. If that points to a ledger, run a small pilot with real partners before scaling.
How Assystant can help
We build blockchain applications – smart contracts, wallets, dApps and on-chain data – designed security-first, and we use a ledger only where it does the job better than a database. If it doesn’t, we will tell you and build the simpler system instead. See Blockchain application development or talk to us about your use case.
Sources
- NIST – Report on blockchain technology aims to go beyond the hype (NISTIR 8202, January 2018)
- Bank for International Settlements – BIS Papers No 159: results of the BIS survey on central bank digital currencies and crypto
- ESMA – MiCA Article 149: entry into force and application
- The White House – Fact sheet on the GENIUS Act (July 2025)
- Bank for International Settlements – Annual Economic Report 2025, chapter III