version bump

streamr-dev · Jan 22, 2024 · d7d87b5 · d7d87b5
1 parent b865418
commit d7d87b5
Show file tree

Hide file tree

Showing 4 changed files with 15 additions and 15 deletions.
diff --git a/docs/docs/guides/how-to-run-streamr-node.md b/docs/docs/guides/how-to-run-streamr-node.md
@@ -50,7 +50,7 @@ Start the Config Wizard with the below command. Docker will download the node im
 #### Run the config wizard (Linux / macOS instructions)
 
 ```
-sudo docker run -it -v $(cd ~/.streamrDocker && pwd):/home/streamr/.streamr streamr/broker-node:v100.0.0-testnet-three.0 bin/config-wizard
+sudo docker run -it -v $(cd ~/.streamrDocker && pwd):/home/streamr/.streamr streamr/broker-node:v100.0.0-testnet-three.1 bin/config-wizard
 ```
 
 #### **Windows PowerShell instructions**
@@ -64,7 +64,7 @@ cd ~/.streamrDocker
 Then run the Config Wizard:
 
 ```
-docker run -it -v ${pwd}:/home/streamr/.streamr streamr/broker-node:v100.0.0-testnet-three.0 bin/config-wizard
+docker run -it -v ${pwd}:/home/streamr/.streamr streamr/broker-node:v100.0.0-testnet-three.1 bin/config-wizard
 ```
 
 #### Using the Config Wizard
@@ -88,7 +88,7 @@ If you're running a node to become an Operator, then you could now jump back to
 #### Linux / macOS instructions
 
 ```
-sudo docker run -p 32200:32200 --name streamr --restart unless-stopped -d -v $(cd ~/.streamrDocker && pwd):/home/streamr/.streamr streamr/broker-node:v100.0.0-testnet-three.0
+sudo docker run -p 32200:32200 --name streamr --restart unless-stopped -d -v $(cd ~/.streamrDocker && pwd):/home/streamr/.streamr streamr/broker-node:v100.0.0-testnet-three.1
 ```
 
 #### Windows PowerShell instructions
@@ -99,7 +99,7 @@ First move into your node's folder:
 cd ~/.streamrDocker
 ```
 ```
-docker run -p 32200:32200 --name streamr --restart unless-stopped -d -v ${pwd}:/home/streamr/.streamr streamr/broker-node:v100.0.0-testnet-three.0
+docker run -p 32200:32200 --name streamr --restart unless-stopped -d -v ${pwd}:/home/streamr/.streamr streamr/broker-node:v100.0.0-testnet-three.1
 ```
 
 **The `docker run` command, deconstructed:**
@@ -232,7 +232,7 @@ For extra logging on your Streamr node, add the `LOG_LEVEL` environmental variab
 
 For example,
 ```shell
-sudo docker run -p 32200:32200 --name streamr --restart unless-stopped -d -e LOG_LEVEL=trace -v $(cd ~/.streamrDocker && pwd):/home/streamr/.streamr streamr/broker-node:v100.0.0-testnet-three.0
+sudo docker run -p 32200:32200 --name streamr --restart unless-stopped -d -e LOG_LEVEL=trace -v $(cd ~/.streamrDocker && pwd):/home/streamr/.streamr streamr/broker-node:v100.0.0-testnet-three.1
 ```
 
 ## Mumbai node config

diff --git a/docs/docs/guides/how-to-update-your-streamr-node.md b/docs/docs/guides/how-to-update-your-streamr-node.md
@@ -10,7 +10,7 @@ Keeping your node up to date is very important as new releases contain bug fixes
 This guide is meant for Linux and MacOS. Windows Powershell commands will be slightly different.
 :::
 
-To update your Streamr node from `v100.0.0-testnet-two.0` to `v100.0.0-testnet-three.0` (for example), run:
+To update your Streamr node from `v100.0.0-testnet-two.0` to `v100.0.0-testnet-three.1` (for example), run:
 
 ```
 sudo docker stop streamr && sudo docker rm streamr && sudo docker container prune --force
@@ -30,7 +30,7 @@ sudo docker rmi IMAGE_ID
 Run your updated node with the new node version,
 
 ```
-sudo docker run -p 32200:32200 --name streamr --restart unless-stopped -d -v $(cd ~/.streamrDocker && pwd):/home/streamr/.streamr streamr/broker-node:v100.0.0-testnet-three.0
+sudo docker run -p 32200:32200 --name streamr --restart unless-stopped -d -v $(cd ~/.streamrDocker && pwd):/home/streamr/.streamr streamr/broker-node:v100.0.0-testnet-three.1
 ```
 
 Your updated node will now be running. As usual, you can checkup on it with 

diff --git a/docs/docs/streamr-testnets/testnet-faq.md b/docs/docs/streamr-testnets/testnet-faq.md
@@ -11,18 +11,18 @@ If you’ve been running a Streamr node in the past you might be familiar with a
 - You can run ~~up to 5 nodes per IP address~~ any number of nodes from the same IP address, although one node per machine is recommended
 - Rewards are ~~automatically paid out at the beginning of the following month~~ claimed from active Sponsorships at any time
 - You can stake ~~up to 20K DATA per node~~ as much as you want. Note that at least 5% of Operator stake must come from the owner, and therefore delegations can not exceed 95%.
-- To participate in the testnets, use specific versions/tags of the Streamr node software, such as `v100.0.0-testnet-three.0`. The `latest` tag still points to the previous milestone (Brubeck) software.
+- To participate in the testnets, use specific versions/tags of the Streamr node software, such as `v100.0.0-testnet-three.1`. The `latest` tag still points to the previous milestone (Brubeck) software.
 - There is no need for a "beneficiary address" in Streamr 1.0. Instead, the node configuration contains the Operator contract address.
 :::
 
 #### Migrating from the Mumbai testing environment to Stream 1.0
 If you've created your node in the Mumbai testing environment and you want to participate in the incentivized testnets with real token rewards and risks, then you'll need to recreate your Operator using the Streamr Network [Hub](https://streamr.network/hub/network/operators). The same funding and pairing steps that you did for your Mumbai Operator need to be repeated here too. The testnets and the future 1.0 mainnet will run on the Polygon Blockchain.
 
-- **Node version:** The `pretestnet` tagged releases shouldn't be used anymore, instead use `v100.0.0-testnet-three.0`. 
+- **Node version:** The `pretestnet` tagged releases shouldn't be used anymore, instead use `v100.0.0-testnet-three.1`. 
 - **Node config:** Your node config should resemble the [Testnet 1 config template](../guides/become-an-operator.md#testnet-node-config).
 
 #### What are the differences between the "pretestnet" and Testnet 1?
-This `v100.0.0-testnet-three.0` version can be used to connect to Testnet 1 **or** the Mumbai testing environment. 
+This `v100.0.0-testnet-three.1` version can be used to connect to Testnet 1 **or** the Mumbai testing environment. 
 
 The active network depends on the node config. The [Mumbai node config](../guides/become-an-operator.md#the-mumbai-test-environment) is unchanged. The [Testnet 1 config](../guides/become-an-operator.md#testnet-node-config) is a much shorter version.
 
@@ -153,7 +153,7 @@ Add given nodes public key to operator node addresses.
 I’m receiving the following warning message.
 
 ```JSON
-INFO [2023-11-10T10:52:30.450] (broker              ): Start broker version v100.0.0-testnet-three.0
+INFO [2023-11-10T10:52:30.450] (broker              ): Start broker version v100.0.0-testnet-three.1
 Error: call revert exception [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (method="metadata()", data="0x", errorArgs=null, errorName=null, errorSignature=null, reason=null, code=CALL_EXCEPTION, version=abi/5.7.0)
 ```
 

diff --git a/docs/docs/streamr-testnets/testnets.md b/docs/docs/streamr-testnets/testnets.md
@@ -24,7 +24,7 @@ To earn DATA tokens on Polygon you must be willing to hold and stake DATA tokens
 :::
 
 ## Current node software version
-Use node version: `v100.0.0-testnet-three.0`. Do not use the `latest` tag release.
+Use node version: `v100.0.0-testnet-three.1`. Do not use the `latest` tag release.
 
 ## Schedules
 Keep a close eye on this page as these dates may change based on the findings of each testnet.
@@ -42,10 +42,10 @@ Keep a close eye on this page as these dates may change based on the findings of
 - **Testnet 2 will have reduced slashing penalties of 0.01% instead of 10%**
 
 ### Testnet 3
-- Start date: 22nd January to 5th February (tentative)
+- Start date: 25th January to 8th February (tentative)
 - Reward pool: 2.5 million DATA
 - Duration: 14 days
-<!-- - **Testnet 3 will have slashing penalties of 0.1%. This penalty has been increased since the last Testnet.** -->
+- **Testnet 3 will have slashing penalties of 0.1%. This penalty has been increased from Testnet 2.**
 
 ### Mainnet launch
 - Coming soon after the completion of **Testnet 3**
@@ -59,7 +59,7 @@ The [Mumbai Hub](https://mumbai.streamr.network) is the place to test out your O
 You'll need Mumbai `MATIC` - widely available with [public faucets](https://mumbaifaucet.com) and you'll need ` TEST` tokens (the Mumbai network's worthless `DATA` tokens) - There is a `TEST` token faucet on the [Streamr Discord](https://discord.gg/gZAm8P7hK8).
 
 **What are the differences between Mumbai and Testnet 1?**
-This `v100.0.0-testnet-three.0` version can be used to connect to Testnet 1 **or** the Mumbai network. 
+This `v100.0.0-testnet-three.1` version can be used to connect to Testnet 1 **or** the Mumbai network. 
 
 The active network depends on the node config. The [Mumbai node config](../guides/become-an-operator.md#the-mumbai-test-environment) is unchanged. The [Testnet 1 config](../guides/become-an-operator.md#testnet-node-config) is a much shorter version.