Oracle Integrity Staking gives PYTH holders a way to participate in the network's economic security and earn rewards proportional to the publishers they back. It's the answer to the question "what aligns publishers' incentives with truthful reporting?" If a publisher submits bad data, the stake delegated to them gets slashed.
How it works
- 01Holders stake PYTH against a specific publisher (not a generic pool).
- 02Each publisher has a cap on how much stake they can attract; this prevents one publisher from dominating the security budget.
- 03Publishers earn rewards by reporting accurate prices; stakers earn a share.
- 04If a publisher is found to have submitted manifestly bad data, their stake (and proportionally the delegated stake) is slashed.
Why this design
Earlier oracle designs either had no skin in the game (data was free to provide, free to lie about) or used pooled-stake models that couldn't attribute slashable events to specific reporters. OIS makes the attribution per-publisher, which is necessary for the slash signal to be meaningful.
OIS gets the most active governance discussion of any primitive: slashing parameters, publisher caps, reward rates all evolve via PIPs. Check the OIS forum section linked below for the current debate.