Raise payload cap for recovery snapshot queries - #12
Merged
Conversation
query_nodes(include_parents) returns every leaf's full ancestor chain in one message; a long-lived wallet blew past the transport's 4 MiB default (seen live: 6.9 MB -> resourceExhausted 'Message has exceeded the configured maximum payload size'). Scoped to the recovery queries via per-call CallOptions. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The owner query also returns historical nodes (old splits, spent intermediates) that no exit package uses. Walk each leaf's parent chain and keep only those ancestors; throw if a needed chain has a hole (replaces the blanket all-parents completeness check, which could fail on irrelevant historical chains). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
A real wallet's include_parents response was 6.9 MB, over the 4 MiB transport default —
resourceExhausted. Sets 128 MiB request/response caps via per-call CallOptions, scoped togetRecoverySnapshot()'s two query_nodes calls only. Verified against mainnet with both funded test wallets.🤖 Generated with Claude Code