[PASSED] OP-PIP 86: Set stake account for a Market Data Provider

Proposals
1

Abstract

This proposal aims to assign stake account 8BYLDKDhAzbf6kB46Jkj86nvKBts2FUCBmPxTv63bRN6 to Market Data Provider (MDP) 5pqDy8FdBBLUVKSs6xoxXmrBvgRfhNVe1wB3vyLFTVeM in the context of Oracle Integrity Staking (OIS).

Rationale

When OIS launched in September 2024, most MDPs were assigned existing stake accounts for the purposes of self-staking i.e. staking their tokens in their own assigned pool. These MDPs can freely rotate their assigned stake account by signing a transaction with the owner of their currently assigned stake account (the reassigment authority).

However, one of Pyth’s MDPs has chosen to rotate their publisher key. New publisher keys require the Pythian Council to assign them a stake account, since they start without stake account and thus no reassignment authority. After the Pythian Council assigns this initial stake account, only the reassignment authority can replace it by another stake account.

Description

This proposal calls the set_publisher_stake_account instruction from the integrity pool program to assign stake account 8BYLDKDhAzbf6kB46Jkj86nvKBts2FUCBmPxTv63bRN6 to publisher key 5pqDy8FdBBLUVKSs6xoxXmrBvgRfhNVe1wB3vyLFTVeM.

Implementation Plan

  1. Check the publisher field is 5pqDy8FdBBLUVKSs6xoxXmrBvgRfhNVe1wB3vyLFTVeM

  2. Check the newStakeAccountPositionsOption field is 8BYLDKDhAzbf6kB46Jkj86nvKBts2FUCBmPxTv63bRN6

1 Like