MVP Implementation of On-Chain Wallet API

[samsiegart]

Implement the backend as an adapter to the collection of existing wallet backends.

Define the minimal API surface.

The wallet UI needs an API from the on-chain wallet, the current functionality of the UI requires the following schema:

  const firstSchema = harden({
    actions: Far('schemaActions', {
      createPurse: (issuer, id = newId('Purse')) =>
        E(walletBridge).makeEmptyPurse(issuer?.issuerPetname, id),
      createContact: (depositFacet, id = newId('Contact')) =>
        E(walletBridge).addContact(id, depositFacet),
      createIssuer: (issuer, id = newId('Issuer')) =>
        E(walletBridge).addIssuer(id, issuer, true),
    }),
    services: iterateNotifier(servicesNotifier),
    dapps: iterateNotifier(E(walletBridge).getDappsNotifier()),
    contacts: iterateNotifier(E(walletBridge).getContactsNotifier()),
    issuers: iterateNotifier(E(walletBridge).getIssuersNotifier()),
    offers: wrapOffersIterator(
      iterateNotifier(E(walletBridge).getOffersNotifier()),
    ),
    payments: iterateNotifier(E(walletBridge).getPaymentsNotifier()),
    purses: iterateNotifier(E(walletBridge).getPursesNotifier()),
  });

The wallet contract will contain all the users' wallets and expose one of these schemas to each user. The objects within the schema (e.g. services, dapps, etc.) need to be typed and documented properly.

[turadg]

@michaelfig this is listed as part of #5356 but this morning we didn't include it in the release planning. Which is correct? cc @dckc

[dckc]

In particular, does / should this block either of these?

• Smart wallets can get balances with zero transactions (for small # of users) #5356
• Smart wallet can trade with small # of users #5354

[dckc]

@michaelfig tells me yes, this blocks #5354

[dckc]

on further consideration, some work already done makes this not necessary.