Hi all, we have released a new version of heimdall-v2, v0.2.5
(ONLY FOR AMOY).
This solves a bug in an API used to fetch state syncs and also provide an endpoint for v2 version.
Steps for Upgrading Heimdall
Before proceeding, please create a backup of your heimdall
config file whose default location is: /var/lib/heimdall/config/config.toml
. This might differ if you have setup heimdall
at a different location.
-
Stop
heimdalld
servicesudo service heimdalld stop
-
Install
heimdall
with a version tag, network name (amoy), and node type (sentry or validator).# Replace the network and node type curl -L https://raw.githubusercontent.com/maticnetwork/install/heimdall-v2/heimdall-v2.sh | bash -s -- v0.2.5 <network> <node_type>
-
Check
heimdall
version/usr/bin/heimdalld version # It should print # 0.2.5
-
Restart
heimdall
servicesudo service heimdalld start
-
Restart the telemetry services
sudo service telemetry restart
What’s Changed
- clerk pagination and version endpoint by @marcello33 in #321
Full Changelog: v0.2.4…v0.2.5
WebSocket for Bor–Heimdall communication
Also, we remind you to enable WebSocket support in your bor config.toml
for the migrated amoy nodes. file. After the migration, to optimize communication between Heimdall and Bor, you can (optionally) 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.
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.
Thanks,
Polygon Team