-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: multiple deposits of unknown brand #7027
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -354,7 +354,7 @@ export const prepareSmartWallet = (baggage, shared) => { | |
/** | ||
* Put the assets from the payment into the appropriate purse. | ||
* | ||
* If the purse doesn't exist, we hold the payment until it does. | ||
* If the purse doesn't exist, we hold the payment in durable storage. | ||
* | ||
* @param {import('@endo/far').FarRef<Payment>} payment | ||
* @returns {Promise<Amount>} amounts for deferred deposits will be empty | ||
|
@@ -374,11 +374,13 @@ export const prepareSmartWallet = (baggage, shared) => { | |
return E(invitationPurse).deposit(payment); | ||
} | ||
|
||
// When there is no purse, queue the payment | ||
// When there is no purse, save the payment into a queue. | ||
// It's not yet ever read but a future version of the contract can | ||
if (queues.has(brand)) { | ||
queues.get(brand).push(payment); | ||
const extant = queues.get(brand); | ||
queues.set(brand, harden([...extant, payment])); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this seems to be the gist of it. |
||
} else { | ||
queues.init(brand, harden([payment])); // TODO: #6961 fix this. | ||
queues.init(brand, harden([payment])); | ||
} | ||
return AmountMath.makeEmpty(brand); | ||
}, | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting... so we don't yet trigger deposits when new issuers come along, but we support upgrade to a wallet that does.
Hm... is there a way for somebody to send an ERTP payment with a brand not known to the vbank? I can't think of one. I was thinking we might owe an issue for the case of newly-approved tokens, but I think we're internally consistent as-is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that's right