summaryrefslogtreecommitdiff
path: root/e3/4067a41907523aaf3172121bbc161af0aa13de
blob: d1d00368216fdca109856fef02645d1fa8831a52 (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
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
Return-Path: <martin@stolze.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 3E94893E
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 27 Mar 2017 17:18:45 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qt0-f173.google.com (mail-qt0-f173.google.com
	[209.85.216.173])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 81670140
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 27 Mar 2017 17:18:43 +0000 (UTC)
Received: by mail-qt0-f173.google.com with SMTP id r45so43397189qte.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 27 Mar 2017 10:18:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=stolze-cc.20150623.gappssmtp.com; s=20150623;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=LQpBIMM98ohNtMeAbY2EAaWKw3ePJmnQAslt3u6RAR0=;
	b=P5kbpI4OeVjgP4K+KApTfFRHLy/DAFV7HSLrmOhk/+KXauHHtnd6B2Nc2Cf3AOvxjH
	gF3qedMzVGhybh/ZzbDZvD5upn6lE6RvSBiYDusj82HNmxd+JXtHztaFdhEOMmquIwVo
	CSI+EFwO0seAboMDIZojbF5H6j/s1RBT9yakPHGei+8LYAkBpXcFKQ+863AeBKlCn6zl
	rciWTNwPdt5mHG7QHS098VwP+ZPcsqKPPgGUxHIejdohp4ax7b+AWRbDPsE879fW8Wwu
	vGOt7YKIlkgyIXQdZivr3pnWZ/wKzdnFXVdlzliEONYRmxUucui7ufc1HeGW9oxSk0j7
	VxyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=LQpBIMM98ohNtMeAbY2EAaWKw3ePJmnQAslt3u6RAR0=;
	b=AV0WguV2fyq2BkY7T3gK0SJFLaqGjW4hxdbDtalJgeVWKoM6uWup6bPGH+oS5zEO6w
	GOOSD8lsFwlO1kadP3HoW6qyEE3MaVbY23b0b5J0ainAF1fKpZRkdIQLT6a9NNdJQZN8
	kwum2A9IpmZbaU/V+y7CmWmOGwar81s5XqvzZHTn/ku9U1wqYXt1veqgCbl/QShQzL9z
	nF5TTqKO96Yq1NvI6JlAo6eqA5cQTvrW2v8vIvJOLof+r9d59Xb2cHE9dh8yd7udKgph
	6oBM6RpEv0s5ecVJT6FmS1YmuAX5sZroK/9yI313XwaOif5RqCL+NYXzReRfhzrk+dvw
	xy6Q==
X-Gm-Message-State: AFeK/H1KgOz6hJwiJRmDMsHHyTYksqrgbEzHQKTsRt2TC+NB9peMegRq1dWOApVuDEb0yuk75ZHXw7C+Gy6HeQ==
X-Received: by 10.200.34.37 with SMTP id o34mr21897161qto.213.1490635122405;
	Mon, 27 Mar 2017 10:18:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.63.78 with HTTP; Mon, 27 Mar 2017 10:18:22 -0700 (PDT)
X-Originating-IP: [193.138.219.231]
In-Reply-To: <BLUPR15MB00516290185A5FC6B82F0D08B1300@BLUPR15MB0051.namprd15.prod.outlook.com>
References: <CAOyfL0r8dLR=7Co5+YzbPQUeTs6Lw+OQjZTy=iyoDmr6VV_Qpw@mail.gmail.com>
	<Rs51ijp6P21vJsv7OxVB-k8vuJC_aUd8KnpxHC3phNw_lPieY2lS-k95gytpHTNzzBfuX030RRFKzrrwS3pfjTuFea_eUfErb3qDp5LDHp4=@protonmail.com>
	<CAOyfL0qW=8091BAo9R2mskbyFSS3hOnXd+Wjsu4LQy7EtqzJjg@mail.gmail.com>
	<BLUPR15MB00516290185A5FC6B82F0D08B1300@BLUPR15MB0051.namprd15.prod.outlook.com>
From: Martin Stolze <martin@stolze.cc>
Date: Mon, 27 Mar 2017 18:18:22 +0100
Message-ID: <CAOyfL0r5f5FzS5phe8LbKuXF=AfE26gtqPy+RBWKg9zP4PsObQ@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11403b8ef714cc054bb98896
X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, HTML_MESSAGE, RCVD_IN_DNSWL_NONE,
	RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Mon, 27 Mar 2017 17:25:05 +0000
Subject: Re: [bitcoin-dev] Inquiry: Transaction Tiering
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: Mon, 27 Mar 2017 17:18:45 -0000

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

Yes, the terminology is creating a lot of confusion. I would be happy to
contribute to a discourse that helps to clear up the ambiguities and
cringeworthiness of current "standardized terminology".
Robert Keagen developed a perspective on psychological development [1] and
it appears to me that Stage 2 and 3 (miner, cash, network upgrade, ...) is
discussing with Stage 4 (hash power, settlement, fork, ...).

"Miner" is not wrong, just not helpful if you try to gauge the deeper
complexities of Bitcoin. Likewise, "money" is not wrong if you explain it
to a child, while credit and debt is much more useful if you want to gauge
the deeper complexities of economics.

still, any form forking has dilutive effect on existing BTC holders.


Not at all, I sleep sound and anticipate any such event as an ugly scrip
dividend.

Regards
Martin

[1] https://en.wikipedia.org/wiki/Robert_Kegan#In_Over_Our_Heads

On Sun, Mar 26, 2017 at 1:11 PM, greg misiorek <greg_not_so@hotmail.com>
wrote:

> agreed, the 'miner' term has run its course and plays a different role
> than it was originally set out to do, esp its original distributed nature.
> the 'mining business' has become concentrated too much and resembles
> today's financial institutions or simply banks, imho.
>
>
> still, any form forking has dilutive effect on existing BTC holders.
>
>
> thx, gm
> ------------------------------
> *From:* bitcoin-dev-bounces@lists.linuxfoundation.org <
> bitcoin-dev-bounces@lists.linuxfoundation.org> on behalf of Martin Stolze
> via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
> *Sent:* Saturday, March 25, 2017 1:15 PM
> *To:* praxeology_guy
> *Cc:* bitcoin-dev@lists.linuxfoundation.org
>
> *Subject:* Re: [bitcoin-dev] Inquiry: Transaction Tiering
>
> Thanks, those are valid concerns.
>
> > Potentially miners could create their own private communication
> channel/listening port for submitting transactions that they would not
> relay to other miners/the public node relay network.
> That is the idea. Transaction Processors could source transactions
> from the public mempool as well their proprietary mempool(s).
>
> > Miners would be incentivized to not relay higher fee transactions,
> because they would want to keep them to themselves for higher profits.
> Not so, a user may want to incentivise a specific Transaction
> Processor or many. A user can detect this behavior and withdraw his
> future business if he notices that his transaction is not included in
> a block despite there being transactions with lower fees included.
> Remember, the transaction can be advertised to different mempools and
> a Transaction Processor could lose this business to a competitor who
> processes the next block if he holds it back.
>
> Best Regards
> Martin
>
> PS: It seems not too late to get rid of misleading terms like "miner".
> Block rewards (infrastructure subsidies) will be neglectable for
> future generations and the analogy is exceedingly poor.
>
> On Sat, Mar 25, 2017 at 4:42 AM, praxeology_guy
> <praxeology_guy@protonmail.com> wrote:
> > Potentially miners could create their own private communication
> > channel/listening port for submitting transactions that they would not
> relay
> > to other miners/the public node relay network.  Users could then chose
> who
> > they want to relay to.  Miners would be incentivized to not relay higher
> fee
> > transactions, because they would want to keep them to themselves for
> higher
> > profits.
> >
> > Cheers,
> > Praxeology Guy
> >
> >
> > -------- Original Message --------
> > Subject: Re: [bitcoin-dev] Inquiry: Transaction Tiering
> > Local Time: March 22, 2017 12:48 PM
> > UTC Time: March 22, 2017 5:48 PM
> > From: bitcoin-dev@lists.linuxfoundation.org
> > To: bitcoin-dev@lists.linuxfoundation.org
> >
> > Hi Tim,
> > After writing this I figured that it was probably not evident at first
> > sight as the concept may be quite novel. The physical location of the
> > "miner" is indeed irrelevant, I am referring to the digital location.
> > Bitcoins blockchain is a digital location or better digital "space".
> > As far as I am concerned the authority lies with whoever governs this
> > particular block space. A "miner" can, or can not, include my
> > transaction.
> >
> > To make this more understandable:
> >
> > Abu Bakr al-Baghdadi can extend his caliphate into Bitcoins block
> > space and rule sovereign(!) over a given block. If he processes my
> > transaction my fee goes directly into the coffers of his organization.
> > The same goes for the Queen of England or the Emperor of China. My
> > interest is not necessarily aligned with each specific authority, yet
> > as you point out, I can only not use Bitcoin.
> > Alternatively, however, I can very well sign my transaction and send
> > it to an authority of my choosing to be included into the ledger, say
> > BitFurry. - This is what I describe in option 1.
> >
> > In order to protect my interest I do need to choose, maybe not today,
> > but eventually.
> >
> > I also think that people do care who processes transactions and a lot
> > of bickering could be spared if we could choose.
> >
> > If we assume a perfectly competitive market with 3 authorities that
> > govern the block space equally, the marginal cost of 1/3 of the block
> > space is the same for each, however, the marginal revenue absent of
> > block rewards is dependent on fees.
> > If people are willing to pay only a zero fee to a specific authority
> > while a fee greater than zero to the others it's clear that one would
> > be less competitive.
> >
> > Let us assume the fees are 10% of the revenue and the cost is 95 we
> > have currently the following situation:
> >
> > A: Cost=95; Revenue=100; Profit=5
> > B: Cost=95; Revenue=100; Profit=5
> > C: Cost=95; Revenue=100; Profit=5
> >
> > With transaction tiering, the outcome could be different!
> >
> > A: Cost=95; Revenue=90; Loss=5 // BSA that does not respect user
> interest.
> > B: Cost=95; Revenue=105; Profit=10
> > C: Cost=95; Revenue=105; Profit=10
> >
> > This could motivate transaction processors to behave in accordance
> > with user interest, or am I missing something?
> >
> > Best Regards,
> > Martin
> >
> >> From: Tim Ruffing <tim.ruffing@mmci.uni-saarland.de>
> >> To: bitcoin-dev@lists.linuxfoundation.org
> >> Cc:
> >> Bcc:
> >> Date: Tue, 21 Mar 2017 16:18:26 +0100
> >> Subject: Re: [bitcoin-dev] Inquiry: Transaction Tiering
> >> (I'm not a lawyer...)
> >>
> >> I'm not sure if I can make sense of your email.
> >>
> >> On Mon, 2017-03-20 at 20:12 +0000, Martin Stolze via bitcoin-dev wrote:
> >>> As a participant in the economy in general and of Bitcoin in
> >>> particular, I desire an ability to decide where I transact. The
> >>> current state of Bitcoin does not allow me to choose my place of
> >>> business. As a consequence, I try to learn what would be the best way
> >>> to conduct my business in good faith. [2]
> >>
> >> Ignoring the rest, I don't think that the physical location /
> >> jurisdiction of the miner has any legal implications for law applicable
> >> to the relationship between sender and receiver of a payment.
> >>
> >> This is not particular to Bitcoin. We're both in Germany (I guess).
> >> Assume we have a contract without specific agreements and I pay you in
> >> Icelandic kronur via PayPal (in Luxembourg) and my HTTPS requests to
> >> PayPal went via Australia and the US. Then German law applies to our
> >> contract, nothing in the middle can change that.
> >>
> >> Also ignoring possible security implications, there is just no need for
> >> a mechanism that enables users to select miners. I claim that almost
> >> nobody cares who will mine a transaction, because it makes no technical
> >> difference. If you don't want a specific miner to mine your
> >> transaction, then don't use Bitcoin.
> >>
> >> Tim
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> bitcoin-dev -- Bitcoin Protocol Discussion - Linux Foundation
> <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>
> lists.linuxfoundation.org
> Bitcoin development and protocol discussion. This list is lightly
> moderated. - No offensive posts, no personal attacks. - Posts must concern
> development of bitcoin ...
>
>
> >
> >
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> bitcoin-dev -- Bitcoin Protocol Discussion - Linux Foundation
> <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>
> lists.linuxfoundation.org
> Bitcoin development and protocol discussion. This list is lightly
> moderated. - No offensive posts, no personal attacks. - Posts must concern
> development of bitcoin ...
>
>
>

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

<div dir=3D"ltr">Yes, the terminology is creating a lot of confusion. I wou=
ld be happy to contribute to a discourse that helps to clear up the ambigui=
ties and cringeworthiness of current &quot;standardized terminology&quot;.<=
br>Robert Keagen developed a perspective on psychological development [1] a=
nd it appears to me that Stage 2 and 3 (miner, cash, network upgrade, ...) =
is discussing with Stage 4 (hash power, settlement, fork, ...).<div><br>&qu=
ot;Miner&quot; is not wrong, just not helpful if you try to gauge the deepe=
r complexities of Bitcoin. Likewise, &quot;money&quot; is not wrong if you =
explain it to a child, while credit and debt is much more useful if you wan=
t to gauge the deeper complexities of economics.<br><br><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">still, any form forking has dilutive effec=
t on existing BTC holders.</blockquote><br>Not at all, I sleep sound and an=
ticipate any such event as an ugly scrip dividend.=C2=A0<br><br>Regards<div=
>Martin<br><br>[1]=C2=A0<a href=3D"https://en.wikipedia.org/wiki/Robert_Keg=
an#In_Over_Our_Heads">https://en.wikipedia.org/wiki/<wbr>Robert_Kegan#In_Ov=
er_Our_Heads</a></div></div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Sun, Mar 26, 2017 at 1:11 PM, greg misiorek <span dir=
=3D"ltr">&lt;<a href=3D"mailto:greg_not_so@hotmail.com" target=3D"_blank">g=
reg_not_so@hotmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">




<div dir=3D"ltr">
<div id=3D"m_-4106169628145346925divtagdefaultwrapper" style=3D"font-size:1=
2pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif" dir=3D"lt=
r">
<p>agreed, the &#39;miner&#39; term has run its course and plays a differen=
t role than it was originally set out to do, esp its original=C2=A0distribu=
ted nature. the &#39;mining business&#39; has become concentrated too much =
and resembles today&#39;s financial institutions or simply
 banks, imho.=C2=A0</p>
<p><br>
</p>
<p>still, any form=C2=A0forking has dilutive effect on existing BTC holders=
.</p>
<p><br>
</p>
<p>thx, gm</p>
<div style=3D"color:rgb(0,0,0)">
<div>
<hr style=3D"display:inline-block;width:98%">
<div id=3D"m_-4106169628145346925x_divRplyFwdMsg" dir=3D"ltr"><font face=3D=
"Calibri, sans-serif" color=3D"#000000" style=3D"font-size:11pt"><b>From:</=
b> <a href=3D"mailto:bitcoin-dev-bounces@lists.linuxfoundation.org" target=
=3D"_blank">bitcoin-dev-bounces@lists.<wbr>linuxfoundation.org</a> &lt;<a h=
ref=3D"mailto:bitcoin-dev-bounces@lists.linuxfoundation.org" target=3D"_bla=
nk">bitcoin-dev-bounces@lists.<wbr>linuxfoundation.org</a>&gt; on behalf of=
 Martin Stolze via bitcoin-dev
 &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_bl=
ank">bitcoin-dev@lists.<wbr>linuxfoundation.org</a>&gt;<br>
<b>Sent:</b> Saturday, March 25, 2017 1:15 PM<br>
<b>To:</b> praxeology_guy<br>
<b>Cc:</b> <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=
=3D"_blank">bitcoin-dev@lists.<wbr>linuxfoundation.org</a><div><div class=
=3D"h5"><br>
<b>Subject:</b> Re: [bitcoin-dev] Inquiry: Transaction Tiering</div></div><=
/font>
<div>=C2=A0</div>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:10pt">
<div class=3D"m_-4106169628145346925PlainText"><div><div class=3D"h5">Thank=
s, those are valid concerns.<br>
<br>
&gt; Potentially miners could create their own private communication channe=
l/listening port for submitting transactions that they would not relay to o=
ther miners/the public node relay network.<br>
That is the idea. Transaction Processors could source transactions<br>
from the public mempool as well their proprietary mempool(s).<br>
<br>
&gt; Miners would be incentivized to not relay higher fee transactions, bec=
ause they would want to keep them to themselves for higher profits.<br>
Not so, a user may want to incentivise a specific Transaction<br>
Processor or many. A user can detect this behavior and withdraw his<br>
future business if he notices that his transaction is not included in<br>
a block despite there being transactions with lower fees included.<br>
Remember, the transaction can be advertised to different mempools and<br>
a Transaction Processor could lose this business to a competitor who<br>
processes the next block if he holds it back.<br>
<br>
Best Regards<br>
Martin<br>
<br>
PS: It seems not too late to get rid of misleading terms like &quot;miner&q=
uot;.<br>
Block rewards (infrastructure subsidies) will be neglectable for<br>
future generations and the analogy is exceedingly poor.<br>
<br>
On Sat, Mar 25, 2017 at 4:42 AM, praxeology_guy<br>
&lt;<a href=3D"mailto:praxeology_guy@protonmail.com" target=3D"_blank">prax=
eology_guy@protonmail.com</a><wbr>&gt; wrote:<br>
&gt; Potentially miners could create their own private communication<br>
&gt; channel/listening port for submitting transactions that they would not=
 relay<br>
&gt; to other miners/the public node relay network.=C2=A0 Users could then =
chose who<br>
&gt; they want to relay to.=C2=A0 Miners would be incentivized to not relay=
 higher fee<br>
&gt; transactions, because they would want to keep them to themselves for h=
igher<br>
&gt; profits.<br>
&gt;<br>
&gt; Cheers,<br>
&gt; Praxeology Guy<br>
&gt;<br>
&gt;<br>
&gt; -------- Original Message --------<br>
&gt; Subject: Re: [bitcoin-dev] Inquiry: Transaction Tiering<br>
&gt; Local Time: March 22, 2017 12:48 PM<br>
&gt; UTC Time: March 22, 2017 5:48 PM<br>
&gt; From: <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=
=3D"_blank">bitcoin-dev@lists.<wbr>linuxfoundation.org</a><br>
&gt; To: <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D=
"_blank">bitcoin-dev@lists.<wbr>linuxfoundation.org</a><br>
&gt;<br>
&gt; Hi Tim,<br>
&gt; After writing this I figured that it was probably not evident at first=
<br>
&gt; sight as the concept may be quite novel. The physical location of the<=
br>
&gt; &quot;miner&quot; is indeed irrelevant, I am referring to the digital =
location.<br>
&gt; Bitcoins blockchain is a digital location or better digital &quot;spac=
e&quot;.<br>
&gt; As far as I am concerned the authority lies with whoever governs this<=
br>
&gt; particular block space. A &quot;miner&quot; can, or can not, include m=
y<br>
&gt; transaction.<br>
&gt;<br>
&gt; To make this more understandable:<br>
&gt;<br>
&gt; Abu Bakr al-Baghdadi can extend his caliphate into Bitcoins block<br>
&gt; space and rule sovereign(!) over a given block. If he processes my<br>
&gt; transaction my fee goes directly into the coffers of his organization.=
<br>
&gt; The same goes for the Queen of England or the Emperor of China. My<br>
&gt; interest is not necessarily aligned with each specific authority, yet<=
br>
&gt; as you point out, I can only not use Bitcoin.<br>
&gt; Alternatively, however, I can very well sign my transaction and send<b=
r>
&gt; it to an authority of my choosing to be included into the ledger, say<=
br>
&gt; BitFurry. - This is what I describe in option 1.<br>
&gt;<br>
&gt; In order to protect my interest I do need to choose, maybe not today,<=
br>
&gt; but eventually.<br>
&gt;<br>
&gt; I also think that people do care who processes transactions and a lot<=
br>
&gt; of bickering could be spared if we could choose.<br>
&gt;<br>
&gt; If we assume a perfectly competitive market with 3 authorities that<br=
>
&gt; govern the block space equally, the marginal cost of 1/3 of the block<=
br>
&gt; space is the same for each, however, the marginal revenue absent of<br=
>
&gt; block rewards is dependent on fees.<br>
&gt; If people are willing to pay only a zero fee to a specific authority<b=
r>
&gt; while a fee greater than zero to the others it&#39;s clear that one wo=
uld<br>
&gt; be less competitive.<br>
&gt;<br>
&gt; Let us assume the fees are 10% of the revenue and the cost is 95 we<br=
>
&gt; have currently the following situation:<br>
&gt;<br>
&gt; A: Cost=3D95; Revenue=3D100; Profit=3D5<br>
&gt; B: Cost=3D95; Revenue=3D100; Profit=3D5<br>
&gt; C: Cost=3D95; Revenue=3D100; Profit=3D5<br>
&gt;<br>
&gt; With transaction tiering, the outcome could be different!<br>
&gt;<br>
&gt; A: Cost=3D95; Revenue=3D90; Loss=3D5 // BSA that does not respect user=
 interest.<br>
&gt; B: Cost=3D95; Revenue=3D105; Profit=3D10<br>
&gt; C: Cost=3D95; Revenue=3D105; Profit=3D10<br>
&gt;<br>
&gt; This could motivate transaction processors to behave in accordance<br>
&gt; with user interest, or am I missing something?<br>
&gt;<br>
&gt; Best Regards,<br>
&gt; Martin<br>
&gt;<br>
&gt;&gt; From: Tim Ruffing &lt;<a href=3D"mailto:tim.ruffing@mmci.uni-saarl=
and.de" target=3D"_blank">tim.ruffing@mmci.uni-<wbr>saarland.de</a>&gt;<br>
&gt;&gt; To: <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" targe=
t=3D"_blank">bitcoin-dev@lists.<wbr>linuxfoundation.org</a><br>
&gt;&gt; Cc:<br>
&gt;&gt; Bcc:<br>
&gt;&gt; Date: Tue, 21 Mar 2017 16:18:26 +0100<br>
&gt;&gt; Subject: Re: [bitcoin-dev] Inquiry: Transaction Tiering<br>
&gt;&gt; (I&#39;m not a lawyer...)<br>
&gt;&gt;<br>
&gt;&gt; I&#39;m not sure if I can make sense of your email.<br>
&gt;&gt;<br>
&gt;&gt; On Mon, 2017-03-20 at 20:12 +0000, Martin Stolze via bitcoin-dev w=
rote:<br>
&gt;&gt;&gt; As a participant in the economy in general and of Bitcoin in<b=
r>
&gt;&gt;&gt; particular, I desire an ability to decide where I transact. Th=
e<br>
&gt;&gt;&gt; current state of Bitcoin does not allow me to choose my place =
of<br>
&gt;&gt;&gt; business. As a consequence, I try to learn what would be the b=
est way<br>
&gt;&gt;&gt; to conduct my business in good faith. [2]<br>
&gt;&gt;<br>
&gt;&gt; Ignoring the rest, I don&#39;t think that the physical location /<=
br>
&gt;&gt; jurisdiction of the miner has any legal implications for law appli=
cable<br>
&gt;&gt; to the relationship between sender and receiver of a payment.<br>
&gt;&gt;<br>
&gt;&gt; This is not particular to Bitcoin. We&#39;re both in Germany (I gu=
ess).<br>
&gt;&gt; Assume we have a contract without specific agreements and I pay yo=
u in<br>
&gt;&gt; Icelandic kronur via PayPal (in Luxembourg) and my HTTPS requests =
to<br>
&gt;&gt; PayPal went via Australia and the US. Then German law applies to o=
ur<br>
&gt;&gt; contract, nothing in the middle can change that.<br>
&gt;&gt;<br>
&gt;&gt; Also ignoring possible security implications, there is just no nee=
d for<br>
&gt;&gt; a mechanism that enables users to select miners. I claim that almo=
st<br>
&gt;&gt; nobody cares who will mine a transaction, because it makes no tech=
nical<br>
&gt;&gt; difference. If you don&#39;t want a specific miner to mine your<br=
>
&gt;&gt; transaction, then don&#39;t use Bitcoin.<br>
&gt;&gt;<br>
&gt;&gt; Tim<br>
&gt; ______________________________<wbr>_________________<br>
&gt; bitcoin-dev mailing list<br>
&gt; <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_bl=
ank">bitcoin-dev@lists.<wbr>linuxfoundation.org</a><br>
&gt; <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-=
dev" id=3D"m_-4106169628145346925LPlnk881896" target=3D"_blank">
https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-<wbr>dev</a=
>
</div></div><div id=3D"m_-4106169628145346925LPBorder_GT_14905300907470.431=
4628742691553" style=3D"margin-bottom:20px;overflow:auto;width:100%;text-in=
dent:0px">
<table id=3D"m_-4106169628145346925LPContainer_14905300907390.9429467228958=
801" cellspacing=3D"0" style=3D"width:90%;background-color:rgb(255,255,255)=
;overflow:auto;padding-top:20px;padding-bottom:20px;margin-top:20px;border-=
top:1px dotted rgb(200,200,200);border-bottom:1px dotted rgb(200,200,200)">
<tbody>
<tr valign=3D"top" style=3D"border-spacing:0px">
<td id=3D"m_-4106169628145346925TextCell_14905300907420.05214088929817473" =
colspan=3D"2" style=3D"vertical-align:top;padding:0px;display:table-cell">
<div id=3D"m_-4106169628145346925LPRemovePreviewContainer_14905300907420.81=
66276469010367"></div>
<div id=3D"m_-4106169628145346925LPTitle_14905300907430.14484606878179007" =
style=3D"color:rgb(0,120,215);font-weight:normal;font-size:21px;font-family=
:wf_segoe-ui_light,&quot;Segoe UI Light&quot;,&quot;Segoe WP Light&quot;,&q=
uot;Segoe UI&quot;,&quot;Segoe WP&quot;,Tahoma,Arial,sans-serif;line-height=
:21px">
<a id=3D"m_-4106169628145346925LPUrlAnchor_14905300907440.8801382218354896"=
 href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" st=
yle=3D"text-decoration:none" target=3D"_blank">bitcoin-dev -- Bitcoin Proto=
col Discussion - Linux Foundation</a></div>
<div id=3D"m_-4106169628145346925LPMetadata_14905300907440.736217379707524"=
 style=3D"margin:10px 0px 16px;color:rgb(102,102,102);font-weight:normal;fo=
nt-family:wf_segoe-ui_normal,&quot;Segoe UI&quot;,&quot;Segoe WP&quot;,Taho=
ma,Arial,sans-serif;font-size:14px;line-height:14px">
<a href=3D"http://lists.linuxfoundation.org" target=3D"_blank">lists.linuxf=
oundation.org</a></div>
<div id=3D"m_-4106169628145346925LPDescription_14905300907460.7248311500000=
215" style=3D"display:block;color:rgb(102,102,102);font-weight:normal;font-=
family:wf_segoe-ui_normal,&quot;Segoe UI&quot;,&quot;Segoe WP&quot;,Tahoma,=
Arial,sans-serif;font-size:14px;line-height:20px;max-height:100px;overflow:=
hidden">
Bitcoin development and protocol discussion. This list is lightly moderated=
. - No offensive posts, no personal attacks. - Posts must concern developme=
nt of bitcoin ...</div>
</td>
</tr>
</tbody>
</table>
</div><span class=3D"">
<br>
<br>
&gt;<br>
&gt;<br>
______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
id=3D"m_-4106169628145346925LPlnk394161" target=3D"_blank">https://lists.li=
nuxfoundation.<wbr>org/mailman/listinfo/bitcoin-<wbr>dev</a>
</span><div id=3D"m_-4106169628145346925LPBorder_GT_14905300907840.53993136=
11030598" style=3D"margin-bottom:20px;overflow:auto;width:100%;text-indent:=
0px">
<table id=3D"m_-4106169628145346925LPContainer_14905300907820.8151816162637=
471" cellspacing=3D"0" style=3D"width:90%;background-color:rgb(255,255,255)=
;overflow:auto;padding-top:20px;padding-bottom:20px;margin-top:20px;border-=
top:1px dotted rgb(200,200,200);border-bottom:1px dotted rgb(200,200,200)">
<tbody>
<tr valign=3D"top" style=3D"border-spacing:0px">
<td id=3D"m_-4106169628145346925TextCell_14905300907830.5199495433130616" c=
olspan=3D"2" style=3D"vertical-align:top;padding:0px;display:table-cell">
<div id=3D"m_-4106169628145346925LPRemovePreviewContainer_14905300907830.36=
095528093563334"></div>
<div id=3D"m_-4106169628145346925LPTitle_14905300907830.14148417394525215" =
style=3D"color:rgb(0,120,215);font-weight:normal;font-size:21px;font-family=
:wf_segoe-ui_light,&quot;Segoe UI Light&quot;,&quot;Segoe WP Light&quot;,&q=
uot;Segoe UI&quot;,&quot;Segoe WP&quot;,Tahoma,Arial,sans-serif;line-height=
:21px">
<a id=3D"m_-4106169628145346925LPUrlAnchor_14905300907830.20590515024781242=
" href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" s=
tyle=3D"text-decoration:none" target=3D"_blank">bitcoin-dev -- Bitcoin Prot=
ocol Discussion - Linux Foundation</a></div>
<div id=3D"m_-4106169628145346925LPMetadata_14905300907830.7737769826803942=
" style=3D"margin:10px 0px 16px;color:rgb(102,102,102);font-weight:normal;f=
ont-family:wf_segoe-ui_normal,&quot;Segoe UI&quot;,&quot;Segoe WP&quot;,Tah=
oma,Arial,sans-serif;font-size:14px;line-height:14px">
<a href=3D"http://lists.linuxfoundation.org" target=3D"_blank">lists.linuxf=
oundation.org</a></div>
<div id=3D"m_-4106169628145346925LPDescription_14905300907830.2687833551841=
585" style=3D"display:block;color:rgb(102,102,102);font-weight:normal;font-=
family:wf_segoe-ui_normal,&quot;Segoe UI&quot;,&quot;Segoe WP&quot;,Tahoma,=
Arial,sans-serif;font-size:14px;line-height:20px;max-height:100px;overflow:=
hidden">
Bitcoin development and protocol discussion. This list is lightly moderated=
. - No offensive posts, no personal attacks. - Posts must concern developme=
nt of bitcoin ...</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<br>
</div>
</span></font></div>
</div>
</div>

</blockquote></div><br></div>

--001a11403b8ef714cc054bb98896--