Agenda: Development, 23 September 2025

[cekickafa]

Solicit suggestions for agenda items for Development meeting to be held on Tuesday Sept 23 @ 19:30 UTC in Grin Governance Public Telegram Group Grin Governance Public Telegram. Please comment to provide topics or suggestions.

Follow Up.

• Fixing peers, grin++ node bans Rust nodes.
• Payment proofs fix.
• Grin Github organization.
• Grin MultiSig
• Grin Node meets UmbrelOs, EmbassyOs
• Cuckatoo reference miner

Proposed Agenda

Discuss ongoing development efforts and practicalities.

1. What is everyone working on?
What would you like to work on and what time-frames are we expecting for each

Open Pull Requests:
https://github.com/mimblewimble/grin-wallet/pulls (15 open PR's)
https://github.com/mimblewimble/grin/pulls (15 open PR's)

2. Who is willing available to take on Reviewing
Some of these pull requests are stuck because they need reviewing. Which ones (assign/reference reviewers on github)?

3. Cleaning up gihub issues
Which old PR's and issues can be closed. Clean up and better managed Github PR's and Issues. Who to contact to apply changes like closing PR's?

4. Developer practicalities

• What problems are there, e.g. do we have good template tutorials for working with Testnet?
• Are all Developer resources (e.g. Ansible workflow) listed properly somewhere, e.g. Grin Hub.
  -Which branch best to work on/prioritize, main or contract?
  -If time allows it, share tips and trick for Rust development, e.g. AI use, editors, plugin's etc.

[Anynomouss]

Developer/Development oriented meeting
Suggestions for the agenda are welcome.

1. Discuss ongoing development efforts and practicalities.

• What is everyone working on? What would you like to work on and what time-frames are we expecting for each

2. Open Pull Requests:
   https://github.com/mimblewimble/grin-wallet/pulls (15 open PR's)
   https://github.com/mimblewimble/grin/pulls (15 open PR's)

• Who is willing available to take on Reviewing some of these requests and which ones (assign/reference reviewers on github)?
• which old PR's can be closed (e.g. redundant updates). Clean up and better managed Github PR's and Issues

3. Developer practicalities

• What problems are there, e.g. do we have good template tutorials for working with Testnet?
• Are all Developer resources (e.g. Ansible workflow) listed properly somewhere, e.g. Grin Hub.
• Which branch best to work on/prioritize, main or contract?
• If time allows it, share tips and trick for Rust development, e.g. AI use, editors, plugin's etc.