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
History: inner (mint held) uref and outer uref (purse owner). Later created a new balance key variant (has an inner payload same as a uref). Purse is an outer key addr which points to an inner "unit" which has the same inner payload as a uref. Only the mint knows how to access this balance-tagged key. Now: managed via strong types. Use strong typing to separate "purse" from URefs.
On upgrade to 2.0: Find existing purse urefs, put them into a new variant key entry called 'purse'. Use the expiry feature to add expiry date to the uref of the old 'purse' uref.
Separates out purses from other urefs and allows us to implement proper commutative subtraction on urefs, because we know there are no longer any urefs that are purses - and allows transfers to be an atomic transaction. Only way to tell if a uref is a purse is to call get-balance and see if it errors.... Will need updates to purse documentation.
Stretch feature - remove 'zombie' purses: Existing purses have to be retained. COULD mark the purse for purging later - for example, add a field to mark when the purse was last used. zero balance purses that have not been used in a long while can be purged.
The text was updated successfully, but these errors were encountered:
History: inner (mint held) uref and outer uref (purse owner). Later created a new balance key variant (has an inner payload same as a uref). Purse is an outer key addr which points to an inner "unit" which has the same inner payload as a uref. Only the mint knows how to access this balance-tagged key. Now: managed via strong types. Use strong typing to separate "purse" from URefs.
The text was updated successfully, but these errors were encountered: