version 7 tracking issue

[hoank101]

Across:

• wasmd
• packet forward middleware
• async-icq

There've been some changes to make how we interact with governance more conventional, and the ability to refund unforwardable forwards has been added.

Given that PFM in particular has made fairly big changes, and it doesn't make sense to stay on retracted code, v7 will stay on v0.47.x while using the mainine wasm client and hopefully mainline IBC.

Version 7

• Use the latest ibc-go/v7
• Use mainline wasm client
  • feat(migration): from previous wasm client to current #371
  • tests for wasm client migration #372
• use latest async-icq #364
• update grandpa contract #287
• Use the latest SDK 47 compatible wasmd (thanks @hoank101 !)
  • Upgrade wasmvm to version v1.5.2
• fix interchaintest in ci by ensuring that this repository can make docker images public #373
• Upgrade the alliance module by merging upstream into notional's composable branch
  • Update the disabled alliance notional-labs/alliance#1
• integrate our changes with the latest PFM, underway here:
  • https://github.com/notional-labs/ibc-apps/pull/new/faddat/update-tweaked-pfm
• review our own use of legacy governance #370
• remove go tools #367
• upgrade to IBC-hooks now support async acknowledgements #228
  • Add test ibc-hooks, make sure work compatible with old data and previous version #431
• Add test upgrade chain
  • Add docker-compose run test upgrade many validators #423

---

nice to haves

• remove alliance
• change bech32 prefix

[faddat]

hey :D

@hoank101 -- we are going to head straight to v0.50.x unless you think that this task is something that must be done this second. (and personally I am unsure)

Note: it's kinda worse than deprecated, wasmd v0.43 and v0.44 are retracted 😬

My vibe on the solution was to jump to v0.50.x but interested in your thoughts here

Related to this, I am currently working on:

cosmos/ibc-apps#153

please feel free to push to my branch if you can help!

I am modeling it after the ibc-go simapp.

[hoank101]

yeah @faddat, I think we need step by step, i just have PR at #361

i will check ibc-apps

[faddat]

@hoank101 will review now :D

it may make sense to do an ugprade on v0.47.x before v0.50.x I'll put you in our channel with skip, I am talking with Barry about that now

[faddat]

@hoank101 Actually I think you found a set of important issues. It took me crazy long to finish this up, but thank you!

I'm going to make this issue into a v7 tracker.

@RustNinja this means that your current work may even make it into the upcoming release!

[dzmitry-lahoda]

Hello, how it is going? May I check WASMD migration if that is good to check ? I guess it would be that I check their release notes and see nothing will break. Said that, do we really have any contracts except mine (CVM+MANTIS)? I doubt.

[dzmitry-lahoda]

I am for jumping to latest possible WASMD which is compile compatible to our go packages - I think all contracts on our chain are alfa - so doubt we care. Will recheck.

Other note - need to bump ontract size 2x like Neutron/Osmosis did and make FEE for contract (now it is zero), may be at least 20 USD to prevent SPAM.

[faddat]

@dzmitry-lahoda this upgrade shouldn't break contracts, except for grandpa.

Grandpa, we will need to update. We should study the smooth way of doing that.

[faddat]

@dzmitry-lahoda we do not yet have a migration, this is only the initial set of changes.

idk if you have a preference: typically, I'll get the changes in place, look at the global changeset, and then write the migration.

There's rather a lot to be concerned with here, so please do feel free to jump in.

I am thinking to merge

• use mainline packages for ibc and 08-wasm #374

to the release/v7.0.x branch tonight.

We also need to ensure that this repository can publish packages (in this case docker images) to ghcr.io so we can put interchaintest back in the ci flow

[dzmitry-lahoda]

I am thinking on making changes to wasmd, assuming nobody works on wasmd now.

What is timeline on delivering this branch? Assuming I do 100% of wasmd related work

[dzmitry-lahoda]

https://github.com/ComposableFi/composable-cosmos/tree/faddat/upgrade-to-mainline

I testind wasmd on this branch and adding config points by me.

#281

#385

[JafarAz]

@faddat @hoank101 Hey sirs, what is the timeline for getting version 7 feature complete?

[dzmitry-lahoda]

some wasmd setup #394 , made it some address only and better size. added v7 upgrade handler.

if somebody knows how to set Upload contract fee - would be awesome. not found how.

[dzmitry-lahoda]

working on pfm upgrade