Bor v2.2.3-beta release for Amoy

Announcements
1

Hi all, we have released a new version of bor, v2.2.3-beta

These releases include a fix for state sync fetching from heimdall-v2.

Only install on Amoy nodes (post heimdall migration).

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.2.3-beta <network> <node_type>

  3. Check bor version

    /usr/bin/bor version

# It should print 
# v2.2.3-beta

  4. (if not done already) Enable websockets for bor-v2 comms. Edit your bor config.toml file and add the following under the [heimdall] section:

    [heimdall]
ws-address = "ws://localhost:26657/websocket"

  5. Restart bor service

    sudo service bor start

Docker Images

You can find the latest docker images here:

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

Why WebSockets for Bor–Heimdall communication?

By default, bor polls heimdall-v2 by using frequent HTTP requests, which can be inefficient.

In step 4 we reminded you to enable WebSocket support in your bor config.toml for the migrated amoy nodes. file. This is because, after the migration, to optimize communication between Heimdall and Bor, you can enable WebSockets. By default, heimdall-v2 polls bor by using frequent HTTP requests, which can be inefficient. Enabling WebSocket support reduces overhead and improves sync responsiveness.

If not done yet, edit your bor config.toml file and add the following under the [heimdall] section:

[heimdall]
ws-address = "ws://localhost:26657/websocket"

This assumes Heimdall-v2 is running with its WebSocket endpoint enabled on port 26657.

Adjust the port or host if your setup differs.

After updating, restart your Bor node to apply the new configuration.

2

Isn’t it the other way around? Bor polls heimdall-v2 by RPC calls on port 1317, and setting this parameter has Bor use WS instead, on a different port?

1 Like
3

You’re right - Bor polls Heimdall-v2 via RPC (usually port 1317) by default. Enabling WebSocket in Bor’s config switches communication to use WS on port 26657, which is more efficient and reduces overhead. This update in v2.2.3-beta improves sync speed and responsiveness for Amoy nodes post-migration. Just make sure Heimdall’s WS endpoint is active on the specified port, then restart Bor to apply the change. It’s a smart optimization to replace frequent HTTP polling with a persistent WebSocket connection.