Most business apps do not need a blockchain, and a normal database is cheaper, faster and easier to change. A blockchain earns its cost only when several parties who do not fully trust each other must share one record that none of them controls, and that record must be tamper-evident. If you can name a single organisation that can safely run the database, use a database. If you cannot, a blockchain may be the right tool, and since 2024 the rules around crypto-assets and stablecoins have become much more concrete in the EU and the US.
Key takeaways
- A blockchain is a tamper-evident, shared ledger kept by many parties, usually without a central authority. NIST's 2018 overview, since withdrawn, said it should be treated like any other technology and used where it is appropriate.
- Ethereum's Fusaka upgrade went live on 3 December 2025; its PeerDAS feature lets each node hold only a fraction of blob data, which theoretically scales blob capacity up to 8x for layer-2 networks.
- In the EU, MiCA's crypto-asset service provider rules have applied since 30 December 2024, with national transitional periods ending no later than 1 July 2026.
- In the US, the GENIUS Act, signed on 18 July 2025, requires 100% reserve backing for payment stablecoins, monthly public disclosure of reserves and Bank Secrecy Act compliance.
- Keep personal data off the chain, and treat key management as a core design decision.
What is a blockchain, in plain terms?
It is a shared record, a ledger, where new entries are added in order and earlier entries cannot be quietly changed. Many computers keep copies and agree on the next entry by rules, instead of trusting one owner. NIST's overview described blockchains as tamper-evident and tamper-resistant digital ledgers implemented in a distributed fashion, usually without a central authority. That report has since been withdrawn, so treat it as background, not current guidance.
That design has a price. Writes are slower and more expensive than in a database, changing or deleting data is deliberately hard, and public chains expose entries to everyone.
Do you need one?
Ask these questions in order:
- Do several organisations need to write to the same record?
- Do they lack a trusted party that could run a shared database?
- Does the record need a tamper-evident history that all can verify?
- Can the data be public, or properly protected and kept off the chain?
If you answered "no" to the first three, use a database.
| Likely a good fit | Usually better with a database |
|---|---|
| A shared record between companies with no neutral operator | An app used by one organisation |
| Tokens or stablecoin payments between parties | A customer list, catalogue or order history |
| Proof that a document or event existed at a time | Anything that needs routine editing or deletion |
| Interoperating with existing public networks | Internal workflows with a known owner |
What has changed since the 2019 posts?
The technology matured. Ethereum's Fusaka upgrade went live on 3 December 2025. Its PeerDAS feature uses data availability sampling, so each node holds only about 1/8th of the blob data, which theoretically scales blob capacity up to 8x and helps layer-2 networks keep fees down.
The rules became concrete. This is general information, not legal or financial advice, and it covers only the EU and US.
- EU, MiCA. The Markets in Crypto-Assets Regulation's provisions on crypto-asset services have applied since 30 December 2024. Firms already operating under national law could continue until an authorisation decision or 1 July 2026 at the latest, whichever came first, and ESMA publishes a register of authorised providers.
- US, GENIUS Act. Signed on 18 July 2025, it requires 100% reserve backing with liquid assets such as US dollars or short-term Treasuries, monthly public disclosure of reserve composition, and subjects issuers to the Bank Secrecy Act. Regulators are still writing detailed rules, so check current status.
- Elsewhere. Rules in Canada, India and other markets differ and are not covered here.
What are the hidden costs?
- Fees and speed. Every write has a cost and a delay, so design what must be recorded on the chain and what stays in a normal database.
- Privacy. An immutable ledger cannot easily forget. Keep personal data off the chain and store only references or hashes.
- Keys. Whoever holds the keys controls the assets. Plan secure storage, recovery and who can sign.
- Upgrades and audits. Smart contracts are hard to change once deployed, so budget for independent security review before launch.
- People. Few teams have long experience here, so check references carefully; see How to hire an app development company in 2026.
How should you start?
- Write the problem and the parties in one page, and run the four questions above.
- Build the simplest version on a database first if you can; many ideas never need more.
- If a chain is justified, prototype one process on a test network.
- Get a security review and legal advice for your market before handling real money.
- Plan the mobile or web front end separately; see How to choose a tech stack for a web or mobile app in 2026 and Cross-platform or native in 2026.
FAQ
Do we need a blockchain for our app?
Probably not. If one organisation can run the database, a database is simpler and cheaper. Consider a blockchain when several parties must share a tamper-evident record without a central operator.
Is blockchain the same as cryptocurrency?
No. Cryptocurrency is one use of blockchains. The technology can also record other entries, such as proofs or shared business records.
Can we delete data from a blockchain?
Not easily, by design. Keep personal or changeable data in a normal database and put only references or hashes on the chain.
Is stablecoin payment legal?
It depends on the market and the issuer. The EU's MiCA and the US GENIUS Act both set rules. Get legal advice for the countries you serve.
How long does a blockchain app take to build?
It depends entirely on scope: a prototype on a test network is a different job from an audited, regulated product. Ask for a plan in stages with a security review before launch.
Sources (4 links)
- NIST, "Blockchain Technology Overview" (NISTIR 8202, 2018, now withdrawn): https://csrc.nist.gov/pubs/ir/8202/final
- ethereum.org, "Fulu-Osaka (Fusaka)": https://ethereum.org/roadmap/fusaka/
- ESMA, "Markets in Crypto-Assets Regulation (MiCA)": https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica
- The White House, "Fact Sheet: President Donald J. Trump Signs GENIUS Act into Law" (18 July 2025): https://www.whitehouse.gov/fact-sheets/2025/07/fact-sheet-president-donald-j-trump-signs-genius-act-into-law/
