tfgrid/info_tfgrid
30
3
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Activity

Update collections/tfgrid3/governance/gep_comm_brainstorm.md

Browse Source
This commit is contained in:
mik-tf 2024-04-11 13:31:08 +00:00
parent b3eb91762f
commit 4afa2cf8e7
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
collections/tfgrid3/governance/gep_comm_brainstorm.md
View File

@ -36,7 +36,7 @@ In brief, the TF overview would be as follows:
15. Part of node additional fees goes to the TF Foundation for grant, R&D, etc.
16. Ensure a proper utilization/capacity ratio (perhaps per region/country? TBD)
17. Farmers should be able to use their tokens at all times for deployments, without having to wait any grace periods.
18. Develop a system for someone to make revenues out of developing on the grid. This can be done in many ways and should be discussed.
18. Develop a system for someone to make revenues out of developing/coding/promoting on the grid. This can be done in many ways and should be discussed.
## Proposition Details
@ -101,7 +101,7 @@ Here are the details of this proposition:
4. Example: New nodes under 33% of utilization per country can only farm POU, but not POC.
3. Farmers should be able to use their tokens at all times for deployments, without having to wait any grace periods.
1. E.g. a farmer purchase an IKON XL that generates approx. 650 TFT, from which they could use 400 TFT to setup a nice cloud environmont. This should always remain the option. No waiting, no locking, no grace period.
4. Develop a system for someone to make TFT revenues out of developing on the grid (providing solutions, dashboard, etc.)
4. Develop a system for someone to make TFT revenues out of developing/coding/promoting on the grid (providing solutions, dashboard, etc.)
1. E.g. find a way to have something along the lines of the previous solution provider system work.
2. E.g. the person hosting a grid stack could get a % of that dashboard instance's revenues to their wallet
3. Note: the current option to add an additional contract on top of the current one means unequal competition. So not ideal.