27
yashraj
276171f64b945ad9978a2045df86a0cbaa92f0eefc1eb0a696e301d1e660762c
@bitcoin.design contributor focussed on bitcoin, privacy and security.

Always feel important and like an influencer once a year when I re-post the same tweet onto nostr

—–/—-/——-

Was a treat to speak at nostr:npub1dwah6u025f2yy9dgwlsndntlfy85vf0t2eze5rdg2mxg99k4mucqxz7c52 privacy edition! Thanks to the inimitable nostr:nprofile1qqsvh300dvquh50l5t9et2257pxrsk5ndsdgdcdmnnxl9nc0f6l2ejcpzpmhxue69uhkummnw3ezumrpdejqzyrhwden5te0dehhxarj9emkjmn9xsn69h & team for having me.

Thanks to the nostr:nprofile1qqsgc2dny8g083sngwyzafyky05ywutfpng9vmjqhy8s3ewngvm24gqprfmhxue69uhkummnw3ezu7n9vfjkget99e3kcmm4vshsz9mhwden5te0dehhxarj9ehkuumpw3ejummjvuhsujanvd Foundation for supporting my efforts to make on-chain privacy accessible to anyone who wants to protect their rights.

Here’s the deck.

Please feel to comment/DM for thoughts, questions or collabs!

https://drive.proton.me/urls/JC8VT617SC#VSoxZVY3YkDL

Had a fascinating convo with nostr:nprofile1qqsv9xjae88ys858zezwapvcz8wppg2e5pqha8yjku0hmx4amg08axcpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgcwaehxw309ahx7um5wgh8xurjdamx7mmnwshxumq3p764m yesterday about hot keys that can only sign timelock refresh payjoin transactions using the magic of miniscript… how would it detect/ensure errant txns arent being signed?

Of course, i was wondering you had any more specific thoughts or conjecture regarding this… even if modes of thinking & governance are cyclical, a relapse just couple decades in needs a more specific explnation IMO.

A signpost is that the public itself is staunchly against this, and yet is happening again.

