Skip to main content
An Economics 2.0 machine can live on instead of peaq. Its identity record, document and are Solana accounts that name a Solana key as owner. The subscription is paid on Solana, in PEAQ or USDC, and booked on peaq, so every Solana machine is still one peaq machine with one .

​
How it works

Onboarding runs terminal-first: seven stages in a fixed order, from two wallets. The peaq operator wallet registers the Solana owner wallet on peaq, once per owner wallet. The owner wallet pays the bond into an activation request on Solana. peaq’s Trust Validator node (the node) credits the request, the owner settles it, and peaq books the bond. The owner then mints the machine on Solana and sends the link push back to peaq, where the node delivers it. There is no messaging fee. The CLI runs all seven stages from one command, or one stage per invocation. The Python and JavaScript SDKs expose the same phases. Events from a Solana-homed machine go to the Solana EventRegistry, and the 2.0 MCR API serves the machine under its decimal machine ID. Everything runs on peaq mainnet and Solana mainnet-beta. The flow was proven on production on 2026-10-06 and 2026-10-07 with all three packages on both pay-in tokens. The code released as CLI 0.0.17 and SDK 0.11.2 was run on production on 2026-10-08 (CLI, PEAQ rail). CLI 0.0.18 adds events for a Solana-homed machine after onboarding and 0.0.19 its --chain solana management writes; both were proven on production on 2026-10-09.

​
Start here

Onboarding quickstart

Your first machine, from a blank terminal: install the CLI, fund the two wallets, and run the seven stages from one command. Choose the Solana tab.

Onboard a machine on Solana

The reference: costs, every CLI argument, what stays fixed, the Python and JavaScript scripts, history and state reads, and recovery after a stopped run.

Activate on Solana

What changes against peaq activation: two wallets, --chain solana, seven stages instead of one transaction, and the bond paid on Solana.

CLI

peaqos activate --chain solana, machine history, Solana-aware machine status, set-evm-operator, and event submission from the terminal.

Python SDK

The registration, the terminal phases, the mint and the link push, the onboarding history, management and event submission for Solana-homed machines.

JS/TS SDK

The same onboarding phases in TypeScript, with the history, management and event submission for Solana-homed machines.

MCR API

GET /mcr/did:peaq:<decimal machine ID> on mcr.peaq.xyz returns the scorecard of a Solana-homed 2.0 machine with home_chain: 5. rating_unavailable names why the score is still a floor (for example no_events_yet). The machine profile (GET /machine/…, peaqos show machine) can name a different reason (event_history_not_indexed) for the same machine. The scorecard’s reason is the rating’s.

​
Under the hood

Omni-chain: Solana

Programs, the Trust Validator node and how peaq and Solana stay in sync.

Economics 2.0

Tiers, bonds and the subscription a Solana machine keeps on peaq.

Roadmap

What is live, and what comes next: ratings for Solana machines once their events are indexed, relocation.