# Cardano Node Diversity Workshop - Porto 2nd & 3rd June 2026

*Leios playground & Cardano level brainstorming documentation*

## Purpose of the workshop

Our main idea for this workshop is to bring every node implementer together and start expirmenting with a live version of Leios.

The Amaru team wants to also bring up architecture topics, specifications discussions and also review our current testing strategy and align on the standards any node implementation should follow.

## Expectations of the workshop

Come as you are with your implementation and plug in the private network that will be running a Leios environment.
Content forecasted using Leios: Follow the chain, reconstruct the Leios path, try to participate by voting with stake.

## Content & Agenda

### Mindset

**Day 1** will be very hands-on and targeted to every kind of node implementors (data notes, indexers, explorers, ect.) : we will run a live network with a first sandbox environment using Leios... so bring your laptop with you and have a working environment ready.

> Damien will reach out to each node implementers and the Leios team to make sure everyone is ready ahead of the workshop and we can spend the first day experimenting together.

**Day 2** will be modeled after the feedback we got from Toulouse, meaning we will have a room dedicated for "main topics" and another one for "free discussions" for people that want to bring something else on the table. The current list of topics (that will evolve in the upcoming weeks) are:
- Testing a Cardano node, agreeing on the "Golden standard"
- Operating a Cardano node: specificy the must haves
- Documentation & Cardano Blueprint: listing the priorities
- Hard fork process, Value Stream Mapping
- Client diversity: where should we access the information?

> We want to have maximum 5 big topics because we will use that workshop as a starting point for turning each big topic into a deliverable or an artifact that (we hope) anyone using Cardano will be interested of knowing about

### When & Where

- When: Tuesday 2nd June & Wednesday 3rd June
- Where: Porto, Portugal
- Venue: https://www.editoryhotels.com/porto-palacio/
- Accommodation will be in the same hotel

### Logistics & What's sponsored

