Steem EVM Is Moving Toward a Community-Driven Public Testnet
A new network infrastructure has been prepared to create a Public Testnet for SVM, created by @blaze.apps
GitHub: SteemVirtualMachine-EVM Instructions
We have our validator here and he has built it quite nicely here and the infrastructure he has built for it is working well and will play a very, very big role in creating a public test match.
The current private testnet is being deprecated and the nodes of blaze.apps are being migrated to the new network. These nodes are being migrated to a new network that will make it much smarter and we are working on making it much, much faster within that new network.
As a result, SVM is moving from a single-developer setup to a more decentralized, community-driven validator network. I did this because it is a very good initiative for us because now it needs to be much more decentralized for us and we are doing these things so that it can reach a good level.
Earlier, the plan was to use Rust-based REVM for the execution layer of SVM. This allowed us to perform much better and would have been a great way to move forward, but it didn't fit the Steem ecosystem, so we went back to Go.
Since it works so complicatedly with the Steem ecosystem, the things we can do by moving to Go are: easy integration with Steem's existing Proto definitions, more modular and maintainable architecture, easy portability in creating a Steem ↔ SVM asset bridge.
Another thing is that when we release the public test net, everything that was created in the private test net will be deleted and everything will be new in the public test net and we will be able to see everything there quite well and all the information from the private test net will be gone.
Once the network is stable, it will be deployed again:
SherpaSwap — PancakeSwap V3 fork
SherpaSwap interface — DEX frontend
BlockScout Explorer — will be connected to the new Public Testnet network