MultiversX Validators Announcements
582 subscribers
60 photos
4 videos
686 links
MultiversX Validators can get all the relevant information here.
Download Telegram
πŸ“£  DEVNET Upgrade for the hardfork1 event D1.6.13.2-hf1

Hello Validators,

We are upgrading the DEVNET. We upgrade the nodes and we try to execute the hardfork event.
This version D1.6.13.2-hf1 contains custom code for this event (to ignore the blocks generated on the other fork) and also new configs so the nodes can connect on the new network as we hane created a new network for this fork.

- For validators that do not care about their local data/history: perform a clean db operation, upgrade and start. It's the easiest way
- For observers that preserve all data or validators that should contain all data perform these steps:
1. download the DB archives from here:
https://elrond-mainnet-db-archive.fra1.digitaloceanspaces.com/elrond-public-devnet/devnet-1694000000/14-Jan-2024/DevNet-Full-History-DB-Shard-0.tar.gz
https://elrond-mainnet-db-archive.fra1.digitaloceanspaces.com/elrond-public-devnet/devnet-1694000000/14-Jan-2024/DevNet-Full-History-DB-Shard-1.tar.gz
https://elrond-mainnet-db-archive.fra1.digitaloceanspaces.com/elrond-public-devnet/devnet-1694000000/14-Jan-2024/DevNet-Full-History-DB-Shard-2.tar.gz
https://elrond-mainnet-db-archive.fra1.digitaloceanspaces.com/elrond-public-devnet/devnet-1694000000/14-Jan-2024/DevNet-Full-History-DB-Shard-metachain.tar.gz
2. replace your nodes DBs with the downloaded ones
3. upgrade your nodes to have their configs/binary to the released one
4. either set in the config.toml file the flag StartInEpochEnabled to false or set in the prefs.toml the FullArchive flag to true
5. start the node(s)
- For Elastic Search DB maintainers, be sure that you remove all the data from the other fork by using the script found in this message: https://xn--r1a.website/MultiversXValidators/212687

πŸ“… There is no activation epoch for this release

⚠️  Do not upgrade your mainnet validators! You risk getting jailed and jeopardizing the mainnet.

🧩 Compatible services:
- proxy: v1.1.43
- notifier: v1.2.3

πŸ‘‰  Let’s upgrade our DEVNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
cd ~/mx-chain-scripts
./script.sh remove_db
./script.sh upgrade
./script.sh start

πŸ›   It's time to build.

🌐  Devnet Explorer | Devnet Wallet | Setup a Devnet Validator
πŸ“£  TESTNET Upgrade T1.6.14.0

Hello Validators,

We are upgrading the TESTNET. We upgrade the nodes and KEEP the database.
- This version T1.6.14.0 brings the reactivation of the faulty MigrateDataTries builtin function along with other fixes found on the v1.6.13 of the node.

πŸ“… The activation epoch is set to 745 which should happen on January 26, 2024, ~15:30

⚠️  Do not upgrade your mainnet validators! You risk getting jailed and jeopardizing the mainnet.

🧩 Compatible services:
- proxy: v1.1.43
- notifier: v1.2.3

πŸ‘‰  Let’s upgrade our TESTNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
cd ~/mx-chain-scripts
./script.sh upgrade
./script.sh start

πŸ›   It's time to build.

🌐  Testnet Explorer | Testnet Wallet | Setup a Testnet Validator
πŸ“£  TESTNET Upgrade T1.6.15.0

Hello Validators,

We are upgrading the TESTNET. We upgrade the nodes and KEEP the database.
- This version T1.6.15.0 brings another fix for the redundancy system found after testing the v1.6.14 release.

πŸ“… There is no activation epoch for this release

⚠️  Do not upgrade your mainnet validators! You risk getting jailed and jeopardizing the mainnet.

🧩 Compatible services:
- proxy: v1.1.43
- notifier: v1.2.3

πŸ‘‰  Let’s upgrade our TESTNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
cd ~/mx-chain-scripts
./script.sh upgrade
./script.sh start

πŸ›   It's time to build.

🌐  Testnet Explorer | Testnet Wallet | Setup a Testnet Validator
πŸ“£  DEVNET Upgrade D1.6.15.0

Hello Validators,

We are upgrading the DEVNET. We upgrade the nodes and KEEP the database.
- This version D1.6.15.0 brings a patch of fixes found after the the v1.6.13 release.

πŸ“… The activation epoch is set to 852 for the MigrateDataTrie functionality.

⚠️  Do not upgrade your mainnet validators! You risk getting jailed and jeopardizing the mainnet.

🧩 Compatible services:
- proxy: v1.1.43
- notifier: v1.2.3

πŸ‘‰  Let’s upgrade our DEVNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
cd ~/mx-chain-scripts
./script.sh upgrade
./script.sh start

