STEEM EVM Update: 212K Blocks, Proposal #7 Upgrade & SHERPA Allocation Coming Soon
Note: Upvoting and resteeming this post directly motivates me to continue building and improving the Steem Virtual Machine ecosystem. Your support is greatly appreciated!
The Steem Virtual Machine (SVM) continues to demonstrate unwavering stability, having now processed over 212,000 blocks. Today marks a pivotal moment as we prepare for our first coordinated software upgrade via Proposal #7, which will bring critical bridge improvements and set the stage for the next phase of development.
Previous Updates
Proposal #7: v0.0.2-Beta1 Upgrade & Bridge Gateway Fix
I have submitted Proposal #7, which combines two critical actions into a single on-chain governance decision:
- Software Upgrade: Schedule the
v0.0.2-Beta1binary upgrade at block height 254,132 (target date: August 4, 2026). - Bridge Parameter Fix: Correctly set the bridge gateway/deposit account to
svm.bankwith the properly formattedLegacyDecthreshold value.
Why This Matters
This proposal resolves the previous execution failure from Proposal #5 by using the correctly scaled decimal value (666666666666666667) for bridge_confirmation_threshold. It also ensures all validators upgrade to the new binary simultaneously, preventing chain splits and enabling the new bridge functionality.
Validator Action Required
If this proposal passes, validators must perform the following at halt height:
git checkout v0.0.2-Beta1
docker compose down # Do NOT use -v flag
docker compose up -d
Voting Period: Ends on 2026-08-03 at 03:52:51 UTC
You can vote via the SVM App or CLI:
SVM App Governance
Technical Post-Mortem: LegacyDec Round-Trip Fix
For transparency, I want to explain why Proposal #5 failed and how Proposal #7 fixes it.
The Root Cause:
The parameter bridge_confirmation_threshold is stored as a math.LegacyDec (18-decimal fixed-point). When queried via JSON, it outputs the raw scaled integer. My previous script fed this raw string back into MsgUpdateParams, causing the decoder to scale it by $10^{18}$ again, resulting in a value > 1 that was rejected by ValidateBasic.
The Fix:
Proposal #7 uses the correctly formatted decimal string representation, ensuring the value is interpreted properly during execution. The deposit from Proposal #5 was fully refunded since it passed voting but failed execution.
Network Health & Statistics
The blockchain remains healthy with zero downtime or consensus failures.
Current Network Stats:
- Total Blocks Produced: 212,000+
- Total Transactions: 976
- Average Daily Transactions: ~31
- Registered Addresses: 79+
- Active Validators: 11+
Upcoming: SHERPA Allocation Details
As we move past the August 1st validator deadline, I am finalizing the calculations for the 5,000,000 SHERPA genesis reward distribution.
I will be posting a detailed breakdown very soon, including:
- The final list of eligible validators.
- The exact token allocation for each participant.
- Information on how these rewards will be distributed upon the transition to the Live Public Network.
Current Validator Set
A huge thank you to all current validators for their continued uptime and support:
- @blaze.apps
- @upex
- @cur8
- @blazed007
- @steem-agora.evm
- @xpilar.witness
- @yasu
- @dhaka.witness
- @happycapital
- @steem-space
- @luxalok
How to Connect & Participate
To start interacting with the SVM or setting up your wallet:
- Network Name: Steem Virtual Machine (SVM)
- RPC URL: https://evm.blazeapps.org
- Chain ID: 8163
- Currency Symbol: STEEM
- Explorer: https://evmscan.steemscanner.com
- SVM App: https://svmapp.blazeapps.org
- Discord: https://discord.gg/xAtjgbm8Tr
Community Engagement
- Vote on Proposal #7: Ensure your validator votes before August 3rd.
- Stay Tuned: Watch for the upcoming post detailing the 5M SHERPA allocation.
- Witness Support: Your vote supports the ongoing development and infrastructure costs of the SVM.
If you value proactive engineering, UX polish, and performance optimizations for the STEEM ecosystem, please consider supporting my witness: blaze.apps
Шо тут сказать, оновлення хоч і перенеслось, проте допомогло мені, бо в скрптові на онолення не було враховано збереження даних томі. Дякую, що додали команду для оновлення, це допомогло внести корективи ☀️
0.00 SBD,
8.43 STEEM,
8.43 SP