Council Meeting Notes December 20, 2022

Community Council (CC) meeting held @ 10 UTC in grincoin#general channel on Keybase. Meeting lasted 98 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 Attendence

  • anynomous
  • future3000
  • cekickafa
  • dtavarez
  • defistaker
  • yeastplume

Short Summary

  • Python wrapper bounty is reopened due to @walkbackgod not responding.Developer @nicolasflamel made contributions and volunteered for the bounty. GRINCC supports @nicolasflamel on principle, feedback from @renokuken will be observed.
  • Request for funding @dtavarez discussed and community voted. Technical deliverables is defined as Grin++ CLI, API & documentation.
  • Request for funding @cekickafa discussed and community voted. Tasks are defined as financials, drafting transactions, keeping account and newsletter.
  • Meeting notes task assigned to @satoshocrat, his funding requests will be voted.
  • Test miners electricity costs payment is discussed and agreed on paying @mattczt for duty tax bill cost.
  • Grin/Wallet Api problem is discussed, focused on getting developers communication to each other so they can respond more quickly.

Voting Results

  • No voting has been held.

1. Request for funding @davidtavarez January-April 2023

Forum discussion

anynomous : My opinion on this funding request is that I am in favour. I always wanted grin rust and grin++ to exist as equals with unified API's for any downstream developers. The only question I have is if this tasks will require 3 months or not. Maybe @yeastplume can better estimate how much time such a task takes.

dtavarez : I want to make it easy for people to develop new things on top of Grin++ now and in the future, but that requires a robust API. And thatโ€™s what I want to continue to focus on. The current API is very UI-bound at the moment, and this should be improved. I have been working on improving the API using as a guide the API in Rust, the RFC and adding the changes that I think are important. In order to make sure things are working fine, I will bring to life the CLI version of Grin++, this CLI version should be using the new APIs and it should have a basic compatibility with the Rust API.

๐Ÿ‘ anynomous

future3ooo : @nicolasflamel1 please feel free to submit a funding request if you want to contribute more. We need more core devs.

๐Ÿ‘ anynomous,defistaker, nicolasflamel1, cekickafa, johndavies.

dtavarez : Recently Satoshocrat managed to compile the master branch for a Raspberry Pi4, this is a huge step, and simplifies the efforts on increasing portability. I would love to make possible to users to run their Grin++ wallets on their Pi4, and a CLI version seems to be more reasonable to me. just for the record: the SecureAPI flow won't be implemented on Grin++

anynomous : True, Grin++ would be to heavy in its current form on a Raspberry Pi. I run only the rust wallet and node on my pi's. Regarding the secureAPI, I know this has been debated and many do not like it, I simply have to get experience myself using it to see if indeed it is so hard to handle, or if it actually is a great security feature.

dtavarez : In my personal experience, and in my experience supporting developers, the benefits of the SecureAPI flow do not outweigh the hustle

anynomous : Ok, I think we need more eyes on this/opinions and if needed bug reports, for now you can simply not implement it in Grin++.

dtavarez : but again, that is just my opinion.

defistaker : Can I ask to summarize deliverables on the funding as list items so that I can put it in grincc.mw

๐Ÿ‘ anynomous

dtavarez : if someone else writes the flow for Grin++ the code will be of course reviewed and merged potentially.

anynomous : @dtavarez Can you summarize the deliverables.

dtavarez :

defistaker : Can I ask to summarize deliverables on the funding as list items so that I can put it in grincc.mw A CLI version runinng on a Pi4 and using the new API can summarize everything.

defistaker : Using the new API on raspberry pi?

anynomous : The new API = a unified API between Grin++ and grin rust? I personally like it more that way.

๐Ÿ‘johndavies

dtavarez : compatiable with this API https://docs.rs/grin_wallet_api/latest/grin_wallet_api/trait.OwnerRpc.html

๐Ÿ‘ anynomous, defistaker

anynomous : Ok, good. Lets proceed with voting. Everyone in favour or against funding David for this request (also non-council members can indicate their vote) with ๐Ÿ‘๐Ÿ‘Ž.

๐Ÿ‘johndavies, anynomous, future3ooo, nicolasflamel1

dtavarez : I am in favour ๐Ÿ‘

cekickafa : are you voting yourself?

anynomous : David can indicate but his vote is not counted. I need more thumbs thereโ˜๏ธ, either up or down, or voice any concerns now.

