public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Alex Morcos <morcos@gmail•com>
To: Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>,
	 Daniele Pinna <daniele.pinna@gmail•com>,
	Mark@friedenbach•org
Subject: Re: [bitcoin-dev] Rebatable fees & incentive-safe fee markets
Date: Fri, 29 Sep 2017 12:50:20 +0000	[thread overview]
Message-ID: <CAPWm=eUCQo+1+2SWjpWG1kcidcLcugwTvVbug6WNmZBRVm_ebg@mail.gmail.com> (raw)
In-Reply-To: <CAEgR2PGrf+4pQRyNC_xKVEKXimKTWveGK9q6YJeZkG0_r=8tkg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

I had the same concern, or a miner could fill the remainder of the block
with their own high fee paying transactions if blocks were required to be
full.

On Fri, Sep 29, 2017 at 7:55 AM Daniele Pinna via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:

> Maybe I'm getting this wrong but wouldn't this scheme imply that a miner
> is incentivized to limit the amount of transactions in a block to capture
> the maximum fee of the ones included?
>
> 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.
>
> Am I missing something?
>
> Daniele
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 1729 bytes --]

  reply	other threads:[~2017-09-29 12:50 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 [this message]
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
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='CAPWm=eUCQo+1+2SWjpWG1kcidcLcugwTvVbug6WNmZBRVm_ebg@mail.gmail.com' \
    --to=morcos@gmail$(echo .)com \
    --cc=Mark@friedenbach$(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