You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we advance and aim to establish the IBC connection, It has become imperative to gain a comprehensive understanding of the customer’s infrastructure and their rollup and cosmos nodes’ specifications, so can consider them for the mainnet launch.
We require detailed information on the following aspects:
Cosmos node characteristics
Insights into the overall architecture and specifications of the Cosmos node. Which version of CometBft is currently operational within their setup? Which specific version of Cosmos SDK is being utilized? Has the WASM module been integrated?
ibc-go configurations
What version of the ibc-go are they operating on? Is that Wasm-enabled and capable of handling 08-wasm messages?
Customer requirements
Are there any specific requirements or constraints from the customer that we should be aware of?
Understanding such details is of paramount importance as it reduces any mismatches in our designs, especially considering the tight deadlines.
The text was updated successfully, but these errors were encountered:
Farhad-Shabani
changed the title
Determine requirements for Integration with customer's rollup and cosmos nodes.
Determine requirements for integration with customer's rollup and cosmos nodes
Jan 11, 2024
Background
As we advance and aim to establish the IBC connection, It has become imperative to gain a comprehensive understanding of the customer’s infrastructure and their rollup and cosmos nodes’ specifications, so can consider them for the mainnet launch.
We require detailed information on the following aspects:
Cosmos node characteristics
Insights into the overall architecture and specifications of the Cosmos node. Which version of CometBft is currently operational within their setup? Which specific version of Cosmos SDK is being utilized? Has the WASM module been integrated?
ibc-go configurations
What version of the ibc-go are they operating on? Is that Wasm-enabled and capable of handling 08-wasm messages?
Customer requirements
Are there any specific requirements or constraints from the customer that we should be aware of?
Understanding such details is of paramount importance as it reduces any mismatches in our designs, especially considering the tight deadlines.
The text was updated successfully, but these errors were encountered: