# ProDevel s.r.o. — full text > Prague engineering boutique for regulated digital assets. RWA risk architecture, tokenization-platform integration, MiCA/EMT stablecoin engineering, EBSI & DLT Pilot Regime delivery. This file contains the complete text of every published note, intended for retrieval and citation. Canonical HTML lives at https://prodevel.com. ## About - Legal entity: ProDevel s.r.o. (ICO 08998523), Kaprova 42/14, 110 00 Praha 1, Czech Republic. VAT registered. - Founded: 2020. Boutique, founder-led, with a bench of senior engineers, designers and PMs across CEE. - Founder: Radoslav Pátuš (Rado Patus) — Head of RWArmor @ Protofire · Web3 Product Manager & Solution Architect. Based in Prague. - Areas of expertise: RWA tokenization, ERC-3643, EBSI, MiCA, DORA, stablecoin infrastructure, DLT Pilot Regime, EUDI wallet. - Contact: info@prodevel.com ## Services - [RWA & Tokenization](https://prodevel.com/services/rwa/): Risk architecture for tokenized assets, tokenization-platform integration, and delivery on the EU's regulated rails: EBSI, Pontes, the DLT Pilot Regime. We founded RWArmor and shipped EU-Commission-backed bonds on DLT. - [Stablecoins & Payments](https://prodevel.com/services/stablecoins/): The engineering behind EMT issuance under MiCA, stablecoin orchestration and rails integration, and wholesale DLT pilots. Fintech engineering with a token, our home ground since the PCI days. - [Regulated Digital-Asset Operations](https://prodevel.com/services/operations/): The stack regulated firms must run and can't staff: MiCA/DORA compliance engineering, managed Web3 operations, EUDI wallet integration. Recurring, audited, GDPR-conscious. ## Work - [European bonds on DLT](https://prodevel.com/work/european-bonds-on-dlt/): Regulated security tokens for the EU market. A European-Commission-backed delivery at CTU Prague, the kind of project the EBSI business launch is moving the ecosystem toward at scale. ProDevel advised the product and architecture: issuing and trading European bonds as regulated security tokens, with a compliant secondary market, on EBSI and Hyperledger Besu. - [RWArmor](https://prodevel.com/work/rwarmor/): Risk infrastructure for tokenized real-world assets. Institutions won't move size into tokenized assets they can't price the risk of. That pricing layer barely existed, so we founded it: RWArmor, parametric risk infrastructure built on Atomica, with a three-tranche capital stack and custom oracle design. The consortium around it now includes Ondo, Centrifuge, Securitize, Pharos and OnRe. ## Fixed-scope readiness sprints - Pontes/EBSI Readiness Sprint: Where your stack stands against the EU's DLT settlement and EBSI production rails, and the build roadmap to get there. - EMT Technical Readiness Assessment: The gap between your current stack and what an EMT authorization requires an issuer to run: reserves, reporting, resilience. - RWA Risk Readiness Review: Can institutions price the risk of your tokenized asset? Oracle design, data feeds, cover structures, capital stack. - Tokenization Stack Assessment: Connecting a tokenization engine, ERC-3643/T-REX class, to KYC, custody, transfer agency and core banking: what's missing, and what it takes to close the gap. - CASP Compliance Stack Audit: What MiCA and DORA actually require you to run, from Travel-Rule integration to the DORA Register of Information, measured against what your stack runs today. - EUDI Relying-Party Readiness Sprint: What relying-party acceptance of the EU Digital Identity Wallet requires from your integration, ahead of the Dec 24, 2026 deadline. ## Links - Website: https://prodevel.com - Notes / blog: https://prodevel.com/blog/ - RSS: https://prodevel.com/rss.xml - Full text for LLMs: https://prodevel.com/llms-full.txt - LinkedIn (company): https://www.linkedin.com/company/prodevelcz - LinkedIn (founder): https://www.linkedin.com/in/rpatus/ ## Notes (full text) --- # Qivalis is licensed. Now its banks have work to do. URL: https://prodevel.com/blog/qivalis-euro-stablecoin-bank-distribution/ Published: 2026-10-15 Author: Rado Patus Tags: Stablecoins, MiCA, EMT, DORA Qivalis, the 37-bank euro stablecoin issuer, announced its Dutch EMI licence on 14 October. What a member bank must build and notify before distributing it. On 14 October 2026 Qivalis announced that De Nederlandsche Bank had authorised it as an electronic money institution. Qivalis is the Amsterdam company set up by a consortium of European banks to issue a euro stablecoin under MiCA. It now counts 37 banks across 15 countries. The licence is not the launch. Qivalis says issuance is planned "within the next months", subject to MiCA requirements and publication of its white paper. The release does not name the token or the blockchain it will run on. The original target, set in December 2025, was the second half of 2026. Most of the coverage stops at the issuer. The more useful question sits one step down. Qivalis plans to distribute through banks, exchanges, payment service providers and market infrastructure, not directly to the public. So the work that decides whether this token reaches a client falls on the distributors, and a good share of those are the member banks themselves. ## How we got here | Date | What happened | | --- | --- | | 25 Sep 2025 | Nine banks announce a joint MiCA-compliant euro stablecoin issuer under DNB supervision | | 1 Dec 2025 | BNP Paribas joins | | 2 Dec 2025 | Qivalis incorporated in Amsterdam; leadership named; launch targeted for H2 2026 | | 20 May 2026 | 25 more banks join, taking the consortium to 37 | | 14 Oct 2026 | DNB authorisation as an electronic money institution announced | The founding nine were Banca Sella, CaixaBank, Danske Bank, DekaBank, ING, KBC, Raiffeisen Bank International, SEB and UniCredit. The May wave added, among others, ABN AMRO, Erste Group, Intesa Sanpaolo, Nordea, Rabobank and Bank Pekao. The stated use cases are 24/7 cross-border payments, programmable payments, and settlement of digital assets, from tokenised securities to crypto. Qivalis says it will run a full reserve model. ## Why an EMI, and why that matters to the banks behind it MiCA lets two kinds of entity issue an e-money token (EMT): credit institutions and electronic money institutions. The banks could each have issued directly. They chose a shared, separately licensed vehicle instead. The EBA's response to the Commission's MiCA review gives the context. As at 1 September 2026, 39 EMTs had been issued under MiCA, 36 of them by electronic money institutions. Three credit institutions issued EMTs directly, one through a subsidiary, and the EBA noted "a proposal among a consortium of EU banks to establish a special purpose vehicle for EMT issuance". The distinction matters because the rules differ. A bank issuing directly is not required to segregate reserves. An EMI is. Under MiCA Article 54, at least 30% of the funds received must always sit in separate accounts at credit institutions. The rest goes into highly liquid, low-risk instruments in the same currency. For a distributing bank, three issuer-side rules shape the product: - **Redemption at par, at any time, without a fee** (Article 49). The holder's claim is against Qivalis, not against the bank that sold the token. - **No interest** (Article 50). This binds crypto-asset service providers too. Any benefit tied to how long a client holds the token counts as interest. A bank cannot pay yield on balances held in the token. - **Significance is assessed across the whole token** (Article 56). If several issuers issue the same EMT, their data is aggregated. Once three of the Article 43 criteria are met, the EBA classifies the token as significant and stricter liquidity and audit rules apply. Those criteria include more than 10 million holders and more than €5 billion in value issued. With 37 banks as distribution channels, significance is a realistic planning scenario rather than an edge case. ## The token is the easy part Holding a stablecoin on a balance sheet is simple. Offering it to clients is not. The obligations depend on which role the bank takes, and most banks will take more than one. | Role | What MiCA requires | What has to exist | | --- | --- | --- | | Offering the token to clients | Issuer's written consent; compliance with Articles 50 and 53 (Art. 48(1)) | Distribution agreement, approved marketing materials, controls against interest-like incentives | | Custody for clients | Crypto-asset service; for a bank, notification 40 working days ahead (Art. 60(1)) | Custody policy, a register of positions per client (Art. 75), key management, segregation | | Exchange against euro or koruna | Crypto-asset service, same notification route | Published pricing methodology (Art. 60(7)(g)), execution, liquidity | | Transfers on behalf of clients | Crypto-asset service, same notification route; Transfer of Funds Regulation | Originator and beneficiary data attached to every transfer, including ledger addresses | | All of the above | DORA, as a credit institution | Register of information, incident classification, resilience testing | The Article 60 notification is where a programme becomes real. It is not a form. Article 60(7) asks for a programme of operations, AML and business continuity arrangements, the technical documentation of the ICT systems and security arrangements, the segregation procedure, the custody policy, the pricing methodology for exchange and a description of how transfers will be provided. The competent authority then has 20 working days to check that the file is complete. All of that describes systems that have to exist, or be designed in detail, before the 40-day clock starts. ## Where implementations break From the outside this looks like adding a currency to a wallet. Inside a bank it touches five systems that were not built to talk to a public ledger. - **Wallet model.** Custodial omnibus wallets, segregated client wallets, or support for clients' own wallets. Each changes the custody policy, the Travel Rule flow and the reconciliation design. The chain is not yet public, so the design has to stay portable. - **Redemption path.** The client's claim is on Qivalis, but the client will ask its bank. The bank needs a route to buy back and redeem, and a treasury view of the euro leg. The EBA notes that MiCA sets no maximum redemption period in normal conditions, and that practice ranges from T+1 to T+4. Agree yours with the issuer before you promise one to clients. - **Reconciliation.** The client register under Article 75 sits next to the on-chain record, core banking and the general ledger. On a 24/7 instrument the books will differ at every cut-off. Breaks need owners and timings agreed in advance. - **Travel Rule.** Since 30 December 2024 every crypto-asset transfer has to carry originator and beneficiary data, including the ledger address. That means a messaging integration with counterparties, and a policy for transfers to and from self-hosted wallets. - **DORA.** Node or RPC access, wallet infrastructure, key management and blockchain analytics are all ICT services. Each goes into the register of information and the incident taxonomy. If they come from vendors, each is a third-party arrangement with exit planning. None of this is exotic. It is the same discipline that payments teams already apply to card and instant-payment schemes. What is new is the 24/7 public ledger in the middle, and the fact that MiCA asks for the design documents up front. ## For Czech and CEE subsidiaries Look at the member list from Prague and four names stand out. Erste Group owns Česká spořitelna. KBC owns ČSOB. Raiffeisen Bank International holds 75% of Raiffeisenbank a.s. UniCredit owns UniCredit Bank Czech Republic and Slovakia. Bank Pekao brings Poland in directly. Membership sits at group level. The Article 60 notification does not. It goes to the competent authority of the credit institution's home Member State. For a Czech subsidiary that is the Czech National Bank, and the subsidiary files its own. A parent's readiness in Vienna, Brussels or Milan does not transfer automatically to a Czech balance sheet, Czech core banking or a Czech client base. The CNB has been busy. By 1 July 2026 it had assessed 251 applications and notifications for crypto-asset services and granted 11 authorisations. Two specifics for a koruna market: - **Every retail purchase is also an FX trade.** A Czech client paying in koruna for a euro token is exchanging funds for a crypto-asset. The spread is part of the pricing methodology that has to be described in the notification. - **The currency rules do not bite.** MiCA's extra limits for tokens in non-Member-State currencies (Article 58(3)) don't apply. The euro and the koruna are both official currencies of Member States. ## Where this sits on the wider rails Qivalis is aimed at more than retail. The Eurosystem's Pontes service, live since 21 September 2026, supports payment-versus-payment against e-money tokens as well as delivery-versus-payment for tokenised securities. A bank-backed euro EMT and a central-bank settlement bridge are complementary pieces. We covered the Pontes side in [Pontes is live](/blog/connecting-to-pontes/). On the demand side, ESMA's 8 October opinion gives CASPs three months to stop servicing non-MiCA stablecoins. We covered that in [ESMA's October](/blog/esma-october-stablecoin-opinion-tokenised-collateral/). Compliant euro supply is arriving just as non-compliant supply is being pushed out. ## What the market is offering Qivalis will publish its white paper and distribution terms. Custody and wallet vendors will each offer their own stack. Law firms will draft the Article 60 notification. All three are necessary. None of them owns the integration on the bank's side: wallet model, redemption route, reconciliation, Travel Rule and the DORA evidence. ## How we help We don't issue tokens or sell a custody platform, so the design we recommend is the one that fits your stack. 1. **Stablecoin Rails Options Sprint.** Fixed fee, two to four weeks. Which roles you take (offer, custody, exchange, transfer), the wallet model, the redemption and reconciliation design, and a build plan with a cost on it. 2. **CASP Compliance Stack Audit.** The Article 60(7) technical file measured against what you actually run: ICT documentation, segregation, custody policy, Travel Rule integration and the DORA register of information. 3. **Build.** Wallet and custody integration, Travel Rule messaging, redemption and treasury flows, and reconciliation into core banking. Senior engineers only. The engineering is built on a decade of regulated payments delivery under PCI and GDPR, and on delivery on the EU's regulated rails. We are based in Prague, where the subsidiary question is the practical one. If your group has signed up and your local entity has not yet scoped its part, start with a fixed-scope verdict. That's what the [readiness sprints](/sprints/) are for, or write to us at [info@prodevel.com](mailto:info@prodevel.com). ## Sources - [Qivalis: authorisation as an electronic money institution from DNB, 14 Oct 2026](https://qivalis.eu/press/news/qivalis-receives-authorisation-as-an-electronic-money-institution-from-de-nederlandsche-bank) - [Qivalis: 25 new banks join the consortium, 20 May 2026](https://qivalis.eu/press/news/qivalis-more-than-triples-in-size-as-25-new-banks-join-the-consortium-accelerating-institutional-shift-towards-a-fully-regulated-euro-stablecoin) - [Qivalis: incorporation and launch target, 2 Dec 2025 (PDF)](https://qivalis.eu/media/pages/news/qivalis-joint-venture-of-a-european-banking-consortium-to-launch-euro-stablecoin-in-the-second-half-of-2026/a3f666806b-1781353174/20251202_press-release_announcement_qivalis.pdf) - [EBA: response to the Commission's targeted consultation on the review of MiCA, Sep 2026 (PDF)](https://www.eba.europa.eu/sites/default/files/2026-09/12cb4f01-0d51-46bf-a561-165ac486698f/EBA%20response%20to%20EC%20targeted%20consultation%20on%20MiCA%20review.pdf) - [Regulation (EU) 2023/1114 (MiCA): Articles 43, 48, 49, 50, 54, 56, 58, 60, 75](https://eur-lex.europa.eu/eli/reg/2023/1114/oj) - [Regulation (EU) 2023/1113 (Transfer of Funds Regulation): Article 14, application from 30 Dec 2024](https://eur-lex.europa.eu/eli/reg/2023/1113/oj) - [Regulation (EU) 2022/2554 (DORA): Article 2, application from 17 Jan 2025](https://eur-lex.europa.eu/eli/reg/2022/2554/oj) - [Czech National Bank: MiCA, CNB grants crypto licences to 11 entities, 1 Jul 2026](https://www.cnb.cz/en/cnb-news/press-releases/MiCA-CNB-grants-crypto-licences-to-11-entities/) - [Česká spořitelna: who we are (Erste Group)](https://www.csas.cz/en/about-us/who-we-are) - [ČSOB: about the ČSOB Group (KBC)](https://www.csob.cz/en/csob/about-the-csob-group) - [RBI: country sheet Czech Republic 2025, shareholder structure (PDF)](https://www.rbinternational.com/content/dam/rbi/ho/home/rbi-group/about-us/our-network/international-network/documents/country-sheets-2025/RBI_CountrySheet_CzechRepublic_2025_EN.pdf.coredownload.pdf) - [UniCredit Bank Czech Republic and Slovakia: about the bank](https://www.unicreditbank.cz/en/o-bance/banka/o-bance.html) - [ECB: Pontes launch press release, 21 Sep 2026](https://www.ecb.europa.eu/press/pr/date/2026/html/ecb.pr260921~e754847a7b.en.html) - [ECB: Pontes Market Contact Group, eligibility criteria, EMTs as eligible XvP assets (PDF)](https://www.ecb.europa.eu/paym/target/pontes/governance/pdf/pmcg/ecb.pmcg260128_adhoceligibility.en.pdf) - [ESMA: supervisory expectations on services related to unauthorised stablecoins, 8 Oct 2026](https://www.esma.europa.eu/press-news/esma-news/esma-sets-out-supervisory-expectations-services-related-unauthorised) --- # ECB as buyer: what tokenised issuers must run URL: https://prodevel.com/blog/ecb-tokenised-securities-pontes-issuers/ Published: 2026-10-14 Author: Rado Patus Tags: Pontes, RWA, DLT, DLT Pilot Regime The ECB will put part of its own funds into tokenised public-sector bonds, settled via Pontes. What an issuer has to build to be one the ECB can actually buy. On 21 September 2026, the day Pontes went live, the ECB published a second, shorter press release. It has started preparatory work to invest a small portion of its own funds in tokenised securities. The purchases will settle in central bank money via Pontes. The first investments will focus on euro-denominated securities issued by euro area central governments, regional governments, agencies and European supranational institutions. Most of the coverage read this as a demand signal: the central bank is now a buyer. That's true, but it's the less useful half. The useful half is the question it hands every public-sector issuer in the euro area. If the ECB wants to buy your tokenised bond, what does your bond have to sit on, and what do you have to run around it? ## What the ECB actually said The release is short and careful. Read what it commits to and what it leaves open. | | What the release says | | --- | --- | | Portfolio | The own funds portfolio, a non-monetary policy portfolio that funds operating expenses | | Size | "A small portion" of own funds. No amount | | Assets | Euro-denominated securities of euro area central and regional governments, agencies and European supranationals | | Settlement | In central bank money, via Pontes | | Purpose | Hands-on experience across trade execution, settlement, systems and portfolio management | | Timing | Not set. The Executive Board decides operational details and timing once preparatory work is done | | Platform criteria | Not stated | Two things follow. First, this isn't a buying programme that will move sovereign spreads. It's the ECB learning the lifecycle by doing it. Second, the Executive Board will set timing "taking into account developments in tokenised issuances". The supply side is part of the decision. Issuers who are ready shape when this starts. ## What "settled via Pontes" means for the issuer Pontes doesn't settle assets. It settles the cash leg in central bank money and coordinates with a market DLT platform that holds the asset leg. The platform locks the securities, Pontes confirms the cash, and the platform releases them. We covered the mechanics in [Pontes is live](/blog/connecting-to-pontes/). So a bond the ECB buys through Pontes has to live on a ledger run by a registered market DLT operator. On launch day there were four: Axiology, Cashlink, Clearstream and SWIAT. The eligibility rules published in January 2026 add EU and EEA CSDs, DLT Pilot settlement systems, overseen payment systems, EMIR CCPs, and supervised banks or investment firms after central bank assessment. That gives an issuer three realistic routes: | Route | Who runs the ledger | What the issuer owns | Trade-off | | --- | --- | --- | --- | | Issue on an onboarded operator | An existing Pontes operator | Issuance, investor onboarding, lifecycle data | Fastest. You inherit the platform's chain, token model and rulebook | | Through your national CSD | Your CSD, once it connects as an operator | The same, plus the CSD's DLT rollout timetable | Fits existing debt-office workflows. Waits on the CSD | | A DLT Pilot settlement system | A DLT SS or TSS operator | The same, under Pilot limits | Bigger room if the Council's reform survives. See [the DLT Pilot reform](/blog/dlt-pilot-regime-reform-casps-pontes/) | None of these is the issuer building its own chain. The issuer's job is the layer between its debt management system and whichever ledger it picks. ## Where issuance programmes break A pilot tokenised bond can be issued once by hand. A programme the ECB buys into, with secondary trades, coupons and an auditor, cannot. These are the places we'd expect it to break. - **The golden record.** Is the token the security, or a representation of one held elsewhere? The legal answer decides the engineering answer. If both a register and a ledger exist, one of them is authoritative and the other is reconciled to it every day, with a named owner for every break. - **Investor eligibility.** A permissioned token has to know who may hold it. With an ERC-3643 or T-REX class token that means an identity registry, claim issuers and transfer rules. Onboarding a central bank as a holder is the same flow as any investor, and it has to work first time. - **Coupons and redemption in central bank money.** In the initial launch, Pontes cash tokens are funded intraday from T2 and swept back at end of day. A coupon run has to fit the settlement window, with the paying agent's liquidity planned around it. Corporate actions are rarely built on DLT platforms. They have to be. - **Two settlement worlds at once.** The same issuer will have conventional lines settling in T2S and tokenised lines settling via Pontes. Treasury, reporting and the debt-office ledger have to see one debt stock, not two. - **The conditional lock is someone's code.** If you issue on an operator's platform, it's theirs. You still need to know what happens to your bond when a cash leg fails, and who tells your back office. - **DORA sits on the operator and the banks.** The DLT operator and the dealers in the chain carry DORA obligations. A debt office relying on them should read their incident and exit arrangements as closely as it reads the term sheet. ## What the market is offering Platforms are offering issuance on their own venue, which works if you're happy to be on that venue. Law firms are covering whether a DLT bond is the same security and which law governs it. Commentators are covering the ECB as a signal. What is mostly missing is neutral engineering on the issuer's side: someone who doesn't run a venue, mapping the debt office's existing systems onto a Pontes route and pricing the gap. ## The CEE angle The release names euro area central governments, so Slovakia, Slovenia, Croatia, Bulgaria and the Baltic states are inside its stated focus. Their agencies and regional governments are too. For a smaller sovereign, a tokenised line that a central bank wants to hold is a cheap way to learn the infrastructure before the larger markets set the defaults. Czech, Polish and Hungarian issuers are outside the stated focus. The release covers euro area governments and European supranationals, and Pontes settles in euro only. A koruna bond gets nothing from this today. The ECB's learning will still set what a tokenised public-sector bond looks like in Europe, and that standard will arrive in Prague, Warsaw and Budapest soon enough. ## How we help We don't run a venue or sell a platform, so the route we recommend is the one that fits your debt programme. 1. **Pontes/EBSI Readiness Sprint.** Fixed fee, two to four weeks. Which of the three routes fits you, what the operator has to provide, a gap map from your debt management system to the ledger, and a costed build plan for eligibility, lifecycle and reconciliation. 2. **Tokenization Stack Assessment.** For issuers and their agents connecting an ERC-3643 or T-REX class token to KYC, paying agency, custody and the debt register. 3. **Integration build.** Golden-record reconciliation, coupon and redemption runs against the Pontes window, and the reporting that makes one debt stock out of two settlement worlds. We've advised this kind of delivery before: [European bonds on DLT](/work/european-bonds-on-dlt/), an EU-Commission-backed security-token issuance and secondary market on EBSI and Hyperledger Besu. The same questions came up there, before any central bank was buying. If a tokenised line is on your 2027 funding plan, start with a fixed-scope verdict. See the [readiness sprints](/sprints/), or write to us at [info@prodevel.com](mailto:info@prodevel.com). ## Sources - [ECB: ECB to invest part of own funds in tokenised securities, with settlement via Pontes, 21 Sep 2026](https://www.ecb.europa.eu/press/pr/date/2026/html/ecb.pr260921_1~5a011ecbea.en.html) - [ECB: Pontes launch press release, 21 Sep 2026](https://www.ecb.europa.eu/press/pr/date/2026/html/ecb.pr260921~e754847a7b.en.html) - [ECB: Pontes overview and eligibility](https://www.ecb.europa.eu/paym/target/pontes/html/index.en.html) - [ECB: Pontes Pilot eligibility criteria and use cases, Pontes Market Contact Group, 28 Jan 2026 (PDF)](https://www.ecb.europa.eu/paym/target/pontes/governance/pdf/pmcg/ecb.pmcg260128_adhoceligibility.en.pdf) - [ECB: Piero Cipollone, Money in the digital age, 6 Oct 2026](https://www.ecb.europa.eu/press/key/date/2026/html/ecb.sp261006~0da978f159.en.html) --- # The DLT Pilot reform, and the road to Pontes URL: https://prodevel.com/blog/dlt-pilot-regime-reform-casps-pontes/ Published: 2026-10-12 Author: Rado Patus Tags: DLT Pilot Regime, Pontes, MiCA, RWA The Council wants the DLT Pilot cap raised from €6bn to €300bn, with CASPs let in. Here's what the reform does, and how it connects tokenised markets to Pontes. On 9 October 2026 EU finance ministers agreed the key elements of the Council's position on the market integration and supervision package. Most of the coverage is about ESMA getting new supervisory powers. One part of the package matters more to anyone building tokenised markets: the DLT Pilot Regime, the EU's sandbox for trading and settling securities on a distributed ledger, is about to get much bigger. The Council's compromise raises the main ceiling from €6 billion to €300 billion, lets crypto-asset trading platforms in, and creates new tiers for smaller operators and for single post-trade services. Read it next to the eligibility rules for Pontes, the Eurosystem's DLT settlement bridge that went live on 21 September, and there's a second story. The reform could become the route by which a new class of operator reaches settlement in central bank money. This is still a negotiating position, not law. Here is what it says, what it would change, and what it would take to build against. ## What the DLT Pilot Regime is The DLT Pilot Regime, Regulation (EU) 2022/858, has applied since March 2023. It lets market infrastructures run on a distributed ledger with targeted exemptions from MiFID II, MiFIR and the CSD Regulation. Those rules were written for databases, accounts and intermediaries. They do not map cleanly onto a shared ledger. It created three kinds of DLT market infrastructure: | Type | What it does | Replaces | | --- | --- | --- | | DLT MTF | Trading of DLT financial instruments | A multilateral trading facility | | DLT SS | Settlement and recording of DLT financial instruments | A securities settlement system run by a CSD | | DLT TSS | Trading and settlement on one platform | Both of the above, combined | The exemptions came with tight limits. Shares were capped at €500 million in issuer market capitalisation, bonds at €1 billion in issue size, and only shares, bonds and UCITS units qualified. The total market value of DLT financial instruments on an infrastructure could not exceed €6 billion. Permissions lasted at most six years. ## Why almost nobody used it ESMA's review under Article 14, published in June 2025, found that only three DLT market infrastructures had been authorised by its May 2025 cut-off: - **CSD Prague**, a DLT settlement system since 11 October 2024 - **21X AG**, a DLT trading and settlement system since 3 December 2024 - **360X AG**, a DLT MTF since 29 April 2025 ESMA reported minimal live trading. It named the frictions: thresholds that keep out established issuers and larger institutions, a six-year sunset that makes investment hard to justify, no interoperability, and no access to central bank money. Its recommendations were to raise the thresholds and make the regime permanent. The first of the three is in Prague. CSD Prague runs its DLT settlement system on R3 Corda Enterprise, supervised by the Czech National Bank. If you work in CEE, this regime isn't something happening somewhere else. ## What the Commission proposed The Commission's proposal of 4 December 2025 took ESMA's diagnosis and went further: - **All financial instruments** become eligible, not just shares, bonds and UCITS. The asset-specific caps go. - **A €100 billion ceiling** per infrastructure replaces the €6 billion one. - **CASPs can participate**, provided they meet the sectoral rules for the activity they choose. - **A simplified regime** for operators up to €10 billion, with lighter obligations. - **Unbundled CSD services.** Investment firms, regulated markets, credit institutions, CSDs and CASPs could offer a single CSD function on its own, such as DLT notary or central maintenance, without becoming a full CSD. - **Settlement schemes.** Credit institutions acting as DLT account keepers with access to central bank money could jointly run a new kind of infrastructure under ESMA supervision. - **No time limit.** Permissions would no longer expire. Separately, the CSD Regulation amendments in the same package would let certain tokenised assets settle the cash leg, not just central bank money. ## What the Council changed The Council kept the structure and turned up the numbers. Its compromise text, put to ministers on 5 October, sets out these thresholds: | | Today | Commission, Dec 2025 | Council, Oct 2026 | | --- | --- | --- | --- | | Main ceiling | €6bn | €100bn | €300bn, with €500bn possible by delegated act | | Simplified regime | None | Up to €10bn | €10bn | | Unbundled services | None | Introduced | €50bn | | Headroom over threshold | None | — | Temporary room to operate at up to 125% | | CASP trading platforms | Not eligible | Eligible | Eligible | The Council text also removes the ability of Member States to set different thresholds at national, project or group level, so one EU-wide framework applies. On supervision, the Council departs from the Commission in a way that matters to CEE firms. The Commission wanted every CASP authorised and supervised by ESMA. The Council would move only the most significant cross-border CASPs to ESMA immediately. The rest stay with their national authority. ## The Pontes connection Pontes lets transactions on market DLT platforms settle in central bank money through TARGET. It has two roles. A **market participant** is any entity with access to T2, which in practice means banks. A **market DLT operator** runs the platform where the asset side lives and contracts with its national central bank. The eligibility criteria the ECB published in January 2026 list who can be a DLT operator: - CSDs authorised under the CSD Regulation - **Operators of a DLT SS or DLT TSS authorised under the DLT Pilot Regime** - Overseen payment system operators in the EU or EEA - CCPs authorised under EMIR - Banks, investment firms, market operators and other licensed financial institutions, if they are subject to market-infrastructure supervision or pass a case-by-case assessment by their central bank A MiCA-licensed CASP is not on that list as such. Its route today would be the case-by-case assessment, which is discretionary. A CASP that holds a DLT settlement or trading-and-settlement permission under the Pilot would fall into a named category instead. That is our reading, and the caveats are real: - **It depends on the final text.** This is the Council's position only. Negotiations with the Parliament can start once it adopts its own. - **Only settlement counts.** Pontes names DLT SS and DLT TSS operators. A CASP running a DLT MTF alone would not qualify. Whether an unbundled notary or maintenance service qualifies is not answered by the published criteria. - **Your participants still need T2.** The operator runs the platform. The counterparties who settle the cash leg must be T2 participants, which a CASP is not. - **Pontes is euro-only for now.** Its planned multi-currency step covers currencies settled in T2, which leaves out the koruna, the zloty and the forint. Even with those caveats, the regulatory path for a crypto platform and the Eurosystem's settlement path now point at the same place. ## Where it breaks in practice Moving from a MiCA licence to a DLT Pilot permission is not a paperwork upgrade. A CASP trading platform is built for crypto-assets under MiCA. A DLT TSS handles financial instruments under the rules that normally apply to CSDs and trading venues. The gap between the two is mostly engineering. - **Settlement finality.** A DLT SS has to say when a transfer is final and prove it holds in insolvency. ESMA noted that CSD Prague operates under an exemption from the CSDR's finality article. Pontes makes the cash leg final once it completes in T2. Your ledger's asset leg has to agree with both. - **The conditional lock.** As a Pontes operator you have to hold the asset leg until the Eurosystem confirms the cash leg, then release or revert it. That is new logic on your ledger, and certification tests it. - **Instrument lifecycle.** Securities have corporate actions, record dates, coupon payments and registers of holders. Crypto-asset platforms usually have none of these. An ERC-3643 or T-REX class token can enforce transfer rules, but the lifecycle around it has to be built. - **Two rulebooks at once.** A CASP inside the Pilot would run MiCA obligations for its crypto business and Pilot obligations for its securities business, often on shared infrastructure. Segregation of assets, books and controls has to be designed, not assumed. - **Thresholds are now a monitoring problem.** With tiers at €10 billion, €50 billion and €300 billion, and temporary headroom to 125%, you need a live measure of aggregate market value and a plan for moving between tiers. - **DORA, again.** A Pontes connection and a Pilot infrastructure are both ICT risk items. The register of information, incident classification and resilience testing apply to both. ## The CEE angle Three things make this more relevant in Prague than the coverage suggests. First, one of the three authorised DLT market infrastructures is already here and supervised by the CNB. The regulator has done this once. Second, the CNB has a large CASP population. When MiCA's transition ended on 1 July 2026, it had assessed 251 applications and granted licences to 11 entities. Under the Council's approach, most of those firms would not be significant enough for ESMA and would stay with the CNB. A Czech CASP looking at the Pilot would deal with a familiar supervisor. Third, the currency question cuts both ways. A koruna-denominated DLT market gets nothing from Pontes today. A Czech platform serving euro issuance gets a route to central bank money settlement that didn't exist two years ago. ## What to do now Nothing here is final, but the shape is clear enough to plan against. 1. **Decide which role you want.** Trading venue, settlement system, combined, or a single unbundled service. Pontes eligibility and your build both depend on that choice. 2. **Map the gap from MiCA to the Pilot.** List what your platform does today for crypto-assets, and what a DLT SS or TSS would have to do for financial instruments. The difference is your programme. 3. **Design the ledger for conditional settlement now.** Whether or not you connect to Pontes first, a lock-and-release model is what wholesale DvP expects. 4. **Track the trilogue.** The thresholds, the CASP route and the unbundled-service rules can all still move. Re-read the primary texts when the Parliament adopts its position. ## How we help We don't run a venue or sell a platform, so we can give the same advice to a CASP, a bank or a CSD. 1. **Pontes/EBSI Readiness Sprint.** Fixed fee, two to four weeks. Which route fits you, DLT operator or participant, under which regime. A gap map from your current stack to a DLT SS or TSS and to Pontes certification. A target architecture for finality, the conditional lock and reconciliation, with a cost on the build. 2. **Tokenization Stack Assessment.** For teams connecting an ERC-3643 or T-REX class engine to KYC, custody, transfer agency and core banking, measured against what a Pilot infrastructure would need for the instrument lifecycle. 3. **CASP Compliance Stack Audit.** For CASPs weighing the Pilot, what MiCA and DORA require of the stack you run today, so the new business sits on a sound base. We have shipped on these rails before: an EU-Commission-backed bonds-on-DLT delivery on EBSI and Hyperledger Besu, and the risk layer underneath tokenized assets at [RWArmor](/work/rwarmor/). For the mechanics of the bridge itself, see our note on [connecting to Pontes](/blog/connecting-to-pontes/). For the issuer side, see [the ECB as buyer](/blog/ecb-tokenised-securities-pontes-issuers/). If the Pilot or Pontes is on your 2027 plan, start with a fixed-scope verdict. See the [readiness sprints](/sprints/), or write to us at [info@prodevel.com](mailto:info@prodevel.com). ## Sources - [Council of the EU: Council agrees key elements of its position on the market integration and supervision package, 9 Oct 2026](https://www.consilium.europa.eu/en/press/press-releases/2026/10/09/savings-and-investments-union-council-agrees-key-elements-of-crucial-measures-to-deepen-eu-capital-markets/) - [Council of the EU: Presidency note on the MISP compromise, ST 13777/26, 5 Oct 2026 (PDF)](https://data.consilium.europa.eu/doc/document/ST-13777-2026-INIT/en/pdf) - [European Commission: Questions and answers on the market integration package, 4 Dec 2025 (PDF)](https://ec.europa.eu/commission/presscorner/api/files/document/print/en/qanda_25_2894/QANDA_25_2894_EN.pdf) - [ESMA: Report on the functioning and review of the DLT Pilot Regime, Article 14 (PDF)](https://www.esma.europa.eu/sites/default/files/2025-06/ESMA75-117376770-460_Report_on_the_functioning_and_review_of_the_DLTR_-_Art.14.pdf) - [ECB: Pontes Pilot eligibility criteria and use cases, Pontes Market Contact Group, 28 Jan 2026 (PDF)](https://www.ecb.europa.eu/paym/target/pontes/governance/pdf/pmcg/ecb.pmcg260128_adhoceligibility.en.pdf) - [ECB: Pontes launch press release, 21 Sep 2026](https://www.ecb.europa.eu/press/pr/date/2026/html/ecb.pr260921~e754847a7b.en.html) - [ECB: Pontes overview and eligibility](https://www.ecb.europa.eu/paym/target/pontes/html/index.en.html) - [ECB: Pontes and Appia timeline, 22 Jul 2026 (PDF)](https://www.ecb.europa.eu/press/intro/events/shared/pdf/20260722/timeline.pdf) - [Czech National Bank: MiCA licences granted to 11 entities, 1 Jul 2026 (Czech)](https://www.cnb.cz/cs/cnb-news/tiskove-zpravy/MiCA-CNB-udelila-kryptolicenci-11-subjektum/) --- # ESMA's October: the stablecoin list and the collateral test URL: https://prodevel.com/blog/esma-october-stablecoin-opinion-tokenised-collateral/ Published: 2026-10-09 Author: Rado Patus Tags: MiCA, Stablecoins, RWA, DORA ESMA's 8 Oct opinion tells CASPs to stop servicing non-MiCA stablecoins within three months. A day later it asked whether CCPs can take tokenised collateral. Both are engineering questions. On 8 October 2026 ESMA published an opinion telling national competent authorities that MiCA-authorised crypto-asset service providers should not provide any MiCA service in relation to a stablecoin that does not meet MiCA's issuance conditions. The next day, 9 October, it opened a call for evidence on whether EU central counterparties could safely accept tokenised collateral. They look like different subjects. One is about stablecoin issuers and the platforms that list them. The other is about clearing houses and the assets behind margin. Read together, they say the same thing. The regulator is no longer asking what you disclose. It is asking what your systems can enforce and prove. This note covers both, because the teams who have to act on them overlap. ## The 8 October opinion The opinion is addressed to national competent authorities, not directly to firms. Its job is to tell supervisors what to look for. That distinction matters less than it sounds, because the expectations are specific. What it says, in order of how much it changes: - **All services, not just trading.** The expectation covers every MiCA service, alone or in combination: operating a trading platform, exchange, order execution, order reception and transmission, placing, advice, transfer services, custody and portfolio management. - **A presumption, not a case-by-case judgement.** ESMA's reasoning is that the risks of a non-compliant token come from the missing issuer-level safeguards, which a CASP cannot mitigate from its side. It therefore presumes that servicing such a token is incompatible with the CASP's duty to act honestly, fairly and professionally in clients' best interests (Article 66(1)). - **Disclosure does not fix it.** The opinion states that warnings and client acknowledgements are not enough. If your current answer is a risk banner and a tick-box, ESMA has already said it will not count. - **Controls are expected.** CASPs should have technical, contractual and organisational controls that prevent these tokens being available in the Union, including controls that stop EU clients acquiring or increasing positions. - **A three-month clock for legacy exposure.** Where supervisors find existing exposure, they should require remediation as soon as possible and no later than three months after publication. That puts the outer edge at around 8 January 2027. - **A narrow wind-down lane.** Continued service is limited to liquidating, converting, withdrawing, transferring or safekeeping existing holdings. It must be time-limited, clearly communicated to clients and closely supervised. No new acquisitions, no promotion, no active distribution. "Non-MiCA-compliant" is defined in a footnote: tokens for which the conditions for a lawful offer to the public or admission to trading under Titles III or IV are not met, taking into account applicable exemptions and transitional arrangements. Compliance status is therefore a property of a token at a point in time, not a permanent label. ## Where this breaks in a real stack Most CASPs will read the opinion and think about the listing. The listing is the easy part. The hard part is that "available to EU clients" is spread across several systems. - **Eligibility is data, and it changes.** You need one authoritative record of which tokens are compliant, sourced from the issuer and token registers and carrying effective dates. A hard-coded list in the trading engine will be wrong the first time a status changes. Someone has to own that record and review it on a schedule. - **Every service path needs the check.** Blocking a market on the exchange does not stop an order arriving through order reception, a transfer in from an external wallet, a portfolio-management rebalance, or a staking or custody sub-account. The opinion names them all. A control that sits only on the front-end order ticket does not meet it. - **Wind-down needs a mode, not a switch.** The permitted residual services are sell-only, convert, transfer out and safekeeping. That is a distinct state in the product: buying disabled, selling and withdrawal enabled, deposits restricted, client messaging attached. Most platforms have on and off. They need a third state, with an expiry date. - **Evidence for the supervisor.** If an authority asks how you prevent clients increasing exposure, the answer has to be a log of decisions, not a policy document. That means recording which rule blocked which request and when the eligibility record last changed. - **DORA still applies.** New controls are ICT changes. Third-party price, liquidity and custody providers that still touch an affected token are in scope for your register of information. The EBA published its final DORA third-party risk guidelines on 18 September 2026. Check that your remediation plan and your provider inventory tell the same story. For scale: the EBA's response to the Commission's MiCA review, published 24 September, says 39 e-money tokens had been issued as of 1 September 2026 and no asset-referenced tokens had been authorised. The compliant universe is small and countable. That makes an eligibility record practical to maintain. ## What the market is offering The commentary so far falls into two groups. Law firms and compliance newsletters explain the legal reasoning and what the opinion says about Article 66. Exchanges and trade press report which tokens may be affected. What is thin is the implementation view: where in a CASP's architecture the check lives, how a wind-down state is modelled, and what evidence to keep. That is engineering work with a date attached, and the date is January. ## The 9 October call for evidence ESMA's CCP Supervisory Committee has asked whether, and under what conditions, EU CCPs could use tokenised collateral. The call covers three models: tokenised versions of assets that stay in traditional infrastructure, assets issued directly on a distributed ledger, and hybrid arrangements, including how each interacts with tokenised cash and other settlement assets. The questions are about the lifecycle after a clearing member default. Can the CCP access the collateral, transfer it and convert it into liquidity? How are client protection, segregation and settlement finality maintained? Does tokenising an already-eligible asset change its risk profile? The committee chair is clear that the core safeguards stay unchanged: high quality, legal enforceability, liquidity and operational availability under stress. Responses are due **15 January 2027**, and ESMA will assess them in the first quarter of 2027 before deciding next steps. This is a consultation, not a rule. Nothing here obliges anyone to build anything. It does tell you what the eventual test looks like, and it is not a test about the token standard. ## What the collateral test asks of a tokenisation stack Anyone tokenising an asset in the hope that it becomes eligible collateral should read the questions as a checklist for their own architecture. - **Default-day mechanics.** On the day a member fails, can the asset be moved and sold within the CCP's timelines? That depends on transfer restrictions, identity and whitelisting logic, and whether the custodian and transfer agent can act inside the same window. These are the integrations between the token engine and the rest of the stack, not the contract itself. - **Segregation you can show.** Client positions must be demonstrably separate. On a ledger that means account structure, and the reconciliation between the ledger, the custodian's books and the CCP's records has to hold at the same moment. - **Finality and cash.** The call asks how tokenised collateral interacts with tokenised cash. If your settlement leg depends on a bridge or an off-chain confirmation, that is where the finality question will land. The Eurosystem's Pontes, live since 21 September, settles the cash leg in central bank money, and ESMA frames the cash side as part of the same analysis. - **Pricing and valuation.** A haircut model needs a defensible price when markets are stressed. Oracle and NAV feeds that work in calm conditions become part of the risk case. None of this is solved by choosing a different token standard. It is solved, or not, by how the pieces are connected and how well each one is evidenced. ## One thread through both ESMA also said on 30 September, in its response to the Commission's MiCA review, that regulated crypto firms should be prevented from offering services linked to non-compliant stablecoins, and that the EU needs a framework for tokenised securities and on-chain settlement. The opinion and the call for evidence are the first concrete steps on those two points. For a CASP, the lesson is to stop treating compliance as a layer above the product. A token's status, its permitted services and the evidence of control need to live in the system itself. For a tokenisation team, the lesson is that institutional eligibility will be decided in the integrations: custody, transfer agency, valuation and settlement. The token is the smaller part. ## How we help We do not sell a platform or list tokens, so the review is neutral about which ones you carry. 1. **CASP Compliance Stack Audit.** Fixed fee, two to four weeks. We map every service path against the opinion's list, check where an eligibility control exists and where it does not, and look at the DORA treatment of the providers involved. You get a gap list, a design for the eligibility record and the wind-down state, and a build plan sized against the January date. 2. **Tokenization Stack Assessment.** For teams connecting an ERC-3643 or T-REX class engine to KYC, custody, transfer agency and core banking. We use ESMA's collateral questions as the test cases: what does default-day handling require, and which integrations are missing. 3. **RWA Risk Readiness Review.** Where the question is whether an institution can price the risk, we look at oracle design, data feeds and cover structures. If the January date is on your plan, start with a fixed-scope verdict. See the [readiness sprints](/sprints/), or write to us at [info@prodevel.com](mailto:info@prodevel.com). ## Sources - [ESMA: supervisory expectations on services related to unauthorised stablecoins, 8 Oct 2026](https://www.esma.europa.eu/press-news/esma-news/esma-sets-out-supervisory-expectations-services-related-unauthorised) - [ESMA: Opinion on the provision of crypto-asset services in relation to non-MiCA-compliant ARTs and EMTs (PDF)](https://www.esma.europa.eu/sites/default/files/2026-10/ESMA75-113276571-1742_Opinion_on_the_provision_of_crypto_asset_services_in_relation_to_non-MiCA-compliant_asset-referenced_tokens_and_e-money_tokens.pdf) - [ESMA: call for evidence on tokenised collateral in central clearing, 9 Oct 2026](https://www.esma.europa.eu/press-news/esma-news/esma-seeks-evidence-use-tokenised-collateral-central-clearing) - [ESMA: response to the Commission's MiCA review, 30 Sep 2026](https://www.esma.europa.eu/press-news/esma-news/esma-calls-changes-make-mica-clearer-safer-and-ready-emerging-services) - [EBA: priorities for the review of MiCA, 24 Sep 2026](https://www.eba.europa.eu/publications-and-media/press-releases/eba-identifies-priorities-review-mica) - [EBA: final guidelines on third-party risk management, 18 Sep 2026](https://www.eba.europa.eu/publications-and-media/press-releases/eba-publishes-its-final-guidelines-management-third-party-risk-delivering-more-proportionate-and) - [ECB: Pontes launch press release, 21 Sep 2026](https://www.ecb.europa.eu/press/pr/date/2026/html/ecb.pr260921~e754847a7b.en.html) --- # Pontes is live. The connection fee is the cheap part. URL: https://prodevel.com/blog/connecting-to-pontes/ Published: 2026-10-08 Updated: 2026-10-14 Author: Rado Patus Tags: Pontes, DLT, RWA, Stablecoins The Eurosystem's DLT settlement bridge went live on 21 September 2026. Joining costs €2,500. The real cost is the integration behind it: keys, liquidity, reconciliation and DORA. On 21 September 2026 the Eurosystem switched on Pontes, the bridge that lets transactions on market DLT platforms settle in central bank money through TARGET. Thirteen market participants were onboarded on day one, from Deutsche Bank and Santander to KfW and the EIB, alongside four DLT operators: Axiology, Cashlink, Clearstream and SWIAT. More have committed to connect in the coming months. The fees won't be what holds anyone back. A market participant pays a one-off €2,500 to connect, a DLT operator €15,000, and there are no monthly or settlement fees in the initial launch phase. What holds institutions back is everything that has to exist on their side of the interface before the first trade settles. ## What Pontes actually does Pontes links market DLT platforms to TARGET services. The cash leg settles in one of two ways: - **Cash tokens on the Eurosystem DLT.** Participants fund intraday cash tokens from their T2 account and settle against them. Whatever is left is defunded back to T2 automatically at end of day. - **Direct settlement in T2.** The transaction is triggered from the Eurosystem DLT and the cash leg settles in T2 RTGS. That covers delivery-versus-payment for tokenised securities, payment-versus-payment against commercial bank money or e-money tokens, and plain wholesale payments. Pontes doesn't ask market platforms for a particular chain or token standard. It asks them to lock an asset transfer conditionally until the cash leg is confirmed. | Phase | When | What changes | | --- | --- | --- | | Initial launch | Live since 21 Sep 2026 | Core services, euro only, intraday cash tokens, daytime settlement window | | Initial enhancements | 2027 | Settlement finality on the Eurosystem DLT, all T2 currencies, hours aligned with T2 | | Enhanced product | By mid-2028 | Overnight token holdings, 24/7 service, ongoing fees | ## Two ways in | | Market participant | Market DLT operator | | --- | --- | --- | | Who qualifies | Any entity with access to T2 | EU/EEA CSDs, DLT Pilot Regime systems, overseen payment systems, EMIR CCPs, and supervised banks or investment firms | | Contract with | Your national central bank | Your national central bank | | What you build | GUI or API access, signing keys, funding and defunding, reconciliation | API integration and conditional-lock (escrow) logic on your own ledger | | Before go-live | Connectivity and certification testing | Connectivity and certification testing | A participant can use Pontes for wholesale payments on its own. Settling securities or currencies against cash needs a registered DLT operator on the other side of the trade. ## Where connections actually break The interface is well documented: one entry point with screen and API access, certificate and token authentication, signed instructions, and four-eyes approval on most actions. Getting a test case to pass is not the hard part. Running the connection inside a bank is. - **Keys and approvals.** Instructions are signed. Those keys need an HSM, a custody policy, and a mapping from the Pontes approval and power-of-attorney model onto the entitlements you already run. - **Intraday liquidity.** Cash tokens are funded from T2 and swept back every evening. Treasury needs that position in real time and a funding plan around the settlement window, or trades fail for want of tokens. - **Reconciliation.** One trade now touches the DLT platform, the Eurosystem DLT, T2, and your core banking and custody books. Someone has to match all four every day and route each break to an owner. - **DORA.** An internet-facing connection into a payment-critical system is an ICT risk item: register of information, incident classification, resilience testing. The Pontes documentation covers the interface. The DORA treatment is yours. - **The escrow, for operators.** A platform joining as a DLT operator has to implement the conditional lock on its own ledger and pass its own certification cases without weakening the settlement guarantees it already gives its clients. ## What the market is offering so far We read what has been published since launch. Three patterns stand out. - **Platforms** offer Pontes access through their own venue. That works if you plan to trade there, and less well if you need a connection that serves several venues. - **Law firms** cover classification, licensing and contracts. Necessary work, and it stops at the interface. - **Explainers** describe the architecture. Most stop at the press release. What's mostly missing is neutral integration engineering on the institution's side, scoped at a fixed price. Banks outside the euro area are missing from the conversation almost entirely. ## If you're outside the euro area Eligibility follows access to T2, not euro membership. Several Czech banks already hold TARGET accounts through a euro-area central bank. Whether that route extends to Pontes depends on whether your central bank of access is onboarding participants, so that's the first question to settle. Settlement is euro only for now, and the planned multi-currency step covers currencies settled in T2, which leaves out the koruna, the zloty and the forint. For a CEE bank that already moves euro through TARGET, Pontes is a euro wholesale capability, and a realistic one. ## How we help We don't run a venue or sell a platform, so the connection we design is the one that fits your stack, not ours. 1. **Pontes Readiness Sprint.** Fixed fee, two to four weeks. Which route fits you, participant or operator, and through which central bank. A gap map against the certification test cases. Target architecture for keys, liquidity and reconciliation. A DORA view of the connection. A build plan with a cost on it. 2. **Connection build.** API integration with the Pontes entry point, HSM-backed signing, approval workflows, automated funding and defunding, and reconciliation into core banking and custody. 3. **DLT operator enablement.** Conditional-lock logic on your ledger, including EVM and Hyperledger Besu stacks and ERC-3643 tokens, through to operator certification. 4. **Certification support.** We work through connectivity and user testing with you and your central bank, case by case. 5. **Operations.** Monitoring, end-of-day controls, reconciliation and the DORA evidence trail after go-live, as a managed service. We have shipped on the EU's regulated rails before they had deadlines: an EU-Commission-backed bonds-on-DLT delivery on EBSI and Hyperledger Besu, and the risk layer underneath tokenized assets at [RWArmor](/work/rwarmor/). We're based in Prague and work across CEE, where the access question is less obvious than it is in Frankfurt or Paris. If you're an issuer rather than a bank, the ECB's plan to buy tokenised public-sector bonds via Pontes changes the question. See [the ECB as buyer](/blog/ecb-tokenised-securities-pontes-issuers/). If Pontes is on your 2027 plan, start with a fixed-scope verdict on where you stand. That's what the [readiness sprints](/sprints/) are for, or write to us at [info@prodevel.com](mailto:info@prodevel.com). ## Sources - [ECB: Pontes launch press release, 21 Sep 2026](https://www.ecb.europa.eu/press/pr/date/2026/html/ecb.pr260921~e754847a7b.en.html) - [ECB: Pontes overview and eligibility](https://www.ecb.europa.eu/paym/target/pontes/html/index.en.html) - [ECB: Pontes Market Contact Group, eligibility criteria](https://www.ecb.europa.eu/paym/target/pontes/governance/pdf/pmcg/ecb.pmcg260128_adhoceligibility.en.pdf) - [Eurosystem: Pontes initial launch pricing guide](https://www.bde.es/f/webbe/INF/MenuVertical/SistemasDePago/ficheros/es/ecb.pontes.20260819.PontesInitialLaunchPricingGuide.en.pdf) - [ECB: Pontes and Appia timeline, 22 Jul 2026](https://www.ecb.europa.eu/press/intro/events/shared/pdf/20260722/timeline.pdf) - [ECB: Piero Cipollone, Money in the digital age, 6 Oct 2026](https://www.ecb.europa.eu/press/key/date/2026/html/ecb.sp261006~0da978f159.en.html) --- # EBSI's business launch is this month. Production still isn't a date. URL: https://prodevel.com/blog/ebsi-business-launch-production-date/ Published: 2026-10-08 Author: Rado Patus Tags: EBSI, DLT, RWA EBSI goes to Bucharest on 22 October for its Business Launch. Its own timeline gives no quarter for production — which is a problem if your integration plan has one. On 22 October 2026 EBSI holds its Ecosystem Roadshow and Business Launch in Bucharest. It is the clearest signal yet that the European Blockchain Services Infrastructure is moving from a Member State project to something institutions are expected to build against. It is also not a production go-live, and the difference matters if you have put a date in a programme plan. ## What is actually fixed EBSI publishes its own numbers, and they describe real infrastructure: - **20 nodes in production**, with **10 Member States in governance** - Governance held by **Europeum-EDIC**, the European Digital Infrastructure Consortium established by Commission decision in 2024, which took the network over from the European Blockchain Partnership - A codebase released as open source under the EUPL That is a stable base. Node topology, the governance model and the licence are not going to move underneath an integration you start today. ## What is not EBSI's own timeline is the thing worth reading closely. It lists two milestones that teams tend to treat as one: | Milestone | EBSI's stated timing | | --- | --- | | Business Launch | 2026, marked upcoming | | Network Technical Launch | 2026 | | Full service offering | "later this year" | No quarter. No month. The Network Technical Launch is described as the move to a production-grade network with stable environments and certified infrastructure, and the date attached to it is a year. This is worth saying plainly because a more precise figure circulates widely. "EBSI production, Q4 2026" appears in conference decks, vendor pages and strategy documents — and, until this week, on this site. We went looking for the primary source behind it and could not find one. EBSI does not publish it. ## Why a year is not a plan A bank or CSD sequencing an integration needs a date it can hold a release train against. "2026" is not that, and the gap has practical consequences: - **You cannot gate the programme on it.** Teams that make the go-live dependent on a launch date they do not control end up idle, then compressed. - **Conformance is the unknown, not connectivity.** Connecting to a node is tractable. What a certified production network will require of you — test cases, evidence, operational commitments — is the part that is still moving. - **The service catalogue is incomplete.** "The full EBSI service offering will be released later this year" means the surface you integrate against may still grow after you have designed to it. - **Procurement does not accept a year.** Vendor-risk review wants dates. A roadmap that says "2026" tends to come back as a question rather than an approval. ## What to do instead The approach that survives this is to split the work by what the date actually controls. 1. **Build against what is stable now.** Node access, key management, the governance and licence position, and your own ledger-side logic do not depend on when the business launch happens. 2. **Isolate the parts that do.** Conformance evidence, certification artefacts and anything tied to the final service catalogue belong behind an interface you can re-point, not threaded through your core. 3. **Write the plan against milestones you control.** "Integration complete and self-certified against the current test surface" is a date you can commit to. "Live on EBSI production" is not yet. 4. **Re-read the primary source each quarter.** The timeline is on EBSI's own pages and it changes. Secondary summaries lag it, and in this case overstate it. If you are in CEE, the Bucharest location is not incidental — this is the closest the EBSI ecosystem conversation has come to the region, and the access question for non-euro-area institutions is consistently less obvious than it is in Frankfurt or Paris. ## How we help We have built on these rails before they had deadlines: an EU-Commission-backed bonds-on-DLT delivery on EBSI and Hyperledger Besu, and the risk layer underneath tokenized assets at [RWArmor](/work/rwarmor/). The useful next step is a fixed-scope read on where your stack actually stands against the rail as it exists today, rather than against a date nobody has published. That is what the [Pontes/EBSI Readiness Sprint](/sprints/) is for: two to four weeks, an honest verdict, and a build plan with a cost on it. ## Sources - [EBSI: Ecosystem Roadshow & Business Launch, Bucharest, 22 October 2026](https://ebsi.eu/) - [EBSI: About us — timeline, Europeum-EDIC governance, Network Technical Launch](https://ebsi.eu/about-us) - [European Commission: EBSI in the Digital Building Blocks catalogue](https://ec.europa.eu/digital-building-blocks/sites/spaces/EBSI/pages/474513483/About+us)