What is the Problem Being Solved?

A user needs some assurance that when they send to an agoric1 address for Orchestration purposes, that the funds will end up where they expect. A UI needs to be able to validate this expectation for them without requesting fresh information from vstorage.

Description of the Design

Support something like "plus addressing" in Gmail addresses (e.g. [email protected] )

A contract can provision an LCA for receiving and staging funds to transfer.
Some new ability allows creation of virtual addresses that specifies an LCA plus supplemental data.

For the use case described, the contract can use the supplemental data to specify the final destination account.
It can publish the LCA so UI libraries can cache the vstorage key (the base account) and automatically create an address that has the final destination encoded.

Scope TBD:

• Change to vat-transfer
  • hopefully sufficient!
  • get the local virtual destination, extract the base and supplement, forward to the base and notify the contract with the supplemental data
• Chain change (requiring Software Upgrade)
• Both?

Security Considerations

Highly powered new capability needs careful review

Scaling Considerations

Test Plan

Upgrade Considerations