bitcoinplebdev's avatar
bitcoinplebdev
bitcoinplebdev@bitcoinpleb.dev
npub1s9et...lxzl
Implementation: voltage.cloud Founder: plebdevs.com Contributor: frostr.org Plebdev: pleblab.dev
bitcoinplebdev's avatar
bitcoinplebdev 8 months ago
Imagine if we had like flexible round-optimized schnorr threshold signatures transmitted by relays?

That would be cool lmao
bitcoinplebdev's avatar
bitcoinplebdev 8 months ago
Bitcoin / Nostr / Lightning do not require permission You can just get your hands dirty, become experienced, an expert. You can become more experienced, knowledgeable, capable than most all of the biggest influencers, talking heads, investors, and suits. You can become the adult in the room. I feel like more people need to realize this lol
bitcoinplebdev's avatar
bitcoinplebdev 8 months ago
I just realized if anyone has locked ecash to my pubkey I haven’t realized it? Unless I got “NutZapped”???? Help me kids…
bitcoinplebdev's avatar
bitcoinplebdev 8 months ago
Awesome thanks using it and thanks for the suggestions! I definitely will add NWC soon for instant zaps. I want to think about how to best do persistent identities for chats to write to nostr relays (currently anon zap is only scenario where we write rather than read) This will take: - better anon keypair persistence and handling (for chat sessions) - nip46 support (pass a chat your connect string eek) - FROSTR support (cause I don’t wanna give an LLM my whole ass private key / signer) View quoted note →
bitcoinplebdev's avatar
bitcoinplebdev 8 months ago
Amazing! Thank you for trying it out! Yeah loading in (unlocking) a share in igloo is basically taking it from being cold to hot so I try to make it pretty explicit in the UI but I can see how it’s a tad confusing More improvements, updates, and new signing clients coming soon! View quoted note →
bitcoinplebdev's avatar
bitcoinplebdev 8 months ago
KEY ROTATION WITH FROSTR

 Rotating keys with FROSTR is MANUAL
 Shares in a FROSTR keyset are interconnected so a rotation is either:
 - DESTROYING the entire old keyset (and creating a new one)
 OR
 - DESTROYING threshold of shares in the old keyset effectively ORPHANING any lost or compromised shares from that keyset There is no overly complicated rube goldberg multi-round rotation/revocation protocol
 TLDR; image