Repository navigation
Ship mainnet RFQ settlement and streamline Chat - #3
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.
APP20 now supports permissionless maker registration, automatic quote comparison with a minimum receive amount, and funded private settlement through the STRK20 mainnet pool. Chat loads incoming messages on unlock and every 60 seconds, keeps an explicitly unlocked session across navigation, and moves history, recovery and device controls into Chat settings.
The submission manifest includes three verified mainnet swaps, each exchanging 0.01 shielded STRK for 0.001 shielded USDC. Public receipt, event, trace and class-hash evidence is committed alongside the deployed contract artifacts. The same operator controlled maker and taker; this establishes Node SDK settlement, not independent trading volume or Ready/Privy browser acceptance. Mainnet Chat still needs its contract deployed, and the published demo video URL remains pending.
Changes include the maker UI and downloadable Node SDK, an authenticated Starkscan proving relay with documented payload exposure, updated agent and operator guides, the [20] favicon, chat wording and unused-code cleanup, and Remotion recording tools with a paced voiceover script. Keys, proving journals and local recordings remain outside Git.
Validation: