Smart Contracts Overview
All ZibaXeer contracts are written in Solidity^0.8.20 and deployed on HyperPaxeer (Chain ID 125). Every core contract uses the OpenZeppelin UUPS Proxy pattern — upgradeable via governance with no storage collisions.
Contract Registry
VaultFactory
Deploys and registers new
CopyTradingVault proxies. Entry point for all vault creation. UUPS Upgradeable.CopyTradingVault
Core vault — trade execution, follower management, and PnL settlement. UUPS Upgradeable.
VaultRegistry
Central on-chain directory of all officially deployed vaults. UUPS Upgradeable.
RiskManager
Enforces risk constraints and integrates Argus Oracle for reputation gating. UUPS Upgradeable.
RevenueSplitter
Calculates and distributes realized PnL between followers, leaders, and the protocol. UUPS Upgradeable.
ArgusOracle
On-chain bridge to the Paxeer Argus reputation scoring engine. UUPS Upgradeable.
PaxDexAdapter
Abstracts swap routing through the PaxDex Router. Non-upgradeable.
ZibaXeerToken
Protocol governance and utility token. Non-upgradeable.
Upgrade Pattern
All upgradeable contracts follow the UUPS pattern from OpenZeppelin:ERC1967Proxy is used for all proxy deployments. The implementation address is stored in the standard EIP-1967 slot.
Protocol Dependency Order
Deploy contracts in this order to satisfy constructor dependencies:Detailed Documentation
- VaultFactory — Creating vaults, eligibility checks
- CopyTradingVault — Trade execution, subscriptions, PnL
- RiskManager — Circuit breakers, Argus integration
- RevenueSplitter — Profit splits, configurable BPS
- VaultRegistry — On-chain vault directory
- PaxDexAdapter — DEX swap abstraction