124 lines
3.5 KiB
Markdown
124 lines
3.5 KiB
Markdown
<h1>Engineering Circle Meeting 2024-10-21 </h1>
|
|
|
|
<h2>Table of Contents</h2>
|
|
|
|
- [Attendees](#attendees)
|
|
- [TODISCUSS](#todiscuss)
|
|
|
|
---
|
|
|
|
## Attendees
|
|
|
|
- Lee
|
|
- Scott
|
|
- Sabrina
|
|
- Mik
|
|
|
|
## TODISCUSS
|
|
|
|
- GEP procedures update
|
|
- https://git.ourworld.tf/tfgrid/circle_promotion/issues/295
|
|
- Stay with v3 as is
|
|
- Go with token-based for v4
|
|
- this can be discussed later
|
|
- Fix dead nodes
|
|
- filter out nodes that didn't have uptime in a given period
|
|
- no longer plan to do minting on chain
|
|
- storage and mapping of integer
|
|
- technically feasible
|
|
- not a problem for the chain
|
|
- storage aspect
|
|
- for every node we store large amount of data
|
|
- computational complexities
|
|
- single write operation
|
|
- fine right now
|
|
- todo
|
|
- list of changes for future updates
|
|
- don't make a GEP for this
|
|
- issue on security report issue
|
|
- some discussions
|
|
- potential solutions
|
|
- Scott will reply to security repo issue and propose the changes as defined by Lee
|
|
- then we implement
|
|
- 3.16
|
|
- GEP voting process feedback
|
|
- https://git.ourworld.tf/tfgrid/circle_promotion/issues/294#issuecomment-8784
|
|
- Don't go with pre-gep period
|
|
- We announce a GEP
|
|
- We invite community members to ask questions if they don't understand something
|
|
- TODO
|
|
- internally
|
|
- when we discuss GEP, we can do it on the forum
|
|
- Comms side
|
|
- say the vote didn't pass and we keep this voting process for v3
|
|
- Allowed list
|
|
- Tech aspect, check blocking issues+progress
|
|
- Lee
|
|
- Status?
|
|
- High-level aspect
|
|
- Thabet
|
|
- Status?
|
|
- one to proceed
|
|
- internal securtiy of the node
|
|
- doesn't need voting
|
|
- one to be voted on
|
|
- allowed-list
|
|
- tell farmers we will force your node to not be able to reach certain domains and IPs
|
|
- GEP todo
|
|
- vote for this change in GEP
|
|
- let farmers decide if they want to allow or not
|
|
- default behaviour: locked on everyone
|
|
- can opt-in, opt-out
|
|
- TODO
|
|
- add the feature then make the vote
|
|
- What we need
|
|
- feedback from Kristof and Jan
|
|
- Thabet has everything ready
|
|
- assigned to Erwan
|
|
- Sabrina will check with Kristof and Jan
|
|
- QSFS + zdb testing
|
|
- Scott
|
|
- Status
|
|
- This week will work on it
|
|
- TODO
|
|
- need alert system to users if system goes down
|
|
- Multi-sign wallet
|
|
- Kristof
|
|
- Status
|
|
- Pretty much done
|
|
- Sabrina will check and have more info
|
|
- Compensating Farmers
|
|
- Sabrina
|
|
- Status?
|
|
- Mycelium GUI
|
|
- Windows SSH issue
|
|
- Lee
|
|
- Status
|
|
- still waiting on reply from QA
|
|
- Thabet can ping QA to make this go forward
|
|
- Farmerbot
|
|
- discuss when thabet is here
|
|
- 3.15 release in relation with the Farmerbot
|
|
- will there be a mandatory update
|
|
- e.g. previous version stops working
|
|
- if it's the case, we need to tell farmers
|
|
- steps what they need to do
|
|
- e.g. process (not official, to be determined)
|
|
- stop farmerbot
|
|
- wake up all nodes
|
|
- update the farmerbot
|
|
- we'd need to plan ahead for that
|
|
- fbot will require an update
|
|
- let farmers know there will need to be an update
|
|
- procedures?
|
|
- e.g.
|
|
- wake all their nodes
|
|
- stop the bot
|
|
- migrate to new bot
|
|
- continue using it from there
|
|
- or any other way?
|
|
- TODO
|
|
- once we know the 3.15 release date
|
|
- tell farmers the procedures
|
|
- KYC part
|
|
- Thabet working on this actively |