This week’s newsletter describes the block parsing bug affecting BTCD and LND last week, summarizes discussion about a planned Bitcoin Core feature change related to replace by fee, outlines research about validity rollups on Bitcoin, shares an announcement about a vulnerability in the draft BIP for MuSig2, examines a proposal to reduce the minimum size of an unconfirmed transaction that Bitcoin Core will relay, and links to an update of the BIP324 proposal for a version 2 encrypted transport protocol for Bitcoin. Also included are our regular sections with summaries of changes to services and client software, announcements of new releases and release candidates, and descriptions of notable merges to popular Bitcoin infrastructure projects.
No two users can claim the same addresses on the platform ensuring that there is no cross-attestation. Additionally, if a user removes an address or wallet, that address cannot be re-attested for at least 60-days.
Block (formerly Square) will be manufacturing their upcoming hardware wallet in Austin, Texas. This post highlights the process they took when making this decision.
No one other than the intended recipient can read transmitted messages, not even Threema as the service operator. It’s not required to provide any personal data whatsoever: If so desired, Threema can be used completely anonymously, i.e., without disclosing one’s phone number or email address.