Blockchain for Banks: How Financial Institutions Are Deploying On-Chain Infrastructure

Banks moved from dismissing blockchain to deploying it in production over a span of roughly three years. The shift is visible in public announcements from JPMorgan, Goldman Sachs, BlackRock, Franklin Templeton, DTCC, Swift, State Street, others. Each of these institutions now runs at least one production program that touches blockchain infrastructure directly.

The category has moved past the question of whether blockchain belongs in banking. The current questions are operational. Which chain should a bank deploy on? What infrastructure standards apply? How should a bank structure its vendor relationships for blockchain systems it cannot run internally? What are the procurement frameworks that apply to this category of technology?

This guide explains how banks are actually using blockchain in 2026, what infrastructure the production deployments depend on, how financial institutions should think about the decisions that the category still forces.

1. Why Banks Are Adopting Blockchain

Banks are adopting blockchain because specific operational problems in banking have better solutions on shared ledgers than on legacy infrastructure. The adoption is not driven by cryptocurrency speculation or hype cycles. It is driven by measurable operational benefits in specific use cases.

Settlement Speed

Traditional securities settlement runs on T+1 or T+2 cycles. Cash settlement happens through correspondent banking networks that can take days to move funds across borders. Blockchain settlement happens in minutes or seconds, with the cash leg and the securities leg atomically linked.

Faster settlement reduces counterparty risk. It improves capital efficiency because capital stays tied up for shorter periods. It reduces the collateral requirements that sit behind settlement exposures. For banks with large settlement volumes, the cumulative capital efficiency gains are significant.

Settlement Cost

Correspondent banking is expensive. Cross-border payments carry fees from each intermediary bank involved in the transaction. Blockchain-based settlement replaces correspondent banking with direct peer-to-peer transactions on a shared ledger, eliminating most intermediary fees.

The cost differential is largest for cross-border transactions involving corridors with few direct banking relationships. For major currency corridors with deep correspondent relationships, the cost benefit is smaller but still present.

Transparency and Auditability

Shared ledgers provide transparency that legacy systems cannot match. Every transaction is recorded on an immutable ledger that regulators and auditors can verify directly. Reconciliation between counterparties is eliminated because both parties read from the same source of truth.

For regulated financial activities, transparency benefits translate directly into reduced compliance cost. Audits become faster. Regulatory reporting becomes simpler. Disputes become rarer.

New Product Capability

Tokenization enables products that traditional infrastructure cannot support economically. Fractional ownership of illiquid assets. 24/7 trading of instruments that traditionally settle on weekdays. Programmable compliance that enforces transfer restrictions automatically. Composability with other on-chain applications.

These capabilities are the reason tokenized money market funds have grown from zero to over ten billion dollars in combined assets between 2024 and 2026. The products exist because blockchain made them possible.

Competitive Pressure

Banks watch each other closely. When JPMorgan announces production volumes on Kinexys, competitors respond. When BlackRock launches BUIDL, other asset managers evaluate tokenization programs. The competitive dynamic accelerates adoption independent of the standalone business case for any specific bank.

2. Where Banks Use Blockchain Today

Bank blockchain deployments cluster around several use case categories. Each category has matured at a different rate.

Tokenized Funds and Securities

The largest and fastest-growing category. Banks and asset managers tokenize existing fund products (money market funds, short-duration treasuries) or launch new products designed for on-chain distribution. Tokenized funds use oracle infrastructure to publish net asset value on-chain and smart contracts to enforce transfer restrictions.

Combined assets across tokenized treasury products passed ten billion dollars by early 2026, growing over two hundred percent year-over-year.

Wholesale Settlement

Banks use blockchain to settle large transactions between institutional counterparties. Deposit tokens, tokenized commercial paper, tokenized collateral all sit in this category. The underlying transactions are not new. What blockchain changes is the settlement mechanics.

JPMorgan’s Kinexys platform (previously Onyx) is the most prominent example. Kinexys settles billions of dollars of daily transaction volume between institutional counterparties using JPMorgan’s own blockchain infrastructure.

Cross-Border Payments

Cross-border payment rails based on blockchain replace or supplement traditional correspondent banking. Stablecoin settlement, CBDC pilots, tokenized deposit systems all target this category. The Swift CCIP pilot with major global banks is the most visible ongoing initiative.

