Bor v2.4.0-beta4 and Erigon v3.2.2.-beta3 releases for Amoy

Hi all, we have released a new beta version of bor (v2.4.0-beta4).

This release defines the block number for the Madhugiri HF in amoy, at block height 28899616, expected on Tue, Nov 11, 2025, 10:30 AM UTC.

Steps for upgrading Bor node

  1. Stop bor service

    sudo service bor stop
    
    
  2. Install Bor with a version tag, network name (amoy), and node type (sentry, validator, or archive).

    # Replace the node type
    curl -L https://raw.githubusercontent.com/maticnetwork/install/main/bor.sh | bash -s -- v2.4.0-beta4 <network> <node_type>
    
    
  3. Check bor version

    /usr/bin/bor version
    
    # It should print 
    # v2.4.0-beta4
    
    
  4. Restart bor service

    sudo service bor start
    
    

What’s Changed

  • chore: set madhugiri block for amoy and consensus block time by @marcello33 in #1867

Full Changelog: v2.4.0-beta3…v2.4.0-beta4

Erigon

The corresponding 0xPolygon/erigon version is v3.2.2-beta3

For node operators upgrading from v3.0.x a resync might be needed. After upgrading your Erigon binary and having done a back-up of your data directory, you can delete data folders and sync from scratch (*chaindata*, *heimdall*, and *polygon-bridge*).

The release notes of upstream Erigon mentions:

Erigon 3.1 Pebble Paws will work flawlessly with old data. For those who want to ensure they have the absolute latest data files and any recent data-specific fixes, you can optionally perform a manual data upgrade. After upgrading your Erigon binary and having done a back-up of your data directory, just run the command erigon snapshots reset --datadir /your/datadir.

Docker Images

You can find the latest docker images here:

Bor: https://hub.docker.com/r/0xpolygon/bor/tags

Erigon: https://hub.docker.com/r/0xpolygon/erigon/tags

Thanks,

Polygon Team