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:33:39 +00:00
parent 4afa2cf8e7
commit f99ce06d89
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

@ -25,7 +25,7 @@ In brief, the TF overview would be as follows:
4. Farming staking vault and farming collateral 4. Farming staking vault and farming collateral
5. Public staking vault (user staking) 5. Public staking vault (user staking)
6. DAO revenues (staking vault revenues) distributed to DAO voters 6. DAO revenues (staking vault revenues) distributed to DAO voters
7. Slashing events for nodes (with bountry programs for users) 7. Slashing events for nodes (with bounty programs for users)
8. Collateral info displayed on dashboard with alerts when nodes' collateral are being unstaked 8. Collateral info displayed on dashboard with alerts when nodes' collateral are being unstaked
9. Communication channels for TF, the users and the farmers 9. Communication channels for TF, the users and the farmers
10. System for farmers to announce maintenance window without loss of reputation or the like 10. System for farmers to announce maintenance window without loss of reputation or the like
@ -70,7 +70,7 @@ Here are the details of this proposition:
1. The farming collateral can be slashed if a workload is destroyed during utilization. 1. The farming collateral can be slashed if a workload is destroyed during utilization.
1. This has an added bonus of ensuring new nodes are serious about providing capacity and creating another utility for token. 1. This has an added bonus of ensuring new nodes are serious about providing capacity and creating another utility for token.
2. Bounty Hunting program for Slashing Events (bad nodes): 2. Bounty Hunting program for Slashing Events (bad nodes):
1. There is a slash event and a bountry reward to the user when a user finds a node that 1. There is a slash event and a bounty reward to the user when a user finds a node that
1. can’t accept a deployment 1. can’t accept a deployment
2. doesn't have a public ip when listed that they do 2. doesn't have a public ip when listed that they do
3. destroys the deployment during utilization 3. destroys the deployment during utilization