OIS Docs #420
Merged
OIS Docs #420
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Co-authored-by: guibescos <59208140+guibescos@users.noreply.github.com>
guibescos
reviewed
Sep 20, 2024
guibescos
reviewed
Sep 20, 2024
guibescos
reviewed
Sep 20, 2024
| The **pool cap** is calculated as follows: | ||
|
|
||
| $$ | ||
| \large{\text{Pool Cap}: {\bold{C_p}} = M \cdot \sum_{s \in \text{Symbols\_p}} \frac{1}{\max(n_s, Z)}} |
There was a problem hiding this comment.
I should make every symbol bold
guibescos
reviewed
Sep 20, 2024
pages/home/oracle-integrity-staking/mathematical-representation.mdx
Outdated
Show resolved
Hide resolved
guibescos
reviewed
Sep 20, 2024
pages/home/oracle-integrity-staking/mathematical-representation.mdx
Outdated
Show resolved
Hide resolved
guibescos
reviewed
Sep 20, 2024
pages/home/oracle-integrity-staking/publisher-quality-ranking.mdx
Outdated
Show resolved
Hide resolved
guibescos
reviewed
Sep 20, 2024
guibescos
reviewed
Sep 20, 2024
|
|
||
| - Prevalent prices for the asset(s) in question and related crosses using the most liquid venues at the time of the incident were at least 250 bps away from the price produced by Pyth | ||
| - The price deviation have lasted for at least 60 seconds | ||
| - Confidence Intervals prints from Pyth do not show an abnormal deviation during the misprint |
guibescos
reviewed
Sep 20, 2024
| - 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) | ||
| - In the case the total amount staked by the stakers responsible for the data quality issue is nil, no slashing takes place | ||
| - **Loss of Rewards** | ||
| - the stakers that may be responsible for the data quality issue forfeit any rewards the epoch following the slashing event |
guibescos
reviewed
Sep 20, 2024
| - **Loss of Rewards** | ||
| - the stakers that may be responsible for the data quality issue forfeit any rewards the epoch following the slashing event | ||
| - **Temporary or Permanent Removal:** | ||
| - 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 |
There was a problem hiding this comment.
you can't get excluded from the stakers but yes from the publishers and your associated pool will have a soft cap of 0, so you'll be getting 0 rewards
There was a problem hiding this comment.
this is for the PFC to exclude them as a publisher all together.
…n.mdx Co-authored-by: guibescos <59208140+guibescos@users.noreply.github.com>
YaserJazouane
approved these changes
Sep 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.