Wow really groundbreaking stuff from Primal! This is super inspiring for us as we're trying to figure out best approach for IOS background signing at this moment! It's possible we might even be able to highjack this functionality to work with Frostr without any code changes?? Will report back 🤔 View quoted note →

igloo-cli version 1.0.2 has just been released! - QR codes in CLI for sharing credentials (toggle with Q) - Improved visuals: animated FROSTR intro + cleaner layout - Refactored arg parsing with better flag handling - 100 new tests massively increasing coverage Use igloo-cli to create a new Frostr keyset OR just run it as a signer:

GitHub

Release v1.0.2 · FROSTR-ORG/igloo-cli

What's Changed qr code display for shares and group by @AustinKelsay in #12 Feature/frostr icon by @AustinKelsay in #13 first pass test coverage o...

opus 4.5 is one of the smartest coding models in the world right now but I still struggle to get even the frontier LLM's to be able to grasp a lot of protocol details of Frostr when working with features in the code or docs. So either we are still (a little) smarter than the AI OR we are just retard maxxing too hard (likely) View quoted note →

Yes you could setup a 3/5 with frostr! It would be best to keep the nsec offline and cold after setup. It is worth understanding though that Frostr uses a "trusted dealer" setup of Frost meaning that the nsec WILL be known and contained on one computer in order to setup the 3/5 initially so basically you need at least one "trusted dealer" to setup the quorum View quoted note →

With frostr your keys DM each other to sign notes 💜

Working on nip46 frostr stuff with opus4.5... Bro doesn't stand a chance 😂 View quoted note →

Share it brother! View quoted note →

Absolutely! But we never wanted to change standards we just need them to be implemented consistently (and actually work lol) We are working on proposals internally though and also FIRST wanna do everything we can on the side of our apps / libs to make the experience as clean as possible (before proposing spec changes) View quoted note →

Should clarify - nip07 is quite simple and standardized across the ecosystem! Barely have run into issues with how the spec is implemented on clients BUT it is (mostly) trapped in the extension environment... View quoted note →

Frostr adds threshold signing to Nostr; no protocol changes! We integrate with NIP-07/46/55 so signed notes look completely normal to clients and relays (no one can tell you are threshold signing) The reality: every client/signer implements these specs differently... This fragmentation is our biggest challenge! Frostr hopes to be boring and simple but the ecosystem needs more standardization to realize this dream

Igloo Android App (alpha) is here! -

GitHub

Releases · FROSTR-ORG/igloo-android

Mobile signing device for nostr apps, using NIP-55 and FROSTR protocol. - FROSTR-ORG/igloo-android

Will say more later 👀

Thinking about partially signed notes 🤔

Say hello to Igloo Web - the easiest and most lightweight way to run a Frostr signer!

igloo web

GitHub

GitHub - FROSTR-ORG/igloo-web: Simple Web Implementation of a FROSTR signer built with igloo-core

Simple Web Implementation of a FROSTR signer built with igloo-core - FROSTR-ORG/igloo-web

Here's a diagram I made for NIP-46 signing flow with Frostr... - nostr client sends nip46 request to relay - igloo server listens for nip46 request - approves - passes to other signer (igloo-cli) for partial sig - gets response from cli and completes sig - passes back to relay - nostr client receives signed note and publishes to relays All of thise happens within like 2 seconds wtf

Yes they are! - View quoted note → View quoted note →

Key rotation is done manually still - you need the threshold of shares within that keyset (2/3 for example) locally in order to recover the nsec, this does not happen over nostr in some fancy protocol manner (only signing does) shares are only valid within a keyset meaning that if you have a 2/3 and you lose a share IF you destroy the other 2 shares than the third stolen share is ORPHANED. So to rotate at this time the steps are: - Recover nsec with threshold of shares - Use that nsec to generate a new keyset (can be any threshold) - DESTROY the shares in the old keyset TLDR; DESTROY AND OPRHAN View quoted note →

Key rotation is done manually still - you need the threshold of shares within that keyset (2/3 for example) locally in order to recover the nsec, this does not happen over nostr in some fancy protocol manner (only signing does) shares are only valid within a keyset meaning that if you have a 2/3 and you lose a share IF you destroy the other 2 shares than the third stolen share is ORPHANED. So to rotate at this time the steps are: - Recover nsec with threshold of shares - Use that nsec to generate a new keyset (can be any threshold) - DESTROY the shares in the old keyset TLDR; DESTROY AND OPRHAN View quoted note →

Here is our demo from Bitcoin 2025 this might help! View quoted note →

Split your nsec into a multisig The keys of that multisig talk to each other over nostr to sign notes View quoted note →

Rumors that first version of Frostr android signer will be released next week!?!?! Can't trust what you hear nowadays though... View quoted note →