Issues
- The policy around Validator slashingRIP-7
- Is there a limit to how much the Phlogiston exchange rate can be changed in each block?RIP-6
- What is the initial exchange rate for Phlogiston / RevRIP-5
- Validators / count of blocksRIP-4
- Staked token / count of blocksRIP-3
- The rate by which Validators can unbondRIP-2
- Specify the unit by which Validators may unbondRIP-1
7 of 7
The policy around Validator slashing
Description
Details
Assignee
UnassignedUnassignedReporter
Medha ParlikarMedha ParlikarPriority
Medium
Details
Details
Assignee
Unassigned
UnassignedReporter
Medha Parlikar
Medha Parlikar
Priority
MediumCreated October 9, 2018 at 10:21 PM
Updated October 9, 2018 at 10:57 PM
Activity
Show:
Strategic Category: Growth & Reduce Risk: 8, 8
Background:
The RChain software is new and under active development. In the event a software bug in the RChain software causes a validator to be slashed, it's reasonable that some recompense be available to the validator.
Proposed Process:
The Validator submits logs to a bug report including evidence of the slash, core issue. Validator has to also provide evidence that they are running CoOp node software. If upon investigation, the outcome is that the issue is a software defect, the slashed amounts are refunded to the validator.
Slashed bond is routed to a CoOperative address, and an out of protocol process for vetting the slash for bugs is in place.