P2P.org

• Name: P2P.org
• URL: https://p2p.org/
• Category: institutional staking operator / validator operations company / staking API middleware
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: P2P.org belongs as an entity note. The interesting surface is not just that it runs validators. It is that the company bundles non-custodial validator operations, staking and restaking APIs, DVT exposure, reporting, and white-label institutional integrations into one operator-controlled workflow shell.
• What it does:
  • Operates staking infrastructure across a large set of proof-of-stake networks for wallets, custodians, exchanges, banks, treasury managers, and asset managers
  • Provides enterprise-grade APIs for staking operations and analytics across multiple chains through a unified integration surface
  • Extends beyond plain staking into restaking, DVT-oriented Ethereum flows, and network-specific yield products that institutions can access without running the underlying stack themselves
  • Sells embedded and white-label integration paths so other intermediaries can expose staking inside their own products while inheriting P2P.org’s operational layer
  • Publishes AI-readable docs and a read-only MCP server for documentation access, reinforcing that the company treats its developer and workflow interfaces as first-class product surfaces
  • Maintains public validator-operations and SSV/DVT-adjacent repositories that make the company boundary look more like active infrastructure stewardship than a thin sales shell
• Key claims:
  • The homepage positions P2P.org as an institutional-grade staking provider delivering secure access to opportunities across 40+ blockchain networks; treat those scale claims as company-published figures rather than independent verification
  • The official site says P2P.org provides non-custodial staking infrastructure and technology for intermediaries such as wallets and exchanges, which is a stronger company-boundary signal than a protocol signal
  • The docs describe P2P.org as an enterprise-grade API platform and explicitly frame the Unified API and Staking API as integration points for businesses to access staking operations and analytics across networks
  • Supported-network materials show that staking, restaking, DVT, pooled staking, and data services are not identical product surfaces, which means P2P.org is choosing which operational workflows and yield paths become easy for customers
  • The AI / MCP docs show the company turning documentation access itself into a machine-readable integration surface, while keeping the MCP path read-only today
  • The public GitHub organization suggests P2P.org is not only a marketing layer but also maintains validator, Cosmos deployment, security, and SSV-cluster-management software in public
• Whitepaper: No standalone company whitepaper is the point here. The strongest primary materials for this pass were P2P.org’s official site, platform-overview docs, supported-network matrix, AI / MCP docs, FAQ/help-center materials, and public GitHub organization; see ../whitepapers/p2p-org-primary-sources-2026-04-25.md.
• Sources:
  • https://p2p.org/
  • https://docs.p2p.org/docs/platform-overview
  • https://docs.p2p.org/docs/networks-supported
  • https://docs.p2p.org/docs/overview-ai
  • https://p2p.org/faq/en/
  • https://p2p.org/faq/en/articles/5280324-what-is-staking
  • https://github.com/p2p-org

Internal linkages

• Project-layer alias: p2p-org.
• Keep this note on the clearest adjacent reads: figment, kiln, and everstake.
• Useful DVT / validator-topology contrast: obol.
• The analytical point is operator workflow, validator leverage, and institution-facing staking packaging — not a directory of every staking company.

Protocol / company boundary

• There is not a very useful standalone P2P.org protocol boundary doing most of the analytical work.
• The useful questions are who operates the validators, who decides which staking / restaking / DVT workflows become turnkey, who authors the reporting and API surface, and who packages those flows for wallets, custodians, exchanges, and banks.
• That is why this note belongs in companies/: the practical authority lives in the company-run operating shell rather than in a neutral protocol primitive.

Control surface

• The leverage sits in validator operations, staking API defaults, supported-network coverage, restaking and DVT product exposure, reporting surfaces, and the white-label integration path inherited by institutional customers.

• The important dependency is not merely which validator gets delegated to but which company defines the easiest staking workflow, the reporting truth, and the supported execution path for institutions that do not want to run this stack themselves.

• Read P2P.org as a validator-operations and staking-workflow company, not as a protocol in its own right.

• Last reviewed: 2026-08-06 UTC