Digital Asset Custody

Custody providers extend their services to tokenized assets. This includes both banks adding digital asset custody to existing custody platforms (State Street, BNY Mellon) and specialized digital asset custodians serving banks as infrastructure providers (Fireblocks, Anchorage, Taurus).

Trade Finance

Letter of credit digitization, supply chain finance, invoice finance use blockchain to track the lifecycle of trade transactions. Adoption has been slower than initially predicted, concentrated in specific corridors and counterparty networks rather than industry-wide.

Repo and Collateral Management

Repo markets use blockchain to automate collateral transfers that traditionally require manual reconciliation. Tokenized collateral can move atomically with cash settlement, reducing operational risk and collateral calls.

Post-Trade Services

DTCC and other post-trade service providers use blockchain for specific functions within clearing and settlement workflows. The work is technical and internal, less visible publicly than front-office products.

3. Real Bank Deployments

The following deployments are all matter of public record as of early 2026.

JPMorgan Kinexys

JPMorgan’s institutional blockchain platform, previously named Onyx. Runs on a proprietary blockchain network. Settles institutional transactions for JPMorgan clients including deposit tokens (JPM Coin) and tokenized money movement services. Handles billions of dollars of daily transaction volume.

Kinexys represents the bank-led blockchain model: a major bank runs its own blockchain network for its institutional client base, retaining control of the infrastructure while gaining the operational benefits of blockchain settlement.

BlackRock BUIDL

BlackRock’s USD Institutional Digital Liquidity Fund launched on Ethereum in March 2024. BUIDL tokenizes a portfolio of cash, US Treasury bills, repurchase agreements. Distributes yield directly to token holders. Uses Securitize for tokenization technology and Chainlink oracle infrastructure for on-chain data.

BUIDL established the template for institutional tokenized funds. Every subsequent institutional product in the category references BUIDL as the design reference point.

Franklin Templeton FOBXX

Franklin OnChain US Government Money Fund. One of the earliest tokenized money market funds from a traditional asset manager. Available on multiple blockchain networks. Distributes yield through on-chain token holders.

DTCC Digital Transactions

The Depository Trust & Clearing Corporation runs blockchain-based programs for tokenized securities and post-trade services. DTCC partnered with major banks to build shared infrastructure for tokenized equity and bond settlement.

Swift CCIP Pilot

Swift partnered with major global banks to pilot cross-chain interoperability using Chainlink’s Cross-Chain Interoperability Protocol (CCIP). The pilot demonstrates how traditional financial messaging can coexist with blockchain settlement by using cross-chain messaging protocols as the bridge layer.

Participating banks include JPMorgan, HSBC, Deutsche Bank, MUFG, BNP Paribas, Santander, OCBC, additional banks from the Middle East and Africa.

Goldman Sachs and the Canton Network

Goldman Sachs participates in the Canton Network, a privacy-enabled blockchain designed for institutional finance. Goldman’s involvement includes tokenization initiatives and collaborative projects with partners including Visa and Microsoft.

State Street Tokenization

State Street has announced multiple initiatives around tokenized funds, digital asset custody, settlement infrastructure. State Street’s role as a major custody bank positions it as one of the most important infrastructure providers as tokenized fund products grow.

Fidelity Digital Assets Expansion

Fidelity has broadened its digital asset offerings to include tokenization-adjacent products and custody for tokenized instruments. Fidelity Digital Assets Trust Company serves as the custodian for multiple institutional digital asset programs.

Ondo Finance Products

Ondo is crypto-native but serves institutional and accredited investors. Its OUSG and USDY products are widely held by treasury managers at Web3 companies and by institutional crypto allocators. Ondo Global Markets extends the category into tokenized equities.

Regional Bank Pilots

Multiple regional and national banks run blockchain pilots that do not receive the press coverage of the global banks. Societe Generale, ANZ, Lloyds, HSBC, Standard Chartered, others have all announced specific blockchain initiatives between 2024 and 2026.

4. The Infrastructure Layer Behind Bank Blockchain Programs

Bank blockchain programs depend on infrastructure across several layers. The quality and reliability of this infrastructure determines whether the programs work in production.

Blockchain Network Selection

The choice of blockchain network has long operational consequences. Ethereum dominates tokenized asset programs by total value because it offers institutional familiarity, deep liquidity, mature tooling. Ethereum layer-2 networks (Arbitrum, Optimism, Base) provide lower transaction costs with similar security guarantees. Purpose-built institutional networks (Canton, Provenance, Polymesh) offer features tailored specifically to regulated use cases. Private or permissioned networks (JPMorgan’s Kinexys network, for example) offer maximum control at the cost of ecosystem connectivity.

Most major bank programs deploy on multiple networks simultaneously. A single tokenized product might live natively on Ethereum while also being accessible on layer-2 networks through cross-chain messaging.

Node Infrastructure

Banks need reliable access to the blockchain networks they operate on. This access is provided by nodes that run the blockchain protocol. For institutional use cases, retail-grade public nodes are typically insufficient. Dedicated nodes, managed nodes run by institutional infrastructure providers, or enterprise variants deployed inside the bank’s own cloud tenancy are the typical configurations.

Node infrastructure must meet the bank’s security, compliance, operational standards. This includes recognized information security certification at minimum, documented incident response procedures, formal SLAs, integration with the bank’s existing monitoring and alerting systems.

Oracle Infrastructure

Oracle infrastructure is the bridge between the bank’s off-chain data and the on-chain smart contracts that implement its products. A tokenized money market fund needs NAV published to its smart contracts daily. A tokenized bond needs interest accrual reflected on-chain. A tokenized commodity needs reference pricing. A proof of reserve system needs regular attestation of backing assets.

This data flows through oracle networks. Chainlink is the dominant oracle network for institutional programs, including BlackRock BUIDL, Ondo products, the Swift CCIP pilot. Chainlink oracles are run by independent node operators who provide the underlying infrastructure.

Matrixed.Link operates as one of those independent Chainlink node operators. We run 500+ active Chainlink price feeds across Ethereum, Polygon, Arbitrum, Base. We operate Data Feeds, CRE, SVR, Proof of Reserve node types in production. Our infrastructure supports oracle operations that tokenized asset programs depend on.

Validator Infrastructure

Banks that participate in proof-of-stake networks need validator operations. This applies to banks running custody services that include staking, banks participating in institutional staking products, banks that validate their own network activity for security reasons.

Validator operations are specialized. They require dedicated hardware, 24/7 monitoring, double-sign monitoring, the operational tempo to handle protocol upgrades and network incidents. Most banks partner with specialized validator operators rather than building internal teams for this function.

Key Management

Every blockchain transaction requires cryptographic keys. Institutional key management uses hardware security modules, enterprise key management systems, multi-party computation solutions, or some combination. The specific approach depends on the bank’s existing security architecture and the regulatory requirements that apply to the activity.

Key management is one of the most consequential choices in a bank blockchain program. Get it right and the program has institutional-grade security. Get it wrong and the program has catastrophic failure modes that no amount of monitoring can detect after the fact.

Smart Contract Standards

Banks typically use compliance-enabled token standards (ERC-1400, ERC-3643) or custom contracts designed for specific products. Standards like these include hooks for access control, transfer restrictions, regulatory reporting that integrate with the bank’s compliance workflows.

Smart contract auditing by reputable security firms is a prerequisite for institutional deployment. Formal verification of critical contract logic is common for high-value products.

5. Build vs Partner for Bank Blockchain Infrastructure

A bank deploying blockchain infrastructure faces a build-vs-partner decision for each infrastructure layer. The right answer depends on strategic intent and operational capacity.

When Banks Should Build

Banks should build infrastructure internally when:

The infrastructure is strategically critical and will operate for a decade or more
The bank has existing technology capability adjacent to blockchain infrastructure
The regulatory environment requires data residency or security standards that vendors cannot meet
The bank has the hiring capacity to build a team with blockchain operational experience

JPMorgan Kinexys is the reference example of a bank that built. JPMorgan concluded its blockchain infrastructure was core strategic capability and committed to building a team large enough to operate it at production scale.

When Banks Should Partner

Banks should partner for infrastructure when:

The time horizon is too short to build internal capability
The infrastructure needs specialized expertise that is not a bank core capability
The scale is not large enough to justify dedicated internal teams
The regulatory requirements can be met by vendors with appropriate certifications

Most tokenized fund launches use partnership models. The asset manager retains control of the fund economics and regulatory framework. Specialized partners run the oracle infrastructure, tokenization technology, key management systems.

