Bump avail-subxt from v1.6.3 to v1.11.0.0

[dependabot]

Bumps avail-subxt from v1.6.3 to v1.11.0.0.

Release notes

Sourced from avail-subxt's releases.

v1.11.0.0

Important Message

This is a required update in order to be able to participate on the Goldberg testnet

This is a important binary upgrade that needs to be done in the next 48 hours. This is a new binary that fixes header commitments not being correctly calculated and adds new bootnodes to the chainspec.

Make sure that you do NOT use the reserved-nodes nor reserved-only flags. They were supposed to be only used to sync up the node up till the latest block and afterwards they need to be removed.

Full Changelog: availproject/avail@v1.10.0.0...v1.11.0.0

v1.10.0.0

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

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. 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.
3. 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.

... (truncated)

Commits

• 38304bb Added more bootnodes to goldberg
• d508963 Switched core from goldberg branch to tag
• 17ee755 Node and Spec Bump
• 38044d4 Fixed e2e tests
• 3f01dd1 Added support for V3 for js and deno
• dafb096 format
• e5f91be Update function ids and verification key for Dencun upgrade. (#401)
• 5b52fee Added HeaderVersion V3
• 64f9a4b Fixed header generation problem with wrong commitments
• b514ad4 Fixed Multiple pending forced authority set changes are not allowed I… (#393)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.