public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Venzen Khaosan <venzen@mail.bihthai.net>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] A Proposed Compromise to the Block Size Limit
Date: Sun, 28 Jun 2015 00:58:59 +0700	[thread overview]
Message-ID: <558EE463.4020601@mail.bihthai.net> (raw)
In-Reply-To: <20150627175428.GA2259@muck>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Very interesting point and comparison. So the fee market is unknown,
similar to a market maker's orderbook - except in the case of Bitcoin
it is not being deliberately hidden from users, its just not knowable
how miners are positioning at any given moment.


On 06/28/2015 12:54 AM, Peter Todd wrote:
> On Sat, Jun 27, 2015 at 07:46:55PM +0200, Benjamin wrote:
>> There is no ensured Quality of service, is there? If you "bid"
>> higher, then you don't know what you are going to get. Also
>> because you have no way of knowing what *others* are bidding.
>> Only if you have auctions (increasing increments) you can
>> establish a feedback loop to settle demand and supply. And the
>> supply side doesn't adapt. Adapting supply would help resolve
>> parts of the capacity problem.
> 
> There's lots of markets where there is no assured quality of
> service, and where the bids others are making aren't known. Most
> financial markets work that way - there's only ever probabalistic
> guarantees that for a given amount of money you'll be able to buy a
> certain amount of gold at any given time for instance. Similarly
> for nearly all commodities the infrastructure required to mine
> those commodities has very little room for short, medium, or even
> long-term production increases, so whatever the production supply
> is at a given time is pretty much fixed.
> 
> 
> 
> _______________________________________________ bitcoin-dev mailing
> list bitcoin-dev@lists.linuxfoundation.org 
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVjuRiAAoJEGwAhlQc8H1mjnwIAIiUSPf6agfMXsFgupoihsTV
Pr1mJWHdLjrF5QadmdyooivYGPkY+zmfJ+N3fkr8l++PDGh03u0RgALf/gwJSSAQ
qSeMmjSZb8ZEkyLlZAGVHT8Ph+lRda65CVxYspKu/54TolqEezOHVaon9uWYVjtB
cSd8fWoqJMq05Pz25QPagxFUpXmtFX1KvxUWqeGkRsuqMgeWbCurQKpOhRXu48nH
Si73iOIyDUT9i1WsPvlpOi0pSxDlGnkMQKaEyIN5JJfKo1imRAtKVRLZh43rXpSW
jeZf8LMRwd49K4vnvHXZ0UbKWhpelh6XJari22citZ7yb5w5iENAcoP/cSGhLaY=
=nfF5
-----END PGP SIGNATURE-----


  reply	other threads:[~2015-06-27 17:59 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-27 14:39 [bitcoin-dev] A Proposed Compromise to the Block Size Limit Michael Naber
2015-06-27 15:21 ` Peter Todd
2015-06-27 15:29   ` Randi Joseph
2015-06-27 15:32     ` Peter Todd
2015-06-27 16:19   ` Michael Naber
2015-06-27 17:20     ` Peter Todd
2015-06-27 17:26       ` Benjamin
2015-06-27 17:37         ` Peter Todd
2015-06-27 17:46           ` Benjamin
2015-06-27 17:54             ` Peter Todd
2015-06-27 17:58               ` Venzen Khaosan [this message]
2015-06-27 19:34               ` Benjamin
2015-06-27 15:33 ` Adam Back
2015-06-27 16:09   ` Michael Naber
2015-06-27 16:28     ` Mark Friedenbach
2015-06-27 16:37     ` Peter Todd
2015-06-27 17:25       ` Michael Naber
2015-06-27 17:34         ` Peter Todd
2015-06-27 18:02           ` Jameson Lopp
2015-06-27 18:47             ` Peter Todd
2015-06-28  5:34 Raystonn
2015-06-28 10:07 ` Adam Back
2015-06-28 10:29   ` Benjamin
2015-06-28 12:37     ` Adam Back
2015-06-28 16:32       ` Raystonn .
2015-06-28 17:12         ` Mark Friedenbach
2015-06-28 17:18           ` Benjamin
2015-06-28 17:29           ` Gavin Andresen
2015-06-28 17:45             ` Mark Friedenbach
2015-06-28 17:51             ` Adam Back
2015-06-28 18:58               ` Adam Back
2015-06-28 21:05                 ` Gavin Andresen
2015-06-28 21:23                   ` Michael Naber
2015-06-28 22:07                   ` Adam Back
2015-06-29  0:59                     ` Eric Lombrozo
2015-06-29  1:13                     ` Eric Lombrozo
2015-06-29  1:45                     ` Andy Schroder
2015-06-30  0:42                     ` Tom Harding
2015-07-10  2:55                 ` Tom Harding
2015-06-28 17:53             ` Jorge Timón
2015-06-28 19:22             ` Andrew Lapp
2015-06-28 19:40               ` Benjamin
2015-06-28 12:32   ` Milly Bitcoin

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=558EE463.4020601@mail.bihthai.net \
    --to=venzen@mail.bihthai.net \
    --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