As mentionned in the [treasury withdrawal](https://adastat.net/governances/2f2fc2539dde550d3c83bea67c11b03861407976bbe8d07c5b0e124aa8a12baa00) Amaru's budget will cover for the accommodation of each participant listed below who confirms their participation by the 15th of May.

The 3 nights that will be covered: Monday 1st June, Tuesday 2nd June, Wednesday 3rd June.

Catering (lunch and dinners) on Monday, Tuesday, Wednesday will be covered for all participants; as well as a few surprises that will be brought to the people joining us.

As for the travel, we'll leave it up to you to organise yourself and be there to anything that you deem interesting on Monday/Tuesday/Wednesday

### Current agenda (up for discussion)

- Monday 1st June: Arrivals, nothing planned
- Tuesday 2nd June: Leios playground, getting our hands dirty
- 9am (plenary for an hour): Introduction of the environment, starting up
- Morning: Run it, see what happens, analyse together
- Afternoon: Reviewing high level topics for Leios
a. Block fetch Leios logic (rules for gathering EBs and timings)
b. Current Leios assumptions and "flavors of Leios" review
c. Benchmarks to be created & targets to be defined together (ledger, consensus, block propagation)
d. How to be a "safe Leios node" from a node agnostic perspective
e. Peer selection and networking rules (cold/hot/warm states) (who de we connect with; whom is providing the results…) "we assume everyone talks to everyone about everything"

- End of the day: Documenting what happend and lessons learned

> These activities will be held in-person, we commit ourselves to delivering a insightful enough recap and artifacts that can give the overview of everything that happened in Porto

- Tuesday night: Restaurant with every participants (location to be confirmed) https://www.murodobacalhau.pt/#contactos

- Wednesday 3rd September: Structured discussion about the future of Cardano in a multi-node era and open forums:
- Testing a Cardano node, agreeing on the "Golden standard"
- Operating a Cardano node: specificy the must haves
- Documentation & Cardano Blueprint: listing the priorities
- Hard fork process, Value Stream Mapping
- Client diversity: where should we access the information?

> NB: We will record every "main session" and turn them into documentation / artifacts for everyone to have access to

### What do you get out of it

Everyone who will be there will have hands on experience on being able to test, simulate and run Leios having the Leios team around for live problem solving.

For people that aren't able to attend, we will document the outcomes of each session organised and make available the resources we used to work during those two days.

As for the second day, we hope to start initiatives that will bring up topics that will improve the overall Cardano environment.

## Who is part of the workshop

For the hands on workshops on day 1 we thought about a group size of around 40, which includes people impacted by Leios, developers of node implementations, power users and integrators - mostly engineers!

:::info
The invitations were sent on April 16th now and below you can see the list of people who we want attending to contribute to what we have planned, we will keep the invitations open until the 22nd of May, if you want to add people to our mix please email [Damien](mailto:[e-mail])
:::

### People invited to the in-person meetings

| Name | Notes | RSVP |
|---------------------------|------------------------------------------------------------------------------------|:-----|
| Alex Sierkov | `TurboCardano`, node implementor | 👍 |
| Alexander Nemish | `Lantr`, node implementor | |
| Alexey Kuleshevich | `Haskell node`, node implementor | |
| Andre Knispel | `Haskell node`, formal methods on ledger specs | |
| Arnaud Dewulf | `Amaru`, infrastructure & node operations | 👍 |
| Brian Bush | `Haskell node`, leios R&D | 👎 |
| Boshko Majdanac | `Intersect`, hard fork working group | |
| Carlos Lopez de Lara | `Leios`, product manager | 👍 |
| Chris Gianelloni | `Dingo`, node implementor | |
| Clark Alesna | `RAZOR`, node implementor | |
| Damien Czapla | `Amaru`, product manager | ✅ |
| Eric Torreborre | `Amaru`, node implementor | |
| Hari Amoor | `Gerolamo`, node implementor | 👍 |
| Jacob Finkelman | `Amaru`, Rust optimisation | |
| Javier Sagredo | `Haskell node`, node implementor | |
| Julien Eluard | `Amaru`, node implementor | 👍 |
| Jon Gaines | `Amaru`, whitehacker | |
| Jonathan Lim | `Amaru`, node implementor | |
| Josh Marchand | `Amaru`, node implementor | |
| Jean-Philippe Raynaud | `Mithril`, implementor | |
| Karl Knutsson | `Haskell node`, node implementor | |
| Kevin Hammond | `Security Council` | |
| Livio Klopp | `Haskell node`, haskell node infrastructure | |
| Marcin Szamotulski | `Haskell node`, node implementor | |
| Marcin Wójtowicz | `Haskell node`, node implementor | |
| Markus Gufler | `Haskell node`, SPO | ✅ |
| Martin Kourim | `Haskell node`, end-to-end testing | 👍 |
| Matthias Benkort | `Amaru`, node implementor | ✅ |
| Michele Nuzzi | `Gerolamo`, node implementor | |
| Mike Hornan | `SanchoNet`, SPO | |
| Nicolas Frisby | `Haskell node`, node implementor and leios R&D | |
| Paul Clark | `Leios`, developer | 👍 |
| Paolo Veronelli | `Haskell node`, node implementor | 👍 |
| Pi Lanningham | `Amaru`, node implementor and Leios | 👍 |
| Ramsay Taylor | `Haskell node`, formal methods on ledger specs | |
| Roland Kuhn | `Amaru`, node implementor | ✅ |
| Ryan Williams | `Intersect`, hard fork working group | 👍 |
| Sam Leathers | `Haskell node`, devops & product manager | |
| Santiago Carmuega | `Amaru` & `Dolos`, node implementor | |
| Sebastian Nagel | `Leios` & `Cardano Blueprint` | 👍 |
| Yves Hauser | `Haskell node` | 👍 |
> ✅ Booked
> 👍 Confirm interest in attending
> 👋 Not sure yet, but considering
> 👎 Cannot attend
> ? Not answered yet

### Open registrations for Day 2

If you want to join us in Porto, please fill [this form](https://tally.so/r/mZA06A)