SVM Testnet Update : Network Health, Validator Status & Sherpa Ahead
The main point of this update is that the SVM Testnet is very close to 200K blocks, as well as clarifying the reasons for failed transactions and validator sync status.
Current status of the SVM Testnet
The SVM Testnet is still consistently producing blocks and the v0.0.4.x security and maintenance patches are working as expected.
Statistics
- Total Blocks: 199,920+
- Total Transactions: 8,893
- Average Block Time: ~5.3 seconds
- Active Validators: 9 / 12
This means that SVM is now only a few dozen/hundred blocks away from the 200,000-block milestone.
Why are Failed Transactions happening?
Although the network is seeing a relatively high number of failed transactions, this is not a bug. This is the expected behavior of the SVM security model.
The SVM v0.0.4 architecture has strict validation on bridge data and oracle attestations.
Currently, some validators are jailed, so their Oracle client can run in the background and try to submit data to the network.
But the network correctly rejects:
Bridge data
Oracle attestations
Price-feed submissions
of jailed validators.
As a result, these are shown as failed transactions.
What is the purpose of ####?
This security mechanism ensures that only:
Active validators
Compliant validators
Fully synced validators
can affect the bridge state and Oracle price feeds.
This protects the network from stale or unauthorized data.
Validator Status
Currently 9 out of 12 registered validators are active.
These 9 validators:
Fully updated
Fully synced
Participating in Consensus
Performing Oracle duties
However, two validators are still jailed:
Due to their jailed status, their validator cannot contribute to the network and their Oracle submissions are being rejected.
Next Goal: Sherpa Protocol Deployment
After SVM crosses the 200,000-block milestone, the next big goal is deployment and testing of Sherpa Protocol smart contracts.
Sherpa Protocol will experimentally add to the SVM ecosystem:
DeFi Capabilities
Trading Features
Liquidity Features
Smart Contract-Based Applications
However, before Sherpa Protocol can be successfully and securely deployed, bringing the validator set back to full capacity is crucial.
So the current goal is to:
- Fully update all validators
- Keep all nodes fully synced
- Deploy the latest Oracle version
- Unjail jailed validators
- Restore the validator set to maximum capacity
Once the validator network is fully restored, Sherpa Protocol deployment and testing will proceed as the next important development phase for SVM.