Bubbles Protocol
User Preferred Payments and Cross-Chain Payment Simplification
Demo
About
**Bubbles Protocol** makes crypto payments as simple as sending an email. Instead of Alice needing to figure out which chain, which token, or which bridge Bob prefers, she just sends to `bob.eth`. * **The problem today:** Alice has USDC on Base, Bob wants ETH on Arbitrum. Normally, Alice must bridge, swap, and then send — **3 steps, 3 fees, 15 minutes**, and lots of logistics. * **With Bubbles Protocol:** Bob sets his payment preference once in his **ENS record** (e.g., “ETH@Arbitrum”). Alice can send **any token on any chain** to `bob.eth` in a single transaction. The protocol reads Bob’s preferences and automatically handles swaps/bridges using **1inch Fusion+**. Bob receives exactly what he wants, where he wants it — instantly. **Demo app: Bubbles Social Layer** To showcase this, we built a fun demo app called **Bubbles**, where users send each other **“appreciation stickers”** (bubbles). Behind the scenes, those bubbles are tied to small payments that are **auto-converted across chains/tokens** via ENS + 1inch. * NFC wristbands map to ENS names → tap to send a bubble. * Sending a bubble automatically resolves the receiver’s chain/token preferences. * Users never see bridging, slippage, or token complexity — just a fun social experience. **Impact:** * Before: 3 steps, 15 minutes, technical knowledge required. * After: 1 step, instant, anyone can use it. This unlocks frictionless crypto payments for **peers, creators, merchants, or even supply chains**.
How it's made
The protocol is built on **ENS (Ethereum Name Service)** with automatic routing powered by **1inch Fusion+ APIs**. ### ENS integration (preferences) * Each user sets their **preferred chain + asset + address** as ENS text records. * Example: `bob.eth` → “ETH@Arbitrum”. * This record acts as a universal payment preference policy. ### Wallet query + resolution * When Alice enters `bob.eth`, her wallet queries ENS to fetch preferences. * If Alice already has the right asset on the right chain, the wallet just transfers directly. * If not, it falls back to cross-chain routing. ### Cross-chain swap with 1inch Fusion+ * If Alice is on **USDC@Base** but Bob prefers **ETH@Arbitrum**, the wallet automatically calls **1inch Fusion+ APIs**. * Fusion+ determines the optimal path (swap + bridge), executes the conversion, and delivers ETH on Arbitrum to Bob’s preferred address. * Alice signs one transaction; routing and bridging happen behind the scenes. ### Components * **ENS text records** → store preferences. * **Smart contracts** → define the routing protocol and intent guardrails. * **Wallet integration** → queries ENS and triggers Fusion+ flows. * **1inch Fusion+ APIs** → execute swaps + cross-chain settlement. * **Demo app (Bubbles):** Next.js frontend with ENS integration + NFC support for tap-to-send appreciation stickers.