Repository navigation
Blockmachine joins the RPC cost and free-tier benches - #3152
Merged
Merged
Conversation
… 15 cost cells
Blockmachine bills 1 Request Unit for almost every method, archive reads
included, and sells 20M units for $25, 100M for $125 and 1B for $999. On
that it leads every Ethereum dapp and indexer cell and simple reads from
100M up. It wins no trace cell: debug and trace cost 25 to 50 units, and a
billion trace requests need 9,722 RU/s against its 4,167 ceiling.
Catalogue entry from its own llms.txt plan table and the Ethereum gateway
method page, with the archive rule confirmed by the team on 2026-10-22
("1 RU except for trace and debug"). Its pages disagree on the Free plan's
rate limit and archive access, so that plan is marked uncertain and the
conflict is written into both specs. The keyless endpoint is a public
endpoint, not a plan, and is not ranked.
Spec prose recomputed from the harness on both catalogues: winners, the
Alchemy and QuickNode ratios (now 1.7x to 16.8x), provider counts, the
free-tier spread (OnFinality 12.0M to Blockmachine 10,000 simple reads).
Logo, product registry entry and the committed cost curve included.
This was referenced Oct 22, 2026
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
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.
Adds Blockmachine to bench 282 (rpc-cost) and bench 283 (rpc-free-tier), with its logo and product registry entry.
What changes on the board, computed by running the harness on the old and new catalogues:
Blockmachine is 8th on trace (25.2 RU a request) and cannot serve 1B trace under its 250,000 RU/min limit. Its keyed Free plan (10,000 RU a month) ranks last on bench 283; the keyless endpoint (60 RU/min per IP) is a public endpoint, not a plan, and is not ranked, as for other keyless RPCs.
Sources:
blockmachine.io/llms.txtplan table (polled, baseline hash), the Ethereum gateway method page (manual, its HTML embeds a build id), and the team's own statement that every method is 1 RU except trace and debug. The Free plan isconfidence: uncertain: the pricing card says 300 requests/min with archive, llms.txt says 100 RU/min with archive from Standard up.Checks:
go test ./...in the harness,pnpm validate(253 specs),tsc --noEmit,bun test src/(678 pass).Before main: the harness image bakes the catalogue in, so the VPS container needs a rebuild after merge, then a worker rebuild for the spec. We told Blockmachine they would see the results before they go live, so staging is the review copy.