STEEM EVM Update: Migrating to Public Testnet
Today marks a significant transition for the Steem Virtual Machine (SVM). I have been in contact with @cur8, who has spun up a new network infrastructure that will serve as the foundation for our upcoming Public Testnet.
As part of this evolution, my current private testnet will be deprecated. I am migrating my nodes to join @cur8's network, creating a more robust and decentralized validator set. This move allows us to transition from a single-developer environment to a truly community-driven public network.
Previous Updates
- SherpaSwap: Join the Testing Phase
- SherpaSwap DEX Interface Live
- PancakeSwap V3 Deployment
- Goodbye Cosmos SDK, Hello Layer-2 on REVM
In my previous post regarding the shift to Rust's REVM, I outlined the initial performance benefits we were seeing. However, after further research and development, I have made the strategic decision to pivot back to Go.
While REVM provided excellent execution speed, the complexity of integrating it with the broader Steem ecosystem presented challenges. By returning to Go, we leverage:
- Proto Generators: Seamless integration with Steem's existing protocol buffer definitions.
- Modularity: Easier maintenance and clearer separation of concerns between the EVM layer and the base chain.
- Portability: A more straightforward path for building the bridge between Steem and the SVM, ensuring assets can move securely and efficiently.
This decision ensures that the SVM remains not just a fast execution environment, but a deeply integrated and portable layer of the Steem blockchain.
Currently, the network is secured by three validators:
This multi-node setup is the first step toward a decentralized consensus mechanism. I am actively working on onboarding additional nodes to further strengthen the network's resilience and decentralization.
Join as a Validator
We are opening the doors for more community members to run nodes and contribute to the network's security. If you are interested in becoming a validator, please refer to the detailed instructions in our GitHub repository:
GitHub: SteemVirtualMachine-EVM Instructions
To ensure a clean and stable Public Testnet, we will be performing a chain reset.
1. State Cleanup
All current data on the private testnet, including transaction history and contract states, will be wiped. This ensures that the Public Testnet starts with a fresh genesis block, free from any legacy data or potential inconsistencies.
2. Contract Redeployment
Once the new network is stable, I will redeploy the core infrastructure:
- SherpaSwap Contracts: The full PancakeSwap V3 fork.
- SherpaSwap Interface: The DEX frontend at
sherpaswap.blazeapps.org. - Block Explorer: My self-hosted BlockScout instance will be migrated to point to the new public network.
I want to extend a special thank you to the users who have been actively testing the platform, including @happycapital, @yoghurty, @steem-agora, and @blackeyedm.
Please note that your current test balances will be cleared during the reset. However, I will ensure that new test tokens are sent to your addresses once the Public Testnet is live so you can continue your testing without interruption.
Your participation is vital as we scale up.
- Run a Node: Check the GitHub instructions and help secure the network.
- Stay Tuned: Follow updates here and on Discord for the official Public Testnet launch date.
- Witness Support: Your vote supports the ongoing development and infrastructure of the SVM.
If you value proactive engineering, UX polish, and performance optimizations for the STEEM ecosystem, please consider supporting my witness: blaze.apps