Sign Solana transactions offline.
World
Joined April 2026
- Tweets63
- Following41
- Followers141
- Likes232
Pinned Tweet
1.- Create a wallet
2.- Write your words
3.- Draw your seed QR code by hand
4.- Keep it offline!
This is the @faradaysigner! An offline wallet that keeps your keys off the internet.
You create a wallet, it generates your keys, and you draw the backup QR code by hand. Scan the drawing, and the wallet loads back.
There is no other way to get the keys out. You write the words, or you scan the QR!
In this video I show how that's done. Hope you like it.
Ever wondered how to sign transactions with an offline device?
This video shows you how!
This time you'll see how to perform a swap using @faradaysigner!
In the previous video I showed you how to create and load your private keys into the Faraday cage. Now you'll see how to use them in a real dApp like @JupiterExchange
Remember that you can sign up to get yours at faraday.to/#waitlist
Faraday retweeted
This time you'll see how to perform a swap using @faradaysigner!
In the previous video I showed you how to create and load your private keys into the Faraday cage. Now you'll see how to use them in a real dApp like @JupiterExchange
Remember that you can sign up to get yours at faraday.to/#waitlist
Faraday retweeted
This is the @faradaysigner! An offline wallet that keeps your keys off the internet.
You create a wallet, it generates your keys, and you draw the backup QR code by hand. Scan the drawing, and the wallet loads back.
There is no other way to get the keys out. You write the words, or you scan the QR!
In this video I show how that's done. Hope you like it.
The only way to avoid this from happening is to buy components off the shelf and build your own signer device yourself. Anything can be built with a raspberry pi or a ESP32 device
We have some difficult news to share. Unfortunately, one of our shipping providers has experienced a data breach that exposed sensitive order data. This affects new customers in the US, UK, Sweden, Colombia, Brazil, Italy, and Portugal who received an order within the 90 days prior to August 8th, 2026.
The data exposed:
- Full names
- Shipping addresses
- Phone numbers
- Email addresses
The incident affects 11,742 customers with full exposure (name, email, phone number, shipping address) and 1,947 customers with partial exposure (name, city, email). The breach is limited due to Trezor’s strict 90-day data storage policy (we were also able to negotiate the same terms with fulfillment partners, who follow the same policy).
All affected customers have been contacted separately by email.
Our systems and devices remain secure, but affected customers could experience an increase in phishing attempts.
NEVER enter your wallet backup on a website or share it with anyone, and only check for updates on official Trezor channels.
We are deeply sorry to the community and those affected.
We are investigating this situation and will post updates on our blog:
trezor.io/blog/news/recent-c…
Faraday retweeted
Usually we don't participate in the creation of our keys, basically we're blindly trusting the software that generates them!
That's exactly why this happened, and why with Faraday you're part of making your own keys.
Flip a coin, roll a dice, take a picture... your randomness gets mixed with the hardware RNG, so the seed is never weaker than either source!
An estimated $100M+ in BTC was swept from air gapped wallets these past weeks. A firmware bug made seed generation predictable, so the keys were weak from the day they were born!
The air gap held. The randomness didn't.
On Faraday, a seed comes from two sources: sensor noise from a photo you take, mixed with the hardware RNG. If good randomness is unavailable, the device refuses to continue.
If you prefer your own luck, flip coins and enter them raw!
The create flow is open Rust, and you can read it here: faraday.to
An estimated $100M+ in BTC was swept from air gapped wallets these past weeks. A firmware bug made seed generation predictable, so the keys were weak from the day they were born!
The air gap held. The randomness didn't.
On Faraday, a seed comes from two sources: sensor noise from a photo you take, mixed with the hardware RNG. If good randomness is unavailable, the device refuses to continue.
If you prefer your own luck, flip coins and enter them raw!
The create flow is open Rust, and you can read it here: faraday.to
Faraday retweeted
great space with the amazing @faradaysigner devs
self custody + amazing UX wasn’t technically possible but this is changing now with @ikadotxyz and security-first devs are noticing
self custodied native bitcoin with spending policies and account recovery is coming to @solana
Faraday retweeted
crypto finally built airplane mode for your keys.
@faradaysigner joins the IKA Space to talk air-gapped signing, QR-only wallets, and why your private keys should never touch the internet.
no wifi. no bluetooth. no nfc. you just scan.
set reminder ↓
dWallets?
On the Faraday firmware?
What is this?
@ikadotxyz 👀
Faraday retweeted
we had a chat with the @faradaysigner team and it’s such a pleasure to talk to paranoid security-focused people, it's rare to have a conversation where everyone's assumption is no attack vector is too far fetched
to me personally this is exactly the kind of team i'm building for, and if faraday integrates @ikadotxyz in any way (and we discussed a few options where it could be beneficial for both usability and security), that's a huge success
it's tough to convince paranoid people (obviously) and they are not convinced yet (of course), and have a lot of reading and verification to do on their side, but -
not to toot my own horn too hard, i think it's fair to say no other MPC infrastructure would have even been considered as an option by a team like faraday, because all other systems introduce some form of trust and/or centralization into the process, which is unacceptable
the combination of radical zero-trust (everything created locally and a user share with the same security as a private key) plus the decentralization of the policy side (no reliance on centralized provider / saas fees etc.) plus the ease of use and valuable added functionality (recovery, policies etc.) make it the only viable option today to even consider for such a team
if it works out i'll be very very happy!