dtavarez : I did not vote.just made a comment

cekickafa : are you voting yourself? why so serious? ๐Ÿ˜…

anynomous : You could have also commented a vote against yourself :)

๐Ÿ˜…dtavarez

cekickafa : hehehe

cekickafa : i am serious.Especially about decision. Related to Grin direction.

dtavarez : Grin is fine, Grin will be fine, don't worry

anynomous : No one is allowed to vote for their own funding requests, that would be corrupt. So in the end we take into account all votes and concerns of both regular community members and CC members, but only the CC members vote that result based on that feedback will be used to make the descision.

๐Ÿ‘johndavies, cekickafa

cekickafa : no doubt it will be fine.

anynomous : Ok, I have three votes in favour, of which two from non-funded community members, we will need more to finalize the desciscions. I anyone has any more feedback or concerns, voice them now. My only concern would be if the workload is indeed 3 months work full time.

cekickafa : it is January to April= 4 Months or mistaken ?

anynomous : Good point, 4 months.

dtavarez : I had added more endpoints previously, for example, but then, when I tried to apply them in the desktop version I realized my mistakes at first So this time instead of writing the C++ code blindly I want to write the implementation right away to make sure they are actually usable that's why I am including the CLI not just the APIs, so we're talking about the APis, Documentation and a CLI.

anynomous : Ok, I think only other developers can estimate how much time it will take exactly, it will probably also really depend on how you implement it. For me it is ok to take the vote further to the other CC members since we have also other agenda points to discuss. It is just a pity there are not other developers present here to give their feedback.

Next agenda point.

2. Request for funding @cobragrin Dec-March 2023

Forum Discussion

anynomous : We discussed within the CC how much we actually want to spend on Groundkeepers. Since Grin is rather calm right now (actually a good thing for development), we would like to cap total funding of Groundkeepers at 2.5k$. This would mean that with this funding request, 1500$ would go to @cekickafa and 1000$ would be available for @satoshocrat. There is a lot of room for discussing distribution of tasks.

dtavarez : based on previous discussions the Groundkeepers tasks are the next: 1- Administrative tasks. 2- Writing & Publishment of Developments, upgrades and news 3- Finance PR Contributing to grincc/finance PR for transparency and accountability. 4- Tracking, calculating and making sure the draft are created. I think @cekickafa is doing an excellent job with the Administrative tasks. I support him continuing to do it.

cekickafa : i would like to keep financial tasks and grin newsletter, tracking and calculating payments . Satoshocrat can take meeting notes.

dtavarez : I think that is quite a load for just one person

cekickafa : i am fine with it.

anynomous : I think that is a reasonable workload for 1.5k$

cekickafa : You said satoshcrat will help you with documentation. my task are clear and transparent.

dtavarez : 4 main tasks, 2 people, 2 main task for each person is that simple the newsletter is OK so far, but I think there is a space to improve it

anynomous : Probably we can ask volunteers to provide input, like technical pieces or so.

cekickafa : The newsletter's goal is to summarize the most recent and important Grin upgrades and developments so that people know Grin is not dead and can quickly see the status of Grin, save them from having to look for the latest news themselves. Ipollo and Nhash appreciated the newsletter and asked specifically to be recognized in it for their donation of Test miner G1 mini asics.

dtavarez : and I've been clear enough already about what I think in regards of the spending logs and the tracking, and calculation topics

cekickafa : But you will focus on technicals or those financial , governance isssues?

dtavarez : what do you mean?

cekickafa : yeastplume is heavily busy with gui wallet, grin++ and you funded well also and should be responsible for acknowledging bug reports and, if possible, attempting to resolve the issues. Renzokuken python is an example

cekickafa : But you will focus on technicals or those financial , governance isssues? that is a workload you interfere still i meant.

anynomous : It is easier for developers to detect bugs and make reports because they are the ones encountering them.

๐Ÿ‘ cekickafa

dtavarez : I am just saying is it way better just to focus in one or two things instead of 10 and that applies to everyone I am not writing the newsletter and I am just giving my opinion on how can be better

cekickafa : yes, it will apply to everyone

dtavarez : I can only focus on Grin++ right now for example

cekickafa : Anyone is free to start and contribute a newsletter, hope they do.

anynomous : Can we summarize this and wrap it up, or the meeting will extend to much.

dtavarez : it seems to me we do not have an agreement on what the tasks are for the groundkeepers.

cekickafa : i am fine with GrinCC decision. i will contribute and do my best as usual.

anynomous : Ok, those tasks are the financials, drafting transactions, keeping account and newsletter (of which later in cooperation with Satoshi and anyone who contributes a piece). I would like to request everyone to vote using ๐Ÿ‘ ๐Ÿ‘Ž

๐Ÿ‘ anynomous, defistaker, future3ooo

dtavarez : so indeed we could group the tasks in 4 categories, right? 1- Administrative tasks. 2- Writing & Publishment of Developments, upgrades and news 3- Finance PR Contributing to grincc/finance PR for transparency and accountability. 4- Tracking, calculating and making sure the draft are created.

future3ooo :

cekickafa : Anyone is free to start and contribute a newsletter, hope they do. I can start to help assist you with parts of the newsletter if need be.

๐Ÿ‘ cekickafa, dtavarez โ™ฅ๏ธ johndavies, anynomous

dtavarez : my suggestion is to split the workload in two

cekickafa :

future3ooo : I can start to help assist you with parts of the newsletter if need be. thanks, i will give you the contribution rights.

anynomous : Lets not forget the vote โ˜๏ธ

dtavarez : there is no need for one person to do everything, and by dedicating more time to a task I understand that the final result can be better. can we move the decision one week?

anynomous : Yes, at @satoshocrat for your funding request we will expect you to be actively involved in the newsletter. Actually, we can also postpone the vote itself, since both funding requests for groundkeepers are less than a day old, which is a bit short for vote although I can already say I will vote in favour.

dtavarez : just to make sure we are all in the same page

cekickafa : Satoshcrat contributing the newsletter is minimum. So i dont see any benefits about discussion.

๐Ÿ‘ anynomous

anynomous : Ok, in that case we need others like @future3000 to help with checking the text and such.

cekickafa : i will handle the contribution right to @future3000 as well.

dtavarez : the problem here is that it is not clear what is the expectation for each groundkeeper.

cekickafa : it is clear

dtavarez : it is not

anynomous : I think mostly for @cekickafa it is clear, for @satoshocrat we now only have the note keeping, so there is room for either more work-load or less funding.

๐Ÿ’ฏ cekickafa, future3ooo, defistaker

dtavarez : I suggest we split the workload in two and see how things goes

anynomous : I think for @cekickafa the three tasks for 1.5k$ are fine as long as there is some help/input on the newsletter. For @satoshocrat we should have another look at the funding request and see what tasks can be added/removed, as well as what he wants himself.

๐Ÿ‘ cekickafa

dtavarez : thing thing is that the newsletter can be improved, and the finance reporting is incomplete

cekickafa : Satoshocrat term is after me. We are one month off of cycle anyway.

dtavarez : thing thing is that the newsletter can be improved, and the finance reporting is incomplete Becuz you didnt review it ?

anynomous : I think for example keepting notes + technical tasks such as these for @satoshocrat :

"My proudest contribution this cycle has been undoubtedly troubleshooting and testing successfully the compiling of Grin++ on RPi running Ubuntu 22.04. This task I did have guidance from David Tavarez on the linux-specific processes, but the research and hours of quasi-masochistic trial and error was both fun and fruitful."

Would be fine.

๐Ÿ‘ defistaker

dtavarez : the Administrative tasks have been solved by @cekickafa very well not doubt. I would like to see how @satoshocrat can improve the newsletter

anynomous : That is also an option, but @satoshocrat should get more involved then. In any case, extending to 1.5$k would be a bit much IMO since then we would spend 3k on basic work while our objective is only 2.5k$ in total.

future3ooo : Iโ€™m happy to approve @cekickafa โ€˜s request now and discuss @satoshocrat โ€˜s further.

anynomous : I think we can do the final vote in 2 weeks from now, but the discussion here already indicate that most are in favour of approving the funding request from @cekickafa, for @satoshocrat we have to fine tune the workload a bit to fit 1k$ Lets move on to the next topic, since we are already in over time.

dtavarez : I am not in favour as it is right now

anynomous : Ok, can you specify. Or do you want to pospone that for the forum or the meeting in 2 weeks.

dtavarez : bad in the results, my logic tells me that it is too much of a burden for one person. I would suggest to pospone the final decision

