feat(rfq): add inventory-aware quote engine - #29
Merged
Conversation
feat(rfq): validate final settlement PSETs
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
Why
PR #28 established the authoritative wallet inventory, confidential destination, and committed-job signer capabilities. This PR builds the next layer over that boundary: a quote request can now be priced against fresh durable availability, converted into one venue-neutral transaction contribution, and reserved without races or ambiguous replay.
The quote engine deliberately remains transport-free.
FirmQuoteis an internal unauthenticated artifact, not a provider-signed network quote. Concrete market-data pricing, final-PSET validation, wallet/RPC/HSM implementations, authenticated networking, signing orchestration, relay, and chain reconciliation remain later milestones.Safety properties
AvailablestateStorage compatibility
The provider database remains disposable preproduction state. Schema and private record-layout versions intentionally remain
1; local databases created by prior alpha builds must be deleted and recreated. A real migration policy is required before provider storage is treated as production data.Validation
nix develop .#default --command just ci-checksNeed help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.