From: Aymeric Vitte <vitteaymeric@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Classic 1.2.0 released
Date: Sun, 8 Jan 2017 00:10:50 +0100 [thread overview]
Message-ID: <dd5072fe-be5b-52a6-7171-ed320c851f6f@gmail.com> (raw)
In-Reply-To: <CAAcC9ysNPC1nHumY4giCi7ffVRviNZBNfoLdS0UsghSX8NRcmw@mail.gmail.com>
Le 07/01/2017 à 21:26, Chris Priest via bitcoin-dev a écrit :
> Bitcoin Classic only changes the block format (by changing the rule
> that they have to be 1MB or less). Miners are the only ones who make
> blocks, so they are the only ones who mater when it comes to changing
> block rules.
Certainly not
> Nodes, wallets and other software are not affected by
> changing block rules. Unlike segwit, where *everybody* has to write
> code to support the new transaction format.
This is what we could call a decentralized system, when everybody is
affected
>
> Also, it doesn't matter that 75% of hashpower is made up of a dozen
> people. That's how the system works, it's not a matter of opinion.
That's an obvious weakness of the system
> If
> you are just a node or just a wallet, and you want your voice to
> matter, then you need to get a hold of some hashpower.
Well, probably you did not mean this, this is not fair. "Just a node"...
Still wondering why you guys don't care about the ridiculous number of
full nodes, no incentive to run one and what would happen if someone
were to control a majority of full nodes
--
Zcash wallets made simple: https://github.com/Ayms/zcash-wallets
Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets
Get the torrent dynamic blocklist: http://peersm.com/getblocklist
Check the 10 M passwords list: http://peersm.com/findmyass
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
next prev parent reply other threads:[~2017-01-07 23:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 10:16 Tom Zander
2017-01-07 8:13 ` Jonas Schnelli
2017-01-07 8:55 ` Eric Lombrozo
2017-01-07 15:15 ` Tom Zander
2017-01-07 20:12 ` Chris Priest
2017-01-07 20:17 ` David Vorick
2017-01-07 20:26 ` Chris Priest
2017-01-07 21:14 ` Eric Voskuil
2017-01-07 23:10 ` Aymeric Vitte [this message]
2017-01-07 23:49 ` Eric Voskuil
2017-01-08 0:28 ` Eric Lombrozo
2017-01-08 1:58 ` Chris Priest
2017-01-07 21:15 ` Btc Drak
2017-01-07 23:08 ` Tom Zander
2017-01-08 0:32 ` 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=dd5072fe-be5b-52a6-7171-ed320c851f6f@gmail.com \
--to=vitteaymeric@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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