OpenRoboto has registered its first 30 OR-S1 data collectors with peaqOS Pro, giving the devices decentralized identities on Solana. The Oct. 15 announcement brings an onchain device registry to OpenRoboto Shift, a network that collects first-person footage for robot training.
OpenRoboto operates Bittensor Subnet 80, but the devices' identity records live on Solana through peaq's cross-chain infrastructure. Future collectors will follow the same setup.
Linking Training Footage to Capture Devices
The OR-S1 is a dual-camera wearable used to record people working in factories, kitchens, and warehouses. OpenRoboto launched Shift on Sept. 22 to collect this kind of first-person robotics data.
The integration links footage to a device with a publicly verifiable identity. That device-level reference alone cannot verify the authenticity of every recorded action or submitted clip.
Device Records on Solana and Bond Accounting on peaq
The machine's identity record, decentralized identifier document, and Machine NFT are Solana accounts owned by a Solana key in peaqOS's Solana architecture. The identifier document holds information such as verification methods and service endpoints; on Solana, what peaq calls the Machine NFT is represented by a machine account.
Activation begins on peaq, where a peaq operator wallet registers the Solana owner wallet. The owner pays the activation bond on Solana in PEAQ or USDC. peaq's Trust Validator node credits the request, and peaq records the bond. The process then mints the machine on Solana and links it back to peaq. Subsequent activity events go to a Solana EventRegistry.
The arrangement runs on peaq mainnet and Solana mainnet-beta, with peaq still handling the subscription's bond accounting.
OpenRoboto #7607, classified as an EgoCapture machine, lists Solana as its home chain, with separate owner, controller, and machine-account fields. The explorer records activation on Oct. 11, a Pro-tier bond of 961.35 PEAQ paid from Solana, and a subscription period ending Oct. 11, 2027.
Its onboarding history lists 11 transactions across peaq and Solana, followed by Solana activity events. That bond amount is specific to this machine; tier bonds use the oracle rate at activation.
Each activated OR-S1 bonded PEAQ. When a machine exits, half of its bond burns and half goes to the peaq Treasury, so the owner receives no refund.
Developer Access and the Financing Plan
Builders can use peaq's activation tools through peaqos activate --chain solana or Python and JavaScript SDKs. The CLI coordinates seven onboarding stages across the two chains, though the transaction count can differ, as #7607's 11-transaction history shows.
The documented Solana payment route covers activation bonds; the documentation leaves the destination of OR-S1 operators' earnings unconfirmed. Machine ownership and controller records alone are insufficient evidence of autonomous spending by the hardware.
OpenRoboto's next stated step is to connect the fleet to peaq's Machine Money Markets for financing and other financial services. The financing would fund additional OR-S1 deployments.
