public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Zac Greenwood <zachgrw@gmail.com>
To: Eric Voskuil <eric@voskuil.org>
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 14:44:49 +0200	[thread overview]
Message-ID: <CAJ4-pEA=aMEkvLRSHjaHYRf=YBqKuZjdSnim=GTOCfLOUm+o1Q@mail.gmail.com> (raw)
In-Reply-To: <C3B41B70-E137-4910-A3BA-ED1464733E8D@voskuil.org>

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

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.

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: 2907 bytes --]

  reply	other threads:[~2021-06-30 12:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27 12:01 [bitcoin-dev] Trinary Version Signaling for softfork 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 [this message]
2021-06-30 18:11         ` Eric Voskuil
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='CAJ4-pEA=aMEkvLRSHjaHYRf=YBqKuZjdSnim=GTOCfLOUm+o1Q@mail.gmail.com' \
    --to=zachgrw@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=eric@voskuil.org \
    --cc=prayank@tutanota.de \
    /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