availproject/avail v1.10.0.0

on GitHub

Important Message

This is a new binary that fixes the issues that we experienced last week. You will need to remove your existing storage database and resync from scratch. It is important to use the following flags in order for the node to pick the correct fork:

--chain goldberg \
--reserved-nodes \
"/dns/bootnode-001.goldberg.avail.tools/tcp/30333/p2p/12D3KooWCVqFvrP3UJ1S338Gb8SHvEQ1xpENLb45Dbynk4hu1XGN" \
"/dns/bootnode-002.goldberg.avail.tools/tcp/30333/p2p/12D3KooWD6sWeWCG5Z1qhejhkPk9Rob5h75wYmPB6MUoPo7br58m" \
"/dns/bootnode-003.goldberg.avail.tools/tcp/30333/p2p/12D3KooWMR9ZoAVWJv6ahraVzUCfacNbFKk7ABoWxVL3fJ3XXGDw" \
"/dns/bootnode-004.goldberg.avail.tools/tcp/30333/p2p/12D3KooWMuyLE3aPQ82HTWuPUCjiP764ebQrZvGUzxrYGuXWZJZV" \
"/dns/bootnode-005.goldberg.avail.tools/tcp/30333/p2p/12D3KooWKJwbdcZ7QWcPLHy3EJ1UiffaLGnNBMffeK8AqRVWBZA1" \
"/dns/bootnode-006.goldberg.avail.tools/tcp/30333/p2p/12D3KooWM8AaHDH8SJvg6bq4CGQyHvW2LH7DCHbdv633dsrti7i5" \
--reserved-only 

Instructions

1. Make sure that your node is not running.
2. Make sure that your db and network folder is empty. These folders you can find inside your base-path folder (Path that you used with either -d or --base-path ). Example: /opt/node-data/chains/avail_goldberg_testnet.
3. Start your node with the flags mentioned in the release. This will force the node to fetch blocks from the nodes that are on the correct chain.
4. After the sync is done, stop the node, remove the reserved-nodes and reserved-only flag and restart the node.

Avoiding full sync

Doing a full sync takes a long time to do. To make it faster you can use our existing snapshot that will cut the sync time in hours.
0. Make sure that your node is not running.

1. Make sure that your db and network folder is empty. These folders you can find inside your base-path folder (Path that you used with either -d or --base-path ). Example: /opt/node-data/chains/avail_goldberg_testnet.
2. Create a folder named full inside db, cd into it, and execute the following command inside that folder: curl -o - -L https://snapshots.avail.nexus/goldberg/avail_goldberg_testnet_snapshot_jan_31.tar.gz | tar -xz -C .
3. Start your node normally with one additional flag: --unsafe-da-sync (there is no need forreserved-nodes and reserved-only flags).
4. Once the sync is done, stop the node, remove the --unsafe-da-sync flag and restart the node.

Q: What if you don't have a db and network folder because you are running your node for the first time?
A: In Instructions ignore step 1. and start with step 2. Wait for the node to sync the first few blocks, stop the node and then normally follow the instruction for Avoiding full sync.

Q: Can I still use my existing session keys?
A: Once the sync is done, just in case, I would advise that you generate new session keys by calling the author.rotateKeys RPC (check docs for the command) and change the keys via the explorer. After that restart your node and wait 2 eras for the keys to get applied.

What's Changed

• Added fork selection for goldberg at block 344638 by @ToufeeqP in #388
• Kate Cells size is now configurable by @markopoloparadox in #383
• Replaced DenyUnsafe with a special cli flag to unable kate rpcs by @markopoloparadox in #384
• Marko/add cache size ci param by @markopoloparadox in #378
• Node version bump by @markopoloparadox in #391
• Fixed da BlockImport validation by @ToufeeqP in #392
• Fixed Multiple pending forced authority set changes are not allowed I… by @markopoloparadox in #393

Full Changelog: v1.9.0.2...v1.10.0.0