On October 28, 2026, custodian BitGo and Solana’s Jupiter aggregator announced a shared validator that lets eligible institutions delegate SOL to a staking validator without moving the asset out of their existing custody account. The Jupiter x BitGo validator pairs Jupiter’s validator operations with BitGo Bank & Trust, an OCC-regulated national trust bank, as the custody layer. The validator is aimed at eligible institutional clients rather than retail users.
Why the trade-off exists
Native Solana staking requires a holder to delegate SOL to a validator. In practice that has meant using a wallet, a staking provider, or a second custody relationship outside the incumbent custodian’s control. For a compliance team, earning yield then competes with keeping assets inside a regulated custody arrangement. The BitGo and Jupiter pairing removes that choice by keeping delegation inside the existing custody workflow. Alternatives such as lending SOL or holding a liquid staking token carry their own custody, credit, or conversion risks, which is why a direct delegation path has appeal.
How Solana staking works
Solana’s proof-of-stake mechanism routes delegation through stake accounts. A holder delegates SOL to a validator’s vote account, and the stake becomes effective only after a warmup period. The network limits how quickly stake can activate or deactivate, currently about 25% of total stake per epoch. An epoch is the network’s accounting window of roughly two to three days. Rewards accrue against the effective portion of the stake and are paid out at the end of each epoch.
Unstaking reverses the flow with a cooldown. After a holder requests deactivation, the stake ramps down over the cooldown period before the balance can be withdrawn. The protocol imposes that delay, and it applies wherever the stake is delegated from.
What custody-native staking changes
The integration removes the step of moving SOL to an external staking provider, but it does not change the underlying economics or risks. Jupiter operates the validator independently, and BitGo has said it does not control validator performance. Staking rewards remain variable and are not guaranteed; they depend on network conditions and how the validator performs. Access is limited to eligible clients, and BitGo has not published fee terms, so institutions will need to confirm those details directly.
Delegated SOL stays under BitGo’s custody rather than transferring to Jupiter, which settles the question of who holds the keys. Staking still carries protocol-level risks: validator downtime or underperformance, possible penalties such as slashing if the network adopts them, and the chance that the asset itself loses value. BitGo’s insurance program covers up to $250 million subject to policy terms and exclusions, but it does not insure against every loss and is not a guarantee of staking rewards.
What to check before relying on it
For an institution evaluating the option, the practical questions are eligibility, fee structure, and the deactivation timeline under Solana’s protocol rules. BitGo notes that the entity providing services depends on the client’s jurisdiction, so custody treatment may differ across institutions.
Source: BlockchainReporter.