From: Gregory Maxwell <greg@xiph•org>
To: Daniele Pinna <daniele.pinna@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Rebatable fees & incentive-safe fee markets
Date: Sat, 30 Sep 2017 00:47:54 +0000 [thread overview]
Message-ID: <CAAS2fgRbC46Wii0KOU6B+5v+OBcSp5syN-oWkNByBdZbmwr3Wg@mail.gmail.com> (raw)
In-Reply-To: <CAEgR2PGrf+4pQRyNC_xKVEKXimKTWveGK9q6YJeZkG0_r=8tkg@mail.gmail.com>
On Fri, Sep 29, 2017 at 10:43 AM, Daniele Pinna via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> As an example, mined blocks currently carry ~0.8 btc in fees right now. If I
> were to submit a transaction paying 1 btc in maximal money fees, then the
> miner would be incentivized to include my transaction alone to avoid that
> lower fee paying transactions reduce the amount of fees he can earn from my
> transaction alone. This would mean that I could literally clog the network
> by paying 1btc every ten minutes.
If I'm not mistaken that is is nothing new or interesting: You can
delay some transaction by paying more than it offered by every block
you delay it from. E.g. if the next full block would pay 0.8 BTC in
fees, you just need to make transactions paying more than that. But
you'll pay it for each delay and the people you push out only pay once
(when they are successful), so it gets awfully expensive fast.
(Arguably the monopoly price model is better because outbidding party
doesn't need to bloat the chain to do their thing; arguable its
somewhat worse because its harder to do by accident.)
My thought on this was the same as PT's initial: miners and users can
arrange OOB payments (and/or coinjoin rebates) and bypass this. I
don't see why it wouldn't be in their individual best interest to do
so, and if they do that would likely be a centralizing effect.
next prev parent reply other threads:[~2017-09-30 0:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEgR2PGCZ=F85yjAbZgC6NtzhpdgBL3n4M2jowN12wJ7x-Ai1A@mail.gmail.com>
[not found] ` <CAEgR2PGrxDQE0k8WX4XXz9GN-RAL6JB51ST9Hdz=ba36gRCa6A@mail.gmail.com>
[not found] ` <CAEgR2PFjt=ihzRBhNXbHTAJz1R+3vz8o-zRZkDA3iBo39x9cTQ@mail.gmail.com>
[not found] ` <CAEgR2PFfSjJjkTYq+DAmTzmkHPxqhn6fUDoXTzrRebz+OoUgqw@mail.gmail.com>
[not found] ` <CAEgR2PG5ZueHKDXbsPDEjQG7xAYBa_JAtPZo9n1V2=STC1srpA@mail.gmail.com>
[not found] ` <CAEgR2PGPQ1e9SmoWOS3V+N9v+OWiM4g3nPN3d9urc+DfkWEJ7A@mail.gmail.com>
[not found] ` <CAEgR2PEKkHH6+Sh8cQGF83-s1tpwQZgd0fiuNz_xyWu0mUPfCA@mail.gmail.com>
[not found] ` <CAEgR2PEyWFO1RFohVEpcb-M7aM-8xjCFvDPeJPD4zF4yTCyZ0A@mail.gmail.com>
2017-09-29 10:43 ` Daniele Pinna
2017-09-29 12:50 ` Alex Morcos
2017-09-29 15:22 ` Mark Friedenbach
2017-09-30 3:53 ` Jorge Timón
2017-09-30 3:55 ` Jorge Timón
2017-09-30 8:54 ` Gregory Maxwell
2017-09-30 0:47 ` Gregory Maxwell [this message]
2017-09-29 1:06 Mark Friedenbach
2017-09-29 1:53 ` Matt Corallo
2017-09-29 2:09 ` Nathan Wilcox
2017-09-29 2:10 ` Peter Todd
2017-09-29 2:17 ` Nathan Wilcox
2017-09-29 3:30 ` Mark Friedenbach
2017-09-29 2:02 ` Peter Todd
2017-09-29 2:45 ` Mark Friedenbach
2017-09-29 3:02 ` Peter Todd
2017-09-29 4:45 ` Anthony Towns
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=CAAS2fgRbC46Wii0KOU6B+5v+OBcSp5syN-oWkNByBdZbmwr3Wg@mail.gmail.com \
--to=greg@xiph$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=daniele.pinna@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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