feat!: remove CW4626

Cargo.toml

@@ -19,7 +19,6 @@ schemars                        = "0.8.11"
 serde                           = { version = "1.0.152", default-features = false, features = ["derive"] }
 cosmwasm-schema                 = "1.2.1"
 cw-utils                        = { version = "1.0.1" }
-cw20                            = { version = "1.0.1" }
 cw-storage-plus                 = "1.1.0"
 cw2                             = "1.1.0"
 mars-owner                      = "2.0.0"

README.md

@@ -46,7 +46,6 @@ The following extensions are included in this repo:
 * [Lockup](src/extensions/lockup.rs)
 * [ForceUnlock](src/extensions/force_unlock.rs)
 * [Keeper](src/extensions/keeper.rs)
-* [Cw4626](src/extensions/cw4626.rs)
 
 Each of these extensions are available in this repo via cargo features. To use them, you can import the crate with a feature flag like this:
 
@@ -65,9 +64,6 @@ The force unlock extension can be used to create a vault that also implements th
 ### Keeper
 The keeper extension can be used to add functionality for either whitelisted addresses or anyone to act as a "keeper" for the vault and call functions to perform jobs that need to be done to keep the vault running.
 
-### Cw4626
-The Cw4626 extension is the only extension provided with in this repo that does not extend the standard `VaultStandardExecuteMsg` and `VaultStandardQueryMsg` enums by putting its variants inside of a `VaultExtension` variant. Instead it adds more variants at the top level, namely the variants from the [CW20 standard](https://github.com/CosmWasm/cw-plus/tree/main/packages/cw20) This is inspired by the [ERC-4626 standard on Ethereum](https://ethereum.org/en/developers/docs/standards/tokens/erc-4626/) and allows the vault to, instead of using a Cosmos native token as the vault token, have the vault contract be it's own vault token by also implementing the CW20 standard. This is useful if you are writing a vault on a chain that does not yet have the [TokenFactory module](https://github.com/CosmWasm/token-factory) available and can therefore not issue a Cosmos native token as the vault token.
-
 
 ## Test Helpers
 

cw-vault-standard/Cargo.toml

@@ -15,7 +15,6 @@ default         = []
 lockup          = ["cw-utils"]
 force-unlock    = []
 keeper          = []
-cw4626          = ["cw20"]
 
 [package.metadata.docs.rs]
 all-features    = true
@@ -27,4 +26,3 @@ schemars        = { workspace = true }
 serde           = { workspace = true }
 cosmwasm-schema = { workspace = true }
 cw-utils        = { workspace = true, optional = true }
-cw20            = { workspace = true, optional = true }

cw-vault-standard/src/extensions/mod.rs

@@ -24,20 +24,3 @@ pub mod force_unlock;
 #[cfg(feature = "keeper")]
 #[cfg_attr(docsrs, doc(cfg(feature = "keeper")))]
 pub mod keeper;
-
-/// The Cw4626 extension is the only extension provided with in this repo that
-/// does not extend the standard `ExecuteMsg` and `QueryMsg` enums with by
-/// putting its variants inside of a `VaultExtension` variant. Instead it adds
-/// more variants at the top level, namely the variants from the [CW20
-/// standard](https://github.com/CosmWasm/cw-plus/tree/main/packages/cw20) This
-/// is inspired by the [ERC-4626 standard on
-/// Ethereum](https://ethereum.org/en/developers/docs/standards/tokens/erc-4626/)
-/// and allows the vault to, instead of using a Cosmos native token as the vault
-/// token, have the vault contract be it's own vault token by also implementing
-/// the CW20 standard. This is useful if you are writing a vault on a chain that
-/// does not yet have the [TokenFactory
-/// module](https://github.com/CosmWasm/token-factory) available and can
-/// therefore not issue a Cosmos native token as the vault token.
-#[cfg(feature = "cw4626")]
-#[cfg_attr(docsrs, doc(cfg(feature = "cw4626")))]
-pub mod cw4626;

cw-vault-standard/src/lib.rs

@@ -99,22 +99,6 @@
 //! The keeper extension can be used to add functionality for either whitelisted
 //! addresses or anyone to act as a "keeper" for the vault and call functions to
 //! perform jobs that need to be done to keep the vault running.
-//!
-//! ### Cw4626
-//! The Cw4626 extension is the only extension provided with in this repo that
-//! does not extend the default [`VaultStandardExecuteMsg`] and
-//! [`VaultStandardQueryMsg`] enums by putting its variants inside of the
-//! [`VaultStandardExecuteMsg::VaultExtension`] variant. Instead it adds more
-//! variants at the top level, namely the variants from the [CW20
-//! standard](https://github.com/CosmWasm/cw-plus/tree/main/packages/cw20). This
-//! is inspired by the [ERC-4626 standard on
-//! Ethereum](https://ethereum.org/en/developers/docs/standards/tokens/erc-4626/)
-//! and allows the vault to, instead of using a Cosmos native token as the vault
-//! token, have the vault contract be it's own vault token by also implementing
-//! the CW20 standard. This is useful if you are writing a vault on a chain that
-//! does not yet have the [TokenFactory
-//! module](https://github.com/CosmWasm/token-factory) available and can
-//! therefore not issue a Cosmos native token as the vault token.
 
 /// Module containing some pre-defined vault standard extensions.
 pub mod extensions;