Partner Staking

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, and (new in V3.2) its own on-chain partner fee — while plugging into the StakeXDC app, UI, and tooling. StakeXDC 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_2 — a self-contained, fee-bearing copy of the StakeXDC flagship PrimeStakedXDC_V3_1 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. On top of the protocol fee, the operator can set a partner fee (0–85% of rewards) whose every change waits out a public 24-hour timelock — see How It Works.

---

Partner Staking vs. Institutional Integration

StakeXDC offers two different partner tracks. Don't confuse them:

---

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. StakeXDC 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 protocol fee rate (15%) and recipient (StakeXDC treasury) are compile-time constants, so every genuine partner vault shares identical runtime bytecode. The PartnerVaultRegistry 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 StakeXDC UI. The partner fee lives in storage, so it never fragments the canonical codehash.
• Operator revenue, without rug risk. The partner fee is bounded (protocol + partner can never exceed 100% of yield, principal is untouchable) and every change goes through a public 24-hour timelock that the app surfaces to stakers as an exit window.
• Curated visibility. Registration is open, but the app shows only pools StakeXDC 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_2 with a name, symbol, the XDC validator contract, a minimum masternode stake, and (optionally) a partner fee + recipient. The deployer becomes the vault admin. → Deploy & List a Pool
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
4. Get verified by StakeXDC to earn the "Verified by StakeXDC" 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 and the pool's partner fee (shown as one total fee in the app). → How It Works

---

In this section

Contact: [email protected]