How it works
Onboarding runs in three phases, in a fixed order, from two wallets: the peaq operator wallet reserves the machine ID and pays the bond on peaq, peaq mirrors both to Solana, then the Solana owner wallet creates the machine on Solana and pays its fees and rent. The CLI runs one phase per invocation; the Python SDK exposes the same phases, and the JS SDK previews, reads and recovers the flow. Events from a Solana-homed machine go to the SolanaEventRegistry, and the MCR API resolves a Solana address to its machine and scorecard. Everything runs on peaq mainnet and Solana mainnet-beta.
Start here
Onboard a machine on Solana
The full walkthrough: configuration, the three phases, the wait for peaq’s mirrors, recovery after a stopped run, and the exact CLI arguments.
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
Previews, reads, recovery, management and event submission for Solana-homed machines; onboarding writes go through the CLI or Python.
MCR API
GET /mcr/did:peaq:<decimal machine ID> on mcr-20.peaq.xyz returns the scorecard of a Solana-homed 2.0 machine; the /solana/* routes serve Tokenomics 1.0 bindings only.Under the hood
Omni-chain: Solana
Programs, mirrors, the Machine NFT bridge 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, 2.0 ratings for Solana machines once the MCR indexer runs, relocation.

