[docs-agent] Point Solana subscription + Yellowstone gRPC mainnet docs at streaming.alchemy.com - #1568
Open
alchemy-bot wants to merge 1 commit into
Open
[docs-agent] Point Solana subscription + Yellowstone gRPC mainnet docs at streaming.alchemy.com#1568alchemy-bot wants to merge 1 commit into
alchemy-bot wants to merge 1 commit into
Conversation
…s at streaming.alchemy.com Solana Subscription API (WebSocket) and Yellowstone gRPC docs now point Mainnet at the new streaming host (`solana-mainnet.streaming.alchemy.com`) while keeping Devnet on the existing `solana-devnet.g.alchemy.com` host. Verified live: streaming host serves HTTP/2 gRPC + WSS subscriptions but 404s on plain HTTP JSON-RPC, so the HTTP JSON-RPC endpoint that appears alongside `wsEndpoint` in @solana/web3.js snippets stays on `.g.alchemy.com`; the two `getSlot` helper calls in the historical-replay guide stay on `.g.alchemy.com` for the same reason. Overview page `solana-subscription-api-endpoints.mdx` gets an explicit Mainnet/Devnet code group and rewritten Info callout that flags the different host bases (users can no longer just swap `solana-mainnet` for `solana-devnet`). Refs DOCS-206 Requested-by: @
🔗 Preview Mode
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Points the Solana Subscription API (WebSocket) and Yellowstone gRPC docs at Alchemy's new streaming host on Mainnet, while keeping Devnet on the existing
g.alchemy.comhost.Mainnet:
wss://solana-mainnet.streaming.alchemy.com/v2/<key>https://solana-mainnet.streaming.alchemy.comDevnet (unchanged):
wss://solana-devnet.g.alchemy.com/v2/<key>https://solana-devnet.g.alchemy.comLive-verified:
solana-mainnet.streaming.alchemy.comserves HTTP/2 withcontent-type: application/grpcon gRPC POST paths and accepts WSS upgrades, but returns 404 on plain HTTP JSON-RPC methods likegetBlockHeight/getSlot. That's why the plain HTTP JSON-RPC references in the WebSocket pages (the@solana/web3.jsConnectionHTTP endpoint alongsidewsEndpoint) and inhistorical-replay.mdx'sgetSlothelper stay on.g.alchemy.com.Changes
Solana Subscription API (WebSocket) —
content/api-reference/websockets/solana-subscription-api-endpoints/:solana-subscription-api-endpoints.mdx: rewritten Mainnet/Devnet URL block into aCodeGroupand updated the Info callout to flag the different host bases (the previous "swapsolana-mainnetforsolana-devnetin the URL above" instruction no longer works because the host base itself changes).account-subscribe.mdx,logs-subscribe.mdx,program-subscribe.mdx,root-subscribe.mdx,signature-subscribe.mdx,slot-subscribe.mdx: swapped everywss://solana-mainnet.g.alchemy.com/v2/...→wss://solana-mainnet.streaming.alchemy.com/v2/...(bothwscatandwsEndpointreferences). Left thehttps://HTTP RPC endpoint used by@solana/web3.jsConnectionon.g.alchemy.combecause the streaming host does not serve HTTP JSON-RPC.Yellowstone gRPC —
content/api-reference/yellowstone/:overview.mdx: updated Mainnet URL in the "supported on both Mainnet and Devnet" Info box.quickstart.mdx: Info box + both Rust code samples.examples.mdx: 3endpointreferences in the Rust snippets.historical-replay.mdx: swapped theGeyserGrpcClient::build_from_sharedendpoint. Left the two.post(format!("https://solana-mainnet.g.alchemy.com/v2/{}", api_key))calls in theget_current_slothelpers untouched — those are HTTP JSON-RPC, not gRPC.Not touched
content/api-reference/solana/HTTP JSON-RPC pages.content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx.docs/solana-block-subscribebranch (PR still in review for DOCS-205) already introduced the streaming URL on the newblock-subscribe.mdxpage; this PR extends the same host to the rest of the subscription surface. No conflicts expected.Linear
DOCS-206 — https://linear.app/alchemyapi/issue/DOCS-206/point-solana-subscription-api-yellowstone-grpc-mainnet-docs-at
Requested by
@victorbware (via Slack thread)