#cosmwasm #cosmos #string #address #marks #addr #query-response

cw-address-like

A trait that marks unchecked or checked CosmWasm address strings

6 stable releases

2.0.0 Aug 12, 2024
1.0.4 Feb 28, 2023
1.0.3 Jan 11, 2023
1.0.1 Dec 6, 2022
1.0.0 Nov 27, 2022

#2 in #addr

Download history 2730/week @ 2024-06-17 2363/week @ 2024-06-24 1738/week @ 2024-07-01 1850/week @ 2024-07-08 2474/week @ 2024-07-15 1965/week @ 2024-07-22 2060/week @ 2024-07-29 2225/week @ 2024-08-05 2884/week @ 2024-08-12 1936/week @ 2024-08-19 2159/week @ 2024-08-26 2361/week @ 2024-09-02 1929/week @ 2024-09-09 2203/week @ 2024-09-16 2198/week @ 2024-09-23 1950/week @ 2024-09-30

8,529 downloads per month
Used in 142 crates (14 directly)

Apache-2.0

5KB

CW Address Like

This crate provides an trait AddressLike, which marks types that can be used as addresses in CosmWasm, namely String and cosmwasm_std::Addr.

Background

In CosmWasm, there are two types that are typically used to represent addresses:

  • String - Represents an unverified address, which are used in contract APIs, i.e. messages and query responses.
  • cosmwasm_std::Addr - Represents an verified address, used in contract internal logics.

When a contract receives an address (as a String) from a message, it must not simply assume it is valid. Instead, it should use the deps.api.addr_validate method to verify it, which returns an Addr. The contract can then use the Addr in its business logics or save it in storage.

Similarly, the contract should also converts Addrs back to Strings when returning them in query responses.

The problem

A problem arises when we want to define a struct or enum that is to be used in both the API and internal logics. For example, consider a contract that saves a "config" in its storage, which uses an Addr inside to represent the address of the contract's owner, while also providing a query method for the config, which uses a String.

In such cases, developers may either define two types, one for each case:

struct Config {
    pub owner: Addr,
}

struct ConfigResponse {
    pub owner: String,
}

This approach works, but is somewhat cumbersome, especially when the config contains more fields.

Another approach is to define a single type that contains a generic:

struct Config<T> {
    pub owner: T,
}

Then use Config<String> in the API and Config<Addr> in internal logics.

The main drawback of this approach is there's no restriction on what T can be. It is theoretically possible to plug any type in as T here, not limited to String and Addr.

How to use

In this crate we provide an AddressLike trait, which is defined simply as:

pub trait AddressLike {}

impl AddressLike for Addr {}
impl AddressLike for String {}

The developer can then define their type as:

struct Config<T: AddressLike> {
    pub owner: T,
}

This restricts that only String and Addr can be used as T.

License

Contents of this crate at or prior to version 1.0.3 are published under GNU Affero General Public License v3 or later; contents after the said version are published under Apache-2.0 license.

Dependencies

~3.5–7MB
~142K SLoC