Bor v1.4.0-beta2 Amoy Release (Gandhinagar Hardfork)

Announcements
1

Hello All,

A new version of Bor (v1.4.0-beta2) has been released for Polygon Amoy Testnet. This version includes a hard fork named Gandhinagar fork.

The Ahmedabad hardfork on Amoy Testnet went through pretty smoothly on Sept 12th. However, the upgrade to WMatic did not go as expected. The changes that were made to the bytecode did not have any effect, thus making the deployment ineffective. During the name change of WMatic to WPOL the assigning of the new values for token symbol and token name didn’t happen properly. This is because during the hardfork, init code doesn’t run, but the new bytecode gets placed directly. The fix was to not rely on the initcode, but to instead use constant values that are part of the bytecode.

Please note, since this deployment was done on Amoy Testnet only, we need to execute this additional hardfork only on Amoy.

Please upgrade your Amoy nodes before block number 12,121,856 (https://amoy.polygonscan.com/block/countdown/12121856) which is expected to be mined on Wed, Sept 18 2024 around 10 AM UTC. Announcement for Erigon with the new release will follow on Mon, Sept 16.

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 -- v1.4.0-beta2 <network> <node_type>

  3. Check bor version

    /usr/bin/bor version

# It should print 
# v1.4.0-beta2

  4. Restart bor service

    sudo service bor start

Bor Changelog

What’s Changed

Full Changelog: v1.4.0-beta…v1.4.0-beta2

Docker Images

You can find the latest docker images here:

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

Heimdall:https://hub.docker.com/r/0xpolygon/heimdall/tags

Thanks,

Polygon Team

1 Like