feat: add Serialized to benches 005 and 090 (chain coverage) - #2263
Merged
Conversation
Serialized publishes its chain list at the free GET /v1/meta/chains. The same list answers both benches: they run their own indexers and do not separate asset-registry coverage from DEX-pool coverage, so the count is identical on 005 and 090 by construction. Only chains the endpoint marks status=live are counted, so a future beta or deprecated status cannot inflate the number. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CpArutAtXuBb1BVNUDXoYA
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.
Adds Serialized to the two chain-count benches, on request.
GET /v1/meta/chainsis free (0 credits) and returns one row per chain with astatusfield. Onlystatus: liverows are counted so a future beta or deprecated entry cannot inflate the number.The same list answers both benches: Serialized runs its own indexers and does not separate "chains where we know tokens" from "chains where we index DEX pools", so the count is identical on 005 and 090 by construction. That is noted in the harness comment and in the 090 formula.
Expected placement
They land last on both, by a wide margin:
This was flagged before merging: the metric is breadth and their product is deliberately narrow. The row is accurate, just unflattering. Confirmed numbers land after the harness redeploys.
🤖 Generated with Claude Code
https://claude.ai/code/session_01CpArutAtXuBb1BVNUDXoYA