public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Eric Voskuil <eric@voskuil.org>
To: LORD HIS EXCELLENCY JAMES HRMH <willtech@live.com.au>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot NACK
Date: Wed, 17 Mar 2021 00:14:42 -0700	[thread overview]
Message-ID: <EA543368-EDE2-4407-99C4-22387F930184@voskuil.org> (raw)
In-Reply-To: <PS2P216MB091436C0E4EA5F587F8EE7879D6A9@PS2P216MB0914.KORP216.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 382 bytes --]


> If you actually believe the operation of consensus and the discussion relevant to that is a mundane or philosophical dissection of people's ability to grasp a humorous while on-topic but obligatorily unnecessary conversation you may prefer if you enquire how Bitcoin is censorship-resistant.

https://github.com/libbitcoin/libbitcoin-system/wiki/Censorship-Resistance-Property

[-- Attachment #2: Type: text/html, Size: 703 bytes --]

  reply	other threads:[~2021-03-17  7:14 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  3:23 [bitcoin-dev] Taproot NACK LORD HIS EXCELLENCY JAMES HRMH
2021-02-27 16:14 ` Jeremy
2021-02-28 11:36   ` LORD HIS EXCELLENCY JAMES HRMH
2021-02-28 13:07     ` Ariel Lorenzo-Luaces
2021-03-01  1:34       ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-01 22:37         ` Eric Voskuil
2021-03-02  1:16           ` Daniel Edgecumbe
2021-03-03  3:06             ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-03 11:58               ` eric
2021-03-03 16:30                 ` micaroni
2021-03-03 14:49               ` Erik Aronesty
2021-03-04  5:06                 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-05 14:04                   ` Ryan Grant
2021-03-10  6:34                     ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-11  0:47                       ` Keagan McClelland
2021-03-12 13:04                         ` R E Broadley
2021-03-12 22:30                           ` Eric Voskuil
2021-03-14 10:13                             ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-14 18:41                               ` Aymeric Vitte
2021-03-17  4:19                                 ` ZmnSCPxj
2021-03-17  5:46                                   ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-17  7:14                                     ` Eric Voskuil [this message]
2021-03-02 11:56           ` Chris Belcher
2021-03-03 11:22             ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-16  2:11               ` ZmnSCPxj
2021-03-16 11:39                 ` DA Williamson
2021-03-17  4:11                   ` ZmnSCPxj
2021-03-17  8:13                     ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-17  9:32                       ` ZmnSCPxj
2021-03-18  1:10                         ` DA Williamson
2021-03-03  2:54           ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-03 11:55             ` eric
2021-03-04  4:53               ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-03 14:32             ` Thomas Hartman
2021-03-04  5:05               ` LORD HIS EXCELLENCY JAMES HRMH
     [not found] <SL2P216MB008922741210CC853A51A5A19D979@SL2P216MB0089.KORP216.PROD.OUTLOOK.COM>
2021-03-04  7:46 ` Eric Voskuil

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=EA543368-EDE2-4407-99C4-22387F930184@voskuil.org \
    --to=eric@voskuil.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=willtech@live.com.au \
    /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