Roadmap

robopay is in alpha. The items below are planned, roughly in order. Nothing here is promised on a date.

Next

  • Simpler install. A single install step instead of the manual pip line.

  • More examples. Payments driven by LiDAR, camera (OpenCV), and other common robot inputs.

  • Non-blocking escrow open, matching how transfers already behave.

Later

  • Scoped session keys. Keys that can only pay certain addresses, up to certain amounts, until a certain time. Limits what a compromised robot can do, and lets the background resolver run with least privilege.

  • Early mutual cancel for escrows both parties want to unwind before the deadline.

  • Optimistic escrow that releases automatically unless disputed, for lower-friction jobs.

  • Managed wallet backend for fleets that prefer a custodial provider over keys on each robot.

  • Robot identity. Registering and resolving robot identities, so an address can be tied to a known robot and owner.

Contributing

Issues and pull requests are welcome on GitHub. If you use robopay on a real robot, we would like to hear about it.