Skip to content

Re-sync the v2 query schemas with the engine - #188

Merged
mo4islona merged 1 commit into
mainfrom
fix/resync-query-schemas-v2
Oct 18, 2026
Merged

mo4islona merged 1 commit into
mainfrom
fix/resync-query-schemas-v2

Conversation

@mo4islona

Copy link
Copy Markdown
Contributor

Copies metadata/{evm,solana,substrate}.yaml from sqd-query-engine master (8dc0f8b) into src/sqd-network/query-schemas-v2/. The other four kinds are already in sync.

The copies predate the engine's encodings for struct members (sqd-query-engine a8f6e03). With them missing, the new engine answers two fields differently from the legacy engine:

  • solana transactions[].transactionConfig.priorityFee: 1000000 instead of "1000000"
  • evm transactions[].authorizationList[].nonce: a number instead of a decimal string

The re-sync also brings two weight hints that change only page sizes: weight: 128 on substrate block digest, and weight_key on evm logs and substrate events.

Compatibility: all three files pass the strict parse of engine 8dc0f8b. Engine 419b99d parses them too: it skips members and weight_key, and only the substrate digest weight changes for it.

A merge to main publishes the files at once.

🤖 Generated with Claude Code

The copies predate the engine's encodings for struct members, so the engine
wrote solana `transactionConfig.priorityFee` and evm
`authorizationList[].nonce` as numbers where the legacy engine writes decimal
strings. Older engines skip the keys they do not know.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@mo4islona
mo4islona merged commit a6bfa62 into main Oct 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant