New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ibc cosmwasm contracts #2591
Ibc cosmwasm contracts #2591
Conversation
3690f37
to
b8e5f5c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See inline comments
b8e5f5c
to
385de23
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When @panoel attempted to upgrade the wormhole
contract, it failed due to the new versioning checks.
bd00ad1
to
3075593
Compare
3075593
to
a281dcc
Compare
cde26ec
to
7530f0c
Compare
9723755
to
686c441
Compare
7530f0c
to
9a86d57
Compare
7c666a3
to
12c64c8
Compare
9a86d57
to
ce6ac2c
Compare
7747f55
to
bd7e4d8
Compare
253949c
to
deb0734
Compare
306f17f
to
d5c9b6b
Compare
…itelist on the receiver end
According to @nik-suri changes addressed. They will follow up with tests
#2198 #2199
This PR adds the two new cosmwasm contract for IBC generic message emission:
wormchain-ibc-receiver
andwormhole-ibc
. These two contracts implement a custom IBC protocol. Thewormhole-ibc
contract should be deployed to IBC-enabled chains, and the variouswormhole-ibc
contract should connect via IBC to thewormchain-ibc-receiver
contract, which will live on Wormchain.For existing Cosmos deployments, the
wormhole
cosmwasm contract should be migrated to thewormhole-ibc
cosmwasm contract after it is uploaded to the chain.