PIP-53: Paloma Mainnet Upgrade to Paloma v1.11.0

Governance
1

PIP Name: PIP-53: Paloma Mainnet Upgrade to Paloma v1.11.0

Status: Proposed

Author(s): @LARRY

Type: Software Upgrade

Discussions-to: PIP-53: Paloma Mainnet Upgrade to Paloma v1.11.0

Created: 01/15/2024

Simple Summary

This is a software upgrade for Paloma to v1.11.0 tags for both Paloma TESTNEST-15 and MAINNEST messenger networks. This update delivers on the following protocol feature requirement: as a user of Paloma, I want Paloma to be able to migrate tokens and funds to new compass-EVM deployments when a vote for new compass passes. This is required when any problems are discovered in the Compass-EVM client that will warrant an upgrade across multiple chains. Paloma Compass-EVM is currently deployed on seven chains and this improvement will ensure future-proofing of Compass-EVM upgrades when the number of target chains increases.

Abstract

The Paloma mainnet continues to achieve the goal of fast and reliable validator node support for effective cross-chain communication and cross-chain relay functionality. Now that Paloma relays are continuing to improve in speed and execution, we want to ensure that Compass-EVM client upgrades deliver successful migrations across all target chains.

Motivation

The upgrade motivations for this new release are as follows:

  • Ensure deployed ERC20 tokens remain under governance during and after compass upgrades
  • Update compass deployment code to keep a reference history of old compass addresses
  • After successful update, Pigeons change ownership of GRAIN token to new compass
  • Only THEN mark new compass contract as enabled

Specification Overview

This action requires an upgrade of palomad to the latest tag v1.11.0. All migrations are included and are being tested on the Paloma public testnest paloma-testnest-15. Validators must install both new binaries and restart their nodes at chainhalt.

Technical Specification

The latest releases of Paloma and Pigeon are available here and include the change logs for each for review prior to deployment:

  1. Download and install the latest Paloma tag: Release v1.11.0 · palomachain/paloma · GitHub
  2. An upgrade proposal that must be submitted by anyone running a node on the network. This proposal should have the correct block height.
  3. Please use the following spreadsheet to calculate the approximate Block Height. https://docs.google.com/spreadsheets/d/1eoXoDWWYHIOYbdPiv8B6vfwDUUkelZgeifnX4foa7yw/edit#gid=0
  4. This upgrade proposal requires 10 GRAIN or 10000000ugrain for deposit for voting.
  5. IMPORTANT: The upgrade height is the block height where the chain halts and requires the upgrade. Allow at least one (1) day AFTER voting end time and upgrade-height for 2/3 of the network to have downloaded the new binary and prepped for the switch over to avoid/minimize downtime of the Paloma chain.
  6. The Target block height for chain halt for this proposal is tentative 11331563 or approximately 01/19/24 11:50 UTC See (Block height: 11331563 )
palomad tx gov submit-legacy-proposal software-upgrade v1.11.0 \
--title "PIP-53: Upgrade Paloma to v1.11.0 on Paloma Mainnet" \
--description "Ensure deployed ERC20 tokens remain under governance during and after compass upgrades" \
--deposit 10000000ugrain \
--fees 400ugrain \
--upgrade-height  <BLOCK_HEIGHT> \
--upgrade-info '{"binaries":{"linux/amd64":"[https://github.com/palomachain/paloma/releases/download/v1.11.0/paloma_Linux_x86_64.tar.gz](https://github.com/palomachain/paloma/releases/download/v1.10.2/paloma_Linux_x86_64.tar.gz)"}}' \
--gas 400000 \
--from <Your Paloma Address>  \
--no-validate \
--y

How to Vote on the Proposal

palomad tx gov vote 44 yes \
--chain-id=messenger \
--from <Your Paloma Address> \
--fees 400ugrain \
-y

How to check if 2/3 of the network are online after vote is complete

curl -s localhost:26657/consensus_state | jq -r ".result.round_state.height_vote_set[0].prevotes_bit_array"

—> needs to return ≥ ~0.67 for the chain to start up again

To see which validators are online with the new binary, use GitHub - blockpane/pvtop: top-like tui for watching validator pre-votes on Tendermint chains

Rationale

The Paloma mainnet continues to achieve the goal of fast and reliable validator node support for effective cross-chain communication and cross-chain relay functionality. This upgrade allows Paloma to upgrade its Compass-EVM client across mutliple chains with one governance vote. The objective is to allow for continuous upgrade of compass, without the need to re-deploy each client with a governance vote for each chain. This is also a security improvement which allows Paloma to upgrade Compass-EVM when critical security upgrades are required.

About Paloma

Paloma wants to be the fastest relay chain in the world with the most decentralized network of validators that can attest to any transaction with fast execution. Paloma aims to make it easy for developers to control smart contracts on any Solana, Ethereum L1, L2, and L3 chain.

To learn more about Paloma, please visit https://palomachain.com

To follow the project on Github, please star the project GitHub - palomachain/paloma: The fast blockchain messenger protocol

To participate in the community, please join the Paloma Discord: Paloma