Vordium Python SDK

The AI Layer for crypto. vordium is the Python SDK for building AI agents that read and trade on Vordium Chain — a Layer 1 whose perp DEX (Vordex) is a central limit order book settled in consensus, chainId 101101.

pip install vordium

Why this SDK is safe to point at a live chain

• The network is discovered, never hardcoded. chainId, RPC, explorer and the Arbitrum bridge are resolved at runtime from the canonical spec and the node's /status. Nothing is baked in, so the SDK always signs for the chain it is talking to.
• The signing chainId is resolved by agreement. eth_chainId, the spec, and any pin you set must all agree, or the SDK refuses to sign — a mismatched signing domain would otherwise yield a valid signature on another chain.
• The deposit bridge is an allow-list of one. The SDK accepts only the bridge address the live network spec names at the moment you ask, and refuses every other address — and every address when the spec cannot be read.
• EIP-712 domains are genesis-bound. The VordCore domain salt is derived from the live genesis_sha256; if the node can't tell the SDK its genesis, the SDK refuses to sign rather than emit a digest the chain will reject.

Quick start (read-only)

from vordium import Vordex

dex = Vordex()
for m in dex.markets():                 # live perp markets (ETH, BTC, …)
    print(m["symbol"], m["mark_price"])

book = dex.orderbook(1)                  # resting bids/asks for pair 1
print(dex.mark_price(1))                 # human mark price

The test network

from vordium import Vordex, use_network

use_network("testnet")                   # JSON-RPC https://rpc-testnet.vordium.com; reads and orders on the
dex = Vordex()                           # testnet's API base https://testnet.vordex.xyz/chain

use_network("testnet") (or VORDIUM_NETWORK=testnet) reads the test network's own spec, asks its JSON-RPC endpoint for the chain id and its node for the genesis, and refuses unless they agree. The main network stays the default (https://rpc.vordium.com). An address you pass yourself -- rpc_url= or VORDIUM_RPC_URL -- still wins.

Agents

An agent on Vordium is an account operated through a session key bounded by opt-in, on-chain caps that the account sets. A session key can only ever do what the native agent gate allows; it can never withdraw funds or change its own caps.

import os
from vordium import Agent, Vordex

agent = Agent(os.environ["VORDIUM_PRIVATE_KEY"])   # never hardcode a key
print(agent.address, agent.balance)                # native VORD (authoritative /vord route)

dex = Vordex()
print(dex.balance(agent.address))                  # USDC collateral
print(dex.positions(agent.address))                # open perp positions

Order placement is EIP-712 signed with the session key. Agent write ops take effect once agent trading is enabled for the account on-chain — reads work regardless, and calls that aren't live yet return an "unavailable" result rather than inventing data.

Deposit bridge

Deposits are made on Arbitrum, to the bridge the network spec names. Read it at the moment you use it, and check any address you were given against it:

from vordium import current_bridge, require_current_bridge, BridgeRefused

bridge = current_bridge()              # read from the live network spec now; raises BridgeRefused if it cannot be read
require_current_bridge(address)        # returns the address only if it is that bridge; raises BridgeRefused otherwise

vordium.bridge_v4 builds deposits into the vault (from Arbitrum, or from Arc through Circle's CCTP) and withdrawals to Arbitrum or Arc. Everything it needs is read from the chain's public bridge routes at the moment of use, and it refuses before anything is signed when a read cannot be confirmed:

from vordium import bridge_v4 as bridge

deployments = bridge.fetch_deployments()                   # the vault and its handler, as the network spec names them
v = bridge.deployment_check(bridge.fetch_vaults(), deployments)
gate = bridge.deposit_gate(v, 42161, deployments)           # deposits from Arbitrum: open right now?
check = bridge.deposit_check(v, 42161, 25_000_000)          # 25 USDC from Arbitrum: may it be built?
print(gate.state, check.ok, check.text)

nonce, why = bridge.fetch_next_nonce(account)               # withdrawals are signed by the account's own key

Deposits are open only when the read is recent, the vault the network spec names is listed and depositsOpen for the source chain is true; otherwise deposit_gate says they are closed and nothing is built. Amounts are USDC base units (6 decimals).

From Arc, the network fee is paid in USDC and Circle delivers the deposit to the vault, so nothing is needed on Arbitrum. Arc refuses USDC transfers from or to an address on its blocklist; both helpers check that first:

prepared = bridge.prepare_arc_deposit(address, 25_000_000, arc_rpc_url=ARC_RPC)
if prepared["ok"]:
    tx = bridge.send_arc_deposit(private_key, prepared, ARC_RPC)   # then follow it: bridge.arc_deposit_stage(...)
else:
    print(prepared["text"])

outcome, code, message = bridge.withdraw_to_arc(private_key, 10_000_000, arc_rpc_url=ARC_RPC)

Signing formats and agent names

The chain publishes the activation height H of its genesis-bound signing formats in releases.json. The SDK reads H, the genesis and the current height live before it signs, and refuses to sign when it cannot confirm the format the chain expects:

from vordium import read_signing_phase, registration, rename, sign_owner_op

phase = read_signing_phase()          # read it right before signing: legacy / window / genesis-bound / unknown
op, value = registration(owner, agent, "strategy: Grid", expires_ms, nonce, phase, name="Grid bot")
body = sign_owner_op(owner_key, op, value)   # RegisterAgentV2 from H: the on-chain name is required

Agent names follow the chain's rule: 3–32 ASCII characters (A-Z a-z 0-9 space - _ .), no reserved words such as "vordium" or "admin"; prepare_name() normalises and checks one (the reason given is the chain's first failing step, and refusal_step() names it), and agent_display_name() renders <name> · 0xAbCd…1234.

Agent policies (from H)

An account sets what its agent may do with SetAgentPolicyV1, and clears a risk lock with ClearAgentLock. The chain drops a policy it refuses without saying so, so the SDK checks the stateless rules first:

from vordium import PolicyV1, set_policy, clear_lock, sign_owner_op, policy_problems

op, value = set_policy(owner, agent, policy, nonce, phase, now_ms)     # raises, naming every reason, if the chain would drop it
body = sign_owner_op(owner_key, op, value)
op, value = clear_lock(owner, agent, lock_since_ms, nonce, phase)     # clears only the lock that began at lock_since_ms

An agent may tighten its own policy (never loosen it) with set_policy(..., stored=current, signer="agent") and sign_agent_policy(agent_key, value).

Pool and staking

Deposits, withdrawals, staking, unstaking and claims are messages the account key signs; a session key is refused on all of them except a claim:

from vordium import sign_money_op
from vordium.money import to_units

body = sign_money_op(owner_key, "VlpDeposit", {"user": owner, "amount_6dec": to_units("25", 6), "nonce": nonce},
                     chain_id, phase)     # POST it to /vlp/deposit

Market makers

from vordium import MarketMaker, Feeds, Mmp, next_mmp_nonce
from vordium import mm

maker = MarketMaker("https://rpc.example", private_key, owner_address)   # owner key or a live session key
spec = mm.pair_specs(maker.specs())[1]                                  # tick, lot, margins, liquidation fee

bid, ask = maker.nonce(), maker.nonce()                        # the account's one nonce clock (also used by KeepAlive)
r = maker.batch([
    mm.place(1, "buy",  mm.round_size(size_18dec, spec), mm.round_price(bid_price_8dec, spec, "buy"), bid, post_only=True),
    mm.place(1, "sell", mm.round_size(size_18dec, spec), mm.round_price(ask_price_8dec, spec, "sell"), ask, post_only=True),
])
for a in r.actions:
    print(a.index, "accepted" if a.accepted else a.refusal.message)

maker.batch([mm.cancel_by_client_nonce(bid)])                  # or mm.cancel(order_id)
maker.cancel_all(1)                                            # 0 = every pair
orders, positions = maker.open_orders(), maker.positions()
maker.set_mmp(Mmp(window_ms=60_000, max_fills=20, freeze_ms=15_000),
              next_mmp_nonce(maker.account()))

feed = Feeds("wss://rpc.example/feeds")
feed.subscribe("book", pair=1)
feed.subscribe("orders", account=owner_address)
for kind, msg in feed.events():         # snapshot, update, resubscribed (after a missed message), reconnected
    ...

Every write is signed for the network of the node it is sent to (its chain id and genesis, read from its /status). If you configure a network -- network= on the client, set_network(), or VORDIUM_CHAIN_ID / VORDIUM_GENESIS_SHA256 -- and the node serves another, nothing is signed and NetworkMismatch is raised.

A 202 answer means the request was accepted for the next block; read the result from your orders, fills or the feeds. Prices are 8-decimal integers, sizes 18-decimal integers and USDC amounts 6-decimal integers.

CLI

vordium init         # scaffold a config
vordium balance 0x…  # read a native VORD balance

Units (do not mix)

Links

• RPC: https://rpc.vordium.com
• Testnet RPC: https://rpc-testnet.vordium.com (test tokens have no value)
• Docs: https://docs.vordium.com
• Explorer: https://vordscan.io
• Source: https://github.com/Vordium/vordium-sdk

License

MIT

Genesis-bound EIP-712 domains (mainnet genesis 2c1c0679…)

Every Vordium signing domain binds its salt to the chain's genesis sha256, so a signature made for one genesis never verifies on another chain with the same chainId. vordium.domains derives the domains from the live node (/status.genesis_sha256) and never pins them; at the current mainnet genesis the two used for trading are VordCore 0x68b86fee… and VordexSession 0x519818aa… (vordium.domains.verify_against_node() re-derives and compares at runtime).