Skip to content

Commit 9a2c37d

Browse files
guibescosguibescos
authored
fix: update guide parameters (#1948)
* fix: update guide parameters * other params * consistency * update * go * fix typo * moar
1 parent b124f2e commit 9a2c37d

File tree

3 files changed

+43
-36
lines changed

3 files changed

+43
-36
lines changed

‎apps/staking/src/components/GeneralFaq/index.tsx

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ export const GeneralFaq = (
105105
{
106106
question: "Does participating in OIS affect my participation in PG?",
107107
answer:
108-
"No. The two programs are separate. Staking in OIS does not affect your participation in PG. For example, staking in OIs does not increase your voting power in PG. Staking to a publisher’s stake pool does not give that publisher additional voting power in PG.",
108+
"No. The two programs are separate. Staking in OIS does not affect your participation in PG. For example, staking in OIS does not increase your voting power in PG. Staking to a publisher’s stake pool does not give that publisher additional voting power in PG.",
109109
},
110110
{
111111
question: "Does slashing reduce voting weights?",
@@ -171,8 +171,10 @@ export const GeneralFaq = (
171171
<p>
172172
The Cooldown Period has two phases: from the time you click{" "}
173173
<strong>Unstake</strong> until the end of the current epoch,
174-
followed by a full epoch. Tokens in the first phase are subject
175-
to rewards and slashing. Tokens in the second phase are not.
174+
followed by a full epoch. Tokens in the first phase are eligible
175+
for rewards. Tokens in both phases are subject to slashing if an
176+
issue is identified in an epoch in which they were eligible for
177+
rewards.
176178
</p>
177179
</>
178180
),

‎apps/staking/src/components/GovernanceGuide/index.tsx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -351,15 +351,15 @@ export const GovernanceGuide = (
351351
<Link
352352
className="underline"
353353
target="_blank"
354-
href="https://forum.pyth.network/t/about-the-pyth-dao/14"
354+
href="https://ipfs.io/ipfs/QmP2GmL1n2WbHd7AtHqyXVWFyyHH36aZLfVZbNoqhommJi"
355355
>
356356
Pyth DAO LLC Operating Agreement
357357
</Link>{" "}
358358
and applicable laws. Learn more about PIPs in the{" "}
359359
<Link
360360
className="underline"
361361
target="_blank"
362-
href="https://forum.pyth.network/t/about-the-pyth-dao/14"
362+
href="https://github.com/pyth-network/governance/blob/main/docs/constitution/pyth-dao-constitution.md"
363363
>
364364
Pyth DAO Constitution
365365
</Link>

‎apps/staking/src/components/OracleIntegrityStakingGuide/index.tsx

Lines changed: 36 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -126,6 +126,11 @@ export const OracleIntegrityStakingGuide = (
126126
faq: {
127127
title: "Adding Tokens FAQ",
128128
questions: [
129+
{
130+
question: "Why do I need to add my tokens?",
131+
answer:
132+
"Adding tokens to the Pyth Staking Dashboard transfers them to your SPL wallet’s staking account. Your tokens will remain under your control on-chain through the Pyth Staking Dashboard.",
133+
},
129134
{
130135
question: "Where are my added tokens stored?",
131136
answer:
@@ -233,22 +238,17 @@ export const OracleIntegrityStakingGuide = (
233238
description: (
234239
<>
235240
<p>
236-
Navigate to the Oracle Integrity Staking tab to begin staking your
237-
tokens to publishers to help secure Pyth Price Feeds.
238-
</p>
239-
240-
<p>
241-
Each publisher is assigned a stake pool that typically includes
242-
the publisher’s self-stake and delegated stakes from other
243-
participants. The rewards distribution protocol programmatically
244-
shares rewards first to publishers, and then to stakers supporting
245-
them.
241+
Once you confirm your choice to stake to a publisher, your tokens
242+
will first enter a Warmup Period, which lasts until the end of the
243+
current epoch. An epoch is a one-week period starting every
244+
Thursday at 00:00 UTC.
246245
</p>
247246

248247
<p>
249-
You can sort publishers by their stake pool details, quality
250-
ranking, and more. Once you have chosen a publisher, click Stake
251-
and specify the number of tokens you wish to stake to their pool.
248+
Tokens in the Warmup Period do not contribute to oracle security
249+
and are not eligible for sharing in publisher rewards or
250+
penalties. Once the Warmup Period ends, these tokens become staked
251+
and will play an active role in strengthening oracle integrity.
252252
</p>
253253
</>
254254
),
@@ -409,12 +409,12 @@ export const OracleIntegrityStakingGuide = (
409409
</p>
410410
<p>
411411
The Pyth DAO sets a maximum reward rate for stake pools,
412-
currently set at 9%. This rate is achieved for a pool when the
413-
total stake is below the stake cap. If the stake cap is
412+
currently set at 10%. This rate is achieved for a pool when
413+
the total stake is below the stake cap. If the stake cap is
414414
exceeded, the reward rate for stakers is reduced.
415415
</p>
416416
<p>
417-
Publishers charge a fixed percentage (5%) of the rewards from
417+
Publishers charge a fixed percentage (20%) of the rewards from
418418
stakers in their stake pool as a delegation fee (net of any
419419
slashed amount). The Pyth DAO can vote to adjust this fee
420420
structure. Learn more about staking rewards in the
@@ -436,7 +436,7 @@ export const OracleIntegrityStakingGuide = (
436436
penalized.
437437
</p>
438438
<p>
439-
The current slashing rate is capped at 10% of publisher and
439+
The current slashing rate is capped at 5% of publisher and
440440
delegated stakes, and this rate can be adjusted by the Pyth
441441
DAO. The slashed amounts are sent to the DAO wallet. The Pyth
442442
DAO can choose to vote on future decisions for these slashed
@@ -483,16 +483,17 @@ export const OracleIntegrityStakingGuide = (
483483
tokens will first undergo a first phase of the Cooldown
484484
Period from the time of clicking Unstake to the end of the
485485
current epoch. These tokens still actively contribute to
486-
oracle integrity and remain subject to programmatic rewards
487-
and slashing.
486+
oracle integrity and remain eligible to programmatic
487+
rewards.
488488
</p>
489489
<p>
490-
After this first phase, these tokens will undergo second
490+
After this first phase, these tokens will undergo a second
491491
phase in the Cooldown Period lasting one full epoch, during
492-
which the tokens are no longer subject to programmatic
493-
rewards or slashing. Once this phase concludes, your tokens
494-
will become unstaked and can be restaked or withdrawn to
495-
your wallet.
492+
which the tokens are no longer eligible to programmatic
493+
rewards. These tokens are subject to slashing if a misprint
494+
in the previous epoch is identified. Once this phase
495+
concludes, your tokens will become unstaked and can be
496+
restaked or withdrawn to your wallet.
496497
</p>
497498
</>
498499
),
@@ -508,20 +509,24 @@ export const OracleIntegrityStakingGuide = (
508509
answer: (
509510
<>
510511
<p>
511-
In the first phase of the <strong>Cooldown Period</strong>
512-
an on-chain protocol consuming Pyth data can choose to raise
513-
a report for a plausible data misprint. The Pythian Council
514-
of the Pyth DAO will then review the reference data provided
515-
and compare against the Pyth data.
512+
Anyone can choose to raise a report for a plausible data
513+
misprint. The Pythian Council of the Pyth DAO will then
514+
review the reference data provided and compare against the
515+
Pyth data to determine whether a slashing event should
516+
occur. The council will have until the end of the epoch
517+
after the epoch of the reported incident to review the
518+
report. The tokens subject to slashing are the tokens
519+
eligible for rewards{" "}
520+
<i>during the epoch of the misprint incident</i>.
516521
</p>
517522
<p>
518523
In the unlikely event that a published aggregate has been
519524
found to be erroneous, a slashing event would then be
520525
triggered. The stakes of the subset of publishers who
521526
contributed to this incorrect aggregate are programmatically
522527
slashed, along with the stakes of anyone who delegated
523-
tokens towards them. Such slashing event occurs during this
524-
same epoch.
528+
tokens towards them. Such slashing event occurs during the
529+
epoch after the epoch of the reported incident.
525530
</p>
526531
<p>
527532
The slashed amounts are sent to the Pyth DAO’s wallet. The

0 commit comments

Comments
 (0)