This is the return value for the majority of the ibc handlers.
That are able to dispatch messages / events on their own,
but have no meaningful return value to the calling code.
In IBC each package must set at least one type of timeout:
the timestamp or the block height. Using this rather complex enum instead of
two timeout fields we ensure that at least one timeout is set.
IBCTimeoutHeight Height is a monotonically increasing data type
that can be compared against another Height for the purposes of updating and
freezing clients.
Ordering is (revision_number, timeout_height)
Additional information from MsgInstantiateContract and MsgExecuteContract, which is passed
along with the contract execution message into the instantiate and execute entry points.
Holds all external dependencies of the contract.
Designed to allow easy dependency injection at runtime.
This cannot be copied or cloned since it would behave differently
for mock storages and a bridge storage in the VM.
A submessage that will guarantee a reply call on success or error, depending on
the reply_on setting. If you do not need to process the result, use regular messages instead.
A thin wrapper around u64 that is using strings for JSON encoding/decoding,
such that the full u64 range can be used for clients that convert JSON numbers to floats,
like JavaScript and jq.
A thin wrapper around u128 that is using strings for JSON encoding/decoding,
such that the full u128 range can be used for clients that convert JSON numbers to floats,
like JavaScript and jq.
An implementation of u256 that is using strings for JSON encoding/decoding,
such that the full u256 range can be used for clients that convert JSON numbers to floats,
like JavaScript and jq.
An implementation of u512 that is using strings for JSON encoding/decoding,
such that the full u512 range can be used for clients that convert JSON numbers to floats,
like JavaScript and jq.
This is the final result type that is created and serialized in a contract for
every init/execute/migrate call. The VM then deserializes this type to distinguish
between successful and failed executions.
IbcOrder defines if a channel is ORDERED or UNORDERED
Values come from https://github.com/cosmos/cosmos-sdk/blob/v0.40.0/proto/ibc/core/channel/v1/channel.proto#L69-L80
Naming comes from the protobuf files and go translations.
These are queries to the various IBC modules to see the state of the contract’s
IBC connection. These will return errors if the contract is not “ibc enabled”
Use this to define when the contract gets a response callback.
If you only need it for errors or success you can select just those in order
to save gas.
Api are callbacks to system functions implemented outside of the wasm modules.
Currently it just supports address conversion but we could add eg. crypto functions here.
A trait that is required to avoid conflicts with other query types like BankQuery and WasmQuery
in generic implementations.
You need to implement it in your custom query type.
The return type for init, execute and query. Since the error type cannot be serialized to JSON,
this is only available within the contract and its unit tests.