From bec1a0ece35dba164eb2e99160aef91c21293526 Mon Sep 17 00:00:00 2001
From: Jayant Krishnamurthy <541339+jayantk@users.noreply.github.com>
Date: Tue, 11 Aug 2026 23:38:41 +0000
Subject: [PATCH] docs(lazer/stellar): add mainnet Lazer verifier to the
 example README

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.
---
 lazer/stellar/README.md | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/lazer/stellar/README.md b/lazer/stellar/README.md
index 498e2eb8..a2c42a4e 100644
--- a/lazer/stellar/README.md
+++ b/lazer/stellar/README.md
@@ -36,12 +36,14 @@ The optimized contract is written to
 
 ## Deploy (testnet)
 
-This example points at the **already-deployed** Pyth Lazer verifier on Stellar testnet — you do not
-deploy the verifier yourself:
-
-| Contract | Testnet address |
-| -------- | --------------- |
-| Pyth Lazer verifier | `CAYFT5JE3UQTKT4Q6ZOZK4FXVYVT6RE3MFC7STA4UB6WAEGBT65MRU52` |
+This example points at the **already-deployed** Pyth Lazer verifier — you do not deploy the verifier
+yourself. It is live on both testnet and mainnet; the walkthrough below stays on testnet, so pass the
+mainnet id as `--lazer` if you deploy there instead:
+
+| Network | Pyth Lazer verifier |
+| ------- | ------------------- |
+| Testnet | [`CAYFT5JE3UQTKT4Q6ZOZK4FXVYVT6RE3MFC7STA4UB6WAEGBT65MRU52`](https://stellar.expert/explorer/testnet/contract/CAYFT5JE3UQTKT4Q6ZOZK4FXVYVT6RE3MFC7STA4UB6WAEGBT65MRU52) |
+| Mainnet | [`CACZ3GBAKUPIAFRILUFO27J5RUH5GJ2VSJ46LP6GJYSKGDRTQ5MS3HCH`](https://stellar.expert/explorer/public/contract/CACZ3GBAKUPIAFRILUFO27J5RUH5GJ2VSJ46LP6GJYSKGDRTQ5MS3HCH) |
 
 Configure a funded testnet identity once: