Engineering Circle Meeting 2024-09-16

<h1>Engineering Circle Meeting 2024-09-16 </h1>

<h2>Table of Contents</h2>

- [Attendees](#attendees)
- [Main Content](#main-content)
- [TODO - Next Meeting](#todo---next-meeting)
- [TODISCUSS - Next Meeting](#todiscuss---next-meeting)

---

## Attendees

- Lee
- Mik
- Sabrina
- Scott
- Thabet

## Main Content

- GEP Voting Process
  - Cool down period
    - Consensus
      - we don't include it in GEP for now
      - we make a GEP for cool down later if we think it's needed.
  - Final version of GEP
    - consensus
      - https://docs.google.com/document/d/1Ovi2ecDI2G75CecLr2tKs7W5a69Ntxo-9F-qaVW7kFI/edit#heading=h.kyru52g80m08
  - What is next
    - comms circle will publish GEP and let 1 week for the community to ask questions
    - Next week (23rd of September), we will sart the GEP on the dashboard and have a 10 days period
- Voting Procedures
  - when there's a GEP
    - we have a meeting with stakeholders
      - we decide the voting, e.g. yes or no
    - we make sure the foundation votes for the GEP
- hetnzer work
  - going well
- QSFS
  - Lee is working on some issues
    - Scott will respond to them
    - Also working on a pulumi version
- GITEA Access: we fixed the issue of spammers
  - https://github.com/threefoldtech/tf_operations/issues/2752
  - summary
    - now we set registration email verification
      - shouldn't have any more spam
      - if it's the case
        - step 1. set captcha
        - step 2. set manual email (verified by admins)

## TODO - Next Meeting

- Ops snapshot node
  - TODO: Sabrina will check with Bert post 19 sept.
  - Reference: https://github.com/threefoldtech/tfchain/issues/981
- GEP
  - start GEP on dashboard 23rd of September, for 10 days period
- git.ourworld.tf ops
  - issue to check how to manage the gitea instance, just like we deal with github instance
    - Sabrina is taking care of this

## TODISCUSS - Next Meeting

- Things to discuss
  - Jimber situation
    - discuss with Kristof
  - push the 0S4
    - how far we are with the network
    - make a list of everything which is blocking
  - Farmerbot-farmer-minting issue
    - scott will present the issue and we can discuss with Thabet, Jan and Kristof on the call: we can't afford to lose farmers, and the error was on TF side, not the farmers.
    - for now the proposition is (not ideal for farmers, we risk to lose farmers and nodes)
      - make sure it doesn't happen again
        - check with the team who implemented the changes
          - ZOS team
      - can't compensate from treasury
      - can't remint
        - not fair for non-fbot-farmer compared to fbot-farmer
  - Farmers deploying on their own nodes
    - for now they can get up to 90% discount
      - 50% utilization rewards
      - 50% dedicated node
      - 60% staking discount
        - 0.5 * 0.5 * 0.4 = 0.1
    - If TFT price goes up, farmers can rent their full node and still farm TFT
      - not sustainable
        - starting from 2 cents tft
          - farmers can make more money by renting the whole node and still farm
    - Discussion
      - how can we make sure this isn't happening for ZOS v4
      - we'd need a GEP to change the discount and rewards
  - info_grid manual (github) to info_tfgrid manual (git.ourworld.tf) migration
    - discuss how to do this smoothly
      - e.g. 
        - replace info_grid manual by info_tfgrid manual on manual.grid.tf
    - OR we wait for the new markdown docs app?