Optional
badgeThe badges to create. Newly created badges will be sent to the "Mint" address. Must have necessary permissions in future transactions to update. However, no restrictions in this genesis Msg. Only used if collection has "Standard" balance type.
Optional
badgeThe new badge metadata timeline. Must have the necessary permissions in future transactions to update. However, no restrictions in this genesis Msg. Note we take first-match only for badge IDs, so do not define duplicates.
Optional
balancesThe balances type. Either "Standard", "Off-Chain - Indexed", "Off-Chain - Non-Indexed" or "Non-Public"
Optional
collectionThe new collection approved transfers timeline. Must have the necessary permissions in future transactions to update. However, no restrictions in this genesis Msg.
The ID of the collection to update.
Optional
collectionThe new collection metadata timeline. Must have the necessary permissions in future transactions to update. However, no restrictions in this genesis Msg.
Optional
collectionThe new collection permissions. Must have the necessary permissions in future transactions to update. However, no restrictions in this genesis Msg.
The creator of the transaction.
Optional
customThe new custom data timeline. Must have the necessary permissions in future transactions to update. However, no restrictions in this genesis Msg.
Optional
defaultThe default balances for users who have not interacted with the collection yet. Only can be set on initial creation. Only used if collection has "Standard" balance type.
Optional
isThe new is archived timeline. Must have the necessary permissions in future transactions to update. However, no restrictions in this genesis Msg.
Optional
managerThe new manager timeline. Must have the necessary permissions in future transactions to update. However, no restrictions in this genesis Msg.
Optional
offThe new off-chain balances metadata timeline. Must have the necessary permissions in future transactions to update. However, no restrictions in this genesis Msg. Only used if "Off-Chain - Indexed" or "Off-Chain - Non-Indexed" balance type.
Optional
standardsThe new standards timeline. Must have the necessary permissions in future transactions to update. However, no restrictions in this genesis Msg.
Optional
updateWhether or not to update the badge metadata timeline.
Optional
updateWhether or not to update the collection approved transfers timeline.
Optional
updateWhether or not to update the collection metadata timeline.
Optional
updateWhether or not to update the collection permissions.
Optional
updateWhether or not to update the custom data timeline.
Optional
updateWhether or not to update the is archived timeline.
Optional
updateWhether or not to update the manager timeline.
Optional
updateWhether or not to update the off-chain balances metadata timeline.
Optional
updateWhether or not to update the standards timeline.
Deep copies the object and returns a new instance.
Converts the object to a different NumberType equivalent.
Optional
options: ConvertOptionsCompares this object's fields to another object's fields for equality. Equality is determined by comparing the JSON representations of the objects.
If normalizeNumberTypes
is true, then all number types will be compared as strings (i.e. "1n" === "1" === 1). Else, they will be compared as their native types (i.e. 1n !== 1 !== "1").
Optional
normalizeNumberTypes: booleanStatic
fromOptional
options: Partial<JsonReadOptions>Static
fromOptional
options: Partial<JsonReadOptions>Static
from
MsgUniversalUpdateCollection is a universal transaction that can be used to create / update any collection. It is only executable by the manager. MsgCreateCollection and MsgUpdateCollection are special cases of this message.
Upon initial creation, you can set the default approved outgoing transfers, default approved incoming transfers, default user permissions, and balances type. However, after that, they are final and ignored in subsequent MsgUniversalUpdateCollection calls.
For a new collection, specify collectionId == "0".
Note that you must have the necessary privileges to update specific fields. If you do not have the necessary privileges, it will throw an error. We update any CollectionPermissions at the end, so the permissions checked for the current execution are the permissions BEFORE the update. In the case of the first MsgUniversalUpdateCollection, the previous permissions are by default all permitted.
To specify you would like to update a field, the corresponding update field must be set to true. If it is set to false, we ignore it.