feat(lazer): Payload reference details#854
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
nidhi-singh02
requested review from
aditya520,
ali-behjati and
tejasbadadare
| | `real_time` | Updates sent immediately when available | High-frequency trading, real-time analytics | | ||
| | `fixed_rate@1ms` | Updates every 1 millisecond | Ultra-low latency applications | | ||
| | `fixed_rate@50ms` | Updates every 50 milliseconds | Low-latency trading systems | | ||
| | `fixed_rate@200ms` | Updates every 200 milliseconds | Standard trading applications | |
There was a problem hiding this comment.
We have a 1s channel now too
There was a problem hiding this comment.
Also real_time updates immediately when a new price is available, no faster than 1ms and no slower than 50ms.
There was a problem hiding this comment.
yeah, 1s channel got added.
I have added 1s and the description in real_time.
There was a problem hiding this comment.
Open to change the use case for real_time if it doesn't go well. @tejasbadadare
| **How to Choose**: Use `evm` for Ethereum-compatible chains, `solana` for | ||
| Solana, `leEcdsa` for custom implementations, and `leUnsigned` for off-chain. |
There was a problem hiding this comment.
I'm mention to choose the optimal signing algorithm for your use case. The formats are not blockchain specific. (We should have named this field better from the start and not mentioned specific chains.)
For example, we've used the solana format in non-SVM blockchains since Ed25519 was the most efficient algo for that specific chain.
There was a problem hiding this comment.
ahh got it, can you provide details to be added to How to Choose as in how they can decide on the basis of their use case ? so this section can be useful to the folks.
There was a problem hiding this comment.
I have changed the How to Choose section specifying the details provided above, hoping that will help the users.
3 participants
Description
Note: Will replace Lazer with Pyth Pro later on.
Type of Change
Areas Affected
Checklist
pre-commit run --all-filesto check for linting errorsRelated Issues
Closes #
Additional Notes
Contributor Information
Screenshots