From: Eric Voskuil <eric@voskuil•org>
To: Zac Greenwood <zachgrw@gmail•com>
Cc: Prayank <prayank@tutanota•de>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Trinary Version Signaling for softfork
Date: Wed, 30 Jun 2021 11:11:06 -0700 [thread overview]
Message-ID: <45EF3F33-E707-4EE7-B02A-AD8A93474B92@voskuil.org> (raw)
In-Reply-To: <CAJ4-pEA=aMEkvLRSHjaHYRf=YBqKuZjdSnim=GTOCfLOUm+o1Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2451 bytes --]
> On Jun 30, 2021, at 05:45, Zac Greenwood <zachgrw@gmail•com> wrote:
>
>
> Eric,
>
> > A million nodes saying a transaction is invalid does nothing to enforce that knowledge
>
> It does. Nodes disregard invalid transactions and invalid blocks as if they never existed. It is not possible for any party to transact bitcoin in a way that violates the set of rules enforced by the network of consensus-compatible nodes that we call Bitcoin.
When Fincen walks into Coinbase and every other exchange (and white market business in the country), and tells them to change a rule or they are taking the CEO out in hancuffs for money laundering, I’m pretty sure that their node with not be able to prevent it.
Enforcement is always people. We use the term node as a metaphorical term for people who use the node to avoid taking bad money. Like those machines that test paper money, they offer no resistance themselves.
A node in a closet checking transactions, unconnected to any human actually rejecting the money in trade, offers no resistance to anything. It can be forked off without any consequence whatsoever.
This subject was discussed here during the BCH split. People were setting up nodes on cloud services, to boost numbers. These non-economic nodes were of course of no consequence, which was not a matter of debate. I’m explaining to you why that is.
The network ignores non-economic nodes as if they never existed.
> Zac
>
>
>> On Wed, Jun 30, 2021 at 2:03 PM Eric Voskuil <eric@voskuil•org> wrote:
>> A million nodes saying a transaction is invalid does nothing to enforce that knowledge.
>>
>> An economic node is a person who refuses to accept invalid money. A node only informs this decision, it cannot enforce it. That’s up to people.
>>
>> And clearly if one is not actually accepting bitcoin for anything at the time, he is not enforcing anything.
>>
>> The idea of a non-economic node is well established, nothing new here.
>>
>> e
>>
>>>> On Jun 30, 2021, at 04:33, Zac Greenwood <zachgrw@gmail•com> wrote:
>>>>
>>>
>>> Hi Eric,
>>>
>>> > A node (software) doesn’t enforce anything. Merchants enforce consensus rules
>>>
>>> … by running a node which they believe to enforce the rules of Bitcoin.
>>>
>>> A node definitely enforces consensus rules and defines what is Bitcoin. I am quite disturbed that this is even being debated here.
>>>
>>> Zac
[-- Attachment #2: Type: text/html, Size: 4452 bytes --]
next prev parent reply other threads:[~2021-06-30 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 12:01 Prayank
2021-06-30 9:17 ` eric
2021-06-30 11:33 ` Zac Greenwood
2021-06-30 12:03 ` Eric Voskuil
2021-06-30 12:44 ` Zac Greenwood
2021-06-30 18:11 ` Eric Voskuil [this message]
2021-06-30 12:12 ` Prayank
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=45EF3F33-E707-4EE7-B02A-AD8A93474B92@voskuil.org \
--to=eric@voskuil$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=prayank@tutanota$(echo .)de \
--cc=zachgrw@gmail$(echo .)com \
/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