Functions on Router chain's middleware contract
In the cosmwasm smart contact, router-wasm-bindings needs to be added to support the cross-chain functionality.
router-wasm-bindings as dependency
The router-wasm-bindings crate dependency can be added as shown in the following code snippet.
[dependencies]
# add the following line in the cargo.toml [dependencies] section
router-wasm-bindings = "0.2.4"
To implement cross-chain interoperability, the contract needs to implement the following functionality
- SudoMsg
- to handle incoming requests from the other chains
- RouterMsg
- to send a request to the other chains
The contract can write the intermediate business logic in-between the incoming request and outbound request. While writing the intermediate business logic, the developer can convert single or multiple incoming requests into single or multiple outbound requests. Also, while creating requests to other chains, the contract can be developed in such a way that multiple requests can be generated for different chains. You can find examples of different scenarios in the cw-bridge-contracts repository.