I'm really excited about the new keypo.io app (coming soon). Biggest change is it's mobile first so you don't need a mac computer to use it. Before going live, would love to do some user interviews to get feedback on the app. If you're interested please reply here! Willing to comp for time too.

Do you want to talk to your openclaw agent using @xmtp? I built a plugin for that. 4 commands and you'll be talking to your agent over decentralized, end-to-end encrypted communication ☺️

Coming soon: the new and improved keypo.io app. Before: you needed an apple computer to use Keypo. After: all of Keypo's functionality (splitting secrets, sending shares to other devices, recovering secrets) will be available on your iPhone.

I wish there was a way for my claud code sessions to "talk to each other." Two simple examples: 1. I like having one session generate a plan and another review it and provide feedback. Rn I have to c/p the plan and feedback between two sessions. 2. Sometimes I have sessions running on different machines (one in a serv... Show more

Keypo.io uses Apple and Yubico secure enclaves to protect your seed phrases. Encryption keys never physically leave the device and enforce policies on how keys are used that is verifiable. Here's a primer on how it works from my convo with @gramajo.eth:

Been doing a lot of work that's more on the boundary of hardware and software (ex: app that uses AR glasses) and coding agents are pretty good but it's really hard to get a good feedback loop going since testing requires doing stuff in the real world. Has anyone solved this?

Recovery codes rule everything around me. Was setting up a Meta developer account and what do they give me? Recovery codes to write down! A month ago I would've done it. Now I use keypo.io to split and store them securely across my Apple devices, backed by biometric auth.

In the age of AI, protecting sensitive data isn't enough. You need to pay attention to: 1. How are the encryption keys derived 2. Where do they live If you're using agents on your local machine like @openclaw, use Keypo to back up sensitive data so it's out of reach of dem claws

Continuing to document setting up openclaw securely. Do NOT talk to your bot in Telegram! Bot chats can not be end to end encrypted, so Telegram can view all your chats with your Openclaw bot. Use Signal. The official Openclaw docs are a little misleading (the way they suggest to set it up you would be using your pho... Show more

Been experimenting with openclaw and finding that a lot of the setup (if you're running it in the cloud) has multiple recovery codes they recommend writing down! So I'm using keypo.io to back these up. Here's a video walkthrough of how to do it:

Shamir Secret Sharing is a core piece of Keypo's architecture, and the reason there's no single point of failure. It's the same cryptography behind products like @privy that you probably already use. Here's a primer on how it works from my convo with @gramajo.eth:

I did a call with a friend who's spent his entire career in sales to pick his brain on how to sell keypo.io to new customers and one advice he gave me was to be "shameless." Now I see what he meant.

Why is Keypo relevant in a world where wallets don't use seed phrases? The reality: all your favorite new wallets have a recovery code, and they put it on you to keep it secure! From my convo with @gramajo.eth: