Skip to content

Latest commit

 

History

History
73 lines (55 loc) · 5.68 KB

20210601-meeting-development.md

File metadata and controls

73 lines (55 loc) · 5.68 KB
Raw

Meeting Notes: Development, June 01 2021

Governance meeting held @ 3PM UTC in grincoin#dev channel on Keybase. Meeting lasted ~ 45 min.

Notes are truncated, and conversations sorted based on topic and not always chronological. Quotes are edited for brevity and clarity, and not always exact.

Community attendance:

  • joltz
  • geneferneau
  • phyro
  • quentinlesceller
  • mark_hollis
  • tromp
  • dburkett

(apologies if I missed someone - submit a PR or contact @lehnberg to add)

Agenda points & Actions

Action follow-up

  • joltz: I trust @phyro is still chugging along on the never ending triage For "fixpastfees" I know the RFC got merged, were the code PRs merged as well? Yep, looks like it mimblewimble/grin#3629

2. Agenda review

The [proposed agenda](agenda for dev meeting later today - mimblewimble#424) was accepted without changes.

4. 5.1.0 release

  • joltz: For 5.1.0 release we had an issue with launching in certain environments mimblewimble/grin#3641 It looks like there was maybe some progress since last dev meeting, but I'm not sure we have landed on anything actionable? Or maybe we have with the build process
  • geneferneau: afaiu, the problem doesn't occur with source build
  • joltz: Right, it is an optimization in how the binary is generated by us?
  • tromp: croaring builds use avx2 instructions unless prohibited with ROARING_DISABLE_AVX
  • geneferneau: don't know if its fixed on the build machines
  • quentinlesceller: Yes disabling avx should do
  • tromp: or with -mno-avx flag to gcc - we need someone familiar with build scripts to try these options and test on a machine with no avx support
  • quentinlesceller: it's here: https://github.com/mimblewimble/grin/blob/master/.ci/release.yml#L7 I could potentially try and fix it.
  • joltz: That would be great @quentinlesceller if it is a quick fix for you. If not let me know and I'll try to find someone to work on it 🙏
  • quentinlesceller: tbh that's a quick fix for me, I'll do it

5. Review atomic swap RFC/PR mimblewimble/grin-rfcs#80 && mimblewimble/grin#3643

  • joltz: It sounds like there is some active ongoing discussion there shame on me for not having engaged much there yet It is an exciting and important area though and will certainly benefit from more engagement Is there anything in those discussions or processes worth highlighting here?
  • geneferneau: definitely, going to make a forum post suggesting a modification to SAS. hopefully, get some feedback from Ruben Somsen- need to implement multiparty outputs in grin-wallet which requires exposing multiparty bulletproofs (already present in secp256k1-zkp) to Rust and grin-wallet- side benefit: Grin multiparty outputs should be generally available after
  • joltz: yes, and multiparty is long overdue for grin imo, glad to see it is being picked up- definitely one of the most exciting things going on in the grin ecosystem right now, thanks @geneferneau!
  • geneferneau: you're welcome 🙏

6. Bounty updates

  • joltz: Anything to add for the bounty update @mark_hollis? We got a nice update a week ago https://forum.grin.mw/t/grin-ledger-hardware-wallet-progress-thread-by-markhollis/8670/13
  • mark_hollis: This week I had some troubles building grin++, this is solved now. Now I am at back grin-walle,t focusing on how to serialize the data to send to the device. Thinking about something like Partially Signed Bitcoin Transactions, but for Grin. It's a format for serializing transactions. The Ledger firmware should expect the data to come in a certain format. This should be uniform for both grin-wallet and grin++ and possible other wallets. thanks to @geneferneau for mentioning psbt's.
  • quentinlesceller: very nice @mark_hollis
  • joltz: thanks @mark_hollis it's great following your progress on this, thanks for your strong efforts 🙏
  • geneferneau: great work @mark_hollis

7. Grin wallet PR to add Tor bridge support. mimblewimble/grin-wallet#617

  • joltz: This will be an important update for users located in places where Tor is blocked. Thanks to @deeev I made a few comments, would be great for others to weigh in as some decisions need to be made about how to handle this extension Nothing too involved though Mostly just wanted to bring the PR on everyone's radar to give any feedback they may have, and to highlight @deeev's contribution

###Other Questions

  • joltz: it looks like there is a suggestion about a CHANGELOG.md. I think it's a great idea if we can find someone willing to consistently put one together without adding more to the plates of existing contributors

  • geneferneau: is there a way to script/automate the changelog?

  • joltz: It's possible. The usefulness would probably depend on the descriptiveness of PR titles, commit messages etc

  • geneferneau: I could spend some cycles looking into it

  • joltz: IMO, I wouldn't worry too much about it and stay focused on your current work. But if you need a break and want to look at something else for a bit..

  • geneferneau: definitely

  • joltz: I noticed there was a comment about a funding request made to the meeting issue, but it is more appropriate for the next governance meeting

  • dburkett: Does it even make sense to separate governance and dev meetings anymore? we get roughly the same attendance regardless of which meeting it is.

  • joltz: I plan to add this as a point in the next governance meeting

  • quentinlesceller: I'd vote for a bi weekly dev + gov meeting. and return to "normal" once there is more activity

Meeting adjourned.