FARMING IMPROVEMENT 3.15 (GEP + TECH) #14

Open
opened 2024-03-13 15:57:29 +00:00 by despiegk · 3 comments
Owner

FARMERS

  • uptime checks include network, min BW, quality of HW ...
  • see info about mem, cpu, ...
  • remark: all farmers have done KYC, see #12
  • for new nodes: we do no register nodes which are not DDR4...
  • bigger farmers they can sign with DMCC for SLA, which will be visible, with penalty
  • lockup of TFT for 2 years unless utilization +30% (as was mentioned before, this will go from 1 billion) = communication & gep (????)

GEP

  • stop burning
  • give 50% on utilization (this might change in 4.x)
  • min uptime...
  • if price > 0.08 for more than X time, then the farming price changes ...
  • ...
## FARMERS - uptime checks include network, min BW, quality of HW ... - see info about mem, cpu, ... - remark: all farmers have done KYC, see #12 - for new nodes: we do no register nodes which are not DDR4... - bigger farmers they can sign with DMCC for SLA, which will be visible, with penalty - lockup of TFT for 2 years unless utilization +30% (as was mentioned before, this will go from 1 billion) = communication & gep (????) ## GEP - stop burning - give 50% on utilization (this might change in 4.x) - min uptime... - if price > 0.08 for more than X time, then the farming price changes ... - ...
despiegk added the
Urgent
label 2024-03-13 15:57:29 +00:00
despiegk added this to the (deleted) project 2024-03-13 15:57:29 +00:00
despiegk added the
Story
label 2024-03-21 07:44:54 +00:00
Author
Owner

@mik-tf @sabrinasadik

to check

  • which GEP's were approved, is there already a 1 BIllion approved?
  • please give overview
@mik-tf @sabrinasadik to check - which GEP's were approved, is there already a 1 BIllion approved? - please give overview
mik-tf was assigned by despiegk 2024-04-23 11:48:17 +00:00
sabrinasadik was assigned by despiegk 2024-04-23 11:48:22 +00:00
Owner

Approved:

Proposal Summary

95% and 98% uptime requirement for DIY and certified nodes respectively
50% of proof-of-utilization revenues will go to the farmer running the 3Node
Minting will be slashed for 1 month if the node cannot wake up within 30-minutes twice within the same minting period
When we reach 1 Billion TFT on Stellar, minting stops on Stellar
TFT burning will stop

Proposal Details

We provide the basic updates to the TFGrid.

Uptime Requirements

DIY Nodes: 95% uptime per month
Certified Nodes: 98% uptime per month

Proof-of-Utilization Revenues

50% of the proof-of-utilization revenues from grid use will go to the farmer running the 3Node being used
Notes
The farmers receive 50% of the utilization of the grid. TF Engineers are investigating how to implement this best, it’s not certain that this will happen on TFChain maybe it will be a combination of a new API gateway running with the cooperative as well as TFChain launched workloads.

The remaining 50% will be distributed as follows: 40% will go to TF cooperative (TF DMCC for now) and 10% to the stakers on the validators.

30-Minute Wake-up Minting rule

Minting will be slashed for 1 month if the node cannot wake up within 30-minutes twice within the same minting period.
Notes
The idea is to give a pass for low probability events (like brief power/network outages for the farmer, TFHub going down), while still ensuring that nodes with chronic issues can’t continue using Farmerbot to mint. It also gives the farmer an opportunity to correct any issues that come up in their infrastructure without an immediate loss of earnings.

TFT Minting Cap

When we reach 1 Billion TFT on Stellar, minting stops on Stellar
TFT Burning Stops
We will stop burning TFT

Approved: ## Proposal Summary 95% and 98% uptime requirement for DIY and certified nodes respectively 50% of proof-of-utilization revenues will go to the farmer running the 3Node Minting will be slashed for 1 month if the node cannot wake up within 30-minutes twice within the same minting period When we reach 1 Billion TFT on Stellar, minting stops on Stellar TFT burning will stop ## Proposal Details We provide the basic updates to the TFGrid. ### Uptime Requirements DIY Nodes: 95% uptime per month Certified Nodes: 98% uptime per month ### Proof-of-Utilization Revenues 50% of the proof-of-utilization revenues from grid use will go to the farmer running the 3Node being used **Notes** The farmers receive 50% of the utilization of the grid. TF Engineers are investigating how to implement this best, it’s not certain that this will happen on TFChain maybe it will be a combination of a new API gateway running with the cooperative as well as TFChain launched workloads. The remaining 50% will be distributed as follows: 40% will go to TF cooperative (TF DMCC for now) and 10% to the stakers on the validators. ### 30-Minute Wake-up Minting rule Minting will be slashed for 1 month if the node cannot wake up within 30-minutes twice within the same minting period. **Notes** The idea is to give a pass for low probability events (like brief power/network outages for the farmer, TFHub going down), while still ensuring that nodes with chronic issues can’t continue using Farmerbot to mint. It also gives the farmer an opportunity to correct any issues that come up in their infrastructure without an immediate loss of earnings. ### TFT Minting Cap When we reach 1 Billion TFT on Stellar, minting stops on Stellar TFT Burning Stops We will stop burning TFT
despiegk modified the project from (deleted) to tfgrid_3_14 2024-05-22 07:56:24 +00:00
despiegk modified the project from tfgrid_3_14 to tfgrid_3_16 2024-06-02 05:35:29 +00:00
Author
Owner

need new story for this, more clear, what do we want to do, do we have input from community, do they agree

I moved it to 3.15

need new story for this, more clear, what do we want to do, do we have input from community, do they agree I moved it to 3.15
despiegk removed the
Urgent
label 2024-07-03 12:55:16 +00:00
despiegk changed title from FARMING IMPROVEMENT (GEP + TECH) to FARMING IMPROVEMENT 3.15 (GEP + TECH) 2024-07-03 12:55:23 +00:00
despiegk removed the
Story
label 2024-07-28 07:57:25 +00:00
Sign in to join this conversation.
No Milestone
No project
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: tfgrid/circle_engineering#14
No description provided.