Mempool websocket #10

Open
opened 2025-05-09 12:08:04 +00:00 by eztvdpqx5 · 2 comments
eztvdpqx5 commented 2025-05-09 12:08:04 +00:00 (Migrated from github.com)

Currently block information is pulled from mempool regular API, but they have a websocket, should we switch to using that or not worth the extra complexity?

Currently block information is pulled from mempool regular API, but they have a websocket, should we switch to using that or not worth the extra complexity?
parabitdev commented 2025-05-09 19:22:19 +00:00 (Migrated from github.com)

Are we pulling on the serverside or clientside? If it is on clientside they should have enough rate limit to be fine, but if on serverside we will want to validate that.

Are we pulling on the serverside or clientside? If it is on clientside they should have enough rate limit to be fine, but if on serverside we will want to validate that.
eztvdpqx5 commented 2025-05-09 19:35:35 +00:00 (Migrated from github.com)

Tt should be called all or almost all on the client side, but would have to double check its not called anywhere by the server

Tt should be called all or almost all on the client side, but would have to double check its not called anywhere by the server
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
parasitepool/parastats#10
No description provided.