Josh

No, the media never touches the KEY, that’s browser to browser WebRTC. Setup needs a relay, but the relay only carries an encrypted wrap signed by the KEY. You can host your own relay and TURN. Scripts will be public, both are fields in settings that can be customised.

2026-07-25 16:50:01 UTC

- reply

Sorry for your loss ❤️

2026-07-25 02:22:57 UTC

GM, Nostr ☕️ have a great day

2026-07-25 01:44:41 UTC

- reply

I love this

2026-07-24 08:31:35 UTC

- reply

Been on that robo juice

2026-07-24 06:02:56 UTC

- reply

25% ain’t bad

2026-07-24 05:47:49 UTC

- reply

2026-07-24 05:46:14 UTC

- reply

2026-07-24 04:16:28 UTC

- reply

GM BankSith

2026-07-24 01:07:23 UTC

GM ☕️ Been heads down building voice and video calls straight into the Favilla KEY. Will Post a demo soon!

2026-07-22 12:40:47 UTC

- reply

Would love that too, but think about who approves the switch. Nobody runs Nostr, so a migration is just a note signed by your old key. A thief with your key can sign one as well, and then you're both trying to move the account at the same time.
Only real answer so far is naming your backup key in advance, before a leak ever happens. Good idea, but it can't rescue a key that's already out. Best defence is still never letting the key touch software.

2026-07-22 12:10:32 UTC

- reply

Honest answer, you can’t un-expose it. But you can stop the bleeding. Move your nsec into a signer so no new app ever sees it again, then delete it from everywhere else. Odds are nobody grabbed it, the risk is what happens as the network grows.
And if your identity really matters to you, the clean move is starting a fresh key that’s never touched software at all. Way cheaper/less hassle to do now than in 5 years. The KEY does either, restore your existing nsec or generate a new one on the device.

2026-07-22 11:50:12 UTC

- reply

Good question. If you value your sovereignty and never want someone else to be BigMilan. You can’t rotate an nsec, once it leaks it’s theirs forever.
Most people paste theirs into every new client they try. Nobody’s hunting nsecs yet because the network is small, but by the time they are it’s too late to un-paste. With the KEY it never leaves the hardware, clients just ask it to sign.
On top of that whoever owns your Nostr keys owns your DMs. Our ecosystem goes a step further with DMs too. When using our app yout DMs stay encrypted when your signer is locked. So even someone unlocking your phone gets only cipher text.

2026-07-21 22:36:06 UTC

- reply

Thanks 🙏 I’m glad you like it. took a few iterations in design but wanted something functional while still pleasing to feel and see.

2026-07-21 12:41:22 UTC

- reply

GM, thanks , making progress everyday!

2026-07-21 12:37:11 UTC

GM,GN wherever you are , here a demo playing FavillaKeys , Cipher , device offline, Air-gapped and submitting scores to Nostr via QR at favillaKey.io
https://blossom.primal.net/8394ec96c59166cd9e98dafa24880c1456bd61b8dd9cacec2e8de3d890881325.mp4
https://blossom.primal.net/d0fe47e9c08cb0d35f51e303f5019c4f526817fcf4bff2536a3b8830e849c77a.mp4

2026-07-21 07:55:15 UTC

- reply

2026-07-20 23:45:45 UTC

- reply

GM to you

2026-07-20 23:44:05 UTC

- reply

Hey mate, you are welcome. It protects your Nostr private key the same way you would your BTC private key, in a hardware wallet. Hash in, signed hash out.
You can view and accept or decline the message being parsed. Or set to automatically sign.
On Nostr our keys are not rented from a platform. The keys are ours (or should be) so you are only as sovereign as the key is safe.
The signers job is to make protecting it and using it the same thing , not a trade off.

2026-07-20 06:00:17 UTC

- reply

GM QnA

2026-07-20 06:00:02 UTC

- reply

GM BankSith 🔥

2026-07-20 00:31:20 UTC

- reply

Thanks, this lines up with how we're thinking, and the identity/signing-key split you've built into Inkan is the same seam we're designing along.
Bitcoin: the real Wi-Fi concern is a remote RCE, so we bracket every transaction with a secure-boot cycle before and after to force a fresh state, and airgapped QR-only mode removes the Wi-Fi RCE surface entirely. Even without airgap, the seed is never plaintext at rest: it's SE-protected and only unwrapped for milliseconds during signing. We originally wanted to offer the QR-or-local-network choice, but we're now leaning toward removing the non-airgapped path entirely and dropping local HTTP with it. Some users won't grasp the risk, and defaults matter more than options when the downside is losing funds. Airgapped QR is still quick for everyday amounts.
Nostr: the identity key is harder because it has to be live to sign on demand, and you can't airgap an interactive signer. So we isolate it on a dedicated second MCU with a tiny attack surface: its only input is a 32-byte hash, it never parses anything, and the nonce is generated in-chip. The scoped claim: no known remote software path can extract the key, because it never enters the network-facing processor. We keep fuzzing our parsers, but that's a different risk, stopping a malicious message from getting the device to sign something it shouldn't, not key extraction. Even then the key stays put and the worst case is a signature you didn't intend, which is recoverable. And the fully airgapped path is always there.
Physical is different. With physical possession of an unlocked device and the right tooling, someone could force a signing event and capture the key in plaintext as the signer uses it. But that means they're already holding your unlocked device, where most security models are in trouble anyway. That's the window our motion lock is built for: it locks the moment the device is moved or handled unexpectedly. It's working well in-house and going to beta before we make firm claims. It doesn't make the theory of physical extraction impossible, nothing does, but it closes the unlocked-and-unattended window this attack depends on.
On whether Inkan's delegation and revocation signing could run on this hardware: yes, and it's arguably a better fit than our own Nostr path. Ethereum delegation transactions are ECDSA over secp256k1, the SE051's native on-chip operation, so the key stays resident in the secure element and never becomes plaintext at all, the exact property we can't fully get for Nostr Schnorr but get for free on your Ethereum case. One caveat: your delegation format presumably wraps the signature in some typed-data encoding (EIP-712 or similar). The primitive is still SE-native ECDSA either way, since encoding and hashing happen host-side before the hash reaches the signer, but I wouldn't claim to know your exact format without looking at it.
To be upfront, our brand is Bitcoin-only, a deliberate identity choice rather than a hardware limit. But the platform isn't closed, and your delegation case is exactly the kind of thing we'd be glad to see run on it. The SE051 exposes ECDSA (secp256k1), ECDH, AES, and EC point ops, so there's real headroom. Modifying the firmware yourself is a direction we'd welcome, though it would be on dev units rather than production hardware, production ships with Secure Boot locked, so for this we'd provide units with Secure Boot unlocked and an attestation key that marks them as dev-only, so a modified unit can never present itself as a trusted production device. An auditable path where you implement your own delegation format and verify the whole chain fits what you've built better than a black box.
We are in continuous development, and we won't go to market until it's been in other hands and independently reviewed. We'd rather have our claims tested by people trying to break them than make firm public statements ahead of it. If you'd want to be a part of that, we'd value your eyes in particular.

2026-07-20 00:18:11 UTC

GM Nostr, hope everyone had a great weekend

2026-07-18 14:09:41 UTC

- reply

Napkin the downside. AI capex is around 5% of US GDP and carrying most of its growth. Cut the buildout 40% in a digestion phase and you remove 1.5 to 2 points of GDP. That is a recession with $1.5 trillion of AI debt repricing underneath it. The response writes itself. Rates back to the floor, balance sheet expansion, deficits into the slowdown. A compute glut is deflationary so the Fed will have cover to do it.
That is the part that matters. The fix for overinvestment is always the same, print. Capital does not rotate back into negative real yield bonds, it hunts hard assets. Gold first, then the harder one.
Bitcoin does not need AI money to rotate in. It needs the monetary response to AI money being wrong.

2026-07-18 14:08:47 UTC

Had a thought so I’ll share it.
Been running numbers on the AI buildout and the maths does not close.
The big five will spend around $670 billion on AI infrastructure this year. Total AI revenue across the whole industry is maybe $80 billion. Roughly 10 to 1, spend to revenue, on chips that are obsolete in 4 to 5 years. The revenue does not just need to grow, it needs to 10x inside the life of the hardware being bought right now.
So where does the revenue come from. The new answer is ads. OpenAI put ads on the free tier and hit $100m run rate in six weeks. Sounds like demand. It is not. Global ad spend is stuck around 1% of GDP and has been for decades. Ad dollars moving into AI chat are dollars leaving search and social. Reallocation, not creation. Google spending record capex to cannibalise its own search revenue is not value, it is defence.
Strip the ads out and the whole $5.5 trillion bet through 2030 rests on one thing, enterprise productivity actually showing up. Maybe it does. But if the labs believed it was coming fast they would not be bolting an ad model onto free chat.
#BTC #AI #NOSTR

2026-07-17 01:11:15 UTC

- reply

Thanks for taking the time to look over the site.
Yes, that's exactly the residual trust. We can make the firmware verifiable, we can't make the silicon verifiable from your chair. We'd rather say that plainly than pretend otherwise.
On signing, the firmware signs three things with three separate keys:
1. Bitcoin keys sign PSBTs only. Always behind a separate spend PIN with physical confirmation on the device. Transport is your call, fully airgapped over QR or over the local network.
2. Your Nostr key signs events, any kind, either locally to the web app or remotely via NIP-46. Plus NIP-44 encrypt/decrypt for DMs. The key never leaves the device either way, only signatures come out.
3. A per device attestation key inside the secure element signs genuineness challenges and CIPHER game scores. Device identity only, never touches your keys.
No generic "sign this hash" API anywhere. And since the hardware itself could sign anything, that scope is really a property of the firmware, which is why it being open and reproducible matters.
That said, developers may well want to sign with other kinds of key pairs, and for that we may offer unlocked dev devices. Their attestation keys would live on a separate dev list in the registry, so a dev unit always verifies as a dev unit and can never pass itself off as a production device.

2026-07-16 12:42:09 UTC

- reply

Haha yes reminds me of that CoD map. But no favilla is Latin for ember or spark. Ember is our cat

2026-07-16 12:39:51 UTC

- reply

Favilla is Latin for Ember or spark

2026-07-16 11:26:02 UTC

- reply

check out my client . It has non stop feed when you are at the top of the feed.
Favillakey.io/bunker

2026-07-16 11:03:04 UTC

- reply

Complementary is exactly how I see it too. favillakey.io/security is best read for now. Would genuinely value your read on it. The site is a bit simplified, I will add the technical document and firmware to it later.

2026-07-16 10:29:01 UTC

- reply

Secure!!!!

2026-07-16 10:23:48 UTC

- reply

Respect! that's the right separation. untouchable root, replaceable daily key. I built KEY around the same model, just with the daily signer in hardware rather than NIP-07.

2026-07-16 09:38:35 UTC

- reply

CIPHER · SIGNAL LOST at 96,372 — NEW ALL-TIME HIGH
21 steps forged into embers · run 14
signed by the secure element · verify: favillakey.io/cipher#run=b4501a62e5e7db412135904f030572297c3a53a6fda42c6ba1b8fe875f5960d0
#favillacipher

2026-07-16 09:12:28 UTC

- reply

CIPHER · SIGNAL LOST at 93,515 — NEW ALL-TIME HIGH
21 steps forged into embers · run 12
signed by the secure element · verify: favillakey.io/cipher#run=b4614766deae9b6b0d83479701283d6169834b75113a5ebf93dd1c2aabaec2e6
#favillacipher

2026-07-16 05:03:47 UTC

TEST

2026-07-15 07:51:08 UTC

- reply

fair, so make it per relay. prompt once when a new relay asks, remember the answer, done

2026-07-15 07:41:17 UTC

GM! Finished building the device verification system for Favilla KEY. At provisioning, each device generates its own unique attestation privkey inside the secure element . it never leaves the chip. The pubkey is published to a signed registry hosted at favillakey.io, so anyone can verify their device is genuine.
https://blossom.primal.net/538935f3271d1d66711af2728d510a062ccbd75272d87ce0cda87c7035f18e30.mp4

2026-07-15 02:19:15 UTC

- reply

Right, the fatigue is at the signer not the relay. imo Kind 22242 should be auto-approve by default in every bunker. One-time, one-relay, nothing to steal, save the toasts for kinds that actually do something.

2026-07-15 00:50:44 UTC

- reply

Nice. Sign only mode that blocks nip44 decrypt is a good idea.
been building a nip-46 bunker too, but in hardware, secure element and physical buttons. Good to see it attacked from the software side.

2026-07-15 00:28:29 UTC

GM! Hope everyone has a great day!

2026-07-14 09:17:50 UTC

- reply

Looks amazing

2026-07-14 05:24:48 UTC

- reply

GM!

2026-07-14 05:14:56 UTC

- reply

Get keys off the internet. Verify, don't trust. This includes Nostr!

2026-07-14 05:05:12 UTC

- reply

Build Web of trust , filter to only see followers or followers, followers.

2026-07-14 05:03:42 UTC

- reply

WoT

2026-07-14 04:40:09 UTC

Using Primal app via FavillaKEY remote signer. TEST

2026-07-14 03:43:24 UTC

How are you storing nsec these days?Browser extension, Amber, a remote signer over NIP-46, something airgapped ? Trying to get a feel for what people actually use and trust.

2026-07-14 03:20:15 UTC

GM Nostr !☕️
I have updated the favillakey.io website, will be publishing the firmware soon
#gm #nostr #btc

2026-07-13 01:21:51 UTC

Air gapped note

2026-07-13 00:53:54 UTC

GM Nostr ☕️

2026-07-10 09:15:54 UTC

- reply

2026-07-09 04:04:47 UTC

GM Nostr! Been busy building, Newest and hopefully last PCBA in action , secure element and accelerometer on board. Here’s a quick demo of the safety motion lock option … plus a quick preview of opening CIPHER, the Favilla key game. More on that soon.
https://blossom.primal.net/bd0be16357eef029b8f4bf29d475ba87acb1d395b3202ae5d5d19c4fb6fc8635.mp4

