From: mm-studios <mm@mm-studios.com>
To: jamtlu@gmail.com, bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Renaming full nodes
Date: Sun, 23 Jan 2022 13:06:36 +0000 [thread overview]
Message-ID: <3iEa2xZax1zTSPKGXJVGwN75k42rkJESv6PuZhgRqDEWBuu4VabN5w1iL3xKP85Wb8sYlhrgM1ZBtkAZKHnEZa6Y2qM30qLd4tEsvF1qGTs=@mm-studios.com> (raw)
In-Reply-To: <CANQHGB0z2v-iK2FdD12dVsoK=grShiX191wnZ16Ai_NX2vahCg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
The problem are.miners, it is pretty.innaccessible to be a miner. That's a major isuue for me.
Block production is pretty much in hands of the wealthy.
Any correlation between be wealthy and run a honest node? Not any under my eyes. Skipping the part of the narrative saying 'they are honest bcs they have skin in the game'. That's not scientific to me.
Block validation yes, the network is pretty decentralized.
Thanks.
Sent from ProtonMail mobile
-------- Original Message --------
On 23 Jan 2022, 02:44, James Lu via bitcoin-dev wrote:
> Much of the confusion around the Bitcoin protocol is the concept that mining nodes 'control' the network.
>
> I suggest renaming full nodes- to something like "validator node" to emphasize that full nodes check if blocks are valid.
>
> Then we could say:
>
> "Bitcoin is decentralized because anyone can run a validator node, even on a low-end laptop."
[-- Attachment #2: Type: text/html, Size: 1837 bytes --]
prev parent reply other threads:[~2022-01-23 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 2:44 [bitcoin-dev] Renaming full nodes James Lu
2022-01-23 13:06 ` mm-studios [this message]
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='3iEa2xZax1zTSPKGXJVGwN75k42rkJESv6PuZhgRqDEWBuu4VabN5w1iL3xKP85Wb8sYlhrgM1ZBtkAZKHnEZa6Y2qM30qLd4tEsvF1qGTs=@mm-studios.com' \
--to=mm@mm-studios.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jamtlu@gmail.com \
/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