πŸ›   It's time to build.

🌐  Devnet Explorer | Devnet Wallet | Setup a Devnet Validator
πŸ“£ MAINNET Upgrade v1.6.15.0

Hello Validators,

We are upgrading the MAINNET!

This version v1.6.15.0 is out πŸ”₯. We call it Sirius Patch 4.

ℹ️ This release addresses some fixes after the launch of the v1.6.13.0 version. It enables the MigrateDataTrie functionality. The release notes can be found here:
https://multiversx.com/release/release-sirius-patch-4-v1-6-15

πŸ’»Please make sure you upgrade your host's operating system if you are running on older versions of Ubuntu. The recommendation from the official docs is Ubuntu 22.04. Some issues were found on hosts running Ubuntu 18.04 that prevented the correct setup of the new version of the node.

🧩 Compatible services:
- proxy: v1.1.43
- notifier: v1.2.3

πŸ‘‰ Actions needed:
❗️please upgrade your nodes as soon as possible.

πŸ“… The activation flag is set to epoch 1293 which should happen on Tuesday, February 13, 2024 ~16:05 UTC

Configuration release notes: https://github.com/multiversx/mx-chain-mainnet-config/releases/tag/v1.6.15.0

πŸ‘‰ Let’s upgrade our MAINNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
./script.sh upgrade
./script.sh start


πŸ›  It’s time to build.

Retweet: https://twitter.com/lucianmincu/status/1753125115636662272

🌐Explorer | Wallet | Setup a Mainnet Validator
πŸ“£  TESTNET Upgrade T1.6.16.0

Hello Validators,

We are upgrading the TESTNET. We upgrade the nodes and KEEP the database.
- This version T1.6.16.0 brings a performance degradation fix found after testing the v1.6.15 release, among with other minor improvements.

πŸ“… There is no activation epoch for this release

⚠️  Do not upgrade your mainnet validators! You risk getting jailed and jeopardizing the mainnet.

🧩 Compatible services:
- proxy: v1.1.43
- notifier: v1.2.3

πŸ‘‰  Let’s upgrade our TESTNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
cd ~/mx-chain-scripts
./script.sh upgrade
./script.sh start

πŸ›   It's time to build.

🌐  Testnet Explorer | Testnet Wallet | Setup a Testnet Validator
πŸ“£  DEVNET Upgrade D1.6.16.0

Hello Validators,

We are upgrading the DEVNET. We upgrade the nodes and KEEP the database.
- This version D1.6.16.0 brings a patch of fixes found after the v1.6.15.0 release.

πŸ“… There is NO activation epoch

⚠️  Do not upgrade your mainnet validators! You risk getting jailed and jeopardizing the mainnet.

🧩 Compatible services:
- proxy: v1.1.44
- notifier: v1.2.3
-indexer: v.4.18

πŸ‘‰  Let’s upgrade our DEVNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
cd ~/mx-chain-scripts
./script.sh upgrade
./script.sh start

πŸ›   It's time to build.

🌐  Devnet Explorer | Devnet Wallet | Setup a Devnet Validator
πŸ“£  TESTNET Upgrade T1.7.4.0

Hello Validators,

We are upgrading the TESTNET. We upgrade the nodes and KEEP the database.
- This version T1.7.4.0 brings the staking v4 feature.

πŸ“…  Staking v4 activation will begin tomorrow, February 20th ~08:00 UTC. Final phase should be active at ~12:00 UTC.

⚠️  Do not upgrade your mainnet validators! You risk getting jailed and jeopardizing the mainnet.

🧩 Compatible services:
- proxy: v1.1.45-sp4
- notifier: v1.2.3
- indexer: v1.4.18

πŸ‘‰  Let’s upgrade our TESTNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
./script.sh upgrade
./script.sh start

πŸ›   It's time to build.

🌐  Testnet Explorer | Testnet Wallet | Setup a Testnet Validator
πŸ“£  TESTNET Upgrade T1.7.5.0

Hello Validators,

We are upgrading the TESTNET. We upgrade the nodes and KEEP the database.
- This version T1.7.5.0 enables the vm-queries on historical data.

πŸ“…  There is no activation epoch for this release.

⚠️  Do not upgrade your mainnet validators! You risk getting jailed and jeopardizing the mainnet.

🧩 Compatible services:
- proxy: v1.1.45-sp4
- notifier: v1.2.3

πŸ‘‰  Let’s upgrade our TESTNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
./script.sh upgrade
./script.sh start

πŸ›   It's time to build.

🌐  Testnet Explorer | Testnet Wallet | Setup a Testnet Validator
πŸ“£  DEVNET Upgrade D1.6.17.0

Hello Validators,

We are upgrading the DEVNET. We upgrade the nodes and KEEP the database.
- This version D1.6.17.0 enables the vm-queries on historical data.

πŸ“… There is NO activation epoch

⚠️  Do not upgrade your mainnet validators! You risk getting jailed and jeopardizing the mainnet.

🧩 Compatible services:
- proxy: v1.1.44
- notifier: v1.2.3
- indexer: v1.4.18

πŸ‘‰  Let’s upgrade our DEVNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
./script.sh upgrade
./script.sh start

πŸ›   It's time to build.

🌐  Devnet Explorer | Devnet Wallet | Setup a Devnet Validator
πŸ“£  TESTNET Upgrade T1.7.6.0

Hello Validators,

We are upgrading the TESTNET. We upgrade the nodes and KEEP the database.
- This version T1.7.6.0 brings a minor fix on deep vm-queries.

πŸ“…  There is no activation epoch for this release.

⚠️  Do not upgrade your mainnet validators! You risk getting jailed and jeopardizing the mainnet.

🧩 Compatible services:
- proxy: v1.1.46
- notifier: v1.2.3
- indexer: v1.4.19

πŸ‘‰  Let’s upgrade our TESTNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
./script.sh upgrade
./script.sh start

πŸ›   It's time to build.

🌐  Testnet Explorer | Testnet Wallet | Setup a Testnet Validator
πŸ“£  DEVNET Upgrade D1.6.18.0

Hello Validators,

We are upgrading the DEVNET. We upgrade the nodes and KEEP the database.
- This version D1.6.18.0 brings a minor fix on deep vm-queries.

πŸ“… There is NO activation epoch

⚠️  Do not upgrade your mainnet validators! You risk getting jailed and jeopardizing the mainnet.

🧩 Compatible services:
- proxy: v1.1.44
- notifier: v1.2.3
- indexer: v1.4.19

πŸ‘‰  Let’s upgrade our DEVNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
./script.sh upgrade
./script.sh start

πŸ›   It's time to build.

🌐  Devnet Explorer | Devnet Wallet | Setup a Devnet Validator
πŸ“£ MAINNET Upgrade v1.6.18.0

Hello Validators,

We are upgrading the MAINNET!

This version v1.6.18.0 is out πŸ”₯. We call it Sirius Patch 5.

ℹ️ This release addresses some fixes after the launch of the v1.6.15.0 version along with the possibility to run historical vm-queries. The release notes can be found here:
https://multiversx.com/release/release-mx-chain-go-sirius-patch-5

πŸ’»Please make sure you upgrade your host's operating system if you are running on older versions of Ubuntu. The recommendation from the official docs is Ubuntu 22.04. Some issues were found on hosts running Ubuntu 18.04 that prevented the correct setup of the new version of the node.

🧩 Compatible services:
- proxy: v1.1.44
- notifier: v1.2.3
- out-of-process-ES-indexer: v1.4.19

πŸ‘‰ Actions needed:
❗️please upgrade your nodes as soon as possible.

πŸ“… There is no activation flag for this release

Configuration release notes: https://github.com/multiversx/mx-chain-mainnet-config/releases/tag/v1.6.18.0

πŸ‘‰ Let’s upgrade our MAINNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
./script.sh upgrade
./script.sh start


πŸ›  It’s time to build.

Retweet: https://twitter.com/lucianmincu/status/1767981856044064932

🌐Explorer | Wallet | Setup a Mainnet Validator
πŸ“’ Announcement: Battle of Stakes πŸ₯© - Staking V4 Testing Campaign

GM MultiversX Builders,

As previously mentioned, we announce the upcoming "Battle of Stakes," the much-anticipated testing campaign for Staking V4.

This campaign aims to provide equal opportunities for all participants, ensuring fairness and transparency throughout. To achieve this, we will be resetting the testnet on Monday, March 25th. This reset will ensure that every participant starts on a level playing field, maximizing the integrity of the testing environment.

Leading up to the reset, we will be sharing all needed information about the Battle of Stakes campaign. This will include details on eligibility, registration procedures, and the rules governing participation. Stay tuned for updates!

We understand the importance of maintaining ongoing projects and commitments within the community. If any builder currently has tests running on the testnet or anticipates any disruptions due to the reset, we encourage you to raise the issue. Your input is valuable, and we are committed to addressing any concerns promptly.

The time for Staking V4 has come, let's make the best of it.

Let's build better together! βš’πŸš€
πŸ“£  TESTNET Reset: T1.6.18.0 - Remove DB

Hello Validators,

We are resetting the TESTNET and bringing it in line with mainnet.

πŸ“… The genesis timestamp is 1711375200 which should happen on Monday, March 25, 2024 14:00:00 UTC
β€’ 1 testnet epoch = 2 hours
β€’ unbonding period = 2400 rounds / 2 epochs / 4 hours
β€’ all features activate in epoch 1

