Upgrade Proposal 1 Passed - v0.0.7 Scheduled for Block 79,664 (Critical Bridge-Out Fix)
Hi everyone,
Following our recent cross-chain withdrawal tests, we identified a specific edge case when initiating bridge-outs directly from EVM wallets like MetaMask. To resolve this, I submitted Upgrade Proposal 1, which has officially passed.
We are now scheduling a coordinated software upgrade to v0.0.7 to patch this issue before we proceed any further toward Mainnet.
⏰ Upgrade Details
- Target Block Height: 79,664
- Estimated Time: 2026-10-24 00:00 UTC
- Upgrade Type: Coordinated Software Upgrade (Cosmovisor will switch automatically at the target height).
The Technical Issue: Why v0.0.7?
During our recent testing, we noticed that bridge-outs initiated through the EVM precompile (e.g., directly from MetaMask) were failing with the error: 'is not allowed to receive funds'.
What was happening under the hood?
When cosmos/evm processes a precompile's bank transfers, it copies them into the EVM state. It is designed to skip "blocked" accounts, but it fundamentally refuses to write to a module account's balance.
In our current setup, the bridge's specific module accounts (steemblackhole and bridge_reward) were not explicitly added to the blocked list. Because the EVM state machine tried to write to these module accounts and was rejected by the bank module, the entire EVM transaction reverted.
The Fix in v0.0.7
v0.0.7 explicitly blocks every module account in x/bank, perfectly aligning our chain's behavior with upstream cosmos/evm standards. This ensures the EVM state machine correctly ignores module accounts during precompile bank transfers, allowing MetaMask bridge-outs to execute smoothly.
Important Note: This is a very clean upgrade. There are no state or parameter changes. The upgrade handler will simply run the necessary module migrations to update the blocked list in the bank module.
⚠️ URGENT: Validator Action Required
If you are running an SVM validator node, you must stage the v0.0.7 binary before block height 79,664. If your node is not updated, it will halt at the upgrade height and you will be jailed for downtime.
Staging Instructions
Please run the following commands from your SteemVirtualMachine-EVM directory immediately:
git fetch origin && git checkout release/v0.0.6 && git pull --ff-only && ./update.sh
(Note: Cosmovisor will automatically handle the binary swap exactly at block 79,664).
Verification
Once staged, you can verify the binary hash to ensure you have the correct release:
- Binary SHA256:
dce7841719984b4c385dee7f4131b6d58f424562c1c7dcdd78dafb189b0936cc
For those who have not yet applied the staging, please do so as soon as possible to ensure a seamless network transition.
Testnet Disclaimer
Important Reminder: The Steem Virtual Machine (SVM) is currently in its testnet phase. All testnet assets are purely for testing the consensus, EVM execution, and bridge layers. There is no real-world monetary value attached to this chain or its assets.
Thank you to the validator set for your rapid response to this governance proposal and your continuous dedication to keeping the SVM network secure and highly functional.
If you value proactive engineering, rigorous security standards, and transparent development for the STEEM ecosystem, please consider supporting my witness: blaze.apps
#svm #steemvirtualmachine #steemevm #upgrade #steemdev #blockchain #testnet #cosmos #validator #bridge