DVT Staking API for Ethereum Validators
Four operators, no SSV token overhead
P2P.org's DVT Staking API gives exchanges, custodians, and staking platforms distributed validator technology via SSV Network, with validator keys split across four independent operators and three of four required to keep a validator running. Non-custodial throughout. Two integration paths are available: SSV 1.0 direct, or SSV 3.1 with no SSV token management.
DVT Staking API Specs
The 32 ETH minimum applies per validator. Cluster composition and operator distribution are managed by P2P.org and documented in the SSV integration guides.
Independent operators
4 per cluster
Resilience
3-of-4 threshold
SSV 3.1 Integration
Tokenless
Pectra compatibility
0x02 ready
Transaction signing
Client-side
Uptime SLA
99.9%
Security & Compliance
How the DVT Staking API Works
The DVT Staking API constructs and returns unsigned transactions for interacting with P2P.org's SSV proxy smart contract or the native SSV Network. The client signs and broadcasts the transaction. P2P.org manages validator registration on the SSV protocol.
Request the deposit transaction
Send a POST request to the DVT Staking API with the stake amount, withdrawal address, and fee recipient address. The API returns a serialized unsigned transaction for the deposit.
Sign and broadcast
Sign the transaction with the client's existing key management or custody solution and broadcast it to Ethereum. The smart contract deposits the stake and registers validators on SSV.
Monitor validator status
After the deposit confirms, the validators enter the Ethereum activation queue. Monitor validator status, deposit history, and staking activity via the API status endpoints.
SSV 1.0 VS SSV 3.1
Two Ways to Integrate DVT Staking
SSV 1.0: Direct Integration
Direct integration with the SSV network's native staking architecture. Full control over the staking process without relying on P2P.org's proxy smart contract. Requires managing SSV tokens to maintain validators on the network.
Best for
- Teams that require alignment with native SSV staking architecture
- Platforms that prefer to minimize smart contract dependencies
- Developers requiring fine-grained control over validator count and effective balance
- Consideration: requires managing and transferring SSV tokens to maintain validator operations
SSV 3.1: Proxy Smart Contract
P2P.org's SSV 3.1 proxy smart contract simplifies DVT staking to a single ETH transfer. P2P.org's smart contract manages SSV tokens and handles validator registration automatically. No SSV token management required.
Best for
- Platforms offering DVT staking to clients without SSV token management overhead
- Teams prioritizing faster integration over native SSV architecture alignment
- Institutional platforms requiring operational simplicity at scale
- Consideration: relies on P2P.org's proxy smart contract rather than the native SSV staking flow
Built For
Who Uses the DVT Staking API
Exchanges and Custodians
- Offer DVT staking to institutional clients with distributed key management
- Non-custodial: signing remains with the client
- Compatible with Fireblocks and major institutional custody solutions
Uptime-Critical Platforms
- Three of four operators required for full validator function: no single point of failure
- Validator cluster distributed across diverse locations and client software
- Reduces correlated slashing and downtime risk
Developer Teams
- SSV 3.1 proxy smart contract removes SSV token management overhead
- Full API reference and getting started guide available
- Testing environment available at api-test.p2p.org before production deployment
Client Results
Trusted by the Institutions That Set the Standard
“We are excited to team up with P2P.org to supply our clients with unparalleled security and efficiency in managing their staked digital assets.”
“We are proud to associate the Bybit name with P2P.org, the most trusted validator and infrastructure provider in the space. We look forward to elevating the space for believers in the digital economy together.”
Developer Resources
Integration Resources
DVT Staking API Overview
Full documentation covering SSV 1.0 and SSV 3.1 integration paths, prerequisites, and architecture overview.
Getting Started with SSV 3.1
Step-by-step guide for integrating SSV 3.1 proxy smart contract staking including request examples and response field descriptions.
Withdrawal Guide
Full withdrawal process documentation for SSV 3.1 including validator exit transaction creation and broadcasting.
API Reference
Complete endpoint reference for all DVT Staking API operations including deposit, status, and withdrawal endpoints.
Explore More
Other Integration Tools Worth Exploring
DVT Staking
The institutional DVT staking page. Use cases, configuration options, and getting started, for non-developer decision-makers.
Staking API
Per-chain staking integration across 17 proof-of-stake networks, including Ethereum native staking, unstaking, and validator status.
SDKs
JavaScript and TypeScript libraries for local transaction signing and typed Staking API access. Keys never leave the client's server.
P2P.org by numbers
P2P.org is a non-custodial staking and DeFi infrastructure provider serving institutional clients across 35+ blockchain networks. Founded in 2018, P2P.org operates validator infrastructure, DeFi execution controls, and transaction data services for custodians, exchanges, asset managers, wallets, and treasury teams worldwide.
Networks supported
35+
Institutional digital assets secured
$10B+
Dedicated support
Global
Operating infrastructure since
2018
Institutional clients
190+
Slashing events track record
Zero
Trusted by industry leaders
Frequently Asked Questions
Help centerAn API for distributed validator technology staking via SSV Network. Validator keys are split across four independent operators, with three of four required to keep a validator running. Non-custodial throughout.
SSV 1.0 integrates directly with SSV Network's native staking architecture and requires managing SSV tokens. SSV 3.1 uses P2P.org's proxy smart contract, reducing staking to a single ETH transfer with no SSV token management required.
Distributed validator technology splits a validator key across multiple independent operators. With a three-of-four threshold there is no single point of failure, and the cluster is distributed across diverse locations and client software, reducing correlated slashing and downtime risk.
The Ethereum minimum of 32 ETH applies per validator. Cluster composition and operator distribution are managed by P2P.org and documented in the SSV integration guides.
Yes. The API returns unsigned transactions; signing happens with the client's existing key management or custody solution, and signing remains with the client at all times.
Pectra introduces the 0x02 withdrawal credential type. The DVT Staking API is 0x02 ready, so validators provisioned through it are compatible with the upgrade.
Yes. A testing environment is available at api-test.p2p.org before production deployment.