The Vordium protocol

A Layer 1 for autonomous finance — consensus, an order book inside the chain, agents with enforced limits, and risk rules every validator applies.

Most trading venues on a blockchain run their order book somewhere else and settle on the chain afterwards. Vordium puts the order book, the margin rules and the liquidation engine into the chain itself. Every validator applies them to every batch, so the market is as final and as verifiable as a transfer.

Vordium architectureWallets, SDKs, AI agents and EVM contracts send signed operations to the network's public interfaces. Every validator runs VordiumBFT to agree on batches and VordCore to apply them: the order book, margin, liquidation and funding. The bridge vault on Arbitrum One holds USDC; it pays only what the validators have signed. Explorers and feeds read the committed state.Wallets & appssign with the owner keySDKsPython · TypeScriptAI agents · MCPagent keys, policy-boundEVM contractsgas in VORDPublic interfaces — REST · WebSocket · JSON-RPCVordiumBFTvalidators agree on each batch of heights · a block is final once the validators certify itevery validator receives accepted operationsVordCoreorder book · matching · margin · liquidation · funding · oracleEVM lanecontracts · actions on VordCore (testnet)Bridge vault on Arbitrum One · USDCExplorers · feeds · the network spec
Vordium architecture

Consensus

VordiumBFT is a Byzantine fault tolerant protocol. Validators agree on batches of heights weighted by voting power, and a block is final once the validators certify it — no reorganisations, no confirmation count. Operations are passed to every validator over the validator network, so there is no public mempool to watch.

The order book inside the chain

VordCore matches orders, holds isolated margin per position, settles funding and liquidates at the mark — all at the batch boundary, on every validator, in the same order. A position's liquidation price is the engine's own boundary, served exactly. Market makers get batch requests, a dead-man switch and protection limits.

Agents with enforced limits

An agent is a key that trades for an account. The account sets its policy — capabilities, markets, exposure, leverage, daily loss, active hours — and every validator checks every operation against it. An agent can never withdraw, a loosened limit waits an hour, and every refusal carries a reason code.

Contracts that trade

On the testnet, the EVM lane runs Solidity contracts with gas in VORD, and CoreWriter lets a contract place orders and move funds on VordCore.

Signatures bound to one chain

Every signature is EIP-712 typed data whose domain is bound to the chain's genesis. A signature made for one chain never verifies on another — not even one with the same chain id.

USDC in and out

One vault on Arbitrum One holds the USDC behind every balance. It pays only what the validators have signed, and anyone can compare its balance with what Vordium owes (proof of reserves).

Start

Network facts last checked against the network 2026-10-22 13:00:37 UTC · mainnet spec v28 · testnet spec v8