From: Anthony Towns <aj@erisian.com.au>
To: Jonas Nick <jonasd.nick@gmail.com>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Covenants Support - Bitcoin Wiki
Date: Tue, 10 Dec 2024 06:13:50 +1000 [thread overview]
Message-ID: <Z1dPfjDwioa/DXzp@erisian.com.au> (raw)
In-Reply-To: <941b8c22-0b2c-4734-af87-00f034d79e2e@gmail.com>
On Fri, Dec 06, 2024 at 09:45:31PM +0000, Jonas Nick wrote:
> I do not think the segwit support page serves as a suitable template for
> building rough consensus, in general and for covenants in particular.
The segwit page followed the example of the p2sh page [0]; I wasn't around
for that, but from the reporting it didn't sound like a particularly
clean result, with the result coming down to the proposers of BIP 16/17
respectively voting "No" and "Very weak" to the competition, and "No"
being worse than "Very weak". It's not a good example to follow.
[0] https://en.bitcoin.it/wiki/P2SH_Votes
The only polling question that's really necessary for establishing
that consensus exists is "have all my objections/concerns been
addressed? [yes/no]" (perhaps with a followup asking your top outstanding
concerns are). If the poll is widely open, and everyone's answer is
"yes"; that's consensus. (Even if some people's answers are "no"; it
might still be "rough" consensus, of course)
Personally, I find it hard to take any of this remotely seriously at this
point; the most recent example is reardencode's claim to have created
scripts for lightning-symmetry using either LNHANCE or CCV. This was
done via a tweet [1] and a gist [2], without any real exploration of
what the full transaction flow would look like. Did it have any chance of
working? Well, no, because it had an invented "3DROP" opcode instead of
"DROP 2DROP" or similar, just as if it were ChatGPT hallucinating what
a wallet script might look like. That would have failed as soon as it
had been run through any of the script test environments out there,
let alone through any actual node software, so it's clear that nobody
involved had done anything of the sort, even locally. If the proponents
aren't taking their proposals seriously, why on earth should anyone else?
[1] https://x.com/reardencode/status/1864749512113483993
[2] https://gist.github.com/reardencode/ae982ede45af12fe1ff7248fd6f1958c#file-ctv-csfs-vault-txt
Cheers,
aj
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/Z1dPfjDwioa/DXzp%40erisian.com.au.
next prev parent reply other threads:[~2024-12-09 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 14:08 [bitcoindev] Covenants Support - Bitcoin Wiki /dev /fd0
2024-12-06 21:45 ` Jonas Nick
2024-12-07 0:29 ` /dev /fd0
2024-12-07 1:42 ` Yuval Kogman
2024-12-09 20:13 ` Anthony Towns [this message]
2024-12-09 20:45 ` Brandon Black
2024-12-11 13:28 ` Anthony Towns
2024-12-11 15:11 ` Brandon Black
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z1dPfjDwioa/DXzp@erisian.com.au \
--to=aj@erisian.com.au \
--cc=bitcoindev@googlegroups.com \
--cc=jonasd.nick@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox