Skip to content

head-lag reads Serialized from its new stream engine - #2967

Merged
Flotapponnier merged 1 commit into
mainfrom
hotfix/serialized-ws-engine
Oct 13, 2026
Merged

Flotapponnier merged 1 commit into
mainfrom
hotfix/serialized-ws-engine

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Cherry-pick of #2966 (dev) onto main, this commit only. Railway's three aggregator-head-lag services build from main, so this is what moves them to wss://ws.serialized.xyz/v1/stream.

Serialized moved its stream to wss://ws.serialized.xyz/v1/stream (same
key, same frames; events gain a `cursor`, subscribed an `updatePeriod`,
both ignored by the decoder) and will retire wss://api.serialized.xyz.
The URL was a constant; it is now SERIALIZED_WS_URL with the new engine
as default, so a rollback is a Railway variable, not a deploy.

Checked side by side with the production key: identical auth, the same
event count and fields on Solana and Base over 15-20 s, and a local run
of the harness published head_lag_ref_seconds on base, bnb and solana.

(cherry picked from commit 2419544)
@Flotapponnier
Flotapponnier merged commit 45e5c44 into main Oct 13, 2026
2 checks passed
@Flotapponnier
Flotapponnier deleted the hotfix/serialized-ws-engine branch October 13, 2026 12:06
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.

1 participant