Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThe 2023 LF Decentralized Trust webinar on Hyperledger Besu and real-world asset (RWA) tokenization centered on a Spanish digital-bond platform described by ioBuilders. The presentation said the platform represented both a bond and cash as tokens and supported issuance, bond payments and delivery-versus-payment settlement on-chain. It was a discussion of an enterprise implementation—not a Besu tutorial or proof that tokenizing an asset automatically makes it legally compliant.
What the webinar covered
LF Decentralized Trust framed the session as a discussion of Besu’s role in real-world use cases managed by ioBuilders. Panelists Jorge Antolinez Ruiz and Carlos Contreras discussed RWA examples and highlighted a collaboration involving BME, BBVA and the Inter-American Development Bank. The central example in the presentation, however, was the BME Digital Bond Platform.
As an Amazon Associate I earn from qualifying purchases.
The session is useful for understanding how a blockchain network can fit into an asset platform and existing market processes. It does not provide a step-by-step Besu setup, a complete system architecture, or a controlled performance study.
Recommended Free Tools
What the BME digital-bond platform did
The webinar deck describes a native tokenized bond denominated and settled using tokenized cash. It says the platform covered the bond’s lifecycle on-chain, including issuance, coupon payments, principal repayments and delivery-versus-payment (DvP) settlement. In DvP, the security and payment legs are intended to transfer together, rather than leaving one side completed while the other remains outstanding.
#1 Best Overall
Roles of the blockchain and the platform
Besu is the blockchain infrastructure layer; it is not, by itself, the bond or the complete financial service. The deck says ioBuilders developed the end-to-end technology stack for issuance, management and trading, including the workflow enabling DvP between tokenized security and tokenized cash. The application and its integrations handle the asset lifecycle and institutional processes built around the network.
This distinction matters: a token can represent or track an instrument within a technical system, but the token alone does not settle the legal rights, obligations, eligibility rules or operating arrangements for that instrument.
Rank #2
What the deck says about the regulated setting
The presentation describes the project as built for a Spanish central securities depository (CSD), with the bond registered under a regulated CSD and supervised by Spain’s CNMV. It says the platform followed existing end-to-end regulatory processes rather than relying on a new exception. These are claims about the case as presented, not a legal conclusion that the same structure will work for another asset, offering or jurisdiction.
The webinar publisher described the collaboration as the “first regulated bond registered with blockchain in Spain”; the deck called it the “first digital bond registered under a regulated CSD.” Those are attributed descriptions of this project, not evidence of an unqualified global first.
Rank #3
Intended benefits versus measured outcomes
The deck presents reducing manual work and long settlement processes as project motivations, and increased efficiency and automation as intended value. It does not provide independent measurements establishing how much time, cost or error rate changed. Treat those benefits as the project’s rationale and stated aims, not as verified performance results.
Where Besu fits—and what the sources do not establish
Besu is an implementation of the Ethereum protocol. A 2020 Hyperledger overview discussed its use on Ethereum mainnet as well as private or consortium networks, and described enterprise-relevant topics such as permissioning, privacy, monitoring, deployment choices and consensus. Its account of IBFT 2.0 as a proof-of-authority option with immediate finality reflects the Besu 1.5-era context; it should not be read as current setup or production guidance.
Rank #4
The webinar deck supports the claim that ioBuilders delivered a broad platform stack, but the available description does not document every component, network configuration, integration or governance rule in the implementation. It also does not establish the legal enforceability of tokenized instruments generally. That depends on the instrument’s terms, jurisdiction and operating arrangements.
Other examples are different projects, not extensions of the BME case
Italian Besu security-token sandbox
Reply describes a separate Italian Security Token & Alternative Investment sandbox built on Besu for issuance, primary placement, real-estate asset events and secondary transfers. It identifies the trial as promoted by CeTIF, Reply and Fondazione CariVerona, with financial institutions participating, and says the sandbox ended at the end of 2021. It is evidence of a historical pilot, not proof of a continuing production market.
Best Value
Reply’s case-study text gives an Italian real-estate market capitalization figure of €7.89 trillion attributed to Reply in 2020. That is a historical, source-attributed figure, not a current valuation.
Later ioBuilders products on Hedera and HashSphere
Hedera’s ioBuilders case page describes a later portfolio context, including Asset Tokenization Studio, developed with Hedera and ecosystem partners, and Asseto, described as developed by ioBuilders and now offered by Hashgraph. The page says Asseto supports issuing, managing and trading tokenized instruments and digital cash on private HashSphere or public Hedera networks, with configurable compliance controls, lifecycle automation and integrations. These are not features established for the Besu-based BME bond implementation.
The same page reports more than 30 organizations using ioBuilders’ services and more than 50 bespoke client projects delivered, but does not state an as-of date for either total. They should be treated as publisher-reported figures without a specified reporting date.
How to evaluate an enterprise tokenization case
The webinar examples illustrate questions to ask when assessing a platform. A pilot, a completed issuance and an ongoing service are different levels of evidence; none should be treated as interchangeable.
- Network model: Is the system public, private or consortium-based, and who operates and governs it?
- Lifecycle coverage: Does it handle only issuance, or also servicing events, transfers and redemption?
- Settlement: Can the asset and payment legs settle together, and what does the implementation mean by DvP?
- Compliance and access: How are identity, participant eligibility, permissions and transfer restrictions handled under the applicable jurisdiction’s rules?
- Privacy and governance: Who can read transaction data, run nodes, validate transactions and change platform rules?
- Integration: How does the platform connect to custody, banking, settlement, reporting and existing market infrastructure?
- Evidence maturity: Is the claim about a concept, sandbox, pilot, completed issuance or continuing service, and what evidence supports it?
The cited examples do not provide a common benchmark or controlled comparison of these approaches. Their value is in showing different implementation contexts, not in establishing that one network or model is universally preferable.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




