Repository navigation
Add confidential RFQ development flow and refresh demo tooling - #4
Merged
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.
The existing RFQ settlement exposes funded trade terms publicly. Add a confidential RFQ development flow using a joint shielded escrow: both parties approve the same encrypted settlement, and either party can independently recover its own funds after expiry.
Includes the Cairo contract, Node SDK with strict action/proof validation and durable recovery metadata, a loopback development workspace, and updated product/agent documentation. Confidential mainnet activation remains disabled; local execution uses simulated proof facts, with real proofs, independent wallet integration, and review still required.
Refresh the demo tooling with the selected ElevenLabs narration, smoother macOS-style cursor movement, shorter framed scenes, natural Chat samples, and automated voice-tail verification. Ignore the whole
artifacts/directory and remove previously tracked artifacts while preserving local files. Keep the existing mainnet submission transactions and durable deployment evidence.Validation:
No new mainnet transactions were submitted, and the video remains a local artifact pending publication.