Skip to content

Conversation

@tejasbadadare
Copy link
Contributor

Summary

Add a README for Pulse Scheduler

Rationale

Needed for the security audit

@vercel
Copy link

vercel bot commented Apr 21, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

6 Skipped Deployments
Name Status Preview Comments Updated (UTC)
api-reference ⬜️ Ignored (Inspect) Visit Preview Apr 22, 2025 8:27pm
component-library ⬜️ Ignored (Inspect) Visit Preview Apr 22, 2025 8:27pm
entropy-debugger ⬜️ Ignored (Inspect) Visit Preview Apr 22, 2025 8:27pm
insights ⬜️ Ignored (Inspect) Visit Preview Apr 22, 2025 8:27pm
proposals ⬜️ Ignored (Inspect) Visit Preview Apr 22, 2025 8:27pm
staking ⬜️ Ignored (Inspect) Visit Preview Apr 22, 2025 8:27pm

Copy link
Contributor

@merolish merolish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WIthout deep familiarity, writeup looks crisp.

- They fetch the latest off-chain price data from a Pyth Price Service endpoint (e.g., Hermes).
- They compare the latest off-chain prices and timestamps with the last prices stored on-chain in this contract for each subscription.
- 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.
3. **Web UI (Off-Chain):** The primary interface for users to interact with Pyth Pulse.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe mention it's written yet?

@tejasbadadare tejasbadadare merged commit e2c7e8f into main Apr 22, 2025
2 of 8 checks passed
@tejasbadadare tejasbadadare deleted the tb/pulse-scheduler/readme branch April 22, 2025 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants