Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save michaelfolkson/352a503f4f9fc5de89af528d86a1b718 to your computer and use it in GitHub Desktop.
Save michaelfolkson/352a503f4f9fc5de89af528d86a1b718 to your computer and use it in GitHub Desktop.
Collect together concerns (alphabetical order by name) made public about premature BIP 119 activation speculation in
Adam Back: <>
AJ Towns: <>
alpacasw: <>
andhans_jail: <>
Bob McElrath: <>
BitcoinLizard: <>
BlueMatt: <>
Christian Decker: <>
darosior: <>
EricSirion: <>
francispouliot_: <>
GrassFedBitcoin: <>
John Carvalho: <>
Kevin Loaec: <>
Michael Folkson: <>
Murch: <>
Neil Woodfine: <>
nvk: <>
OneSirMeow: <>
Peter Todd: <>
Sachin Meier: <>
yojoots: <>
zndtoshi: <>
Copy link


However, I'm not sure how ethical it is to put someone's opposition on there without their express consent.

All the links were said in public (linkable) forums and if anyone contacts me privately I will certainly take their names off this doc and even consider deleting it entirely. I have used pseudonyms rather than actual names wherever possible. I understand your concern though.

The signals page is certainly more formal.

It isn't. It is a web page rather than a gist but any kind of positive comment towards CTV is being used as a "soft signal" indicating implicit support of this CTV activation attempt. The process for inclusion (and removal) of individuals is non-existent which this gist has copied.

Both are a form of authorized curation by a single individual, with non-originator contributions kept separately until curated into the presentation format.

Agreed. I don't like this as much as you don't. But I didn't start this. When a soft fork activation is attempted users naturally try to understand whether it has community consensus or not. Other than setting up this gist I didn't know what to do. Let what I believe is an inaccurate narrative that a soft fork activation attempt has community consensus ( when it clearly doesn't or repeat the same exercise to counteract what I believe is an inaccurate and misleading narrative.

Copy link

Very fair points. I'm inclined to agree. I think it's fair to want to push back on a one-sided narrative, and that page does look very one-sided. What tools we have available to us are clumsy. I also don't think Jeremy would want BIP-119 to go in any different than Taproot did, with over 90% consensus. Of course, how that consensus is measured might also have been imperfect. Have you looked into tx signalling any? Signals from txs signed by wallets are used by participating nodes. Tx fees are counted, rather than tx quantity. The dynamics and game theory of it are complex, though, there's certainly nuance in how it should work. Miners, developers, and users are all major factors. @ProofOfKeags and I were discussing all of this the other day. I'm considering formalizing a proposal. But that's just what we need, right? Just another BIP...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment