Repository navigation
Add Pinax to Blockchain Access / Data Indexing - #103
chillsauce wants to merge 3 commits into
Conversation
Pull Request ReviewThis PR adds Pinax to the Blockchain Access / Data Indexing section of data.json for BNB Smart Chain. The new catalog entry includes its logo, website, supported chain, tags, and a description of its Firehose, Substreams, archive JSON-RPC, and Token API services. Sensitive ContentNo sensitive content detected. Security IssuesNo serious security issues detected. Generated by Hashdit Bot. This tool can absolutely NOT replace manual audits. |
|
Checking in — this is a single entry appended to Verified today: I can see external PRs here tend to land in batches rather than one at a time, so no urgency — just confirming it's still current and that nothing is needed from my side. |
"Pinax maintains both projects alongside StreamingFast" is a claim the entry gives no source for. Another chain's docs reviewer asked us to cut the same sentence, so remove it here too rather than leave the two listings saying different things. The remaining statements are checkable: bsc.firehose.pinax.network reports blockFeatures ["extended"], which is what backs the call traces, balance changes and storage changes described above. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Pull Request ReviewThis PR adds Pinax to the project’s data catalog under Blockchain Access / Data Indexing for BNB Smart Chain. The new entry includes Pinax’s logo, website, supported chain, service description, and tags. Sensitive ContentNo sensitive content detected. Security IssuesNo serious security issues detected. Generated by Hashdit Bot. This tool can absolutely NOT replace manual audits. |
The entry said Firehose carries call traces, balance changes and storage changes "that a JSON-RPC node does not return". That is wrong. Archive nodes expose them through debug_ and trace_ methods, and Pinax's own RPC documentation lists those methods, so the sentence contradicted us. The real difference is narrower: Firehose carries that data in the block stream rather than one trace call per transaction, which is a throughput argument rather than an availability one. A reviewer on ethereum/ethereum-org-website#19378 caught this. The same sentence had been copied into several chain listings, so it is being corrected in each rather than left standing where nobody flagged it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Pull Request ReviewThis PR adds Pinax to Sensitive ContentNo sensitive content detected. Security IssuesNo serious security issues detected. Generated by Hashdit Bot. This tool can absolutely NOT replace manual audits. |
Adds Pinax to
data.jsonunder Blockchain Access / Data Indexing, alongside Envio.Submitted per the parameter table in the README:
bscNo new category or group is needed.
Annotation
Scope
bsconly. Pinax does not currently serve opBNB or Greenfield, so those are deliberately not claimed.Verification
Checked against the live service before submitting:
https://bsc.rpc.pinax.networkbsc.firehose.pinax.network:443bsc.substreams.pinax.network:443https://api.pinax.network(BNB Smart Chain included)data.jsonwas validated as JSON after the edit, and the entry was inserted beside the existing Data Indexing entries so the diff is additive only.🤖 Generated with Claude Code