Guy-Louis Grau

Monolithic security fails monolithically. Keycard separates: - Interface - Signing - Key storage So one compromised layer doesn’t compromise everything.

@Logos_devs wow, cool!

LEZ ←→ Ethereum atomic swaps working on Logos Testnet v0.1. Messaging, execution, and UI are modular and run through Logos Basecamp. Install Basecamp, try out the testnet, and come build private-by-default apps: build.logos.co

@Keycard_ and Shell are truly cypherpunk. They are 100% yours, down to every byte and every piece of silicon. While others are busy adding subscriptions, tracking, and extra fees, Keycard is focused on giving you freedom and control. Choose wisely.

We've spent years thinking about what's wrong with hardware wallets. Closed source designs. Monolithic architecture. Conditional self-custody. Today we wrote down what we're trying to build instead and why it matters beyond crypto.

I'll be around in Cannes at EthCC. Any one who want to chat about self custody, hardware or @keycard_ , hit me up!

🚨 🚨 mainnet launch update 🚨🚨 > testnet v1 (Sepolia) is still live but will be sunsetted early next month > a snapshot of early users of testnet v1 has been made 📸 > testnet v2 (Hoodi) is currently under private deployment and will soon be publicly available > testnet v2 includes the RLN-based spam protection that will be implemented on mainnet > mainnet launch is now planned for end of April > we added some extra rewards in $SNT and $LINEA for pre-depositors and adjusted the yield calculation in the vaults > pre-deposits are still open for now > earn 9%+ liquid yield on ETH and 16%+ on stablecoins on top of Karma > the Status Network whitepaper will be published early April, along with detailed Karma tokenomics > native apps are getting onboarded: native DEX: @OrvexFi native CDP: @usf_money native launchpad: to be announced soon native privacy layer: to be announced soon > you'll soon be able to experience a new way to interact with blockchains based on reputation (Karma) and not gas Karma counts.

Live demo: encrypted notes running inside @Logos_network App, unlocked by @Keycard_. It shows what hardware means for the ecosystem. Any app can be unlocked by a card. Keys never leave the chip. Pull it out and session ends. No passwords, no keys on the disk. Pure hardware joy.

@Logos_network Implemented @Keycard_ support by wrapping status-keycard-go as a C shared library and wiring it into our @Logos_network App plugin - hardware-derived AES-256-GCM encryption for notes is ready. Long exhale. Live demo coming soon. 1.0.0 is here github.com/xAlisher/logos…

Status Network  🤝 @synthesis_md’s agent hackathon 

if you're building with AI agents, this is your sign  join the first hackathon where AI agents register with their own identity, build real projects, and compete - judged by both AI + humans register your agent today↓  https://synthesis.md/

Disassembled the @Keycard_ Shell to take a photo for the new @Logos_network zine to highlight how simple, minimalist, and thoughtful its design is. Reassembled it afterward and it works like a charm. By the way, I forgot to include one small detail in the photo. Can you spot what’s missing? P.S. Tinker responsibly. 🛠️

Events like Parallel Society Festival by @Logos_network remind us why we build. A community that cares deeply about privacy, security, sovereignty, and open technology. Thanks to everyone who came by the Keycard booth to talk self-custody 🔐

I rarely write anything, but I really need to speak my mind on this. LLMs are becoming an integral part of our lives. They are already influencing technological progress and have high potential to shape society. This is unavoidable and can even be something to welcome.

If you own Keycard or Shell: What’s the #1 reason you chose it over other wallets? Security model? Open firmware? Architecture? Reply below. We’re turning the best answers into a public FAQ.

Speakers: @brewster_kahle x @internetarchive, @avilarenata, @jardemalie, @Fatalmeh, @FraMoira, @fryorcraken, @glgrau, @0xcyp, @harryhalpin, @InessBeng, @MarinaMarkezic, @jarradhope_, @Boyke, @lunar_mining, @siakaborn2ball, @tommasoastazi, @JedlickaVit

For years, MetaMask has been the gateway to Web3. 🦊 Now Keycard Shell is officially supported — and listed inside MetaMask’s hardware wallet options. That means native compatibility. Recognized support. No workarounds. Hardware security. Open architecture. MetaMask integration. This is what real self-custody looks like. Connect in minutes: keycard.tech/en/help/connec…

Answering here what some might ask: what's the difference between a @keycard_ and @satochip Seedkeeper since both (will) work with Shell? Both have a backup value: they hold your private keys securely, and you can use them as fully functional backups. Still, they differ: - @keycard_ is a signer. It's private keys will never get out. Which means you won't ever be able to duplicate it without knowing the seed itself. - Seedkeeper is designed to be a back up, not a signer. You can actually get your seed out of it, and so it can replicate itself only with its pin code.

Two open-source smart card teams, one shared vision. We're excited to be working with @satochip on integrating Seedkeeper with Shell, giving users a seamless way to back up or restore their Keycard seed using a dedicated secure card. The proposed flows are open for community feedback 👇

@Zodomo @pcaversaccio @KeystoneWallet @gridplus @Trezor @COLDCARDwallet @keycard @keycard_ I meant ofc

@Zodomo @pcaversaccio @KeystoneWallet @gridplus @Trezor @COLDCARDwallet check @keycard shell and it's community of builders

so it's common knowledge that apps cannot be sideloaded on the Ledger Nano X. What is not public knowledge, to the best of my understanding, is _why_. It cannot be sideloaded because of a bug in the secure element (SE). To be precise, this is _not_ a user-facing vulnerability. Due to this bug, STM private code on the chip cannot be sufficiently protected, so Ledger chose to disable sideloading. Before you panic, it's all safe, everything is fine. I'm disclosing this publicly for two reasons: - stop buying the Ledger Nano X immediately. It is an inferior product and sideloading will become very important in the future - inform the public about a bug that cannot be disclosed due to NDAs between Ledger and STMicroelectronics to be very clear, the Ledger Nano X is secure. Ledger did their duty. A red team uncovered the issue. Disabling sideloading was a security decision. What I disagree with is the lack of transparency here, even if the constraints are legal. Ledger has great products (not talking about the data breaches tho!), including the best one they ever shipped, the Ledger Nano S, which is unfortunately no longer sold. But please stop buying the Ledger Nano X. Sideloading is a core feature. Ledger should reconsider keeping it in the product lineup.

An obvious one is modularity and ease of use when you're a power user with several seeds. With @keycad_ Shell it takes < 3 seconds to switch from one seed to an other: you just switch the card, enter its pin and you're good to go. You've got to experience it to truly understand how much friction you remove with such a setup when you're signing a lot everyday.

@FractalEncrypt @newzealandhodl @SparrowWallet @Trezor @Ledger @Keycard_ @r0ckstardev @bitcoinbutlers I'm still waiting for someone to explain one advantage stateless signers have over encrypted state signers. I'm pretty sure there isn't one.

Sparrow v2.4.0 released with: Send to silent payments hardware wallet support Address display chunking Wallet discovery for USB hardware wallets Codex32 support Trezor Safe 7, Ledger Nano Gen5, Keycard and Keycard Shell support sparrowwallet.com/download

@vpavlin @ethstatus @Keycard_ would you give him access to keycard with keycard CLI ? github.com/keycard-tech/k…

I'm just gonna give the money to Jimmy I guess:) Given that he already uses @ethstatus he just needs to integrate the Status wallet... curious if he'll be able to use @Keycard_ ...