📣 Good morning dear Friends! A few words about the main mission and rules of this channel

🚀 Channel mission:
- Inform validators about changes in evernode

❗️Our rules:
- No ads
- Only important information for evcerscale validators
- Evernode updates notifications
- Evernode changelogs

😉 Stay tuned and have a good day!

📣 Imprortant news about the changelog updates

#evernode_update #evernode_changelog
Node Version: 0.50.5
Tools version: 0.1.262
Block version: 22

❗️Important❗️

DB restoring is mandatory while deploying this node version to fix internal DB data errors that happened earlier. For the correct update:

1. Change the “restore_db” key value from “false” to “true” at the very end of the config.json file (node config file)
2. Stop the node
3. Update the node image
4. Restart the node

❗️DB restoration may take time (1 hour or more)❗️

🛠Changelog
- New ZEROROTRIF instruction
ZEROROTRIF (x y – x y or 0 x y), pushes a Zero under the second stack entry from the top, but only if the topmost Integer y is non-zero.

- New ZEROROTRIF2 instruction
ZEROROTRIF2 (x y – x y or 0 0 x y), pushes two Zeros under the second stack entry from the top, but only if the topmost Integer y is non-zero. Equivalent to ZEROROTRIF; ZEROROTRIF.

- New ZEROROTRIFNOT instruction
ZEROROTRIFNOT (x y – x y or 0 x y), pushes a Zero under the second stack entry from the top, but only if the topmost Integer y is zero.

- New ZEROROTRIFNOT2 instruction
ZEROSWAPIFNOT2 (x – x or 0 0 x), pushes two Zeros under the topmost Integer x, but only if x = 0. Equivalent to ZEROSWAPIFNOT; ZEROSWAPIFNOT.

- New ZEROSWAPIF instruction
ZEROSWAPIF (x – x or 0 x), pushes a Zero under the topmost Integer x, but only if x <> 0.

- New ZEROSWAPIF2 instruction
ZEROSWAPIF2 (x – x or 0 0 x), pushes two Zeros under the topmost Integer x, but only if x <> 0. Equivalent to ZEROSWAPIF; ZEROSWAPIF.

- New ZEROSWAPIFNOT instruction
ZEROSWAPIFNOT (x – x or 0 x), pushes a Zero under the topmost Integer x, but only if x = 0.

- New ZEROSWAPIFNOT2 instruction
ZEROSWAPIFNOT2 (x – x or 0 0 x), pushes two Zeros under the topmost Integer x, but only if x = 0. Equivalent to ZEROSWAPIFNOT; ZEROSWAPIFNOT.

- Disabled setlibcode, changelibcode instruction

- Validator not validating in some cases fix

- Security fix for ADNL packet signature

- Improved DB restoration

- Fixed several bugs (storage fee calculation, storing last state of validator)

Many thanks to EverX for the Changelog

😉 Stay tuned and have a good day!

❗️Important❗️
Don't upgrade your nodes!

At the moment, a new version of the ever node is being tested.

⚡️ We will publish information on the test result:
- commit ID
- Node Version
- Tools version
- Block version

😉 Stay tuned and have a good day!

#evernode_update #evernode_changelog
Commit ID: 51f91af8269e648ff7b3f4a80f2eff0d1e5d831d
Node Version: 0.50.13
Tools version: 0.1.262
Block version: 26

❗️Important❗️
Please update your nodes strictly one at a time! Until one finishes updating completely, it is forbidden to run the other one!



1. Build node.
2. Restart the node


🛠Changelog
node from 0.50.5 to 0.50.13 diff

adnl from 0.7.67 to 0.7.69 diff

ever-crypto from 0.1.7 to 0.1.17 diff

overlay from 0.6.50 to 0.6.52 diff

rldp from 0.7.61 to 0.7.63 diff

ton_block_json from 0.7.5 to 0.7.11 diff

ton_executor from 1.15.57 to 1.15.64 diff

ton_types from 1.10.12 to 1.10.14 diff

ton_block from 1.7.39 to 1.7.43 diff

ton_vm from 1.8.32 to 1.8.33 diff

ton_abi from 2.1.14 to 2.2.1 diff

ton_labs_assembler from 1.2.31 to 1.2.34 diff

dht from 0.5.62 to 0.5.64 updated dependencies only
ton_api from 0.2.120 to 0.2.123 updated dependencies only

😉 Stay tuned and have a good day!

#evernode_changelog

Node Version: 0.50.21
Tools version: 0.1.280
Block version: 30

🛠Changelog

evernode tools from 0.1.262 to 0.1.280
🔹Minor update and update dependencies

