peaqOS on Solana

Machines homed on Solana: identity, DID document and Machine NFT as Solana accounts, the bond on peaq, ratings and events across both chains.

An Economics 2.0 machine can live on Solana instead of peaq. Its identity record, peaqID document and Machine NFT are Solana accounts owned by a Solana key. The subscription bond and the registry entry stay on peaq, so every Solana machine is still one peaq machine with one Machine Credit Rating.

How it works

Onboarding runs in four signed phases, in a fixed order, from two wallets: the peaq operator wallet reserves the machine ID and pays the bond on peaq, the LayerZero Executor delivers the reservation mirror to Solana and the Trust Validator writes the subscription status, then the Solana owner wallet creates the machine on Solana, pays its fees and rent, and sends the link push back to peaq. The CLI runs all four from one command (or one phase per invocation) and the Python SDK exposes the same phases; the JS SDK previews and reconciles the phases but does not submit them. Events from a Solana-homed machine go to the Solana EventRegistry; the 2.0 MCR API serves the machine under its decimal machine ID. Everything runs on peaq mainnet and Solana mainnet-beta.

Start here

Onboarding quickstart

First machine, from a blank terminal: install the CLI, fund the two wallets, run the four phases from one command. Choose the Solana tab.

Onboard a machine on Solana

The reference: every CLI argument, what the CLI fingerprints, the state reads, and recovery after a stopped run.

Activate on Solana

What changes against peaq activation: two wallets, --chain solana, phases instead of one transaction, and what the bond still does on peaq.

CLI

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

Python SDK

Reservation, bonding, Solana onboarding, management and event submission for Solana-homed machines.

JS/TS SDK

Onboarding previews, management and event submission for Solana-homed machines, with progress you can persist and restore. Submitting and recovering the onboarding phases goes through the CLI or the Python SDK.

MCR API

GET /mcr/did:peaq:<decimal machine ID> on mcr-20.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).

Under the hood

Omni-chain: Solana

Programs, mirrors and how peaq state reaches Solana.

Economics 2.0

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

Roadmap

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