Skip to content

Commit bc12c87

Browse files
authored
fix(benchamrks) Fix broken links (#455)
1 parent c3f0a65 commit bc12c87

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

pages/benchmarks/index.mdx

+3-3
Original file line numberDiff line numberDiff line change
@@ -18,10 +18,10 @@ Technically, each displayed price corresponds to the Pyth price update published
1818

1919
## On-Chain Contracts
2020

21-
On-chain contracts can consume benchmark prices using the same pull model as [Pythnet Price Feeds](pythnet-price-feeds.md).
21+
On-chain contracts can consume benchmark prices using the same pull model as [Pythnet Price Feeds](../price-feeds/price-feed-ids.mdx).
2222
Integrators can follow these three steps:
2323

24-
1. Use the [Hermes](pythnet-price-feeds/hermes) endpoint `/api/get_vaa` to retrieve a signed price update for the desired price feed and time.
24+
1. Use the [Hermes](pythnet-price-feeds/hermes) endpoint `/v2/updates/price/{price_time}` to retrieve a signed price update for the desired price feed and time.
2525
This endpoint will return a signed price update, specifically the price update immediately after the queried time.
2626
This step can be done in either a web frontend or a backend process, depending on who is expected to initiate the transaction.
2727
2. Pass this price update to your on-chain contract as part of the transaction that needs the benchmark data.
@@ -30,7 +30,7 @@ Integrators can follow these three steps:
3030
The price update will only be valid if the signatures are correct and the update falls within a user-configured time interval; integrators should set this time interval such that it matches their desired time.
3131

3232
Note that this process is similar to the standard process for consuming pull updates.
33-
The main differences are that users call the `get_vaa` endpoint instead of `latest_vaas`, and the on-chain contract calls `parsePriceFeedUpdates` instead of `updatePriceFeeds`.
33+
The main differences are that users call the `/v2/updates/price/{price_time}` endpoint instead of `/v2/updates/price/latest`, and the on-chain contract calls `parsePriceFeedUpdates` instead of `updatePriceFeeds`.
3434
The pyth-crosschain repo has [example code](https://github.com/pyth-network/pyth-crosschain/blob/main/target_chains/ethereum/sdk/js/src/examples/EvmBenchmark.ts) for an integration along the lines above for EVM chains.
3535

3636
## API Documentation

0 commit comments

Comments
 (0)