#native #tokens #contract #proxy #cw1 #set #subkeys

bin+lib abstract-cw1-subkeys

Implement subkeys for authorizing native tokens as a cw1 proxy contract

6 releases (stable)

new 3.0.0 Jul 11, 2024
2.0.1 Jun 17, 2024
2.0.0 May 1, 2024
2.0.0-rc Apr 25, 2024
1.2.2 Jan 24, 2024

#255 in Magic Beans

Download history 567/week @ 2024-03-14 412/week @ 2024-03-21 496/week @ 2024-03-28 435/week @ 2024-04-04 800/week @ 2024-04-11 507/week @ 2024-04-18 982/week @ 2024-04-25 663/week @ 2024-05-02 381/week @ 2024-05-09 516/week @ 2024-05-16 799/week @ 2024-05-23 502/week @ 2024-05-30 1026/week @ 2024-06-06 877/week @ 2024-06-13 784/week @ 2024-06-20 484/week @ 2024-06-27

3,210 downloads per month
Used in 2 crates (via abstract-cw-plus-interfac…)

Apache-2.0 and GPL-3.0-only

135KB
3K SLoC

CW1 Subkeys

This builds on cw1-whitelist to provide the first non-trivial solution. It still works like cw1-whitelist with a set of admins (typically 1) which have full control of the account. However, you can then grant a number of accounts allowances to send native tokens from this account.

This was proposed in Summer 2019 for the Cosmos Hub and resembles the functionality of ERC20 (allowances and transfer from).

Details

Basically, any admin can add an allowance for a (spender, denom) pair (similar to cw20 IncreaseAllowance / DecreaseAllowance). Any non-admin account can try to execute a CosmosMsg::Bank(BankMsg::Send{}) from this contract and if they have the required allowances, their allowance will be reduced and the send message relayed. If they don't have sufficient authorization, or if they try to proxy any other message type, then the attempt will be rejected. Admin can give permissions to subkeys to relay specific types of messages (covers Delegate, Undelegate, Redelegate, Withdraw for now). Subkeys have no permission on creation, it can be setup with SetupPermission message.

Messages

This adds 2 messages beyond the cw1 spec:

enum ExecuteMsg {
    IncreaseAllowance {
        spender: HumanAddr,
        denom: String,
        amount: Uint128,
        expires: Option<Expiration>,
    },
    DecreaseAllowance {
        spender: HumanAddr,
        denom: String,
        amount: Uint128,
        expires: Option<Expiration>,
    },
    SetupPermissions {
        spender: HumanAddr,
        permissions: Permissions,
    }
}

Queries

It also adds one more query type:

enum QueryMsg {
    Allowance {
        spender: HumanAddr,
    },
    AllAllowances {
        start_after: Option<HumanAddr>,
        limit: Option<u32>,
    },
}

pub struct AllowanceInfo {
    pub spender: HumanAddr,
    pub balance: Balance,
    pub expires: Expiration,
    pub permissions: Permissions,
}

pub struct AllAllowancesResponse {
    pub allowances: Vec<AllowanceInfo>,
}

Running this contract

You will need Rust 1.44.1+ with wasm32-unknown-unknown target installed.

You can run unit tests on this via:

cargo test

Once you are happy with the content, you can compile it to wasm via:

RUSTFLAGS='-C link-arg=-s' cargo wasm
cp ../../target/wasm32-unknown-unknown/release/cw1_subkeys.wasm .
ls -l cw1_subkeys.wasm
sha256sum cw1_subkeys.wasm

Or for a production-ready (optimized) build, run a build command in the the repository root: https://github.com/CosmWasm/cw-plus#compiling.

Dependencies

~4–17MB
~196K SLoC