Unified Staking API: Multi-Chain Integration
One endpoint, every supported network
P2P.org's Unified API gives exchanges, custodians, wallets, and fintechs one endpoint for staking, unstaking, and transaction broadcasting across 22 blockchain networks. Its modular architecture means new networks are added without requiring additional integrations. Non-custodial throughout: only unsigned transactions are generated, with signing and key management remaining entirely under the client's control.
Unified API Specs
Figures describe the standard API tier. Per-chain parameters, signing methods, and network availability are documented per network in the Docs.
* Integration time is an estimate based on prior client integrations and varies with the client's existing infrastructure and release process.
Network coverage
20+
Integrations to maintain
1
Architecture type
Modular
Average integration time *
~10 hrs / network
Environments
Mainnet / testnet
Transaction Signing
Client-side
Uptime SLA
99.9%
Average Response Time
200 ms
Security & Compliance
How the Unified API Works
Every supported network follows the same three-step flow: prepare, sign, broadcast. The request format is consistent across all 20+ networks. Network-specific parameters are documented per chain in the Docs.
Prepare the unsigned transaction
Send a POST request to the Unified API for a stake, unstake, or withdraw operation. The API validates the parameters and returns a raw unsigned transaction in the standardized format.
Sign the transaction
Sign the unsigned transaction using the client's preferred signing method or P2P.org's Signer SDK. Signing logic varies by chain: chain-specific signing guides are available in the Docs.
Broadcast to the network
Submit the signed transaction to the network using the Unified API's dedicated broadcast endpoint. The API handles network-specific routing automatically.
Networks
Supported Networks
The Unified API currently supports 22 blockchain networks across mainnet and testnet environments. New networks are added regularly.
*NRR figures are estimated, protocol-determined, variable, and not guaranteed.
ETH
Ethereum
Staking, DeFi
2.9%
SOL
Solana
Staking, DeFi
6.6%
HYPE
Hyperliquid
·
TBA
DOT
Polkadot
·
5.8%
TIA
Celestia
·
5.2%
NEAR
Near
·
4.89%
POL
Polygon
·
2.94%
APT
Aptos
·
7.26%
ATOM
Cosmos
·
16.59%
GRAM
TON
·
20.69%
ADA
Cardano
·
2.2%
Built For
Who Uses the Unified API
Exchanges and Trading Platforms
- Offer staking across multiple networks without managing separate integrations per chain
- Single API key covers all supported networks
- Programmatic staking and unstaking at any position size
Custodians and Asset Managers
- Integrate multi-network staking into existing custody workflows
- Non-custodial: signing and key management remain with the custodian at all times
- Compatible with Fireblocks and major institutional custody solutions
Wallets and Fintechs
- Add staking across 20+ networks to the platform without building chain-specific integrations
- Consistent response format simplifies reporting and balance tracking
- Average 10-hour* integration time per additional network after initial setup
Developer Teams
- Modular architecture supports rapid onboarding of new networks as they are added
- Signer SDK available for streamlined transaction signing across all supported chains
- Full API reference, code recipes, and integration guides available in Docs
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 Docs
Getting Started
Step-by-step integration guide covering authentication, request format, and your first staking transaction.
Networks Supported
Full chain and network parameter table for all 22 supported networks, including mainnet and testnet environment details
Sign and Broadcast Transaction
Chain-specific signing guides for Cardano, The Graph, Near, Tezos, and all other supported networks.
API Reference
Complete endpoint reference for stake, unstake, withdraw, and broadcast operations across all supported networks.
Explore More
Other Integration Tools Worth Exploring
Staking API
Per-chain staking across 17 proof-of-stake networks for teams requiring chain-specific control.
SDKs
JavaScript and TypeScript libraries for local transaction signing and typed Staking API access.
Staking Data API
Validator performance, reward, and balance data for reporting and client-facing dashboards.
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 centerOne endpoint for staking, unstaking, and transaction broadcasting across 22 blockchain networks. Its modular architecture means new networks are added without requiring additional integrations.
22 blockchain networks across mainnet and testnet environments, with new networks added regularly.
The Unified API is one endpoint covering every supported network with a consistent request format. The Staking API is per-chain, for teams that need chain-specific control.
Yes. Only unsigned transactions are generated — signing and key management remain entirely under the client's control at all times.
Roughly 10 hours per network on average. That is an estimate based on prior client integrations and varies with the client's existing infrastructure and release process.
Transactions are signed client-side using the client's preferred signing method or P2P.org's Signer SDK. Signing logic varies by chain, and chain-specific guides are available in the Docs.
Yes. Both mainnet and testnet environments are supported, with per-network details documented in the Docs.