cekickafa : https://forum.grin.mw/t/cekickafa-progress-update-sept-december/9662/9

my tasks are trasparent and questionable. We dont need this drama. Job is done. Why this mess ?

๐Ÿ‘ johndavies

anynomous : Ok, we need to discuss this more. Based on the results I think @cekickafa has no problem with the tasks assigned, appart from that he needed more input/checking of the newsletter, which only minimally happened.

๐Ÿ‘ cekickafa

dtavarez :

cekickafa : https://forum.grin.mw/t/cekickafa-progress-update-sept-december/9662/9 my tasks are trasparent and questionable. We dont need this drama. Job is done. Why this mess ?

I have already explained myself several times, it is not drama.

cekickafa : you are complicating everything, offering a problem, presenting it like a solution and complaining and accusing us after it.

dtavarez : I'm sorry if I am not being clear enough that's why I want to suggest to pospone the decision maybe I am getting things wrong

cekickafa : everything is clear.

anynomous : Ok, sorry, I am going to interfere here. It is clear that some of us want more discussion, but the general sentiment is clear that there is support for this funding request. We can leave further discussion for the forum, or the next meeting simply because the post is less than 24 hour old, we agreed we would always give the community around a week to give their input

๐Ÿ’— johndavies

No need to complicate it, but in that way no one can complain.

cekickafa : My funding period already ended on December 15. I need the payment if approved.

anynomous : For me it is simple, the results have been good, newsletter needs more input, so we can give it or @satoshocrat has to step up since he was supposed to do this as well. But again, that discussion is for later.

dtavarez : 1 out of 4 tasks are good

cekickafa : I have organized Grinฤฐstanbul last month and covered all expenses on mine

dtavarez : 2 (the newsletter) can be improved and the financial logs are awful I am saying: just focus on 2 out of 4 tasks

anynomous : We can make the vote in 6 days from now, you already have my and @future3000 ๐Ÿ‘

cekickafa : Thank you.

anynomous : This discussion can be continued on the forum.

dtavarez : good

cekickafa : excellent

anynomous : Our next topic: Sorry, I am combining both for the sake of time,

3. Request @jaw709 Jan-April 2023.@navie funding Dec 22- Q1 2023

dtavarez : https://forum.grin.mw/t/request-for-funding-navie-dec-2022-q1-2023/10210/6?u=davidtavarez

one user offered himselfs to funding this

anynomous : We have to check if indeed that user paid, no need to pay another time

dtavarez : correct. if the userd did not send any transaction, I am in favour of the CC supporting this

anynomous : Also, we could ask them to disconnect their miner, we will see a drop in hashrate, which will give proof they were mining Testnet. Or we just pay on faith.

cekickafa : With Grinmint.com you can connect and check with email.

dtavarez : https://testnet.grinexplorer.net/

they are not using grinmint.com. they are doing solo mining

anynomous : In that case we can ask them to drop the connection as proof.

dtavarez : I provided them with the nodes

anynomous : Ok, we will ask such proof, then we can pay @jaw709 , for @navie we have to check if he already was compensated. @cekickafa can you contact him on the forum (TO DO for next meeting)?

cekickafa : Sure.

๐Ÿ‘ anynomous.

future3ooo :

anynomous : Ok, we will ask such proof, then we can pay @jaw709 , for @navie we have to check if he already was compensated. Ok so pay both now unless naive has been paid.

cekickafa : jaw709=satoshocrat. Mattczt3 runs test miner.

๐Ÿ‘ anynomous.

anynomous : ok.

cekickafa : Mattczt demads duty custom bill for 65 pound and electircity costs 34.5 pound as well

future3ooo : I donโ€™t like cc paying electric but Iโ€™m happy to approve the first payments on good faith. Donโ€™t need to drag out any longer

๐Ÿ’ฏ anynomous

anynomous : Rather expensive, but that is the UK unfortunately. I am also ok to pay on good faith, since micromanaging costs a a lot of peoples time. But yes, I also would have liked electricity to be paid/volunteered.

๐Ÿ’ฏjohndavies

cekickafa : https://github.com/cekickafa/finance/blob/main/pending-payments.md

I will add here.

๐Ÿ‘ anynomous.

anynomous : Ok, next and last topic.

4. Wallet issues; mimblewimble/grin-wallet.owner api

cekickafa : yes that is important issue.

anynomous : I can try to reproduce the issue. If one cannot retrieve a transaction log, that is rather bothersome. But maybe the problem has to do with other details, e.g. maybe id=0 should be id=1, I will have a quick look at it this week. It would be better though if those who have experience with the software answer, such as the developers @yeastplume. Is there more to discuss regarding this bug that appears to be rather problematic since @Marekyggdrasil is losing his motivation over it?

defistaker : That is the most important thing, He was very motivated on telegram Grin Bot

๐Ÿ‘ future3ooo

He even plans to extend it to a general framework for bot development.

cekickafa : @renzokuken is a honest Grin fan. I would like to see him more with Grin developmment

๐Ÿ‘ anynomous

defistaker : Grin should not lose a capable developer like him.

anynomous : I hate it when unnecessary problems like these kill someone's enthusiasm, but I can understand. It remains to be determined if it is a problem with help/support, the software, documentation or just bad luck. In any case we have to take practical issues like these serious.

future3ooo :

cekickafa : @renzokuken is a honest Grin fan. I would like to see him more with Grin developmment Yes, I hope he takes a break to reset and then submits a funding request.

๐Ÿ’ฏcekickafa

defistaker : No one is responding on the issue also.

yeastplume : I have a lot of things going on, but I'd absolutely take this seriously if someone came here and brought it up and said it was affecting their project. Thing is, first I heard about any of this was a twitter rant about how unresponsive devs are. I thought this to be grossly unfair, it's not like he doesn't know how to find me.

๐Ÿ‘ anynomous

anynomous : Ok, so in this case it basically was just a missed communication issue. Maybe next time not only report the bug but also directly contact on KeyBase @renzokuken, since I know @yeastplume to be very responsive there.

yeastplume : Unfortunately, putting an issue up on github isn't enough, I have no idea how serious this is for somebody's project unless they let me know about it. If he'd just asked, I'd have looked at it immediately.

๐Ÿ’—anynomous, cekickafa

dtavarez : I think he asked

anynomous : Ok, in that case I think we do not need to discuss it further but just to remember to keep close contact and direct communication channels. Also, it is fine for @renzokuken to just take a break of submit a funding request when he is running out of finances of motivation.

๐Ÿ’ฏcekickafa

dtavarez : @yeastplume what would it be the proper way to report things then?

yeastplume :

dtavarez : I think he asked He couldn't have asked me directly because I wouldn't have ignored him

future3ooo :

yeastplume : Unfortunately, putting an issue up on github isn't enough, I have no idea how serious this is for somebody's project unless they let me know about it. If he'd just asked, I'd have looked at it immediately. Can you please look into it now ?

dtavarez :

yeastplume : He couldn't have asked me directly because I wouldn't have ignored him that's true

yeastplume : Putting stuff up in github is a good start, but because it's mostly just me on 4 grin-related repos now, I can't prioritize unless people get my attention in some other way.. I do see the issues but it's not always clear that it might be having a huge detrimental effect on someone's project.

dtavarez : to be fair when someone report something on Grin++ they tend to DM me directly but most of the times I do not like it that way

yeastplume : Yes, unfortunately people might need to shout a bit louder if an issue is directly affecting them

๐Ÿ‘ johndavies, cekickafa

cekickafa :

yeastplume : Yes, unfortunately people might need to shout a bit louder if an issue is directly affecting them i will take this advise seriously.

anynomous : Unfortunately I have to go right now. Before I leave, I would like to to Thank you all for your input and also make you aware of this thread: https://forum.grin.mw/t/grin-gui-excitement-thread/10204/31

I hope you are as excited as I am๐Ÿ˜๐ŸŽ‰!. @yeastplume my virus scanner flags the gui build, I will later look what the problem is, but we should try to avoid that ofcourse.

๐Ÿ‘future3ooo

cekickafa : GUI ๐Ÿ’›

yeastplume : Anyhow, I am happy to look into it, and will prioritise if he's not taking a break.

๐Ÿ‘ anynomous ๐Ÿš€ cekickafa, future3ooo, anynomous

Heh, only caveat is that nobody's allowed to shout about the GUI yet, it's too new ๐Ÿ˜€

๐Ÿ’—johndavies

anynomous : Thanks all ๐Ÿ‘‹ Feel free to continue the discussion.

๐Ÿ‘‹ defistaker, yeastplume, future3ooo, cekickafa

Meeting adjourned

Action Points