peaqOS on Solana

peaqOS gives each machine an identity and a way to log its work. It runs natively on Solana.

What works today

• Machine identity. A machine created on Solana gets a peaqID (did:peaq:<id>) and a Machine NFT stored in Solana accounts.
• Ed25519 keys. Machines can sign with the same key type Solana checks natively.
• Event logging. Machines can log revenue and activity events.
• Cheap bonds. Activating a machine costs $0.02,$0.20 or $40 a year.

What does not work yet

• Verify (chip and business checks) only covers machines homed on peaq.
• Reading peaq data from Solana. Bonds, points and subscriptions live on peaq. There is no trusted way to read them from Solana.
• Moving machines between chains is switched off.
• Credit data (MCR) is delayed and often unavailable for Solana machines.
• Event trust levels are set by whoever sends the event. Nothing checks them.

What BotBot does about it

• Checks machine signatures on Solana itself.
• Counts revenue only when real USDC arrives.
• Keeps its own credit score.

What we need from peaq

1. The Solana registry layout, so the hook can read machine keys.
2. Which peaqID key signs receipts.
3. Machine liveness readable on Solana.
4. Verify for Solana machines.
5. A test network and a pilot fleet.