VORDIUM DOCS
Trading Infrastructure

Contract Addresses

Reserved system addresses on Vordium Chain.

Genesis V5 system addresses (Vordium Chain)

ContractAddress
PositionRecord0x0000000000000000000000000000000000001000
AssistanceFund (VLP)0x0000000000000000000000000000000000001001
VordexVault0x0000000000000000000000000000000000001002
FeeConfig0x0000000000000000000000000000000000001003
BuybackEngine0x0000000000000000000000000000000000001004
AgentRegistry (caps read-mirror)0x0000000000000000000000000000000000001005
Bridge (Vordium)0x0000000000000000000000000000000000001007
StakingRewards0x0000000000000000000000000000000000001009
BridgedUSDC0x000000000000000000000000000000000000100a
InsuranceFund0x000000000000000000000000000000000000100b
AirdropClaimer0x000000000000000000000000000000000000100c
VestingVault0x000000000000000000000000000000000000100d
ReferralRegistry0x000000000000000000000000000000000000100e
ValidatorRegistry0x0000000000000000000000000000000000001013
VordCoreState0x7777777777777777777777777777777777777777

Deferred (not live): the Solidity agent contracts — SessionManager (0x…1014), an on-chain AgentRegistry, AgentEcosystemRewards, and the one-time agent starter grant — are built but not deployed live (EVM execution is off; the agent system runs native-only). Don't rely on them. There is no AgentRewards contract.

Arbitrum contracts

ContractAddress
Bridge (Arbitrum)0xAEa4118e93184A9D6754c9907DEEc48A981189B9
USDC (Arbitrum)0xaf88d065e77c8cC2239327C5EDb3A432268e5831

Trading pairs (ETH, BTC, BNB, SOL, etc.) are handled natively by VordCore. There are no individual ERC20 token contracts for trading pairs. Oracle, orderbook, and matching are all part of the VordCore native execution layer.