EBSI's business launch is this month. Production still isn't a date.
- 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.
- 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.
- 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.
- 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.
- 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.
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 is for: two to four weeks, an honest verdict, and a build plan with a cost on it.