evernode from 0.50.13 to 0.50.21
🔹Block version up to 30
🔹Support TIP-1.1 COPYLEFT
🔹CapFullBodyInBounced (return full body for bounces messages) in development
🔹CapStorageFeeToTvm (return storage fee value) in development
🔹Fix and refactoring evernode stopping by SIGINT
🔹Node stopping delay up to 1000 milliseconds from 100 milliseconds
🔹Check max part size for partially transmitted data like archives and states
🔹Change node statuses (get it from evernode tools console):
🔹🔹Rename finish boot to finish_boot
🔹🔹Rename synchronization by blocks to synchronization_by_blocks
🔹🔹Rename synchronization finished to synchronization_finished
🔹🔹Rename no set status to no_set_status
🔹🔹Add checking_db
🔹🔹Add db_broken
🔹New optional flag for evernode
🔹🔹force_check_db - start check & restore db process forcely
🔹Add DB versions. Preview version 0, current version 1DB updated automatically when node started
🔹Option

adnl.set_options(AdnlNode::OPTION_FORCE_COMPRESSION)

ON in evernode version 0.50.21

ton_vm from 1.8.33 to 1.8.38
🔹Add benchmarks
🔹Add instructions
🔹🔹INITCODEHASH 256 bit hash of code cell with contract was deployed
🔹🔹STORAGEFEE collected storage fee from account in this transaction
🔹🔹SEQNO current sequence number of collating block
🔹🔹FIND_BY_INIT_CODE_HASH the list of accounts with initial code hash
🔹🔹FIND_BY_CODE_HASH list of accounts with code hash
🔹🔹FIND_BY_DATA_HASH list of accounts with data hash
🔹🔹TRYELECT executes try_elect method for accounts got by config param 30
🔹🔹COPYLEFT Add license payment to code creator.

overlay from 0.6.52 to 0.6.58
🔹Fixes

rldp from 0.7.63 to 0.7.68
🔹Add several logs

ton_abi from 2.2.1 to 2.2.8
🔹Fixes

ton_api from 0.2.123 to 0.2.128
🔹Add data for RempMessageStatus

ton_block from 1.7.43 to 1.7.51
🔹Support global config 42 (TIP-1.1 COPYLEFT)

ton_block_json from 0.7.11 to 0.7.18
🔹Remp
🔹Global config 30
🔹Global config 42 (TIP-1.1 COPYLEFT)

ton_executor from 1.15.64 to 1.15.72
🔹Add benchmarks, support global config 42 (TIP-1.1 COPYLEFT)

ton_types from 1.10.14 to 1.11.2
🔹Boc ser/deserialisation with safe aborting

adnl from 0.7.69 to 0.7.74 updated dependencies only
dht from 0.5.64 to 0.5.68 updated dependencies only
ever-crypto from 0.1.17 to 0.1.24 updated dependencies only
lockfree no changes

#evernode_update

📣 Dear validators, an important node update is ahead.

❗️Important❗️

During this update, the node will be inoperable and stop validation for an hour or more.

To maintain network health, follow these rules:
▫️ Do not update more than one node at a time.
▫️ After updating the node and restoring timediff, wait 6 hours before updating the next one.
▫️ Inform the RU EN validators chat about the beginning and completion of the node update.

⚠️ Attention: if a large number of nodes are updated at the same time, this may lead to network instability. Be careful when updating.

📌 Update Instructions
‼️ Attention: do not update the next node until the previous one has worked successfully for 6 hours.‼️

If you use @Custler scripts
1️⃣ They will automatically pick up a convenient update time and update your node
2️⃣ If the database cannot recover on its own and the node goes to the db_broken status, the script PostUpdate_Actions.sh running automatically and resync database

For manual updates
1️⃣ build the node and the tools
Node commit id:
5c3951a4de03833a49079d1c07ad5a05798df169
Node Tools commit id:
a69b0c4b8fe2c95eaea4145dffba9734d8570070
2️⃣ Start a new node (~ 1 hour)
The node will start restoring the database and stop validation
The node gives the status

"sync_status":  "checking_db"

3️⃣ If the node has restored the database successfully It will sync the blocks that were missed while restoring the database (~30 minutes)
4️⃣ Node start validation and do some checks (~30 minutes)
5️⃣ Node save new DB state. The node stop validation and resync (~30 minutes)
6️⃣ Node sync the blocks and restore validation

‼️ Attention: do not update the next node until the previous one has worked successfully for 6 hours. ‼️

⚠️ If the recovery failed and the node switched to the status

"sync_status":  "db_broken"

In this case, you need to delete the old database and synch with the network again.
Full sync time more than 12 hours

❓How to check node status?
./console -C /path/to/console.json -c "getstats"

💬 Need help? Ask it in RU EN

✅ Our goal is the stable operation of the network!