From: alicexbt <alicexbt@protonmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP-119 UASF
Date: Sun, 20 Aug 2023 17:46:01 +0000 [thread overview]
Message-ID: <Sd0HdkW021oxOx3N5nLA-gJr6bgGEZUNXbrGSmwJMXntc6nVWC5Hackx3C5PTQMfP-B1vwC9A14cDlkCu3K986oHD57ivIAxxdTC8JInZgY=@protonmail.com> (raw)
Hi Bitcoin Developers,
Note: This email is inspired from https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018538.html written by Chris Belcher
Lets compare all covenant proposals:
https://docs.google.com/spreadsheets/d/1YL5ttNb6-SHS6-C8-1tHwao1_19zNQ-31YWPAHDZgfo/edit#gid=0
Why general and recursive covenants are controversial:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-February/019976.html
Why I prefer CTV over APO?
- LN symmetry can be achieved with CSFS later if there is really a demand apart from twitter
- CTV improves LN
- CTV does not change how sighash works still we get covenants
- Less bytes
- More tooling
- Not recursive
- Not limited to taproot
- Other differences
MASF or speedy trial allows miners to coordinate and signal "readiness". This is misunderstood by lot of users as miners can always refuse to follow new consensus rules even after signaling or economics nodes can reject blocks with new consensus rules later.
Instead of doing this we could do a UASF in which things are clear that economic nodes enforce consensus rules and miners or majority of miners at this point wont go against bitcoin communities including nodes with some economic activity.
If there is a positive feedback, we could work on building UASF client for activation and bitcoin core can follow.
/dev/fd0
floppy disk guy
reply other threads:[~2023-08-20 17:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='Sd0HdkW021oxOx3N5nLA-gJr6bgGEZUNXbrGSmwJMXntc6nVWC5Hackx3C5PTQMfP-B1vwC9A14cDlkCu3K986oHD57ivIAxxdTC8JInZgY=@protonmail.com' \
--to=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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