Back to News
SVP Chain Testnet v9.10 Upgrade Announcement
Network Upgrade

SVP Chain Testnet v9.10 Upgrade Announcement

SVP Chain Testnet is scheduled to upgrade to v9.10 on September 17, 2026, from 17:00 to 20:00 (UTC+8).

v9.10 introduces two major capabilities for the SVP Chain ecosystem: the Agent Registry and UserVault workflows. Together, they add an on-chain foundation for discoverable, bonded Agents and a more complete lifecycle for user-managed trading vaults.

Upgrade Schedule

| Item | Details | | --- | --- | | Network | SVP Chain Testnet | | Version | v9.10 | | Scheduled window | September 17, 2026, 17:00-20:00 (UTC+8) |

Some Testnet services and transactions may be temporarily unavailable during the scheduled maintenance window. Please plan time-sensitive testing accordingly.

What's Included

Agent Registry

The Agent Registry makes Agents discoverable and accountable on-chain. It provides a shared registry for applications, users, and other Agents to locate services by their declared capabilities rather than relying on off-chain directories alone.

Each registered Agent has a persistent on-chain identity and can publish:

  • An owner account responsible for the Agent record
  • A reachable service endpoint
  • Capability tags for discovery and routing
  • Metadata and pricing information
  • A bond associated with the Agent's registration

Applications can query Agents by identity, owner, or capability. This makes it possible to discover the providers that advertise a particular service and then retrieve their on-chain record before interacting with them.

The registry also introduces an economic accountability model. Agent registration includes a registration fee and a bond; the initial Testnet defaults are 500 SVP for registration and a 5,000 SVP minimum bond. Agent owners can maintain their records and manage the bond lifecycle, while governance has a defined mechanism to slash an Agent when required.

UserVault Workflows

v9.10 introduces UserVault workflows for managed vault operations. A UserVault is designed to give a vault owner and its participants a structured, on-chain lifecycle for capital, trading, risk controls, and withdrawals.

The new workflows support:

  • Creating a UserVault and defining its eligible CLOB markets
  • Depositing capital into a vault and receiving vault shares
  • Manager top-ups and owner-management transitions
  • Placing and cancelling vault orders, including conditional orders
  • Reviewing vault status, performance, snapshots, and share positions
  • Requesting, amending, cancelling, and completing withdrawals
  • Settlement, capital-repair, and wind-down processes where they are required

Vault actions use current snapshot and configuration versions. This gives users and integrators a way to verify that a deposit, order, or withdrawal is being evaluated against the expected vault state rather than stale information.

Risk and Operational Controls

UserVault includes a versioned configuration model for creation, review, risk, disposition, fees, display, capacity, resource, and feature controls.

The initial configuration establishes safeguards for:

  • Minimum initial capital and NAV floors
  • Pre-review leverage, cash-ratio, and post-trade margin-buffer limits
  • Oracle freshness, order price-impact, and fair-price-deviation checks
  • Review duration, trade activity, drawdown, snapshot coverage, and exit-impact requirements
  • Withdrawal quote tolerance and maximum blocked periods
  • Per-vault subaccount and stateful-order limits
  • Performance reporting windows and stress scenarios

The configuration also enables the initial UserVault feature set for public investment, short-term orders, and native UserVault workflows. Settlement fees and the per-vault market-count limit remain disabled in the initial configuration.

Impact on Users and Integrators

  • Existing accounts, balances, positions, CLOB markets, Vaults, and Subaccounts remain available under their current interfaces.
  • Existing Vault quoting parameters and operator parameters are not reset by v9.10.
  • The Agent Registry and UserVault interfaces are additive. Existing Cosmos, EVM, and CLOB integrations can continue to use their current transaction flows.
  • Integrators that want to use the new capabilities should add support for Agent Registry queries and UserVault transaction and query workflows after the upgrade.
  • Testnet users should expect a short maintenance interruption during the announced window and should avoid time-sensitive testing until normal service has resumed.

Getting Started After the Upgrade

After v9.10 is live, developers can begin by:

  1. Registering an Agent with an endpoint, capability tags, metadata, and the required bond.
  2. Querying the registry to discover Agents by capability or owner.
  3. Creating a UserVault with an eligible market set and its initial capital.
  4. Using UserVault deposit, order, review, performance, and withdrawal flows in Testnet applications.

Detailed API references, client examples, and feature-specific integration guidance will be shared through SVP Chain's official documentation and community channels.

Important Notes

  • v9.10 is a Testnet upgrade. Developers should validate Agent and UserVault integrations in Testnet before relying on them in production-facing applications.
  • The announced window is for network maintenance. Availability may vary while the upgrade is being completed.
  • Feature defaults and governance-controlled settings are subject to future Testnet governance decisions.

Follow SVP Chain's official channels for status updates, documentation, and follow-up integration information.

Back to All News