Vultisig Weekly Update — July 3, 2026

Vultisig’s next wave of updates is about giving users more ways to use their assets—and more control over how every transaction is executed.

Native staking is expanding, swaps are becoming more intelligent, and advanced users are gaining finer control through custom RPC endpoints and new swap settings. At the same time, work across the SDK and Vultisig clients is making balances faster to load, fees easier to understand and transactions more reliable across devices.

Here is what is coming to Vultisig.

Platform Snapshot

The latest all-time platform figures show continued growth across the ecosystem:

• 248,772 iOS impressions

• 10,655 iOS downloads

• 37,646 Android downloads

• 9,550 extension installs

• $106.67M in total swap volume

• $515.6K in total fees generated

More than $106 million has now been swapped through Vultisig. That growth reflects an increasingly capable product: one vault for holding, exchanging and managing assets across chains without giving up custody.

Native Staking Is Expanding

Native staking for Solana and TON is coming to Vultisig.

Users will be able to stake assets and manage the full staking lifecycle from within the Vultisig experience. For Solana, that includes delegating SOL, unstaking and withdrawing completed stake—all while keeping control through the vault.

The underlying Solana staking transaction builder has already been added to the Vultisig SDK. Building this functionality at the SDK level creates a common foundation that can be used across Vultisig clients rather than tying staking to a single device or platform.

TON staking is also on the way, extending Vultisig’s native DeFi capabilities into another major ecosystem.

This is part of a broader direction for the product. Vultisig is becoming more than a secure place to hold and swap assets. It is becoming a vault from which users can actively manage them.

Smarter Swap Routing with SwapKit

Vultisig’s swap experience is also getting more intelligent beneath the surface.

Upcoming routing improvements will use live pool data to determine whether assets are currently eligible for swaps through THORChain and Maya Protocol. This replaces static assumptions with decisions based on the liquidity that is actually available.

User-selected slippage will be passed correctly to SwapKit, ensuring the routing layer respects the parameters chosen in Vultisig. Gas costs will also play a role when comparing close alternatives. A marginally better quote is not truly better if the additional execution cost outweighs the difference.

Jupiter is being added as a Solana swap provider, bringing greater routing depth to swaps within the Solana ecosystem. CowSwap RFQ support is also part of the recent desktop expansion, opening another source of competitive execution for supported assets.

The aim is straightforward: offer the best practical route, not simply the most attractive number before fees.

Advanced Swap Gives Users More Control

Advanced Swap introduces a more configurable experience for users who want greater control over transaction execution.

The new interface includes market and limit modes, configurable slippage, adjustable gas limits and the option to send the output of a swap directly to an external address.

External recipients are particularly useful when the destination asset does not need to return to the initiating vault. A user can complete a swap and direct the resulting assets to another wallet or recipient as part of the same flow, removing an unnecessary follow-up transaction.

Advanced settings are available through the applicable VULT tier, giving qualifying users access to finer transaction controls while keeping the standard swap experience straightforward for everyone else.

Custom RPC Endpoints

Custom RPC endpoints are coming for users at the Silver VULT tier and above.

By default, a wallet connects to blockchains through predefined RPC providers. Custom RPC support allows a user to replace those defaults with an endpoint of their choice on supported chains.

For most people, the standard infrastructure remains the simplest option. For advanced users, teams and professional operators, choosing an RPC endpoint provides an additional layer of control over reliability, privacy and infrastructure dependencies.

It is a technical feature with a clear philosophical fit: self-custody should extend beyond control of the keys to meaningful control over how the vault interacts with the network.

Faster EVM Balance Loading

Multi-chain portfolios can create a heavy workload behind the scenes. A vault containing many EVM assets may need to make a separate network request for each token before the complete portfolio can appear.

Upcoming improvements will batch EVM balance requests through Multicall3. Multiple token balances can be retrieved together, reducing the number of calls required to load a vault.

