From: Ivan Brightly <ibrightly@gmail•com>
To: "Jorge Timón" <jtimon@jtimon•cc>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] The need for larger blocks
Date: Sun, 28 Jun 2015 12:01:31 -0400 [thread overview]
Message-ID: <CAAre=yQvp68CaWmGfBGhehxAdz2HJGYU0nuxrn+wskyRYFfcSQ@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDo8ZmEO5SHwZVLX0Ajg3vUu2OoJkz2urA61wAoVm_f+zA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
I don't think that rights are a pillar of how bitcoin works - rather I
would say it's a matter of aligned incentives. The fact is that the
majority technically *can* dictate through PoW and acceptance. The only
reason that the majority would not chose this path is because there is
greater economic value in consensus, whether perceived or realized.
If bitcoin were about "doing the right thing" there wouldn't be a need for
PoW since no individual would be incentivized to double spend.
On Sun, Jun 28, 2015 at 11:05 AM, Jorge Timón <jtimon@jtimon•cc> wrote:
> On Sun, Jun 28, 2015 at 3:51 PM, Ivan Brightly <ibrightly@gmail•com>
> wrote:
> > On Sun, Jun 28, 2015 at 8:13 AM, Jorge Timón <jtimon@jtimon•cc> wrote:
> >>
> >>
> >> No, this is very important. The majority has no right to dictate on
> >> the minority.
> >
> >
> > While an interesting philosophical question, I don't think that this is
> > accurate. First off, bitcoin doesn't imbue any 'rights' on individuals
> - it
> > provides the choice of participating or not, nothing more.
>
> I think you're not contradicting me: ff there's not rights built into
> the system, the majority has no "right to dictate" anything.
>
[-- Attachment #2: Type: text/html, Size: 1695 bytes --]
next prev parent reply other threads:[~2015-06-28 16:01 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 14:09 Pieter Wuille
2015-06-26 14:38 ` Venzen Khaosan
2015-06-26 15:22 ` Milly Bitcoin
2015-06-26 15:24 ` Pieter Wuille
2015-06-26 18:05 ` Jeff Garzik
2015-06-26 18:32 ` Milly Bitcoin
2015-06-26 15:38 ` Tom Harding
2015-06-26 16:22 ` Venzen Khaosan
2015-06-26 17:04 ` Tom Harding
2015-06-26 17:55 ` Gavin Andresen
2015-06-26 17:57 ` Jeff Garzik
2015-06-26 18:12 ` Pieter Wuille
2015-06-26 18:23 ` Jeff Garzik
2015-06-26 18:31 ` Mark Friedenbach
2015-06-26 19:05 ` Aaron Voisine
2015-06-26 18:34 ` Pieter Wuille
2015-06-26 19:18 ` Ross Nicoll
2015-06-26 19:36 ` Peter Todd
2015-06-27 6:13 ` Filipe Farinha
2015-06-27 7:14 ` Aaron Voisine
2015-06-27 15:13 ` Peter Todd
2015-06-27 19:40 ` Aaron Voisine
2015-06-26 18:47 ` Patrick Strateman
2015-06-26 19:03 ` Tier Nolan
2015-06-26 19:12 ` Mark Friedenbach
2015-06-26 20:44 ` Owen Gunden
2015-06-27 2:18 ` Eric Lombrozo
2015-06-27 2:54 ` Eric Lombrozo
2015-06-27 8:16 ` Venzen Khaosan
2015-06-26 18:29 ` Alex Morcos
2015-06-27 7:43 ` Wladimir J. van der Laan
2015-06-27 9:55 ` NxtChg
2015-06-27 10:04 ` Wladimir J. van der Laan
2015-06-27 10:29 ` NxtChg
2015-06-27 11:04 ` Jorge Timón
2015-06-27 11:18 ` Eric Lombrozo
2015-06-27 11:43 ` Jorge Timón
2015-06-27 12:10 ` NxtChg
2015-06-28 12:13 ` Jorge Timón
2015-06-28 13:51 ` Ivan Brightly
2015-06-28 14:13 ` Eric Lombrozo
2015-06-28 14:16 ` Eric Lombrozo
2015-06-28 14:22 ` Ivan Brightly
2015-06-28 15:05 ` Jorge Timón
2015-06-28 16:01 ` Ivan Brightly [this message]
2015-06-28 15:28 ` s7r
2015-06-28 15:45 ` Jorge Timón
2015-06-27 10:19 ` Venzen Khaosan
2015-06-27 19:55 ` Aaron Voisine
2015-06-28 16:37 ` Venzen Khaosan
2015-06-28 20:56 ` Aaron Voisine
2015-06-27 10:13 ` Jorge Timón
2015-06-27 12:09 ` Wladimir J. van der Laan
2015-06-27 12:15 ` NxtChg
2015-06-27 12:17 ` Greg Sanders
2015-06-27 12:25 ` NxtChg
2015-06-27 12:35 ` Greg Sanders
2015-06-27 12:25 ` Wladimir J. van der Laan
2015-06-27 12:50 ` NxtChg
2015-06-27 13:01 ` Wladimir J. van der Laan
2015-06-28 12:03 ` Jorge Timón
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='CAAre=yQvp68CaWmGfBGhehxAdz2HJGYU0nuxrn+wskyRYFfcSQ@mail.gmail.com' \
--to=ibrightly@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jtimon@jtimon$(echo .)cc \
/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