From: Drak <drak@zikula.org>
To: "Warren Togami Jr." <wtogami@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] On OP_RETURN in upcoming 0.9 release
Date: Fri, 28 Feb 2014 20:10:32 +0000 [thread overview]
Message-ID: <CANAnSg346s0FqhP+57f1TdnCj3=MVht--qGTCpO+BxOpHA=9Uw@mail.gmail.com> (raw)
In-Reply-To: <CAEz79Po37XkoQ=+kQOTdagVn-vYuqYwotQf58YcgTndaaAmXNw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
On 28 February 2014 14:42, Warren Togami Jr. <wtogami@gmail.com> wrote:
>
> https://github.com/litecoin-project/litecoin/commit/db4d8e21d99551bef4c807aa1534a074e4b7964d
>
> In one way in particular, the transaction fees per kilobyte completely
> failed to account for the actual cost to the network. If Bitcoin had
> adopted a common-sense rule like this, I would have had no reason to join
> Litecoin development last year. This is one of the few economic design
> flaws that Satoshi overlooked in the original design.
>
Is there any particular reason that patch would not make it into bitcoin if
submitted?
Drak
[-- Attachment #2: Type: text/html, Size: 1207 bytes --]
next prev parent reply other threads:[~2014-02-28 20:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 16:03 [Bitcoin-development] On OP_RETURN in upcoming 0.9 release Jeff Garzik
2014-02-24 16:16 ` Pieter Wuille
2014-02-24 16:32 ` Jeff Garzik
2014-02-24 16:33 ` Jeff Garzik
2014-02-24 16:39 ` Wladimir
2014-02-24 16:45 ` Gavin Andresen
2014-02-24 16:50 ` Pavol Rusnak
2014-02-24 17:23 ` Mark Friedenbach
2014-02-24 23:06 ` Andreas Petersson
2014-02-24 23:13 ` Gregory Maxwell
2014-02-24 23:13 ` Luke-Jr
2014-02-28 5:25 ` Troy Benjegerdes
2014-02-28 14:42 ` Warren Togami Jr.
2014-02-28 19:25 ` Mark Friedenbach
2014-02-28 19:36 ` Justus Ranvier
2014-02-28 20:10 ` Drak [this message]
2014-02-24 17:10 ` Jeff Garzik
2014-02-24 22:12 ` Jeremy Spilman
2014-02-24 22:50 ` Jeff Garzik
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='CANAnSg346s0FqhP+57f1TdnCj3=MVht--qGTCpO+BxOpHA=9Uw@mail.gmail.com' \
--to=drak@zikula.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=wtogami@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