0xFloyd

 

Work


00

Pluto Frame

'Plaid-for-everything' iframe + SDK that lets any app verify user web data and run automations with TEE-attested results: no user installs required.

Under active development. I am co-architecting the frontend npm libraries, Frame UI, and in-browser playground editor with @drewjenkins.
2025In-house
Pluto Frame
  • Drop-in SDK, zero installs: Less than 5 lines of code. <Frame /> or Pluto.initialize() embeds the secure iframe; published on npm as @plutoxyz/react-frame and @plutoxyz/frame-js.
  • Four-piece toolkit: live playground, production iframe bundle, framework-agnostic frame-js, and ergonomic react-frame in a TypeScript monorepo with pnpm workspaces.
  • Real-time DX: in-browser code editor, virtualised log console, and postMessage↔WebSocket bridge that streams Playwright events and hot-reloads scripts into the frame for live debugging.
01

RAG Assistant

Retrieval-Augmented Generation (RAG) chat assistant that debugs, explains, and writes Pluto automation scripts using private + public SDK knowledge.

I built the entire project.
2025In-house
RAG Assistant
  • Unified knowledge index: ingests docs, guides, and example scripts, chunks them semantically, and embeds with OpenAI; vectors stored in Supabase Postgres with pgvector.
  • Fast retrieval: ANN similarity plus keyword fallback surfaces the right context in real time for every chat turn.
  • Edge-streamed chat: Next.js on Vercel Edge streams completions; Drizzle ORM enforces strict typing.
  • Impact: dramatically cut support load by enabling developers to self-troubleshoot Playwright-style scripts.
02

Attest Chrome Extension

Multi-context Chrome extension that lets users privately generate "Web Proofs" of their authenticated data: zero trust in Pluto or any server.

Co-built the extension: architecture, UI, and proof pipeline with @drewjenkins.
2024In-house
Attest Chrome Extension - Image 1
  • Multi-context architecture: service worker, content scripts, injected SDK, offscreen docs, and sandboxed iframes form an isolated proof pipeline.
  • Client-side Web Proofs: Rust-to-WASM cryptography in Web Workers lets users prove facts (e.g., Venmo balance) entirely in-browser.
  • Secure & private: JSON-only messaging, per-session keys, IndexedDB caching; secrets and artifacts never leave the device.
  • Seamless site integration: Any web page can kick off a proof flow using a tiny window.pluto.prove() API, thanks to a secure SDK injection and strict message passing across contexts.
03

Pluto Developer Dashboard

Full-stack Next.js dashboard where Pluto developers self-serve billing, generate API keys, and monitor usage with real-time analytics.

I built the entire project.
2025In-house
  • Typed, robust stack: Next.js, Supabase, Drizzle ORM, shadcn/ui, and GitHub/Google OAuth via NextAuth.
  • Automated billing: Stripe checkout and customer portal handle plans, invoicing, and usage webhooks.
  • Real-time analytics: live dashboard shows API usage, session logs, and billing status via Supabase Postgres.
  • Zero-friction onboarding: developers sign up with one click and instantly receive API keys: no passwords or approvals.
04

Web Proofs Library

TypeScript library that lets developers integrate the Pluto iOS app and Chrome extension to generate Web Proofs with a single call.

Built the entire library.
2024In-house
Web Proofs Library
  • 5 lines of code: Single component/function drop in, making integration frictionless for devs, with optional theme customization and data callbacks.
  • Smart UI orchestration: <Prove /> decides in real time whether to show a “Prove” button (extension), a QR code (mobile hand-off), or an “Install CTA” - no extra logic required.
  • Cross-environment SDK: Use the React component or plain JS function prove(config) - both share the same core, typed API and ship in a single ESM bundle built with Rollup.

Agency - the drive to act without waiting for permission - is elevated above specialization as the key economic differentiator in an AI-powered world.