summaryrefslogtreecommitdiff
path: root/a8/946f5df44fbddf438a97715b5cf745a73603a0
blob: c896f04875fbdf4e43ee1a3ad511ca3ee24227a1 (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
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
Return-Path: <fresheneesz@gmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 90D7BC002D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 27 Aug 2022 21:03:21 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 5569B40140
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 27 Aug 2022 21:03:21 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 5569B40140
Authentication-Results: smtp2.osuosl.org;
 dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
 header.a=rsa-sha256 header.s=20210112 header.b=aQlGTajO
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.599
X-Spam-Level: 
X-Spam-Status: No, score=-1.599 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, PDS_BTC_ID=0.499, RCVD_IN_DNSWL_NONE=-0.0001,
 SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
 by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id dMzHEarTDUui
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 27 Aug 2022 21:03:19 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org A84354038E
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com
 [IPv6:2607:f8b0:4864:20::e34])
 by smtp2.osuosl.org (Postfix) with ESMTPS id A84354038E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 27 Aug 2022 21:03:18 +0000 (UTC)
Received: by mail-vs1-xe34.google.com with SMTP id p6so4847761vsr.9
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 27 Aug 2022 14:03:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:from:to:cc;
 bh=f3drPIe1/1Q/il1Fr5VVCqAe/9drcDXfOZegyf65JI8=;
 b=aQlGTajO1h5T4EzlHR1j0dkepOhdKx5wdmMQp+uUEKLe7LhyZ1Ju5T/HwnKiicW5Aa
 +Y/tSvXHl/lolCBFm2lBxGh9IEd2uLT6Mu2K4P9K+qhwaDrT5r9+TIuGrURatfdzIACS
 1BeZYCCCSybO7IDFjJbG8NWA4Nz8fVPtUtGaYDtN2Z5J3ih+0io8eNTrtnNQ/cAB5xME
 h0/8TWGopMiY+ehfEs4Zu+/hSjnBgFBb7lEA8CPNPkOno6o9U6sBQ56OPH9OeFAKf3Jf
 2/L89TOegazkCnzpa1jvmMTKju0dIGPnb2tTx7bIPpXALnEbmVyLlsRKgFgj0qIts3pb
 yfkw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:x-gm-message-state:from:to:cc;
 bh=f3drPIe1/1Q/il1Fr5VVCqAe/9drcDXfOZegyf65JI8=;
 b=A+3ImofdB2o0cAmYyCynOF5p7pZiOcArYWQy+jiQ/unGc6z9oBrKcEOS9C0Agmx+O8
 7OInZlgX+YceFjaT52bWydLo4gGTKpGrj4oC9sWTbnAAr/q9fwy9NO63AupB3C2Ka5KI
 +4GI4DTXKLY6fLn6jAlDfNyeRb6gxt8gu/M8FZYvn3/L2PBQfFu5zRRjwvdPyEcRkMgq
 mL+/37kfykuFpVna91XW2M63lj1R6OzcbV3b5EFAk5bIvpeKCBF70mOPsnNCgBc9ARZx
 nYzdNX7EpXL7Gb6sLuFg3kEhIn5O6+alg2qK/6y3ZQkwSxjn/6wDkLFEuPBz87p4NoXg
 iOSA==
X-Gm-Message-State: ACgBeo3nyRNftDWOW1lP5MhaDYilGeYogB0eo2/GmpnbGtIiPl/yRwIh
 dwdjr77A9Ew83/JunRc9KEe1IKLxJ1BCN0+q9kk=
X-Google-Smtp-Source: AA6agR5ewlkSAX+hZFSivl3xckOHQCpS6kGQKHq7/5PhHCQSkW2/SH8Yvf8jzXTnSOGRy0BHNknM/Q/a1zPNKKY6mE4=
X-Received: by 2002:a67:ec18:0:b0:390:3de8:acc with SMTP id
 d24-20020a67ec18000000b003903de80accmr1471983vso.44.1661634197402; Sat, 27
 Aug 2022 14:03:17 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.9.1661342403.3868.bitcoin-dev@lists.linuxfoundation.org>
 <20220824190958.gklg3riadci3ttgm@artanis>
In-Reply-To: <20220824190958.gklg3riadci3ttgm@artanis>
From: Billy Tetrud <billy.tetrud@gmail.com>
Date: Sat, 27 Aug 2022 16:03:01 -0500
Message-ID: <CAGpPWDb9jPxcZcQ_u+H+K0mbpYdyRU_FAJ6usQy0iJKXn+RPpQ@mail.gmail.com>
To: Ali Sherief <ali@notatether.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000001538d605e73f5c08"
X-Mailman-Approved-At: Sat, 27 Aug 2022 21:07:38 +0000
Subject: Re: [bitcoin-dev] BIP Proposal: Wallet Labels Export Format
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Sat, 27 Aug 2022 21:03:22 -0000

--0000000000001538d605e73f5c08
Content-Type: text/plain; charset="UTF-8"

@Ali Thats some good well thought through and well articulated feedback. I
have one point of contention

> it's important that unnecessary types are kept out of the format. People
are known to leave files lying around on their computer that they don't
need anymore, so these files can find their way via telemetry to
surveillence entities. While we can't specify what users can do with their
exports, we can control the information leak by preventing certain types of
items that we know most users will never use from being exported in the
first place.

This seems to run contrary with your point about letting users be in
control of how they store this. Given that you can always connect together
an output and its address or find the outputs at any address, it doesn't
seem like it would actually leak any more information than just including
addresses. Am I missing something?

On Wed, Aug 24, 2022, 14:44 Ali Sherief via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hi Craig,
>
> This a really good proposal. I studied your BIP and I have some feedback
> on some parts of it.
>
> > The first line in the file is a header, and should be ignored on import.
>
> From past experience and lessons, most notably BIP39, it is important that
> a version byte is defined somewhere in case someone wants to extend it in
> the future, currently there is no version byte which someone can increment
> if somebody wants to extend it. In the unique case of CSV files, you should
> make the header line mandatory (I see you have already implied this, but
> you should make it explicit in the BIP), but instead of a line with columns
> in it, I suggest instead of Reference,Label, you make the format like this:
>
> BIP-wallet-labels,<version>
>
> Since there are two columns per record, this works out nicely. The first
> column can be the name of the BIP - BIPxxxx where the x's are numbers, and
> the second column can be an unsigned 32-bit integer (most significant 8
> bits reserved for version, the remaining for flags, or perhaps the entirety
> for version - but I recommend leaving at least some bits for flags, even if
> they all end up being just "reserved").
>
> You should make importing fail if the header line is not exactly as
> specified - or appropriate, should you decide a different format for the
> header.
>
> > Files exported should use the <tt>.csv</tt> file extension.
> Don't mandate the file extension (read below for why):
>
> > In order to reduce file size while retaining wide accessibility, the CSV
> > file may be compressed using the ZIP file format, using the <tt>.zip</tt>
> > file extension.
> I see three problems with this. The first is more important than the later
> two because it makes them moot points, but I'll mention them anyway so you
> get a background of the situation:
> - The BIP is trying to specify in what file format the export format can
> be written in onto the filesystem. There is no way to enforce this on a BIP
> level (besides, Unix operating systems don't even consider the file
> extension, they use its mimetype). Also specifying this in the BIP will
> prevent modular "Layer 2" protocols and schemes from encoding the Export
> labels into another format - for example Base64 or with their own
> compression algorithm.
>
> Now for the two "moot problems":
> - ZIP does not have good performance or compression ratio, there are
> better algorithms out there like gzip (which also happens to be more
> ubiquitous; nearly all websites are serving HTML compressed with gzip
> compression).
> - ZIP is an archiving format, that happens to have its own compression
> format. Archiving format parsers can have serious vulnerabilities in their
> implementation that can allow malware to swipe private keys and passwords,
> since the primary target for this BIP is wallets. For example, there was
> Zip Slip[1] in 2018, which allows for remote code execution. So the malware
> can even hide in memory until private keys or passwords are written to
> memory, then send them accros the network. Assuming it's targeting a
> specific wallet software it's not hard to carry out at all.
>
> There's two solutions for all this:
> 1. The duck-tape solution: Use some compression algorithm like gzip
> instead of ZIP archive format.
> 2. The "throw it out and buy a new one" solution: Get rid of the optional
> compression specs altogether, because users are responsible for supplying
> the export labels in the first place, so all the compression stuff is
> redundant and should be left up to the user use if they desire to.
>
> I prefer the second solution because it hits the nail at the problem
> directly instead of putting duck tape on it like the first one.
>
> > This <tt>.zip</tt> file may optionally be encrypted using either AES-128
> or
> > AES-256 encryption, which is supported by numerous applications including
> > Winzip and 7-zip.
> > The textual representation of the wallet's extended public key (as
> defined
> > by BIP32, with an <tt>xpub</tt> header) should be used as the password.
> Not specific to AES, but I don't see the benefit of encrypting addresses
> and labels together. Can you please elaborate why this would be desireable?
>
> Like I said though, it's better to leave it up to users to decide how to
> store their exports, since BIPs can't enforce that anyway (additionally,
> the password you propose is insecure - anybody with access to the wallet
> can unlock it, which is not desireable to some users who want their own
> security).
>
> > * Transaction ID (<tt>txid</tt>)
> > * Address
> > * Input (rendered as <tt>txid<index</tt>)
> > * Output (rendered as <tt>txid>index</tt> or <tt>txid:index</tt>)
> Why the need for input and output formats? There is no difference between
> them on the wallet level, because they are always identified with a txid
> and output index. To distinguish between them and hence write them with the
> correct format would require a UTXO set and thus access to a full node,
> otherwise the CSV cannot be verified to be completely well-formed.
>
> Another important point is that practically nobody labels inputs or
> outputs because most people do not know that those things even exist, and
> the rest don't bother to label them.
>
> But the biggest downside to including them is related to the problem of
> information leaking which you make reference to here:
> > In both cases, care must be taken when spending to avoid undesirable
> leaks
> > of private information.
> A CSV dump that has inputs/outputs and addresses mixed together can infer
> the owner of all those items. In fact, A CVS label dump is basically a
> personal information store so everything in it can be correlated as coming
> from the same wallet, so it's important that unnecessary types are kept out
> of the format. People are known to leave files lying around on their
> computer that they don't need anymore, so these files can find their way
> via telemetry to surveillence entities. While we can't specify what users
> can do with their exports, we can control the information leak by
> preventing certain types of items that we know most users will never use
> from being exported in the first place.
>
> > The order in which these records appear is not defined.
> Again, since the primary use case for this BIP is wallets, which likely
> use heirarchical derivation schemes like BIP44, there is a net benefit for
> the addresses to be exported in ascending order of their `address_type`. It
> means that wallets can import them in O(n) time as opposed to O(n^2) time
> spent serially checking in which index the address appears at. Of course,
> this implies that all addresses up to a certain index have to be exported
> into the CSV as well, but most wallets I know of like Core, Electrum
> already store addresses like that.
>
> Also if you do this, you will need to group all the transaction records
> before the address records or vice versa - you can use lexigraphical
> sorting if you want (ie. Addresses before Transactions). The benefit of
> this separation of parts is that wallets can split the imported address
> records from the transaction records internally, and feed them to separate
> functions which set these labels internally.
>
> If you decide on doing it this way, then you need a 3rd column to identify
> the item type, and also you should quote the label (see below). I strongly
> recommend using numbers for identification as opposed to character strings,
> so you don't have to worry about localization or character case issues.
> There is always one unique number, but there could be multiple strings that
> reference the same type. This will complicate importing functions.
>
> If you insist on include Input and Output types then they can both be
> specified as <txid>:<index> if you do this change. They won't be used to
> determine the type anyway.
>
> > The fields may be quoted, but this is unnecessary, as the first comma in
> > the line will always be the delimiter.
> Don't implement it like that, because that will break CSV parsers which
> expect a fixed amount of rows in each record (2 in the header, and some
> rows have >2 rows). It's better to mandate that they should always be
> double-quoted, since only wallets will generate label exports anyway. If
> you plan to use headers then the 3rd column can be blank for it (or you can
> split the version and flags from each other).
>
> > ==Importing==
> >
> > When importing, a naive algorithm may simply match against any reference,
> > but it is possible to disambiguate between transactions, addresses,
> inputs
> > and outputs.
> > For example in the following pseudocode:
> > <pre>
> >   if reference length < 64
> >     Set address label
> >   else if reference length == 64
> >     Set transaction label
> >   else if reference contains '<'
> >     Set input label
> >   else
> >     Set output label
> > </pre>
> The importing code is too naive and in its current form will prevent the
> BIP from getting a number. It is perhaps the single most important part of
> a BIP. When implementing an importer, it should utilize a dedicate item
> type field that unambiguously identifies the item. So the naive importer is
> not good, you need use a 3rd column for that like I explained above, so
> that the importer becomes robust.
>
> In summary (exclamation marks indicate severity - one means low, two means
> medium, and three means high):
>
> 1. Convert the header into a version line with optional flags, otherwise
> nobody can extend this format without compatibility issues (!)
> 2. Get rid of the specs related to file compression (!!!)
> 3. Add a 3rd column for item type (address, transaction etc.) preferably
> as numeric constants and grouping items of one type after items of another
> type, or if you insist on strings, then only recognize their Titlecase
> ASCII versions <spreadsheet software like Excel always tries to titlecase
> the words> (!!)
> 4. Require double quotes around the label (or single quotes if you prefer,
> as long as spreadsheet software doesn't choke on them) (!!)
> 5. Require sorting the records according to the order they are stored in
> the wallet implementation. (!)
> 6. Consider getting rid of Input and Output item types. (!)
> 7. And last and most importantly, please write a more robust importer
> algorithm in the example given by the BIP, because code in BIPs are
> frequently used as references for software. (!!!)
>
> I hope you will consider these points in future revisions of your BIP.
>
> - Ali
>
> [1] https://github.com/snyk/zip-slip-vulnerability
>
> On Wed, 24 Aug 2022 11:18:43 +0200, craigraw@gmail.com wrote:
> > Hi all,
> >
> > I would like to propose a BIP that specifies a format for the export and
> > import of labels from a wallet. While transferring access to funds across
> > wallet applications has been made simple through standards such as BIP39,
> > wallet labels remain siloed and difficult to extract despite their value,
> > particularly in a privacy context.
> >
> > The proposed format is a simple two column CSV file, with the reference
> to
> > a transaction, address, input or output in the first column, and the
> label
> > in the second column. CSV was chosen for its wide accessibility,
> especially
> > to users without specific technical expertise. Similarly, the CSV file
> may
> > be compressed using the ZIP format, and optionally encrypted using AES.
> >
> > The full text of the BIP can be found at
> > https://github.com/craigraw/bips/blob/master/bip-wallet-labels.mediawiki
> > and also copied below.
> >
> > Feedback is appreciated.
> >
> > Thanks,
> > Craig Raw
> >
> > ---
> >
> > <pre>
> >   BIP: wallet-labels
> >   Layer: Applications
> >   Title: Wallet Labels Export Format
> >   Author: Craig Raw <craig@sparrowwallet.com>
> >   Comments-Summary: No comments yet.
> >   Comments-URI:
> > https://github.com/bitcoin/bips/wiki/Comments:BIP-wallet-labels
> >   Status: Draft
> >   Type: Informational
> >   Created: 2022-08-23
> >   License: BSD-2-Clause
> > </pre>
> >
> > ==Abstract==
> >
> > This document specifies a format for the export of labels that may be
> > attached to the transactions, addresses, input and outputs in a wallet.
> >
> > ==Copyright==
> >
> > This BIP is licensed under the BSD 2-clause license.
> >
> > ==Motivation==
> >
> > The export and import of funds across different Bitcoin wallet
> applications
> > is well defined through standards such as BIP39, BIP32, BIP44 etc.
> > These standards are well supported and allow users to move easily between
> > different wallets.
> > There is, however, no defined standard to transfer any labels the user
> may
> > have applied to the transactions, addresses, inputs or outputs in their
> > wallet.
> > The UTXO model that Bitcoin uses makes these labels particularly valuable
> > as they may indicate the source of funds, whether received externally or
> as
> > a result of change from a prior transaction.
> > In both cases, care must be taken when spending to avoid undesirable
> leaks
> > of private information.
> > Labels provide valuable guidance in this regard, and have even become
> > mandatory when spending in several Bitcoin wallets.
> > Allowing users to export their labels in a standardized way ensures that
> > they do not experience lock-in to a particular wallet application.
> > In addition, by using common formats, this BIP seeks to make manual or
> bulk
> > management of labels accessible to users without specific technical
> > expertise.
> >
> > ==Specification==
> >
> > In order to make the import and export of labels as widely accessible as
> > possible, this BIP uses the comma separated values (CSV) format, which is
> > widely supported by consumer, business, and scientific applications.
> > Although the technical specification of CSV in RFC4180 is not always
> > followed, the application of the format in this BIP is simple enough that
> > compatibility should not present a problem.
> > Moreover, the simplicity and forgiving nature of CSV (over for example
> > JSON) lends itself well to bulk label editing using spreadsheet and text
> > editing tools.
> >
> > A CSV export of labels from a wallet must be a UTF-8 encoded text file,
> > containing one record per line, with records containing two fields
> > delimited by a comma.
> > The fields may be quoted, but this is unnecessary, as the first comma in
> > the line will always be the delimiter.
> > The first line in the file is a header, and should be ignored on import.
> > Thereafter, each line represents a record that refers to a label applied
> in
> > the wallet.
> > The order in which these records appear is not defined.
> >
> > The first field in the record contains a reference to the transaction,
> > address, input or output in the wallet.
> > This is specified as one of the following:
> > * Transaction ID (<tt>txid</tt>)
> > * Address
> > * Input (rendered as <tt>txid<index</tt>)
> > * Output (rendered as <tt>txid>index</tt> or <tt>txid:index</tt>)
> >
> > The second field contains the label applied to the reference.
> > Exporting applications may omit records with no labels or labels of zero
> > length.
> > Files exported should use the <tt>.csv</tt> file extension.
> >
> > In order to reduce file size while retaining wide accessibility, the CSV
> > file may be compressed using the ZIP file format, using the <tt>.zip</tt>
> > file extension.
> > This <tt>.zip</tt> file may optionally be encrypted using either AES-128
> or
> > AES-256 encryption, which is supported by numerous applications including
> > Winzip and 7-zip.
> > In order to ensure that weak encryption does not proliferate, importers
> > following this standard must refuse to import <tt>.zip</tt> files
> encrypted
> > with the weaker Zip 2.0 standard.
> > The textual representation of the wallet's extended public key (as
> defined
> > by BIP32, with an <tt>xpub</tt> header) should be used as the password.
> >
> > ==Importing==
> >
> > When importing, a naive algorithm may simply match against any reference,
> > but it is possible to disambiguate between transactions, addresses,
> inputs
> > and outputs.
> > For example in the following pseudocode:
> > <pre>
> >   if reference length < 64
> >     Set address label
> >   else if reference length == 64
> >     Set transaction label
> >   else if reference contains '<'
> >     Set input label
> >   else
> >     Set output label
> > </pre>
> >
> > Importing applications may truncate labels if necessary.
> >
> > ==Test Vectors==
> >
> > The following fragment represents a wallet label export:
> > <pre>
> > Reference,Label
> >
> c3bdad6e7dcd7997e16a5b7b7cf4d8f6079820ff2eedd5fcbb2ad088f767b37b?,Transaction
> > 1A69TXnEM2ms9fMaY9UuiJ7415X7xZaUSg,Address
> > c3bdad6e7dcd7997e16a5b7b7cf4d8f6079820ff2eedd5fcbb2ad088f767b37b?<0,Input
> >
> c3bdad6e7dcd7997e16a5b7b7cf4d8f6079820ff2eedd5fcbb2ad088f767b37b?>0,Output
> >
> c3bdad6e7dcd7997e16a5b7b7cf4d8f6079820ff2eedd5fcbb2ad088f767b37b?:0,Output
> > (alternative)
> > </pre>
> >
> > ==Reference Implementation==
> >
> > TBD
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr"><div dir=3D"auto">@Ali Thats some good well thought throug=
h and well articulated feedback. I have one point of contention<div dir=3D"=
auto"><br></div><div dir=3D"auto">&gt;=C2=A0<span style=3D"font-size:12.8px=
">it&#39;s important that unnecessary types are kept out of the format. Peo=
ple are known to leave files lying around on their computer that they don&#=
39;t need anymore, so these files can find their way via telemetry to surve=
illence entities. While we can&#39;t specify what users can do with their e=
xports, we can control the information leak by preventing certain types of =
items that we know most users will never use from being exported in the fir=
st place.</span></div><div dir=3D"auto"><br></div><div dir=3D"auto">This se=
ems to run contrary with your point about letting users be in control of ho=
w they store this. Given that you can always connect together an output and=
 its address or find the outputs at any address, it doesn&#39;t seem like i=
