Skip to content

Promote develop to main: live socket gate and the block not-found status - #17

Merged
bitcoinuniverseadmin merged 4 commits into
mainfrom
develop
Aug 29, 2026
Merged

bitcoinuniverseadmin merged 4 commits into
mainfrom
develop

Conversation

@bitcoinuniverseadmin

Copy link
Copy Markdown

Carries PR 15 (the cutover now proves the live socket accepts a browser handshake, the check whose absence let the websocket be refused for every real user) and PR 16 (Core's unknown block answers 404 rather than 500, so multichain search stops reporting a healthy Bitcoin as unavailable on every transaction query).

🤖 Generated with Claude Code

bitcoinuniverseadmin and others added 4 commits August 29, 2026 09:00
The overlay refuses a websocket upgrade whose Origin is not on its
allowlist, and an unset allowlist refuses every origin. A handshake sent
without an Origin header is allowed, so every check we had said the live
socket worked while every real browser was refused and quietly fell back
to polling: pages still updated, and nothing on the server said no. The
cutover now sends the header a browser sends and refuses the release if
the answer is not 101, naming the setting to fix.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Core reports an unknown block as "Block not found" rather than as an
HTTP status, so the route mapped it to 500 and a hash that is simply not
a block became indistinguishable from a server fault. The explorer's own
search consults this route for every 64 hex query, so every transaction
search reported the whole Bitcoin chain unavailable while Bitcoin was
healthy and had answered definitively. The transaction routes beside it
already match Core's message this way.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Prove the live socket accepts a browser handshake
Answer 404 for a block hash Core does not know
@bitcoinuniverseadmin
bitcoinuniverseadmin merged commit 521a091 into main Aug 29, 2026
13 checks passed
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