This is a really good (and entirely non-technical, for those who glaze over at equations) summary of a very thorny issue: repudiability in digital communications (it's technically only about DKIM, but the points made apply to other protocols than email).
I think I do agree with the conclusions, but it's something that isn't always so clear (how useful *in reality* are protocols like OTR, for example?)
Transcript of Jonas Nick, Tim Ruffing on MuSig, MuSig-DN and MuSig2 on @stephanlivera podcast https://diyhpl.us/wiki/transcripts/stephan-livera-podcast/2020-10-27-jonas-nick-tim-ruffing-musig2/
I've written about the evolution of the signature size in Bitcoin over the years.
NIck Szabo shared this on Twitter 😂
Started rebuilding joinmarket.me , see here: http://joinmarket.me/pages/main-page.html .. it's going to take quite a while, because I've got a lot on my plate.
(Rebuilding the articles isn't *too* bad, there are just a few steps I need to take in each case, and the formatting will be scuffed, but oh well).
I'm using pelican on github-pages, although I'll probably move back away from the latter to my own self-hosting eventually.
(yes there is fun with TLS going on, no surprise there lol).
"We didn't call it fuzzing back in the 1950s, but it was our standard practice to test programs by inputting decks of punch cards taken from the trash.
We also used decks of random number punch cards. We weren't networked in those days, so we weren't much worried about security, but our random/trash decks often turned up undesirable behavior.
Every programmer I knew used the trash-deck technique."
-- Gerald M. Weinberg
Default Signet, Custom Signets and Resetting Testnet https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-August/018145.html
@SimpleAristocrats Anything new is going to be risky. That was true once of Bitcoin multisig (hello off-by-one bug), P2SH (hello 520 byte push limit), and segwit (hello fee overpayment attack). It'll also be true of schnorr. However, one of the nice things about the commitment to soft forking in new features is that they're optional---you don't need to use P2SH or segwit if you don't want to and you'll also be able to let other people take the early adoption risk of trying schnorr/taproot.
Next Wednesday's Bitcoin Core PR Review Club is on PR 19339 "Re-delegate absurd fee checking from mempool to clients" (rpc/rest/zmq, tests, validation, wallet).
Notes and questions are up -- thanks Gloria Zhao for hosting.
Joinmarket 0.7.0 release published:
BIP78 payjoin is the main user-noticeable change, you can pay in Qt or on command line, to https servers or onions, with a p2sh wallet or a native bech32 wallet. URIs can just be pasted in and recognized.
There's a lot of other stuff in the background e.g. basic PSBT support. Make sure to read the release notes if you need to upgrade. Py3.6 is a requirement now.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!