Crates.io | something-for-tests |
lib.rs | something-for-tests |
version | 0.1.0 |
source | src |
created_at | 2021-07-26 09:46:52.926421 |
updated_at | 2021-07-26 09:46:52.926421 |
description | for test |
homepage | |
repository | |
max_upload_size | |
id | 427353 |
size | 113,857 |
This version of the cw20 base contract is compatible with legacy contract running on Terra chain Columbus-4.
This is a basic implementation of a cw20 contract. It implements the CW20 spec and is designed to be deployed as is, or imported into other contracts to easily build cw20-compatible tokens with custom logic.
Implements:
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/cw20_base.wasm .
ls -l cw20_base.wasm
sha256sum cw20_base.wasm
Or for a production-ready (optimized) build, run a build command in the the repository root: https://github.com/CosmWasm/cosmwasm-plus#compiling.
You can also import much of the logic of this contract to build another ERC20-contract, such as a bonding curve, overiding or extending what you need.
Basically, you just need to write your handle function and import
cw20_base::contract::handle_transfer
, etc and dispatch to them.
This allows you to use custom ExecuteMsg
and QueryMsg
with your additional
calls, but then use the underlying implementation for the standard cw20
messages you want to support. The same with QueryMsg
. You could reuse instantiate
as it, but it is likely you will want to change it. And it is rather simple.
Look at cw20-staking
for an example of how to "inherit"
all this token functionality and combine it with custom logic.