freedom tech, FOSS, privacy @InstituteFT @Keycard_ @logos_network

encrypted
Joined May 2022
Panel alert: What Cypherpunks Can Learn From GenZ? How young people already practice informal privacy with burner accounts, close-friends lists, pseudonymous online identities, even without the vocabulary of “privacy tech.” What cypherpunk builders can learn from how teens already protect themselves socially, and what tools would actually meet them where they are. moderator: @thisischandresh x @ethmumbai Featuring @_devisha x @Logos_network & @Keycard_ , @lifewradss x @fhenix, @kashvi x @BoundlessHQ Only @ Cypherpunk Congress, Mumbai: congress.web3privacy.info
1
7
32
1,685
ambire + keycard are a great combo
👀 @glgrau creates and signs a 2/2 Safe multisig transaction with Keycard Shell in Ambire.
6
24
771
Transparency beats trust. So we made Shell hardware easy to verify. Here are videos and pictures to help you check the integrity of your Shell: docs.keycard.tech/en/help/ch…
5
14
2
79
2,665
devisha retweeted
λλλλ ⠀⠀⠀λλ ⠀⠀⠀⠀λλ ⠀⠀⠀⠀⠀λλ ⠀⠀⠀⠀⠀⠀λλ ⠀⠀⠀⠀⠀⠀⠀λλ ⠀⠀⠀⠀⠀⠀⠀λλλ ⠀⠀⠀⠀⠀⠀λλ⠀λλ ⠀⠀⠀⠀⠀λλ⠀⠀⠀λλ ⠀⠀⠀⠀λλ⠀⠀⠀⠀⠀λλ ⠀⠀⠀λλ⠀⠀⠀⠀⠀⠀⠀λλ ⠀⠀λλ⠀⠀⠀⠀⠀⠀⠀⠀⠀λλ ⠀λλ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀λλ λλ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀λλλ
6
26
669
There is transparency (as in open source code), then there is TRANSPARENCY (as in code + HW specs/BOM etc.) and then...there is @Keycard_
Replying to @0x_ridam
Or just move to something that's already transparent and open source - @Keycard_
6
15
301
devisha retweeted
Mobile app supports @Keycard_ NFC signing. Just tap your Keycard to your phone and complete transactions on the go.
7
5
53
3,104
dear algo please show this to Keycard users
Mobile app supports @Keycard_ NFC signing. Just tap your Keycard to your phone and complete transactions on the go.
3
34
709
devisha retweeted
Build what they can't control. @Logos_network @Keycard_ #privacy #tech
1
5
18
423
Follow-up on the Keycard Shell OpenPGP work: The SIGN_MESSAGE crypto/protocol path is now proven end-to-end on physical hardware. Flashed the beta5 firmware, generated a fresh signing request for the exact 74-byte Thurin statement, reviewed it on the Shell, signed with the Keycard, recovered the detached OpenPGP signature from the response QR, and verified it independently with GnuPG: gpg: Good signature from "Keycard Test " The resulting signature is a real OpenPGP v4 canonical-text signature: • type 0x01 • ECDSA / secp256k1 • SHA-256 • correct issuer fingerprint • correct signature creation time • exact statement bytes preserved with no trailing newline So the hardware signing path works. Physical testing also caught two UX issues: • SIGN_MESSAGE review was split across separate review steps • signing authorization used a normal press instead of an explicit hold Both are now fixed in the PR branch. SIGN_MESSAGE is now one combined trusted-review document: message → signature time → fingerprint → HOLD TO SIGN CREATE_IDENTITY now uses the same explicit hold-to-confirm authorization. Commit: 636d94f — openpgp: fix trusted review flow Then I updated the Thurin integration to the current stack: • @thurinlabs/thurin 0.13.8 • @thurinlabs/identity-kit 2.2.1 The good news: current Thurin supports exactly the detached-signature format the Shell produces. The verifier also caught one more OpenPGP interoperability issue: the certificate generated by CREATE_IDENTITY did not advertise Key Flags in its UID self-certification. identity-kit correctly rejected it as a signing key. Fixed that on the Shell side by adding the hashed OpenPGP Key Flags subpacket: 0x03 = certify + sign SIGN_MESSAGE itself stays unchanged. Commit: 635a8a2 — openpgp: advertise signing key flags Release firmware builds cleanly and the signing/certification paths remain separated. Now waiting for the next firmware build so I can do the final physical regression: CREATE_IDENTITY → confirm key flags → SIGN_MESSAGE → identity-kit verified: true → Thurin Sepolia attestation This ended up being a really useful integration pass — the hardware crypto works, the UX got tightened, and the current Thurin verifier caught a certificate metadata issue before the first on-chain claim.
1
9
302
Keycard Shell OpenPGP current status: SIGN_MESSAGE is now implemented and pushed for review. Shell can produce hardware-backed detached OpenPGP signatures with trusted review before signing. Added proper OpenPGP canonical-text signing (type 0x01): • LF → CRLF canonicalization • existing CRLF preserved • trailing newline semantics preserved • bare CR rejected • message length bounded to 104 bytes so the full statement remains reviewable on-device Trusted review now shows: • the exact message • signature creation time in UTC • the OpenPGP fingerprint The fingerprint is reconstructed from the Shell-owned key + key creation time. The host never supplies the fingerprint or derivation path. Also verified that CREATE_IDENTITY stayed wire-compatible. Software regressions now cover protocol round trips, malformed requests, timestamp ordering, 104/105-byte boundaries, newline canonicalization, trailing data rejection, and host-generated CBOR. Release firmware builds cleanly. Added host-side tooling for SIGN_MESSAGE too: • generate signing request QR • recover detached OpenPGP .sig • validate packet structure The first Thurin statement is 74 bytes and already satisfies the byte-exact requirements: lowercase Ethereum address, no trailing newline. Commit 0bb0442 — “openpgp: add message signing” — is pushed to the PR #227 branch. Next step is review + a fresh demo firmware build, then: physical Shell signing → recover .sig → GPG verify → first Thurin Sepolia claim. Good stopping point for today.
1
1
11
511
devisha retweeted
Built two libraries for @Logos_network. One lets the owner throw away the keys to their own building. The other locks everyone out. On purpose. Also learned that green tests are a mood, not a verdict. The whole story: mmlado.com/blog/keycards-for… #Rust #cypherpunk
1
3
12
258
List of services worldwide that had 0 downtime since inception 1. Ethereum End of list.
41
62
5
420
13,006
Keycard Shell v1.4.0 firmware is ready with - bitcoin multisig descriptors management - btc address verification by QR scan - improved device verification UI You can update your Shell firmware in air gapped mode, or with your browser. See shell.keycard.tech/update github.com/keycard-tech/keyc…
2
4
2
21
1,163
Replying to @ambire @safe @Keycard_
@Keycard_ is based. Second signer on a 2/3 Safe and it’s just a tap on the phone. That’s how hardware wallets should work.
1
2
104
devisha retweeted
something's cooking .... @mmlado_eth is building an android+iphone app to use any QR wallet (ERC-4527) with @Keycard_ github.com/mmlado/keycard-pa…
5
7
27
1,345
devisha retweeted
Replying to @nickisanders
love how you can talk anything with folks at a crypto event, they are so well versed - be it economics, tax, longevity, inflation, quantum computing, cybersecurity, digital privacy and so much more - one can say all rounders whereas ai people just live inside an ai bubble stuck between the new model launches and obsessed w unicorns - their knowledge net is very small
1
2
7
301
devisha retweeted
alright y'all - this last ledger vulnerability was the last straw. i haven't downloaded the ledger live app in years since it became obvious how much data was being collected from there and there's seemingly no way to update your app without it i've already been using @Keycard_ for some things. moved my 'most used' one to a card today. i'm all in on Keycard and @ambire now pls don't become evil, my dudes. we need you
7
15
3
107
9,956
devisha retweeted
19 Chrome & Edge extensions were caught draining wallets and stealing seed phrases by the @SocketSecurity team The malware could hijack wallet flows, spoof hardware wallet recovery screens, and capture seed phrases entered into the browser. This is why your browser should never be where your keys live. With Keycard, the private key stays on the card and transaction signing happens on the card, not inside Chrome.
6
2
1
20
1,613