summaryrefslogtreecommitdiff
path: root/81/a8cfe30d2a0a70f8903ec1d72b3bb153afbd55
blob: 4a9779169cf9cc4aa59aa5152a640cadc2c1dd66 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
Return-Path: <morcos@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id E82A340A
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 29 Sep 2017 12:50:32 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-it0-f41.google.com (mail-it0-f41.google.com
	[209.85.214.41])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 73836433
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 29 Sep 2017 12:50:31 +0000 (UTC)
Received: by mail-it0-f41.google.com with SMTP id e134so1929144ite.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 29 Sep 2017 05:50:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:references:in-reply-to:from:date:message-id:subject:to; 
	bh=r+mBWK7utey7l0pMwjk157lZbsu2qHGdPJ90GDPvX+Y=;
	b=LuhLP4vxFhcg9WqeNua6UXB6czyL3KZBsvsXnlxIHfrDTsHBX73Jc4KPCEvvUzQdbe
	B9wtTVDpcDCeArariGK61/BVYdTi+uiJwIbIYEAQHar9nBkGT4LIQiWCoweyC26cDi/N
	KajGpneJDaqzR/oOmSEv8DnPRIDZRGWmSP1q0BzV7+5FhdiC/iKCK5vEdzXej7A2k+lp
	HdVuFZUCI05r/5Tiwc/kmx1JEZ2Q0EKue9BKfwJfciFFjA5BVRa4UQa4a3OyA62ZzNsq
	ygbRV5n0I3h/uwbxoVi1fx5SXmfNgTe+2V2LyZtUdA+WLKZ2XESrz0xjs8g4T57N6IT/
	r3tg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:references:in-reply-to:from:date
	:message-id:subject:to;
	bh=r+mBWK7utey7l0pMwjk157lZbsu2qHGdPJ90GDPvX+Y=;
	b=WZEB1P1DT1sq31vQnOxPXLUSxLyqFqAJIq5YpnQuaNyhLeljBfrXxcXdFo7n6kf8MD
	l50gzSQ1txYTtvgYbzYwwubYO/p0ZQcvBG6AQMr5JAP41q5Q2x+BKrggsu1r/Oj/LjN7
	RcVuFEO1nI53alR7bSgIdGtUVxnA/bMqIcI3ErPklxfDXzFcpqSNtfTbT+/7aN0ZZOoi
	90lv1WW/ORy5QDaDbTIRLS5Gk/xklx0epK1+Ebg2JjEPEyTcgpCte0SJyw6psRimcvqx
	G8NzVk79T1YML41dyvYs2R8N38tu+Xva8SrMmh+Gcxow196u5bXhL/rbZF1/TXkxMN3Y
	1QTw==
X-Gm-Message-State: AMCzsaWu/zO86c4n0f3yMosuoac5A2V4GbMMSYD66zWerWv+YV0yLh0T
	pcXXc2csdNcNjp+yKe++SXjuuwicACYNGBHpmPdF5A==
X-Google-Smtp-Source: AOwi7QDv0Nc+1y8KDsXU0qLIsJ8/TU4cbGv6ZgluXpg0qsXFUzGiwRJMcwxKKdRZ0/lDomii3UQfV6Ln1lXrgXV9Md0=
X-Received: by 10.36.84.82 with SMTP id t79mr6837078ita.98.1506689430759; Fri,
	29 Sep 2017 05:50:30 -0700 (PDT)
MIME-Version: 1.0
References: <CAEgR2PGCZ=F85yjAbZgC6NtzhpdgBL3n4M2jowN12wJ7x-Ai1A@mail.gmail.com>
	<CAEgR2PGrxDQE0k8WX4XXz9GN-RAL6JB51ST9Hdz=ba36gRCa6A@mail.gmail.com>
	<CAEgR2PFjt=ihzRBhNXbHTAJz1R+3vz8o-zRZkDA3iBo39x9cTQ@mail.gmail.com>
	<CAEgR2PFfSjJjkTYq+DAmTzmkHPxqhn6fUDoXTzrRebz+OoUgqw@mail.gmail.com>
	<CAEgR2PG5ZueHKDXbsPDEjQG7xAYBa_JAtPZo9n1V2=STC1srpA@mail.gmail.com>
	<CAEgR2PGPQ1e9SmoWOS3V+N9v+OWiM4g3nPN3d9urc+DfkWEJ7A@mail.gmail.com>
	<CAEgR2PEKkHH6+Sh8cQGF83-s1tpwQZgd0fiuNz_xyWu0mUPfCA@mail.gmail.com>
	<CAEgR2PEyWFO1RFohVEpcb-M7aM-8xjCFvDPeJPD4zF4yTCyZ0A@mail.gmail.com>
	<CAEgR2PGrf+4pQRyNC_xKVEKXimKTWveGK9q6YJeZkG0_r=8tkg@mail.gmail.com>
In-Reply-To: <CAEgR2PGrf+4pQRyNC_xKVEKXimKTWveGK9q6YJeZkG0_r=8tkg@mail.gmail.com>
From: Alex Morcos <morcos@gmail.com>
Date: Fri, 29 Sep 2017 12:50:20 +0000
Message-ID: <CAPWm=eUCQo+1+2SWjpWG1kcidcLcugwTvVbug6WNmZBRVm_ebg@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>, 
	Daniele Pinna <daniele.pinna@gmail.com>, Mark@friedenbach.org
Content-Type: multipart/alternative; boundary="001a1135045e4eb473055a53784d"
X-Spam-Status: No, score=0.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,
	RCVD_IN_SORBS_SPAM autolearn=disabled version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Rebatable fees & incentive-safe fee markets
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Sep 2017 12:50:33 -0000

--001a1135045e4eb473055a53784d
Content-Type: text/plain; charset="UTF-8"

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
>

--001a1135045e4eb473055a53784d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><div dir=3D"auto">I had the same concern, or a miner could fill the re=
mainder of the block with their own high fee paying transactions if blocks =
were required to be full.=C2=A0</div><br><div class=3D"gmail_quote"><div>On=
 Fri, Sep 29, 2017 at 7:55 AM Daniele Pinna via bitcoin-dev &lt;<a href=3D"=
mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfounda=
tion.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D=
"auto">Maybe I&#39;m getting this wrong but wouldn&#39;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?<div dir=3D"auto"><br></di=
v><div dir=3D"auto">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 litera=
lly clog the network by paying 1btc every ten minutes.</div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">Am I missing something?</div></div><div dir=
=3D"auto"><div dir=3D"auto"><br></div><div dir=3D"auto">Daniele=C2=A0</div>=
</div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div></div>

--001a1135045e4eb473055a53784d--