defistaker : Well, both of today's topic need input from CC members :)

phyro : should we start going through the agenda anyway or is this skipped because no one from CC is around?

jankie1800 : I can raise the questions and perhaps they can respond a bit later and I can add an edit if there are any decisions made

defistaker : Sure, go ahead please

jankie1800 : I think the plan was to point miners to a donation pool. I'm thinking to further transparency; maybe an income_log with where miners can account for energy use and be compensated for the cost of running the machine- Also I'm wondering how/if the delivery was processed to everyone housing the machines/ are situated accordingly. Really just checking in for an update.

dtavarez : ASIC miners are in one place right now; we are ready to deliver them starting this month. We tried to find a co-location place for at least the G1 but it has been an almost impossible task.

jankie1800 : thanks @dtavarez; I think we can revisit and work out how to build transparency as in process- I have access to low cost electricity + a mining friendly jurisdiction. Something I may consider moving forward if there continues to be an issue

dtavarez : We will have more news on this in the near future, in the meantime, we can proceed with the delivery of ASIC miners that were intended for distribution. Any other question before moving into the next topic?

defistaker : I think we can't officially hold a voting but can talk about the request. I think all the proposed items are needed including bug fixes. Any comments?

jankie1800 : Like @defistaker said I don't think we will reach a quorum regarding the vote, but this may serve as a placeholder for the decision and I will update as the council reaches their decision

• defistaker : Officially, only CC member's vote is counted, is it correct @dtavarez ?
• dtavarez : it looks like, yes

dtavarez : A small summary- @mcmmike me and @Mokhtar are running Grin++ public nodes; they helped to find things that need to be fixed asap- what I will do now is to focus mostly on the node code for the next months

cekickafa : Payment proof and one time slatepack adress? Does 2 include soft hard fork? sorry for not knowing- I think these 2 things are very important

• dtavarez : no, only new endpoints should be added to the grin++ api- new" for grin++

defistaker : According to grinnode.live stats, an important portion of running nodes are grin++

<p align="center"> <img width="460" height="300" src="https://u.teknik.io/OJzsx.png"> </p>

• dtavarez : the issues started since v1.2.6 after a rewriting almost code related to P2P; I now need to fix things that I am now aware of since I am receiving feedback from Community members
  • :+1: (defistaker)

jankie1800 : do you have any thoughts on the coming PIBD update and if it will affect your work?

• dtavarez : I'll work on PIBD after the things I added to my forum post

phyro : Is there going to be any work on payment proofs? I may have missed something on the forum, I did notice one-time addresses but maybe I missed these.

• dtavarez : only to add the same behavior like the Rust implementation
• phyro : oh I see :+1:

dtavarez : the thing is that I am receiving too many support request lately specially from gate.io users, I need to simplify my life and save some hours on support; also the same with tor too many: "I sent X amount to Gate.io, they are requesting proof" and the typical: "my address is orange", which is solved 99% of the time by using tor bridges. And address reuse is something we should not encourage but, since I am now receiving also feedback from people running public grin++ nodes, now my backlog increased and some issues should be addressed asap from the grin++ perspective

• defistaker : Security issues take priority :+1:
• cekickafa : too many: "I sent X amount to Gate.io, they are requesting proof" this torture is since 2019!

vegycslol : Is address reuse bad if u only reuse with the same user? I feel like it shouldn't be. I personally think address reuse is great when you're transacting with the same person. We should not follow btc's each tx new address since addresses on btc and on grin are completely different

• phyro : there are two different concepts really which we (mostly) bulk into one. Grin address is both the destination and the identity. An identity is like a phone number, the destination is the physical location at which you meet. You may want to hide the latter but keep the former intact to be able to call people any time you want. But that's probably a topic that's larger than this meeting
• dtavarez : but you don't want people using grinchck.uber.space to check confirm whether or not your wallet is running in terms of privacy

dtavarez : Special thanks to @Mokhtar and @Mike, again they are actively testing and running public nodes; I am also running some grin++ public nodes, I think it would be nice if more people deploy more public nodes

dtavarez : I wrote a python script to download and extract the node binary from the GrinPlusPlus repo; now it is easier to do it; but the node should work smoothly, so it is my priority to solve the problems encountered

jankie1800 : I appreciate your attention to detail for the end user experience. Instead of counting out those who are blocked or being frustrated by poor exchange experiences it seems like you are being creative and solving their problems through the wallet. I'm excited to see where you take things

• dtavarez : I'm just saving time on support 😂 some (a lot of) people DM me directly instead of using the telegram group, I hate it, but from time to time, I discover new things to help users achieve what they need while using grin++
• defistaker : Thanks for all the hardwork
  • 👆 (phyro, vegysclol) 👍 (cekickafa, dtavarez)

cekickafa : yes after Burkett, DTavarez official customer support is perfect. it is not easy to deal people just like me 😂 Burkett was dealing the same i mean. guy was so patient

• dtavarez : Talking directly to users helps Grin++ to be better

dtavarez : All topics were discussed, right?

• defistaker : Yes, we have discussed both topics
• cekickafa : well discussed.if you say so. I took my answers.thnx

dtavarez : If the CC woud like to proceed with the decision and update on the forum post @jankie1800 can add it to the meeting notes here to account on record. Can we finalize today's CC meeting then? @defistaker

• 👍 (jankie1800)

defistaker : Yes, I think we can close. Thanks all

Meeting adjourned