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