Collection of awesome things related to CosmWasm smart contracts.
Please read the contribution guidelines if you want to contribute.
- General Resources
- CosmWasm Framework
- Smart Contract Libraries
- Smart Contracts
- External Projects
- Tooling
- dApps
- The CosmWasm book - a step-by-step guide to writing CosmWasm smart contracts.
- CosmWasm framework - a "core" CosmWasm repo. This includes the core Rust framework for writing a smart contract, a virtual machine that runs smart contracts and is embedded in any chain running them, the IDL format for describing the interface of a smart contract, and more! A few of these are commonly dependencies of smart contracts.
- CosmWasm template - a template for getting an empty smart contract up and running quickly. Instructions included!
- cosmwasm-std (repo): The standard library for building CosmWasm smart contracts. Code in this package is compiled into the smart contract.
- cw-storage-plus (repo): Helper methods to reduce boilerplate for storing data types. Easier and more secure persistence layer.
- cosmwasm-schema
(repo): A
dependency for CosmWasm contracts to generate the IDL (interface description)
files. These are consumed e.g. by
ts-codegento automagically get a TypeScript client for your contract. - cw-multi-test (repo):
- cw-utils
(repo): A collection of (somewhat
random) helpers we found useful when developing
cw-pluscontracts and specs. Available as a library at crates.io! - cw-coins (repo): A helper for managing multiple coins in a smart contract.
- cw-item-set
(repo): A
HashSetequivalent (set of unique items) that can be stored in smart contract storage.
Before you create a PR to add your contract here, read the
publishing guidelines
and make sure you complete them all, specifically adding an OSI-approved license
and checking in valid artifacts for the build (contract.wasm,
schema/*.json).
We do validate the artifacts and perform a basic code review of contracts included in this list. However, nothing terribly comprehensive and inclusion here should not be taken in lieu of a proper audit. We do provide some guidelines on sharing code reviews in a decentralized manner which can be used as the basis for a peer-reviewed audit.
The cw-plus repo houses both
protocol specifications and their reference implementations. These
implementations are meant both as examples of production-ready contracts and
pieces you might like to use in your project as they are.
- cw1 - proxy contracts that are meant to forward a message (probably after checking the sender against some form of access control), this time with the contract as the sender.
- cw2 - contract metadata (name and version) that can be inspected directly, without querying the contract.
- cw3 - multisig and voting.
- cw4 - group membership management with weights.
- cw20 - fungible token.
- cw1-whitelist by ethanfrey: This may be the simplest implementation of cw1, a whitelist of addresses. It contains a set of admins that are defined upon creation. Any of those admins may Execute any message via the contract, per the CW1 spec.
- cw1-subkeys by ethanfrey: 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.
- cw3-fixed-multisig: This is a simple implementation of the cw3 spec. It is a multisig with a fixed set of addresses created upon initialization. Each address may have the same weight (K of N) or some may have extra voting power.
- cw3-flex-multisig: This builds on cw3-fixed-multisig with a more powerful implementation of the cw3 spec. It is a multisig contract that is backed by a cw4 (group) contract, which independently maintains the voter set.
- cw4-group: This is a basic implementation of the cw4 spec. It fulfills all elements of the spec, including the raw query lookups, and it designed to be used as a backing storage for cw3 compliant contracts.
- cw4-stake: This is a second implementation of the cw4 spec. It fufills all elements of the spec, including the raw query lookups, and it is designed to be used as a backing storage for cw3 compliant contracts.
- cw20-base by ethanfrey: Basic implementation of a cw20 contract. It implements the cw20 spec and is designed to be deloyed as is, or imported into other contracts to easily build cw20-compatible tokens with custom logic.
These contracts demonstrate best practices and learning references. Please do not use them in production as is. You are welcome to fork them, and independently review, refine and audit them, using them as a basis for your protocol. Or just as inspiration
- cw-tokens - a few other cw20 (fungible token) contracts.
- cw-nfts - non-fungible tokens. Official
repository for all work on NFT standards and reference contracts. This is
where the
cw721 speclives.
These projects/contracts are developed and maintained by CosmWasm community.
- DA0-DA0/dao-contracts - DAO DAO is the leading software to build your own DAO on CosmWasm chains, quickly surpassing Aragon in functionality
- mars-protocol/v1-core - Delphi's "Mars Protocol" is the leading lending protocol on Terra and soon launching on Osmosis
- public-awesome/launchpad - Stargaze provides contracts to easily create and manage new NFT collections.
- CronCats/cw-croncat - Croncat provides a general purpose, fully autonomous network that enables scheduled function calls for blockchain contract execution. It allows any application to schedule logic to get executed in the future, once or many times, triggered by an approved “agent,” in an economically stable format.
- cosmwasm/rust-optimizer - This is
a Docker build with a locked set of dependencies to produce reproducible
builds of cosmwasm smart contracts. It also does heavy optimization on the
build size, using binary stripping and
wasm-opt. - cosmology-tech/create-cosmos-app - set up a modern Cosmos app with one command, ready to be iterated on.
- mandrean/cw-optimizoor - A very
fast alternative to
rust-optimizerfor local development and testing. Written in Rust, no dependency on Docker. - cosmwasm devtools (repo) - A web-based console for interacting with CosmWasm smart contracts deployed locally or remotely. Can use Keplr account or generate new addresses as needed.
- cosmwasm/ts-codegen - Convert your CosmWasm smart contracts into dev-friendly TypeScript classes so you can focus on shipping code.
- Terran-One/cosmwasm-vm-js - A JavaScript runtime for running CosmWasm contracts in Node.js or the browser.
- CWSimulate - An online playground / simulation environment for interacting with CosmWasm contract binaries without a blockchain. Can be used for execution visualization / interactive debugging with time-traveling navigation.
- cosmy-wasmy - A vscode extension to interact with CosmWasm smart contracts on devnet or testnet chains. Allows to query, execute, upload contracts as well as provide code completion snippets.
- cosmwander - Explore on-chain cosmwasm contracts and discover their message scheme.
- WELLDONE Code - Remix IDE plugin that supports CosmWasm. It is a web-based IDE that allows developers to deploy smart contracts and execute functions through a browser wallet. It supports its own compiler server, so developers do not need to set up a development environment.
- Cosmwasm Studio - Monaco IDE that supports CosmWasm. It allows developers to code, build smart contracts and execute functions through a simulation. It supports its own rust-analyzer in Web Assembly so developers can code it the same as local VS Code.
- cosmwasm-tools - A super
fast and cross-platform alternative to
rust-optimizerthat produces optimized wasm files. Written in Typescript, supporting watch mode, parallel builds, and ts-codegen sharing common dependencies. - beaker - A toolkit that simplifies interactions with CosmWasm smart contracts which offers scaffolding, deployment, upgrades, execution, querying, an interactive console, and task scripting capabilities.
Looking for dApps to feature. See #19.