2026-07-08 08:49:41 UTC

- reply

2026-07-04 23:48:28 UTC

- reply

Happy birthday!

2026-07-04 08:31:30 UTC

- reply

💯 keep on building !

2026-07-03 02:01:20 UTC

Test 📝

2026-07-03 01:38:29 UTC

- reply

⚡️⚡️ 🛠️🛠️ every day !!

2026-07-03 01:27:18 UTC

GM Nostr ! Keep building !

2026-07-02 12:13:14 UTC

- reply

GM mr Ross

2026-07-02 09:03:10 UTC

- reply

2026-07-02 08:56:40 UTC

- reply

GM , and then they treat that data like its theirs to lose

2026-07-02 07:23:28 UTC

- reply

GM☕️

2026-07-02 07:12:33 UTC

- reply

GM, so satisfying

2026-07-02 07:11:05 UTC

- reply

GM, and to you , also

2026-07-02 06:19:08 UTC

- reply

GM, when soon ? 😂

2026-07-02 04:27:05 UTC

Excited! First run of CNC housings for Favilla KEY have arrived! Happy with the result so far. Waiting on glass and buttons now.
https://blossom.primal.net/6a72faa6eee3637ce11d1b3ce5fcad82a3546c8e9052f2297c1be66186f765ab.mp4
https://blossom.primal.net/a00c06eedb45e99ab0ad2df6d8c7b0a64d33cabe478171bbe443b8e9168f3868.jpg

2026-07-02 02:17:30 UTC

- reply

Haha I love this

2026-07-01 22:53:21 UTC

- reply

Massive congratulations!

2026-07-01 13:45:20 UTC

- reply

Haha good job, someone has todo it !

2026-07-01 13:29:02 UTC

- reply

2026-07-01 13:28:03 UTC

- reply

GM!

2026-07-01 09:03:16 UTC

- reply

Agreed , I have been working on Favilla KEY a, hardware signer , seed/keys protected by a secure element. Will be open sourcing the code soon and delivering development units to people who willing to use and verify it.
Favillakey.io
Also have built a remote connect only Nostr client.
Favillakey.io/bunker

2026-07-01 08:44:28 UTC

- reply

2026-07-01 08:39:09 UTC

- reply

The future is great, but sometimes I wish I were back in time.

2026-07-01 07:54:15 UTC

- reply

Haha GM , yep

2026-07-01 07:15:22 UTC

- reply

It’s amazing how obvious it is, yet most don’t see it .

2026-07-01 07:02:06 UTC

- reply

GM! it only grows

2026-07-01 07:00:42 UTC

- reply

2026-07-01 07:00:19 UTC

- reply

2026-07-01 06:31:27 UTC

- reply

2026-07-01 06:29:59 UTC

Good afternoon! #nostr ,
I have been building this client for a while now. It was mainly to test remote connections with our Favilla KEY hardware signer. I have added a Nostr connection option now for those that want to have a play.
Here’s a demo of me remote singing a test account using the Primal remote signer option.
DM me a hello , with zap emoji reaction and I’ll private zap you back.
Also play around with the colour theme randomiser.
https://blossom.primal.net/6b536cf7b1d6661184777ed1b417d09cbda240a73468eea3f882f42a8c1522db.mp4

2026-07-01 02:37:22 UTC

- reply

Yes, when I have the production Developer version (just means it’s won’t have RF compliance yet) ready I’ll send you a DM .

2026-07-01 02:20:31 UTC

- reply

I am building something similar into Favilla key. Sign a PSBT, it gets stored on your hardware device , you set an inheritance mode. X amount of time from no activity from Y npub, broadcast to network.

2026-07-01 01:13:14 UTC

- reply

Plus in Australia , UK and soon USA. They are banning under 16s from social media, fining the companies. Due to Nostr architecture, for now, in most cases a client or relay should be safe.
In regards to the chat control and privacy over reach that UK is pushing (having your private messages accessed), I have built a solution that is native to the Nostr ethos.

2026-07-01 01:04:31 UTC

- reply

This is so true , though governments world wide seem to be pushing people towards Nostr . The New law are making the convenience of centralised social media inconvenient. We are just early.

2026-06-30 10:48:28 UTC

Testing Nostr.com!

2026-06-30 10:26:39 UTC

GE Nostr

2026-06-29 10:14:11 UTC

Nostr is saved !!
Albo’s $99M crackdown removed 5 million under-16 accounts from social media.
Welcome to Nostr, kids. There are no accounts here to remove. 🧡
https://blossom.primal.net/79c9a635350ec26bfbdebe2898a1c7e266bb3fde743639e02d3a8169316f79c1.jpg

2026-06-29 07:33:02 UTC

- reply