Skip to content

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

Merged
Flotapponnier merged 1 commit into
devfrom
harness/serialized-ws-engine
Oct 13, 2026
Merged

Flotapponnier merged 1 commit into
devfrom
harness/serialized-ws-engine

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Serialized asked us to move from wss://api.serialized.xyz/v1/stream to wss://ws.serialized.xyz/v1/stream: same key, same messages, new engine; the old one is being retired.

  • The URL was a hard-coded constant in serialized_head_lag_monitor.go; it is now SERIALIZED_WS_URL (config.go) defaulting to the new engine, so rolling back is a Railway variable.
  • Provider page copy updated to the new URL.

Verified with the production key: both endpoints authenticate identically and stream the same event count and fields (the new one adds cursor / updatePeriod, ignored by the decoder). A 60 s local run of the harness subscribed all 4 pools and published head_lag_ref_seconds on base, bnb and solana. go build and go test ./cmd/script pass.

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.
@Flotapponnier
Flotapponnier merged commit 2419544 into dev Oct 13, 2026
2 checks passed
@Flotapponnier
Flotapponnier deleted the harness/serialized-ws-engine branch October 13, 2026 12:06
Flotapponnier added a commit that referenced this pull request Oct 13, 2026
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)
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