Blockchain in Finance: Useful Rails or Core Product?
Blockchain powers more financial products, but is often infrastructure rather than the product. Learn where it adds value and who captures the upside.

Does Finance Need Blockchain? Separating the Product from the Rails
A financial product can be tied to crypto without needing blockchain under the hood. Prediction markets and perpetual futures are a good example. They've grown up in crypto culture, but centralized exchanges can still run them with conventional matching, clearing, and settlement.
That distinction matters because adoption and value capture don't automatically travel together. A product can pull in users while blockchain sits in the background - maybe handling deposits, withdrawals, or tokenized assets. The company that owns the customer relationship and the core business logic often captures more value, while the underlying network mainly provides infrastructure.
This isn't me arguing that blockchain is useless. Shared, programmable financial rails can make assets easier to move, trade, and combine. The real question is where those rails create an advantage that a non-blockchain setup can't match - and whether the product would still make sense without them. In this article, I'll use Kalshi and a few financial-market examples to lay out a practical way to judge blockchain's role, its limits, and what the industry should do next.
Why Can a Crypto-Associated Product Work Without Blockchain?
People use crypto to mean a bunch of different things at once: an asset class, an industry, a set of products, and a technical architecture. They overlap, but they're not the same. A trading product can start out in crypto and later get offered by a firm that doesn't use blockchain for its day-to-day operations.
Take Kalshi. It's a centralized derivatives exchange regulated by the US Commodity Futures Trading Commission (CFTC). It offers prediction markets and perpetual futures. Its core exchange functions - order matching and clearing - don't depend on a public blockchain. In the model described here, orders run through Kalshi's proprietary matching engine, while clearing and settlement are handled through Kalshi Klear, a CFTC-registered derivatives clearing organization.
Blockchain can still show up around the edges. Users might move funds with stablecoins, and positions might be tokenized or made available through blockchain-based platforms. But those integrations don't automatically mean the exchange's main trading and clearing logic runs onchain. The product's operating model remains centralized.
Product history is not a technical requirement
Prediction markets became associated with crypto partly because early platforms leaned on blockchain components. Polymarket, for instance, used Polygon and the UMA oracle in parts of its market-resolution and settlement design. That history helped connect prediction markets with blockchain in the public mind. But the category itself doesn't require that architecture - regulated, centralized operators can offer similar products without it.
Perpetual futures have a similar backstory. Crypto markets run around the clock, so "no fixed expiry" fits naturally. Onchain exchanges made perps a visible product there. Still, the contract itself is a financial instrument, not a blockchain primitive. A centralized venue can run perpetual futures using conventional exchange infrastructure.
The practical takeaway is simple: a product can feel crypto-native in its history, audience, or market culture without being blockchain-dependent in how it's implemented. When people blur those ideas, it becomes harder to see what the technology is actually doing - and what users are paying for.
What Does Blockchain Actually Add to Financial Products?
In a lot of financial products, blockchain is best thought of as shared financial rails. It can provide a common ledger, programmable asset transfers, and access to markets that never "close." Those features can matter even if the product's rules, interface, or trading strategy are managed elsewhere.
For a centralized exchange, that role might include accepting stablecoin deposits, supporting withdrawals, or making a position transferable as a token. The exchange can still control customer accounts, decide which markets to list, run the matching engine, and handle compliance. Blockchain may change parts of how users move through the system, but it doesn't automatically decentralize the business itself.
You see the same split across other crypto categories. Memecoins use blockchains to issue tokens and let people trade them. Stablecoins use blockchains to transfer tokenized money. Tokenized real-world assets (RWAs) use blockchains to represent claims or interests, while vaults can use programmable contracts to manage deposits and strategies. The business models differ, but often the network mainly makes it easier to issue, hold, or move financial assets.
Rails can be a real product advantage
Calling blockchain "just infrastructure" shouldn't mean calling it trivial. Payment networks, clearing systems, and databases are infrastructure too - the question is whether they improve the product built on top of them. Blockchain rails can enable 24/7 settlement, broader asset composability, and fewer barriers between separate applications. For some users, those differences are the product.
But you have to count the downsides. Public networks can mean transaction fees, performance variability, extra wallet friction, and real security risks. A regulated platform still has to manage identity checks, transaction monitoring, custody controls, and ways to handle mistakes and disputes. If the business needs a centralized operator anyway to cover those requirements, the onchain piece may be a useful layer - not a replacement for the whole system.
A good assessment comes back to the user's workflow. Does it reduce settlement time or operating costs? Does it make assets more portable? Does it let applications interoperate in a way users actually feel? If the "benefit" is mainly that the product can claim a blockchain connection, it's unlikely to create durable demand on its own.
Who Captures the Value When Blockchain Is Just Infrastructure?
Technology doesn't always translate into the same company capturing the money. The thing that makes a product possible can be less valuable financially than the platform that packages it, distributes it, and maintains the customer relationship.
You can see this with blockchain-based financial products. A platform may own the brand, interface, market listings, customer support, compliance process, and relationships with liquidity providers. Blockchain can enable deposits or asset transfers, but users may choose the platform for its prices, market selection, ease of use, or reputation. In that setup, the network is an important supplier, but it doesn't automatically control the customer - or the business logic.
This is one reason onchain activity doesn't automatically mean everyone in the infrastructure stack gets paid. A market can grow while the underlying infrastructure stays interchangeable. If multiple networks can support the same stablecoin transfers or tokenized positions, competition tends to compress infrastructure margins. Meanwhile, a platform with distribution strength can keep more control over how the product is sold and experienced.
Adoption is not the same as value capture
This distinction matters when people evaluate whether a sector is growing. Prediction markets and perpetual futures can be popular without blockchain. Stablecoins and tokenized assets lean more directly on blockchain for transfer and settlement, but issuers, custodians, exchanges, or asset managers can still capture much of the commercial value.
That doesn't make adoption irrelevant. It just answers a different question: adoption asks whether users want the product. Value capture asks which parts of the system have bargaining power and real differentiation that lasts. A growing market can validate a use case without proving that every chain, protocol, or token benefits in proportion.
For builders and investors, the next questions should be concrete:
- Who owns the user relationship and controls distribution?
- Who sets the product's rules, and how do those rules evolve?
- Can users move assets or activity to another platform without losing access or usefulness?
- What does the blockchain contribute that a centralized database or payment rail can't provide at a comparable cost?
- If the blockchain layer becomes cheaper or interchangeable, where does the value still land?
The answers tell you whether a project is building a differentiated financial product, offering a commodity-like rail, or leaning on the idea that more onchain usage will automatically create more value for the infrastructure.
When Is Blockchain Essential Rather Than Optional?
Here's a useful test: imagine removing the blockchain from the product. If the same users can still get the same outcome using a conventional database, a payment provider, and a centralized operator, blockchain is probably optional infrastructure. It might improve access or settlement, but it isn't the core reason the product exists.
If removing blockchain breaks a capability users truly rely on, then it's closer to indispensable. That can happen when independent parties need to coordinate around shared state without trusting one operator, when assets must be composable across applications, or when users need to hold and transfer assets under rules enforced by public code. Even then, the project has to show that these properties matter enough to justify both the cost and the operational complexity.
A four-part necessity test
- Identify the trust problem. What does the user have to trust today? Is there one custodian, exchange, or administrator whose failure could block access or change the rules? Blockchain can reduce dependence on a single operator - but only if the rest of the system doesn't quietly recreate the same dependency elsewhere.
- Name the capability. "Transparency" and "decentralization" are too vague. Get specific: independently verifiable balances, censorship resistance, open access to a contract, portability between applications. A capability only matters if it changes the user's choices or the product's reliability.
- Compare the alternatives. Measure the blockchain design against the best realistic centralized option, not a strawman "paper process." Include transaction costs, settlement delays, security, compliance, customer support, and recovery from mistakes. A system that's technically open but unusable for the target customers is the wrong trade-off.
- Check the dependencies. A smart contract can be public, but the product might still rely on a central company for an oracle, a front end, an administrator key, liquidity, or a legal claim. Those dependencies affect how much independence users actually get.
This test doesn't require every product to be decentralized. It's meant to help teams make a clearer, more honest design decision. Sometimes a conventional setup is simpler and safer. Other times, open and composable settlement is worth the extra burden. The point is to connect architecture to a user need, not treat blockchain as the default.
How Should You Evaluate a Blockchain Business?
If you're a founder, product lead, or investor, the question isn't just whether the company uses blockchain. The better question is whether it has a defensible reason for using it - and whether the business captures enough value to keep running.
Start with the customer problem. Write down the job the user is trying to complete, then explain how the product improves the outcome. If the answer depends on token ownership, 24/7 access, or composability, spell out where those properties change the measurable result. If users mainly want a simpler interface or access to a popular market, the platform layer may matter more than the chain.
Next, map the system. Separate what the user sees from business rules, settlement, custody, identity checks, data sources, and dispute handling. Label what's onchain, what a company controls, and what depends on third parties. Often, this makes one thing obvious: "onchain" isn't a clean yes-or-no label. A product can be decentralized in one layer and tightly controlled in another.
Then look at the economics. Identify who pays fees, who collects them, and what costs blockchain adds or removes. Ask whether the product still works if transaction fees drop, the network changes, or another chain offers the same functionality. If the plan depends on a specific token appreciating, separate that assumption from revenue created by real usage.
A practical decision checklist
Before committing to an onchain design, answer these questions in plain language:
- User advantage: What gets materially better for the target user?
- Necessity: What core feature stops working if the blockchain is removed?
- Trust: What do users still have to trust a company or intermediary to do?
- Operations: Who handles compliance, security incidents, failed transactions, and support?
- Portability: Can users or assets move to another application, and is that useful in practice?
- Economics: Does the design create sustainable revenue, or does it mainly move costs to users?
- Fallback: What happens when the chain, oracle, or key service is unavailable?
These questions also help teams avoid confusing "technical novelty" with product-market fit. A system can be interesting and still fail to find a repeatable customer need. On the other hand, a product that uses blockchain mainly as a settlement layer can still be commercially useful - even if the chain isn't the main differentiator.
The strongest case is when user benefit, system design, and the business model reinforce each other. The weakest is when a product adds blockchain complexity without changing what customers can do - then assumes ecosystem growth will fix the economics later.
Conclusion: Rails Are Progress, but Not the Whole Destination
Blockchain has proven it can be useful financial infrastructure. It can make assets easier to issue, move, and combine - and in the right context, that's a real improvement. But a product's association with crypto doesn't automatically prove it needs blockchain. And more onchain activity doesn't automatically mean value will flow to the underlying infrastructure.
For any project, start with the user's problem, identify the capability blockchain is actually providing, and compare it to the best practical alternative. Then trace who controls the customer relationship, what the system depends on, and how the economics work. That approach leaves room for two outcomes: using a conventional system when it's the better fit, and building blockchain-native products when open, programmable rails really are central to the experience.
The industry challenge is to stop treating blockchain like the destination. Financial rails are helpful, but the bigger opportunity is in products where the core value depends on what those rails make possible.