summaryrefslogtreecommitdiff
path: root/d0/6c74e0acafa4d4f5470370e0036ec3eda45d8a
blob: 52eca7f3605bd50a28d1dc33824b579dc7a6094b (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
Return-Path: <tomz@freedommail.ch>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 367FF5A9
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 17 Jul 2017 13:40:36 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mx.kolabnow.com (mx.kolabnow.com [95.128.36.41])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1658F151
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 17 Jul 2017 13:40:35 +0000 (UTC)
Received: from localhost (unknown [127.0.0.1])
	by ext-mx-out003.mykolab.com (Postfix) with ESMTP id 2F86EA62
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 17 Jul 2017 15:40:33 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kolabnow.com; h=
	content-type:content-type:content-transfer-encoding:mime-version
	:references:in-reply-to:message-id:date:date:subject:subject
	:from:from:received:received:received; s=dkim20160331; t=
	1500298831; x=1500298853; bh=F7bGSqQ3lDSv8ymhtYeOVatKDfZCAtdmSu8
	xV/cgD/E=; b=Z+WozwCpKJ6eqmA/8ozvTqa1ypXIF+4c6i4/IXYj/nV9oaqgZ4o
	hNIu2S6QVAAlG83sSLo5RXSukKnAOhHonhRgvK/WNeOc2xvQkSWt41qO6karVB+n
	vYcWS5CWt7gQgYfvg0vNmBOxkH/HUPy60rnpE7NIHXWIPQ6YYBeURC493ScTgGQu
	8Uz4t+oMaa7xGpztZ9gVeNT4rWVr9Ed1WgiuOqLFBSaineNJ1oScG7ab4InY3zEy
	I9CaoE2UaW66PL6brgBcBMbvW4uzt3IjDCKQ++xy6SB5sjecij8GHHiw4V2C5pd8
	DvmUHRvbG7S6Hw9x6DIlUmGtTpxVoR73s4SFJzUYXjsBocL+bbCMHvgwFfLZpKvp
	j9ZC3GXCOSUdWv3UdAlKXwaCoTAIJzyxn0DoRazLvleQDZnS7YBcxZuyNghNUnao
	WNhRmJF1LyJNphlxNvN1ZKdyUgnVfUy7qloiW2zi0zKYOh2NG5TApfhxBOAOCadF
	cNetBqvph26d9o7JNTS4vMr0WmcAzKaFMd+4FFAGO00AvjMXXkY2ig8GpeaN4xyK
	bautRe0oiQbo5My/Hush6ZVO2d90htwgvQPtvNpynQZ1rZ3L6v7/9s3w96JNykqo
	6ZBbPPhJqKxYcZu2AqsZCj4WA0stCSyu7fSqi78M7Ug77LoPrrXRDWIc=
X-Virus-Scanned: amavisd-new at mykolab.com
Received: from mx.kolabnow.com ([127.0.0.1])
	by localhost (ext-mx-out003.mykolab.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 3TeezjzoATxn
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 17 Jul 2017 15:40:31 +0200 (CEST)
Received: from int-mx003.mykolab.com (unknown [10.9.13.3])
	by ext-mx-out003.mykolab.com (Postfix) with ESMTPS id B9BBD3A7
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 17 Jul 2017 15:40:31 +0200 (CEST)
Received: from ext-subm003.mykolab.com (unknown [10.9.6.3])
	by int-mx003.mykolab.com (Postfix) with ESMTPS id A8BC01F95
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 17 Jul 2017 15:40:31 +0200 (CEST)
From: Tom Zander <tomz@freedommail.ch>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Date: Mon, 17 Jul 2017 15:40:29 +0200
Message-ID: <1695234.eLYGsKu2sb@strawberry>
In-Reply-To: <CAHGSxGs8Dko1UeZbRLN0VEDfcV9t6fONv3_N48hV36wTzLwu1w@mail.gmail.com>
References: <CAHGSxGs8Dko1UeZbRLN0VEDfcV9t6fONv3_N48hV36wTzLwu1w@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID 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: Mon, 17 Jul 2017 15:40:32 +0000
Subject: Re: [bitcoin-dev] A BIP proposal for conveniently referring to
	confirmed transactions
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, 17 Jul 2017 13:40:36 -0000

On Friday, 14 July 2017 20:43:37 CEST Clark Moody via bitcoin-dev wrote:
> I can understand the desire to keep all reference strings to the nice
> 14-character version by keeping the data payload to 40 bits

I=E2=80=99m not so clear on this, to be honest.

What is the point of having a user-readable tx-reference?

In the actual blockchain you will still be using txid, and if you want to=20
change that then a less readable but more compact format is useful because=
=20
we want to optimize for space, not for human comprehention.

Another usecase I can come up with is you wanting to spend a specific outpu=
t,=20
or you reporting a specific tx as proof to a merchant (or tax office).

=46or any such usecases you sill need to actually provide a proof of holdin=
g=20
the private keys and using a human-readable format just doesn=E2=80=99t see=
m to make=20
much sense because a cryptographic proof of ownership is not going to be=20
readable however hard you try.

Apologies for missing the point,
can you list one or two usecases that you can see this being used for?
=2D-=20
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel