Skip to content

Commit d4dd31d

Browse files
committed
minor changes
1 parent 34908e8 commit d4dd31d

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

pages/home/oracle-integrity-staking/slashing-rulebook.mdx

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ The Pyth Network is designed to provide reliable and trustworthy financial data
3030

3131
Staking through OIS is a program to enhance the security of price feeds produced by publisher on the Pyth Network.
3232

33-
Per the design of OIS, a pool aligned with a data publisher accepts stake from the moment such publisher declares its stake account through configuration. The additional stake allows such publisher to earn a delegation fee to contribute to the costs of providing data to the Pyth Network. Data publishers compete with one another to increase the number of price feeds they contribute to, and/or increase the quality of data that allows them to be selected to publish and/or enable higher staking cap for the pool each publisher is aligned to.
33+
Per the design of OIS, a pool aligned with a data publisher accepts stake from the publisher itself and from delegators. The additional stake allows such publisher to earn a delegation fee to contribute to the costs of providing data to the Pyth Network. Data publishers compete with one another to increase the number of price feeds they contribute to, and/or increase the quality of data that allows them to be selected to publish and/or enable higher staking cap for the pool each publisher is aligned to.
3434

3535
## Slashing
3636

@@ -52,8 +52,6 @@ If slashing event confirmed, the Pythian Council will process calculation and di
5252
- **Stake Slashed**
5353
- capped at 5% of the total amount staked (including the amount delegated) into pools associated with publishers identified as directly responsible for poor data quality. distribution of the slashed amount is uniform amongst publishers and delegator(s)
5454
- In the case the total amount staked by the stakers responsible for the data quality issue is nil, no slashing takes place
55-
- **Loss of Rewards**
56-
- the stakers that may be responsible for the data quality issue forfeit any rewards the epoch following the slashing event
5755
- **Temporary or Permanent Removal:**
5856
- Stakers responsible for more than 4 slashing events per calendar year may be excluded permanently from the network exclusion from the set of stakers and/or publishers
5957

0 commit comments

Comments
 (0)