# \[PASSED\] OP-PIP-96: Enable Trusted Signer for Pyth Lazer on Sui (mainnet & testnet)

**URL:** <https://forum.pyth.network/t/passed-op-pip-96-enable-trusted-signer-for-pyth-lazer-on-sui-mainnet-testnet/2352>\
**Category:** Proposals\
**Tags:** operational-pip\
**Created:** [February 16, 2026, 11:05am UTC](https://forum.pyth.network/t/passed-op-pip-96-enable-trusted-signer-for-pyth-lazer-on-sui-mainnet-testnet/2352 "2026-02-16T11:05:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![KemarTiti](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/kemartiti/32/5_2.png) [@KemarTiti](https://forum.pyth.network/u/KemarTiti)\
**Post date:** [February 16, 2026, 11:05am UTC](https://forum.pyth.network/t/passed-op-pip-96-enable-trusted-signer-for-pyth-lazer-on-sui-mainnet-testnet/2352/1 "2026-02-16T11:05:30Z")

</div>

**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.

**Implementation plan**  
Proposal ID: [`7Jo7BWbTwUnbEwTMgQETR5UovvLZXyKZPVJZ29mDJ2CV`](https://proposals.pyth.network/?tab=proposals&proposal=7Jo7BWbTwUnbEwTMgQETR5UovvLZXyKZPVJZ29mDJ2CV)

**Proposal verification**

Install `pnpm` and `jq`

Clone the pyth-crosschain repository, build contract\_manager, and run `check_proposal` script:

```auto
git clone https://github.com/pyth-network/pyth-crosschain \
  --branch lazer-proposal-test
cd pyth-crosschain

pnpm install && pnpm turbo build
pnpm tsx scripts/check_proposal.ts
  --cluster mainnet-beta \
  --proposal 7Jo7BWbTwUnbEwTMgQETR5UovvLZXyKZPVJZ29mDJ2CV

```

Script should respond with the following output:

```auto
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

```

---

<div class="post-metadata">

**Author:** ![scp](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/scp/32/627_2.png) [@scp](https://forum.pyth.network/u/scp)\
**Post date:** [February 16, 2026, 11:12am UTC](https://forum.pyth.network/t/passed-op-pip-96-enable-trusted-signer-for-pyth-lazer-on-sui-mainnet-testnet/2352/2 "2026-02-16T11:12:05Z")

</div>

Dear @KemarTiti,

I am a bit curious, if Pyth Lazer is live on Sui, are all dApps on SUI will be allowed to use the feed?

Or would each dApp have to pay separately for an api key to acess the lazer feed?

How is it compared with the integration in Cardano?

From SCP with Love

---

<div class="post-metadata">

**Author:** ![KemarTiti](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/kemartiti/32/5_2.png) [@KemarTiti](https://forum.pyth.network/u/KemarTiti)\
**Post date:** [February 16, 2026, 11:28am UTC](https://forum.pyth.network/t/passed-op-pip-96-enable-trusted-signer-for-pyth-lazer-on-sui-mainnet-testnet/2352/3 "2026-02-16T11:28:17Z")

</div>

gm @scp

Great question!

1st it is important to understand that it will work the same for all chains: Sui, Solana, any EVMs, etc…

**Pyth Core (Price Feeds)**

1. Anyone can fetch price proofs from Hermes at no cost
2. Anyone can submit those proofs to the public smart contracts
3. Contracts store the latest price onchain
4. ⚠ Free-riding possible: once a price is pushed onchain, others can read it without paying

**Pyth Lazer (Pro)**

1. You must have a Pyth Pro API key to receive Lazer price updates
2. Only with that key can you get the signed data needed to interact with the contracts
3. Contracts do not store prices — they only verify and pass through
4. ✅ 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.

---

<div class="post-metadata">

**Author:** ![scp](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/scp/32/627_2.png) [@scp](https://forum.pyth.network/u/scp)\
**Post date:** [February 16, 2026, 11:36am UTC](https://forum.pyth.network/t/passed-op-pip-96-enable-trusted-signer-for-pyth-lazer-on-sui-mainnet-testnet/2352/4 "2026-02-16T11:36:55Z")

</div>

@KemarTiti thanks for the quick reply,

A followup question. What about pyth integration on fogo chain? I think Pyth lazer is enshrined in the blockchain.

From SCP

---

<div class="post-metadata">

**Author:** ![KemarTiti](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/kemartiti/32/5_2.png) [@KemarTiti](https://forum.pyth.network/u/KemarTiti)\
**Post date:** [February 16, 2026, 11:41am UTC](https://forum.pyth.network/t/passed-op-pip-96-enable-trusted-signer-for-pyth-lazer-on-sui-mainnet-testnet/2352/5 "2026-02-16T11:41:00Z")

</div>

It has been deployed already – for Pyth Lazer/Pro official/public deployments, check the docs: [Contract Addresses | Pyth Developer Hub](https://docs.pyth.network/price-feeds/pro/contract-addresses)

---

<div class="post-metadata">

**Author:** ![scp](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/scp/32/627_2.png) [@scp](https://forum.pyth.network/u/scp)\
**Post date:** [February 16, 2026, 11:47am UTC](https://forum.pyth.network/t/passed-op-pip-96-enable-trusted-signer-for-pyth-lazer-on-sui-mainnet-testnet/2352/6 "2026-02-16T11:47:17Z")

</div>

Thanks for the reply. I am looking forward to see more chains integrating pyth lazer directly.