PIP-145: Update BNB reference Block After BNB Hard Fork

Governance
1

Proposal: PIP-145: Update BNB reference Block After BNB Hard Fork

Status: Proposed

Author(s): @BoweryKing

Type: Software Upgrade

Discussions-to: Governance - Paloma

Created: 06/30/2025

Simple Summary

On June 30, 2025, BNB chain executed a hard fork. As such, the reference hash for BNB chain changed and was not recoverable by the Paloma flock, halting all relays. This is a proposal to update the BNB chain referenceBlock to a valid Block and Hash pair.

Abstract

On June 30, 2025, BNB chain executed a hard fork. As such, the reference hash for BNB chain changed and was not recoverable by the Paloma flock, halting all relays. Attempts by Paloma to recover the reference block hash failed. Paloma updates the referenceBlock data of the target chains every 10,000 blocks. If the referenceBlock data is incorrect for some reason. E.g. a chain reorg or fork of the target chain, the chain-infos for that chain becomes unreliable and all pigeons become stuck resulting in

  • message relays
  • pigeon status updates
  • reference block updates

no longer being processed.

This proposal updates the referenceBlock to this block -hash pair

  • Block Height: 52362072
  • Hash: 0x44f493a15123548839c91b8f33fc51f0ca5635d9a4af0635593a098f3001d299

Motivation

Updating the referenceBlock data in evm chains-infos is required to restart relaying.

Technical Specification

Proposal Vote Command for CLI

palomad tx gov submit-proposal ./pip-145.json \
--gas auto \
--node=https://rpc-1.paloma.nodes.guru/ \
--chain-id tumbler \
--from <Your Paloma Address>

pip-145.json

{
 "messages": [
  {
   "@type": "/palomachain.paloma.evm.MsgProposeNewReferenceBlockAttestation",
   "metadata": {
    "creator": "paloma10d07y265gmmuvt4z0w9aw880jnsr700jz87xyk",
    "signers": ["paloma10d07y265gmmuvt4z0w9aw880jnsr700jz87xyk"]
   },
   "authority": "paloma10d07y265gmmuvt4z0w9aw880jnsr700jz87xyk",
   "chain_reference_id": "bnb-main",
   "blockHeight": "52362072",
   "blockHash": "0x44f493a15123548839c91b8f33fc51f0ca5635d9a4af0635593a098f3001d299"
  }
 ],
 "metadata": "ipfs://QmQe525acBbVWHZ7JHFN5bXGWvxZjQC1tnjmLFWzb56XzQ",
 "deposit": "1000000000ugrain",
 "title": "PIP-145: Update BNB reference Block After BNB Hard Fork",
 "summary": "PIP-145: Update BNB reference Block to a valid block and hash.",
 "expedited": true
}

pip-145_metadata.json

{
 "title": "PIP-145: Update BNB reference Block After BNB Hard Fork",
 "authors": [
  "birdlady"
 ],
 "summary": "PIP-145: Update BNB reference Block After BNB Hard Fork",
 "details": "PIP-145: Update BNB reference Block After BNB Hard Fork on June 30, 2025",
 "proposal_forum_url": "https://forum.palomachain.com/c/governance/6",
 "vote_option_context": "Vote YES to update the BNB reference block in evm chains-info"
}

How to Vote on Proposal 208 with CLI

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

How to Vote on Proposal 208with Paloma LightNodes

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

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

Rationale

This vote fixes the reference hash for the new BNB chain after the hard fork on June 30, 2025. This vote is preventative to ensure that validators are able to relay.

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