⚠️  Do not upgrade your mainnet validators! You risk getting jailed and jeopardizing the mainnet.

🧩 Compatible services:
- proxy: v1.1.44
- notifier: v1.2.3
- indexer: v1.4.19

πŸ‘‰  Let’s upgrade our TESTNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
./script.sh stop
./script.sh remove_db
./script.sh upgrade
./script.sh start

πŸ›   It's time to build.

🌐  Testnet Explorer | Testnet Wallet | Setup a Testnet Validator
Calling all MasterChef Validators! πŸ§‘β€πŸ³

As always, the validators community is surpassing expectations, receiving over 100 registrations for the Battle of Stakes campaign! However, not all entries were valid. 🍳 Some lacked that special ingredient - contact details (to contact you in case of further investigations are needed). We've prepared a list of participants missing either their Telegram ID or Email. Check it out and make sure your entry is complete at
- https://docs.google.com/spreadsheets/d/1ac08N6TMYWg_o-KAWmNj3xFetf710LhwX7t4s-VJhjQ/edit?usp=sharing.

Without this, we can't serve you your share of xEGLD!

πŸ”₯ Hot Off the Grill: We've noticed a high number of questions coming our way. A key flavor we want to add to the mix: consider forming Staking Providers rather than going at it alone with individual nodes.

⏰ The xEGLD distribution will take place today between 12:00 UTC - 16:00 UTC. If your address is on the list above, bring in your missing details to ensure you receive your xEGLD. The clock's ticking, and we want everyone to enjoy their rightful piece of the pie.

We're here to help with any questions or support you might need. Thank you to every validator who's thrown their steak in the ring. The testnet grill is fired up, and we're just hours away from those stakes starting to sizzle. Stay tuned for more juicy details coming your way soon.
πŸ“£  TESTNET Upgrade T1.7.7.0

Hello Validators,

We are upgrading the TESTNET. We upgrade the nodes and KEEP the database.
- This version T1.7.7.0 brings the staking v4 feature.

πŸ“…  Staking v4 activation will begin today, March 28th ~20:00 UTC. Final phase should be active at ~00:00 UTC March 29th.

⚠️  Do not upgrade your mainnet validators! You risk getting jailed and jeopardizing the mainnet.

🧩 Compatible services:
- proxy: v1.1.47
- notifier: v1.2.3
- indexer: v1.4.21

πŸ‘‰  Let’s upgrade our TESTNET VALIDATORS. Please do:

cd ~/mx-chain-scripts
./script.sh github_pull
./script.sh upgrade
./script.sh start

πŸ›   It's time to build.

🌐  Testnet Explorer | Testnet Wallet | Setup a Testnet Validator
πŸš€ xEGLD Distribution Announcement πŸš€
The distribution of xEGLD is set to begin shortly!
Please be reminded that in order to receive your xEGLD, it is essential that your registration includes either a Telegram ID, an email, or a valid erd1... address. Unfortunately, we will not distribute funds to participants who have not provided one of the aforementioned pieces of information. This is to ensure fairness and efficiency in the distribution process.
If you have yet to update your details, please do so at the earliest convenience to secure your xEGLD before the activation epoch (39).
PS: Registrations remain open throughout the entire competition, but it is recommended to participate from the start. If you have any issues you can go to discord and discuss the topic in the open thread or here in Telegram. You can also DM the team for information (Iulian, Mihai)
Let's heat up the testnet!
πŸŽ‰ 2nd wave of xEGLD Distribution πŸŽ‰

Things are heating up, validators! Since the first wave of xEGLD distribution, we're welcoming 42 new participants to the campaign. We'll do the distribution to the newcomers in the next few minutes. Welcome aboard!

Important update regarding registrations: While we initially planned to keep registrations open throughout the entire campaign, we've revised this approach. Registrations will now close as soon as staking v4 becomes active - Testnet Epoch 39.

Stay tuned for more updates! πŸ‘€πŸ‘€
πŸ›  Testnet Reset Announcement βš’

Dear Validators,

We have encountered an unexpected bug, a situation that has introduced the need for some additional rules and has forced us to remove certain participants. To ensure the integrity and success of Battle of Stakes campaign, we've decided to reset the testnet. We aim to relaunch, refreshed and improved, by Monday at the latest.

What can you expect? New rules that refine our process and an enhanced testnet environment that leverages the lessons learned. This reset is a step towards ensuring a robust and effective platform for all involved.

We understand this sudden pause might come as a surprise, but it already ensures a better Vega release. We're committed to keeping you informed and will share updates as soon as they're available.

Thank you for your understanding and support through this adjustment. The path to improvement is sometimes unpredictable, but it's always forward. For the next restart we will use the already registered participants which means that you won't have to complete the form again.

Stay tuned for a stronger restart!