Repository navigation
Conversation
Pull Request ReviewThis documentation-only PR adds BlockVectra to the RPC Providers list on the BNB Smart Chain JSON-RPC endpoint page. The new entry links to BlockVectra's official documentation with a referral query parameter. Sensitive ContentNo sensitive content detected. Security IssuesNo serious security issues detected. Generated by Hashdit Bot. This tool can absolutely NOT replace manual audits. |
|
@0xlucasliao gentle ping — this docs-only PR adds BlockVectra to the BSC RPC providers list (one row, links to our public docs). It's mergeable and the automated review found no issues. Happy to adjust the wording or placement if needed. Thanks! |
3a188ec to
929acfd
Compare
Pull Request ReviewThis documentation-only PR adds BlockVectra to the BNB Smart Chain RPC Providers list. The new entry links to BlockVectra's official documentation with a referral query parameter. Sensitive ContentNo sensitive content detected. Security IssuesNo serious security issues detected. Generated by Hashdit Bot. This tool can absolutely NOT replace manual audits. |
|
Friendly follow-up: this entry is still current and the branch is up to date. Happy to adjust anything if needed — thanks for maintaining the list. |
Pull Request ReviewThis documentation-only PR adds BlockVectra to the BNB Smart Chain RPC Providers list and links directly to its BSC Mainnet setup page. It does not modify RPC defaults, endpoint behavior, application code, or policy text. Sensitive ContentNo sensitive content detected. Security IssuesNo serious security issues detected. Generated by Hashdit Bot. This tool can absolutely NOT replace manual audits. |
Proposes adding BlockVectra to the existing BSC RPC Providers list, with one BSC-specific setup link.
eth_getLogsresponse. This is one internal QA sample, not a reproduction of the legacy endpoint issue, a performance benchmark or proof of full history.node src/public-read-cli.ts 56. It reads the current chain directory, verifies the selected public chain ID, then reads a block number, with at most three HTTP requests and no account or key. It stops if the directory does not advertise the required public methods. The log comparison above used a keyed endpoint; it does not imply keylesseth_getLogsaccess.The patch remains a provider-list entry; it changes no endpoint defaults or policy text.
A saved keyless BSC first-use check is now available: the unchanged CLI at
71a78c0bcompleted on 2 November at 20:34 UTC with Node.js 24.21.0, exit 0, chain ID 56 and a block number. It includes the original stdout, pinned reproduction command and explicit internal-QA scope. No dependency installation or credentials were used. Total process time is not a performance benchmark; transport attempts and raw HTTP responses were not captured.The listing now links directly to the BSC setup page rather than the documentation homepage. A single link check on 3 November returned HTTP 200 and confirmed chain ID 56, the keyless endpoint and the separate API-key requirement for
eth_getLogs. The page lists the current public history window as 100 blocks. No RPC was executed for this link check.Acceptance: only the provider-link destination changes; the BSC page returns 200 with the correct public endpoint and canonical URL; all other upstream document bytes are unchanged.