Tracking issue for Core v2.2.0 release

[nghuyenthevinh2000]

• cosmos - sdk v46
• cometbft
• update ibc-go to v6 to match with cosmos - sdk v46
• update current wasmd to use cosmos - sdk v46
• wasmd with FundCommunityPool, and genesis fix
• Support WASM stargate queries #309
• feat(treasury): split the burn tax to the distribution module #272
• feature: Smart Contract Tax Whitelist #301
• migration guide (https://github.com/classic-terra/documents/blob/main/migration/core_v220.md)

[nghuyenthevinh2000]

@alchemist-ti can you check our wasmd compatible with cosmos - sdk v46, there are some incompatibles: https://github.com/classic-terra/wasmd

currently, I am using this modified version of cosmos - sdk v46: classic-terra/cosmos-sdk#8, feel free to modify it if you see fit.

[alchemist-ti]

@alchemist-ti can you check our wasmd compatible with cosmos - sdk v46, there are some incompatibles: https://github.com/classic-terra/wasmd

currently, I am using this modified version of cosmos - sdk v46: classic-terra/cosmos-sdk#8, feel free to modify it if you see fit.

Yes, I will check it.

[nghuyenthevinh2000]

@inon-man since we are removing legacy rest on cosmos - sdk, I think that we have to discus about rest endpoints migration else station, and all dependant front - end will break heavily

[inon-man]

@inon-man since we are removing legacy rest on cosmos - sdk, I think that we have to discus about rest endpoints migration else station, and all dependant front - end will break heavily

legacy rest endpoints were removed from terra.js very long time ago, and fcd does not use it too anymore. Station will be safe but I will test it on my local.