🚧 1.16.0 Roll out plan

[byte-bandit]

There is likely a lot of edge cases I haven't thought about yet.

For example, after the upgrade to Paloma 1.16.0, we will need to deploy a new version of compass, immediately. All calls to the old version of compass will fail (since Pigeon will already use the new syntax). This is a problem, since we need to make calls to old compass in order to update the token ownership.

We also won't have any governance yet for exchanges, nor will we have the fee manager contract deployed.

The most obvious solution to the problems outlined above is a multi stage release, something like this:

• release 1: introduce options to upgrade consensus and upload fee manager (might need small compass upgrade), make sure user fees are set and metrics collected
• release 2: deploy new (full) compass, pigeon can distinguish between compass versions and makes calls accordingly to which version is needed (old compass, new compass)
• release 3: flip ownership of tokens and fee manager contracts, enable new compass usage

Also:

We want the Node Sale to be the only price for GRAINS. As such, we want to delay the launching of the GRAIN pools until AFTER the Node Sale is complete. We won't be able to control the DEX price and our floor price for Paloma is an FDV of $5MM.

Thus, we want Pigeon Feed to launch, but holding of the relay fees until we "FEE SWITCH" with a launch of the Pools after the node sale completes.

There's probably still stuff missing in this plan, but it gives an idea of what's needed.

[verabehr]

from discussion with Christian and Taariq:

• we will stop the bot backend scripts about an hour before upgrade and then restart so we don't risk a malformatted SLC message
• we will not worry about migrating any currently deployed test tokens. Vera will send all tokens back to Paloma before the upgrade

[maharifu]

Even if we don't want to move test tokens, since we have them set, paloma will still try to move them. This will fail since (new) pigeon won't be compatible with (old) compass, so we will still need to deal with this.

Can we disable this mechanism in 1.16.0 and re-enable it in 1.16.1? This might be the faster option to allow us to deploy now.

[verabehr]

disabling works for me. We plan to move the tokens back to Paloma and end testing once the vote for the weights has passed and relaying is unblocked again

[verabehr]

https://www.notion.so/volumefi/EPIC-08-16-24-Paloma-2-0-rollout-plan-5bfa33fa286f4d828ae6ef93ed478e91?pvs=4