diff --git a/apps/staking/src/components/PublisherFaq/index.tsx b/apps/staking/src/components/PublisherFaq/index.tsx index ea6fc2aacf..8d0c4ce411 100644 --- a/apps/staking/src/components/PublisherFaq/index.tsx +++ b/apps/staking/src/components/PublisherFaq/index.tsx @@ -20,7 +20,7 @@ export const PublisherFaq = ( For a comprehensive walkthrough of the OIS program, publishers can refer to the{" "} @@ -72,8 +72,9 @@ export const PublisherFaq = ( <>

Publishers that have locked tokens are{" "} - automatically opted-in with their existing - stake account with the most funds as their main stake account. + automatically opted-in with their main stake + account, which is the stake account in which they last received + locked tokens.

Publishers that have never received locked tokens will be @@ -83,7 +84,7 @@ export const PublisherFaq = (

If you wish to opt out of rewards, please follow the{" "} @@ -108,7 +109,7 @@ export const PublisherFaq = (

Please follow the{" "} @@ -131,12 +132,16 @@ export const PublisherFaq = ( answer: ( <>

- Yes. Opting in makes you subject to OIS’ decentralized staking - rewards and slashing mechanisms. Programmatic rewards for - staking for publishers are determined by a number of stake pool - parameters. Programmatic slashing is capped at a 5% percentage - amount of the total stake within a publisher’s stake pool. The - Pyth DAO can vote to adjust these parameters. + Opting-in makes you subject to staking rewards from delegate + stakers but does not make you subject to slashing unless you + stake to your own stake pool. +

+

+ Programmatic rewards for staking for publishers are determined + by a number of stake pool parameters. Programmatic slashing is + capped at a 5% percentage amount of the total stake within a + publisher’s stake pool. The Pyth DAO can vote to adjust these + parameters.

Please refer to the{" "} @@ -176,7 +181,7 @@ export const PublisherFaq = ( It is important to understand the requirements, responsibilities, and implications of participating in OIS. The{" "} @@ -311,7 +316,7 @@ export const PublisherFaq = (

Please refer to the{" "} @@ -336,7 +341,7 @@ export const PublisherFaq = (

Please refer to the{" "} @@ -369,7 +374,7 @@ export const PublisherFaq = (

Please refer to the{" "} @@ -387,7 +392,7 @@ export const PublisherFaq = (

Please refer to the{" "} @@ -492,15 +497,29 @@ export const PublisherFaq = ( answer: ( <>

- An on-chain protocol can report a potential data error for the - previous epoch. If a report is raised, the Pythian Council - reviews it by comparing it with the reference data. If a - discrepancy is confirmed, a slashing event is triggered. + 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. +

+

+ If a discrepancy is confirmed, a slashing event is triggered. In + this event, the stakes of publishers who contributed to the + incorrect aggregate will be programmatically slashed, along with + the stakes of anyone who delegated tokens towards their stake + pools. +

+

+ 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.

During the same epoch, the stakes of the subset of publishers involved in the error and their stakers are slashed. Slashed - amounts are sent to the DAO wallet for future decisions. + amounts are sent to the DAO wallet. The Pyth DAO can choose to + vote on future decisions for these slashed amounts.

Please refer to the{" "}