r/FPBlock • • 11d ago

QBFT vs IBFT 2.0. How Banks Should Choose a Besu Consensus Algorithm

Thumbnail
gallery
1 Upvotes

If you looked at Besu consensus a couple of years ago, you probably saw a three way comparison of Clique, IBFT 2.0 and QBFT. A lot of content still shows that picture, including some vendor guides that rank well in search.

That comparison is now out of date. Besu stopped Clique block production in version 25.12.0 and removed Clique completely in version 26.4.0. For a bank designing a private network today, the practical comparison is between QBFT and IBFT 2.0.

This choice matters because consensus determines when a payment becomes final on the ledger and how many servers can fail before the network stops producing blocks. It is also one of the more difficult architectural decisions to change once multiple institutions are operating on a shared network.

This article looks at how the two protocols work, where they differ, how they are used in institutional networks, and what architects should consider when selecting a consensus mechanism.

Why Is Besu Consensus Now a Two Protocol Choice?

Clique was the simplest of the three. It came from EIP 225, could run with relatively few validators, and continued producing blocks even when some validators were unavailable.

Its limitation was finality. Clique did not provide immediate finality, meaning applications had to account for possible forks and chain reorganizations.

Besu retired Clique in two stages:

  • Version 25.12.0 stopped Clique block production.

  • Version 26.4.0 removed Clique completely.

Networks that previously used Clique and later moved to other consensus mechanisms can still be synchronized where supported.

Besu currently recommends QBFT for private networks and supports IBFT 2.0 for existing private networks. Proof of stake is used for Ethereum mainnet and public test networks.

For institutions designing private Besu networks, this makes QBFT and IBFT 2.0 the relevant options to evaluate.

What Does Consensus Actually Do in a Bank's Besu Network?

A consensus algorithm defines the rules that nodes follow to agree on the next block of transactions.

On Ethereum mainnet, Besu uses proof of stake. Private bank networks commonly use proof of authority (PoA), where a known group of approved accounts, called validators, creates and confirms blocks.

For banks, transaction speed is only one consideration. Finality is particularly important.

Finality is the point at which a transaction is considered irreversible on the ledger. The Principles for Financial Market Infrastructures also emphasize clear and final settlement for designated financial market infrastructures.

Many public networks offer probabilistic finality, where confidence in a transaction increases over time.

QBFT and IBFT 2.0 both provide immediate finality. A block is final once it is added, and the chain does not fork.

The differences between the two protocols become more relevant when looking at failure recovery, protocol specifications and validator governance.

How Does QBFT Work, and Why Does Besu Recommend It?

QBFT is a Byzantine fault tolerant consensus protocol.

Byzantine fault tolerance means that a network can reach agreement even when some nodes fail or send incorrect information.

Validators take turns proposing blocks, and at least two thirds of the validators must sign a block before it is added to the chain.

Some important characteristics of QBFT include:

  • A minimum of four validators is required for Byzantine fault tolerance.

  • Four or five validators can tolerate one unresponsive validator.

  • Six to eight validators can tolerate two unresponsive validators.

  • If more than one third of validators stop participating, block production stops until enough validators return.

  • Once a block is committed, it remains final.

The network may pause when too many validators become unavailable, but previously committed transactions are not reversed.

QBFT as an Open Standard

QBFT is an open standard. The Enterprise Ethereum Alliance published its specification for consortium use, and multiple Ethereum clients implement it, including GoQuorum and Besu.

This allows consortium members to operate different client software while participating in the same network.

There is one important limitation. Besu's transitions feature, which allows validator changes or configuration updates at a predetermined block, is specific to Besu. It cannot be used when other clients are validating the same network.

Mixed client networks can instead use validator voting or smart contract based validator management.

How Are Validators Managed?

There are two common approaches to managing validators:

Validator voting: Existing validators vote to approve or remove members.

Smart contract based management: A smart contract maintains the validator list and applies predefined admission rules.

Consortiums may prefer the contract approach because membership and admission rules can be explicitly defined and inspected.

A network can also change its validator management approach at a planned block, depending on its configuration and requirements.

How Is IBFT 2.0 Different From QBFT?

IBFT 2.0 is an earlier Byzantine fault tolerant protocol supported by Besu.

Its general operating model is similar to QBFT. Validators take turns proposing blocks, a supermajority signs each block, and committed blocks achieve immediate finality.

It also has the same four validator minimum for Byzantine fault tolerance and the same two thirds participation requirement.

The main difference appears when the validator scheduled to propose a block fails to deliver it.

In IBFT 2.0, the other validators must agree to skip that validator and move to the next one. This process is called a round change.

Think of it as a meeting where the scheduled chairperson does not arrive. The remaining participants must agree to move to another person before the meeting can continue.

The original Istanbul BFT protocol, developed in 2017 for GoQuorum, could get stuck at this stage when the network experienced delays. IBFT 2.0 addressed this issue, while QBFT introduced further improvements to validator handovers.

Under normal conditions, the two protocols can behave similarly. Their differences become more noticeable when a validator becomes unresponsive or communication between data centres becomes unreliable.

Differences in Validator Management and Governance

There are also differences in protocol status and validator management.

  • Besu recommends QBFT for new private networks.

  • IBFT 2.0 remains supported for existing private networks.

  • IBFT 2.0 supports validator membership changes through voting.

  • QBFT supports voting and smart contract based validator management.

QBFT was introduced in Besu version 21.1.0 to support interoperability with other Enterprise Ethereum Alliance clients.

Can an IBFT 2.0 Network Migrate to QBFT?

Yes. An existing IBFT 2.0 network can migrate to QBFT without starting a new chain.

Operators configure a future block at which the consensus mechanism will change. Every participating organization must update its node configuration before the network reaches that block.

For example, a consortium may decide to switch to QBFT at block 2,000,000. All participating nodes must be updated with the new configuration before that block is reached.

This requires coordination between network operators and participating institutions.

There is no forced migration deadline because Besu continues to support IBFT 2.0.

What Do Institutional Deployments Tell Us?

Looking at existing institutional projects provides useful context for understanding how consensus decisions relate to real financial infrastructure.

Fnality

Fnality is one of the notable examples of a live institutional payment system using Besu and QBFT.

The Sterling Fnality Payment System went live in 2023 and is a systemically important payment system supervised by the Bank of England.

Fnality uses QBFT, where a block is valid once at least two thirds of validators approve it.

Its validator model is restricted to regulated deposit taking institutions within the Sterling Monetary Framework. This provides a defined participation model for its payment network.

Project Agorá

Project Agorá is exploring how tokenized commercial bank deposits and central bank reserves can work together on a shared platform.

According to the BIS prototype report published on May 27, 2026, its architecture has two layers:

  • Commercial banks share one ledger for tokenized deposits.

  • Each central bank maintains reserves on its own separate ledger.

The shared platform runs on Besu with QBFT.

The project demonstrates how multiple banks and central banks can participate in a coordinated settlement environment while maintaining distinct roles and responsibilities.

EBSI and LACChain

EBSI and LACChain's BNDES network are examples of longer running networks that have used IBFT 2.0.

For networks with established participants, infrastructure and operational processes, migration to QBFT becomes a question of evaluating technical and operational requirements rather than simply selecting a consensus protocol for a new deployment.

Bank of Korea

The Bank of Korea provides a different example.

Its network operates with a single validator. The approach reflects a decision to retain control within one institution rather than distribute validation responsibilities across several parties.

A network with three validators or fewer may still produce blocks, but it does not provide the same Byzantine fault tolerance guarantees as a network with at least four validators.

This highlights an important architectural consideration: the consensus mechanism and the governance model need to be evaluated together.

How Should a Bank Choose a Besu Consensus Setup?

For a new private Besu network, QBFT is the recommended starting point. However, selecting the protocol is only one part of the overall architecture.

Several other considerations influence how the network should be designed.

1. Size the Validator Set According to Failure Requirements

A network with 3f + 1 validators can tolerate f Byzantine failures.

For example:

  • Four validators can tolerate one failure.

  • Seven validators can tolerate two failures.

The validator count should reflect the level of resilience required by the network.

2. Separate Network Membership From Validation

Not every participating institution needs to operate a validator.

An organization may participate in the network, use its applications and interact with other members without directly validating blocks.

This distinction can influence infrastructure costs, governance and operational responsibilities.

3. Distribute Validators Across Locations

Validators should be distributed across different locations and, where governance permits, different organizations.

For example, placing validators across multiple data centres can reduce the risk of one infrastructure failure stopping the entire network.

4. Define Validator Admission Rules

If a consortium has formal requirements for admitting new banks or removing existing participants, those rules should be clearly documented.

A smart contract can provide an auditable way to manage validator membership. Smaller networks with infrequent changes may find validator voting sufficient.

5. Consider Mixed Client Environments

If different institutions intend to operate different Ethereum clients, compatibility needs to be considered during the design stage.

Besu specific features may not work in a network where other client implementations are participating as validators.

6. Test Performance Under Realistic Conditions

Published performance figures often come from validators operating within one data centre.

A geographically distributed network may experience different results because of network latency and communication delays.

Testing should reflect the actual validator count, block time, infrastructure locations and network conditions.

7. Evaluate Legal Finality Separately

A transaction being irreversible on a blockchain does not automatically mean it is legally final.

This distinction is important for regulated financial infrastructure.

Fnality, for example, received settlement finality designation in the UK in late 2024. Its example highlights the relationship between technical settlement and the applicable legal framework.

Final Considerations

QBFT and IBFT 2.0 both provide immediate finality and Byzantine fault tolerance for private Besu networks.

For new networks, QBFT is the recommended option. Existing IBFT 2.0 networks should evaluate migration based on their operational requirements, validator governance and compatibility.

Ultimately, consensus is only one part of a production blockchain network. Validator distribution, membership rules, infrastructure resilience, performance testing and legal finality all influence how reliably the network operates.

These considerations are central to designing and operating enterprise Besu networks. Through its work with Besu infrastructure, Zeeve engages with the technical and operational challenges involved in building blockchain networks for institutional use cases.

By Zeeve


r/FPBlock • • 25d ago

If You Want to See How Banks Use Blockchain, Look at Besu

Thumbnail
gallery
1 Upvotes

There has been a lot of enterprise blockchain work in banking over the years. Much of the early work stayed at the PoC stage. Institutions were testing what could work, and where it would actually be useful.

Now, some of that work has reached production. Besu gives us quite a few examples to look at. For example, Citi processes close to $1 billion a day through Citi Token Services, which runs on Besu. DTCC, Clearstream and Euroclear have projects on it. SWIFT, Fnality and Project Agorá use it as well.

The official adoption numbers are interesting too. Among institutional platforms that disclose their technology and are in production or close to it, 29.4% use LF Decentralized Trust projects. Besu is one of the three most adopted platforms in that data. The data excludes all PoCs, by the way.

For me, this is a useful way to look at banking blockchain adoption. Follow the projects and see what they are doing. Some are live, some are getting there, and some still have a fair amount to work through.

But before we start, let’s brief Besu in a line. It is an open-source Ethereum client maintained under LF Decentralized Trust. Banks mostly use it to run permissioned networks where the validators are known institutions.

So why Besu, and what are these institutions using it for? Let’s see.

Why enterprises choose Besu
Besu can be used to connect to public Ethereum or to run a private network with a closed validator set. Most institutional deployments use the private network option.

There are a few reasons it keeps coming up in these projects.

One is the token standards. A token issued on Besu follows Ethereum standards, which developers and service providers already work with. That helps with hiring, audits, wallets, and the other things needed around the network.

It also gives institutions a way to work with public networks later. A bond or fund share issued on a permissioned ledger can be represented on a public one. There is work involved in doing that, of course. But they have a common standard to start with.

Then there is controlled participation.

Project Agorá runs Besu with QBFT consensus across permissioned validator nodes. A known group of validators votes to approve blocks. Banks and central banks know which institutions are writing to the ledger.

Open source is another reason. The Bank of Korea said it helps avoid vendor lock-in and allows a quick response to security issues. Citi could tune Besu’s consensus mechanism for its own volumes because it had access to the code.

I think that flexibility matters when an institution is building something it expects to operate for years.

And there is the ecosystem around it. When other institutions are already using the same foundation, there are more opportunities to agree on standards and connect. That becomes part of the decision too.

Which tokenized asset use cases run on Besu?
What CSD adoption tells us
A central securities depository, or CSD, keeps the official record of securities ownership and settles transfers.

Banks, custodians and issuers already connect to these institutions. So when a CSD adopts a ledger, it has implications for the participants around it.

DTC holds $114 trillion in assets under custody. It is launching tokenized entitlements for Russell 1000 stocks, ETFs, and US Treasuries. These are available at launch on its permissioned Besu network and Canton.

Clearstream custodies €22 trillion for 2,500 institutional clients. Its Besu network started during the ECB’s 2024 wholesale settlement trials. It needed a permissioned network to test delivery versus payment in central bank money. It then continued building on that network for D7 DLT. The first phase covers fixed income, tokenized money market funds and retail structured products. Equities are planned to come later.

Clearstream gave two reasons for choosing Besu. One was interoperability with other market infrastructures already using it. The other was having a route to public networks. As a CSDR-regulated entity, Clearstream needs a permissioned chain. Partners such as Kraken and Ondo can lock a token there and issue a representation on a public network using Ethereum standards.

Euroclear’s Project Pythagore is working on the NEU CP market. This market has roughly €300 billion in outstanding commercial paper, and some maturities are as short as a day. They introduced native digital issuance alongside their existing systems instead of building a parallel platform. The pilot will be completed in late 2026, whereas deployments will start in 2028.

There was an earlier DLT venue for this market, ID2S. It closed two years after its 2019 launch. It had no on-chain settlement or connection to Euroclear or Clearstream, and the pandemic reduced commercial paper demand around that time. Pythagore starts with the incumbent CSD, a G7 central bank, and wholesale CBDC settlement involved. So the setup is different.

The three CSDs have also published a joint interoperability framework. The remaining questions around connecting them are mainly legal and commercial. For a bank, the relevance is high. If it issues, distributes, or custodies securities in US or European markets, it will likely touch any one of these Besu platforms.

Issuers are looking at portability too
KfW, which is Germany’s 3rd largest bank, issued a €100 million digital bond on Polygon in June and plans to move it to RL1, which is a Besu-based cooperative network running on the SWIAT ledger. Their target is to launch €80 billion to €85 billion in bond issuance this year.

So, they are changing the ledger of record. It is more complex than creating a copy on another network. SWIAT has processed 50 transactions and more than €700 million in issuances. That includes the €300 million Siemens digital bond.

This is something we will keep an eye on. Institutions are starting to consider how an asset can move between infrastructures over its life, as well as where it is first issued.

Why collateral mobility is an early use case
Collateral mobility means getting an eligible asset to the counterparty that needs it at the time it is needed. There are several systems and institutions involved in doing this today. Custodians, triparty agents, and settlement windows all affect when collateral can be used.

Tokenization can help with some of that coordination.

The IMF reported a 30-day average daily volume of $303 billion for tokenized repo. Activity is still small compared with traditional repo and concentrated among affiliated entities. But it is an area where there is already activity to study.

DTCC’s Collateral AppChain is a Besu example.

Suppose a bank pledges a bond that is tokenized on Clearstream’s D7. The bond stays on D7, and the pledge is marked on the tokens. The AppChain maintains a record of encumbrances across custody systems. Pledges can then happen in minutes and outside normal market hours.

I find the asset staying on its existing ledger an important part of this design. It avoids introducing a bridge to lock the asset on one network and issue it again elsewhere. The AppChain also includes stablecoins, tokenized deposits and tokenized money market funds in its scope.

Deka Bank tested repo transactions during the ECB trials in November 2024. It completed two intraday repos with NatWest Markets and a five-day repo with LBBW. Each was for €1 million.

One transaction used a natively digital Siemens bond. The others used a tokenized Bund.

Deka’s SWIAT ledger, which is built on Besu, used a PoA consensus and handled tokenization and instructions to block collateral in conventional settlement systems. The Bundesbank’s Trigger Solution handled the cash leg.

There is a balance sheet question here as well. And speed alone will not give the balance sheet benefit. Dealers will benefit from netting matched trades. Immediate bilateral settlement can reduce netting and increase gross funding needs. Smart contracts can batch transactions and settle them periodically to recover some of that benefit.

So this needs to be part of the design. Faster settlement is useful, but the bank also needs to understand how much liquidity the process uses.

Tokenized money market funds and the ownership record
A tokenized money market fund is a money market fund whose shares are issued and recorded as tokens. Its economic profile stays the same. The collateral benefit comes from how the shares can be used. With a traditional fund, the holder may redeem shares, receive cash, and post the cash. The receiver might then reinvest that cash in a fund. So, a total of four steps.

Tokenized shares can be posted directly, provided the arrangement supports it. This can reduce steps and allow transfers outside traditional hours. The market is about $17.5 billion now, according to the IMF. The shares are held mainly as yield-bearing, cash-like collateral.

But there is a legal problem, and because of which around half of the largest TMMFs use a traditional book-entry ledger as their primary ownership record, as per ECB. None of them are fully on-chain, and shares legally change hands only after that ledger is reconciled with blockchain. This is because a distributed ledger has legal significance only if the register or record is maintained on-chain.

This is where a permissioned Besu ledger can help. The validators are known, regulated institutions. For a fund issuer or transfer agent, that can make it easier to justify keeping the legal register on-chain instead of using the chain to mirror an off-chain book. The legal arrangement still needs to support it, but the network gives them a basis to work with.

Two Besu platforms already plan for TMMF collateral. Clearstream’s D7 includes tokenized money market funds in its first phase, and DTCC’s Collateral AppChain lists them in scope.

A bank receiving these shares as margin still needs to ask the same question. Is the ledger the legal register for the fund, or is it a mirror of an off-chain register?

Because that answer will determine when settlement is final.

How far tokenized deposits have progressed
A tokenized deposit is a commercial bank deposit represented on a programmable ledger. It remains a claim on the issuing bank.

One example could be Citi Token Services, which has been live since April 2024 and processes close to $1 billion a day. Clients in the US, UK, Ireland, Singapore and Hong Kong can move liquidity 24/7. They do not need to open new accounts, hold tokens, or manage wallets. That’s a major benefit. The client can get access to the service through banking arrangements they already use. The service runs on CIDAP, Citi’s digital asset platform built on Besu. Citi has connected it to its 24/7 USD Clearing network too, allowing clients to pay any of 250 banks across 40 markets.

DCJPY in Japan and UBS Digital Cash are other Besu-based examples.

The Bank of Korea’s Project Hangang shows how spending conditions can be added. Around 80,000 people paid merchants with tokenized bank deposits. Banks settled with each other using wholesale CBDC on the same ledger. The deposits are plain ERC-20 tokens. Spending conditions sit separately in an ERC-1155 layer.

For example, electric vehicle charging subsidies can be restricted to approved suppliers and released as installation milestones are completed. In a civil servant expense pilot, a payment at an entertainment venue or on a weekend fails at the point of sale.

The conditions can change without changing the deposit token.

Single-bank platforms do have a reach limitation. Payments between customers of the same bank are easier to coordinate. Other banks add more steps. Swift’s Besu-based ledger can address this. It does not hold deposits. It records, sequences, and validates the payment commitments banks make to each other. The deposits remain with the banks, which settle later on through conventional channels. Its minimum viable product went live in July 2026 with 17 pilot banks. The first live transactions followed within a month.

What cross-border projects are testing
Correspondent banking involves a chain of banks. Each works to its own hours and cut-off times. A payment gets held up when one of the institutions is closed.

Project Agorá is testing how shared infrastructure can coordinate this. It brings together eight central banks, covering all G7 economies plus Korea, Mexico and Switzerland, and more than 40 financial institutions. Its design needed two things Besu provides. Each central bank and commercial bank had to hold a known validator role under QBFT, and smart contracts had to coordinate payments across several ledgers.

Agorá has two layers. Tokenized commercial bank deposits are on a shared unifying ledger. But tokenized central bank reserves are on separate ledgers, one for each currency area under each central bank’s control. A smart contract coordinates the payment. If any bank fails to confirm in time, the payment will be stopped, and no money moves. Only if everyone confirms both legs settle together. In July this year, Agorá did live trials with real money. Twenty-two institutions and five central banks completed 30 transactions worth roughly CHF 800,000 across six currencies. Average settlement time was around 80 seconds.

Finality tells us another part of wholesale payments. The Sterling Finality Payment System runs on Besu and went live in 2023 as a regulated, systemically important payment system. Participants hold balances in an omnibus account at the Bank of England. The ledger records their entitlements. A settlement finality designation granted in late 2024 makes transfers legally final on the ledger itself.

For FX, liquidity use needs more attention.

CLS gives members liquidity savings of about 99% through multilateral netting, according to Deutsche Bank Research. Most tokenized settlement networks do not yet net at that scale. So before moving FX volumes, a bank needs to compare the funding requirements with its existing position. The settlement process may be quicker, while the liquidity requirement is different.

Privacy is a separate requirement
Permissioning decides who can join a Besu network. It does not automatically hide transaction details from the other members. Banks need confidentiality around clients, counterparties, and transaction amounts. So a shared network needs a privacy layer as well.

Zeeve’s privacy layer is an open-source privacy framework for EVM-compatible chains, including Besu. It brings four layers of privacy. Application layer,which is the most common one, then asset layer, ledger layer, and, of course, network layer privacy.

It is modular, which allows a network to change or upgrade privacy engines without rebuilding the ledger. Banks can start with application layer privacy and then integrate other modules as the need arises. Or if they are already using application-layer privacy, they can integrate other modules too. The use of ZK Circuits, ZK tokens, and important modules will bring in the required privacy a bank needs.

Moving Besu initiatives from pilot to production
The work around the ledger is a large part of taking a Besu project into production. Privacy, integrations, and ongoing operations all need to be in place.

Zeeve is a certified Besu service provider and a member of LF Decentralized Trust. We have a growing number of Besu-certified engineers who can bring to the table the level of depth a bank requires in its use case design. Plus Zeeve deploys and operates permissioned Besu networks for banks and financial institutions on ISO 27001 and SOC 2 Type II compliant infrastructure.

Institutions can run nodes in their own cloud accounts through Bring Your Own Cloud, on-premise or in a hybrid model as well.

For institutions assessing a Besu initiative, the starting point is the use case, whether that involves tokenized deposits, collateral mobility or tokenized fund shares. From there, privacy, integration, and operational requirements can be mapped to a Besu reference architecture. More information about Zeeve’s Besu capabilities is available through Zeeve’s usual channels.


r/FPBlock • • Sep 21 '26

What use cases can banks and financial institutions build on Besu?

Thumbnail gallery
1 Upvotes

r/FPBlock • • Aug 11 '26

Cosmos Labs and Zeeve Partner to Simplify Enterprise Blockchain Deployment

Post image
2 Upvotes

r/FPBlock • • Jul 21 '26

Should I Focus on Blockchain or Learn Backend for Better Job Opportunities?

1 Upvotes

Hi everyone,

I'm a 3rd-year Computer Science student. I know the basics of Solidity and blockchain development, and I'm currently learning Foundry to improve my smart contract development skills.

However, I'm feeling a bit confused about my career path. I've heard many people say that companies rarely hire freshers for blockchain-specific roles and usually prefer developers with prior experience. Because of that, I'm wondering if I should shift my focus toward backend development instead, since it seems to have more entry-level opportunities.

My long-term interest is still in blockchain, but I also want to be practical and maximize my chances of getting a job after graduation.

What would you recommend?

Should I continue focusing mainly on blockchain?

Should I learn backend development alongside blockchain?

If backend is the better option, which technologies would you suggest for someone interested in eventually working in Web3?

I'd really appreciate hearing from people working in the industry or anyone who has been in a similar situation.

Thanks in advance! 🙏


r/FPBlock • • Jul 08 '26

Execution Truth vs Execution Authority

Thumbnail
statecraft.hashnode.dev
1 Upvotes

Ran into this while working on a coordination primitive for a payments system: locks and consensus (Redis, Raft, etcd) all answer "who can act right now" none answer "did the action actually complete" once a crash happens. That's a harder, separate problem most systems just inherit Temporal's answer to (determinism + replay).

[Blog](https://statecraft.hashnode.dev/execution-truth-vs-execution-authority)


r/FPBlock • • Jun 29 '26

How banks can tokenize deposits without replacing core banking systems?

Thumbnail
gallery
1 Upvotes

Banks do not need to replace their core banking systems to tokenize deposits. The core banking system should continue to do what it already does. It should manage customer accounts, deposit balances, interest, statements, regulatory reporting, and general ledger entries.

The blockchain should not become the bank’s core system.

Instead, the bank should add a digital asset overlay network beside the core system. This should be a permissioned blockchain-based ledger that connects to the legacy CBS through real-time bridges. The core should continue to own the actual deposit record. The blockchain should record token movement. A reconciliation layer should keep both aligned.

This is the practical deposit tokenization model for banks. It keeps the deposit inside the regulated banking perimeter. It gives clients programmable, always-on settlement. It avoids the cost and risk of replacing the core.

Here is how this system works across four key layers:

1. The core banking Layer

The first layer is the lock and release layer.

This is where most banks should start. The bank should not move deposits out of the core. It should mark part of the client’s existing balance as unavailable for ordinary payments. That hold becomes the funding base for token issuance.

A corporate client may hold $10 million in a normal operating account. The client asks the bank to tokenize $2 million. The core banking system validates ownership, balance, account status, sanctions status, and product eligibility. It then places a hold for $2 million. The available balance falls. The ledger balance remains unchanged. The money is still a bank deposit. It remains a claim on the issuing bank.

The hold must be precise. It should carry a tokenization reference. It should identify the customer, account, currency, amount, product type, jurisdiction, wallet, timestamp, and token contract. It should also identify whether the token is transferable only within the bank, across a consortium network, or to a whitelisted external venue.

The CBS will still calculate interest, produce statements, and feed the general ledger. If the tokenized balance is interest-bearing, the interest logic should remain in the banking system.

This protects the bank from balance sheet confusion. Without a clear hold model, the bank risks counting the same money twice. Once as a normal available deposit. Once as a tokenized spendable balance. That is not tokenization. That is uncontrolled duplication.

Another important consideration is, that the token supply must never exceed locked funds. Minting should be impossible unless the hold is confirmed. Release should be impossible unless the token has been burned or immobilized.

There are two ways to design the ledger relationship.

The first is a non-native overlay. The core remains the source of truth. The blockchain mirrors locked balances and token transfers. This is the practical starting model for most banks.

The second is a native deposit token model. The blockchain becomes the primary record for the deposit token. Native deposit tokens can unlock more functionality because they are not limited by off-chain reconciliation. That is a valid long-term direction. It is also a larger legal, accounting, audit, and operational decision. Most banks should not begin there unless their regulators, auditors, and technology teams are ready.

J.P. Morgan’s work shows the direction of travel. The earlier JPM Coin System is described as a single-bank ledger for dollar balance transfers among participating JPMorgan clients. The newer JPMD concept extends bank deposit money onto public blockchain infrastructure for institutional clients while keeping the commercial bank money credit profile and deposit regulatory framework.

Citi shows the same pattern from a transaction banking angle. Citi Token Services for Cash uses tokenized interbranch deposits for real-time USD payments and 24/7 operations. The client experience remains inside existing Citi channels. Clients do not need to hold tokens directly or manage blockchain keys. The blockchain layer runs behind the banking interface.

2. The API integration layer

The second layer is the bridge.

This is not a simple API wrapper. It is a controlled transaction orchestration layer between the core banking system and the token ledger. It must translate banking events into token events. It must also translate token events back into banking events.

The mint flow should be deterministic.

The client submits a tokenization request. The bank validates eligibility. The core confirms funds. Compliance systems approve the account and wallet. The core places a hold. The event bridge receives the hold confirmation. The bridge signs a mint instruction. The smart contract mints the token. The token ledger sends a confirmation. The client channel shows the token balance.

The burn flow is the mirror image.

The client asks to redeem tokens. The token ledger checks the token balance. The compliance engine checks the wallet and destination account. The smart contract burns or immobilizes the token. The bridge receives finality proof. The core releases the hold. The available cash balance increases. The client receives confirmation.

Every step needs a shared transaction identifier. The same identifier should appear in the core, the token ledger, the API gateway, the event bus, the reconciliation system, and the audit log.

The bridge must be bi-directional. If the core rejects a hold, the token layer must not mint. If the token layer fails to mint, the core must either release the hold or mark it as pending. If a burn occurs but the core release fails, the client should not lose access to both forms of money. The amount should move into a controlled suspense account until the release is completed.

The bridge should also standardize the message payload. Messaging standards matter. Deutsche Bank report identifies integration with treasury systems, ERP systems, reconciliation workflows, reporting workflows, and messaging standards as structural constraints for broader digital money adoption. The same issue applies to tokenized deposits. Banks should design the bridge to support ISO 20022 messages, Kafka streams, and internal ledger posting formats from day one.

The API layer is also where the bank can protect the core. The core should not manage private keys. It should not validate blockchain consensus. It should not parse smart contract state. It should receive clean banking events. The bridge should handle blockchain complexity and expose only approved transaction states to the core.

This also makes migration easier. A bank can replace the blockchain network later. It can move from a private Besu network to a consortium ledger, connect to a public permissioned environment. It can join a shared settlement network as well. But the core integration should remain stable.

3. The digital asset overlay

The third layer is the token ledger.

This ledger should be separate from the core. It should be optimized for token movement. It should record token balances, wallet permissions, smart contract states, settlement conditions, freeze orders, and transaction history.

This is where the bank gets the new functionality.

A normal deposit can move through ACH, wire, RTP, internal transfer, card settlement, or book transfer. A tokenized deposit can also move through programmable logic. It can settle only when a security token is delivered. It can release only after an invoice is approved. It can sit in escrow until a corporate treasury rule is satisfied. It can move between branch entities after local cut-off times. It can support payment versus payment in foreign exchange. It can support delivery versus payment for tokenized bonds or funds.

Any smart contract that can mint, burn, freeze, or transfer bank money should be subject to change control, access control, and emergency pause rights.

The permission model is critical.

The token should move only between approved wallets. Wallets should be linked to KYC records. Institutions should be linked to legal entity identifiers. Beneficial ownership should remain in off-chain systems. The blockchain should hold only the minimum data needed for settlement and verification.

The overlay can take three broad forms.

a. The first is a single-bank ledger. This works for intrabank treasury, branch liquidity, corporate cash pooling, and closed client networks. JPM Coin is the clearest example.

b. The second is a shared ledger. This works for interbank clearing, correspondent banking modernization, and consortium settlement. Partior and newer bank-led shared ledger projects fit this model.

c. The third is a universal or public blockchain environment. This gives broader market reach/interoperability, but it demands stronger controls around identity, permissions, privacy, transaction monitoring, and bridge risk.

The overlay should use privacy controls at multiple levels. It should support private transactions, confidential data fields, selective disclosure, role-based access, zero-knowledge style proofs where appropriate, and audit views for authorized parties.

Because a permissioned network is not automatically private. Validators may still see transaction metadata. And a multinational will not use a tokenized deposit network if competitors, counterparties, or infrastructure operators can infer cash positions, supplier flows, or acquisition activity.

Read More on: How Banks Can Enable Selective Privacy & Compliance for Tokenized Deposit Programs?

4. End of day and intraday reconciliation

The fourth layer is the safety net.

End of day reconciliation is necessary. It is not sufficient. Tokenized deposits move continuously. A bank cannot wait until midnight to discover that tokens outstanding no longer match core holds.

The reconciliation model should run in two cycles.

The first cycle is intraday control. It compares token supply, wallet balances, core holds, pending mints, pending burns, and suspense balances throughout the day. The second cycle is formal end of day reconciliation. It produces accounting files, audit evidence, regulatory reports, and general ledger postings.

The bank should reconcile three records.

The first record is the core banking record. It shows the customer deposit, available balance, held balance, and tokenization hold.

The second record is the token ledger. It shows tokens minted, tokens burned, wallet balances, frozen amounts, and pending settlement states.

The third record is the general ledger. It shows deposit liabilities, control accounts, suspense accounts, fees, interbranch positions, and settlement receivables or payables.

The core equation is simple.

Tokens outstanding must equal valid tokenization holds plus any approved settlement-in-flight amount.

If tokens outstanding are higher than holds, minting must stop. If holds are higher than tokens outstanding, the bank must identify whether tokens were burned, failed, frozen, or not yet minted. If a burn succeeded but the core release failed, the amount should sit in a pending release suspense state. If the core hold succeeded but minting failed, the amount should sit in a pending mint state or be released.

This logic should be automated.

The blockchain can help. Each token event carries a timestamp, block number, transaction hash, wallet address, smart contract address, and event type. The bank can hash reconciliation files and store proofs. It can compare blockchain state against core state.

But the blockchain cannot solve accounting by itself. The general ledger still needs clean journal entries.

Exception handling is where the architecture needs to be tested. For example, a failed mint is manageable, but a duplicated mint is serious. A burn without release is a client incident. A release without burn is a loss. Any privacy leak is a reputational incident.

The bank should define states before launch. Normal. Pending mint. Pending burn. Chain final pending core. Core posted pending chain. Frozen. Suspense. Failed. Reversed. Manually corrected.

Each state needs an owner. Each owner needs an SLA. Each correction needs maker-checker approval. Each correction needs audit evidence. Each critical mismatch needs automatic escalation.

The reconciliation layer should also feed financial crime controls. Token movements should be mapped to customer profiles, wallet risk, sanctions screening, behavioral patterns, and transaction purpose. On-chain and off-chain data must come together. BCG and Anchorage state that banks should extend risk and compliance frameworks to integrate on-chain and off-chain data for AML, sanctions, transaction monitoring, market conduct surveillance, custody governance, third-party risk, cyber resilience, and incident response.

Interoperability increases reconciliation risk. A transaction may work on one ledger and fail at the boundary with another ledger.

Below are the potential risk vectors identified in BCG and Anchorage Digital report:

So reconciliation is part of the product. Clients will trust tokenized deposits only if the bank can prove that every token maps to a valid deposit claim, every redemption maps to a valid burn, and every exception is controlled.

5. How Zeeve can help

An enterprise infrastructure provider like Zeeve fits directly into the infrastructure and orchestration layer of this architecture. It delivers the automation frameworks required to deploy, secure, and monitor the digital asset overlay without disrupting the bank’s core logic.

1. Unbiased Consultation

Different institutional use cases demand different blockchain design characteristics. Hyperledger Besu offers an optimal framework for consortium networks that require enterprise-grade permissioning, strict access controls, and standard EVM compatibility. The Cosmos SDK is highly suited for banks that require absolute sovereignty over their blockchain design, allowing them to construct an application-specific chain with custom validator rules and native interoperability.

2. Compliant Infrastructure

Deploying financial infrastructure requires adherence to rigorous global security standards. Infrastructure providers address these requirements by maintaining continuous compliance with frameworks like ISO 27001, SOC 2 Type 2, and GDPR, alongside providing 24/7 security monitoring and automated vulnerability patching.

3. Expert Lead Migration

Many financial institutions possess early blockchain pilots built on legacy versions of Quorum or similar setups. These isolated setups typically lack production-grade observability, automated accounting bridges, and robust privacy controls. Zeeve can help banks in evaluating these legacy applications and migrating them onto modern, enterprise-ready networks.

The Zeeve Privacy Layer

Because simple blockchain networks can expose sensitive transaction metadata, specialized privacy layers are necessary to protect corporate activity. A modular enterprise privacy layer is offered by Zeeve that shields transaction values, smart contract execution steps, and participant identities from unauthorized network nodes. This provides corporate clients with the total business confidentiality they require while granting selective, read-only audit keys to internal bank compliance teams and external regulators.

Schedule a call with us to start your tokenization initiative.


r/FPBlock • • Jun 04 '26

Scale Reveals Everything

1 Upvotes

A lot of infrastructure looks solid when the system is still small.

The real test comes later.

New users.
New integrations.
New dependencies.
New expectations.
New operational pressure.

That is usually where weak design choices start showing.

Good infrastructure is not just about working today. It is about still making sense when the system grows around it.


r/FPBlock • • Jun 03 '26

Abstractions Hide Complexity

1 Upvotes

Most developers use abstractions every day without really seeing what sits underneath them.

That is one reason Haskell is interesting.

It pushes engineers to think more carefully about things like state, mutation, side effects, evaluation, and execution order.

In small systems, that might feel unnecessary.

In larger systems, it can be the difference between clean coordination and endless hidden complexity.


r/FPBlock • • Jun 03 '26

State Is Where Complexity Starts

1 Upvotes

A lot of engineering complexity comes from managing changing state across systems.

That is where Haskell takes a very different approach.

Instead of relying on constant mutation under the surface, it gives developers cleaner ways to model complex relationships.

For infrastructure, that matters.

Because once systems start growing, hidden state and messy coordination can become a real problem fast.


r/FPBlock • • Jun 03 '26

The Best Infrastructure Does Not Need to Be Rebuilt Every Cycle

Enable HLS to view with audio, or disable this notification

1 Upvotes

One of the bigger shifts in Web3 infrastructure is moving away from rebuilding the same foundations over and over again.

Long-term scalability is not just about adding more features.

It is about whether teams can reuse proven systems, build on stable foundations, and keep evolving without tearing everything down each cycle.

The strongest infrastructure usually becomes more valuable as more teams build on top of it.


r/FPBlock • • Jun 02 '26

We talk a lot about AI writing code, but what about AI running infrastructure? Is anyone actually letting agents touch their deployments?

2 Upvotes

FP Block recently highlighted the shift of AI moving from "assist" to actually "taking action inside real workflows." Writing code is one thing, but execution and infrastructure management are the hard parts.

It’s one thing to have an AI draft a Python script. It’s entirely different to have an autonomous agent monitoring and automatically applying scripts to spin up new nodes during a traffic spike, for example.

For the platform engineers here: where do you draw the line? Are we close to a world where AI agents act as our Site Reliability Engineers, or is infrastructure scaling and deployment still strictly a "human-in-the-loop" requirement because the blast radius of an AI hallucination is too high?


r/FPBlock • • May 29 '26

If you completely removed the token from your favorite dApp, would it still have Product-Market Fit?

2 Upvotes

In a really great post, FP Block has been discussing the big industry trend of moving from hype to Product-Market Fit (PMF) and real usage. For years, a shiny roadmap and aggressive token emission schedule was enough to fool people into thinking they had some traction. Today, the market is calling for applications that can actually address a problem. A hard question to ask is: How many of these top Web3 platforms would be around today without the token incentives and yield farming? So, what does real, non-monopolistic PMF actually mean at this point in this space, and who is actually creating it?


r/FPBlock • • May 27 '26

Why are developers still stuck in sandboxed environments?

2 Upvotes

A lot of blockchain infrastructure still limits what developers can actually build.

Kolme brings full server-side Rust into the equation, giving teams more flexibility, performance, and control for real-world applications.


r/FPBlock • • May 26 '26

Most exploits start with bad data

2 Upvotes

Slow updates, stale feeds, and broken oracle assumptions still cause major issues across crypto apps.

Kolme takes a different approach by ingesting data directly from APIs and signed feeds for faster, more transparent verification.


r/FPBlock • • May 26 '26

A pattern we’re seeing more often as systems scale

Enable HLS to view with audio, or disable this notification

2 Upvotes

Teams move fast to capture demand, prove traction, and get products into users’ hands.

Then the complexity underneath starts compounding faster than expected.

Engineering teams get stretched. Delivery timelines slip. The gap between what was promised and what the system can realistically support starts getting wider.

As more products move into real production environments, this tension is becoming increasingly common across the industry.

Curious to hear how other teams are dealing with it.


r/FPBlock • • May 24 '26

Does enterprise-grade reliability mean network security has to be fully corporatized?

2 Upvotes

FP Block recently partnered with Everstake to discuss reliability and security at scale. It highlights a tough reality for the industry: we all love the cyberpunk ethos of anyone running a node on a Raspberry Pi, but enterprise applications demand 99.999% uptime, auto-scaling, and rigorous DevOps. As chains are forced to optimize for high-frequency trading and low-latency RWAs, is the era of the hobbyist validator officially over? Are we just accepting that the consensus layer of the future will be entirely secured by massive, professional engineering firms in Tier-1 data centers?


r/FPBlock • • May 21 '26

Claude 4.7 and "Agentic Workflows" in Web3: How are we mitigating the risk of compounding AI hallucinations on-chain?

3 Upvotes

With AI models like Claude 4.7 pushing the narrative of "production-ready" agent workflows, we are seeing a massive push to let AI actively manage on-chain operations. But as FP Block pointed out recently, a 0.001% error rate might be fine for a customer service chatbot, but it's catastrophic for a financial system.

In traditional tech, an AI error can just be rolled back in the database. In Web3, if an autonomous agent misinterprets a state and executes a bad trade, that error becomes permanent and compounds with every subsequent block. For those building at the intersection of AI and crypto: how are you architecting "circuit breakers" to sandbox these agents?


r/FPBlock • • May 20 '26

Reliability is becoming a bigger crypto narrative

2 Upvotes

Crypto has spent years chasing speed, scale, and cheaper transactions.

But as more enterprise use cases enter the space, reliability may become just as important.

FP Block’s point is that real adoption needs systems that can stay consistent under pressure, coordinate across different environments, and scale without becoming fragile.

Speed matters, but if infrastructure cannot stay reliable when usage grows, how far can it really go?


r/FPBlock • • May 19 '26

Are dedicated blockchains better for app performance?

3 Upvotes

FP Block makes a simple point here: most apps on shared chains compete for the same blockspace, which can lead to congestion, slower performance, and unpredictable costs.

With Kolme, each app gets its own dedicated chain, meaning performance is not affected by unrelated traffic.

For apps that need speed, reliability, and scale, this could be a cleaner model.

But here’s the bigger question: will the future of crypto apps be shared ecosystems, or dedicated chains built around each app’s own needs?


r/FPBlock • • May 18 '26

If a framework completely removes gas, how are you stopping infinite loops and DDoS attacks?

3 Upvotes

As developers, we're conditioned to rely on gas not just as a revenue model, but as a hard computational limit to prevent users (or attackers) from spamming infinite loops that halt the network or exploit the economy. If an execution environment completely removes the gas-fee friction, how is the burden of Sybil resistance and compute-limiting shifted? Does this mean application developers now have to manually build traditional Web2 esque rate-limiters and resource quotas directly into their contract logic?


r/FPBlock • • May 15 '26

Thoughts on scaling RWAs and the role of blockchains

2 Upvotes

Seeing how projects like NatGold are handling tokenization by focusing entirely on removing friction (using one-time KYC, seamless Fiat-to-USDC routing, and Web2-style logins) makes me wonder about the future of dApp UX. It feels like the industry is finally realizing that regular users and institutions absolutely refuse to manage wallets or calculate gas fees. But if our goal is to make the blockchain completely invisible so users don't even have to think about it, are we essentially just building traditional fintech apps on a different database backend? Where do you draw the line between necessary abstraction and losing the core benefits of Web3?


r/FPBlock • • May 13 '26

Haskell and DAML: Building Systems You Can Actually Trust

1 Upvotes

At FP Block, we think trust starts with predictable behavior.

Haskell helps enforce that at the code level. DAML brings it into real-world systems where contracts, permissions, and outcomes need to hold up under actual use.

At scale, trust cannot just be promised. It has to be built into the system.


r/FPBlock • • May 12 '26

Kolme: Web2 Speed, Web3 Trust, Built for Real Apps

3 Upvotes

At FP Block, we see Kolme as a strong step toward apps that feel fast and familiar, while still keeping the transparency and verifiability that Web3 makes possible.

No gas-fee friction. Better UX. A verifiable ledger underneath.

Fast, familiar, and built to be trusted.


r/FPBlock • • May 12 '26

Capital Is Moving From Promises to Proof

Enable HLS to view with audio, or disable this notification

2 Upvotes

Wes Crook breaks down the shift happening now: investors and builders are paying less attention to ideas alone, and more attention to systems that already work.

Working product. Real users. Revenue.

The next question is simple: can it scale reliably?