A new Steem Virtual Machine (SVM) v0.0.3 Bridge Oracle update is now available.

All SVM validators listed below are requested to update to the latest version and complete the new validator setup.

@blaze.apps
@upex
@cur8
@blazed007
@steem-agora
@xpilar.witness
@yasu
@dhaka.witness
@happycapital
@steem-space
@luxalok
@justyy

🚨 IMPORTANT — READ BEFORE STARTING

This update creates a new SVM wallet address for your validator.

Your existing SVM wallet address will not be reused.

The first step also removes the existing Docker containers and volumes so that the new validator setup starts with a clean environment without stale chain data.

If you have anything important inside your existing SVM Docker volumes, back it up before continuing.

---

1. Stop SVM and remove stale Docker data

Go to your SVM repository:

cd /home/SteemVirtualMachine-EVM

Stop the SVM Docker services and remove their associated volumes:

docker compose down -v

This removes the containers and the Docker volumes associated with the Compose project.

Remove any remaining unused Docker volumes

You can then clean up unused Docker volumes:

docker volume prune -a

Docker will ask for confirmation.

Are you sure you want to continue? [y/N]

Enter:

y

⚠️ IMPORTANT

docker volume prune -a is a destructive cleanup command.

It can remove unused Docker volumes from other applications on the server, not just SVM.

If the server runs other Docker applications, do NOT blindly run docker volume prune -a.

Instead, identify the SVM volume first:

docker volume ls

Then remove only the old SVM volume:

docker volume rm <SVM_VOLUME_NAME>

The goal is to make sure there is no stale SVM chain/validator data remaining before running the new validator setup.

---

2. Fetch the latest SVM code

From:

cd /home/SteemVirtualMachine-EVM

Fetch the latest changes:

git fetch

Then checkout the Bridge Oracle branch:

git checkout -b feat/v0.0.3-bridge-oracle origin/feat/v0.0.3-bridge-oracle

If you already have the branch locally:

git checkout feat/v0.0.3-bridge-oracle
git pull

---

3. Run the new validator setup

Run:

sh new-validator.sh

The script will ask for your moniker.

Use your Steem username as the moniker.

The script will then fetch your live Steem public keys and display them for confirmation.

If the keys are correct, simply press:

Y

to accept them.

The script will use these keys when configuring your new SVM validator.

---

4. CoinMarketCap API key is required

The Bridge Oracle requires a CoinMarketCap API key.

You can create a free CoinMarketCap account and generate an API key here:

https://coinmarketcap.com/api/dashboard/api-keys/

Have your API key ready before running the validator setup.

---

5. The script will build the chain and create a new wallet

The new-validator.sh script will build the required SVM components and create your new validator wallet.

🚨 IMPORTANT — YOUR WALLET ADDRESS WILL CHANGE

This update will reset your current SVM wallet setup and create a new wallet address.

Your old SVM wallet address will not be reused by the new validator setup.

Please make sure you understand this before proceeding.

---

6. SAVE YOUR MNEMONIC

During the setup, the script will display your new wallet's mnemonic phrase.

🚨 VERY IMPORTANT

COPY AND SAVE THE MNEMONIC PHRASE IN A SAFE PLACE.

This is your wallet recovery phrase.

Do not:

• Share it with anyone
• Post it publicly
• Put it in Discord or Telegram
• Commit it to GitHub
• Include it in screenshots
• Store it somewhere accessible to other users

Keep it somewhere secure.

---

7. If you missed copying the mnemonic

If you accidentally missed copying the mnemonic, don't panic.

The generated Oracle private key is also available on the validator server in:

SteemVirtualMachine-EVM/oracle/.env

Look for:

ORACLE_PRIVATE_KEY=25.....6C09

The value above is only an example.

You can inspect the file with:

cat oracle/.env

🔐 SECURITY WARNING

The ORACLE_PRIVATE_KEY is a private credential.

NEVER share your actual private key with anyone.

Do not publish it in a Steemit post, GitHub repository, Discord, Telegram, screenshots, logs, or support messages.

Anyone who obtains the private key may be able to control the associated wallet.

The mnemonic should be your preferred backup, but the private key can provide a recovery option if you forgot to save the mnemonic.

---

8. Register your new SVM wallet

After creating the wallet, the script will save your new validator address and display instructions to send 0.001+ STEEM from your Steem account to svm.bank.

The memo must be exactly as generated by the script.

For example:

✔ Address saved to validator-address.txt

==> Send 0.001+ STEEM from 'xpilar.witness' to 'svm.bank',
memo EXACTLY:

svm-register steem1ykn5qzmtv2r5kfr3f3zar3keqs2v2pk7tl480x

⚠️ Do NOT use the address from this example.

The SVM address shown above is only an example.

Use the exact address generated by your own validator setup.

Also make sure the registration memo is copied exactly.

---

9. Let the setup script finish

After the registration transaction is detected, the script will continue with the remaining validator setup and configuration.

Please do not interrupt the script unless necessary.

The complete setup script is available here:

https://github.com/blazeapps007/SteemVirtualMachine-EVM/blob/feat/v0.0.3-bridge-oracle/new-validator.sh

Validators are encouraged to review the script before running it.

---

Validator Update Checklist

Before starting the update, make sure you have:

• Your Steem username
• Your CoinMarketCap API key
• Access to your validator server
• A secure place to save your new mnemonic
• A backup of anything important from your existing validator environment

After running the script:

• Confirm your Steem public keys
• Save the new mnemonic
• Record your new SVM validator address
• Send the required 0.001+ STEEM registration transaction
• Use the exact svm-register memo generated by the script
• Never share your ORACLE_PRIVATE_KEY

---

Final Notice to All SVM Validators

Please update your validator to the latest SVM v0.0.3 Bridge Oracle version.

Start by removing the old SVM Docker environment and stale volumes, then fetch the latest code and run the new validator setup.

Remember:

New code → Clean Docker environment → New wallet → Save mnemonic → Register wallet → Complete validator setup

This update creates a new SVM wallet address, so do not assume that your previous SVM wallet address will remain the same.

If you missed the mnemonic during setup, the Oracle private key can still be found in:

SteemVirtualMachine-EVM/oracle/.env

under:

ORACLE_PRIVATE_KEY=...

Keep this key private and secure.

Thank you to all SVM validators for keeping the network running and helping us move forward with the new Bridge Oracle, SBD bridging, price feeds, and validator accountability infrastructure.