Major release v0.19: add `CollectionInfo`, `RoyaltyInfo`, updatable NFTs for creator, etc. #156

taitruong · 2024-02-27T13:48:25Z

Major refactoring for upcoming v0.19 release.

TL;DR: The cw721 v0.19 release sees a major refactor, introducing distinctions between Creator (manages collection metadata like royalties) and Minter (controls minting), and adds a new UpdateMetadata utility for onchain metadata. We've integrated a new CollectionMedata structure within the cw721 package, moving all core logic for easier access and implementation across contracts, thus streamlining contract architecture. This update simplifies the ecosystem by removing the need for separate cw721-metadata-onchain and cw2981-royalty contracts and clearly defining roles and functionalities.

Distinction between `Creator` and `Minter`

In previous release cw721 only knows minter (aka owner). Here we added Creator. Creator controls collection metadata (like royalties) whereas minter controls minting.

NEW utility: `UpdateNftInfo` and `UpdateCollectionMetadata` msg

By adding a new CollectionMetadataExtension store as an optional extension for CollectionMetadata (name and symbol), there is also logic introduced here for updating collection metadata.

Same logic is also applied now for updating onchain NFT metadata (after mint).

The creator is now able to do both: updating collection and onchain NFT metadata!

NEW `CollectionMedata` in `cw721` package

#[cw_serde]
pub struct CollectionMetadata<TCollectionMetadataExtension> {
    pub name: String,
    pub symbol: String,
    pub extension: TCollectionMetadataExtension,
    pub updated_at: Timestamp,
}

#[cw_serde]
pub struct CollectionMetadataExtension<TRoyaltyInfo> {
    pub description: String,
    pub image: String,
    pub external_link: Option<String>,
    pub explicit_content: Option<bool>,
    pub start_trading_time: Option<Timestamp>,
    pub royalty_info: Option<TRoyaltyInfo>,
}

#[cw_serde]
pub struct RoyaltyInfo {
    pub payment_address: Addr,
    pub share: Decimal,
}

For making it available to all existing contracts, I had to move all core logic into cw721 package. As a result, outcome is the following:

there are now default implementations for the Cw721Execute and Cw721Query traits
all structs like CollectionMetadata, NftMetadata, RoyaltyInfo, NftInfo, OwnerOfResponse, ApprovalResponse, ... moved to package

Another upgrade is adding creator along to existing minter address. In previous release due to the introduction of cw-ownable there has been a renaming of minter to ownership - which is confusing. With upcoming v0.19 release it looks like this:

minter can mint (formerly aka ownership in v0.17-18)
there is no more ownership (deprecated)
creator as part of collection metadata, can update collection metadata - including royalty
- NOTE: all props is owned by collection creator, except start_trading_time which belongs to minter
- creator and minter ownership is checked in new trait StateFactory
both, minter and creator, uses cw-ownable and can be transferred to another owner

all stores are in state.rs (pls note new Cw721Config which will be used for contracts):

/// Creator owns this contract and can update collection metadata!
/// !!! Important note here: !!!
/// - creator is stored using using cw-ownable's OWNERSHIP singleton, so it is not stored here
/// - in release v0.18.0 it was used for minter (which is confusing), but now it is used for creator
pub const CREATOR: OwnershipStore = OwnershipStore::new(OWNERSHIP_KEY);
/// - minter is stored in the contract storage using cw_ownable::OwnershipStore (same as for OWNERSHIP but with different key)
pub const MINTER: OwnershipStore = OwnershipStore::new("collection_minter");

/// Default CollectionMetadataExtension using `Option<CollectionMetadataExtension<RoyaltyInfo>>`
pub type DefaultOptionCollectionMetadataExtension =
    Option<CollectionMetadataExtension<RoyaltyInfo>>;
pub type DefaultOptionCollectionMetadataExtensionMsg =
    Option<CollectionMetadataExtensionMsg<RoyaltyInfoResponse>>;
/// Default NftMetadataExtension using `Option<NftMetadata>`.
pub type DefaultOptionNftMetadataExtension = Option<NftMetadata>;
pub type DefaultOptionNftMetadataExtensionMsg = Option<NftMetadataMsg>;

// explicit type for better distinction.
pub type NftMetadataMsg = NftMetadata;
#[deprecated(since = "0.19.0", note = "Please use `NftMetadata` instead")]
pub type MetaData = NftMetadata;
#[deprecated(
    since = "0.19.0",
    note = "Please use `CollectionMetadata<DefaultOptionCollectionMetadataExtension>` instead"
)]
pub type ContractInfoResponse = CollectionMetadata<DefaultOptionCollectionMetadataExtension>;

pub struct Cw721Config<
    'a,
    // Metadata defined in NftInfo (used for mint).
    TNftMetadataExtension,
    // Message passed for updating metadata.
    TNftMetadataExtensionMsg,
    // Extension defined in CollectionMetadata.
    TCollectionMetadataExtension,
    // Message passed for updating collection metadata extension.
    TCollectionMetadataExtensionMsg,
    // Defines for `CosmosMsg::Custom<T>` in response. Barely used, so `Empty` can be used.
    TCustomResponseMsg,
> where
    TNftMetadataExtension: Cw721State,
    TNftMetadataExtensionMsg: Cw721CustomMsg,
    TCollectionMetadataExtension: Cw721State,
    TCollectionMetadataExtensionMsg: Cw721CustomMsg,
{
    /// Note: replaces deprecated/legacy key "nft_info"!
    pub collection_metadata: Item<'a, CollectionMetadata<TCollectionMetadataExtension>>,
    pub token_count: Item<'a, u64>,
    /// Stored as (granter, operator) giving operator full control over granter's account.
    /// NOTE: granter is the owner, so operator has only control for NFTs owned by granter!
    pub operators: Map<'a, (&'a Addr, &'a Addr), Expiration>,
    pub nft_info: IndexedMap<
        'a,
        &'a str,
        NftInfo<TNftMetadataExtension>,
        TokenIndexes<'a, TNftMetadataExtension>,
    >,
    pub withdraw_address: Item<'a, String>,
...
}

Essentially all boilerplate code (default implementations in Cw721Execute and Cw721Query traits) are now in cw721 package.
As a result contracts are very slim. Please note, implementations by Cw721Config, along with Cw721Execute and
Cw721Query traits are opionated - though contracts may be implement differently by overriding default implementations.

Here is how new cw721-base looks like by using cw721 package:

Define struct for contract interaction:

pub struct Cw721Contract<
    'a,
    // Metadata defined in NftInfo (used for mint).
    TNftMetadataExtension,
    // Message passed for updating metadata.
    TNftMetadataExtensionMsg,
    // Extension defined in CollectionMetadata.
    TCollectionMetadataExtension,
    TCollectionMetadataExtensionMsg,
    // Defines for `CosmosMsg::Custom<T>` in response. Barely used, so `Empty` can be used.
    TCustomResponseMsg,
> where
    TNftMetadataExtension: Cw721State,
    TNftMetadataExtensionMsg: Cw721CustomMsg,
    TCollectionMetadataExtension: Cw721State,
    TCollectionMetadataExtensionMsg: Cw721CustomMsg,
{
    pub config: Cw721Config<
        'a,
        TNftMetadataExtension,
        TNftMetadataExtensionMsg,
        TCollectionMetadataExtension,
        TCollectionMetadataExtensionMsg,
        TCustomResponseMsg,
    >,
}

impl<
        TNftMetadataExtension,
        TNftMetadataExtensionMsg,
        TCollectionMetadataExtension,
        TCollectionMetadataExtensionMsg,
        TCustomResponseMsg,
    > Default
    for Cw721Contract<
        'static,
        TNftMetadataExtension,
        TNftMetadataExtensionMsg,
        TCollectionMetadataExtension,
        TCollectionMetadataExtensionMsg,
        TCustomResponseMsg,
    >
where
    TNftMetadataExtension: Cw721State,
    TNftMetadataExtensionMsg: Cw721CustomMsg,
    TCollectionMetadataExtension: Cw721State,
    TCollectionMetadataExtensionMsg: Cw721CustomMsg,
{
    fn default() -> Self {
        Self {
            config: Cw721Config::default(),
        }
    }
}

Then implement execute and query traits and using default implementations:

// implements Cw721Execute
impl<
        'a,
        TNftMetadataExtension,
        TNftMetadataExtensionMsg,
        TCollectionMetadataExtension,
        TCollectionMetadataExtensionMsg,
        TCustomResponseMsg,
    >
    Cw721Execute<
        TNftMetadataExtension,
        TNftMetadataExtensionMsg,
        TCollectionMetadataExtension,
        TCollectionMetadataExtensionMsg,
        TCustomResponseMsg,
    >
    for Cw721Contract<
        'a,
        TNftMetadataExtension,
        TNftMetadataExtensionMsg,
        TCollectionMetadataExtension,
        TCollectionMetadataExtensionMsg,
        TCustomResponseMsg,
    >
where
    TNftMetadataExtension: Cw721State,
    TNftMetadataExtensionMsg: Cw721CustomMsg + StateFactory<TNftMetadataExtension>,
    TCollectionMetadataExtension: Cw721State,
    TCollectionMetadataExtensionMsg: Cw721CustomMsg + StateFactory<TCollectionMetadataExtension>,
    TCustomResponseMsg: CustomMsg,
{
}

// implements Cw721Query
impl<
        'a,
        TNftMetadataExtension,
        TNftMetadataExtensionMsg,
        TCollectionMetadataExtension,
        TCollectionMetadataExtensionMsg,
        TCustomResponseMsg,
    > Cw721Query<TNftMetadataExtension, TCollectionMetadataExtension>
    for Cw721Contract<
        'a,
        TNftMetadataExtension,
        TNftMetadataExtensionMsg,
        TCollectionMetadataExtension,
        TCollectionMetadataExtensionMsg,
        TCustomResponseMsg,
    >
where
    TNftMetadataExtension: Cw721State,
    TNftMetadataExtensionMsg: Cw721CustomMsg,
    TCollectionMetadataExtension: Cw721State,
    TCollectionMetadataExtensionMsg: Cw721CustomMsg,
    TCustomResponseMsg: CustomMsg,
{
}

And finally in lib.rs:

    // This makes a conscious choice on the various generics used by the contract
    #[cfg_attr(not(feature = "library"), entry_point)]
    pub fn instantiate(
        deps: DepsMut,
        env: Env,
        info: MessageInfo,
        msg: Cw721InstantiateMsg<DefaultOptionCollectionMetadataExtensionMsg>,
    ) -> Result<Response, Cw721ContractError> {
        let contract = Cw721Contract::<
            DefaultOptionNftMetadataExtension,
            DefaultOptionNftMetadataExtensionMsg,
            DefaultOptionCollectionMetadataExtension,
            DefaultOptionCollectionMetadataExtensionMsg,
            Empty,
        >::default();
        contract.instantiate(deps, &env, &info, msg, CONTRACT_NAME, CONTRACT_VERSION)
    }

    #[cfg_attr(not(feature = "library"), entry_point)]
    pub fn execute(
        deps: DepsMut,
        env: Env,
        info: MessageInfo,
        msg: Cw721ExecuteMsg<
            DefaultOptionNftMetadataExtensionMsg,
            DefaultOptionCollectionMetadataExtensionMsg,
        >,
    ) -> Result<Response, Cw721ContractError> {
        let contract = Cw721Contract::<
            DefaultOptionNftMetadataExtension,
            DefaultOptionNftMetadataExtensionMsg,
            DefaultOptionCollectionMetadataExtension,
            DefaultOptionCollectionMetadataExtensionMsg,
            Empty,
        >::default();
        contract.execute(deps, &env, &info, msg)
    }

    #[cfg_attr(not(feature = "library"), entry_point)]
    pub fn query(
        deps: Deps,
        env: Env,
        msg: Cw721QueryMsg<
            DefaultOptionNftMetadataExtension,
            DefaultOptionCollectionMetadataExtension,
        >,
    ) -> StdResult<Binary> {
        let contract = Cw721Contract::<
            DefaultOptionNftMetadataExtension,
            DefaultOptionNftMetadataExtensionMsg,
            DefaultOptionCollectionMetadataExtension,
            DefaultOptionCollectionMetadataExtensionMsg,
            Empty,
        >::default();
        contract.query(deps, &env, msg)
    }

    #[cfg_attr(not(feature = "library"), entry_point)]
    pub fn migrate(
        deps: DepsMut,
        env: Env,
        msg: Cw721MigrateMsg,
    ) -> Result<Response, Cw721ContractError> {
        let contract = Cw721Contract::<
            DefaultOptionNftMetadataExtension,
            DefaultOptionNftMetadataExtensionMsg,
            DefaultOptionCollectionMetadataExtension,
            DefaultOptionCollectionMetadataExtensionMsg,
            Empty,
        >::default();
        contract.migrate(deps, env, msg, CONTRACT_NAME, CONTRACT_VERSION)
    }

That's it!

`cw721-metadata-onchain` and `cw2981-royalty` contracts removed

Another positive side effect of this refactoring is that there's no need for cw721-metadata-onchain and cw2981-royalty contracts anymore. This is covered in cw721-base. Design hasnt changed and onchain metadata is stored in NftInfo<TNftMetadataExtension>. Before this PR, funny thing is that in cw721-base it was defined as:

TMetadataExtension = Option<Empty>, allowing to NOT store onchain data, but it doesnt make sense having None and Some(Empty).

In cw721-metadata-onchain contract it was defined as:

TMetadataExtension = Option<Metadata>, here for onchain contract it was allowed to either provide onchain data or event not!

In this PR it defines a pub type DefaultOptionNftMetadataExtension = Option<NftMetadata> which is used in cw721-base. onchain contract is obsolete and is removed.

…CollectionInfo, ContractInfoResponse -> CollectionInfoResponse

…ration and keep legacy data for backward migration

- new query GetMinterOwnership and GetCreatorOwnership, deprecated Ownership - new execute UpdateMinterOwnership and UpdateCreatorOwnership, deprecate UpdateOwnership - dedicated stores for minter and creator, where creator usess by default cw_ownable singleton! - new migrate msg allowing to reset creator and minter - cleanup migration and split legacy part to dedicated functions - also make sure using decicated CREATOR and MINTER stores and NOT use cw_ownable::...

- move logic from cw721-base to cw721 - merge cw721-base and cw721-metadata-onchain into one, distinction is: `extension: T` where T for base contract is `type DefaultMetadataExtension = Option<Metadata>` - all logic now in default implementation for traits Cw721Execute and Cw721Query

taitruong · 2024-03-07T22:51:43Z

packages/cw721/src/query.rs

