Slashing events for nodes (with bounty programs for users) #7

Open
opened 2024-05-22 13:45:55 +00:00 by mik-tf · 0 comments
Owner

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 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
      4. Etc. (Todo: build list of slashable events)

References

Part of the community brainstorm to improve the 3.0 decentralized grid.

https://threefold.info/tfgrid3/tfgrid3/gep_comm_brainstorm.html

Notes

Previously here: tfgrid/circle_engineering#44

# 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 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 4. Etc. (Todo: build list of slashable events) # References Part of the community brainstorm to improve the 3.0 decentralized grid. https://threefold.info/tfgrid3/tfgrid3/gep_comm_brainstorm.html # Notes Previously here: https://git.ourworld.tf/tfgrid/circle_engineering/issues/44
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 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_feedback#7
No description provided.