[ONGOING] OP-PIP-125: Cross-Chain Fee Repatriation Framework

Abstract


Establish the operational framework for, and empower, the Pythian Council to repatriate DAO-owned fees from non-Solana chains, as mandated by OP-PIP-87 Section 3.

This proposal formalizes the community discussion at Operationalizing Cross-Chain Fee Repatriation.

PROPOSAL: OP-PIP-125: Cross-Chain Fee Repatriation Framework | Pyth Governance

Proposal


1. PC Multisigs on EVM Chains

Deploy Safe (Gnosis) multisigs on chains requiring fee retrieval.

  • Threshold: 5/8 (mirrors Pythian Council on Solana minus Ops wallet)
  • Chains without Safe support deferred until infrastructure available
  • Contract upgrades via OP-PIP redirect accumulated fees to these multisigs

2. Withdrawal Triggers

| Trigger         | Condition                                 |
| --------------- | ----------------------------------------- |
| Chain Risk      | Chain sunset, instability, or deprecation |
| Minimum Balance | β‰₯$2,000 accumulated                       |

3. Bridging & Swaps

  • USDC/USDT only: native tokens swapped to stablecoins before bridging
  • ≀5% slippage on all transactions (per OP-PIP-87)
  • Aggregators (Jumper, LI.FI, etc.) for optimal routing
  • Bridge choice flexible, provided not subject to applicable sanctions
  • Solana hop allowed: If bridging directly to DAO Treasury is complex, PC may bridge to the Pythian Council Solana multisig first, then transfer to DAO Treasury

4. Scope & Flow

Fees on Chain X β†’ PC EVM Multisig β†’ Swap to USDC β†’ Bridge β†’ DAO Treasury
                                                       β†˜οΈ (or PC Solana Multisig β†’ DAO Treasury)

The Pythian Council acts with strictly limited discretion, executing repatriation within the parameters, executing repatriation strictly within the parameters set forth by this proposal and OP-PIP-87. Once funds reach Treasury, existing allocation rules apply.

5. Reporting & Documentation

PC posts completion report per batch:

  • Transaction hashes
  • Amounts per chain
  • Bridge/swap breakdown
  • Final deposit to Treasury

Upon passage, all deployed Safe multisig addresses and their respective chains will be documented by the Pythian Council in About the Pythian Council.

Implementation


Upon passage:

  1. PC deploys Safe multisigs on priority chains

  2. Subsequent OP-PIPs authorize contract upgrades redirecting fees

  3. PC executes repatriation per this framework

PROPOSAL: OP-PIP-125: Cross-Chain Fee Repatriation Framework | Pyth Governance

1 Like