From f99ce06d8933a0434ef9956b0434bbfa20475043 Mon Sep 17 00:00:00 2001 From: mik-tf Date: Thu, 11 Apr 2024 13:33:39 +0000 Subject: [PATCH] Update collections/tfgrid3/governance/gep_comm_brainstorm.md --- collections/tfgrid3/governance/gep_comm_brainstorm.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/collections/tfgrid3/governance/gep_comm_brainstorm.md b/collections/tfgrid3/governance/gep_comm_brainstorm.md index b7fd0aa..2a7f548 100644 --- a/collections/tfgrid3/governance/gep_comm_brainstorm.md +++ b/collections/tfgrid3/governance/gep_comm_brainstorm.md @@ -25,7 +25,7 @@ In brief, the TF overview would be as follows: 4. Farming staking vault and farming collateral 5. Public staking vault (user staking) 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 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 @@ -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. 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): - 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 2. doesn't have a public ip when listed that they do 3. destroys the deployment during utilization