September 17, 2026
SIG-DRG 2026-09-17
Participants: Anuraj, Spencer Norwick, shreeram, Andre Comeau
This was a working session ahead of an upcoming robotics workshop/symposium in which participants will assemble a small "PiCar"-style robot and put it behind a crypto-payment gateway. Anuraj gave an extended screen-share walkthrough of his current build: an MCP server plus a browser teleoperation UI, a Cloudflare Worker payment service using testnet USDC, on-chain robot registration/attestation, and hashed time-based access tokens. The rest of the group (Spencer, Andre, shreeram) asked questions about hardware readiness, security/hackability, extending the gateway to other IoT devices, and adding a Stripe-based payment option.
- **Hardware readiness (mixed):**
- **The gateway demo (Anuraj):**
- **Extending to other devices (shreeram's interest):** shreeram asked whether household devices (he has a rootable, dead Roomba) could be placed behind the gateway. Anuraj said yes — the robot is essentially an ESP32-class device, and IoT devices can be put behind the gateway by writing a **plugin** (a protocol adapter + the MCP tools). Adapter type depends on the device's interface (HTTP endpoint → HTTP adapter; UDP → UDP adapter). He'd previously tried Home Assistant devices behind the gateway but hit issues and didn't pursue it.
- **Assembly/config detail (Anuraj):** There's a setup script that runs a series of tests and, because everyone mounts motors differently, walks you through identifying each wheel's rotation direction (e.g. "front right wheel, which direction?") and stores the result in a config file. This is installed as a **system service** on the Pi so it persists across reboots; the HTTP endpoints read the config to drive wheels in the correct direction. Anuraj runs the Pi headless via SSH.
- **Vibe-coding the plugin:** Anuraj mentioned building the PiCar plugin quickly (~15–18 minutes) by pointing his coding assistant at the SDK, the gateway, and templates/"little parts."
Session Recording Summary · 35m 33s · Full notes ↗
Reading: Not clearly identified in the discussion. This session was a hands-on planning/demo meeting for an upcoming robotics workshop ("symposium"), not a discussion of a written reading. It centered on Anuraj's demo of a payment-gated robot teleoperation gateway rather than a text.
This was a working session ahead of an upcoming robotics workshop/symposium in which participants will assemble a small "PiCar"-style robot and put it behind a crypto-payment gateway. Anuraj gave an extended screen-share walkthrough of his current build: an MCP server plus a browser teleoperation UI, a Cloudflare Worker payment service using testnet USDC, on-chain robot registration/attestation, and hashed time-based access tokens. The rest of the group (Spencer, Andre, shreeram) asked questions about hardware readiness, security/hackability, extending the gateway to other IoT devices, and adding a Stripe-based payment option.
- **Hardware readiness (mixed):**
- **The gateway demo (Anuraj):**
- **Extending to other devices (shreeram's interest):** shreeram asked whether household devices (he has a rootable, dead Roomba) could be placed behind the gateway. Anuraj said yes — the robot is essentially an ESP32-class device, and IoT devices can be put behind the gateway by writing a **plugin** (a protocol adapter + the MCP tools). Adapter type depends on the device's interface (HTTP endpoint → HTTP adapter; UDP → UDP adapter). He'd previously tried Home Assistant devices behind the gateway but hit issues and didn't pursue it.
- **Assembly/config detail (Anuraj):** There's a setup script that runs a series of tests and, because everyone mounts motors differently, walks you through identifying each wheel's rotation direction (e.g. "front right wheel, which direction?") and stores the result in a config file. This is installed as a **system service** on the Pi so it persists across reboots; the HTTP endpoints read the config to drive wheels in the correct direction. Anuraj runs the Pi headless via SSH.
- **Vibe-coding the plugin:** Anuraj mentioned building the PiCar plugin quickly (~15–18 minutes) by pointing his coding assistant at the SDK, the gateway, and templates/"little parts."
Questions & Disagreements: - **Spencer** repeatedly probed **security/"hackability"**: whether the vulnerable surface is the Cloudflare-managed layer, ngrok/gateway, or the browser — and how the rental clock is enforced. Anuraj's answer: the hashed, signed token makes browser-side time manipulation infeasible. - **Spencer** asked how hard it would be to stand up a **Stripe layer** in front of the robot for people who don't
Participants: Anuraj, Spencer Norwick, shreeram, Andre Comeau