SVM Testnet Update: 573K+ Blocks, 11/11 Validators Online, and Proposal 4 (v0.0.5 Upgrade) Live
Hi everyone,
The Steem Virtual Machine (SVM) testnet continues to operate in excellent health. We have reached another significant milestone, and with the network running at full capacity, we are now initiating the next coordinated software upgrade to further harden the chain and restore key functionality.
Network Health and Current Metrics
The SVM testnet is running flawlessly. The chain continues to produce blocks at a highly consistent rate, and the active validator set is maintaining perfect consensus stability.
Current Testnet Statistics:
- Total Blocks Produced: 573,478+
- Total Transactions: 42,662+
- Average Block Time: ~5.3 seconds
- Active Validators: 11 / 11 (100% Online)
Governance Alert: Proposal 4 (v0.0.5 Upgrade)
I have just submitted Proposal 4, a coordinated software upgrade to v0.0.5. This upgrade introduces critical validator identity hardening, re-enables EVM staking with proper safeguards, and hardcodes the 1 gwei gas floor into the chain parameters.
Proposal Details:
- Proposal Link: View Proposal 4 on SVM Scan
- Voting Ends: 2026-10-01 16:59:35
- Target Upgrade Block Height: 620,500
What is Changing in v0.0.5?
- Validator Identity Hardening: Every route to creating or editing a validator now strictly enforces the Steem-identity rule. This requires an ACTIVE Steem name owned by the validator, with owner, active, and posting keys properly registered in the details. This enforcement now applies universally: direct transactions, authz, interchain accounts (ICA), and the EVM staking precompile.
- EVM Staking Precompile Re-enabled: The staking precompile (
0x0000000000000000000000000000000000000800) is switched back ON, but now with the Steem-identity check built directly into it. This restores the ability to delegate and manage validators directly from MetaMask and other EVM wallets, which was temporarily disabled in Proposal 3 because it previously bypassed this critical check. - 1 Gwei Gas Floor: The 1 gwei minimum EVM gas price, previously set via parameter change, now becomes a permanent, hardcoded part of the chain's logic.
Note: Your keys, stake, and existing validator identities are completely untouched by this upgrade.
Validator Action Required: Pre-Staging the v0.0.5 Binary
This is a coordinated, state-breaking upgrade. Every validator must stage the new binary before the chain reaches block height 620,500.
Important: If you previously staged a v0.0.5 binary before September 29, you must run the staging commands again, as the binary has been updated.
Staging Instructions (via Cosmovisor / Docker)
From your SteemVirtualMachine-EVM directory, run the following:
# 1. Fetch the latest code and checkout the release branch
git fetch
git checkout release/v0.0.5-validator-identity
# 2. Run the automated update script to stage the binary
./update.sh
Verification Details:
- Docker Image:
steemblazer/steemvmd:v0.0.5 - Staged Binary SHA256:
5915bf669c390d3f6e08c81961d8aec2818145e1a9155e26a88b080a507d334f
For comprehensive, step-by-step instructions, please refer to the official documentation:
🔗 Instructions/UPGRADE_v0.0.5.md
Detailed Upgrade Guide Coming to EVM Community
To ensure all operators have the exact voting commands, troubleshooting steps, and cosmovisor configuration details, I will be posting a comprehensive v0.0.5 Voting and Upgrade Guide on the EVM Community (hive-196634) shortly. Please keep an eye on that tag for the full technical breakdown.
Testnet Disclaimer
Important Reminder: The Steem Virtual Machine (SVM) is strictly in its testnet phase. All bonded STEEM, transactions executed, and tokens generated are purely for testing the consensus and EVM execution layers. There is no real-world monetary value attached to this chain or its assets.
Reaching over 573,000 blocks with 100% validator participation is a massive achievement. Thank you to all 11 operators for your unwavering dedication, prompt updates, and commitment to maintaining a secure and efficient SVM network.
Please cast your vote on Proposal 4 and begin staging your binaries as soon as possible.
If you value proactive engineering, rigorous security standards, and transparent development for the STEEM ecosystem, please consider supporting my witness: blaze.apps