Repository navigation
docs(unichain): add Pinax to data indexers - #1168
chillsauce wants to merge 1 commit into
Conversation
Pinax serves Unichain mainnet and Sepolia with Firehose block streaming and Substreams parallel indexing.
|
Thanks for contributing to Uniswap Docs! 🦄 Quick heads up on how this repo works: the docs you see on developers.uniswap.org are built from a separate source repo. When we accept a change here, we port it over there, so your fix might show up on the live site before it lands in this repo. Updates to this repo come in batches on a regular cadence. When yours is included, you'll be credited as a co-author on the commit, so the contribution counts on your GitHub profile and in Uniswap/docs. We review every PR but can't merge everything. Either way, someone from the docs team will follow up here once we've taken a look. One legal bit: by submitting a PR you agree your contribution is licensed under the repo's MIT license. |
|
Reviewed the diff (
Nothing blocking from a docs-accuracy standpoint. |
Adds Pinax to the Unichain Data Indexers page.
Pinax maintains the open source Firehose and Substreams projects alongside StreamingFast, and runs its own Unichain nodes. Firehose streams full blocks over gRPC — including call traces, internal transfers and balance changes a JSON-RPC node doesn't return — and Substreams runs Rust modules in parallel on top of those blocks.
This fills a category gap on the page: the current entries cover analytics platforms and subgraph frameworks, and there's no streaming-primitive provider listed.
Verified before submitting
eth_chainId→ 130eth_chainId→ 1301grpcurl … listreturnssf.firehose.v2.Streamsf.substreams.rpc.v2.StreamEntry format follows the existing ones — short description, getting-started link, and a
### Supported networkslist. Appended at the end, matching how Dune sits after The Graph.One thing I deliberately left out
I have not added Pinax to
node-providers.mdx, even though we serve archive JSON-RPC for Unichain. That page opens with:Our RPC gateway doesn't serve WebSocket — a
wss://handshake returns 200 with noUpgradeheader — so adding us there would make that statement false for one of the entries. Flagging it rather than quietly skipping it, in case you'd rather reword the callout or list us with a caveat.🤖 Generated with Claude Code