chore(lazer) How Lazer works

[aditya520]

Description

• Add Mermaid/Process Flow Diagram
• Explain DL sequencer

Type of Change

• New Page
• Page update/improvement
• Fix typo/grammar
• Restructure/reorganize content
• Update links/references
• Other (please describe):

Areas Affected

Checklist

• I ran pre-commit run --all-files to check for linting errors
• I have reviewed my changes for clarity and accuracy
• All links are valid and working
• Images (if any) are properly formatted and include alt text
• Code examples (if any) are complete and functional
• Content follows the established style guide
• Changes are properly formatted in Markdown
• Preview renders correctly in development environment

Related Issues

Closes #

Additional Notes

Contributor Information

• Name:
• Email:

Screenshots

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ready	Preview	Comment	Oct 16, 2025 5:31pm
documentation	Error			Oct 16, 2025 5:31pm

[aditya520]

We call relayers and routers in our pyth-lazer code, but sequencers and observers in our internal docs. Are we going to rename stuff in future? I went with what was written in the code for brevity.

[Riateche]

It's not entirely true right now. We don't drop updates entirely, but relayer can mark any update as rejected. Its logic is not fully deterministic because we still have a circuit breaker. (We plan to remove it.)

[jayantk]

let's describe the policy that is implemented here -- "no price dropping outside of circuit breakers"

[aditya520]

I was trying not to mention circuit breakers at all as we are planning to remove it.

[Riateche]

We call relayers and routers in our pyth-lazer code, but sequencers and observers in our internal docs. Are we going to rename stuff in future? I went with what was written in the code for brevity.

Sequencers and observers are the names used in early docs that predate the code I think. Let's stick with relayers and routers.

[ali-behjati]

Overall looks good, i'd approve once you apply my comments.

[ali-behjati]

this is where deterministic behaviour is important, all the aggregators produce the exact same aggregate solely relying on the consistent stream of price updates.

[ali-behjati]

here if you are not mentioning Douro running the service and think about the future that this part gets more decentralized, the publishers signature should be checked too (otherwise Douro can forge them). You can add that the aggregator validates the signatures of publisher update transactions.

p.s: we don't do it now, but will do in the future.

[aditya520]

So should we mention that right now?