The Hybrid Model

Many successful bank blockchain programs use a hybrid model. Strategic capabilities are built internally. Specialized operational work is contracted to external partners under formal vendor relationships.

This pattern matches how banks already operate in traditional technology. No bank builds its own database management system. Most banks build their own fraud detection systems. The specific boundary depends on strategic judgment about which capabilities are core.

6. Security and Compliance Requirements

Bank blockchain programs face stricter security and compliance requirements than most other blockchain use cases. These requirements shape vendor selection, infrastructure design, operational procedures.

Information Security Standards

ISO/IEC 27001:2022 is the baseline expectation for infrastructure vendors serving banks. The standard provides a formal framework for information security management systems, with requirements around access controls, incident response, business continuity, regular audits.

Banks themselves typically hold this certification. When they procure infrastructure from third parties, they expect the same standard from their vendors.

SOC 2 Type II

Service Organization Control 2 Type II reports are the standard for US institutional procurement. SOC 2 reports are prepared by independent auditors and cover trust service criteria around security, availability, processing integrity, confidentiality, privacy.

Most US banks require SOC 2 Type II from technology vendors, particularly for services that involve handling client data or performing regulated activities.

Regulatory Frameworks

Bank blockchain programs operate under multiple regulatory frameworks simultaneously. In the United States, SEC, CFTC, OCC, FinCEN, state-level financial regulators may all have relevant rules. In the European Union, MiCA, MiFID II, DORA, national competent authorities each contribute different requirements. Similar complexity applies in most jurisdictions.

Infrastructure vendors serving banks must understand the regulatory context and design systems that accommodate the bank’s compliance workflows. This includes documented procedures, audit trail support, incident reporting that matches regulatory expectations.

Operational Resilience

The EU’s Digital Operational Resilience Act (DORA), effective since January 2025, creates specific operational resilience requirements for financial institutions and their critical third-party technology providers. Similar frameworks exist in the UK, Singapore, other jurisdictions.

Infrastructure vendors serving banks need operational resilience programs that align with these frameworks. This includes documented incident response, tested business continuity plans, regulatory reporting procedures.

Know Your Customer and Anti-Money Laundering

Banks are subject to comprehensive KYC and AML requirements. When blockchain infrastructure touches transactions or holdings subject to these requirements, the infrastructure must support the compliance workflows. This includes transfer restriction enforcement, identity verification integration, transaction monitoring.

Token standards like ERC-3643 include built-in hooks for KYC and AML enforcement. Oracle networks can publish identity attestations that smart contracts use to validate transfers. The integration patterns are well-established for banks deploying on permissioned or hybrid networks.

7. Common Implementation Patterns

Bank blockchain deployments tend to follow a small number of architectural patterns. Understanding these patterns helps orient new programs.

Pattern 1: Public Chain with Permissioned Token

The bank issues a token on a public blockchain (typically Ethereum). The token uses a compliance-enabled standard that restricts transfers to whitelisted wallets. KYC and AML enforcement happens at the token level through identity oracles or smart contract allowlists.

This pattern fits tokenized funds and securities. BUIDL, FOBXX, most institutional tokenized treasury products use this pattern.

Advantages: leverages the liquidity and composability of public networks while maintaining institutional compliance.

Disadvantages: relies on the security and operational stability of the public network, which the bank does not control.

Pattern 2: Permissioned Network

The bank deploys on a permissioned blockchain network where participation is restricted to approved institutions. JPMorgan’s Kinexys network is the most prominent example. The Canton Network is the leading multi-institution permissioned network.

This pattern fits wholesale settlement, interbank transactions, programs where the bank needs direct control over which counterparties can participate.

Advantages: maximum control over participants, network governance, technical decisions.

Disadvantages: limits liquidity and composability with public network participants.

Pattern 3: Cross-Chain Architecture

The program operates across multiple networks connected through cross-chain messaging protocols like Chainlink CCIP. Tokens, messages, settlement instructions move between networks as needed.

This pattern fits programs that need both public network liquidity and permissioned network control, or programs that span jurisdictions with different network preferences.

Advantages: combines the strengths of multiple network types.

Disadvantages: architectural complexity, additional infrastructure dependencies.

Pattern 4: Hybrid Off-Chain / On-Chain

Some functions happen off-chain on traditional bank systems. Other functions happen on-chain for specific benefits (settlement speed, composability, programmability). Oracle infrastructure bridges the two.

This pattern fits programs that are exploring blockchain benefits in specific areas without moving entire product lines on-chain. Tokenized collateral for repo transactions, on-chain NAV reporting for otherwise-traditional funds, on-chain proof of reserve for custody programs are common examples.

Advantages: incremental adoption, minimized disruption to existing systems.

Disadvantages: operational complexity from running parallel infrastructures.

8. Risks Banks Actually Face

Bank blockchain programs carry risks that are specific to the technology and the institutional context. Understanding these risks is part of running a successful program.

Operational Risk

Blockchain infrastructure can fail. Networks can experience outages. Oracle feeds can delay or report incorrect data. Nodes can fall behind consensus. Validators can be slashed. These operational risks must be managed through redundancy, monitoring, incident response.

The operational risk profile differs from traditional systems. Banks cannot call a vendor hotline for a network-wide Ethereum incident. Response procedures need to account for the decentralized nature of public blockchain infrastructure.

Vendor Concentration Risk

Bank blockchain programs often concentrate vendor risk in a small number of infrastructure providers. A tokenization platform, an oracle network, a custody provider, a key management vendor. If any critical vendor fails, the program fails.

Vendor concentration risk management for blockchain infrastructure follows the same principles as other technology vendor management, with additional focus on the specialized nature of blockchain operations.

Regulatory Risk

Regulatory frameworks for blockchain in banking are evolving. Rules that apply today may change. New requirements may emerge. Banks must monitor regulatory developments and maintain infrastructure flexibility to adapt.

This is not unique to blockchain, but it is more acute because the category is newer than most bank technology stacks.

Security Risk

Smart contract vulnerabilities, key compromises, oracle manipulation are all categories of security risk specific to blockchain infrastructure. Banks manage these through contract auditing, secure key management, oracle infrastructure selection.

The worst outcomes in blockchain security tend to be catastrophic rather than degraded. A compromised key can result in complete loss of tokens controlled by that key. This makes security engineering for blockchain systems particularly important.

Reputation Risk

Banks operate under reputational constraints that most technology companies do not face. A public incident involving the bank’s blockchain program generates press coverage that affects the bank’s broader brand. This constrains the kinds of experiments banks can run and the risks they can accept.

Reputation risk is one reason bank blockchain programs tend to move more slowly than technology observers expect. Speed increases risk. Banks prioritize getting the first production program right over launching quickly.

Transition Risk

Blockchain programs that succeed often create transition challenges. When a tokenized product reaches material scale, it changes how the bank needs to operate. Reporting, treasury, compliance, client service all adapt. Managing this transition requires organizational change management that is not purely a technology question.

9. How Banks Evaluate Blockchain Infrastructure Vendors

Bank procurement for blockchain infrastructure follows the same general pattern as other technology procurement, with specific additions for the category.

Standard Procurement Requirements

Banks expect vendors to meet standard procurement requirements: commercial insurance coverage, liability frameworks, standard contract terms, financial stability documentation, reference clients, security certifications.

Infrastructure vendors serving banks must have these in place before they can participate in bank vendor onboarding processes. Startups without these requirements can still sell to banks, but typically through extended onboarding periods or special procurement arrangements.

Blockchain-Specific Questions

Beyond standard requirements, banks ask questions specific to blockchain infrastructure:

What blockchain networks do you run infrastructure on? How long have you been operating?
What is your track record on protocol upgrades and network incidents?
What is your operational posture for 24/7 monitoring and incident response?
What security certifications do you hold, what is your roadmap for additional certifications?
What is your key management architecture?
What reference clients can you provide with similar operational scale?
What happens to our infrastructure if you experience a corporate event (acquisition, bankruptcy)?

Vendors that answer these questions specifically and with evidence tend to advance through bank procurement. Vendors that answer with marketing language tend not to.

Technical Validation

For material engagements, banks conduct technical validation of vendor claims. This may include site visits to operational facilities, technical deep-dives with vendor engineering teams, independent review of security controls, reference calls with existing clients running comparable workloads.

Commercial Structure

