Clarify public WebSocket availability in Flashblocks docs

Open Beginner friendly
#1,409 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Domain
api, documentation

Research direction

Start with the RPC overview, eth_subscribe, Flashblocks FAQ, newFlashblocks, newFlashblockTransactions, and pendingLogs pages named in the issue. Verify their WebSocket guidance against the observed 405 response, then update the examples and availability statements so completion means they consistently direct subscription users to a provider or self-hosted node.

Written by the indexing model from the issue text.

Description

Summary

Several Base docs pages currently imply that the public wss://*.base.org endpoints can be used directly for Flashblocks subscriptions.

What I observed

A WebSocket upgrade request to the public Base RPC endpoints returns 405 Method Not Allowed instead of establishing a subscription connection.

Impacted areas

  • RPC overview
  • eth_subscribe
  • Flashblocks FAQ
  • newFlashblocks
  • newFlashblockTransactions
  • pendingLogs

Suggested fix

Update the docs to clarify that:

  • the public base.org RPC endpoints are currently HTTP-only
  • subscription-based Flashblocks usage should go through a node provider or a self-hosted Flashblocks-aware node
  • examples should avoid suggesting direct use of wss://mainnet-preconf.base.org
Dominant language
JavaScript
Stars
337
Forks
798
Avg merge
7h 24m
Merged PRs (30d)
51

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from base/docs

All issues in base/docs

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.