+            #[allow(deprecated)]
+            Cw721QueryMsg::ContractInfo {} => {
+                to_json_binary(&self.query_collection_info(deps, env)?)
+            }
+            Cw721QueryMsg::GetCollectionInfo {} => {
+                to_json_binary(&self.query_collection_info(deps, env)?)
+            }
+            Cw721QueryMsg::NftInfo { token_id } => {


Also ContractInfo is deprecated and is replaced by GetCollectionInfo. In next release all deprecated msgs should be removed. Here it is kept for backward compatibility, so existing frontends wont break!

taitruong · 2024-03-07T22:54:05Z

packages/cw721/src/msg.rs

+    #[deprecated(since = "0.19.0", note = "Please use GetMinterOwnership instead")]
+    #[returns(Ownership<Addr>)]
+    Ownership {},
+
+    #[returns(Ownership<Addr>)]
+    GetMinterOwnership {},
+
+    #[returns(Ownership<Addr>)]
+    GetCreatorOwnership {},


Ownership -> GetMinterOwnership
new GetCreatorOwnership

Comments on these queries would be helpful. Good to note what they are in plain English and that minter will soon be deprecated.

Done: https://github.com/CosmWasm/cw-nfts/pull/156/files#r1521680742

taitruong · 2024-03-07T22:55:01Z

packages/cw721/src/msg.rs

+    #[deprecated(since = "0.19.0", note = "Please use GetMinterOwnership instead")]
+    #[returns(MinterResponse)]
+    Minter {},


Also for backward compatibility: Minter -> GetMinterOwnership

taitruong · 2024-03-07T22:55:58Z

packages/cw721/src/msg.rs

+pub enum Cw721MigrateMsg {
+    WithUpdate {
+        minter: Option<String>,
+        creator: Option<String>,
+    },
+}


Important: new migrate msg allowing to reset creator and minter!

taitruong · 2024-03-07T23:02:27Z

packages/cw721/src/traits.rs

-pub trait Cw721Execute<T, C>
-where
-    T: Serialize + DeserializeOwned + Clone,
-    C: CustomMsg,
-{
-    type Err: ToString;
-
-    fn transfer_nft(
-        &self,
-        deps: DepsMut,
-        env: Env,
-        info: MessageInfo,
-        recipient: String,
-        token_id: String,
-    ) -> Result<Response<C>, Self::Err>;


Before it e.g. Cw721Execute was rather an interface with no logic. Also note confusing generics naming like in Cw721Execute<T, C> and ...

taitruong · 2024-03-07T23:11:52Z

packages/cw721/src/state.rs

+pub const CREATOR: OwnershipStore = OwnershipStore::new(OWNERSHIP_KEY);
+/// - minter is stored in the contract storage using cw_ownable::OwnershipStore (same as for OWNERSHIP but with different key)
+pub const MINTER: OwnershipStore = OwnershipStore::new("collection_minter");
+


CREATOR and MINTER. Please note that singleton ownership was used before for minter, but now used for creator! new minter ownership has a new key collection_minter. This is also covered in migration (as shown later below).

Okay so to be clear, we now have an optional second owner which is creator. The max number of owners in the contract would now be 2 and not more than that right?

Okay so to be clear, we now have an optional second owner which is creator. The max number of owners in the contract would now be 2 and not more than that right?

Correct. They are both optional: creator and minter. Naming convention before was very confusing - started with the introduction of cw-ownable. There it was minter = owner = ownership.

Imo, using terms creator and minter is much more clear. Ownership appears here only in terms of minter ownership and creator ownership. Both uses for 2-step for transfer as defined by cw-ownable:

Owner transfers to new owner

New owner accepts, on acceptance minter/creator ownership is changed

taitruong · 2024-03-07T23:27:26Z

packages/cw721/src/execute.rs

+/// Migrates only in case ownership is not present
+/// !!! Important note here: !!!
+/// - creator owns the contract and can update collection info
+/// - minter can mint new tokens
+///
+/// Before v0.19.0 there were confusing naming conventions:
+/// - v0.17.0: minter was replaced by cw_ownable, as a result minter is owner
+/// - v0.16.0 and below: minter was stored in dedicated `minter` store (so NOT using cw_ownable at all)
+pub fn migrate_legacy_minter_and_creator(


migrate_legacy_minter_and_creator: migrate legacy minter and set new creator...

@humanalgorithm here is the most important part, allowing to migrate any older version to the latest

packages/cw721/src/execute.rs

contracts/cw721-base/src/lib.rs

taitruong · 2024-03-07T23:44:09Z

contracts/cw721-base/src/upgrades/v0_17.rs

-pub fn migrate<T, C, E, Q>(deps: DepsMut) -> Result<Response<C>, ContractError>
-where
-    T: Serialize + DeserializeOwned + Clone,
-    Q: CustomMsg,
-    E: CustomMsg,
-{
-    // remove old minter info
-    let tract16 = v16::Cw721Contract::<T, C, E, Q>::default();
-    let minter = tract16.minter.load(deps.storage)?;
-    tract16.minter.remove(deps.storage);
-
-    // save new ownership info
-    let ownership = cw_ownable::initialize_owner(deps.storage, deps.api, Some(minter.as_str()))?;


Also this old migrato logic of minter to ownership is error prone. Like it is e.g. possible to migrate from v0.16 to v0.18. Then minter is transferred to new addr. Keep in mind in old minter store there is still old addr. So migrating back to v0.16 and to v0.18 again, would reset minter addy. Better to always check whether new minter ownship is set - if so no migration needed.

This is an edge case, but still not good.

We needed this for migration to v.01.7. I think I might have been the one that "wrote" it but I was just copying migration logic from cw base contract.

contracts/cw721-base/Cargo.toml

…ts-codegen

taitruong added 5 commits February 27, 2024 12:23

rename states: tokens -> nft_info, contract_info -> collection_info

2c684b8

renamed structs and deprecate: TokenInfo -> NftInfo, ContractInfo -> …

c3dc54c

…CollectionInfo, ContractInfoResponse -> CollectionInfoResponse

cargo schema

98b7300

change storage keys for collection info and nft info, consider in mig…

5fd2f3b

…ration and keep legacy data for backward migration

use PA repo for cw-ownable

a2b5c12

taitruong force-pushed the collection-info branch from afaa196 to a2b5c12 Compare February 28, 2024 21:12

taitruong added 9 commits February 29, 2024 13:25

rename generics and make more readable

b2f73a0

CollectionInfoResponse -> CollectionInfo

d46d2b7

add CollectionInfoExtension with RoyaltyInfo

3d101cb

cargo schema

ddc3758

typo

18dd4d3

cleanup

917103c

rename

b3aac9e

cargo schema

8d61f85

cleanup

89da1ab

taitruong force-pushed the collection-info branch from 5fe10c0 to 89da1ab Compare March 3, 2024 19:01

taitruong added 3 commits March 4, 2024 14:50

fix ci

895f462

taitruong force-pushed the collection-info branch from 0494810 to 895f462 Compare March 7, 2024 20:12

taitruong added 5 commits March 7, 2024 21:13

cargo fmt

920a7d4

cargo fmt + clippy

641ede9

cargo fmt

0e27df8

cargo schema

8d91900

cargo clippy

9010cac

taitruong commented Mar 7, 2024

View reviewed changes

taitruong changed the title ~~WIP - Collection info~~ Add new CollectionInfo, including RoyaltyInfo and creator (along with existing minter). Mar 7, 2024

taitruong added 2 commits March 8, 2024 08:51

undo: do not rename token keys

bebe8b2

fix unit test

3d77652

taitruong commented Mar 8, 2024

View reviewed changes

contracts/cw721-base/Cargo.toml Show resolved Hide resolved

taitruong added 25 commits April 30, 2024 14:12

store royalty info as binary directly

0a085a7

move to contract

a4254b2

docs

abd1b3f

docs

b5801ea

rename

eb08455

Explicit type equivalent to Vec<Attribute>, for better distinction.

6ddf2c5

cleanup

ef1ab7b

add GetAllInfo and GetCollectionExtensionAttributes

0bc7a24

new TExtensionQueryMsg as a distinction for TNftExtension

0e1bbe9

cargo schema

c07cb42

cleanup

8d47685

new TExtensionMsg as a distinction for TNftExtensionMsg

2e32d1c

cargo schema

8581012

rate limit query

934573a

cargo schema

7d549f7

use ok_or_else()

486176f

cargo fmt

8555469

clippy

c1f5bb2

docs

acb1184

cleanup

e81d4fe

typo

8afb7b6

allow setting to None for token uri and optional props in NftExtension

e7a10c5

cargo schema

e6d8f90

cargo clippy

b62eee5

cleanup docs

11f3231

taitruong force-pushed the collection-info branch from ccf4784 to 11f3231 Compare April 30, 2024 12:12

cleanup

d460005

taitruong mentioned this pull request May 6, 2024

Cleanup cw2981-royalties #158

Closed

taitruong added 2 commits May 14, 2024 22:41

make public for re-use

82241f2

rename Extension -> GetExtension, otherwise there's name clash using …

c4801c3

…ts-codegen

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Major release v0.19: add `CollectionInfo`, `RoyaltyInfo`, updatable NFTs for creator, etc. #156

Major release v0.19: add `CollectionInfo`, `RoyaltyInfo`, updatable NFTs for creator, etc. #156

taitruong commented Feb 27, 2024 •

edited

taitruong Mar 7, 2024

taitruong Mar 7, 2024

JakeHartnell Mar 11, 2024

taitruong Mar 12, 2024

taitruong Mar 7, 2024

taitruong Mar 7, 2024

taitruong Mar 7, 2024

taitruong Mar 7, 2024

humanalgorithm Mar 8, 2024

taitruong Mar 9, 2024

taitruong Mar 7, 2024

taitruong Mar 9, 2024

taitruong Mar 7, 2024

humanalgorithm Mar 8, 2024

Major release v0.19: add CollectionInfo, RoyaltyInfo, updatable NFTs for creator, etc. #156

Are you sure you want to change the base?

Major release v0.19: add CollectionInfo, RoyaltyInfo, updatable NFTs for creator, etc. #156

Conversation

taitruong commented Feb 27, 2024 • edited

Major refactoring for upcoming v0.19 release.

Distinction between Creator and Minter

NEW utility: UpdateNftInfo and UpdateCollectionMetadata msg

NEW CollectionMedata in cw721 package

cw721-metadata-onchain and cw2981-royalty contracts removed

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Major release v0.19: add `CollectionInfo`, `RoyaltyInfo`, updatable NFTs for creator, etc. #156

Major release v0.19: add `CollectionInfo`, `RoyaltyInfo`, updatable NFTs for creator, etc. #156

taitruong commented Feb 27, 2024 •

edited

Distinction between `Creator` and `Minter`

NEW utility: `UpdateNftInfo` and `UpdateCollectionMetadata` msg

NEW `CollectionMedata` in `cw721` package

`cw721-metadata-onchain` and `cw2981-royalty` contracts removed