Abstract
Perform a trusted signer update on Sui Lazer contracts to allow processing of user requests. This proposal enables signer key 03a4380f01136eb2640f90c17e1e319e02bbafbeef2e6e67dc48af53f9827e155b with expiration time 2027-02-13T06:26:40.000Z.
Rationale
Once deployed, Sui Lazer contracts can only have their configuration changed through proposal process, including trusted signers set. Contracts are deployed with empty configuration, effectively making them unable to process user requests until they receive initial configuration through proposal process.
Description
Proposal should emit a single Wormhole message targeted to Sui chain, with key configuration mentioned above.
secp256k1 unavailable, reverting to browser version
Verifying UpdateTrustedSigner264Bit on 'sui'
Trusted signer proposal info:
public key: 03a4380f01136eb2640f90c17e1e319e02bbafbeef2e6e67dc48af53f9827e155b
expires at: 2027-02-13T06:26:40.000Z
1st it is important to understand that it will work the same for all chains: Sui, Solana, any EVMs, etc…
Pyth Core (Price Feeds)
Anyone can fetch price proofs from Hermes at no cost
Anyone can submit those proofs to the public smart contracts
Contracts store the latest price onchain
Free-riding possible: once a price is pushed onchain, others can read it without paying
Pyth Lazer (Pro)
You must have a Pyth Pro API key to receive Lazer price updates
Only with that key can you get the signed data needed to interact with the contracts
Contracts do not store prices — they only verify and pass through
No free-riding: without API access, you can’t get the data to use the contracts
TLDR: The gate for Pro/Lazer is at the offchain layer — even though contracts are public, you can’t use them without first having API access to fetch the signed price data.