> For the complete documentation index, see [llms.txt](https://docs.primestaking.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.primestaking.xyz/partner-staking/partner-staking.md). # Partner Staking {% hint style="info" %} **Status: live on XDC Mainnet.** The [`PartnerVaultRegistry`](/partner-staking/partner-staking/registry-and-verification.md) is deployed at [`0x325DEEA5C7c0Ce0D774c4A67EcCaAf1cF8953a67`](https://xdcscan.com/address/0x325DEEA5C7c0Ce0D774c4A67EcCaAf1cF8953a67) and partner pools are already being registered. Pools appear in the app's directory once PrimeStaking marks them **Verified**. {% endhint %} **Partner Staking** lets a community, validator, exchange, or institution run its **own** XDC liquid staking pool — its own branded token, its own masternode operators, its own admin keys — while plugging into the PrimeStaking app, UI, and tooling. PrimeStaking does not custody the pool or operate its validators; it provides the audited vault design and the directory, and earns a flat **15% protocol fee** on the pool's staking rewards. Each pool is a deployment of [`PartnerStakedXDC_V3`](/partner-staking/partner-staking/smart-contract-reference.md) — a self-contained, fee-bearing copy of the PrimeStaking flagship [`PrimeStakedXDC_V3`](/products/xdc-liquid-staking/v3-architecture.md) vault. It is a fully independent contract: separate state, separate token, separate admin keys, separate masternode operators. It shares no storage, funds, or permissions with the flagship vault. *** ## Partner Staking vs. Institutional Integration PrimeStaking offers two different partner tracks. Don't confuse them: | | **Partner Staking** (this section) | **Institutional Integration** ([For Partners](/for-partners/institutional.md)) | | ------------------------ | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | What it is | The partner **deploys and runs their own vault** (`PartnerStakedXDC_V3`) and lists it in the PrimeStaking directory | The partner **integrates the flagship PrimeStaking vault** into their own product (White Label / Powered by Prime) | | Who custodies validators | The **partner's** masternode operators | PrimeStaking's infrastructure | | Token | The partner's own branded share token (e.g. `acXDC`) | psXDC (the flagship share token) | | PrimeStaking's cut | Flat **15% protocol fee** skimmed on-chain from rewards | Negotiated revenue share (see [Revenue Model](/for-partners/revenue-model.md)) | | Best for | Communities, validators, regional platforms that want their own pool | Exchanges and custodians embedding XDC staking into an existing app | *** ## Why it's built this way * **Self-service & self-managed.** The partner deploys the vault, holds the admin keys, registers their own masternode operators, and covers their own masternode hosting costs. PrimeStaking never holds the keys or the funds. * **Non-custodial & ERC-4626.** Same share-based, native-XDC design as the flagship V3 vault — instant withdrawals against a liquidity buffer, an automatic FIFO queue when the buffer is empty, masternode delegation, time-locked governance, and per-report / daily loss caps. * **Trust-minimized listing.** The fee rate (15%) and recipient (PrimeStaking treasury) are **compile-time constants**, so every genuine partner vault shares identical runtime bytecode. The [`PartnerVaultRegistry`](/partner-staking/partner-staking/registry-and-verification.md) only lists a vault whose `codehash` matches an allow-listed canonical hash — a partner cannot deploy a 0%-fee fork and have it appear in the PrimeStaking UI. * **Curated visibility.** Registration is open, but the app shows only pools PrimeStaking has marked **Verified**, so the branded directory can never be flooded with spam pools. *** ## How a pool comes to life 1. **Deploy** a `PartnerStakedXDC_V3` with a name, symbol, the XDC validator contract, and a minimum masternode stake. The deployer becomes the vault admin. → [Deploy & List a Pool](/partner-staking/partner-staking/deploy-and-list.md) 2. **Configure** operators, KYC, buffer, and governance parameters from the partner admin dashboard. 3. **Register** the vault in `PartnerVaultRegistry` (requires the canonical codehash and the vault admin role), then set presentation metadata. → [Registry & Verification](/partner-staking/partner-staking/registry-and-verification.md) 4. **Get verified** by PrimeStaking to earn the "Verified by PrimeStaking" badge and appear in the default directory. 5. **Users stake** native XDC into the pool and earn rewards via NAV growth, net of the 15% protocol fee. → [How It Works](/partner-staking/partner-staking/how-it-works.md) *** ## In this section | Page | What it covers | | ---------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | | [How It Works](/partner-staking/partner-staking/how-it-works.md) | The economic model, the 15% fee chokepoint, what the partner manages vs. what PrimeStaking provides | | [Deploy & List a Pool](/partner-staking/partner-staking/deploy-and-list.md) | Deploying `PartnerStakedXDC_V3`, roles & governance, registering and getting verified | | [Registry & Verification](/partner-staking/partner-staking/registry-and-verification.md) | `PartnerVaultRegistry` — codehash gating, verification badge, metadata, delisting | | [Smart Contract Reference](/partner-staking/partner-staking/smart-contract-reference.md) | Function-level reference for both partner contracts | **Contact:** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.primestaking.xyz/partner-staking/partner-staking.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.