On October 15, 2026, KR1 launched dedicated Ethereum validators in a Lido stVault operated by P2P.org, with a near-term target of staking up to 6,000 ETH. The Lido announcement says the rollout starts with 10 validators and depends on Ethereum’s validator entry queue. It does not give a date for reaching the target.
KR1 is a London Stock Exchange-listed onchain infrastructure company. Under the arrangement, P2P.org runs the dedicated stVault while KR1 retains control of deposits, withdrawals, the validator fee arrangement, and the vault’s roles and permissions. KR1 can also mint $stETH against assets in the vault when it wants liquidity.
The structure separates three functions that pooled liquid staking normally combines. KR1 chooses the validator operator, controls the vault, and decides whether to create a liquid staking token position. P2P.org handles validator operation. Lido’s contracts provide the vault and the route for optional $stETH minting.
How the stVault changes KR1’s staking position
Direct Ethereum staking gives the owner operator choice, but withdrawn capital must pass through Ethereum’s exit queue. Lido says that queue can take weeks when demand to exit rises. Traditional liquid staking supplies immediate liquidity, while operator selection and validator performance are pooled across many participants.
The stVault gives KR1 a third configuration. The company can keep validator selection and attribution inside a dedicated vault, then mint $stETH against the staked assets if it needs a liquid token. The Lido documentation describes stVaults as isolated, non-custodial staking primitives that preserve operator choice and optional access to $stETH liquidity.
Optional minting matters because it is a separate decision from depositing $ETH into the vault. KR1 can stake through its selected operator without automatically turning the entire position into $stETH. If it mints, the resulting $stETH or wrapped $wstETH can be used in DeFi while the underlying $ETH continues earning validator rewards. Lido describes both assets as broadly supported across DeFi, but the announcement does not identify any protocol where KR1 plans to deploy them.
The choice changes what KR1 must manage. A vault that has minted $stETH needs health monitoring, repayment controls, and rebalancing, all of which Lido assigns to the vault owner. KR1 can trigger validator withdrawals when it wants to move toward an exit, although the native queue still determines how quickly that exit clears. If KR1 chooses not to mint, it keeps the dedicated operator arrangement without creating the liquid asset described in the announcement. The published terms therefore make liquidity optional at the vault level, not an automatic result of staking.
Validator attribution also remains specific to the vault. The pooled route averages validator performance across a broad set, while the dedicated route preserves the outcome associated with the selected operator. That gives KR1 a clearer operating boundary around P2P.org’s validators. It also means the arrangement does not spread operator selection across the wider pool in the way the traditional liquid staking model does.
KR1 also controls the vault’s validator fee terms and permissions. Those controls determine who can perform actions around the vault rather than leaving every operating decision to a common pool. The announcement says the owner can supply or withdraw $ETH, mint or repay $stETH, monitor vault health, trigger validator withdrawals, rebalance, and disconnect from Lido.
That final option defines the boundary of the arrangement. KR1 is using Lido V3 contracts and P2P.org operations, but the vault design leaves the owner with a route to exit the protocol. The announcement does not disclose KR1’s fee agreement with P2P.org, its intended reserve settings, or how much $stETH it expects to mint.
Controls and risks around the rollout
The dedicated structure does not remove Ethereum staking risk. Lido explicitly says standard staking risks apply and warns that audits, bug bounties, and operating controls reduce risk without eliminating protocol or market losses. A dedicated vault also concentrates operator selection in the choice made by its owner. KR1 therefore keeps control over that choice and bears the consequences of how the selected validator setup performs.
Lido lists security reviews by Certora, MixBytes, Consensys Diligence, Composable Security, Ackee Blockchain, and Sigma Prime. It also points to an ongoing Immunefi program with rewards of up to $2M. These are controls around the software, not guarantees for KR1’s stake. The announcement acknowledges that unidentified risks may remain.
Vault health adds another operating constraint when the owner mints $stETH. Lido’s documentation tells vault owners to monitor parameters and metrics, manage minting, and handle withdrawals. The announcement names repayment and rebalancing among the actions under owner control. KR1 will therefore have more discretion than a holder in the pooled product, along with the work of managing those controls.
The initial 10-validator deployment is smaller than the stated target and gives the parties a first operating stage. Expansion depends on the validator entry queue, so the target is not a committed completion date. The source also does not state how much $ETH entered the vault at launch, which validators are active, or the fee rate P2P.org will receive.
For KR1, the practical change is access to validator-specific staking without giving up the option to create a liquid DeFi asset. For other stakers, the launch provides a public example of a listed company choosing a dedicated Lido V3 vault instead of using only direct staking or the pooled Lido route. It does not establish that the same fee, permission, or operator terms are available to another vault owner.
The next observable milestone is movement beyond the initial 10 validators toward the target of up to 6,000 ETH. The timing remains tied to Ethereum’s entry queue, and neither KR1 nor Lido has published a completion date or a planned $stETH minting amount.
