From 79ae1f5ef109a42d3e785ab9ff244ef830381d2b Mon Sep 17 00:00:00 2001
From: Guillermo Bescos
The Pyth DAO sets a maximum reward rate for stake pools, - currently set at 9%. This rate is achieved for a pool when the + currently set at 10%. This rate is achieved for a pool when the total stake is below the stake cap. If the stake cap is exceeded, the reward rate for stakers is reduced.
- Publishers charge a fixed percentage (5%) of the rewards from
+ Publishers charge a fixed percentage (20%) of the rewards from
stakers in their stake pool as a delegation fee (net of any
slashed amount). The Pyth DAO can vote to adjust this fee
structure. Learn more about staking rewards in the
From 272e4a32fe48dc9c26951b7f113a303cd3cda3a3 Mon Sep 17 00:00:00 2001
From: Guillermo Bescos
The Pyth DAO sets a maximum reward rate for stake pools, - currently set at 10%. This rate is achieved for a pool when the - total stake is below the stake cap. If the stake cap is + currently set at 10%. This rate is achieved for a pool when + the total stake is below the stake cap. If the stake cap is exceeded, the reward rate for stakers is reduced.
@@ -436,7 +436,7 @@ export const OracleIntegrityStakingGuide = ( penalized.
- The current slashing rate is capped at 10% of publisher and + The current slashing rate is capped at 5% of publisher and delegated stakes, and this rate can be adjusted by the Pyth DAO. The slashed amounts are sent to the DAO wallet. The Pyth DAO can choose to vote on future decisions for these slashed @@ -508,7 +508,7 @@ export const OracleIntegrityStakingGuide = ( answer: ( <>
- In the first phase of the Cooldown Period
+ In the first phase of the Cooldown Period{" "}
an on-chain protocol consuming Pyth data can choose to raise
a report for a plausible data misprint. The Pythian Council
of the Pyth DAO will then review the reference data provided
From 840b30a2ea36907d55d81ae8e51d6f227cb879ab Mon Sep 17 00:00:00 2001
From: Guillermo Bescos
- After this first phase, these tokens will undergo second + After this first phase, these tokens will undergo a second phase in the Cooldown Period lasting one full epoch, during - which the tokens are no longer subject to programmatic - rewards or slashing. Once this phase concludes, your tokens - will become unstaked and can be restaked or withdrawn to - your wallet. + which the tokens are no longer eligible to programmatic + rewards. These tokens are subject to slashing if a misprint + in the previous epoch is identified. Once this phase + concludes, your tokens will become unstaked and can be + restaked or withdrawn to your wallet.
> ), @@ -513,11 +514,15 @@ export const OracleIntegrityStakingGuide = ( answer: ( <>- In the first phase of the Cooldown Period{" "} - an on-chain protocol consuming Pyth data can choose to raise - a report for a plausible data misprint. The Pythian Council - of the Pyth DAO will then review the reference data provided - and compare against the Pyth data. + Anyone can choose to raise a report for a plausible data + misprint. The Pythian Council of the Pyth DAO will then + review the reference data provided and compare against the + Pyth data to determine whether a slashing event should + occur. The council will have until the end of the epoch + after the epoch of the reported incident to review the + report. The tokens subject to slashing are the tokens + eligible for rewards during the epoch of the misprint + incident.
In the unlikely event that a published aggregate has been
From 45f9b8ea714b62a6aaca8a641e4b1a5b29dd7a2a Mon Sep 17 00:00:00 2001
From: Guillermo Bescos
- Navigate to the Oracle Integrity Staking tab to begin staking your
- tokens to publishers to help secure Pyth Price Feeds.
+ Once you confirm your choice to stake to a publisher, your tokens
+ will first enter a Warmup Period, which lasts until the end of the
+ current epoch. An epoch is a one-week period starting every
+ Thursday at 00:00 UTC.
- Each publisher is assigned a stake pool that typically includes
- the publisher’s self-stake and delegated stakes from other
- participants. The rewards distribution protocol programmatically
- shares rewards first to publishers, and then to stakers supporting
- them.
-
- You can sort publishers by their stake pool details, quality
- ranking, and more. Once you have chosen a publisher, click Stake
- and specify the number of tokens you wish to stake to their pool.
+ Tokens in the Warmup Period do not contribute to oracle security
+ and are not eligible for sharing in publisher rewards or
+ penalties. Once the Warmup Period ends, these tokens become staked
+ and will play an active role in strengthening oracle integrity.
The Cooldown Period has two phases: from the time you click{" "}
Unstake until the end of the current epoch,
- followed by a full epoch. Tokens in the first phase are subject
- to rewards and slashing. Tokens in the second phase are not.
+ followed by a full epoch. Tokens in the first phase are eligible
+ for rewards. Tokens in both phases are subject to slashing if an
+ issue is identified in an epoch in which they were eligible for
+ rewards.
In the unlikely event that a published aggregate has been @@ -525,8 +525,8 @@ export const OracleIntegrityStakingGuide = ( triggered. The stakes of the subset of publishers who contributed to this incorrect aggregate are programmatically slashed, along with the stakes of anyone who delegated - tokens towards them. Such slashing event occurs during this - same epoch. + tokens towards them. Such slashing event occurs during the + epoch after the epoch of the reported incident.
The slashed amounts are sent to the Pyth DAO’s wallet. The