Repository navigation
feat: add multi_buy atomic slippage-protected key purchases across creators - #1208
Open
Vhickcrypt150-pixel wants to merge 1 commit into
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.
Overview
This PR adds event definitions supporting the
multi_buyflow: a per-legKeyPurchasedevent reuse and a newMultiBuyCompletedevent emitted once when all legs succeed. The atomic execution logic and pre-flight validation live in the contract entrypoint, which is not part of this changed-file set.Related Issue
Changes
🔐 Event Definitions
creator-keys/src/events.rsMultiBuyCompletedevent carryingbuyer,leg_count,total_cost, andledger, emitted only after every leg has succeeded.KeyPurchasedevent shape for each individual leg.Verification Results
Not run as part of this change set. Only
creator-keys/src/events.rswas modified; the unit and integration tests described in the issue (3-leg success, mid-leg slippage rollback, duplicate creator, 11-leg rejection, past deadline, insufficient funds) are not included in the changed files and have not been verified here.max_priceMultiBuyCompletedevent emitted only when all legs succeedCloses #717