Uses new Rust 2021
|0.2.0-beta.6||Nov 25, 2022|
|0.2.0-beta.5||Nov 18, 2022|
|0.2.0-beta.1||Oct 26, 2022|
|0.1.0||Oct 10, 2022|
#157 in Operating systems
322 downloads per month
Used in fewer than 8 crates
This package contains everything you need to interact with Abstract contracts.
This package contains:
- Abstract contract interface messages
- Abstract contract states
- Abstract objects (preferably use the re-exported version in Abstract-SDK)
// Import a contract Exec/Init/Query message abstract_os::contract::ExecuteMsg // Import a contract state lay-out abstract_os::contract::state::STATE // Import a state object abstract_os::object::ProxyValue;
Each interface in individually commented.
Each state-layout is also individually covered
Abstract Objects are used to store information along with helper functions. We provide these as imports so the data can be retrieved externally (using Raw Queries).
If you want to use these objects in your own contracts we suggest using the abstract-sdk package.
Abstract OS is the interface-defining crate to the Abstract OS smart-contract framework.
This crate provides the key utilities that are required to integrate with or write Abstract contracts.
All interfacing message structs are defined here so they can be imported.
cw-asset is used for asset-management.
If a message requests a String value for an Asset field then you need to provide the human-readable ans_host key.
The full list of supported assets and contracts is given here.
The contract will handel address retrieval internally.
The internal state for each contract is also contained within this crate. This ensures that breaking changes to the internal state are easily spotted. It also allows for tight and low-gas integration between contracts by performing raw queries on these states. A contract's state object can be imported and used like:
use crate::manager::state::OS_ID let os_id = OS_ID.query(querier, manager_address).unwrap();
The internally stored objects are also contained within this package in [
Abstract contract names are used internally and for version management. They are exported for ease of use: