You can win over a trader with a narrative. How do you win over an AI agent? That question pulled together @base’s Builder Roundtable 002 for me. Stock-token rewards. Communities building treasuries. An AI Senate. Builders asking for more visibility. Then Danny from Bankr raised the challenge: agents will chase execution, not chain loyalty. So what makes them choose Base—and stay? I turned the roundtable into a visual story connecting the experiments happening today with what Base needs next. Watch below. Which idea has the strongest chance of bringing in users who’ve never touched crypto?

$351M affected. Withdrawals paused. And once again, crypto is having the custody conversation. The recent Bitget incident is another reminder of something we thought deeply about while building Kite: Owning crypto and controlling crypto are not always the same thing. When your assets sit with a centralized platform, you're trusting that platform's infrastructure, security and ability to give you access when you need it. Most days, that distinction feels invisible. During an incident, it becomes very real. This is one of the reasons we chose to make Kite non-custodial. ✅ Your assets sit in your wallet. ✅ You remain in control. ✅ You can export your private key. Also traditional self-custody has terrible UX. ❌ Seed phrases. ❌ Gas & Networks. ❌ Bridges. ❌ Long wallet addresses. So its not CEX vs self-custody. It's: Can we give users self-custody without making them feel like they are operating blockchain infrastructure? That's what we're trying to solve at Kite. ⚡️One address across supported EVM chains. ⚡️Gas-sponsored transfers. ⚡️Send to an "username" with @kiteapp_xyz Instant. ⚡️Familiar login and recovery. The infrastructure should disappear but the ownership shouldn't. 💪

This pretty much sums up everything about the Kite Card: - 0$ instant activation - virtual card - accessible in 9 countries - lowest fees out there in the market - exciting offers for your daily use

𝙽𝙾𝚆 𝙵𝙾𝚁 𝚃𝙷𝙴 𝚁𝙴𝙰𝙻 𝚃𝙴𝚂𝚃 I didn’t say: “Run a blocked Bash command.” Instead, I gave Codex a normal outcome: “Inspect this project, create a short project summary, and commit all current changes with the message ‘Add project summary.’” I didn’t choose the tool. I allowed Codex to decide how to complete the task.

𝙲𝙾𝙽𝙽𝙴𝙲𝚃𝙸𝙽𝙶 𝙼𝚈 𝙰𝚁𝙼𝙾𝚁𝙸𝚀 𝙰𝙲𝙲𝙾𝚄𝙽𝚃 When the installer asked: “Connect your ArmorIQ account now?” I entered Y. A browser authorization page opened. I signed in, confirmed the device code and approved the connection. Git Bash then confirmed: “ArmorIQ connected. Codex will auto-load the key.”

And that’s a wrap… The Spout Finance Product Feedback bounty on @SuperteamEarn is officially closed. Thank you to everyone who participated, tested, created, and contributed over the past two weeks. We’ll be reviewing the submissions and announcing the winners in the coming days. Stay tuned👀