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
Certain Cosmos SDK chains such as Akash have signalled their intention to not support CosmWasm.
DAOs provisioning cloud resources on Akash would be a significant addressable market for DAO DAO and Akash.
As Akash may have valid reasons to not integrate CosmWasm. Would this Go Cosmos SDK module feature request be technically possible on the DA0-DA0/polytone side?
The text was updated successfully, but these errors were encountered:
Polytone is our smart-contract version of ICA. DAOs can already use native ICA actually to connect to Akash, so this is already possible.
But the UX of ICA isn't great because of how channels work, and for some reason you can't simulate messages as an ICA host account. You can simulate messages as a smart contract account, which lets our UI verify that your messages are valid on the destination chain before submitting a proposal. Also, ICA doesn't store results while Polytone does, so we can query a contract to check for execution success or error.
I'm not exactly sure where the technical limitations lie, but I find it hard to believe that creating another SDK Go module is the best solution when both the Polytone smart contracts and the CosmWasm SDK module have been audited and battle-tested with lots of money and time.
Certain Cosmos SDK chains such as Akash have signalled their intention to not support CosmWasm.
DAOs provisioning cloud resources on Akash would be a significant addressable market for DAO DAO and Akash.
Akash is in the process of:
upgrading to SDK v47 akash-network/support/issues/212
to support ICA akash-network/support#171
DAO DAO <> Akash #570
CosmWasm on Akash Network GitHub organization
As Akash may have valid reasons to not integrate CosmWasm. Would this Go Cosmos SDK module feature request be technically possible on the
DA0-DA0/polytone
side?The text was updated successfully, but these errors were encountered: