docs(lazer/stellar): add mainnet Lazer verifier to the example README - #133
Merged
Conversation
The Deploy section listed only the testnet verifier id, so a consumer flipping the walkthrough to mainnet had no way to find the right --lazer argument from the example itself. Replace the single-row table with a Testnet/Mainnet table linking both contracts on stellar.expert, and reword the lead-in to say the verifier is deployed on both networks while the walkthrough stays on testnet.
aditya520
approved these changes
Aug 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The
## Deploy (testnet)section oflazer/stellar/README.mdlisted only the testnet Pyth Lazer verifier:CAYFT5JE3UQTKT4Q6ZOZK4FXVYVT6RE3MFC7STA4UB6WAEGBT65MRU52Replaced with a two-row Testnet/Mainnet table, both ids linked to stellar.expert, and reworded the lead-in to say the verifier is deployed on both networks while the walkthrough stays on testnet.
Why
A consumer flipping the example from
--network testnettomainnetneeds the mainnet verifier id for the--lazerconstructor arg, and had no way to find it from the example itself.The walkthrough itself is deliberately left on testnet (
stellar keys generate deployer --network testnet, the testnet id in thestellar contract deploysnippet) — this is tutorial code and new users shouldn't be pointed at mainnet by default.Contract ids
Both ids are the canonical ones from the
contract_managerregistry inpyth-network/pyth-crosschain(contract_manager/src/store/contracts/StellarLazerContracts.json), and mirror the deployment tables in thepyth-network/pyth-lazercontracts/stellar/README.md.Verified live on-chain — both contracts resolve, expose the identical Pyth Lazer verifier interface (
verify_update,list_trusted_signers,update_trusted_signer, LE-ECDSA error set), and report the same trusted signer03a4380f01136eb2640f90c17e1e319e02bbafbeef2e6e67dc48af53f9827e155b.Testing
Docs-only.
ci-lazer-stellar.ymlcoverslazer/stellarwith Rust fmt/clippy/build only, which this change does not touch.