chore: release v2.3.0-mainnet

[RiccardoM]

Description

This PR implements the changes needed in order to tag v2.1.0-mainnet of Desmos. Refer to #657 for major details.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[RiccardoM]

Updated to match the current mainnet data

[RiccardoM]

Revert the changes to match Cosmos v0.42 events list

[codecov]

Codecov Report

Merging #660 (a47566b) into master (581744d) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #660      +/-   ##
==========================================
- Coverage   15.78%   15.77%   -0.01%     
==========================================
  Files         169      169              
  Lines       46009    46033      +24     
==========================================
  Hits         7263     7263              
- Misses      38119    38143      +24     
  Partials      627      627              

Impacted Files	Coverage Δ
app/app.go	77.88% <0.00%> (-4.56%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 581744d...a47566b. Read the comment docs.

[dadamu]

Ready

[leobragaz]

Forgot to approve this.

[leobragaz]

@RiccardoM I've solved the conflicts. Please take a look whenever you can. It should be the correct configuration since this is the first on-chain auto-upgrade of the mainnet/.

[leobragaz]

@RiccardoM done

[leobragaz]

@RiccardoM looking at this I've seen that we need to hardcode the ConseusVersion to 1 the first time.
Currently it's set to 3. We should change it, confirm?

[RiccardoM]

@RiccardoM looking at this I've seen that we need to hardcode the ConseusVersion to 1 the first time. Currently it's set to 3. We should change it, confirm?

That is not correct. The ConsensusVersion identifies the latest version of a module. In our case, the x/profiles module should be at its third version (ConsensusVersion = 3) due to 2 previous migrations we had to run.

When the upgrade height comes, what happens is the following:

• the current veision of each module is read using the fromVm map
• the updated version of each module is read using the ConsensusVersion method
• for each module, we perform an upgrade old_version -> current_version

If the current version is 1 and the new one is 3, then two upgrades are performed:

1. From 1 to 2
2. From 2 to 3

And this is why inside the x/profiles migrator we have two methods: Migrate1To2 and Migrate2To3