Open turadg opened 6 months ago
Dropping priority because we don't need this for release. We can retrofit later by upgrading the holder object (with the invitationMakers etc) with a makeTransfer
method that revokes its access to the underlying account.
What is the Problem Being Solved?
https://github.com/Agoric/agoric-sdk/issues/9075 and other Orchestration invitations need to provide ownable objects (aka "use objects") so that they can be transferred and revoked.
VaultFactory has a vaultHolder exo for this. We now have
prepareOwnable
but it hasn't been battled tested.Description of the Design
Security Considerations
Scaling Considerations
Test Plan
Upgrade Considerations