Registry & Verification

PartnerVaultRegistry is the on-chain directory that powers the StakeXDC app's partner pool listing. It answers one question trust-minimally: "is this address a genuine, unmodified partner vault that charges the 15% protocol fee, controlled by the person registering it?"

It is an Ownable2Step contract (two-phase ownership handoff so control can't be lost to a mistyped address). The owner is StakeXDC.

Codehash gating

Because the partner vault bakes the protocol fee rate and recipient in as constants (the V3.2 partner fee is storage, so it does not affect the bytecode), every genuine partner vault of a generation has identical runtime bytecode and therefore one canonical codehash per generation. StakeXDC allow-lists those hashes:

setCanonicalCodeHash(bytes32 codeHash, bool allowed)   // owner only, once per published vault bytecode version

register(vault) then enforces:

• isCanonicalCodeHash[vault.codehash] == true, else NotCanonicalBytecode
• caller holds vault's DEFAULT_ADMIN_ROLE, else NotVaultAdmin
• vault != address(0) and not already registered, else ZeroAddress / AlreadyRegistered

This makes it impossible to list a fork with a different protocol fee, a different recipient, or hidden modifications. If the vault bytecode is ever revised, StakeXDC publishes and allow-lists the new codehash; older deployments stay valid under their own hash unless explicitly revoked. That is exactly how the V3 → V3.2 upgrade (partner fees) shipped: both codehashes are allow-listed, existing V3 pools stayed registered, and new deploys use V3.2.

Verification & visibility

The app reads verifiedVaults() for the curated listing, so the directory can never be flooded with unverified spam pools, while registration itself stays permissionless. setVerified and unregister are owner-only (StakeXDC); unregister clears all registry state for a vault but does not touch the vault contract; its admin can register it again later.

Metadata

Presentation data lives in the registry (not the vault, whose bytecode is codehash-locked) and is editable only by the vault's admin:

struct PoolMeta { string description; string website; string logoURI; string twitter; string telegram; }
setMetadata(address vault, PoolMeta meta)   // vault DEFAULT_ADMIN_ROLE only

Read API (used by the app & indexers)

Events

→ How It Works → Deploy & List a Pool → Smart Contract Reference