t would actually leak any more information than just including addresses. A=
m I missing something?=C2=A0</div></div></div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Aug 24, 2022, 14:44 Ali She=
rief via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundatio=
n.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrot=
e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Craig,<br>
<br>
This a really good proposal. I studied your BIP and I have some feedback on=
 some parts of it.<br>
<br>
&gt; The first line in the file is a header, and should be ignored on impor=
t.<br>
<br>
From past experience and lessons, most notably BIP39, it is important that =
a version byte is defined somewhere in case someone wants to extend it in t=
he future, currently there is no version byte which someone can increment i=
f somebody wants to extend it. In the unique case of CSV files, you should =
make the header line mandatory (I see you have already implied this, but yo=
u should make it explicit in the BIP), but instead of a line with columns i=
n it, I suggest instead of Reference,Label, you make the format like this:<=
br>
<br>
BIP-wallet-labels,&lt;version&gt;<br>
<br>
Since there are two columns per record, this works out nicely. The first co=
lumn can be the name of the BIP - BIPxxxx where the x&#39;s are numbers, an=
d the second column can be an unsigned 32-bit integer (most significant 8 b=
its reserved for version, the remaining for flags, or perhaps the entirety =
for version - but I recommend leaving at least some bits for flags, even if=
 they all end up being just &quot;reserved&quot;).<br>
<br>
You should make importing fail if the header line is not exactly as specifi=
ed - or appropriate, should you decide a different format for the header.<b=
r>
<br>
&gt; Files exported should use the &lt;tt&gt;.csv&lt;/tt&gt; file extension=
.<br>
Don&#39;t mandate the file extension (read below for why):<br>
<br>
&gt; In order to reduce file size while retaining wide accessibility, the C=
SV<br>
&gt; file may be compressed using the ZIP file format, using the &lt;tt&gt;=
.zip&lt;/tt&gt;<br>
&gt; file extension.<br>
I see three problems with this. The first is more important than the later =
two because it makes them moot points, but I&#39;ll mention them anyway so =
you get a background of the situation:<br>
- The BIP is trying to specify in what file format the export format can be=
 written in onto the filesystem. There is no way to enforce this on a BIP l=
evel (besides, Unix operating systems don&#39;t even consider the file exte=
nsion, they use its mimetype). Also specifying this in the BIP will prevent=
 modular &quot;Layer 2&quot; protocols and schemes from encoding the Export=
 labels into another format - for example Base64 or with their own compress=
ion algorithm.<br>
<br>
Now for the two &quot;moot problems&quot;:<br>
- ZIP does not have good performance or compression ratio, there are better=
 algorithms out there like gzip (which also happens to be more ubiquitous; =
nearly all websites are serving HTML compressed with gzip compression).<br>
- ZIP is an archiving format, that happens to have its own compression form=
at. Archiving format parsers can have serious vulnerabilities in their impl=
ementation that can allow malware to swipe private keys and passwords, sinc=
e the primary target for this BIP is wallets. For example, there was Zip Sl=
ip[1] in 2018, which allows for remote code execution. So the malware can e=
ven hide in memory until private keys or passwords are written to memory, t=
hen send them accros the network. Assuming it&#39;s targeting a specific wa=
llet software it&#39;s not hard to carry out at all.<br>
<br>
There&#39;s two solutions for all this:<br>
1. The duck-tape solution: Use some compression algorithm like gzip instead=
 of ZIP archive format.<br>
2. The &quot;throw it out and buy a new one&quot; solution: Get rid of the =
optional compression specs altogether, because users are responsible for su=
pplying the export labels in the first place, so all the compression stuff =
is redundant and should be left up to the user use if they desire to.<br>
<br>
I prefer the second solution because it hits the nail at the problem direct=
ly instead of putting duck tape on it like the first one.<br>
<br>
&gt; This &lt;tt&gt;.zip&lt;/tt&gt; file may optionally be encrypted using =
either AES-128 or<br>
&gt; AES-256 encryption, which is supported by numerous applications includ=
ing<br>
&gt; Winzip and 7-zip.<br>
&gt; The textual representation of the wallet&#39;s extended public key (as=
 defined<br>
&gt; by BIP32, with an &lt;tt&gt;xpub&lt;/tt&gt; header) should be used as =
the password.<br>
Not specific to AES, but I don&#39;t see the benefit of encrypting addresse=
s and labels together. Can you please elaborate why this would be desireabl=
e?<br>
<br>
Like I said though, it&#39;s better to leave it up to users to decide how t=
o store their exports, since BIPs can&#39;t enforce that anyway (additional=
ly, the password you propose is insecure - anybody with access to the walle=
t can unlock it, which is not desireable to some users who want their own s=
ecurity).<br>
<br>
&gt; * Transaction ID (&lt;tt&gt;txid&lt;/tt&gt;)<br>
&gt; * Address<br>
&gt; * Input (rendered as &lt;tt&gt;txid&lt;index&lt;/tt&gt;)<br>
&gt; * Output (rendered as &lt;tt&gt;txid&gt;index&lt;/tt&gt; or &lt;tt&gt;=
txid:index&lt;/tt&gt;)<br>
Why the need for input and output formats? There is no difference between t=
hem on the wallet level, because they are always identified with a txid and=
 output index. To distinguish between them and hence write them with the co=
rrect format would require a UTXO set and thus access to a full node, other=
wise the CSV cannot be verified to be completely well-formed.<br>
<br>
Another important point is that practically nobody labels inputs or outputs=
 because most people do not know that those things even exist, and the rest=
 don&#39;t bother to label them.<br>
<br>
But the biggest downside to including them is related to the problem of inf=
ormation leaking which you make reference to here:<br>
&gt; In both cases, care must be taken when spending to avoid undesirable l=
eaks<br>
&gt; of private information.<br>
A CSV dump that has inputs/outputs and addresses mixed together can infer t=
he owner of all those items. In fact, A CVS label dump is basically a perso=
nal information store so everything in it can be correlated as coming from =
the same wallet, so it&#39;s important that unnecessary types are kept out =
of the format. People are known to leave files lying around on their comput=
er that they don&#39;t need anymore, so these files can find their way via =
telemetry to surveillence entities. While we can&#39;t specify what users c=
an do with their exports, we can control the information leak by preventing=
 certain types of items that we know most users will never use from being e=
xported in the first place.<br>
<br>
&gt; The order in which these records appear is not defined.<br>
Again, since the primary use case for this BIP is wallets, which likely use=
 heirarchical derivation schemes like BIP44, there is a net benefit for the=
 addresses to be exported in ascending order of their `address_type`. It me=
ans that wallets can import them in O(n) time as opposed to O(n^2) time spe=
nt serially checking in which index the address appears at. Of course, this=
 implies that all addresses up to a certain index have to be exported into =
the CSV as well, but most wallets I know of like Core, Electrum already sto=
re addresses like that.<br>
<br>
Also if you do this, you will need to group all the transaction records bef=
ore the address records or vice versa - you can use lexigraphical sorting i=
f you want (ie. Addresses before Transactions). The benefit of this separat=
ion of parts is that wallets can split the imported address records from th=
e transaction records internally, and feed them to separate functions which=
 set these labels internally.<br>
<br>
If you decide on doing it this way, then you need a 3rd column to identify =
the item type, and also you should quote the label (see below). I strongly =
recommend using numbers for identification as opposed to character strings,=
 so you don&#39;t have to worry about localization or character case issues=
. There is always one unique number, but there could be multiple strings th=
at reference the same type. This will complicate importing functions.<br>
<br>
If you insist on include Input and Output types then they can both be speci=
fied as &lt;txid&gt;:&lt;index&gt; if you do this change. They won&#39;t be=
 used to determine the type anyway.<br>
<br>
&gt; The fields may be quoted, but this is unnecessary, as the first comma =
in<br>
&gt; the line will always be the delimiter.<br>
Don&#39;t implement it like that, because that will break CSV parsers which=
 expect a fixed amount of rows in each record (2 in the header, and some ro=
ws have &gt;2 rows). It&#39;s better to mandate that they should always be =
double-quoted, since only wallets will generate label exports anyway. If yo=
u plan to use headers then the 3rd column can be blank for it (or you can s=
plit the version and flags from each other).<br>
<br>
&gt; =3D=3DImporting=3D=3D<br>
&gt;<br>
&gt; When importing, a naive algorithm may simply match against any referen=
ce,<br>
&gt; but it is possible to disambiguate between transactions, addresses, in=
puts<br>
&gt; and outputs.<br>
&gt; For example in the following pseudocode:<br>
&gt; &lt;pre&gt;<br>
&gt;=C2=A0 =C2=A0if reference length &lt; 64<br>
&gt;=C2=A0 =C2=A0 =C2=A0Set address label<br>
&gt;=C2=A0 =C2=A0else if reference length =3D=3D 64<br>
&gt;=C2=A0 =C2=A0 =C2=A0Set transaction label<br>
&gt;=C2=A0 =C2=A0else if reference contains &#39;&lt;&#39;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Set input label<br>
&gt;=C2=A0 =C2=A0else<br>
&gt;=C2=A0 =C2=A0 =C2=A0Set output label<br>
&gt; &lt;/pre&gt;<br>
The importing code is too naive and in its current form will prevent the BI=
P from getting a number. It is perhaps the single most important part of a =
BIP. When implementing an importer, it should utilize a dedicate item type =
field that unambiguously identifies the item. So the naive importer is not =
good, you need use a 3rd column for that like I explained above, so that th=
e importer becomes robust.<br>
<br>
In summary (exclamation marks indicate severity - one means low, two means =
medium, and three means high):<br>
<br>
1. Convert the header into a version line with optional flags, otherwise no=
body can extend this format without compatibility issues (!)<br>
2. Get rid of the specs related to file compression (!!!)<br>
3. Add a 3rd column for item type (address, transaction etc.) preferably as=
 numeric constants and grouping items of one type after items of another ty=
pe, or if you insist on strings, then only recognize their Titlecase ASCII =
versions &lt;spreadsheet software like Excel always tries to titlecase the =
words&gt; (!!)<br>
4. Require double quotes around the label (or single quotes if you prefer, =
as long as spreadsheet software doesn&#39;t choke on them) (!!)<br>
5. Require sorting the records according to the order they are stored in th=
e wallet implementation. (!)<br>
6. Consider getting rid of Input and Output item types. (!)<br>
7. And last and most importantly, please write a more robust importer algor=
ithm in the example given by the BIP, because code in BIPs are frequently u=
sed as references for software. (!!!)<br>
<br>
I hope you will consider these points in future revisions of your BIP.<br>
<br>
- Ali<br>
<br>
[1] <a href=3D"https://github.com/snyk/zip-slip-vulnerability" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://github.com/snyk/zip-slip-vulner=
ability</a><br>
<br>
On Wed, 24 Aug 2022 11:18:43 +0200, <a href=3D"mailto:craigraw@gmail.com" r=
el=3D"noreferrer" target=3D"_blank">craigraw@gmail.com</a> wrote:<br>
&gt; Hi all,<br>
&gt;<br>
&gt; I would like to propose a BIP that specifies a format for the export a=
nd<br>
&gt; import of labels from a wallet. While transferring access to funds acr=
oss<br>
&gt; wallet applications has been made simple through standards such as BIP=
39,<br>
&gt; wallet labels remain siloed and difficult to extract despite their val=
ue,<br>
&gt; particularly in a privacy context.<br>
&gt;<br>
&gt; The proposed format is a simple two column CSV file, with the referenc=
e to<br>
&gt; a transaction, address, input or output in the first column, and the l=
abel<br>
&gt; in the second column. CSV was chosen for its wide accessibility, espec=
ially<br>
&gt; to users without specific technical expertise. Similarly, the CSV file=
 may<br>
&gt; be compressed using the ZIP format, and optionally encrypted using AES=
.<br>
&gt;<br>
&gt; The full text of the BIP can be found at<br>
&gt; <a href=3D"https://github.com/craigraw/bips/blob/master/bip-wallet-lab=
els.mediawiki" rel=3D"noreferrer noreferrer" target=3D"_blank">https://gith=
ub.com/craigraw/bips/blob/master/bip-wallet-labels.mediawiki</a><br>
&gt; and also copied below.<br>
&gt;<br>
&gt; Feedback is appreciated.<br>
&gt;<br>
&gt; Thanks,<br>
&gt; Craig Raw<br>
&gt;<br>
&gt; ---<br>
&gt;<br>
&gt; &lt;pre&gt;<br>
&gt;=C2=A0 =C2=A0BIP: wallet-labels<br>
&gt;=C2=A0 =C2=A0Layer: Applications<br>
&gt;=C2=A0 =C2=A0Title: Wallet Labels Export Format<br>
&gt;=C2=A0 =C2=A0Author: Craig Raw &lt;<a href=3D"mailto:craig@sparrowwalle=
t.com" rel=3D"noreferrer" target=3D"_blank">craig@sparrowwallet.com</a>&gt;=
<br>
&gt;=C2=A0 =C2=A0Comments-Summary: No comments yet.<br>
&gt;=C2=A0 =C2=A0Comments-URI:<br>
&gt; <a href=3D"https://github.com/bitcoin/bips/wiki/Comments:BIP-wallet-la=
bels" rel=3D"noreferrer noreferrer" target=3D"_blank">https://github.com/bi=
tcoin/bips/wiki/Comments:BIP-wallet-labels</a><br>
&gt;=C2=A0 =C2=A0Status: Draft<br>
&gt;=C2=A0 =C2=A0Type: Informational<br>
&gt;=C2=A0 =C2=A0Created: 2022-08-23<br>
&gt;=C2=A0 =C2=A0License: BSD-2-Clause<br>
&gt; &lt;/pre&gt;<br>
&gt;<br>
&gt; =3D=3DAbstract=3D=3D<br>
&gt;<br>
&gt; This document specifies a format for the export of labels that may be<=
br>
&gt; attached to the transactions, addresses, input and outputs in a wallet=
.<br>
&gt;<br>
&gt; =3D=3DCopyright=3D=3D<br>
&gt;<br>
&gt; This BIP is licensed under the BSD 2-clause license.<br>
&gt;<br>
&gt; =3D=3DMotivation=3D=3D<br>
&gt;<br>
&gt; The export and import of funds across different Bitcoin wallet applica=
tions<br>
&gt; is well defined through standards such as BIP39, BIP32, BIP44 etc.<br>
&gt; These standards are well supported and allow users to move easily betw=
een<br>
&gt; different wallets.<br>
&gt; There is, however, no defined standard to transfer any labels the user=
 may<br>
&gt; have applied to the transactions, addresses, inputs or outputs in thei=
r<br>
&gt; wallet.<br>
&gt; The UTXO model that Bitcoin uses makes these labels particularly valua=
ble<br>
&gt; as they may indicate the source of funds, whether received externally =
or as<br>
&gt; a result of change from a prior transaction.<br>
&gt; In both cases, care must be taken when spending to avoid undesirable l=
eaks<br>
&gt; of private information.<br>
&gt; Labels provide valuable guidance in this regard, and have even become<=
br>
&gt; mandatory when spending in several Bitcoin wallets.<br>
&gt; Allowing users to export their labels in a standardized way ensures th=
at<br>
&gt; they do not experience lock-in to a particular wallet application.<br>
&gt; In addition, by using common formats, this BIP seeks to make manual or=
 bulk<br>
&gt; management of labels accessible to users without specific technical<br=
>
&gt; expertise.<br>
&gt;<br>
&gt; =3D=3DSpecification=3D=3D<br>
&gt;<br>
&gt; In order to make the import and export of labels as widely accessible =
as<br>
&gt; possible, this BIP uses the comma separated values (CSV) format, which=
 is<br>
&gt; widely supported by consumer, business, and scientific applications.<b=
r>
&gt; Although the technical specification of CSV in RFC4180 is not always<b=
r>
&gt; followed, the application of the format in this BIP is simple enough t=
hat<br>
&gt; compatibility should not present a problem.<br>
&gt; Moreover, the simplicity and forgiving nature of CSV (over for example=
<br>
&gt; JSON) lends itself well to bulk label editing using spreadsheet and te=
xt<br>
&gt; editing tools.<br>
&gt;<br>
&gt; A CSV export of labels from a wallet must be a UTF-8 encoded text file=
,<br>
&gt; containing one record per line, with records containing two fields<br>
&gt; delimited by a comma.<br>
&gt; The fields may be quoted, but this is unnecessary, as the first comma =
in<br>
&gt; the line will always be the delimiter.<br>
&gt; The first line in the file is a header, and should be ignored on impor=
t.<br>
&gt; Thereafter, each line represents a record that refers to a label appli=
ed in<br>
&gt; the wallet.<br>
&gt; The order in which these records appear is not defined.<br>
&gt;<br>
&gt; The first field in the record contains a reference to the transaction,=
<br>
&gt; address, input or output in the wallet.<br>
&gt; This is specified as one of the following:<br>
&gt; * Transaction ID (&lt;tt&gt;txid&lt;/tt&gt;)<br>
&gt; * Address<br>
&gt; * Input (rendered as &lt;tt&gt;txid&lt;index&lt;/tt&gt;)<br>
&gt; * Output (rendered as &lt;tt&gt;txid&gt;index&lt;/tt&gt; or &lt;tt&gt;=
txid:index&lt;/tt&gt;)<br>
&gt;<br>
&gt; The second field contains the label applied to the reference.<br>
&gt; Exporting applications may omit records with no labels or labels of ze=
ro<br>
&gt; length.<br>
&gt; Files exported should use the &lt;tt&gt;.csv&lt;/tt&gt; file extension=
.<br>
&gt;<br>
&gt; In order to reduce file size while retaining wide accessibility, the C=
SV<br>
&gt; file may be compressed using the ZIP file format, using the &lt;tt&gt;=
.zip&lt;/tt&gt;<br>
&gt; file extension.<br>
&gt; This &lt;tt&gt;.zip&lt;/tt&gt; file may optionally be encrypted using =
either AES-128 or<br>
&gt; AES-256 encryption, which is supported by numerous applications includ=
ing<br>
&gt; Winzip and 7-zip.<br>
&gt; In order to ensure that weak encryption does not proliferate, importer=
s<br>
&gt; following this standard must refuse to import &lt;tt&gt;.zip&lt;/tt&gt=
; files encrypted<br>
&gt; with the weaker Zip 2.0 standard.<br>
&gt; The textual representation of the wallet&#39;s extended public key (as=
 defined<br>
&gt; by BIP32, with an &lt;tt&gt;xpub&lt;/tt&gt; header) should be used as =
the password.<br>
&gt;<br>
&gt; =3D=3DImporting=3D=3D<br>
&gt;<br>
&gt; When importing, a naive algorithm may simply match against any referen=
ce,<br>
&gt; but it is possible to disambiguate between transactions, addresses, in=
puts<br>
&gt; and outputs.<br>
&gt; For example in the following pseudocode:<br>
&gt; &lt;pre&gt;<br>
&gt;=C2=A0 =C2=A0if reference length &lt; 64<br>
&gt;=C2=A0 =C2=A0 =C2=A0Set address label<br>
&gt;=C2=A0 =C2=A0else if reference length =3D=3D 64<br>
&gt;=C2=A0 =C2=A0 =C2=A0Set transaction label<br>
&gt;=C2=A0 =C2=A0else if reference contains &#39;&lt;&#39;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Set input label<br>
&gt;=C2=A0 =C2=A0else<br>
&gt;=C2=A0 =C2=A0 =C2=A0Set output label<br>
&gt; &lt;/pre&gt;<br>
&gt;<br>
&gt; Importing applications may truncate labels if necessary.<br>
&gt;<br>
&gt; =3D=3DTest Vectors=3D=3D<br>
&gt;<br>
&gt; The following fragment represents a wallet label export:<br>
&gt; &lt;pre&gt;<br>
&gt; Reference,Label<br>
&gt; c3bdad6e7dcd7997e16a5b7b7cf4d8f6079820ff2eedd5fcbb2ad088f767b37b?,Tran=
saction<br>
&gt; 1A69TXnEM2ms9fMaY9UuiJ7415X7xZaUSg,Address<br>
&gt; c3bdad6e7dcd7997e16a5b7b7cf4d8f6079820ff2eedd5fcbb2ad088f767b37b?&lt;0=
,Input<br>
&gt; c3bdad6e7dcd7997e16a5b7b7cf4d8f6079820ff2eedd5fcbb2ad088f767b37b?&gt;0=
,Output<br>
&gt; c3bdad6e7dcd7997e16a5b7b7cf4d8f6079820ff2eedd5fcbb2ad088f767b37b?:0,Ou=
tput<br>
&gt; (alternative)<br>
&gt; &lt;/pre&gt;<br>
&gt;<br>
&gt; =3D=3DReference Implementation=3D=3D<br>
&gt;<br>
&gt; TBD<br>
<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" rel=3D"noreferrer"=
 target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linuxfoundati=
on.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--0000000000001538d605e73f5c08--