Skip to content

Commit d6b2fb4

Browse files
committed
doc: update readme
1 parent 68929d3 commit d6b2fb4

File tree

1 file changed

+2
-2
lines changed
  • target_chains/ethereum/contracts/contracts/pulse/scheduler

1 file changed

+2
-2
lines changed

target_chains/ethereum/contracts/contracts/pulse/scheduler/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,12 +34,12 @@ Pyth Pulse ensures that on-chain Pyth prices remain up-to-date according to user
3434
- Provides functions for users (Readers) to read the latest pushed prices for a subscription.
3535
- Allows Managers to manage their subscription parameters and funds.
3636
- Allows Keepers to discover active subscriptions (`getActiveSubscriptions`).
37-
2. **Keeper Network (Off-Chain):** A permissionless network of off-chain providers.
37+
2. **Keeper Network (Off-Chain):** _Implementation pending._ A permissionless network of off-chain providers.
3838
- Keepers constantly monitor active subscriptions listed in this Scheduler Contract.
3939
- They fetch the latest off-chain price data from a Pyth Price Service endpoint (e.g., Hermes).
4040
- They compare the latest off-chain prices and timestamps with the last prices stored on-chain in this contract for each subscription.
4141
- If a subscription's trigger conditions (e.g., time since last update > `heartbeatSeconds`, or price deviation > `deviationThresholdBps`) are met, the Keeper submits a transaction to this contract's `updatePriceFeeds` function, including the necessary Pyth price update data.
42-
3. **Web UI (Off-Chain):** The primary interface for users to interact with Pyth Pulse.
42+
3. **Web UI (Off-Chain):** _Implementation pending._ The primary interface for users to interact with Pyth Pulse.
4343
- Allows users (Managers) to easily create, configure, monitor, and fund their price feed subscriptions by interacting with this Scheduler Contract's functions.
4444

4545
### High level flow

0 commit comments

Comments
 (0)