frost2x awaiting approval in the chrome web store 😴

what is the rate limit on the damus relay? "you are noting too much" how much is too much? 😭

I put all this work into asynchronous batch handling of NIP-07 requests, and nostr clients just `await window.nostr.doSomething()` one request at a time. It's actually pretty crazy that clients behave like this. This old and busted synchronous request paradigm needs to change, especially for: * Primal, which requires signing of multiple events with each page refresh, all of them blocking. * Nostrudel, which has a "decrypt all" button, but then decrypts events one at a time. Does nos2x support asynchronous handling of requests? I didn't notice anything blocking, so I want to say yes (assuming you have permissions set). If a client makes requests to a signing device, and those requests have a) permissions and b) no dependencies, then they shouldn't block other requests. Let the requests flow freely!

me going through the jira backlog

Just upgraded bifrost to perform single-round batch signing of messages, similar to how bitescrow worked with building covenants. Batching signatures allows for very fast and robust signing of PSBTs and multi-transaction packages, which will hopefully unlock many kinds of bitcoin protocols over frost and nostr. The frost2x wallet is almost complete: ``` window.bitcoin = { getAccount() // done, getBalance() // done, getUtxos(amount) // done, signPsbt(psbt, manifest) // in progress } ``` Very exciting times ahead!

gm nostr today is a great day to build a wallet

It is pretty disgusting how much I violate bitcoin core on a daily basis using this. Complete and total disrespect. Just ramming through all sorts of dog-food transactions.

GitHub

GitHub - cmdruid/core-cmd: A suite of CI/CD friendly tools that plug into bitcoin core and help you interact with the blockchain.

A suite of CI/CD friendly tools that plug into bitcoin core and help you interact with the blockchain. - cmdruid/core-cmd