Community Council (CC) meeting held @ 15:00 UTC in grincoin#general channel on Keybase. Meeting lasted 67 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.
- nicolasflamel1
- cekickafa
- dtavarez
- defistaker
- anynomous
- yeastplume
- quentinlesceller
- future3ooo
- Dissolving the GRINCC and returning funds opinion is voted against due to feedback from community and council members.
- Suggestion about allowing GrinCC Github access to groundskeeper is voted & agreed.
- The demand for unlocking Support for Nano Hardware wallet bounty decision is left to Original council.
- On Python wrapper bounty current progress, @cekickafa will contact @walkbackgod.
- Process of payment managements about approved funding requests is to be tracked by @cekickafa.
- A time period of 48 hours is defined with regard to the signing of transactions by key holders for approved funding requests.
- Community farming project management is being discussed.
- Test miners check-management is discussed.
- Gui wallet development is mentioned by @yeastplume.
-
Last meeting notes here: https://github.com/grincc/agenda/tree/main/notes
-
Current meeting agenda
future3ooo : I’m here but don’t expect much input. Just woke up and it’s 4am
anynomous : Good luck waking up ☕ Lets take a minute to read the agenda, if anything needs to be added let us know. Lets start.
First agenda point:
anynomous : @future3000 gave a nice summary of the discussion Github
Brief summary from forum discussions:
not everything is included.
Question for all CC members: Does anyone want to leave?
Vote: Should a groundskeeper be added as a keyholder and be responsible for drafting all transactions ? inline with this proposal here:
Agenda: Community Council (CC), 22 November 2022 #72 (comment)
Vote: Should the limit to send a transaction from an approved funding request be 24 or 48 hours?
Discussion : If a grounds keeper is not added as a key holder, then who's responsibility will it be for drafting transactions ?
Further Discussion
1.CC mining farm management. What exactly is required | Who's willing to step up and manage the admin side of it.
-
Should specific CC members take responsibility for leading meetings, or just whoever is around? I'm willing to lead the 10:00 UTC meeting.
-
Should CC members be excepted to be anything more than key holders?
-
What should the max time limit be to vote on a funding request?
-
If CC is paying electric cost for testnet miners, how can er verify that those specific miners are on testnet?
-
Is anyone willing to take responsibility for managing the CC Grin payments ?
cekickafa : yes, it is all summed.
anynomous : First thing that I find important to mention is that I noticed based on the discussion that the 'problem' or the feeling of there being a problem is mostly limited to the Community Council itself. To be more specifically @dtavarez feels strongly about this since he has been patching up the gaps of activity of other members and since he did not receive his 10% Grin payment in time. All in all we can learn lessons from these mistakes, but I have the impression the community itself is not asking the CC to dissolve or return funds.
cekickafa : I didn't get that impression either about dissolving.
dtavarez : 👋
👋 anynomous, defistaker
defistaker : I am against it for one, there could be on-going projects which we may or may not know that can apply for funding. We have a procedure and funds to develop Grin, we should hold on to it.
future3ooo : I vote no to dissolving.
anynomous : I also vote agains disolving, I want to make procedural improvements, but am 100% against stopping our activity all together.
dtavarez : maybe we could integrate some of the lessons learned to the procedures that would it be a good outcome imo.
👍 future3ooo, anynomous
anynomous : One of the most important improvements we have to make is to define a clear habit of paying transactions after CC meetings. In this way we can be more efficient since we know that payments are every 2 weeks, and at the same time we make clear to those who have Funding Requests when they can expect payments. Secondly we have to define the time maximally needed to sign a transaction. I propose 48h with an aim of being better than this minimal requirement and drafting and signing most payments within 24 hours after a meeting.
dtavarez : I think the only disagreement I have is in regards to that I prefer 24 hours.
cekickafa : 48h is better than 24h.
👍 anynomous
anynomous : A third improvement which all CC members allready agreed on is that we will have another CC member hold the keys to the Grin CC wallet, so we can ensure this wallet is accessible all the time. I think 48 hours is more realistic for all cases although I expect that 9 out of 10 times we can make it work within 24 hours.
dtavarez : I would not expand the number of CC members, but I would invite gatekeepers to the CC github.
future3ooo : I’m going with 48 too. Seems more practical.
dtavarez : I would not expand the number of CC members, but I would invite gatekeepers to the CC github.
What about if someone wants to leave the CC?
dtavarez :
future3ooo :What about if someone wants to leave the CC?
a new CC member can be added like @mo5itoo was added same process.
anynomous : I agree with @dtavarez, in case someone wants to leave we can ask the community if they are ok with voting in a groundkeeper. One worry I still have about our improvements is who calculates and drafts transactions, it is quite time consuming, signing is manageable, but firs tracking, calculating and drafting transaction is quite a bit of work.
dtavarez : but I don't think any of the CC members want to leave, as far as I know.
cekickafa :
anynomous :One worry I still have about our improvements is who calculates and drafts transactions, it is quite time consuming, signing is manageable, but firs tracking, calculating and drafting transaction is quite a bit of work.
i can help about that as much as i can.
🙏🏻 future3ooo, anynomous.
future3ooo :
dtavarez : but I don't think any of the CC members want to leave, as far as I know.
I’m not so sure about this. That’s why I bought it up.
anynomous : If someone wants to leave, lets leave it those members themselves to announces it or not.
👍 dtavarez, future3ooo
Lets vote here and now on giving access to @cekickafa for Github. Should we also give @satoshocrat access to the Grin CC Github?
dtavarez : both I think.
👍 anynomous
anynomous : I think both would be best, in case @cekickafa gets ill or needs some time for something else.
future3ooo : I’m happy for both.
👍 dtavarez
anynomous : Probably we can limited it to one or two of the subdirectories, or all. Lets discuss it further in the CC chat and also ask @mcmmike opinion. I think he already made some sugestions.
cekickafa : i hope i dont get ill :)
anynomous : Stay healthy and Grinning ;)
💯cekickafa
cekickafa : All of us.
anynomous : 👍 Ok, that is decided allthough we need one more vote to make it final, but I assume we will get that vote.
On to our next topic:
dtavarez : regarding the Mining Project, someone or several people are needed to follow up on the farm, making sure that the g1's are running and the rewards are being withdrawn.
anynomous : My opinion has always been and will be, to make it as hands-off as possible. Let the guys from the mining facilities do the work for modes pay. We only transfer to the GrinCC wallet.
Also I think it is important to clarify that these miners are in fact "community miners". We bought them as community council, but the decision and responsibility is for the whole Grin community, similar to how this council is also just a representative body for the whole community. As such the council members should cut ourselves some slack and not always take the burden upon ourselves.
dtavarez : there are some technical issues that could be done to improve the security of the network that a more experienced person could accomplish; this would be a one-time thing.
anynomous : Ok. I would see this as optional. Only if and when time and motivation is available.
👍 dtavarez
We should also make sure that withdrawing is relatively easy and that at least two members can have the access, similar to the wallet. We could even make so that all members who have access to the Grin CC wallet, also have access to the mining pool account.
dtavarez : true. then we can open the debate in the forum and wait for someone to assume the responsibilities.
anynomous : Maybe you can explain later in the CC chat how difficult or easy withdrawing is.
future3ooo :
dtavarez : regarding the Mining Project, someone or several people are needed to follow up on the farm, making sure that the g1's are running and the rewards are being withdrawn.
What if one of the G1s goes down and requires someone at the facility to check it ? I assume there’s a direct contact that we need to reach out to ?
dtavarez : correct. all the contacts will be shared.
👍 anynomous, future3ooo
anynomous : Ok. Anything else that needs to be discussed or mention on this topic? If not we can discuss shortly how to manage the test miners. I guess we need access to that mining pool, just for monitoring?
cekickafa : i think from testnet explorer, you can monitor also.
👍 anynomous
anynomous : We can probably see the total hashrate of the testnet miners. So if we know all of those are the ones we pay for, I guess that is enough. Or if there is another constant test miner that we know of, we can still simply know what the total testnet hash/graph rate should be.
💯cekickafa
Ok, with that I think we discussed everything that was on the agenda. Is there anything we still need to discuss?
nicolasflamel1 : Following up on a pending topic from the last meeting. Did anyone hear from @renzokuken and/or walkbackgod about unlocking the Python CFFI secp256k1-zkp wrapper bounty? And did anyone hear from the Grin OC about unlocking the Ledger hardware wallet support bounty?
dtavarez : I'm in favor of unlocking the HW bounty.very in favor
👍 future3ooo, mably, nicolasflamel1, cekickafa, defistaker
anynomous : About the Ledger hardware wallet bounty. We did some checking and the bounty is actually put and managed by the OC. So it is up to them to decide what to do with that bounty. @phyro @yeastplume @quentinlesceller It would make sense to open up the bounty. But it is not for us to decide.
nicolasflamel1 : How about the Python wrapper bounty? Walkbackgod's last github commit and forum post regarding the Python wrapper were more than 2 months ago. As per the bounty's progress requirement, it should be unlocked now. Walkbackgod can re-apply for the bounty if they want to continue working on it.
cekickafa : i will contact again about it.
👍 nicolasflamel1
dtavarez :
nicolasflamel1 : How about the Python wrapper bounty? Walkbackgod's last github commit and forum post regarding the Python wrapper were more than 2 months ago. As per the bounty's progress requirement, it should be unlocked now. Walkbackgod can re-apply for the bounty if they want to continue working on it.
for that it would be nice to open a request on the forum and ask for feedback.
👍 nicolasflamel1
quentinlesceller : Sorry, maybe I don’t have all the elements but given the MWC ledger support. What should we do about the bounty ?
cekickafa : applied as MWC ?
anynomous : It was proposed to maybe open up the bounty again. Since @nicolasflamel1 build Ledger support for Grin, that would mean the bounty would become his.
dtavarez :
quentinlesceller : Sorry, maybe I don’t have all the elements but given the MWC ledger support. What should we do about the bounty ?
what would it the process to unlock the bounty?
quentinlesceller : Okay. I see, given the fact that the bounty is now locked for 1 year + that would make sense.
anynomous : Also it should be considered some work has been done on the Rust implementation by @mark_hollis. This makes it a bit more complex. But in general it makes sense to unlock the bounty.
dtavarez : the sad part is that there is no code from mark.and the code has to be open sourced. nicola's work is right there for everyone to use it.
👍 nicolasflamel1
anynomous : We indeed have no view of the current status or progress. In any case, I leave that to @quentinlesceller and the OC to decide.
👍 dtavarez, quentinlesceller, nicolasflamel1, cekickafa, defistaker, yesgrinyes
I think we have to add as TO DO for this meeting to contact @renzokuken and @Walkbackgod
👍 nicolasflamel1, cekickafa
cekickafa :Ok,noted.
anynomous :Is there anything else we need to discuss in this meeting?
cekickafa : That is all i think.
anynomous : In that case I would like to thank you all for your input today. Lets not forget our TO DO's for next meeting and also to do payments now .... 😉
😊 defistaker, nicolasflamel1
O, If @yeastplume is here. Just a short question, what is the status of the GUI wallet, can it already be played with or are the screenshots or mockups?
yeastplume : Sure, yes. Opening, closing and creating wallets and syncing the node. I'm working on creating transactions, but right at this moment I've stopped to rework the transaction list display. Progress is coming along nicely very much thanks to @lesserkey
🚀anonymous, nicolasflamel 🎉cekickafa 👍 dtavarez
anynomous : Great that you are working together on this. If mockups of the wallet are there, be sure to share them on the Forum. Looking forward to see and test the Grin GUI wallet.
👍 yeastplume, future3ooo
Ok. I am of now, thanks all. 👋
-
Give GrinCC- github access to groundskeeper for more management improvements.
-
Contact @walkbackgod and @renzokuken about Python wrapper bounty progress again.
-
Discuss and define the responsibilities about mining farm management process.
Meeting adjourned.