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
|
Return-Path: <marcel@jamin.net>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id F29F98A5
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 15 Dec 2017 06:27:12 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-it0-f42.google.com (mail-it0-f42.google.com
[209.85.214.42])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 52A6AE5
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 15 Dec 2017 06:27:12 +0000 (UTC)
Received: by mail-it0-f42.google.com with SMTP id z6so17031964iti.4
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 14 Dec 2017 22:27:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=jamin-net.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-transfer-encoding;
bh=xmOB/48ytpVDQHBnck7CCr4pD+PJsE3OWl1NOEIloTM=;
b=CO5nC2/41v23E3vSXLgJfDyJTwvRjKVL6fe1zpFLansrorHrJhzTKGgmTXK/szquoO
Znym86qxhOxFIUCCrThwEyA1lB8UGRIFMC5rwjM1kMviohhqY8OyMp8G7zHifp/rBPpi
bVnbpiagiMkfwEX7ca6FK2wyfHB9cMEFHWzMud96ezgmQBmkyNVgnrTf7CKzjwh2Z4dk
URnTCTNdnjyuQpDguB83OueF/XIjM1t2S+wYGKKz4LfucdYwHdI/VdqDFweaRsIjWK5V
gBvqj8Lm/oBSylw6bAzKOF8TSbJ/2kCwUfYw8v5xBViTOV5mX50bSy0pI5P8x/jfw4N1
OETw==
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:content-transfer-encoding;
bh=xmOB/48ytpVDQHBnck7CCr4pD+PJsE3OWl1NOEIloTM=;
b=BdfG5587xk+VmWBCCJuzM3k501ytnXKbo8fo3VhXvAzhVw3Xl/WBeF7EAermRmljc0
vzfDEb23NmPhoB5mgAm8g0OQPx/2TTxYrlYXxYeSYohFJJalh3P2bCltPLVoV4PMj5DP
lFzDmHYw4+byH2KJKf/ogqcqV5mGWTU4orZ9wd742pff/kG/4qD6YYqSeOY6KeXJsoJZ
nj56xLcr0YOMOcCAMbLM6tCgYNOi591cljTU5xMYcw0n8SYG9h89xSCyrMpagnfmEjyq
ijNrBsxsU+PLwhn2Xv6OwEvDERjUPVQ2qADo1BsjsGTq03d9uMnc5RTvMD2tbdvvCjHI
JMuw==
X-Gm-Message-State: AKGB3mKbM2XchEL9GfWWt/AMGmELuhF1Y5QhboZ5JAFEAjXoiMfDGrO3
sWlZJZk/0klifl4XU8XFdtAqplDAWUoOqlr7Tjvl467k9Go=
X-Google-Smtp-Source: ACJfBosNEA11//373Wao23pNebv5k6YFKvilwrU9TMxc2wEAMKEaAsJzOu4k+/GZmoC0nFjU3vce7XT8B0JvW8CB6Zw=
X-Received: by 10.107.157.197 with SMTP id g188mr10365709ioe.92.1513319231373;
Thu, 14 Dec 2017 22:27:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.2.35.140 with HTTP; Thu, 14 Dec 2017 22:27:10 -0800 (PST)
In-Reply-To: <CAAt2M19ZrbvrKc+mz1LEKrM2AuGH01gN+i9w8zSvdmazommMxg@mail.gmail.com>
References: <CAJR7vkqcBo+o9BL8sK1TBqqNUNSMWdut_aL_YMXse8rDC2ju9A@mail.gmail.com>
<20171213213607.ijlvqwpdaokucgi6@fedora-23-dvm>
<CAAUq485pTYs++FY9GkAt64gvba_Mngzpui7TWXdQM-x9GyAQdg@mail.gmail.com>
<CAAt2M19ZrbvrKc+mz1LEKrM2AuGH01gN+i9w8zSvdmazommMxg@mail.gmail.com>
From: Marcel Jamin <marcel@jamin.net>
Date: Fri, 15 Dec 2017 07:27:10 +0100
Message-ID: <CAAUq487ijoaWV46YHSS_tRak8gigT7jvfUBQ=mRntkfz9KV57Q@mail.gmail.com>
To: Natanael <natanael.l@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,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: Fri, 15 Dec 2017 08:37:16 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Proposal: Utilization of bits denomination
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Dec 2017 06:27:13 -0000
I think one could make the argument that the only people who talk
about and understand 24 bit audio or 256 bit cryptography are the ones
who can tell the difference very easily.
To me, your example seems to try hard to make the case for a problem
that won't exist in reality.
Bitcoin (BTC), Millibitcoin (mBTC) and Microbitcoin (=C2=B5BTC) is the
>correct< approach. It's tidy, systematic and precise. But that won't
stop people from using something that's easier to deal with as I just
had to google the =C2=B5 character again.
Let's also keep in mind that Coinbase has been using "bits" as the
default for over 2 years now:
https://blog.coinbase.com/bits-is-the-new-default-and-all-new-users-get-100=
-bits-for-free-9165f757594b
Just from a linguistic standpoint, chances are we'll end up with bits
anyway. Why fight it? We don't have a SI prefix educational mandate.
Marcel
On 14 December 2017 at 23:01, Natanael <natanael.l@gmail.com> wrote:
>
> Reposting /u/BashCo's post on reddit here, for visibility:
>
> ---8<---------------------------------------------------------------
>
>> Before anyone says 'bits' are too confusing because it's a computer
>> science term, here's a list of homonyms
>> [https://en.wikipedia.org/wiki/List_of_true_homonyms] that you use every
>> day. Homonyms are fine because our brains are able to interpret language
>> based on context, so it's a non-argument.
>
>
> This ignores the fact that there exists multiple meanings of bits *within
> the same context*, and that beginners likely can't tell them apart.
>
> Feel free to try it yourself - talk about Bitcoin "bits" of a particular
> value with somebody who doesn't understand Bitcoin. Then explain that th=
e
> cryptography uses 256 bit keys. I would be surprised if you could find
> somebody who would not be confused by that.
>
> Let's say a website says a song is 24 bits. Was that 24 bit audio resolut=
ion
> or 24 bit price? Somebody writes about 256 bit keys, are that their size =
or
> value?
>
> You guys here can probably tell the difference. Can everybody...? Bits wi=
ll
> cause confusion, because plenty of people will not be able to tell these
> apart. They will not know WHEN to apply one definition or the other.
>
> https://www.reddit.com/r/bitcoin/comments/24m3nb/_/ch8gua7
>
>
|
