handle invitation offer results in smart wallet

[dckc]

What is the Problem Being Solved?

A normal pattern in Zoe contracts is, as in Atomic Swap:

const invitationP = aliceSeat.getOfferResult();

But the current walletFactory doesn't know to put that in the invitation purse.

Its only support for offer results is

• if it's primitive data (string, number, ...) put it in vstorage
• if it has invitationMakers, keep it around for continuing invitations

Description of the Design

Use E(invitationIssuer).getAmountOf(offerResult) to see if an offer result is an invitation; if so, put it in the invitation purse.

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations

[dtribble]

Since in some scenarios, you might want an invitation back and some continuing invitations, perhaps this. should just extend the continuing invitation pattern with an additional category of direct invitations.

[dckc]

In Jun 12 office hours, I talked with @Jovonni and co about...

~/projects/agoric-sdk/packages/smart-wallet
11:48 connolly@bldbox$ git diff .
diff --git a/packages/smart-wallet/src/offerWatcher.js b/packages/smart-wallet/src/offerWatcher.js
index 3b2bc004f..6994d6dbd 100644
--- a/packages/smart-wallet/src/offerWatcher.js
+++ b/packages/smart-wallet/src/offerWatcher.js
@@ -191,6 +191,11 @@ export const prepareOfferWatcher = baggage => {
               }
               facets.helper.updateStatus({ result: UNPUBLISHED_RESULT });
               break;
+              case 'remotable':{
+                const amt = await E(invitationIssuer).getAmountOf(result); // isLivePayment?
+                await E(invitationPurse).deposit(result)
+              }
+
             default:
               // drop the result
               facets.helper.updateStatus({ result: UNPUBLISHED_RESULT });