T9.3-b — The One After The Last One

Complete upgrade instructions (same as always) are live at https://medium.com/witnet/testnet-9-3-b-released-upgrade-your-witnet-node-s-now-9233e6392b92

Coordinated bootstrap

This is a coordinated scheduled network bootstrap: as soon as you run your node, it will start peering with other nodes in the network but it will not mine until the genesis checkpoint (Wednesday 23 September 2020 at 9am UTC).

Operators not using Docker need to update witnet.toml files so they look like this one.

This release bootstraps a new network with the same genesis block from 0.9.3. However, balances and reputation scores will be reset.

T9.3 — The Last One

Complete upgrade instructions (same as always) are live in https://medium.com/witnet/fc93e3e2e29f

Coordinated bootstrap

This is a coordinated scheduled network bootstrap: as soon as you run your node, it will start peering with other nodes in the network but it will not mine until the genesis checkpoint (Sept 8 at 9am UTC).

Operators not using Docker need to update witnet.toml files so they look like this one.

This release bootstraps a new network with a fresh genesis block. **Operators not using Docker DO need to make sure they are using ** the latest version of the genesis_block.json file this time (download below).

T9.2 — The One That Is More Fair

Complete upgrade instructions (same as always) are live in https://medium.com/witnet/cefd0785e00c

Coordinated bootstrap

This is a coordinated scheduled network bootstrap: as soon as you run your node, it will start peering with other nodes in the network but it will not mine until the genesis checkpoint (August 19 at 9am UTC).

Operators not using Docker need to update witnet.toml files so they look like this one.

This release bootstraps a new network with a fresh genesis block. **Operators not using Docker DO need to make sure they are using ** the latest version of the genesis_block.json file this time (download below).

T9.1 — The One Where Sybil Peers Are Rekt

Upgrade instructions (same as always) are live in https://medium.com/witnet/upgrade-your-witnet-node-to-testnet-9-now-2621e626f76b

0.9.0-d

feat(session): move feeler connection dropping logging to debug level

0.9.0-c

Blocks in 9.0c will NOT be part of the Block Counting Period.
That is, they will NOT be rewarded with Mainnet tokens.

T9.0b — The One Where We Start Counting Blocks

Upgrade instructions are live in https://medium.com/witnet/upgrade-your-witnet-node-to-testnet-9-now-2621e626f76b

T9.0 — The One Where We Failed To Bootstrap Because We Were Too Many Folks

DON'T RUN THIS RELEASE

This is the binary that was used for the failed T9.0 bootstrapping ceremony. It is kept here only for archival purposes.

The correct T9 binaries are tagged as 0.9.0-b, and available here:
https://github.com/witnet/witnet-rust/releases/tag/0.9.0-b

0.8.1-next1

This is a pre-release whose only purpose is testing the next version of the docker image.
PLEASE DON'T RUN THIS RELEASE, IT MAY CONTAIN HIGHLY UNSTABLE SOFTWARE.

T8.1 — The One That Solved Ludicrous Memory Usage

Among other improvements and fixes, this version completes the integration of the "Collaterals" feature, and hugely reduces the memory footprint of the node software, which had increased a lot with T8.0.

Remember that the recommended procedure for updating your node is this:

1. Stop your Docker container: docker stop witnet_node
2. Pulll the latest Docker image: docker pull witnet/witnet-rust
3. Start your Docker container again: docker start witnet_node

As usual, you can check that the upgrade went right with this command:

docker exec witnet_node ./witnet node --version

This is a coordinated scheduled network bootstrap: as soon as you run your node, it will start peering with other nodes in the network but it will not mine until the genesis checkpoint (May 21 at 10am UTC).

Operators not using Docker need to update witnet.toml files so they look like this one. Special attention must be given to the new public_addr, which should contain their public IP and port.

This release bootstraps a new network with a fresh genesis block that is totally empty. Operators not using Docker DO need to update the genesis_block.json file this time (download below).

Privacy considerations

This release adds automatic bug reporting (aka "telemetry") using Sentry. Every time a bug happens in your node, the trace of the error and some basic system information will be anonymously reported to the developers.

This helps the community better troubleshoot errors and will hopefully lead to a quicker and more effective improvement of the software (i.e. we'll be mainnet-ready sooner).

This feature can be disabled through the witnet.toml configuration file by setting sentry_telemetry to false or simply deleting the sentry_telemetry line.

Acknowledgements

Special thanks to everyone in the community for their eagerness and constant support for the advancement of the ecosystem.