public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Hector Chu <hectorchu@gmail.com>
To: Adam Back <adam@cypherspace.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] "A Transaction Fee Market Exists Without a Block Size Limit"--new research paper suggests
Date: Wed, 5 Aug 2015 20:04:35 +0100	[thread overview]
Message-ID: <CAAO2FKH7YO0WVf17_tH8dhZJ7Rt2-sHO40hx9afVjobY1i4i+A@mail.gmail.com> (raw)
In-Reply-To: <CAAO2FKGwf0yNFT1VaSVQ7B88YRnSaGONrCrTxuVoe4d0ryw5mA@mail.gmail.com>

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

To put some flesh on the bones of this idea, imagine a hypothetical
security named BLK. Demand for bigger blocks should buy up BLK and demand
for smaller blocks should short BLK. The price of BLK in BTC is the ideal
block size.
Now imagine that there are futures contracts for the security BLK. On the
settlement date of those futures the current BLK/BTC price of those futures
is taken to be the new Bitcoin block size for the next 3 months.
For instance, if I predict or want the block size to be higher on September
than it currently is, I would buy up September BLK futures. My actions
would nudge the price up, and if come September I am right I get what I
want and have a floating profit on the futures market.
The nice thing about a futures market is that it allows capacity planning
for the months ahead. Also there is no need for an underlying BLK security
for a futures market in BLKs to exist.
If the market is efficient and correctly sets the block size, BTC/USD will
rise and the BTC profits of the market participants will go up in USD terms
as a result.

On 5 August 2015 at 12:35, Hector Chu <hectorchu@gmail.com> wrote:

> On 5 August 2015 at 12:07, Adam Back <adam@cypherspace.org> wrote:
>
>> This prediction market in block-size seems like something extremely
>> complex to operate and keep secure in a decentralised fashion.
>
>
> Why would it need to be decentralised? Bitcoin.org could run the exchange,
> and the profits from the exchange could be used to fund Core development.
>
> We also have no particular reason to suppose other than
>> meta-incentive, that it should result in a secure parameter set.
>>
>
> Security is a continuous variable, trading off against others. If security
> gradually begins to be threatened as a result of block size gradually
> increasing, the concerns of users will be enough that the bears will gain
> control over the bulls on the block size market.
>
> I suspect that, while it is interesting in the abstract, it risks
>> converting a complex security problem into an even more complex one,
>> rather than constituting an incremental security improvement which is
>> more the context of day to day discussions here.
>
>
> Hard problems call for complex solutions.
>

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

  reply	other threads:[~2015-08-05 19:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 15:22 [bitcoin-dev] Eli Dourado on "governance" Gavin Andresen
     [not found] ` <1438640036.2828.0.camel@auspira.com>
2015-08-03 22:21   ` Gavin Andresen
2015-08-04  6:40     ` [bitcoin-dev] "A Transaction Fee Market Exists Without a Block Size Limit"--new research paper suggests Peter R
2015-08-04 18:41       ` Dave Hudson
2015-08-04 21:18         ` Peter Todd
2015-08-04 21:30         ` Gavin Andresen
2015-08-04 21:46           ` Peter Todd
2015-08-05  0:26             ` Milly Bitcoin
2015-08-05  0:40               ` Neil Fincham
2015-08-04 23:37           ` Dave Hudson
2015-08-05 22:15         ` Peter R
2015-08-05 22:44           ` Dave Hudson
2015-08-05 23:45             ` Tom Harding
2015-08-05  8:33       ` Benjamin
2015-08-05  9:18         ` Hector Chu
2015-08-05  9:57           ` Adam Back
2015-08-05 10:51             ` Hector Chu
2015-08-05 11:07               ` Adam Back
2015-08-05 11:35                 ` Hector Chu
2015-08-05 19:04                   ` Hector Chu [this message]
2015-08-05 10:26         ` Peter R
     [not found]       ` <CAAS2fgTzeFnmnr2ScZvf1pDUtF+M3HhF9xo0yhjVPObpqhgz0A@mail.gmail.com>
     [not found]         ` <6ED57388-6EC3-4515-BF3F-E753301537AB@gmx.com>
     [not found]           ` <CAAS2fgRoFna4i-d=hpmz-CpV35VQ=J1aEoTTT6B1oD4f15C1KA@mail.gmail.com>
     [not found]             ` <C8B38FEC-0EF2-483F-9E53-43AB937455A0@gmx.com>
     [not found]               ` <CAAS2fgQjXNTi9Y_YwLg2dR8baYZhvmEjw43ictt749zR2AOEWw@mail.gmail.com>
     [not found]                 ` <6FED5604-4A6F-4CE1-B42E-36626375D557@gmx.com>
     [not found]                   ` <CAAS2fgQ7hRRvRtD8igcZ2aWBmnqre6iM27peCFGxgC8ODb9jgw@mail.gmail.com>
     [not found]                     ` <6BA86443-7534-4AAA-92BC-EC9B1603DE5F@gmx.com>
     [not found]                       ` <CAAS2fgTTZKD9LQHpMmEH0OU=T8Ta7cCaavWzhM1yQ68-MAT8UQ@mail.gmail.com>
     [not found]                         ` <27B16AB4-0DAD-4665-BF08-7A0C0A70D8D8@gmx.com>
     [not found]                           ` <CAAS2fgRm_CSmWgr7CGmBUD0nX+V0fJ8N4TQN01Vchgip9-s6uQ@mail.gmail.com>
     [not found]                             ` <CAAS2fgT+DP+DaoCMG276uF4=Yoi-w40YyNP-RDRG7NQgOmtpGw@mail.gmail.com>
     [not found]                               ` <CAEgR2PGn_SER18sMuKPJJz5RT=1K=346eCm ph5FJQhhoLcV1zw@mail.gmail.com>
     [not found]                                 ` <CAEgR2PGn_SER18sMuKPJJz5RT=1K=346eCmph5FJQhhoLcV1zw@mail.gmail.com>
2015-08-30 20:08                                   ` Peter R
2015-08-30 21:02                                     ` Daniele Pinna
2015-08-04 14:22 ` [bitcoin-dev] Eli Dourado on "governance" Anthony Towns
2015-08-04 18:28   ` Owen
2015-08-05  3:07     ` Eric Lombrozo
2015-08-05  6:32       ` Mashuri Clark
2015-08-05 13:28       ` Mashuri Clark
2015-08-07 16:26 ` Thomas Zander

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=CAAO2FKH7YO0WVf17_tH8dhZJ7Rt2-sHO40hx9afVjobY1i4i+A@mail.gmail.com \
    --to=hectorchu@gmail.com \
    --cc=adam@cypherspace.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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