Balance retrieval is also being separated from price fetching. On-chain balances will not need to wait for fiat pricing information before they can be displayed.

The implementation may be invisible, but the result should be noticeable: quicker and more dependable portfolio loading, particularly for vaults containing a large number of tokens.

Clearer Costs Before Signing

Good self-custody depends on informed approval. Users should understand both the transaction and its cost before they sign it.

Fiat values are being added to the send flow so that the initiator and co-signer can review the monetary value of a transaction at the point of approval.

Affiliate fees will also be shown on the swap overview, making the cost of a route clearer before confirmation. For assets priced below one cent, a new subscript format will make long strings of leading zeros easier to read.

Fee calculation is improving for Akash and Cosmos as well. Dynamic fees will combine a safe minimum with gas limits derived from transaction simulation, producing estimates that are more closely aligned with the transaction being prepared.

These changes all serve the same purpose: less ambiguity at the moment a user is being asked to sign.

Deeper Multi-Chain Support on Desktop

Recent desktop work significantly expands what users can do across Solana, Sui and Cosmos.

Solana gains batch signing and sending, allowing multiple operations to be handled more efficiently. Sui support now includes custom tokens as well as dApp transaction and message signing through MPC.

The Vultisig extension can decode Sui programmable transaction blocks and use Blockaid to present clearer intent information for swaps and sends. Instead of exposing users only to raw transaction data, the extension can provide a more understandable view of what a connected application is asking the vault to approve.

Cosmos SDK staking has also been added to the DeFi experience. Keplr support now includes transaction broadcasting and ADR-36 arbitrary-message signing, while minimum-fee handling has been improved for Cosmos transactions.

Ethereum wallet permissions round out the expansion, giving connected applications a clearer and more familiar way to request account access.

The latest extension improvements are included as part of the desktop release rather than a separate extension release.

A Stronger Foundation for Cross-Device Signing

Many Vultisig features depend on multiple devices independently constructing and approving the same transaction. That makes consistency at the SDK level essential.

The latest SDK work aligns Terra Classic gas handling across clients, reducing the risk of different devices producing mismatched transaction payloads during co-signing.

Cardano transactions gain native CIP-20 memo support through WalletCore auxiliary data. Solana transactions will surface the rejection reason returned by the network when a broadcast fails, replacing a generic failure with information that users and support teams can act on.

Contract preflight checks have also been strengthened, helping detect potential failures before a transaction reaches the signing stage.

These improvements are not the most visible part of a release, but they are central to making a multi-device vault feel dependable.

Security and Everyday Usability

The release cycle also includes a series of smaller changes that make Vultisig safer and easier to use.

Passcode-based encryption has been strengthened with PBKDF2, adding a more robust key-derivation process to the protection of locally encrypted data.

MLDSA keys will be visible in vault details, giving users a clearer view of their post-quantum security configuration. When a vault already contains an MLDSA-44 key, Vultisig will no longer display an irrelevant option to add another one.

Dense QR codes will be easier to scan through an expanded, full-width view. Receive addresses can also be shared as QR images, making it easier to move address information between applications and devices.

The local joining flow on iPad is being improved with clearer network handling and a direct retry option. Promotional banner dismissal will become time-based, allowing important future notices to return without repeatedly showing messages a user has already dismissed.

Individually, these are modest refinements. Together, they make the product feel more predictable—and predictability matters when real assets are involved.

A Vault Designed to Do More

This release cycle brings several parts of Vultisig’s longer-term direction into focus.

Native staking is expanding across chains. SwapKit routing is becoming more responsive to live liquidity and real execution costs. Advanced Swap and custom RPC endpoints are giving experienced users greater control. Underneath it all, the SDK is creating a more consistent foundation across clients and devices.

Vultisig began with a clear proposition: strong self-custody without seed phrases or a single point of failure. The next step is to make that security genuinely useful across the full life of a multi-chain portfolio.

The vault should not only protect assets. It should give their owner better ways to manage them, move them and put them to work.