Infrastructure · 15 October 2026 · 6 min read

Thirty robot-data collectors now carry a peaq identity. A buyer has not been shown the difference

OpenRoboto says the first 30 of its OR-S1 units on Bittensor subnet 80 use peaqOS Pro, each with an identity anchored on Solana. peaq says later units will too. Neither post shows a recording that was rejected because the identity failed, or a buyer who paid more because it passed.

A dark announcement frame with the OpenRoboto and peaq names over a piece of equipment. — Still from OpenRoboto’s 15 October announcement. Not a photograph of the 30 collectors in use.

OpenRoboto said on 15 October that it is putting peaq’s machine-identity tools on its Shift data collectors. The first 30 OR-S1 units, it said, now run peaqOS Pro, and each has a decentralised identity on Solana. peaq repeated the figure and added that every OpenRoboto collector now runs the Pro tier, that 30 are live, and that every later unit will get the same identity. peaq described OpenRoboto as the largest robotics subnet on Bittensor. That description is the company’s. Neither post published a count of the other robotics subnets it was measured against.

The reason they gave is the one that matters to a buyer of robot video. Training data is becoming worth faking. A recording that cannot be tied to a particular machine, on a particular day, is a recording anyone can invent. An identity on the collector is meant to be the start of a path from device to file to payment. Solana’s own account went further and said the devices can be verified and paid for performance on Solana. OpenRoboto’s post said the 30 have identities. It did not say a payment has already moved because of one.

An identity is not a check on the pixels

A decentralised identifier can show that a known device signed a record. It cannot, by itself, show that the record is a true view of a room, that the gripper did the job, or that the same scene was not filmed twice and sold as two. Those checks are a different system. peaq has shipped a verify function for machines, filed on this desk earlier in the month. This announcement does not say the 30 collectors are using that check, or any other, on the files they upload.

What a buyer would actually use is a filter. Can a customer refuse a file whose machine has no history, or pay less for one that has failed a check before? Neither company said that filter exists. Thirty identities on a wait of future units is a start, and it is the right shape of tool if robot data is going to be sold rather than just collected for a reward. It becomes infrastructure when a named buyer can point at a file and say the identity is why they took it, or why they did not.