Skip to main content
peaq chain is the home chain of the peaq Trust Layer, the decentralized infrastructure layer underneath peaqOS. It is an L1 blockchain where the peaqOS contracts are deployed; their state mirrors out to satellite chains so other ecosystems can read it locally. Most teams building with peaqOS do not need to interact with peaq chain directly, since the peaqOS SDK abstracts it. This section covers protocol-layer work: deploying your own smart contracts, running a node, staking, and legacy peaqID, RBAC, and UMT primitives that predate peaqOS. The peaq overview explains how peaqOS and peaq chain fit together.

Start with peaqOS

The opinionated Machine Financial Passport flow, and the path most teams should take.

Build at the protocol layer

Solidity, node operations, staking, and the legacy peaq SDK primitives.

​
When to use peaqOS vs peaq chain

Both SDKs coexist. @peaqos/peaq-os-sdk is the opinionated path through the Machine Financial Passport flow. @peaq-network/sdk gives full access to peaq chain primitives (DID pallet operations, RBAC, Storage, UMT, chain-level transactions). Most teams use the peaqOS SDK and drop to the peaq SDK for primitives peaqOS does not cover.

​
What you’ll find in this section

  • Build reference: Solidity deployments, gas, wallets, event listening, indexers, precompiles, node operations, account abstraction, and ERC-8004 at the contract layer.
  • SDK reference: legacy @peaq-network/sdk (JavaScript + Python), the Robotics SDK (Python + ROS 2), and the RWA SDK for fractional ownership primitives.
  • Tokenomics: $PEAQ supply, inflation schedule, validator rewards, and staking economics.