🤝󠅓󠅑󠅣󠅘󠅥󠄲󠅠󠄷󠄶󠅛󠅓󠅜󠄾󠅜󠅒󠅞󠅁󠅗󠅊󠅞󠄺󠅦󠅒󠅃󠄲󠄾󠅑󠅇󠄥󠅠󠅉󠅝󠅜󠄠󠅓󠄢󠄶󠅤󠅕󠄳󠄺󠅟󠅔󠄸󠅂󠅧󠅓󠅪󠅟󠅦󠄼󠄢󠄡󠅠󠅒󠅞󠅁󠅥󠅒󠅇󠅜󠅥󠅑󠅇󠄺󠅠󠅔󠄸󠄽󠅥󠅉󠄢󠄶󠅪󠅑󠄳󠄩󠄳󠅑󠅈󠅂󠅚󠅒󠄢󠅜󠅥󠅉󠅈󠅃󠄲󠅟󠅝󠄶󠅠󠅃󠄱󠄲󠅁󠄲󠅆󠄴󠅧󠅃󠅅󠄶󠄷󠅉󠅈󠄳󠄴󠅟󠄢󠄶󠅘󠄱󠅇󠄶󠅚󠅇󠄳󠄵󠄴󠅥󠄣󠅜󠅘󠅙󠅁󠅑󠅕󠄠󠄩󠄿󠄴󠅑󠅔󠅔󠅕󠅙󠄸󠄸󠅀󠅉󠅇󠅤󠅞󠄳󠅛󠄦󠅃󠄾󠄝󠅢󠄿󠅩󠅂󠅒󠄽󠄡󠅙󠅀󠄝󠄿󠅩󠅘󠅘󠅓󠄣󠅘󠄱󠅉󠅪󠅓󠄣󠅉󠅪󠄶󠅝󠄽󠅇󠄵󠅧󠄾󠅇󠄺󠅛󠄾󠄴󠅓󠄢󠄾󠅄󠅅󠄡󠄽󠅚󠅆󠅙󠄽󠅇󠄾󠅙󠄾󠅝󠅉󠄣󠅊󠅚󠄾󠅜󠄽󠄴󠄱󠄢󠄾󠅚󠅛󠅨󠅊󠅇󠄾󠅚󠄽󠄴󠄵󠅩󠄽󠄢󠅆󠅜󠅊󠅇󠄺󠅛󠄽󠄷󠄵󠄠󠄿󠅄󠅗󠅪󠅉󠅪󠅓󠄣󠄿󠅄󠅅󠅩󠄽󠅄󠅘󠅙󠄽󠄦󠄾󠅘󠅉󠅁󠅂󠅘󠅉󠄡󠅗󠅘󠄱󠅢󠅉󠄱󠄱󠅔󠄧󠄳󠄦󠅝󠄝󠄥󠅈󠅏󠄾󠅏󠄺󠄲󠅔󠅣󠄾󠅙󠅟󠅙󠅃󠅇󠄷󠅜󠅘󠄣󠅓󠄦󠄥󠅙󠅙󠅅󠅞󠅧󠄼󠅇󠅣󠄝󠄺󠅕󠅉󠅈󠄾󠄤󠅁󠄷󠅂󠅜󠄽󠅚󠄾󠅝󠄾󠅝󠅉󠅪󠄽󠄢󠄽󠄤󠄾󠅚󠅅󠄣󠄽󠄷󠅉󠄠󠅊󠅄󠅜󠅜󠄽󠄴󠅁󠅧󠄽󠄴󠅊󠅝󠅊󠅇󠅆󠅛󠄽󠄴󠅅󠄣󠅉󠅄󠄾󠅝󠄾󠅪󠅛󠄡󠄾󠄷󠄹󠅨󠄾󠅝󠄶󠅙󠄾󠅪󠅛󠄥󠅊󠅄󠄲󠅝󠄽󠅄󠅜󠅛󠄽󠅪󠅔󠅜󠅊󠅝󠄵󠅪󠄾󠄢󠄽󠅩󠄾󠅪󠄿󠅚󠅉󠅇󠄵󠅁󠅉󠅇󠄾󠅉󠄹󠅁󠄿󠅚󠅁󠅟󠅀󠅨󠅁󠄶󠅂󠄠󠄲󠅩󠅞󠅠󠅉󠄦󠄸󠅄󠄩󠅒󠅠󠄾󠅗󠅉󠅩󠅖󠄹󠅕󠅇󠅠󠅟󠅞󠅙󠄨󠅘󠄣󠅘󠅨󠅕󠅂󠅛󠄵󠄡󠅝󠄶󠅪󠅕󠄵󠄱󠄣󠄽󠅪󠅅󠄡󠅊󠅝󠄹󠄢󠅉󠅪󠅜󠅜󠄿󠄷󠅂󠅙󠄽󠅝󠄶󠅘󠅊󠅄󠄹󠅨󠅉󠅄󠅜󠅚󠄾󠅄󠄲󠅚󠄿󠄷󠅉󠄤󠅊󠅇󠄵󠅧󠄾󠄴󠄾󠅘󠄾󠅪󠅆󠅘󠄾󠅄󠄾󠅝󠅊󠄴󠅜󠅛󠄽󠅚󠅅󠅪󠄾󠅚󠄱󠅪󠄿󠅄󠅅󠄠󠅊󠅚󠄽󠄠󠅉󠅪󠅆󠅝󠅊󠄷󠄽󠅨󠄾󠅚󠄵󠄤󠅉󠅈󠅆󠅚󠅓󠄢󠄶󠄠 nostr:npub15dnln6cukw3yrflnv3hnrntdt9amh0uw466u6tns05ymqp3nal4qzz3lfc

🥹󠅓󠅑󠅣󠅘󠅥󠄲󠅠󠄷󠄶󠅛󠅓󠅈󠅂󠅟󠅉󠅇󠄥󠅢󠄹󠄸󠅜󠅦󠅔󠅃󠄲󠅪󠅉󠅈󠅂󠅦󠅓󠄢󠅘󠅠󠅉󠅇󠄡󠄤󠄹󠅝󠅘󠄠󠅔󠄸󠄲󠅪󠄿󠅙󠄨󠅦󠅒󠅇󠅜󠅥󠅔󠄳󠄥󠅤󠅑󠅇󠄥󠅠󠅉󠅝󠅜󠄠󠅓󠅩󠄥󠅚󠅉󠅈󠄾󠅟󠄼󠄠󠄺󠅠󠅔󠄷󠄾󠅦󠅑󠅇󠄥󠅘󠅔󠄹󠄷󠅙󠅉󠅇󠅜󠄹󠄱󠄶󠄱󠄶󠅅󠅀󠄲󠄺󠅁󠅅󠅊󠅘󠅓󠄹󠄿󠅚󠅉󠅇󠄵󠄲󠅉󠅇󠄾󠅉󠄹󠅁󠄿󠄤󠅚󠄨󠄣󠄿󠅁󠄺󠄧󠅟󠅒󠅨󠅉󠅝󠄹󠄣󠅜󠄣󠅘󠅑󠅈󠅁󠄠󠅡󠅑󠅅󠄶󠅀󠅉󠅗󠅉󠄴󠅒󠅊󠄵󠅕󠅩󠅦󠅁󠅝󠄹󠅢󠅤󠅝󠄶󠅪󠅕󠄵󠄱󠄥󠄾󠄴󠅛󠄤󠄾󠅚󠅔󠅚󠅉󠅚󠅗󠄤󠄾󠄴󠅔󠅙󠄽󠅪󠅗󠅪󠄾󠅪󠅁󠄤󠄽󠄴󠅗󠅩󠄽󠅪󠄵󠄡󠅊󠅝󠅅󠄤󠅊󠄴󠄽󠄥󠄽󠄢󠅊󠅛󠅊󠄴󠅅󠄡󠅊󠅝󠄽󠅧󠄽󠅪󠅁󠅨󠅉󠅪󠄱󠅩󠄽󠄴󠅆󠅜󠄿󠄷󠅆󠅛󠄿󠅄󠅜󠅙󠄽󠅝󠅉󠄥󠄽󠅇󠄵󠄣󠄿󠄷󠄵󠄥󠅟󠄢󠄶󠅘󠄲󠄷󠄶󠅚󠅇󠄳󠄵󠄴󠄨󠅤󠅀󠄺󠅔󠅚󠄝󠅔󠄱󠅓󠅢󠅄󠄷󠅇󠅉󠅃󠅠󠄦󠅑󠅀󠄽󠄱󠄹󠄸󠄩󠅣󠄳󠄣󠄷󠄩󠅙󠅚󠅢󠄳󠅈󠄹󠅊󠄳󠄣󠅤󠅤󠄩󠅜󠅘󠅓󠄣󠅘󠄱󠅉󠄢󠅁󠅨󠅊󠅄󠄽󠄣󠄾󠄢󠄽󠄤󠄿󠄴󠅓󠅩󠄾󠅚󠅁󠄣󠄾󠄢󠄺󠅜󠅉󠅪󠅅󠄤󠄾󠅝󠅁󠄣󠅊󠄴󠄵󠅩󠄾󠅪󠄾󠅛󠄽󠅄󠄱󠄢󠄾󠅪󠅉󠄡󠄽󠅪󠄽󠄤󠄽󠄴󠅂󠅚󠅉󠄢󠅁󠅨󠄽󠅪󠄹󠄣󠅉󠄢󠅆󠅘󠄽󠄴󠅅󠅪󠅊󠅄󠅘󠅛󠄾󠅄󠅁󠅧󠄽󠅚󠄽󠅨󠅊󠅡󠄾󠅘󠅉󠅂󠄲󠅘󠅉󠄡󠅗󠅘󠄱󠅚󠅣󠄨󠄤󠅕󠅦󠄠󠅑󠄤󠅄󠄽󠅡󠄱󠅟󠅚󠄥󠅤󠅣󠅨󠅑󠅞󠅇󠅕󠅀󠅢󠅣󠅝󠅩󠅞󠅒󠅈󠅧󠄻󠄥󠅕󠅕󠄲󠄩󠅦󠅨󠅠󠅜󠅀󠅉󠅈󠄾󠄤󠅁󠄴󠅅󠅩󠄽󠅚󠅉󠄤󠅊󠅄󠄾󠅜󠄽󠅄󠅛󠅪󠄽󠄴󠄹󠅧󠅉󠅄󠅂󠅙󠄽󠅪󠅁󠄣󠄽󠅝󠄾󠅝󠅊󠅄󠄹󠅨󠄽󠅚󠅆󠅚󠄽󠄷󠅅󠅩󠅊󠅚󠅗󠄣󠄽󠅄󠅅󠅨󠅉󠄢󠅂󠅘󠄽󠅚󠄾󠅜󠅉󠅪󠄲󠅘󠄽󠄷󠅅󠅪󠅊󠄴󠅗󠄠󠅊󠅄󠅗󠅩󠅊󠅄󠄽󠅪󠄽󠅚󠅔󠅙󠄾󠄴󠄾󠅘󠅔󠅇󠄾󠅪󠅉󠅈󠅁 nostr:npub1mznweuxrjm423au6gjtlaxmhmjthvv69ru72t335ugyxtygkv3as8q6mak

Fuck I’ve been spending time on the wrong app again 💀

happy to be back - hope I manage to stay this time 🥶

Replying to Avatar willsin

Perhaps this is a warrant canary, coz they cannot talk about some things as per UK law. What page did you find this on?

Thanks much nostr:npub1kmwdmhuxvafg05dyap3qmy42jpwztrv9p0uvey3a8803ahlwtmnsnhxqk9 🫠🥰

nostr:note13v3lal9jtf2u4j390nd9zyzkqdn2mnn438696mgdmcrevf3r7h9qyhxzta

good one… same as the ones they had before? 😬

Replying to Avatar Wasabi Wallet

🚨 New release 2.2.0.0 is out 🚨

🥕 Taproot receive addresses

🚀 Faster transaction broadcasting

🔍 Help to setup and find a coordinator.

⏫ More accurate CPFP fee estimation

📉 Safer protocol

🪲 Backend optimizations

Release notes & Download: https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.2.0.0

🥕 Taproot receive addresses

Users can now choose taproot when generating a new receiving address. Spending a taproot input is 16% cheaper compared to spending a native segwit input. Users aren’t the only ones that benefit - Bitcoin nodes can verify taproot’s signatures faster than legacy ones, so the entire network gets a little speed boost.

🚀 Faster transaction broadcasting

A more sophisticated transaction broadcasting mechanism was introduced to make the process faster. Transactions are now broadcast to multiple nodes in parallel (through the Tor network) and fail more quickly if the transaction is rejected by the network. Users who upgrade will notice it now takes half as long to send their coins.

🔍 Help to setup and find a coordinator

A new message is now shown when no coordinator is configured, along with some help to understand how to find and setup one.

⏫ More accurate CPFP fee estimation

The CPFP feature now takes into account the fee paid by the parent transaction. In previous releases, the child transaction assumed the parent paid 0 sats in fees, and thus always overpaid for the speed up.. This improvement will be especially significant in high-fee environments, where the CPFP feature is most useful!

📉 Safer protocol

In order to avoid introducing unknown incentives and to limit risk to users, the coordination fee concept has been removed. Only coinjoin coordinators that don't charge any coordination fee continue to be supported. Read more: https://blog.wasabiwallet.io/killing-coordination-fee/

🪲 Backend optimizations

Users who run a Wasabi backend can now do so with a pruned node and significant CPU/RAM savings. This makes hosting a backend much cheaper and helps to decentralize this component which Wasabi clients still depend on.

nice… wen silent payments 🥲?