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
The transfer invitation must include details of the vault being transferred in order for it to have a legible value.
Description of the Design
Add (at least) the current debt and collateral in the invitation custom properties,
Security Considerations
For an invitation to be a usefully transferrable eright, the invitation's amount must contain enough reliable information for someone else to determine whether they would want an invitation with that amount.
This is invitation legibility (#4822), also known as "The Fred problem" and "The (invitation) pig-in-a-poke problem". It is this legibility that enables higher-order smart contract composition, where derived rights created by contracts to be treated like any other eright by other contracts. This is indeed the purpose of converting active vaults into their exclusively transferrable invitation form.
In general, for an eright to be meaningfully tradable, they must be assayable. For the trading of erights to be protected by Zoe offer safety, the amount used in a proposal's want must be adequate to describe the right desired such that any right that satisfies that want actually satisfied the desire it is supposed to represent.
The current invitation form of a vault has none of the information needed to evaluate whether one would want the right it represents. The call to zcf.makeInvitation should include customProperties to be included in the invitation's amount that will reliably provide the needed information.
Test Plan
Make a test that wants more than the invitation specifies and therefore rejects the reallocate.
The text was updated successfully, but these errors were encountered:
What is the Problem Being Solved?
The transfer invitation must include details of the vault being transferred in order for it to have a legible value.
Description of the Design
Add (at least) the current debt and collateral in the invitation custom properties,
Security Considerations
For an invitation to be a usefully transferrable eright, the invitation's amount must contain enough reliable information for someone else to determine whether they would want an invitation with that amount.
This is invitation legibility (#4822), also known as "The Fred problem" and "The (invitation) pig-in-a-poke problem". It is this legibility that enables higher-order smart contract composition, where derived rights created by contracts to be treated like any other eright by other contracts. This is indeed the purpose of converting active vaults into their exclusively transferrable invitation form.
In general, for an eright to be meaningfully tradable, they must be assayable. For the trading of erights to be protected by Zoe offer safety, the amount used in a proposal's
want
must be adequate to describe the right desired such that any right that satisfies thatwant
actually satisfied the desire it is supposed to represent.The current invitation form of a vault has none of the information needed to evaluate whether one would want the right it represents. The call to
zcf.makeInvitation
should includecustomProperties
to be included in the invitation's amount that will reliably provide the needed information.Test Plan
Make a test that wants more than the invitation specifies and therefore rejects the reallocate.
The text was updated successfully, but these errors were encountered: