Identity before payments

Payments are the exciting sentence. Identity is the sentence that has to come first. If two machines can present the same story, or if a record can be rewritten by whoever runs the database, then “the robot earned this” is a claim, not a fact another party can use.

What “who is this machine?” has to survive

• A new owner, without the history vanishing or being easy to forge.
• A repair that swaps a part, without the whole identity becoming a new fiction.
• A check by someone who does not have a login to the manufacturer’s cloud.
• A later dispute: which unit, which site, which hour.

Decentralized identifiers and onchain machine records are one way to publish that answer so it is not trapped in a single vendor account. Projects in this lane — peaq is the one this desk mentions most often, because it is built around machine identity rather than around a general chain — treat the robot as a long-lived participant: an ID, a record, sometimes a way to hold and spend value. The pattern matters more than any ticker. A private fleet platform can do parts of the same job. The open version matters when the counterparty is not already your customer.

Then, and only then, settlement

Once a machine can be told apart, the economic verbs get simpler to say: it consumed a correction, it sold a sensor trace, it paid for a burst of inference, it shared revenue with the people who financed it. Those verbs are where machine RWAs and fleet financing enter the conversation. Read them as claims about cashflow from work, and ask who can audit the work. A yield number with no machine behind it is not robotics.