Addressing the risk of inaccurate Pyth data to increase the security of DeFi

Yes, exactly! Old school whitepaper ideas

I’m quoting here, but the ideas were along the lines of:

“Delegators stake tokens and earn data fees in exchange for potentially losing their stake if the oracle is inaccurate.”

" Data staking allows delegators to stake tokens to earn data fees. The delegators in aggregate also determine the level of influence that each publisher has on the aggregate price. In addition, this mechanism determines whether delegators’ stakes are slashed."

“Finally, the mechanism collects data fees from consumers and distributes a share to delegators. The remainder goes into a reward pool that is distributed to publishers.”

The context for the final passage about the data fees from consumers was in reference to a different idea than the (currently implemented) cross-chain fees generated by the Pyth pull oracle.

Nevertheless, there’s maybe a world where the data fees generated by Pyth (see the opBNB fees discussion) could go into such a “delegator mechanism” that makes the Pyth Price Feeds more robust.

The weightings of data providers for each price feed, for example, is one of those topics that’s long overdue, IMO

4 Likes