From: Gregory Maxwell <greg@xiph•org>
To: "Jorge Timón" <jtimon@jtimon•cc>,
"Bitcoin Protocol Discussion"
<bitcoin-dev@lists•linuxfoundation.org>
Cc: Daniele Pinna <daniele.pinna@gmail•com>
Subject: Re: [bitcoin-dev] Rebatable fees & incentive-safe fee markets
Date: Sat, 30 Sep 2017 08:54:57 +0000 [thread overview]
Message-ID: <CAAS2fgQR48pLBPh7=yntE8iXcQSeQU22nptze76DjAUJ9A1KSQ@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDqmOXGZ_qxyNjFYg8qTRu4Tmo7V+zYZCt0j5RekUNVkWw@mail.gmail.com>
On Sat, Sep 30, 2017 at 3:55 AM, Jorge Timón via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> Gmaxwell I think what's new is that in this case, with a single tx you would
> take out all txs with fee below 1 btc. With current rules, you would only
> remove enoguh txs for that one to fit, not empty the whole block and mine
> only a block with that single tx.
I think this is not relevant: By paying the same amount you can delay
the same transactions today.
The difference is that your 'attack' wastes less capacity-- it can be
a simple 150 weight txn rather than a collection that add up to almost
4 million weight; but it costs exactly the same. To the extent that
this difference matters at all, I think it's an improvement.
The only argument that I see for it not being one is that it's easier
to do accidentally. But part of the purpose of this alternative
market is to achieve an equilibrium other than the ultrabloating one;
so yes, you're going to find outcomes where the blocks are not
maximally full.
I wonder how the economics would respond if there is a PI controller
on the maximum size, so that 'lost space' in single blocks with bogon
fee transactions could be recovered if doing so didn't change the
medium timescale total. I think the paper's analysis assumes there is
no limit, but that is impractical for technical reasons (e.g. making
it impossible to budget communications and storage capacity for
nodes...).
next prev parent reply other threads:[~2017-09-30 8:54 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 [this message]
2017-09-30 0:47 ` Gregory Maxwell
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='CAAS2fgQR48pLBPh7=yntE8iXcQSeQU22nptze76DjAUJ9A1KSQ@mail.gmail.com' \
--to=greg@xiph$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=daniele.pinna@gmail$(echo .)com \
--cc=jtimon@jtimon$(echo .)cc \
/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