Bor Mumbai Upgrade: v0.3.2-beta (patch for v0.3.1-mumbai) [Action Required]

Hello all, bor v0.3.2-beta is a small patch release for the nodes running v0.3.1-mumbai on the Mumbai Testnet. This update is NOT FOR POLYGON MAINNET.

Change log

  • Revert addition of actual miner/author address at the RPC layer for eth_getBlockByNumber calls. It will now return “0x00” as the miner of the block as it used to do earlier. You can get the miner address of a block using bor_getAuthor call. This revert was done because started breaking downstream tooling/applications which rely on the equivalence of COINBASE opcode and the miner field in response to the RPC request. The underlying miner value of the block (COINBASE) was still “0x00” and only the RPC layer had been changed earlier.
  • Updates and improvement in the description and documentation of the flags in new-cli along with their default values in the help command.
  • Pruning has been introduced in the new-cli. The internal mechanism of pruning will work in the same way as it used to with the previous versions. The command snapshot prune-state will be available as a subcommand of the bor binary and will accept relevant flags (e.g. --datadir). More details can be found here.


The instructions given below assumes that you already have v0.3.x of bor installed for mumbai testnet. If not, please find the announcement mentioning steps for the same here. Once that is installed, please follow the instructions below to upgrade to v0.3.2-mumbai.

Instructions to Upgrade

  1. Stop bor service

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

    # Replace the node type
    curl -L | bash -s -- v0.3.2-beta mumbai <node_type>
  3. Check bor version

    /usr/bin/bor version
    # It should print 
    # 0.3.2-beta
  4. Restart bor service

    sudo service bor start

Docker Images

You can find the latest docker images here:



Polygon Team