You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(pro): move ExampleConsumer lazer address into constructor (#3874)
Stores the pyth-lazer-stellar verifier's contract address at deploy
time via __constructor instead of taking it as an argument on every
update_price call. Matches the shipped example at
pyth-examples/lazer/stellar and the standard Soroban pattern where
one-time deployment configuration lives in instance storage.
Co-authored-by: Jayant Krishnamurthy <541339+jayantk@users.noreply.github.com>
Every property your contract reads must be requested in the Step 1 subscription — feed properties not in the subscription decode to `None`, so an unguarded `.expect(...)` will trap on-chain. Signed integer properties (`price`, `best_bid_price`, `best_ask_price`, `confidence`, `funding_rate`, `ema_price`, `ema_confidence`) are decoded as `Option<i64>`. Per-feed `feed_update_timestamp` (microseconds since epoch, requested as `feedUpdateTimestamp`) is the right field for freshness checks; the top-level `update.timestamp` is the payload-level timestamp. See the [Pyth Pro payload reference](/price-feeds/pro/payload-reference) for the complete wire format.
140
163
141
164
<Callouttype="info">
142
-
Submit the transaction from your off-chain client using
165
+
Pass the deployed [`pyth-lazer-stellar` contract id](/price-feeds/pro/contract-addresses#stellar)
166
+
as the `lazer` constructor argument at deploy time — e.g.
0 commit comments