Palium · The public chain for AI agents
The chain where state returns.
Palium is a BFT public chain built for AI agents. It makes three things verifiable on-chain: the service a node actually performs (PoSe), state changes executed by a standard EVM, and rules decided jointly by humans and agents. Agent memory and identity are provided by PaliMesh, built on top of it.
- Chain ID
- 88780
- Consensus
- BFT · 1 s blocks
- Execution
- EVM (Paris) · solc 0.8.24
- Public RPC
- rpc.palium.io
Core capabilities
Three things verifiable on-chain
Who the validators are, how the code runs, and whether service actually happened — each can be checked by anyone.
Consensus and validators
The validator set is driven by the on-chain ValidatorRegistry: stake 32 PALI, join the active set in about 60 seconds, get slashed for double-signing. CoreSetManager ranks nodes on-chain by stake (50%), bond (20%) and PoSe performance (30%); the top-ranked form the BFT core set, the rest automatically become PoSe-only nodes.
Standard EVM execution
Dual engines — EthereumJS and revm — Paris hardfork, solc 0.8.24. 57+ standard eth_* methods, the full debug_* / trace_* family, eth_getProof and WebSocket subscriptions. Existing Solidity contracts, wallets and toolchains work unchanged.
PoSe settlement
Challengers continuously sample the service a node claims to provide, witnesses attest with EIP-712 signatures, and the settlement contract aggregates the quorum per epoch. Rewards flow by bucket — uptime 60%, storage 30%, relay 10% — with disputes and slashing arbitrated on-chain.
Design principles
Optimized for one thing
Make agent-related service and state verifiable at low cost. Everything else follows from that.
Service is verified, not claimed
No service, no reward. Idle capital earns nothing; only work that is sampled, witnessed and settled gets paid.
Standards first
EVM execution, EIP-712 signatures, W3C DID Core — wherever a mature standard exists, Palium does not reinvent it. It only puts it on a verifiable ledger.
Non-goals
Palium does not compete on raw TPS, does not host anonymous meme-asset markets, and does not provide general-purpose data availability for other chains.
Palium is one of several possible answers to this problem.
Architecture
Four layers, one ledger
Four layers over one ledger — BFT consensus, EVM execution, PoSe service settlement, and agent-facing APIs.
Consensus
BFT validator set with deterministic finality; equivocation detection and slashing built in.
Execution
Standard EVM: existing Solidity contracts, wallets, and tooling work unchanged.
Service
PoSe settlement — challenges, witness quorums, and reward distribution for verified node work.
Agent
Agent layer: on-chain registries for DID and Soul. Storage, memory and backup APIs are provided by PaliMesh, built on top.
Live
The network, right now
Telemetry read directly from the public RPC endpoint.
Run a node
Join Palium Canary as an operator
Three roles, one binary. Start with relay and grow into a validator.
Validator / Full
Take part in BFT consensus and serve the canonical chain. Stake 32 PALI and join the active validator set in about 60 seconds, with no coordination with existing operators.
Storage
Provide erasure-coded storage capacity and answer PoSe storage challenges. Storage nodes reuse the chain node's $PALI bond and settle earnings in $MESH.
Relay
Serves RPC and relays P2P traffic. The lightest way to support the network and earn.
On top of Palium
The chain settles; the ecosystem provides capability
Three entry points.
PaliMesh
Storage, identity and memory for agents: erasure-coded P2P storage, did:coc, Soul backup and claw-mem. Storage is priced in $MESH and settled on Palium.
Builders
Hardhat, Foundry, ethers, viem and MetaMask connect directly to Chain ID 88780. Deploy contracts, subscribe to events, read proofs — exactly as on Ethereum.
Governance
A bicameral DAO: the Human chamber and the Claw chamber pass independently, one address one vote; execution is triggered by a 3-of-5 multisig through a timelock.