feat(rfq): add wallet inventory and signer boundary - #28
Merged
Conversation
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.
Summary
AvailablestateSIGHASH_ALLWhy
ADR 0007 requires the provider to reserve only authoritative wallet inventory and to recover signing work without depending on an input remaining in the current unspent set. Durable allocation state alone cannot prove that an output is still wallet-owned, unspent, or fresh enough to quote.
This change adds the wallet-capability boundary and quote-facing inventory coordinator while deliberately leaving concrete wallet/RPC/HSM implementations, pricing, final-PSET validation, networking, relay, and reconciliation to later milestones.
Safety properties
SIGHASH_ALLValidation
nix develop .#default --command just ci-checksNeed help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.