summaryrefslogtreecommitdiff
path: root/a2/964c624040bcbeae6e74c04ab67b300866b6dc
blob: 85330a09a6669188a38eb8c949de8bc050678baf (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
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
Return-Path: <vitteaymeric@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 1353BCB8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  2 Apr 2019 16:49:00 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr1-f44.google.com (mail-wr1-f44.google.com
	[209.85.221.44])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5D751712
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  2 Apr 2019 16:48:58 +0000 (UTC)
Received: by mail-wr1-f44.google.com with SMTP id w1so17585181wrp.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 02 Apr 2019 09:48:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=subject:to:references:from:message-id:date:user-agent:mime-version
	:in-reply-to; bh=nGEnddA9Lx0x5p19ENmH6Kv0ucpN+EUAeZhl2izgHME=;
	b=p4Dwq5uyWzjGP6s3EUSh+7/N5Top3liudDw9lCNb4X01E4YcjohcN2Z7mkJyeDGyHE
	kfKhIY488K6AdfknxYp3zNPfV1RmC70WJn4mSZXnPXWI0LsUAYaIEZtAKKaRYY3K/Afq
	/SBVDQq5Qq8IpH70121XbiPP2644E5JkbwL6iHxUyW/cgyQTuip8f9KBmqGIdUlrBGRW
	tGOmBNLjOKosJt1m/TuAurRYiccPt2vczZmoVG/SsyqXMp69lJj4ZH84tNqCLCnjygnp
	V/jBnIhA6IOWktSB8yqfVV3m5N65oLNLVo3x7yPuaw/RG2OUpsXCGxoDn/ey/JkSt/Yq
	WTPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:subject:to:references:from:message-id:date
	:user-agent:mime-version:in-reply-to;
	bh=nGEnddA9Lx0x5p19ENmH6Kv0ucpN+EUAeZhl2izgHME=;
	b=kmGG4BL6qXHlOK3XTzcSmTZq44uy4n7TlROE6GGD/6n7bqrbwkjaRmeweODY4fC2uk
	bhnurtSBRzyW0zut15UOGJKqISg3p/zUm7XzPqajRKfTx7MVtBrnv9XPthg4Q8HfxQ4N
	Yw/+tt8DteGpG+otNg5B/Nfzoq/Tw7MCH3T+Pp4iYP+KYoYK1ka28T7Ayzob7dFTggJD
	G1HCj2NaWjE5JsbmRTBYM3WXmx+eLOFfEn9BPauRZk9CSqS/ix69oh6AwODqHgyLoMCD
	YAFW/ZCop23iUyN+l2Gjiuv4IO4o741ITcRkkRolvbSCTxvKOgbIPnrZWyYmapAs2UNJ
	39jw==
X-Gm-Message-State: APjAAAXNLzrSCKbFr6FB4YDkXWeDJAPpT2DTJiFMMM3r4T+5gNWjs2lV
	0CrdPMdJ8RL2CTTg5cECIh6PaCa3
X-Google-Smtp-Source: APXvYqwLlhkcQZvsuMUo86Glp/JAORpmPpXE8N90C1h3Iv915nBFglcjDvuQtNnjYX3olOB4Q+K7Dw==
X-Received: by 2002:adf:e443:: with SMTP id t3mr15326393wrm.257.1554223736985; 
	Tue, 02 Apr 2019 09:48:56 -0700 (PDT)
Received: from [192.168.43.146] ([92.184.101.240])
	by smtp.googlemail.com with ESMTPSA id
	w11sm39652431wre.15.2019.04.02.09.48.55
	(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Tue, 02 Apr 2019 09:48:56 -0700 (PDT)
To: "Dana L. Coe" <dana.coe@bitlox.com>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
	Melvin Carvalho <melvincarvalho@gmail.com>
References: <201904010030.34825.luke@dashjr.org>
	<CAKaEYhLfBVFQXST4DavZ=tK=ZGuPgOYa9CxpuPvEVL1CybVFjA@mail.gmail.com>
	<DFB57847-C402-4206-BA9E-E3DA2FB3077C@bitlox.com>
From: Aymeric Vitte <vitteaymeric@gmail.com>
Message-ID: <df67f6f3-ded7-6f71-98ee-6a868b802ada@gmail.com>
Date: Tue, 2 Apr 2019 18:48:55 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:45.0) Gecko/20100101
	Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <DFB57847-C402-4206-BA9E-E3DA2FB3077C@bitlox.com>
Content-Type: multipart/alternative;
	boundary="------------1EF9017E410CF12F9406B9DF"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Wed, 03 Apr 2019 00:09:25 +0000
Subject: Re: [bitcoin-dev] Softfork proposal for minimum price of $50k
	USD/BTC
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: Tue, 02 Apr 2019 16:49:00 -0000

This is a multi-part message in MIME format.
--------------1EF9017E410CF12F9406B9DF
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Right and everybody knows that Tether is the most clever sidechain ever 
invented far more sophisticated than lightning, which makes me think 
that a punishment should be added in the proposal for the cheater 
advertising a price < 50 k (or 100) and/or selling before 1-3 years 
(tbd) so all his coins go to the Bitcoin Mediator, a new notion here to 
sustain the community (I modestly apply for the position)


Le 01/04/2019 à 13:50, Dana L. Coe via bitcoin-dev a écrit :
> I suggest in the spirit of the times that we not use USD as the 
> reference, but USDT.
>
> Everyone knows Tethers are much more flexible in tracking the true 
> value of the US dollar.
>
> Dana
>
>> On Apr 1, 2019, at 7:22 PM, Melvin Carvalho via bitcoin-dev 
>> <bitcoin-dev@lists.linuxfoundation.org 
>> <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
>>
>>
>>
>> On Mon, 1 Apr 2019 at 02:32, Luke Dashjr via bitcoin-dev 
>> <bitcoin-dev@lists.linuxfoundation.org 
>> <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
>>
>>     Certain parts of the community have been selling bitcoins for
>>     unreasonably
>>     low prices. This has halted Bitcoin's valuation at $20k and even
>>     driven the
>>     price down below $15k! However, clearly Bitcoin is worth much
>>     more than
>>     that, and there is widespread support for higher prices.
>>
>>     In light of this, I have written and implemented two BIPs: one to
>>     add a
>>     signed price field to Bitcoin transactions, and the other to
>>     softfork a
>>     minimum price of $50k USD/BTC a year from today.
>>
>>     The BIPs are here, as well as included at the bottom of this
>>     email for
>>     convenience:
>>     https://github.com/luke-jr/bips/blob/softfork_50k/bip-usdprice.mediawiki
>>     https://github.com/luke-jr/bips/blob/softfork_50k/bip-softfork-50k-price.mediawiki
>>
>>     A reference implementation is here:
>>     https://github.com/bitcoin/bitcoin/compare/v0.17.1...luke-jr:softfork_50k
>>
>>     Please review ASAP so we can get these deployed in Bitcoin Core
>>     v0.18.
>>
>>
>> This seems a little arbitrary.  Ask yourself, "Why the USD?".  Yes, 
>> it is the dominant currency now, but in 2, 6, 10, 14 years?  Who knows.
>>
>> You could make equally an argument to denominate in euros.  Or a 
>> basket of currencies, or even the Bancor.
>>
>> However the wider question is why even denominate in fiat at all?
>>
>> I suggest denominating the minimum value in satoshsis themselves, 
>> which would be a negligable upgrade to the network.
>>
>>
>>     Luke
>>
>>
>>     <pre>
>>       BIP: ?
>>       Layer: Applications
>>       Title: Signed USD Price Indicator
>>       Author: Luke Dashjr <luke+bip@dashjr.org
>>     <mailto:luke%2Bbip@dashjr.org>>
>>       Comments-Summary: No comments yet.
>>       Comments-URI:
>>     https://github.com/bitcoin/bips/wiki/Comments:BIP-????
>>       Status: Draft
>>       Type: Standards Track
>>       Created: 2019-04-01
>>       License: BSD-2-Clause
>>     </pre>
>>
>>     ==Abstract==
>>
>>     This BIP proposes a method to explicitly specify and sign the
>>     USD/BTC price
>>     for transactions.
>>
>>     ==Copyright==
>>
>>     This BIP is licensed under the BSD 2-clause license.
>>
>>     ==Motivation==
>>
>>     Certain parts of the community have been selling bitcoins for
>>     unreasonably low
>>     prices. This has halted Bitcoin's valuation at $20k and even
>>     driven the price
>>     down below $15k! However, clearly Bitcoin is worth much more than
>>     that, and
>>     there is widespread support for higher prices.
>>
>>     This problem can be fixed by setting a global minimum price for
>>     bitcoins.
>>     Unfortunately, today, the consensus protocol is completely
>>     oblivious to the
>>     price bitcoins are traded at. Therefore, we must first add a
>>     field to Bitcoin
>>     transactions to indicate their price.
>>
>>     ==Specification==
>>
>>     ===New field and legal implication===
>>
>>     A new field is added to Bitcoin transactions. This field, if
>>     present, must
>>     represent the honest and true USD/BTC rate used for the
>>     transaction. By
>>     signing the transaction, the sender legally affirms this is the
>>     valuation of
>>     bitcoins used for the transaction.
>>
>>     For the avoidance of doubt: when the transaction is valued in a
>>     currency other
>>     than USD, any reasonable exchange rate may be used to come up
>>     with the USD
>>     valuation.
>>
>>     ===Serialisation===
>>
>>     When serialising the transaction for any purpose, including
>>     signing, weight
>>     calculation, and so on, the output count must be incremented by
>>     one. Prior to
>>     the first real output, the following bytes must be inserted:
>>
>>     * Constant: 00 00 00 00 00 00 00 00
>>     * A single byte, the size in bytes of the remainder of the
>>     inserted data
>>     * Constant: 6a 04 55 53 44 24
>>     * A single byte, the size in bytes of the remainder of the
>>     inserted data
>>     * The USD/BTC rate used for the transaction, in standard signed
>>     integer
>>     serialisation, with all leading zeros removed (except as
>>     necessary to
>>     preserve the sign bit).
>>
>>     ==Backwards compatibility==
>>
>>     ===Consensus===
>>
>>     The new price field is serialised as a dummy output, with a value
>>     of zero, and
>>     a scriptPubKey that begins with OP_RETURN (6a). Existing nodes
>>     will ignore
>>     this dummy output, and the leading OP_RETURN in the scriptPubKey
>>     ensures it
>>     is never considered spendable.
>>
>>     Therefore, current nodes will ignore the new field entirely, and
>>     accept
>>     transactions using it.
>>
>>     ===Wallets===
>>
>>     Existing wallets do not typically generate price indicators as
>>     specified.
>>     Under this BIP, this absence of the field is perfectly acceptable.
>>
>>     ==Reference implementation==
>>
>>     https://github.com/bitcoin/bitcoin/compare/v0.17.1...luke-jr:usd_price_tx_field
>>
>>     <pre>
>>       BIP: ?
>>       Layer: Consensus (soft fork)
>>       Title: $50k USD/BTC Minimum Price
>>       Author: Luke Dashjr <luke+bip@dashjr.org
>>     <mailto:luke%2Bbip@dashjr.org>>
>>       Comments-Summary: No comments yet.
>>       Comments-URI:
>>     https://github.com/bitcoin/bips/wiki/Comments:BIP-????
>>       Status: Draft
>>       Type: Standards Track
>>       Created: 2019-04-01
>>       License: BSD-2-Clause
>>       Requires: usdprice
>>     </pre>
>>
>>     ==Abstract==
>>
>>     This BIP defines a minimum price of $50k USD/BTC for Bitcoin
>>     transactions.
>>
>>     ==Copyright==
>>
>>     This BIP is licensed under the BSD 2-clause license.
>>
>>     ==Motivation==
>>
>>     Certain parts of the community have been selling bitcoins for
>>     unreasonably low
>>     prices. This has halted Bitcoin's valuation at $20k and even
>>     driven the price
>>     down below $15k! However, clearly Bitcoin is worth much more than
>>     that, and
>>     there is widespread support for higher prices.
>>
>>     bip-usdprice defines a new field to indicate the price of
>>     transactions. Using
>>     this, we can softfork to require a minimum transaction price.
>>
>>     ==Specification==
>>
>>     Beginning with block height 622370 (expected approximately 2020
>>     April 1), a
>>     block is reject as invalid unless all transactions it contains
>>     both declare a
>>     USD/BTC price (as defined in bip-usdprice) and specify a price
>>     that is at a
>>     minimum $50k USD/BTC.
>>
>>     ==Backwards compatibility==
>>
>>     As a soft fork, older nodes will continue to accept the
>>     blockchain without
>>     modification. Non-upgraded nodes, however, will not validate the
>>     minimum
>>     price requirement, and may accept invalid blocks if miners choose
>>     to make
>>     them. Since transactions not declaring a price are at this time
>>     still
>>     common-place, the softfork activation has been set a full year
>>     into the
>>     future to ensure time to upgrade both nodes and wallet software.
>>
>>     ==Reference implementation==
>>
>>     https://github.com/luke-jr/bitcoin/compare/usd_price_tx_field...softfork_50k
>>     _______________________________________________
>>     bitcoin-dev mailing list
>>     bitcoin-dev@lists.linuxfoundation.org
>>     <mailto:bitcoin-dev@lists.linuxfoundation.org>
>>     https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org 
>> <mailto:bitcoin-dev@lists.linuxfoundation.org>
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

-- 
Peersm : http://www.peersm.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms


--------------1EF9017E410CF12F9406B9DF
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Right and everybody knows that Tether is the most clever
      sidechain ever invented far more sophisticated than lightning,
      which makes me think that a punishment should be added in the
      proposal for the cheater advertising a price &lt; 50 k (or 100)
      and/or selling before 1-3 years (tbd) so all his coins go to the
      Bitcoin Mediator, a new notion here to sustain the community (I
      modestly apply for the position)<br>
    </p>
    <br>
    <div class="moz-cite-prefix">Le 01/04/2019 à 13:50, Dana L. Coe via
      bitcoin-dev a écrit :<br>
    </div>
    <blockquote
      cite="mid:DFB57847-C402-4206-BA9E-E3DA2FB3077C@bitlox.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      I suggest in the spirit of the times that we not use USD as the
      reference, but USDT.
      <div class=""><br class="">
      </div>
      <div class="">Everyone knows Tethers are much more flexible in
        tracking the true value of the US dollar.</div>
      <div class=""><br class="">
      </div>
      <div class="">Dana<br class="">
        <div><br class="">
          <blockquote type="cite" class="">
            <div class="">On Apr 1, 2019, at 7:22 PM, Melvin Carvalho
              via bitcoin-dev &lt;<a moz-do-not-send="true"
                href="mailto:bitcoin-dev@lists.linuxfoundation.org"
                class="">bitcoin-dev@lists.linuxfoundation.org</a>&gt;
              wrote:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <div dir="ltr" class="">
                <div dir="ltr" class=""><br class="">
                </div>
                <br class="">
                <div class="gmail_quote">
                  <div dir="ltr" class="gmail_attr">On Mon, 1 Apr 2019
                    at 02:32, Luke Dashjr via bitcoin-dev &lt;<a
                      moz-do-not-send="true"
                      href="mailto:bitcoin-dev@lists.linuxfoundation.org"
                      class="">bitcoin-dev@lists.linuxfoundation.org</a>&gt;
                    wrote:<br class="">
                  </div>
                  <blockquote class="gmail_quote" style="margin:0px 0px
                    0px 0.8ex;border-left:1px solid
                    rgb(204,204,204);padding-left:1ex">Certain parts of
                    the community have been selling bitcoins for
                    unreasonably<br class="">
                    low prices. This has halted Bitcoin's valuation at
                    $20k and even driven the<br class="">
                    price down below $15k! However, clearly Bitcoin is
                    worth much more than<br class="">
                    that, and there is widespread support for higher
                    prices.<br class="">
                    <br class="">
                    In light of this, I have written and implemented two
                    BIPs: one to add a<br class="">
                    signed price field to Bitcoin transactions, and the
                    other to softfork a<br class="">
                    minimum price of $50k USD/BTC a year from today.<br
                      class="">
                    <br class="">
                    The BIPs are here, as well as included at the bottom
                    of this email for <br class="">
                    convenience:<br class="">
                      <a moz-do-not-send="true"
href="https://github.com/luke-jr/bips/blob/softfork_50k/bip-usdprice.mediawiki"
                      rel="noreferrer" target="_blank" class="">https://github.com/luke-jr/bips/blob/softfork_50k/bip-usdprice.mediawiki</a><br
                      class="">
                    <a moz-do-not-send="true"
href="https://github.com/luke-jr/bips/blob/softfork_50k/bip-softfork-50k-price.mediawiki"
                      rel="noreferrer" target="_blank" class="">https://github.com/luke-jr/bips/blob/softfork_50k/bip-softfork-50k-price.mediawiki</a><br
                      class="">
                    <br class="">
                    A reference implementation is here:<br class="">
                      <a moz-do-not-send="true"
href="https://github.com/bitcoin/bitcoin/compare/v0.17.1...luke-jr:softfork_50k"
                      rel="noreferrer" target="_blank" class="">https://github.com/bitcoin/bitcoin/compare/v0.17.1...luke-jr:softfork_50k</a><br
                      class="">
                    <br class="">
                    Please review ASAP so we can get these deployed in
                    Bitcoin Core v0.18.<br class="">
                  </blockquote>
                  <div class=""><br class="">
                  </div>
                  <div class="">This seems a little arbitrary.  Ask
                    yourself, "Why the USD?".  Yes, it is the dominant
                    currency now, but in 2, 6, 10, 14 years?  Who knows.</div>
                  <div class=""><br class="">
                  </div>
                  <div class="">You could make equally an argument to
                    denominate in euros.  Or a basket of currencies, or
                    even the Bancor.</div>
                  <div class=""><br class="">
                  </div>
                  <div class="">However the wider question is why even
                    denominate in fiat at all?  <br class="">
                  </div>
                  <div class=""><br class="">
                  </div>
                  <div class="">I suggest denominating the minimum value
                    in satoshsis themselves, which would be a negligable
                    upgrade to the network.<br class="">
                  </div>
                  <div class=""> </div>
                  <blockquote class="gmail_quote" style="margin:0px 0px
                    0px 0.8ex;border-left:1px solid
                    rgb(204,204,204);padding-left:1ex">
                    <br class="">
                    Luke<br class="">
                    <br class="">
                    <br class="">
                    &lt;pre&gt;<br class="">
                      BIP: ?<br class="">
                      Layer: Applications<br class="">
                      Title: Signed USD Price Indicator<br class="">
                      Author: Luke Dashjr &lt;<a moz-do-not-send="true"
                      href="mailto:luke%2Bbip@dashjr.org"
                      target="_blank" class="">luke+bip@dashjr.org</a>&gt;<br
                      class="">
                      Comments-Summary: No comments yet.<br class="">
                      Comments-URI: <a moz-do-not-send="true"
                      href="https://github.com/bitcoin/bips/wiki/Comments:BIP-??"
                      rel="noreferrer" target="_blank" class="">https://github.com/bitcoin/bips/wiki/Comments:BIP-??</a>??<br
                      class="">
                      Status: Draft<br class="">
                      Type: Standards Track<br class="">
                      Created: 2019-04-01<br class="">
                      License: BSD-2-Clause<br class="">
                    &lt;/pre&gt;<br class="">
                    <br class="">
                    ==Abstract==<br class="">
                    <br class="">
                    This BIP proposes a method to explicitly specify and
                    sign the USD/BTC price <br class="">
                    for transactions.<br class="">
                    <br class="">
                    ==Copyright==<br class="">
                    <br class="">
                    This BIP is licensed under the BSD 2-clause license.<br
                      class="">
                    <br class="">
                    ==Motivation==<br class="">
                    <br class="">
                    Certain parts of the community have been selling
                    bitcoins for unreasonably low <br class="">
                    prices. This has halted Bitcoin's valuation at $20k
                    and even driven the price <br class="">
                    down below $15k! However, clearly Bitcoin is worth
                    much more than that, and <br class="">
                    there is widespread support for higher prices.<br
                      class="">
                    <br class="">
                    This problem can be fixed by setting a global
                    minimum price for bitcoins. <br class="">
                    Unfortunately, today, the consensus protocol is
                    completely oblivious to the <br class="">
                    price bitcoins are traded at. Therefore, we must
                    first add a field to Bitcoin <br class="">
                    transactions to indicate their price.<br class="">
                    <br class="">
                    ==Specification==<br class="">
                    <br class="">
                    ===New field and legal implication===<br class="">
                    <br class="">
                    A new field is added to Bitcoin transactions. This
                    field, if present, must <br class="">
                    represent the honest and true USD/BTC rate used for
                    the transaction. By <br class="">
                    signing the transaction, the sender legally affirms
                    this is the valuation of <br class="">
                    bitcoins used for the transaction.<br class="">
                    <br class="">
                    For the avoidance of doubt: when the transaction is
                    valued in a currency other <br class="">
                    than USD, any reasonable exchange rate may be used
                    to come up with the USD <br class="">
                    valuation.<br class="">
                    <br class="">
                    ===Serialisation===<br class="">
                    <br class="">
                    When serialising the transaction for any purpose,
                    including signing, weight <br class="">
                    calculation, and so on, the output count must be
                    incremented by one. Prior to <br class="">
                    the first real output, the following bytes must be
                    inserted:<br class="">
                    <br class="">
                    * Constant: 00 00 00 00 00 00 00 00<br class="">
                    * A single byte, the size in bytes of the remainder
                    of the inserted data<br class="">
                    * Constant: 6a 04 55 53 44 24<br class="">
                    * A single byte, the size in bytes of the remainder
                    of the inserted data<br class="">
                    * The USD/BTC rate used for the transaction, in
                    standard signed integer <br class="">
                    serialisation, with all leading zeros removed
                    (except as necessary to <br class="">
                    preserve the sign bit).<br class="">
                    <br class="">
                    ==Backwards compatibility==<br class="">
                    <br class="">
                    ===Consensus===<br class="">
                    <br class="">
                    The new price field is serialised as a dummy output,
                    with a value of zero, and <br class="">
                    a scriptPubKey that begins with OP_RETURN (6a).
                    Existing nodes will ignore <br class="">
                    this dummy output, and the leading OP_RETURN in the
                    scriptPubKey ensures it <br class="">
                    is never considered spendable.<br class="">
                    <br class="">
                    Therefore, current nodes will ignore the new field
                    entirely, and accept <br class="">
                    transactions using it.<br class="">
                    <br class="">
                    ===Wallets===<br class="">
                    <br class="">
                    Existing wallets do not typically generate price
                    indicators as specified. <br class="">
                    Under this BIP, this absence of the field is
                    perfectly acceptable.<br class="">
                    <br class="">
                    ==Reference implementation==<br class="">
                    <br class="">
                    <a moz-do-not-send="true"
href="https://github.com/bitcoin/bitcoin/compare/v0.17.1...luke-jr:usd_price_tx_field"
                      rel="noreferrer" target="_blank" class="">https://github.com/bitcoin/bitcoin/compare/v0.17.1...luke-jr:usd_price_tx_field</a><br
                      class="">
                    <br class="">
                    &lt;pre&gt;<br class="">
                      BIP: ?<br class="">
                      Layer: Consensus (soft fork)<br class="">
                      Title: $50k USD/BTC Minimum Price<br class="">
                      Author: Luke Dashjr &lt;<a moz-do-not-send="true"
                      href="mailto:luke%2Bbip@dashjr.org"
                      target="_blank" class="">luke+bip@dashjr.org</a>&gt;<br
                      class="">
                      Comments-Summary: No comments yet.<br class="">
                      Comments-URI: <a moz-do-not-send="true"
                      href="https://github.com/bitcoin/bips/wiki/Comments:BIP-??"
                      rel="noreferrer" target="_blank" class="">https://github.com/bitcoin/bips/wiki/Comments:BIP-??</a>??<br
                      class="">
                      Status: Draft<br class="">
                      Type: Standards Track<br class="">
                      Created: 2019-04-01<br class="">
                      License: BSD-2-Clause<br class="">
                      Requires: usdprice<br class="">
                    &lt;/pre&gt;<br class="">
                    <br class="">
                    ==Abstract==<br class="">
                    <br class="">
                    This BIP defines a minimum price of $50k USD/BTC for
                    Bitcoin transactions.<br class="">
                    <br class="">
                    ==Copyright==<br class="">
                    <br class="">
                    This BIP is licensed under the BSD 2-clause license.<br
                      class="">
                    <br class="">
                    ==Motivation==<br class="">
                    <br class="">
                    Certain parts of the community have been selling
                    bitcoins for unreasonably low <br class="">
                    prices. This has halted Bitcoin's valuation at $20k
                    and even driven the price <br class="">
                    down below $15k! However, clearly Bitcoin is worth
                    much more than that, and <br class="">
                    there is widespread support for higher prices.<br
                      class="">
                    <br class="">
                    bip-usdprice defines a new field to indicate the
                    price of transactions. Using <br class="">
                    this, we can softfork to require a minimum
                    transaction price.<br class="">
                    <br class="">
                    ==Specification==<br class="">
                    <br class="">
                    Beginning with block height 622370 (expected
                    approximately 2020 April 1), a <br class="">
                    block is reject as invalid unless all transactions
                    it contains both declare a <br class="">
                    USD/BTC price (as defined in bip-usdprice) and
                    specify a price that is at a <br class="">
                    minimum $50k USD/BTC.<br class="">
                    <br class="">
                    ==Backwards compatibility==<br class="">
                    <br class="">
                    As a soft fork, older nodes will continue to accept
                    the blockchain without <br class="">
                    modification. Non-upgraded nodes, however, will not
                    validate the minimum <br class="">
                    price requirement, and may accept invalid blocks if
                    miners choose to make <br class="">
                    them. Since transactions not declaring a price are
                    at this time still <br class="">
                    common-place, the softfork activation has been set a
                    full year into the <br class="">
                    future to ensure time to upgrade both nodes and
                    wallet software.<br class="">
                    <br class="">
                    ==Reference implementation==<br class="">
                    <br class="">
                    <a moz-do-not-send="true"
href="https://github.com/luke-jr/bitcoin/compare/usd_price_tx_field...softfork_50k"
                      rel="noreferrer" target="_blank" class="">https://github.com/luke-jr/bitcoin/compare/usd_price_tx_field...softfork_50k</a><br
                      class="">
                    _______________________________________________<br
                      class="">
                    bitcoin-dev mailing list<br class="">
                    <a moz-do-not-send="true"
                      href="mailto:bitcoin-dev@lists.linuxfoundation.org"
                      target="_blank" class="">bitcoin-dev@lists.linuxfoundation.org</a><br
                      class="">
                    <a moz-do-not-send="true"
                      href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev"
                      rel="noreferrer" target="_blank" class="">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a><br
                      class="">
                  </blockquote>
                </div>
              </div>
              _______________________________________________<br
                class="">
              bitcoin-dev mailing list<br class="">
              <a moz-do-not-send="true"
                href="mailto:bitcoin-dev@lists.linuxfoundation.org"
                class="">bitcoin-dev@lists.linuxfoundation.org</a><br
                class="">
<a class="moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a><br
                class="">
            </div>
          </blockquote>
        </div>
        <br class="">
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
bitcoin-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class="moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Peersm : <a class="moz-txt-link-freetext" href="http://www.peersm.com">http://www.peersm.com</a>
node-Tor : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms/node-Tor">https://www.github.com/Ayms/node-Tor</a>
GitHub : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms">https://www.github.com/Ayms</a></pre>
  </body>
</html>

--------------1EF9017E410CF12F9406B9DF--