Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/abstractsdk/cw-orchestrator
All-in-one Rust-based CosmWasm testing, scripting, and deployment tool.
https://github.com/abstractsdk/cw-orchestrator
blockchain cosmwasm deployment-automation rust scripting smart-contracts
Last synced: 12 days ago
JSON representation
All-in-one Rust-based CosmWasm testing, scripting, and deployment tool.
- Host: GitHub
- URL: https://github.com/abstractsdk/cw-orchestrator
- Owner: AbstractSDK
- License: gpl-3.0
- Created: 2022-09-11T14:12:10.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2024-10-29T16:11:11.000Z (15 days ago)
- Last Synced: 2024-10-29T21:45:20.922Z (14 days ago)
- Topics: blockchain, cosmwasm, deployment-automation, rust, scripting, smart-contracts
- Language: Rust
- Homepage: https://orchestrator.abstract.money
- Size: 7.3 MB
- Stars: 79
- Watchers: 4
- Forks: 18
- Open Issues: 17
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
Awesome Lists containing this project
README
# cw-orchestrator
A Rust tool for interacting with [CosmWasm](https://cosmwasm.com/) smart contracts. It provides a type-safe interface to CosmWasm contracts and allows you to easily interact with them. It does this by providing a set of macros that generate type-safe interfaces to your contracts. You can then combine your contract interfaces into a single object that can be shared with others to ease integration efforts and encourage collaboration.
The documentation here gives you a brief overview of the functionality that cw-orchestrator provides. We provide more documentation at [orchestrator.abstract.money](https://orchestrator.abstract.money).
> Versions >= 0.25.0 are compatible with CosmWasm 2.x. For more information on migrating from CosmWasm 1.x to 2.x, see the [MIGRATING.md](./MIGRATING.md) file.
## How it works
Interacting with a [CosmWasm](https://cosmwasm.com/) contract involves calling the contract's endpoints using the appropriate message for that endpoint (`ExecuteMsg`,`InstantiateMsg`, `QueryMsg`, `MigrateMsg`, etc.). cw-orchestrator generates typed interfaces for your contracts, allowing them to be type-checked at compile time. This generic interface then allows you to write environment-generic code, meaning that you can re-use the code that you write to deploy your application to `cw-multi-test` when deploying to test/mainnet.
## Maintained Interfaces
We maintain a small set of interfaces ourselves that we use in our own projects. These interfaces are maintained by the Abstract team and are a good reference for how to use the library.
| Codebase | Latest Version |
|---|---|
| [cw-plus](https://github.com/AbstractSDK/cw-orchestrator/tree/main/packages/integrations/cw-plus) | 
|
| [abstract](https://github.com/AbstractSDK/abstract/tree/main/framework/packages/abstract-interface) | 
|
## Creating an Interface
In order to generate a typed interface to your contract you can pass the contract's message types into the `cw_orch::interface` macro.
### The `interface` Macro
Provide your messages to a new struct that's named after your contract.
```rust,ignore
use cw_orch::interface;
use cw20_base::msg::{InstantiateMsg, ExecuteMsg, QueryMsg, MigrateMsg};
// Provide the messages in the order Init, Exec, Query, Migrate.
#[interface(InstantiateMsg, ExecuteMsg, QueryMsg, MigrateMsg)]
pub struct Cw20;
```
The macro will generate a `new` function that takes the contract name and the chain that you want to interact with. You can then use this interface to interact with the contract.
### Usage
You can use this interface to deploy and interact with the contract:
```rust,ignore
use cw_orch::interface;
use cw_orch::prelude::*;
use cw20::{Cw20Coin, BalanceResponse};
// Implement the Uploadable trait so it can be uploaded to the mock.
impl Uploadable for Cw20 {
fn wrapper() -> Box> {
Box::new(
ContractWrapper::new_with_empty(
cw20_base::contract::execute,
cw20_base::contract::instantiate,
cw20_base::contract::query,
)
.with_migrate(cw20_base::contract::migrate),
)
}
}
fn example_test() {
let sender = Addr::unchecked("sender");
// Create a new mock chain (backed by cw-multi-test)
let chain = Mock::new(&sender);
// Create a new Cw20 interface
let cw20_base: Cw20 = Cw20::new("my_token", chain);
// Upload the contract
cw20_base.upload().unwrap();
// Instantiate a CW20 token
let cw20_init_msg = InstantiateMsg {
decimals: 6,
name: "Test Token".to_string(),
initial_balances: vec![Cw20Coin {
address: sender.to_string(),
amount: 10u128.into(),
}],
marketing: None,
mint: None,
symbol: "TEST".to_string(),
};
cw20_base.instantiate(&cw20_init_msg, None, None).unwrap();
// Query the balance
let balance: BalanceResponse = cw20_base.query(&QueryMsg::Balance { address: sender.to_string() }).unwrap();
assert_eq!(balance.balance.u128(), 10u128);
}
```
## Features
`cw-orchestrator` provides two additional macros that can be used to improve the scripting experience.
### ExecuteFns
The `ExecuteFns` macro can be added to the `ExecuteMsg` definition of your contract. It will generate a trait that allows you to call the variants of the message directly without the need to construct the struct yourself.
The `ExecuteFns` macro will only be applied on the Msg when compiled for non-wasm target.
```rust,ignore
use cw_orch::prelude::*;
#[cosmwasm_schema::cw_serde]
#[derive(cw_orch::ExecuteFns)]
pub enum ExecuteMsg {
Freeze {},
UpdateAdmins { admins: Vec },
/// the `payable` attribute can be used to add a `coins` argument to the generated function.
#[cw_orch(payable)]
Deposit {}
}
```
The generated functions can then be used for any interface that uses this `ExecuteMsg`.
```rust,ignore
// Define the interface, which is generic over the CosmWasm environment (Chain)
#[cw_orch::interface(Empty,ExecuteMsg,Empty,Empty)]
struct Cw1;
impl Cw1 {
pub fn test_macro(&self) {
// Enjoy the nice API!
self.freeze().unwrap();
self.update_admins(vec!["new_admin".to_string()]).unwrap();
self.deposit(&[Coin::new(13,"juno")]).unwrap();
}
}
```
### QueryFns
The `QueryFns` derive macro works in the same way as the `ExecuteFns` macro but it also uses the `#[returns(QueryResponse)]` attribute from `cosmwasm-schema` to generate the queries with the correct response types.
### Nested types
For nested messages (execute and query), you just need to derive `ExecuteFns` or `QueryFns` on the underlying structures. In general, every structure that implements the `Into` trait for the contract message will make the function available on the contract. To make that clearer, her's an example:
```rust,ignore
use cw_orch::interface;
use cw_orch::prelude::*;
// An execute message that is generic.
#[cosmwasm_schema::cw_serde]
pub enum GenericExecuteMsg {
Generic(T),
}
// A type that will fill the generic.
#[cosmwasm_schema::cw_serde]
#[derive(cw_orch::ExecuteFns)]
pub enum Foo {
Bar { a: String },
}
// Now we construct the concrete type with `Foo` in place of the generic.
type ExecuteMsg = GenericExecuteMsg;
// And we implement the `From` trait (which auto-implements `Into`).
impl From for ExecuteMsg {
fn from(msg: Foo) -> Self {
ExecuteMsg::Generic(msg)
}
}
#[interface(Empty, ExecuteMsg, Empty, Empty)]
struct Example;
impl Example {
pub fn test_macro(&self) {
// Function `bar` is available because `Foo` implements `Into>`
self.bar("hello".to_string()).unwrap();
}
}
```
## WASM flagging
Cw-orch cannot be used *inside* smart contracts. In order to prevent you from having to add feature flags inside your smart-contract, the library excludes itself when building for the WASM target architecture. If you see errors during the build process like shown below, you will want to `target-flag` the related code:
```bash
error[E0432]: unresolved import `cw_orch::prelude`
--> contracts/counter/src/interface.rs:4:26
|
4 | use cw_orch::{interface, prelude::*};
| ^^^^^^^ could not find `prelude` in `cw_orch`
error[E0432]: unresolved import `cw_orch::anyhow`
--> contracts/counter/src/interface.rs:38:14
|
38 | use cw_orch::anyhow::Result;
| ^^^^^^ could not find `anyhow` in `cw_orch`
error: cannot find macro `artifacts_dir_from_workspace` in this scope
--> contracts/counter/src/interface.rs:19:9
|
19 | artifacts_dir_from_workspace!()
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
error[E0405]: cannot find trait `Uploadable` in this scope
--> contracts/counter/src/interface.rs:16:13
|
16 | impl Uploadable for CounterContract {
| ^^^^^^^^^^ not found in this scope
```
Just add the `#[cfg(not(target_arch = "wasm32"))]` to not include the code inside wasm builds:
```rust,ignore
#[cfg(not(target_arch = "wasm32"))]
mod interface;
```
## Supported chains
Cw-orchestrator supports the following chains natively:
🟥 LocalNet, 🟦 Testnet, 🟩 Mainnet
- Archway 🟦🟩
- Cosmos Hub 🟩
- Injective 🟦🟩
- Juno 🟥🟦🟩
- Kujira 🟦
- Migaloo 🟥🟦🟩
- Neutron 🟦🟩
- Nibiru 🟦
- Osmosis 🟥🟦🟩
- Sei 🟥🟦🟩
- Terra 🟥🟦🟩
- Rollkit 🟥🟦
- Xion 🟦
- Landslide 🟥
Additional chains can easily be integrated by creating a new [`ChainInfo`](./packages/cw-orch-networks/src/chain_info.rs) structure. This can be done in your script directly. If you have additional time, don't hesitate to open a PR on this repository.
### Testing with OsmosisTestTube
[OsmosisTestTube](https://github.com/osmosis-labs/test-tube) is available for testing in cw-orchestrator. In order to use it, you may need to install [clang](https://clang.llvm.org/) and [go](https://go.dev/) to compile the osmosis blockchain that serves as the backend for this env. This compilation is taken care of by cargo directly but if you don't have the right dependencies installed, weird errors may arise.
- Visit for a comprehensive list of dependencies.
- Visit [the INSTALL.md file](./INSTALL.md) for a list of dependencies we have written specifically for use with cw-orch.
## Installation
Cw-orch relies on external tools to work properly. Visit [the INSTALL.md file](./INSTALL.md) for a list of dependencies and install commands that are needed for cw-orch to work properly on your machine.
## Contributing
We'd really appreciate your help! Please read our [contributing guidelines](docs/src/contributing.md) to get started.
## Documentation
The documentation is generated using [mdbook](https://rust-lang.github.io/mdBook/index.html). Edit the files in the `docs/src` folder and run
```shell
just serve-docs
```
to view the changes.
[Release Docs](https://orchestrator.abstract.money)
[Dev Docs](https://dev-orchestrator.abstract.money)
## Testing
To test the full application you can run the following command:
```shell
cargo test --jobs 1 --all-features
```
## References
Enjoy scripting your smart contracts with ease? Build your contracts with ease by using [Abstract](https://abstract.money).
## Disclaimer
This software is provided as-is without any guarantees.
## Credits
cw-orchestrator is inspired by [terra-rust-api](https://github.com/PFC-Validator/terra-rust) and uses [cosmos-rust](https://github.com/cosmos/cosmos-rust) for [protocol buffer](https://developers.google.com/protocol-buffers/docs/overview) gRPC communication.
## License
This software is licensed under LGPL-3.0. For more information, see the [LICENSE](LICENSE.LESSER) file.
Versions of this software on and before commit `cbab5f51b9e0b4ddec88906e263e4290e5b2dedf`, corresponding to version `v0.25.0`, are licensed under GPL-3.0. For more information, see the [LICENSE](LICENSE) file.