You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user, I can find an invitation in my wallet to use for an offer, without having to know the details (such as the invitation handle) for that particular invitation. Just knowing the instance and description should be enough to choose an invitation to use.
Status
A user can do this, but they can only try to match the keys and values of invitation details exactly and the search is not very efficient. It might get slow if there are a very large number of invitations in the user's wallet.
Details
As of 2/5/2021, a dapp can specify an invitation to use for a particular proposed offer in the wallet by including the property invitationQuery with the keys and values that they wish to use to match. The included keys and values are matched against exactly, and keys and values that are not included are ignored. This does not allow for general amount patterns, but does allow for this user story to be fulfilled. Additionally, it is not very efficient:
There is also a deploy-script-support helper findInvitationAmount which is used within the offer helper. It has the same efficiency problems as the wallet method:
Story
As a user, I can find an invitation in my wallet to use for an offer, without having to know the details (such as the invitation handle) for that particular invitation. Just knowing the instance and description should be enough to choose an invitation to use.
Status
A user can do this, but they can only try to match the keys and values of invitation details exactly and the search is not very efficient. It might get slow if there are a very large number of invitations in the user's wallet.
Details
As of 2/5/2021, a dapp can specify an invitation to use for a particular proposed offer in the wallet by including the property
invitationQuery
with the keys and values that they wish to use to match. The included keys and values are matched against exactly, and keys and values that are not included are ignored. This does not allow for general amount patterns, but does allow for this user story to be fulfilled. Additionally, it is not very efficient:agoric-sdk/packages/dapp-svelte-wallet/api/src/findOrMakeInvitation.js
Lines 49 to 60 in 0f02d52
There is also a deploy-script-support helper
findInvitationAmount
which is used within theoffer
helper. It has the same efficiency problems as the wallet method:agoric-sdk/packages/deploy-script-support/src/offer.js
Lines 15 to 30 in 0f02d52
Next Steps
Please see the Amount Patterns Implementation Plan issue
The text was updated successfully, but these errors were encountered: