data(apis): add optional requestLimits column, document Alchemy HTTP batch limit (DBIP #3724) - #3737
Open
foxxx009 wants to merge 1 commit into
Open
Conversation
…batch limit (DBIP Chain-Love#3724) - Append empty requestLimits column to the canonical apis.csv and all 102 listing apis.csv files (header + one trailing empty field per row; no other column, row, or file touched). - Fill 6 canonical Alchemy offer rows with the documented provider-wide HTTP batch ceiling: [{"method":"*","transport":"http","metric":"batchRequests","maximum":1000, "sourceUrl":"https://www.alchemy.com/docs/reference/batch-requests"}] - Deliberately left blank: Alchemy WebSocket batch limits (official pages conflict: 20 vs 1,000) and QuickNode eth_getLogs block span (5 free vs 10,000 paid is plan-dependent and cannot be represented at offer granularity). Blank means unverified - no 0 sentinel, no guess. Local validation with the matching tools-side scripts: validate_csv.py All checks passed; csv_to_json.py exit 0; validate.py green. Resolved listing rows inherit the value (e.g. alchemy-mainnet-free in ethereum.json).
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.
Closes #3724
Problem (file:line)
references/offers/apis.csvexposes only free-textlimitations; a developer selecting a provider cannot see structured per-request ceilings (batch size,eth_getLogsblock span).Changes (by file)
references/offers/apis.csv+ 102 listingapis.csvfiles: append the optionalrequestLimitscolumn (header + one trailing empty field per row; no other column, row or file touched).[{"method":"*","transport":"http","metric":"batchRequests","maximum":1000,"sourceUrl":"https://www.alchemy.com/docs/reference/batch-requests"}]Deliberately left blank (per the DBIP's own rules)
eth_getLogsblock span: 5 (Free Trial) vs 10,000 (paid) is plan-dependent and cannot be represented accurately at offer granularity.Acceptance
blockSpancounts inclusive blocks (toBlock - fromBlock + 1) - documented in the column metadata*used only because the source documents an all-method transport constraintlimitations; nothing removedalchemy-mainnet-freeinethereum.jsoninherits the array)Tools PR
json-tools companion: schema (optional array, exact item shape, enums, positive integer), columns.json metadata, and
validate_request_limits()(exact key set, http(s) sourceUrl,(method, transport, metric)uniqueness, canonical offers + per-network resolved rows).Local validation
With the matching tools-side scripts:
validate_csv.pyAll checks passed;csv_to_json.pyexit 0;validate.pygreen. Negative cases (duplicate tuple,maximum: 0, bad transport/metric/URL) all rejected with per-row messages.Rewards address: 0x2409b47a530be3831158f10b08ac93f7d08c1ff2