From: Mike Hearn <mike@plan99.net>
To: Odinn Cyberguerrilla <odinn.cyberguerrilla@riseup.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fee drop
Date: Tue, 25 Feb 2014 18:25:18 +0530 [thread overview]
Message-ID: <CANEZrP1wB9zpnD+DOnmCNycEGB+nZMt8gQrjpn5V92MMkausaA@mail.gmail.com> (raw)
In-Reply-To: <f35865264f37315d580a30dc49789a5a.squirrel@fulvetta.riseup.net>
[-- Attachment #1: Type: text/plain, Size: 254 bytes --]
Given that the fee drop puts fees in "real" (i.e. dollar) terms back to
where they were some months ago, it seems odd to claim this is creating
vulnerabilities that didn't exist in the previous version. The cost of an
attack would be the same as before.
[-- Attachment #2: Type: text/html, Size: 290 bytes --]
next prev parent reply other threads:[~2014-02-25 12:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 4:41 [Bitcoin-development] Fee drop Peter Todd
2014-02-25 7:34 ` naman naman
2014-02-25 12:40 ` Odinn Cyberguerrilla
2014-02-25 12:55 ` Mike Hearn [this message]
2014-02-25 14:49 ` Peter Todd
2014-02-25 16:55 ` Mike Hearn
2014-02-25 17:13 ` Peter Todd
2014-02-25 18:09 ` Jeremy Spilman
2014-02-28 11:18 ` Peter Todd
2014-02-25 22:43 ` Odinn Cyberguerrilla
2014-02-26 22:51 ` Jeff Garzik
2014-02-28 4:50 ` Troy Benjegerdes
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=CANEZrP1wB9zpnD+DOnmCNycEGB+nZMt8gQrjpn5V92MMkausaA@mail.gmail.com \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=odinn.cyberguerrilla@riseup.net \
/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