Everscale's Core Development Strategy Report 🚀

A new report about key results and main updates in the Everscale development process was published in the Everscale blog.

Soft Majority Fault Tolerance (SMFT)

Current status:

• The testnet is up using 20 servers
• With a constant, small load, the network drops intermittently
• The issue of the election process is being resolved

Short-term plans:

• Maintaining a constant workload for testing purposes
• Tests and fixes
• Development of arbitration (underway)
• Deployment for public tests

Reliable External Message Protocol (REMP)

Current status:

• REMP is being merged with the RFLD network
• Works well at 500 TPS
• Load testing

Short-term plans:

• Merging REMP with temp_rc
• Starting public tests
• High load testing of REMP
• Everscale node development

Everscale node development

Current status:

• New block version: 35 (optimizations and minor fixes)
• REMP prep and testing

Short-term plans:

• Deploying the current version
• Work on sending bounce messages
• Сlearance of old materials due to rebranding
• Decreasing the network’s gas fees

🔗 To read the full report

#remp #smft #review #post

Soft Majority Fault Tolerance (SMFT) 📝

Wishing to improve the security of the Everscale network, while keeping it fast and decentralized enough, Mitya Goroshevsky described the SMFT consensus protocol, his vision of solving several problems of the original Nikolai Durov protocol.

The problems SMFT is trying to solve:

🔴Security of block generation in tracks and finality: validators can release an incorrect block if 2/3+1 of them conspire

🔴Fixing screwed up state: Nikolai Durov suggested using vertical blocks to fix contracts, but their implementation is complicated and requires changes not only in node software, but in other parts of the network as well

🔴Problems in DeFi: lack of finality can cause problems for many DeFi services, such as bridges, and fixing through vertical blocks will no longer be possible

How SMFT solves these problems with verifiers:

🟢Blocks must collect 50% + 1 BLS signatures of the entire workchain to be included in the master, which guarantees their availability

🟢Verifiers verify blocks and send ACK or NACK to the masterchain

🟢In case of NACK, the block is checked by the whole masterchain, and invalid blocks lead to a slash of validators who signed it, sent an ACK, or went silent

🟢Every N blocks, validators must reveal their keys to determine which blocks they should have checked

🟢If a block takes a long time to verify, the verifiers send a timeout, and if several timeouts are set, the block is verified by the masterchain. This allows you to determine the required number of verifiers for each block and eliminate the chance of an attack

🟢SMFT also offers simplification of BFT in a validation session or abandonment of it in favor of selecting a random block maker verified by verifiers to speed up block release

Overall, SMFT is an Everscale innovation that raises the fault tolerance bar to 50% (vs. 33% consensus BFT), which is the maximum level of security in decentralized systems.

#ever #smft #education #post