PIP-142: Update the last observed nonce on Arbitrum

Governance
1

Proposal: PIP-142: Update the last observed nonce on Arbitrum

Status: Proposed

Author(s): @BoweryKing

Type: Other

Discussions-to: Governance - Paloma

Created: 03/26/2025

Simple Summary

Due to validators failing to attest Skyway Batches that check for nonce increment on Compass on Arbitrum, we must reset the nonce via governance. We expect PIP-140 to resolve this issue with validators being jailed for failing to attest to Skyway nonces on target chains.

Abstract

Due to validators failing to attest Skyway Batches that check for nonce increment on Compass on Arbitrum, we must reset the nonce via governance. This is a proposal to update the lastObservedNonce height to the most recent height observed in the pending transactions to allow pigeons to relay again on Arbitrum.

Motivation

Updating the lastObservedNonce data in is required to restart skyway message relaying on Arbitrum.

Technical Specification

We identify the lastObservedNonce by checking Compass on Arbitrum for the last recorded nonce here:

Compass Analyzed: Active Paloma Networks | Official Paloma Protocol Documentation

Arbitrum Compass Event Logs: Arbitrum One Transaction Hash: 0xab3fc22cf1... | Arbitrum One

Chain New Nonce
Arbitrum 3171

Proposal Vote Command for CLI

palomad tx gov submit-proposal ./pip-142.json \
--gas auto \
--node=<Your node> \
--chain-id tumbler \
--from <Your Paloma Address>

Arbtirum

pip-142.json

{
 "messages": [
  {
   "@type": "/palomachain.paloma.skyway.MsgNonceOverrideProposal",
   "metadata": {
    "creator": "paloma10d07y265gmmuvt4z0w9aw880jnsr700jz87xyk",
    "signers": ["paloma10d07y265gmmuvt4z0w9aw880jnsr700jz87xyk"]
   },
   "chain_reference_id": "arbitrum-main",
   "nonce": "3171"
  }
 ],
 "metadata": "ipfs://QmQe525acBbVWHZ7JHFN5bXGWvxZjQC1tnjmLFWzb56XzQ",
 "deposit": "1000000000ugrain",
 "title": "PIP-142: Update the last observed nonce on Arbitrum",
 "summary": "Update last observed nonce on Arbitrum to restart skyway messages.",
 "expedited": true
}

pip-142_metadata.json

{
 "title": "PIP-142: Update the last observed nonce on Arbitrum",
 "authors": ["BoweryKing"],
 "summary": "PIP-142: Update the last observed nonce on Arbitrum.",
 "details": "Update last observed nonce on Arbitrum to restart skyway messages",
 "proposal_forum_url": "https://forum.palomachain.com/c/governance/6",
 "vote_option_context": "Vote YES to update the last observed nonce height"
}

How to Vote on Proposal 206 with CLI

palomad tx gov vote 206 yes \
--chain-id tumbler \
--from <Your Paloma Address> \
--node <Your node> \
-y

How to Vote on Proposal 206 with Paloma LightNodes

# Mac & Linux
sh ~/Downloads/setup.sh vote-proposal 206 yes

# **Windows**
docker run --rm --pull=always -ti -v $env:USERPROFILE\\paloma-lightnode:/root/lightnode palomachain/lightnode-client:v2 vote-proposal 206 yes

Rationale

Due to validators failing to attest Skyway Batches that check for nonce increment on Compass on Arbitrum, we must reset the nonce via governance. We expect PIP-140 to resolve this issue with validators being jailed for failing to attest to Skyway nonces on target chains.

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 the fastest possible 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