Maintainer Committee discussions - Minutes of Meetings

[Dam-CZ]

04 Feb 2025 - Demo scope alignment

Agreed upon scope for the demo on Friday:

Consensus: "Naïve" chain selection
Ledger: Rewards calculation & structuration of the ledger library
Node simulation test environment overview
Metrics & traces overview

Discussion topics:

• While starting and running the demo emphasize very explicitly on the assumptions that are considered for the demo environment
• UTxO RPC implementation is worth pursuing harder once we can use Amaru as a trusted source
• UTxO RPC: list of functions that are used by Blaze as an example

ReadParams
SearchUtxo by address
SearchUtxo by address with asset
SearchUtxo by asset (extremely hard with cardano node > uses the global utxo state)
ReadUtxo
SubmitTx
WaitForTx (reading mempool local tx monitor)

[Dam-CZ]

18 Feb 2025 - Maintainer Committee

Agenda

• Pallas evolutions
• Treasury proposal: Marketing / Public relation role alignment
• Next demo scope
• Treasury proposal discussion

Pallas: txpipe/pallas#599

The current issue raised for Amaru is looking into memoization, de-couple rust from CDDL/CBOR, full-deserialization, stronger type safety, rework Pallas primitive
Santiago will build a prototype to tackle the approach discussed and move forward on this

Marketing/PR Role Amaru:

We need to specify the scope of activity of the marketing related to the current target of Amaru, and integrate an estimate of the workload and costs related to that activity in our treasury proposal.

Current target for Amaru in 2025: be a bloc producing node that operates smoothly and with better performance than the current Haskell one
Concrete current goal: 5% of the SPO/Stake that uses Amaru
Concrete side goal: External contributors to contribute to Amaru
Scope of activity: build blogpost, social media engagement, engage with the community, exchange on various platforms
Things that the person should be able to be interact with: Logbook, codebase alignment, maintainers alignments
Set of skills:Find someone technical enough to navigate the codebase, graphic design, communication background
Example of marketing activity: social media management, marketing campaign design, ad campaign design and monitoring
Examples of things that can be a deciding factor: visual communication and transform sketching into a clear article to communicate
Current set of target: Stake Pool Operators
SPO outreach and users (we are selling to SPOs)
Bloc production and people that require that kind of interaction

Next demo scope discussion

• @QuantumPlation: Block validation demo
• @scarmuega: Peer 2 peer demo
• @stevana: (to be confirmed with Arnaud) connect simulation test with Amaru and focus on finding the existing bug
• @KtorZ: Complete ledger state with governance (at least proposal refunds, possibly protocol parameters)

Discussions

@QuantumPlation: Josh will work 50% of his time on the project, 2 weeks on, 2 weeks off
@KtorZ: potential to build Zero knowledge use cases and find someone with expertise to build with Amaru
@QuantumPlation: Sundae Labs can be a user for Zero Knowledge
@KtorZ: CIP-0137 being a first class citizen with Amaru related to this use case
@scarmuega: TxPipe can be helping with the CIP-0137 (GitHoney can be a good way to kickstart the activity)

[Dam-CZ]

04 Mar 2025 - Maintainer Committee

Agenda

• Treasury proposal: updates for marketing and PR role
• Treasury proposal: "why" integration
• Treasury proposal: timeline review & socialization strategy
• Roundtable of people connected
• Next demo discussion

Marketing/PR Role Amaru:

As per the statutes of PRAGMA it's one of the role of the Lead Maintainer of the project to handle the community engagement, the workload estimated for the marketing, PR and community management on the project is 0.25 FTE. Santiago doesn't have the bandwith to handle that role so Damien will be the bounded context owner on that topic.
The estimation of the costs and FTE will be integrated this week into the proposal

Treasury proposal: "why" integration

See: Discord discussion and provide feedback until integration next week

Treasury proposal: timeline review & socialization strategy

The current forecast gives us May 17 as the new target for the info action submission with the details of our proposal.
We will align during the next maintainer committees how we can push the socialization a few weeks before to finalise the discussions using X; Cardano forum; Gov tools; Discord.

Roundtable of people connected

• @abailly: Roland Kuhn @rkuhn will be joining the project to work on consensus and to use his experience with concurrent asynchronous systems and Rust for some internal auditing activities
• @jeluard : working on governance rules, so far so good
• @KtorZ: alignment needed between ledger rules, block validation, storage... event organised next week on Discord
• @KtorZ: concern shared about involvement on code reviews and a feeling of legitimacy lacking from people on the Amaru project, encourages everyone to be more involved in code reviews and be part of the integration of PR
• @Quantumplation: Ethan involved in problem solving for Sundae products and Josh on vacation, which explains why they weren't involved that much; will encourage them; other than that agreed that alignment is needed to reconciliate ledger rules & validation
• @scarmuega: nothing more to be shared
• @stevana: ongoing work to link testing

Next demo forecasted on 28th March scope

• @Quantumplation: Block validation demo
• @scarmuega: Peer 2 peer demo
• @stevana: (to be confirmed with Arnaud) connect simulation test with Amaru and focus on finding the existing bug
• @KtorZ: Complete ledger state with governance (at least proposal refunds, possibly protocol parameters)
• @Quantumplation: demonstrate Mempool features implemented

[Dam-CZ]

18 Mar 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Engineering Decision Records: 3 new items that were discussed in Toulouse but not formalised

• EDR for error handling and structuring the hierarchy
• EDR for putting the logic of the behavior of Amaru and the components functions and describe the overall way the node is working

For example: making obvious the components/crates that are asynchronous and work in parallel
End goal: make the code more digestable for people and have everything in one place: pipeline, things that work in parallel, how the parts are interconnected

• EDR to centralise the traces and make them available (traces are hard to document and there's not a place where you find all the traces)

One approach: Tracing details (metrics and such) generates the documentation from the traces generated and have code parsing that does that with structure
Other approach: macros with Rust to generate traces automatically and the documentation that goes with it
#144

Final discussion around manually tracking of interfaces (threading the span and such) and using gasket to glue the traces together, might need to be turned into an EDR or optimised

Action taken during the meeting:

• @jeluard: will write the EDR on error handling with Roland Kuhn @rkuhn
• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

Ledger rules API

There was a discussion about having an API that uses correctly "Ledger slices" (which are basically a subset of the key values)
Main problem to be solved: how do you update back this "slice" while not duplicating operations and such

• @KtorZ: We will need to create an API in the ledger that separates state and validation rules

Node diversity workshop in Paris

https://hackmd.io/@ch1bo/HywE1zFt1e

@abailly: Simulation testing on consensus looking good for the demo and should be a good topic for the workshop in Paris

Peer 2 Peer progress and updates

@scarmuega: 1st and 2nd Catalyst milestone done, proof of concept on an isolated setup available for inbound and peer selection

Outbound still needs some work, testing environment with multiple dummy node needs to be demonstrated before integrating in Amaru

This will also be implemented in Dolos for connection throwback and performance improvement on chainsync

@scarmuega will setup a meeting to welcome contribution after the dummy nodes interaction with the chainsync demo

Pallas discusison

@scarmuega has the idea of setting up a maintainer committee to manage feature evolutions, participation from Amaru members would be good enough
Also working on documentation for Amaru integrated features and connections will be useful to have in Pallas, will discuss further once the recurring committee is setup

Roundtable information

• The Cardano Foundation is starting a contract with Anthitesis (https://antithesis.com/) to simulate cluster of nodes, Amaru will be one of the beneficiaries of that activity
• Roland started to put together the downstream part of the consensus, feel free to chime in on the PR: https://github.com/pragma-org/amaru/pull/149/files
• Various feedback on the documentation of the node that is hard to use (hard to access and understand) for other node implementors: we need to make the documentation more suited for the people that want to build a node: Cardano blueprint can be a good way to formalise this
• @abailly will be at a consensus workshop for Peras this week, feel free to feed him with questions you want them to solve
• @KtorZ: will start pushing code to Pallas once refactor: Eliminating roundtrip-codec safe structures txpipe/pallas#611 is done and will take part in the alignment meetings

Reminder: next demo forecasted on 28th March scope

• @Quantumplation: Block validation demo
• @scarmuega: Peer 2 peer demo
• @stevana: (to be confirmed with Arnaud) connect simulation test with Amaru and focus on finding the existing bug
• @KtorZ: Complete ledger state with governance (at least proposal refunds, possibly protocol parameters)
• @Quantumplation: demonstrate Mempool features implemented

[Dam-CZ]

01 Apr 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Haskell node implementation bug discussion

Bugs were found in the Haskell implementation, discussions about how to report the bug and who to reach out to.
Conclusion was to reach out on Discord first and then see if that is successful.

Logo discussion

1st round of voting done, the "Relay" version of the was the most voted one, we will do one final iteration and one more voting round before choosing our logo.

Antithesis update

Contract between the Cardano Foundation and Antithesis is now signed, the kickoff will be done on the 2nd April.
The scope of their contribution is currently focused on the Haskell node and can be extented to Amaru, Dingo depending on the intereset.
The idea is to share publicly as much as is possible to show the results of the experiments and the outcome of it.
Current timeline is: 1 month for a proof of concept with the Haskel node. And then a 1 year contract potentially, if the contract is renewed there should be targets linked with Amaru (and potentially Dingo)

Demo done on the 28th March

Scope covered:

• @stevana: recap of the simulation environment progress and strategy
• @abailly: connect the simulation test environment with Amaru and focus on finding the existing bug
• @JSHy: demonstrates the implemented block validation features (and shows the current limitations with specific use cases)
• @KtorZ: ledger state and ledger validation - inspiration of design, approach chosen, status of progress
• @scarmuega: status of the P2P scope and assumptions for integration in Amaru
  Recording will be available on the PRAGMA website

WebAssembly compatibility

@jeluard is currently pushing for the consensus to be compatible with webassembly, expect some refactoring coming

Deterministic setup improvement

@stevana is currently improving the setup for the simulation environment of Amaru to be more deterministic, documentation will be shared soon regarding that topic.

Action taken during last meeting (reminder):

• @jeluard: will write the EDR on error handling with Roland Kuhn @rkuhn
• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

[Dam-CZ]

15 Apr 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Node diversity workshop recap

See: Node diversity meetup report to get the outcome of the workshop

Logo discussion

After reviewing the results of the votes the option Logo_Amaru_v1

Treasury proposal update and new documentation

Every info related to the treasury proposal can be found here Amaru treasury thread
Now the project has a new set of Milestones related to the proposal
The timeline will be:

• Expected info action: 25 April (because the second info NCL expires 24 April)
• Expected treasury withdrawal: 26 May (1 month +1day)

Action taken (reminder):

• @jeluard: will write the EDR on error handling with Roland Kuhn @rkuhn
• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

[Dam-CZ]

13 May 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Next demo: relay node release (timeline: first two weeks of June)

The idea is to focus on the relay node aspect and make available a docker image to run both Amaru & Dolos.
We want to make it as simple as it can be and be explicit about the capabilities of that release and its limitations.

Pallas PR to be checked

This Pallas PR might need some help from the team to finalize its merging

Round table of people connected to the call

• @stevana: working on a Rust version of the simulation environment
• @JSHy: Node diversity worshop will continue on May 20th to synchronize together all the node implementation, this time facilitated by @abailly
• @Quantumplation: Sundae secured a contract with Acropolis to build a modular Cardano product that can be used as a node; Some building blocs of Amaru will probably be used as a starting point for some parts of that project;
• @geoff @fifty tuned in to say that they were looking forward to contributing to the project

Action taken (reminder):

• @jeluard: will write the EDR on error handling with Roland Kuhn @rkuhn
• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

[aleeusgr]

I ran amaru as @yHSJ suggested and run into an error: #219

[Dam-CZ]

27 May 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Next 2 months priorities

On the Miro of the project a space has been created to brainstorm the priorities of the next 2 months for the project
The most urgent ones that were pointed forward:

• Treasury withdrawal setup (on-chain smart contract), communication strategy and on-chain specifics (after 9th June)
• Demo (when the binary for the relay node is available): forecasted for the 13th-20th June

Designer and communication plan

We are making the final adjustments to work with Mirko Grisendi to design illustrations for the website and make the documentation intuitive and illustrated with pictures that encapsulate the concepts and gives a nice vibe to going through the documentation

Treasury withdrawal smart contract setup

Currently building a specific version of the Sundae smart contract setup (with @mpizenberg & @Quantumplation)
Have a few weeks to build something, test it on preview, preprod and mainnet

Round table of people connected to the call

• @JSHy: next demo sounds challenging but will try to put as many rules as possible within the timeframe that is given and have some back and forth with @KtorZ to review progress
• @KtorZ: progress made on ratification of governance rules (see logbook 21st May)
• @abailly: working on setting up Amaru nodes together for testing the consensus at various scales (ideally Amaru & Haskell nodes together); also working on this to get access to running lower level deterministic simulation tests for the consensus (can be a good scope for Antithesis: running this setup and playing with the limits i.e. filling blocks, playing with the CPU threshold...) consensus scope will be ready for the upcoming demo
• @stevana: progress made with the Rust version of the simulation environment, what's left is to introduce the new API build by @rkuhn and the Rust environment should be operational after that
• @JSHy: script validation progress ongoing, a bit tricky to implement, should be done this week
• @jeluard: focusing on running Amaru with different networks (preview right now) will be helpful for mainnet; ongoing discussion with @abailly to create an "Amaru testnet"
• @geoff: built a terminal UI framework (inspecting the ledger or the database) with a PR that will enable scrolling through the UTxOs and look into them interactively; this will help with diving deeper in the batching strategy of UTxOs; going to be involved in designing and implementing the peripheral tooling

Action taken (reminder): (should be linked with the website and designer timeline to see how the documentation can fit in)

• @jeluard: will write the EDR on error handling with Roland Kuhn @rkuhn
• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

[aleeusgr]

I helped the team improve "getting started" section of the readme.
Looking for mentorship opportunities and ways to contribute to the project regularly.

[Dam-CZ]

10 June 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Budget info action

Our governance info action finished at 80.43% yes vote from DReps with very high participation, we are more than satisfied with the result.

Treasury withdrawal: setup, timeline

Our current treasury smart contract setup relies on the Sundae solution built for Intersect but with some scripts that enable PRAGMA to have the ownership of choosing maintainers for the project (as per the statutes)
We have an ongoing audit that should be finalized close to end of June, but we don't want to wait for this to make the treasury withdrawal governance action.

As we don't want this to be delaying our treasury withdrawal, we will use the standard setup of Sundae in the meantime (that has been already audited and that can fulfill the basic functions linked to managing the withdrawal). This will be made with a very simple multi signature from scope owners and a 3 out of 4 decision making standpoint for anything related to the project, and a 4 out of 4 for the contingency funds. But we plan to use our setup as soon as it is audited and deemed valid.

Our current timeline is:

• Get the funds back from the budget info action (should happen on the 13th of June)
• Get the treasury withdrawal on chain on the 16th
• Once the audit of our treasury smart contract setup is complete, transfer the smart contract to the setup described in our proposal that ticks every boxes

Designer and communication plan

We are now working with Mirko Grisendi to design illustrations for the website and make the documentation intuitive and illustrated with pictures that encapsulate the concepts and gives a nice vibe to going through the documentation. First item on the menu is the website landing page that should be available within weeks.

Paid contributors environment and legal perspective

As we are getting closer to paying vendors and paid contributors with ADA or stablecoins we need to provide a setup for companies to get paid by the treasury funds. We are currently targeting: Germany, France, USA, Switzerland as legal jurisdiction to have a read on the situation. We want to provide (as early as we are able to):

• Have a point of view of the rules of the country linked to "getting paid by cryptocurrencies"
• Having a step by step process for paid contributors to be on-boarded on the project
• Propose a way forward for setting up payments and legal papers that go with it

Round table of people connected to the call

• @abailly: made some progress thanks to pairing session with Roland and Stevan to get an almost working simulation environment with deterministic tests; still working on connecting 2 Amaru nodes together (preprod first then on another test network) one of the big question is booting up from genesis.

• @abailly: discussions ongoing with antithesis to host a workshop 22nd 23rd September or 29th 30th. This might be a good idea to push the workshop to node diversity and towards technical steering reflections (we can invite Tim Beiko from the Ethereum foundation that can give us the perspective on how they do it for the Ethereum ecosystem.

• @Dam-CZ: question about the scope of antithesis and using it in our project: "who should be owning their scope and playing with them: consensus? mercenaries?"; @abailly: a bit of both, we are building with antithesis an online tracking system for running antithesis > see who does what (currently used on Cardano Nodes) and once we are running Amaru nodes we can track and split the activities according to the targeted scope and use cases.

• @stevana: progress made with the pipeline to generate the whole simulation, still ongoing

• @jeluard: still focusing on running Amaru with different networks (preview right now) now at the part where working on different networks requires changes in Ogmios; also working on creating custom testnet environments

• @jeluard: special shoutout to @geoff working on the Amaru doctor tool (getting very useful) now we just need to publish and package to make it more easy to use; let's see what new features can be brought to the table (currently working on ledgerdb & the UI)

Arnaud: Can we read the blocks? Can we store the blocks? might be worth pursuing
Julien: formalise specific requirements would be great (make explicit what you want to get from the queries, what information you require)
Arnaud: direct access to the data & troubleshoot things having the information available would be awesome

• @geoff: working on Amaru Doctor fed by Julien with ideas and eating ideas (ex: showing process into tabs to inspect the network)

• @KtorZ: progress made on the treasury contract, now being audited; currently updating tooling (Ogmios):

Get snapshots from mainnet (for bootstraping) - previous snapshot was 2.5GB not good for websocket
Rewards data (along with the calculations) are currently down to epoch 182 (done by forking the node, which is dirty) now trying to setup

• @KtorZ: overall remark about how we onboard new people on the project that want to contribute, first suggestion would be opening a call (bi-monthly) just to work and see what others are doing, some kind of pairing session. Other ideas include:

Ceremony to onboard new contributors (draft a discussion on topics to be done)
Use items not on the critical path to make a sandbox environment for playing with Amaru
Organise the contribution "steps" to get people contributing
Have a set of "go-to" mentor / point of contact for discussing & pairing the code in every scope of the project
This will be linked with the bug bounty as an initial step of "starting up with Amaru"

Next demo prep: 17th June 16:00 CET

Running a sanity check for the following must have to our next demo & binary

Protocol parameters manageable anywhere else than Preprod
Storing block on disk (for queries)
Governance actions ratification (state of the rules necessary, stake management)
Networking: node to node static topology (implement duplex?)
Staying alive timing: identify the transactions that crashes and see how we can work around or solve it

Next 2 months priorities (reminder)

On the Miro of the project a space has been created to brainstorm the priorities of the next 2 months for the project, so far no change from what we discussed last week
The most urgent ones that were pointed forward:

• Treasury withdrawal setup (on-chain smart contract), communication strategy and on-chain specifics (after 9th June)
• Demo (when the binary for the relay node is available): forecasted for the 27th June

Action taken (reminder): (should be linked with the website and designer timeline to see how the documentation can fit in)

• @jeluard: will write the EDR on error handling with Roland Kuhn @rkuhn
• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

[Dam-CZ]

24 June 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Website illustration

Here is the result of the back and forth about designing the landing page of our future website:

There's still some work to be done around designing the content of the website and the illustration that can capture the idea behind each section imagined, here is a draft of the current ideas:

• Documentation & resources: explaining how Amaru works and how to run
• Major decisions: central piece of information about major architecture choices, current tradeoffs and content
• Workflows & tools: showcase things like Amaru-doctor to understand the behavior of the node and its processes/activities

Round table of people connected to the call

• @abailly: focused on building up the demo, a few issues like downstream peer crashes because he can't find the header of the peer, troubleshooting session with Roland tomorrow, but looking good to showcase traces and an environment with metrics. Memory leak issue being looked into.

• @abailly: working with Santiago on the P2P and Pallas v2

• @abailly: starting to design an EDR linked to observability: define top metrics for the core crates, starting with Consensus

• @abailly: new resource on the project (Pascal) will work on building a docker image of the demo cluster to simplify using Amaru

• @geoff: working on Amaru Doctor: now if you have a hash you can look for things (it's nice enough to use). Looking for feedback to use cases, met with Julien to add features to Amaru doctor like integrating metrics from the Opentelemetry stack

• @jeluard: working on making Amaru node run on mainnet

• @jeluard: building a small library to extract meta-data (codegraph like) for the instruments functions and understand how things link together and see how the codebase behaves, what the code doing and also generate documentation on top. This will also make sure that we have an "API like" behavior for people to connect to.

• @KtorZ: done with the treasury withdrawal setup, only 1 signature missing, we will then leave it to the DReps voting

• @KtorZ: reviewing PR, data hash mismatch to be looked into, having a new version of Pallas released might make us redo the fix, will have to spend some time using the Pallas environment, will have to make a decision moving forward to manage the interface with Pallas (directly update Pallas, use a fork...)

• @Quantumplation: building a standardized on disk ledger format (generating from cddl) and creating a crate for every node implementor to reuse

• @stevana: solving issues in the simulator with cleaning up and refactoring the code, e.g. one due to two events scheduled at the exact same time now fixed

• @Dam-CZ: potential themes for the next node diversity workshop

Main activity: Building test cases and running them with Antithesis (1 day hackathon, 1 day open space)
Side workshop: How to decide what’s in and out of the base node product ? (Guest: Tim Beiko, core Ethereum protocol facilitator)
Side workshiop: Showcase of documentation with Cardano Blueprint & think tank (Ran by Sebastian Nagel)

Next demo: 27th June 16:00 CET

Content to be shown:

• Golden test vectors, a testing solution for all nodes (Joshy)
• Ledger rules visualization & traces (Joshy)
• Running simulations & display of processes involved (Stevan)
• Plugging Amaru nodes together and seeing it work (Arnaud)
• Metrics and things to measure on the node (& recap from SPO feedback)

Next 2 months priorities (reminder)

On the Miro of the project a space has been created to brainstorm the priorities of the next 2 months for the project, so far no change from what we discussed last week
The most urgent ones that were pointed forward:

• Treasury withdrawal setup (on-chain smart contract), communication strategy and on-chain specifics done
• Demo (when the binary for the relay node is available): forecasted for the 27th June

Action taken (reminder): (should be linked with the website and designer timeline to see how the documentation can fit in)

• @jeluard: will write the EDR on error handling with Roland Kuhn @rkuhn
• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

[Dam-CZ]

08 July 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Workshop on 22nd and 23rd of September

Node diversity workshop #2 organised with day 1 being a very hands on approach of testing, simulation and playing with the node environment, and day 2 being a more open discussion setup with a set of topics defined and an open innovation forum.

Next relay node binary

There's still some items on the menu on each scope before releasing the binary that can be used as a relay node:

• Ledger: governance ratification and era history calculations,
• Networking: static peer management and recovering from an adversarial peer, overall strategy to be clarified for our first release
• Consensus: build the disclaimer of what's covered and provide a "clean" environment based on the scope covered

We will organise alignment calls to have a sanity check of each scope and review the progress towards that release start of August

Round table of people connected to the call

• @Dam-CZ: given the status of the treasury withdrawal we need to build a clearer perspective of the current progress of the project, have a better understanding of which scope is in which situation and build up the refined roadmap and put items on the menu to prioritize with our treasury spending

• @KtorZ: some adjustment will have to be made for the ledger regarding how we manage the Pallas dependency and the overall progress of the ledger

• @KtorZ: would be a good idea to have Amaru run a Raspeberry Pi and showcase it as soon as it's available, topic will have to be discussed with Pi see if it can be a fitting job for the mercenary scope

Next 2 months priorities (reminder)

On the Miro of the project a space has been created to brainstorm the priorities of the next 2 months for the project, so far no change from what we discussed last week
The most urgent ones that were pointed forward:

• Binary: relay node release

Action taken (reminder): (should be linked with the website and designer timeline to see how the documentation can fit in)

• @jeluard: will write the EDR on error handling with Roland Kuhn @rkuhn
• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

[Dam-CZ]

22 July 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Treasury withdrawal information

You can find in that Journal a list of all the thing that happen related to the Treasury withdrawal that was successfully done

Scope sanity check and 2025/2026 roadmap alignment

Damien will do some progress check up on all the scope and bring up all the delivery targets for 2025 and 2026 to consolidate both an overview of the 2025 "reste à faire" and the 2026 planned work ahead. This will condition both the current treasury expenditure targets and the content of the 2026 budget.

Round table of people connected to the call

• @geoff: progress made on Amaru-doctor, see the screenshots of the sudo flame graph and the terminal

• @jeluard: kudos to Geoff for his work on Amaru-doctor, starting to take a very interesting shape and helps a lot with understanding what actually happens with the metrics and their content! Working on a bunch of "summer" projects:

• @jeluard: Preparing for the Cardano Summit to have an all inclusive Raspberry Pi with a pre-built Amaru in it that showcase the consumption of resources, some nice traces and that can integrate things like Amaru-doctor to see what's happening with the node. Working with @pgrange with activity centered around creating images for the ARM setup and figuring out a way to bootstrap a database to kickstart the node on the Raspberry

• @jeluard: Created an EDR that describes how we handle errors and error management, feel free to give it a look

• @jeluard: Working on something called "Cardano Proofs" similar to Ethereum proofs which is zero knowledge proofs of block validation (currently a Proof of Concept) trying to use Zero Knowledge Virtual Machines from the Rust environment already available and picking/tailoring the fastest and most convenient to use

• @jeluard: Working on making Amaru being a Mithril signer and integrating with Mithril overall

• @Quantumplation: looked into a setup in which we could pay contributors with the Cardano Treasury funds. Accountants linked to Sundae Labs said there's a way to create a coherent paper trail to go from the wallets owned by the scope owners to the contributors and paying their company or them directly.

• @stevana: solving issues in the simulator with cleaning up and refactoring the code, e.g. one due to two events scheduled at the exact same time now fixed

• @Dam-CZ: given the status of the treasury withdrawal we need to build a clearer perspective of the current progress of the project, have a better understanding of which scope is in which situation and build up the refined roadmap and put items on the menu to prioritize with our treasury spending

• @KtorZ: some adjustment will have to be made for the ledger regarding how we manage the Pallas dependency and the overall progress of the ledger

• @KtorZ: would be a good idea to have Amaru run a Raspeberry Pi and showcase it as soon as it's available, topic will have to be discussed with Pi see if it can be a fitting job for the mercenary scope

• @Quantumplation: building a standardized on disk ledger format (generating from cddl) and creating a crate for every node implementor to reuse

• @stevana: created an EDR describing the environment of deterministic simulation testing and explaining for example the difference with Antithesis' setup

Next 2 months priorities (reminder)

On the Miro of the project a space has been created to brainstorm the priorities of the next 2 months for the project, so far no change from what we discussed last week
The most urgent ones that were pointed forward:

• Binary: relay node release

Action taken (reminder): (should be linked with the website and designer timeline to see how the documentation can fit in)

• @jeluard: will write the EDR on error handling with Roland Kuhn @rkuhn DONE!
• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

[Dam-CZ]

5th August 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Setting up a contractual environment for contributors to get paid

We are very close to having a paper trail that makes sense both from a legal and accounting perspective. Final steps are to make the setup sound in all the jurisdictons we are targetting and sign 2 first contract next week for Geoff and Eric.

Cardano Summit & Raspberry Pi

The main idea we have for Amaru at the Summit is to show that the node runs on a Pi (the smallest possible) and have ~20ish products to give out to people and 3 bigger product to showcase things that happens with the node. We should think about integrating Amaru-doctor to showcase some key elements of the node running.
Branding, visual aspect and components will be very important to choose and align in the coming months to get across the message "Cardano can run in a very small CPU & RAM usage, even in your pocket"

Round table of people connected to the call

• @abailly: welcoming @etorreborre to the consensus team; firstly revamping the chain selection to be less resource heavy

• @geoff: cleaning up the code for better traces management

• @geoff: contributing to an Open source project in close relationship to running Amaru in a browser for wasm and understanding what that means

-@rkuhn: currntly focused on running Amaru in a browser: working on pure stage framework (using it with Gasket)

• @stevana: documenting and solving issues in the simulator with cleaning up and refactoring the code

• @KtorZ: had chats with the Haskell team about the upcoming roadmap for Cardano; a lot of new features implemented that are impacting a lot of the pieces we put together, constantly moving target, currently not involved in the evolution discussion but we want to be more involved; will try to compile all the things discussed for clarification and measure what they mean for our development

Action taken (reminder):

(should be linked with the website and designer timeline to see how the documentation can fit in)

• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

[Dam-CZ]

19th August 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Setting up a contractual environment for contributors to get paid

The setup has been aligned from a legal perspective and requires one final accounting and tax perspective to be met before we can sign our first Amaru contract, hopefully by the end of today.

Amaru roadmap update

The technical roadmap has been updated based on our latest items that will make us deliver a relay binary and a block producing binary.

Round table of people connected to the call

• @abailly: bringing @etorreborre up to speed & working on finalising the chain selection part

• @abailly: writing a generator for block trees and found some issues

• @abailly: one goal will be to finalise the test cases and use it as a references in the Cardano blueprint project for the Consensus part of a Cardano node

• @abailly: next big step will be merging everything with the simulation environment

• @stevana: next step is to understand the pure stage part and apply it to the simulation environment

• @KtorZ: big chunk coming for Governance ratification, getting closer to a complete ledger state, noticed ledger stake discrepencies, next big step will be shipping a relay binary

• @JSHy: focusing on Midnight right now until teh 1st of September, onboarding new ressources and people that will work on Amaru

• @abailly: we will have to put some effort reaching out to SPOs for the functional requirements and the fact that we want to embed a form of Key management setup into Amaru, we will start with the SPOs that are close-by and start from their perspective

• @geoff @jeluard nothing major to share

Action taken (reminder):

(should be linked with the website and designer timeline to see how the documentation can fit in)

• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

[Dam-CZ]

2nd September 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Round table of people connected to the call

• @Dam-CZ: still ongoing work on the contract setup. First to make it simple and explicit: setting up something to make the paper trail resulting from payments to be clean and included in the transaction trail that will also do the disbursement. Hopefully the setup and the contracts should be finalized and signed on the 9th September

• @abailly: pairing with @etorreborre on chain selection robust, no more memory leak that we can't identify

• @abailly: running an Amaru node and measuring memory usage, see this:
  

• @abailly: Will focus on generating Amaru snapshots to run Amaru with antithesis hopefully before the Node diversity workshop

• @etorreborre: working on headers tree refactoring for chain selection

• @etorreborre: looking into the simulation code to simplify parameters for pure stage and API related things

• @jeluard: working on the ability for ledger to load blocks from the file system bypassing the Consensus > having loaded things for performance testing or other testing targets

• @jeluard: everything generates a lot of data, might be worth considering a shared storage for things that we want people to access while running a node / building with Amaru (Cloudflare with a nice API would be nice)

• @jeluard: for example we are generating cbor files periodically, an Amaru database, a set of curated snapshots...

• @jeluard: testing out raspberry Pi LCD screen: what to display? Using Ratatouille to display things, trying to get Amaru-doctor on it

• @KtorZ: we can synchronize preview and preprod, governance is in, we still have a problem on one of the last epoch, we are still troubleshooting on the data (ledger state and finding the discrepancies and diving into solving the problem)

• @KtorZ: Ledger state almost complete, we have a better perspective on database, storage on disk, can be improved and optimized (two store option: Memory; roxdb) rather than having it in the store implementation we will target the ledger to have that option

• @KtorZ: looking into the Raspberri Pi, running Amaru on mainnet gives us 2.5/3 Gb of RAM used, surprisingly high, the memory optimisation targets:

Volatile database (last 360 blocks stored in memory)
Stake distribution (the last 3 stored in memory)
Header tree storage (storing the entire header currently in memory) > can be a trimmed down version

• @KtorZ: reached out to Steve to see the metrics of the Haskell node (CPU, RAM, epoch boundary, Grafana template for having a basic dashboard)

• @pgrange: memory mapping: make the system cherry-pick things (see if it fits with Rust) could be a way to gain some memory usage

• @stevana: finished the prototype and write up about simulating time: https://github.com/pragma-org/simulation-testing/blob/main/blog/dist/07-extending-dsl-with-rpc.md , this is basically the "simulating time" section of the simulation testing EDR

• @whankinsiv: worked on memory store bootstraping and removed the roxdb specific logic

• @geoff: nothing Amaru related to share, excited for the conclusion of the contracting to be more involved in Amaru

• @JSHy: was focusing on Midnight, as of September 1st, Amaru full time

• @geoff @jeluard nothing major to share

• @rkuhn: 45minutes presentation based on work from Stevan an overview of Amaru simulation testing that will be presented at Codemotion and probably also at the node diversity workshop

Next demo: 23rd September during the Node diversity workshop in Toulouse

Timing aligned during the maintainer committee, current list of content to be showcased:

• Ledger: Governance implementation > ratification and impact on Pure stage
• Consensus: Consensus chain selection, connection and wiring up
• Simulation: Simulation environment wired up (isomorphic) accurate simulation with respect to the production code
• Live running: Running an Amaru node and shows that it works
• Live running: Zoom on the metrics using the mainnet Amaru for it (synchronise until the very last epoch)
• Live running: Showcase specific CPU and RAM usage (compare with running Haskell: how long does it take 'epoch boundary' and how much does the Haskell node takes of CPU and RAM)
• Amaru-doctor: Demo Amaru-doctor with its current state
• UPLC VM: Demo the new UPLC VM & show tests passing
• Project management: Showcase the structure of the contracts and how we pay people

Action taken (reminder):

(should be linked with the website and designer timeline to see how the documentation can fit in)

• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

Amaru roadmap

The technical roadmap has been updated based on our latest items that will make us deliver a relay binary and a block producing binary.

[yHSJ]

Correction: We were focusing on Midnight. As of September 1st, Sundae has put me on Amaru full time. Getting myself spun up on Amaru progress that happened while I was working on Midnight

[Dam-CZ]

Corrected it, thanks

[Dam-CZ]

16th September 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Next demo: 23rd September during the Node diversity workshop in Toulouse

Timing aligned during the maintainer committee, current list of content to be showcased:

• Ledger: Governance implementation > ratification and impact on Pure stage
• Consensus: Consensus chain selection, connection and wiring up
• Simulation: Simulation environment wired up (isomorphic) accurate simulation with respect to the production code
• Live running: Running an Amaru node and shows that it works
• Live running: Zoom on the metrics using the mainnet Amaru for it (synchronise until the very last epoch)
• Live running: Showcase specific CPU and RAM usage (compare with running Haskell: how long does it take 'epoch boundary' and how much does the Haskell node takes of CPU and RAM)
• Amaru-doctor: Demo Amaru-doctor with its current state
• UPLC VM: Demo the new UPLC VM & show tests passing
• Project management: Showcase the structure of the contracts and how we pay people

Round table of people connected to the call

• @Dam-CZ: contracting setup agreed and ongoing signature process, first transaction expected this week

• @Dam-CZ: SPO topics linked to demo and release should be moving forward in November/December and have a first "SPO dashboard" ready to go by then with a simple filled template

• @abailly & @KtorZ & @jeluard finalising steps for the binary and the demo release

• @KtorZ: we now have some metrics about the Haskell node (CPU, RAM, epoch boundary...) that will be used for benchmarking Amaru behaviour on mainnet

Action taken (reminder):

(should be linked with the website and designer timeline to see how the documentation can fit in)

• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

Amaru roadmap

The technical roadmap has been updated based on our latest items that will make us deliver a relay binary and a block producing binary.

[Dam-CZ]

30th September 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Node diversity workshop

Recap of the two days available here: Twitter Cardano Forum
Video of the demo at the end of Day 2 still being edited out, a video recap to be available soon
Main outcome: have one concrete action following each of the sessions that have been held, Damien to facilitate the process of getting something out that is beneficial to the project or to the Cardano node implementers.

Round table of people connected to the call

• @abailly: after a workshop held just after the node diversity days, the HAL team will look into streamlining the snapshot generation process for Amaru (dbsynthetiser & dbserver) by downloading mithril snapshots to bootstrap Amaru (before Summit); also will look into the crypto behind Leios & Peras

• @etorreborre: gasket stages moved to pure-stage, still have some effects to be migrated (mostly store) proves to be challenging

• @geoff: now fully contracted with Amaru, working on Amaru-doctor and pushing some evolutions on it

• @JSHy: tooling and metrics should come out of the box from now compatible with nView, currently working on implementing a specific

• @jeluard: implementing metrics compatible with Grafana would be great, have some dashboard and test them out

• @jeluard: reimplementing some Mithril based PR for performance testing; Raspberry Pi enclosure building with a Pi5; trying with Pi0 as well but can't sync right now; working on optimizing memory and trying to find out where we can save some usage; sync Amaru-doctor to be able to run into a small screen with buttons

• @KtorZ: we can synchronise mainnet, somewhat stable (previous problem was a governance ratification bug); small discrepancies in the state, still needs to be investigated and rework the way we perform the epoch boundary calculations

Action taken (reminder):

(should be linked with the website and designer timeline to see how the documentation can fit in)

• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

Amaru roadmap

The technical roadmap has been updated based on our latest items that will make us deliver a relay binary and a block producing binary.

[Dam-CZ]

14th October 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Next demo: 7th November at 16:00 CET

The main idea of that demo is to showcase what will be available at the Cardano Summit the week after, and give a heads up of things that are progressing, current plan involves:

• Demonstrate the use of Amaru as a relay (with multiple connections) in a simulation environment (Eric)

Generate a "happy path" with a million block > long chain with long forks (within the rules)
Showing error case & breaking points with the simulation, looking at the output
Showcase what we are testing and getting confidence in the results

• Amaru-doctor showcasing what we have and the display (Geoff)

• Preview of the Raspberry Pi content: using it to sync the whole chain (Julien)

Round table of people connected to the call

• @etorreborre: running the simulation tests and getting complex data and getting something interesting for the demo

• @geoff: working on an easier way to get the Raspberry Pi setup running

• @JSHy: UPLC VM & script context (mapping the transaction) > might be nice to showcase at the demo

• @jeluard: replaying transaction with a Mithril snapshot (creating a 'fresh' Amaru without having to connect to peers) could be a way to rethink the way of using snapshots and bootstrapping; exploring options to optimise this

• @jeluard: focusing on the Raspberry pi for the summit and removing the last minutes surprises

• @Dam-CZ: we will need to align on writing the content of the booklet of 'how to' and 'how to update' the Pi that we will giveaway

• @JSHy: will collect a list of question for Pallas and scope it with Santiago to see how we manage the dependency and move forward with it for Ledger, Networking and all the interfaces with have

• @abailly: nothing major to share

Action taken (reminder):

(should be linked with the website and designer timeline to see how the documentation can fit in)

• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

Amaru roadmap

The technical roadmap has been updated based on our latest items that will make us deliver a relay binary and a block producing binary.

[Dam-CZ]

28th October 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Reminder: next demo: 7th November at 16:00 CET

The main idea of that demo is to showcase what will be available at the Cardano Summit the week after, and give a heads up of things that are progressing, current plan involves:

• Demonstrate the use of Amaru as a relay (with multiple connections) in a simulation environment (Eric)

• Amaru-doctor showcasing what we have and the display (Geoff)

• Preview of the Raspberry Pi content: using it to sync the whole chain

New item on the demo Plutus VM V3 should be ready but not yet fully integrated and structured codebases (Jshy)

Round table of people connected to the call

• @etorreborre: working on simulation to generate better data and created an animation to showcase the tree and the decision behind deciding which chain is the better; found a bug thanks to doing that visualisation and showcasing what we do; working on making data better and visualisation

• @Dam-CZ: new actor in the project Yaacov that will be interacting with us to optimise the way we use Rust as a language and find improvement paths for overall resource usage; preparing the Summit with goodies and designing a few illustrations with our designer

• @KtorZ: went down rabbit hole of optimisation, target is 1GB of RAM, currently exploring efficiency and waiting for Jacob to come in to dig into big chunks of optimisation; looking at traces: way too many spans created, needs to be investigated; Raspberry Pis are working, preparing them for the Summit

• @rkuhn: worked on making upstream connection robust and making more complex scenarios; still using pallas network tools; pushed some PR to prod on Friday to fix a few things, hopefully no big bugs; cardano-ignite might be a good thing to setup testing and integrate with Antithesis things we want to build

Action taken (reminder):

(should be linked with the website and designer timeline to see how the documentation can fit in)

• @abailly: will write the EDR on tracing
• @KtorZ: will write down the EDR on logic and behavior of Amaru

Amaru proposal for 2026

The technical roadmap has been updated based on our latest items that will make us deliver a relay binary and a block producing binary

The current items considered for 2026 are available in our Whiteboard playground and currently being tailored for our proposal

[Dam-CZ]

11th November 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Demo done on 7th November

• Demonstrated the use of Amaru as a relay (with multiple connections) in a simulation environment (Eric)
• Amaru-doctor showcasing what we have and the display & preview of the Raspberry Pi content: using it to sync the whole chain (Geoff)
• Amaru website showcase (Matthias)
• Plutus VM & phase 2 validation progress (Josh)

All the demos be integrated in the website

Round table of people connected to the call

• @abailly: current problem with the CI is that we are soon at the maximum capacity GitHub allows, mainly linked to the tests checking all the crazy things happening and using Chainsync every time; ways of solving this would be the ability to produce snapshots that starts at any point you choose that are lighter and have a test that checks the ledger can "digest" block instead of syncing to the tip

• @abailly: scheduling time with Antithesis later this week to run Amaru;

• @JSHy: merging the Jonathan PR into Amaru, phase 2 validation: Plutus V3 and V1 scripts (no validation on V2 yet); relying on Ogmios so far for testing

• @rkuhn: tracing span parenting issue fixed; switching soon the focus to moving networking to pure stage; joined the Cardano networking group, asking what would they need to have Amaru a valid implementation of a Cardano node: and the current assumption for Amaru that we do not sync from genesis and not have all the blocks might be considered adversarial node by the Haskell implementation, discussions ongoing on how to move forward

• @abailly: Karl reached out about syncing the whole chain; we have an example of a solution: download the blocks from a trusted validated source like Mihtril; we download a proven snapshot for epoch 500, you have a trusted state and a trusted chain, Amaru can serve blocks

• @rkuhn: implement in Amaru the chain selection algorithm from Genisis 'densest chain selection' and eclipse use Mithril snapshots

• @etorreborre: working on simulation to generate better data and created an animation to showcase the tree and the decision behind deciding which chain is the better; found a bug thanks to doing that visualisation and showcasing what we do; working on making data better and visualisation

• @Dam-CZ: we will need to have a documented architectural perspective and the decision for the implementation choice in an EDR for Amaru, some kind of a "assumptions registry" once we have a binary release pipeline

Amaru proposal for 2026

The technical roadmap has been updated based on our latest items that will make us deliver a relay binary and a block producing binary

The current items considered for 2026 are available in our Whiteboard playground and currently being tailored for our proposal

[Dam-CZ]

25th November 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Amaru proposal for 2026

Amaru budget being built with discussions on scope owners and such, timeline is to make an on-chain budget info action before Christmas.
The technical roadmap has been updated based on our latest items that will make us deliver a relay binary and a block producing binary.
The current items considered for 2026 are available in our Whiteboard playground and currently being tailored for our proposal

Demo 19th December: final stop of the year

Content to be updated, current draft:

• Showing Antithesis test cases linked to mainnet forking events (Arnaud)
• Rough implementation of transaction propagation with Amaru (Eric)

Round table of people connected to the call

• @abailly: setting up docker, starting Antithesis and building the environment around it, test fails related to timeouts; mostly setting up Antithesis; working on replicating the network split using antithesis + Haskell node + Amaru as a proof of concept to advocate for more Antithesis use cases and show that Amaru follows the right chain in that case

• @abailly: scheduling time with Antithesis later this week to run Amaru;

• @etorreborre: simulation found a bug thanks to the environment, added a CI tasks linked to the simulation; working on a transaction submission protocol (server, client, mempool simple setups) testing basic setup and working on running edge cases; by the end of the week plug everything into Amaru

• @JSHy: working on script evaluation, UPLC work is almost ready (benchmark & testing ongoing), not dependent on a version of Plutus, Phase 2 validation optimisations ongoing, will require some changes to phase 1 might not be the right time to make changes because of the impact, working on a worst case scenario and cloning the whole data to have something working before optimizing the setup

• @JSHy: working on a robust testing for primitives on Amaru and being able to own the data and logic linked to Pallas (library and API)

• @etorreborre: Pallas network and data types are missing, currently using parsers to make room for it, what should be the next step for using Pallas? (PR for Pallas? Internalize and remove a dependency?)

Overall discussions hinted towards internalizing the features required as we move forward

• @rkuhn: while needed a type, moving it to the Amaru network is the go to next step, but we need to organise the "Amaru kernel" and breaking it up into crates; we will need different types and have a crate that captures the protocols and the data types, we will build it the way we need it; publishing the library will be an additional effort and require a PR review process taking into interfaces and dependencies

• @JSHy: just a quick note of developing the debugging tool based on Amaru's implementation to solve Friday's event faster was a faster and smoother way forward than anything existing, so congratz to everyone who built Amaru so far :)

• @rkuhn: working on a multiplexer that will help building the miniprotocols

• @jeluard: Raspberry Pi was very successful didn't have enough to give away, working on the image and a Web-API or Bluetooth-API to use the Pi as a Hotspot to connect; looking into the Mithril PR waiting for Matthias to merge it and apply it.

[Dam-CZ]

9th December 2025 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Amaru proposal for 2026

Amaru budget still ongoing discussions on various topics, see our latest draft on hackmd

Round table of people connected to the call

• @abailly: Antithesis CLI now working

• @etorreborre: Most of the code in place with transaction propagation, tried many configuration and not working

• @etorreborre: Amaru node is going to cold to warm to cold again; not the same behavior of 2 Haskell node; need someone with the networking knowledge to analyse that

• @etorreborre: wasm failing the CI (dependency created for Pallas) that makes the wasm build fail; main goal: isolate from the network crate the Pallas types

• @etorreborre: help with testing end to end the minimal

• @abailly: transaction submission client can be used to test out

• @etorreborre: current goal is to get a PR with the code, the CI passing

• @rkuhn: git random dependency not useless, needs a feature flag to work specific type

• @etorreborre: actor framework, swallowing something wrong that the forwarding chainsync; missing blocks from genesis could be a problem? Neil Marcin & Roland > Networking meeting 15th December could solve it

• @etorreborre: Pieces that are necessary and pieces that are missing for transaction propagation

• @rkuhn: depending on Pallas for the handshake; Karl said that there's a bug in the handshake in Pallas; reimplementing the whole networking stacks

• @etorreborre: relationship with Pallas (instances in Pallas with Rust) relying on the branch for the Pallas dependency - will need to get into the Txpipe office hours

• @KtorZ: rewriting the kernel to not depend on Pallas anymore and make Amaru own the primitives types; owning the deserialiser and be in control

• @geoff: auto update flow for the Amaru Pi: receive automatically update for the products distributed at the Summit; some debugging needed still

• @geoff: creating a document for specific goals in refactoring the storage traits;

• @JSHy: Ledger side getting close of Phase 2 validation; running on Preprod and almost close to the tip (bug in Conway currently); and having actual tests

• @JSHy: Found UPLC evolutions that can be nice; validation context improvements are nice

• @JSHy: preparing the storage traits CBOR bits, to list out the things that might be nice to improve overall the node performance; having some people using the node and already complaining, it's a good sign

• @jeluard: Running Amaru on a mobile phone was pointed out, probably like Daedalus, not sure if the project still works; related to using Amaru as a library, started to implement PR about

• @KtorZ: cleaning up things to be focused on Amaru; need to resynchronise with everyone to get the big picture of what's missing with the relay and where we can get closer

• @rkuhn: working on a big PR; upstream reconnection bug

• @geoff: error hosting (panic on rollback) (wetransfer)

[Dam-CZ]

6th January 2026 - Maintainer Committee

Agenda

No set agenda, overall discussions on progress and decisions required

Amaru proposal for 2026

Amaru budget still ongoing discussions on various topics, see our latest draft on hackmd

Round table of people connected to the call

• @KtorZ: Day to day activities, we need to resolve the snapshots issue with the disk space

• @KtorZ: Phase 2 validation sanity check before going into more optimisation

• @KtorZ: Cache behaviour needs to be checked (Windows is 5Gb; Linux is 2Gb) mostly Rust dependencies, have to investigate why is it that big

• @KtorZ: new EDR how the CI is setup and how it works and how it works > documenting

• @KtorZ: epoch by epoch snapshot test and conformance validation needs some work

• @KtorZ: wanted to publish the Amaru budget by early December 2025 but made a lot of changes and some are still ongoing

• @JSHy: eager to merge Phase 2 validation

• @JSHy: Jonathan working on UPLC VM stuff

• @JSHy: Officially part time on the Amaru project now

• @jeluard: experimenting with mobile & desktop, quite easy to run Amaru on mobile, could be a nice community topic to pursue

• @jeluard: trying to ease the bootstraping snapshots creation, worked on cleaning up the environment (boostrap will fail if you have a db); will move to testing snapshots; improving the way we run Amaru and the way we run tests

• @jeluard: preview doesn't sync to the tip, not sure why, issue has been open to investigate

• @jeluard: removing the V9 protocol support as a way to simplify the internal logic (forces us to keep track of things we don't really need) > need more recent snapshot in order to achieve this

• @JSHy: as a temporary forcable snapshots and upload the ledger db to use as a bootstrap (one from an already synced state)

• @JSHy: should be able to run from a Haskell snapshot / bootstrap from it

• @jeluard: started working on having a better convention & standard related to opentelemtry / traces / logs (using it as an API for 3rd parties with "1 right way of looking at traces")

• @jeluard: having things that triggers when traces are broken; being aware when we remove spans

• @etorreborre: we are collecting traces in Json and we need to work on it a little bit

• @jeluard: we need to work on traces and have some kind logic

• @etorreborre: working on a big PR to finish implementing the miniprotocols on top of the pure stage framework, following the execution of all the miniprotocols right now; Roland did some refactoring to have a mini state machine for each
  (txsubmission is being transferred to it) there's still some work to be done on the PR

• @etorreborre: after this is done, we will have the upstream part working, but not the downstream part