Michael Folkson @[email protected]

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?)

https://blog.cryptographyengineering.com/2020/11/16/ok-google-please-publish-your-dkim-secret-keys/

#crypto

I've written about the evolution of the signature size in Bitcoin over the years.

https://b10c.me/blog/006-evolution-of-the-bitcoin-signature-length/

Censoring a president in the middle of an election is totally normal. /s

I thought I should start giving people a bit more about my thoughts on Joinmarket, from time to time. I guess it's mostly of interest to users of the system, but still:

https://joinmarket.me/blog/blog/oct-2020-update/

#joinmarket #bitcoin

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).

Looking for a tester for building #Bitcoin QT on OpenBSD
https://github.com/bitcoin/bitcoin/pull/19903

"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

Bitcoin Optech #113

- proposed change to LN commitment transactions
- discussion of a default signet
- standardizing temporarily trusted LN channels
- recently transcribed talks/conversations

original: https://bitcoinops.org/en/newsletters/2020/09/02/
archive: https://archive.vn/gGQNC

@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.

https://bitcoincore.reviews/19339

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.

https://github.com/JoinMarket-Org/joinmarket-clientserver/releases/tag/v0.7.0

#joinmarket #bitcoin