From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YrVgl-0008IK-Q6 for bitcoin-development@lists.sourceforge.net; Sun, 10 May 2015 18:10:55 +0000 X-ACL-Warn: Received: from mail-ig0-f173.google.com ([209.85.213.173]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YrVgi-00044q-Oc for bitcoin-development@lists.sourceforge.net; Sun, 10 May 2015 18:10:55 +0000 Received: by iget9 with SMTP id t9so59686269ige.1 for ; Sun, 10 May 2015 11:10:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=TLsV8m2P0wovMIzvgXbdOYdTmDMDwfc63aTZ0Tv0qos=; b=TlIT3IrkR0NXHb40MLmd5Bz64c3KOpp7fIIb6mwpx1MZodnmzxCru2k+vth0mGIlzv t+W6kCLoXu6yGpUy01AtiDHojEl0YUxaGdSNcLCH0AgRW96/VoBsryGRGGRU3ItA2Z2h NQELK/xnFWJfjWrc79rwGW8QiCOV1lzkRInoZ5bsyIony0VE9qiOJQ6nx2pCVrSFbpJq SFifCB4By7MVn5Q07T2O82nMOtYCxt455nkGVV95Bgl+HHADxlOJPCorNJOiV9/DxV9h rQxHgmZC0X/NEOMewMeycMYgdriwlIXkPqWhCjQSgB/z9EscLrQ3IDVeL439x5zl3w/b qFHA== X-Gm-Message-State: ALoCoQmr+OmAdHk+CJA+WTCCyGAqjOQF/vYTdd1O/Vrbdl+fU0EiDRmPMW7/kUSjGZhT22vZndkZ MIME-Version: 1.0 X-Received: by 10.50.143.38 with SMTP id sb6mr8927453igb.44.1431281447368; Sun, 10 May 2015 11:10:47 -0700 (PDT) Received: by 10.107.25.203 with HTTP; Sun, 10 May 2015 11:10:47 -0700 (PDT) X-Originating-IP: [208.54.4.197] Received: by 10.107.25.203 with HTTP; Sun, 10 May 2015 11:10:47 -0700 (PDT) In-Reply-To: <554F9720.4040105@phauna.org> References: <16096345.A1MpJQQkRW@crushinator> <554F9720.4040105@phauna.org> Date: Sun, 10 May 2015 11:10:47 -0700 Message-ID: From: Mark Friedenbach To: Owen Gunden Content-Type: multipart/alternative; boundary=001a1135ffb83e92f10515be2e14 X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1YrVgi-00044q-Oc Cc: Bitcoin Development Subject: Re: [Bitcoin-development] Proposed alternatives to the 20MB step function X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 May 2015 18:10:55 -0000 --001a1135ffb83e92f10515be2e14 Content-Type: text/plain; charset=UTF-8 Micropayment channels are not pie in the sky proposals. They work today on Bitcoin as it is deployed without any changes. People just need to start using them. On May 10, 2015 11:03, "Owen Gunden" wrote: > On 05/08/2015 11:36 PM, Gregory Maxwell wrote: > > Another related point which has been tendered before but seems to have > > been ignored is that changing how the size limit is computed can help > > better align incentives and thus reduce risk. E.g. a major cost to the > > network is the UTXO impact of transactions, but since the limit is blind > > to UTXO impact a miner would gain less income if substantially factoring > > UTXO impact into its fee calculations; and without fee impact users have > > little reason to optimize their UTXO behavior. > > Along the lines of aligning incentives with a diversity of costs to a > variety of network participants, I am curious about reactions to Justus' > general approach: > > > http://bitcoinism.liberty.me/2015/02/09/economic-fallacies-and-the-block-size-limit-part-2-price-discovery/ > > I realize it relies on pie-in-the-sky ideas like micropayment channels, > but I wonder if it's a worthy long-term ideal direction for this stuff. > > > ------------------------------------------------------------------------------ > 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 > --001a1135ffb83e92f10515be2e14 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Micropayment channels are not pie in the sky proposals. They= work today on Bitcoin as it is deployed without any changes. People just n= eed to start using them.

On May 10, 2015 11:03, "Owen Gunden" &= lt;ogunden@phauna.org> wrote:<= br type=3D"attribution">
On 05/08/2015 11:36 = PM, Gregory Maxwell wrote:
> Another related point which has been tendered before but seems to have=
> been ignored is that changing how the size limit is computed can help<= br> > better align incentives and thus reduce risk.=C2=A0 E.g. a major cost = to the
> network is the UTXO impact of transactions, but since the limit is bli= nd
> to UTXO impact a miner would gain less income if substantially factori= ng
> UTXO impact into its fee calculations; and without fee impact users ha= ve
> little reason to optimize their UTXO behavior.

Along the lines of aligning incentives with a diversity of costs to a
variety of network participants, I am curious about reactions to Justus'= ;
general approach:

http://bitco= inism.liberty.me/2015/02/09/economic-fallacies-and-the-block-size-limit-par= t-2-price-discovery/

I realize it relies on pie-in-the-sky ideas like micropayment channels,
but I wonder if it's a worthy long-term ideal direction for this stuff.=

---------------------------------------------------------------------------= ---
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-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment
--001a1135ffb83e92f10515be2e14--