[PASSED] OP-PIP-126: Enable Trusted Signer for Pyth Lazer on IOTA

Proposals
1

Abstract

Perform a trusted signer update on IOTA Lazer contracts to allow Douro Labs to process user requests. This proposal enables signer key 03a4380f01136eb2640f90c17e1e319e02bbafbeef2e6e67dc48af53f9827e155b with expiration time 2036-07-21T22:00:00.000Z.

This follows the same pattern as OP-PIP-96: Enable Trusted Signer for Pyth Lazer on Sui.

PROPOSAL: Pyth Network

This Proposal is verified and signed by the Pythian Council.

Rationale

Once deployed, IOTA Lazer contracts can only have their configuration changed through the proposal process, including trusted signers. Contracts are deployed with empty configuration, effectively making them unable to process user requests until they receive initial configuration through the proposal process.

Description

Proposal should emit a single Wormhole message targeted to the IOTA chain, with the key configuration mentioned above.

Implementation Plan

Proposal ID: J2Ecp3CNJBwg6dVXuQ7Tk2CkgfAs78AU1ufzXWvvSiaa

Link: Pyth Network

Proposal Verification

Install pnpm, jq, and Node.js v24+

Clone the pyth-crosschain repository and run the check_proposal script:

git clone <https://github.com/pyth-network/pyth-crosschain>
cd pyth-crosschain
git fetch origin pull/3921/head:lazer-proposal-check
git checkout lazer-proposal-check

Verify you’re on commit a2ed211:

git rev-parse HEAD
# Should output: a2ed211d0f9061bde7b6e109a9031d906bc83781

Build and run:

pnpm install && pnpm turbo build --filter=@pythnetwork/contract-manager
cd contract_manager
tsx scripts/check_proposal.ts \
  --cluster mainnet-beta \
  --proposal J2Ecp3CNJBwg6dVXuQ7Tk2CkgfAs78AU1ufzXWvvSiaa

Script should respond with the following output:

secp256k1 unavailable, reverting to browser version
Verifying UpdateTrustedSigner on 'iota_sui_mainnet'
Trusted signer proposal info:
  public key: 03a4380f01136eb2640f90c17e1e319e02bbafbeef2e6e67dc48af53f9827e155b
  expires at: 2036-07-21T22:00:00.000Z
2 Likes