Bank commercial arrangements for blockchain infrastructure typically include master service agreements with formal SLAs, documented escalation procedures, committed uptime targets with financial penalties for missed targets, data handling and confidentiality provisions appropriate for regulated environments, transition-out procedures that guarantee the bank’s ability to migrate to a different vendor if needed.

Negotiation takes months. Banks are used to this. Vendors that try to close bank deals on retail-style commercial terms typically fail the procurement process regardless of technical capability.

Are banks actually using blockchain in production?

Yes. JPMorgan Kinexys handles billions of dollars of daily transaction volume. BlackRock BUIDL holds over a billion dollars in tokenized treasury assets. DTCC runs blockchain-based post-trade services. Swift is piloting cross-chain messaging with over thirty global banks. These are production programs with material scale.

Which blockchain do most banks use?

Ethereum dominates bank tokenization programs by total value because it offers institutional familiarity, deep liquidity, mature tooling. Ethereum layer-2 networks and purpose-built institutional networks (Canton, Provenance) also see significant bank adoption. Some banks run proprietary permissioned networks for specific programs.

Is blockchain banking secure?

Secure blockchain banking depends on the quality of the infrastructure, the security of the smart contracts, the key management architecture, the operational procedures of all participants. Well-designed bank blockchain programs have strong security posture. Poorly-designed programs do not. The technology itself does not determine security.

Will blockchain replace traditional banking?

No. Blockchain changes specific aspects of how banking works. It does not eliminate the need for banks. Banks provide services (credit creation, regulatory interface, fiduciary relationships, risk management) that blockchain technology does not replace. Blockchain is infrastructure that banks use, not a substitute for banks.

What role do oracles play in bank blockchain programs?

Oracles bridge off-chain data to on-chain smart contracts. For bank blockchain programs, oracles publish net asset values for tokenized funds, reference prices for tokenized commodities, proof of reserve attestations for backed assets, identity attestations for compliance enforcement. Without reliable oracle infrastructure, most institutional tokenized products cannot function.

Does Matrixed.Link work with banks?

Yes. Matrixed.Link is an institutional blockchain infrastructure provider and an official Chainlink node operator. We work with banks, asset managers, custody providers, other financial institutions on oracle infrastructure, managed node operations, validator services, blockchain consulting. We are independently certified for information security, with SOC 2 Type II currently in progress.

What certifications should bank blockchain vendors have?

Independent information security certification is the baseline. SOC 2 Type II is strongly preferred for US institutional procurement. Industry-specific certifications (PCI-DSS for payment-adjacent work, HIPAA for healthcare-adjacent work) apply to specific use cases. Banks typically request the full certification package during vendor evaluation.

About Matrixed.Link

Matrixed.Link is a specialized Web3 infrastructure provider and an official Chainlink node operator. We build and operate blockchain infrastructure for banks, asset managers, custody providers, payment networks, Web3 protocols.

We are the first Node Operator to build the first major RWA integration with over 100 million dollars in total value locked. Our infrastructure runs 500+ active Chainlink price feeds across Ethereum, Polygon, Arbitrum, Base. We operate Data Feeds, CRE, SVR, Proof of Reserve node types in production. We have pushed 12M+ data points on-chain through oracle operations. We validate proof-of-stake networks including Ethereum, Enjin, Polygon. Our Web3 API endpoints handle 2 billion daily requests through BoltRPC.

ISO/IEC 27001:2022 certified for Information Security Management Systems, effective February 2026. SOC 2 Type II currently in progress.

For financial institutions evaluating blockchain infrastructure, we provide consulting on architecture and vendor selection, specialized infrastructure operations under institutional SLAs, transition support from pilot to production, ongoing managed services for deployed programs.

Schedule a discovery call →

This article is for informational purposes only and does not constitute legal, tax, or investment advice. Consult qualified advisors before making decisions that affect your institution.

Sources & References

Authoritative sources cited in this article and recommended for further reading:

Work with Matrixed.Link

Matrixed.Link operates Chainlink oracle infrastructure, validator nodes, full-stack blockchain infrastructure for protocols and institutions that demand institutional-grade reliability. ISO/IEC 27001:2022 certified. AAA-rated by StakingRewards. Continuous operations since the Chainlink Oracle Olympics.

Long-term partnerships with Chainlink, Lido, Enjin, Stake.link, bitsCrunch.

Contact Matrixed.Link to discuss your infrastructure needs.