-
Notifications
You must be signed in to change notification settings - Fork 214
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
Smart wallet cannot handle invitations in offer proposals #9378
Comments
The smart wallet uses a read-only marshaller when publishing wallet contents; if something isn't already on the board, the smartWallet doesn't add it. A work-around is for the contract that creates the invitation to put the invitation handle on the board.
|
@erights points out that Amounts are designed to be not sensitive - parties should be able to It looks like none of the other things in the current and update records that the smartWallet publishes are sensitive either. So changing Downside: the board has no mechanism for collecting entries. So the invitation handles would consume space indefinitely. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Trying to grok... this snippet is about returning an invitation from an offer result, rather than from a payout. This allows Alice to give an invitation to Bob without Bob exiting his seat, but I'm unclear on how this addresses the |
oops; I think that comment should have gone on #8550 |
Describe the bug
In the invitation purse published to vstorage, invitations have a
null
slot value for their "handle" property. When trying to make an offer through the smart wallet with an invitation in the proposal, this null slot causes an error:To Reproduce
Send a
WalletSpendAction
with an invitation amount in the proposal, observe the error in the smart wallet.Expected behavior
A client can execute offers with invitation amounts in proposals.
Additional context
Discovered when trying to swap an invitation in Agoric/dapp-agoric-basics#42
The text was updated successfully, but these errors were encountered: