RT @bitcoinoptech
Bitcoin Optech newsletter #185 is here:
- describes an analysis of the proposed OP_CHECKTEMPLATEVERIFY (CTV) opcode’s effect on discreet log contracts
- summarizes a discussion about alternative changes to tapscript to enable CTV and SIGHASH_ANYPREVOUT
@arbedout 83 or 93? 83 seems super early to me.
RT @bitcoinoptech
Bitcoin Optech newsletter #182 is here:
- describes an idea to add accounts to Bitcoin for paying transaction fees
- recaps the "Erlay support signaling" Bitcoin Core PR Review Club Meeting
@arbedout Yeah, but that article says they don't have to disclose their trades until 45 days after making them, so it would be a very trailing ETF, basically perfect for congressional pumping a dumping.
(I know you were joking, it was just fun to think about the practicalities.)
@midnightmagic @livestradamus @jb55 I agree that's what hash commitments are, which is exactly the problem with them. If you don't build non-repudibility into the protocol, third-parties will create their own non-repuditiation systems on top of the protocol, and those third-party systems will be corruptible.
I'd rather have a system where people are verifying my signature on my posts than a system where people are asking trusted third-parties to attest to the contents of my posts.
@midnightmagic @livestradamus @jb55 in short, cryptographic non-reputibiliity > implict trust in archive.org.
@midnightmagic @livestradamus @jb55 doesn't really matter anyway. As long as your posts are public, a bunch of people will post hash commitments to your posts to opentimestamps, creating a believable set of attestations. In that case, it's better for publishers to cut out the middlemen and bake non-reputibility into the protocol so there's no risk the timestampers will collude to damage to publisher's reputation.
@midnightmagic @livestradamus @jb55 yeah, but Signal is a chat app used for private communication, nostr is for public microblogging. Non-reputibility would be a liability for nostr.
"It is easier to port a shell than a shell script."
-- Larry Wall
Me trying to explain what I do to a normal human:
"I work in an industry where, if you can type a semicolon, someone will probably throw a six-figure salary at you"
Them: "Cool, cool…"
"Oh also, some of the most difficult and time-consuming work I do is on nights and weekends, for free, for strangers I have no working relationship with."
Them: "Uhhhh…"
@borderdoggo Also, Drew's post about why using Discord for FOSS projects is a bad idea
https://drewdevault.com/2021/12/28/Dont-use-Discord-for-FOSS.html
@jb55 boosted this both because its cool and to remind me to try it.
follow me on https://nostr.com :
fd3fdb0d0d8d6f9a7667b53211de8ae3c5246b79bdaf64ebac849d5148b5615f
read about the nostr protocol here here:
Today, James Webb telescope switched on camera to acquire 1st image from deep space.
New version of Joinmarket, 0.9.2 :
https://github.com/JoinMarket-Org/joinmarket-clientserver/releases/tag/v0.9.2
Corrects an error in Qt where fidelity bonds were not preferred for takers like in CLI, and new IRC, and new opt-in rbf for ordinary spends. Please share as you see fit.
Bitcoin Optech newsletter #168 is here:
- summarizes a proposal to implement breaking changes in the DLC specification
- examines options for allowing recovery of closed LN channels using just a BIP32 seed
- describes an idea to generate stateless LN invoices
- includes popular questions and answers from the Bitcoin Stack Exchange
- continues the 'how to prepare for taproot' series: signmessage protocol still needed
Really interesting idea re: 'degrading multisignatures' laid out in @bitcoinoptech #166 (sent two weeks ago - I'm playing catchup)
