public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pedro Worcel <pedro@worcel.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Long-term mining incentives
Date: Wed, 13 May 2015 09:24:41 +1200	[thread overview]
Message-ID: <CAPS+U98sh6BmuGHWOffrmTpaM3CNfhBUWdmgACb9++jU6M1fmQ@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T3AxM3et7hgXx3+Rn3BvhQkF-Cn797sHcyztkMpD1UQmA@mail.gmail.com>

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

Disclaimer: I don't know anything about Bitcoin.

> ​2) Proof-of-idle supported (I wish Tadge Dryja would publish his
proof-of-idle idea....)
> 3) Fees purely as transaction-spam-prevention measure, chain security via
alternative consensus algorithm (in this scenario there is very little
mining).

I don't understand why you would casually mention moving away from Proof of
Work, I thought that was the big breakthrough that made Bitcoin possible at
all?

Thanks,
Pedro

2015-05-13 4:10 GMT+12:00 Gavin Andresen <gavinandresen@gmail.com>:

> Added back the list, I didn't mean to reply privately:
>
> Fair enough, I'll try to find time in the next month or three to write up
> four plausible future scenarios for how mining incentives might work:
>
> 1) Fee-supported with very large blocks containing lots of tiny-fee
> transactions
> ​​
> 2) Proof-of-idle supported (I wish Tadge Dryja would publish his
> proof-of-idle idea....)
> 3) Fees purely as transaction-spam-prevention measure, chain security via
> alternative consensus algorithm (in this scenario there is very little
> mining).
> 4) Fee supported with small blocks containing high-fee transactions moving
> coins to/from sidechains.
>
> Would that be helpful, or do you have some reason for thinking that we
> should pick just one and focus all of our efforts on making that one
> scenario happen?
>
> I always think it is better, when possible, not to "bet on one horse."
>
>
> On Tue, May 12, 2015 at 10:39 AM, Thomas Voegtlin <thomasv@electrum.org>
> wrote:
>
>> Le 12/05/2015 15:44, Gavin Andresen a écrit :
>> > Ok, here's my scenario:
>> >
>> > https://blog.bitcoinfoundation.org/a-scalability-roadmap/
>> >
>> > It might be wrong. I welcome other people to present their road maps.
>> >
>>
>> [answering to you only because you answered to me and not to the list;
>> feel free to repost this to the list though]
>>
>> Yes, that's exactly the kind of roadmap I am asking for. But your blog
>> post does not say anything about long term mining incentives, it only
>> talks about scalability. My point is that we need the same kind of thing
>> for miners incentives.
>>
>
>
>
> --
> --
> Gavin Andresen
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

[-- Attachment #2: Type: text/html, Size: 4543 bytes --]

  parent reply	other threads:[~2015-05-12 21:53 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 16:28 [Bitcoin-development] Long-term mining incentives Thomas Voegtlin
2015-05-11 16:52 ` insecurity
2015-05-11 17:29   ` Gavin Andresen
2015-05-12 12:35     ` Thomas Voegtlin
     [not found]       ` <CABsx9T1h7p3hDr7ty43uxsYs-oNRpndzg=dowST2tXtogxRm2g@mail.gmail.com>
     [not found]         ` <555210AF.3090705@electrum.org>
2015-05-12 16:10           ` Gavin Andresen
2015-05-12 16:21             ` Dave Hudson
2015-05-12 21:24             ` Pedro Worcel [this message]
2015-05-12 23:48               ` Adam Back
2015-05-13 15:41                 ` Gavin Andresen
2015-05-13 20:05                   ` Pedro Worcel
2015-05-13  9:49             ` Thomas Voegtlin
2015-05-13 10:14               ` Tier Nolan
2015-05-13 10:31                 ` Alex Mizrahi
2015-05-13 11:29                   ` Tier Nolan
2015-05-13 12:26                     ` Alex Mizrahi
2015-05-13 13:24                       ` Gavin
2015-05-13 13:28                       ` Tier Nolan
2015-05-13 14:26                         ` Alex Mizrahi
2015-05-13 23:46                   ` Jorge Timón
2015-05-14  0:11     ` Jorge Timón
2015-05-14  0:48       ` Aaron Voisine
2015-05-14  0:58         ` Pieter Wuille
2015-05-14  1:13           ` Aaron Voisine
2015-05-14  1:19             ` Pieter Wuille
2015-05-14  1:31               ` Aaron Voisine
2015-05-14  2:34                 ` Aaron Voisine
2015-05-16 20:35                 ` Owen Gunden
2015-05-16 22:18                   ` Tom Harding
2015-05-17  1:08                   ` Aaron Voisine
2015-05-14  0:44 ` Melvin Carvalho
2015-05-25 18:31 ` Mike Hearn
2015-05-26 18:47   ` Thomas Voegtlin
2015-05-27 21:59   ` Mike Hearn
2015-05-27 22:22     ` Gregory Maxwell
2015-05-28 10:30       ` Mike Hearn
2015-05-13 17:49 Damian Gomez
2015-05-18  2:29 Michael Jensen

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=CAPS+U98sh6BmuGHWOffrmTpaM3CNfhBUWdmgACb9++jU6M1fmQ@mail.gmail.com \
    --to=pedro@worcel.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gavinandresen@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