From: rhavar@protonmail•com
To: "damgaard.martin@gmail•com" <damgaard.martin@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Suggestion for a universal bitcoin value scale
Date: Mon, 20 Aug 2018 23:36:14 +0000 [thread overview]
Message-ID: <xlH72fF0W83RnOFpO_YJZg8i72LT5xIliO623-2AkwrB1FdxS7Z-wnV8F7OpYm5LXwcQqcfx3o_Z-Y-tP6Dt7GpNqDH9DFnjTekJtXa7oAI=@protonmail.com> (raw)
In-Reply-To: <5b787d19.1c69fb81.e0628.771a@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 1830 bytes --]
I think you have correctly identified dealing with small amounts while working in the "bitcoin" denomination as a major pain point, and I will go as far as agreeing that a standard color coding would help people eyeball what 0.000011 BTC means if they were used to seeing the same color pallet.
However, I don't think it's a good solution. I strongly suspect very few services or wallets are going to be willing to adopt such a thing as it'll make their design look ridiculous and it's cumbersome to type.
Furthermore, my experience in using BIP76 (Bits Denomination) in several services with people of varying levels of familiarity to be entirely positive, and in my strong believe a vastly superior solution that should be advocated and used more.
And BTW i think what would help the readability of the "bitcoin" denomination more than colors if it was standard to always write it to 8 decimal places (e.g. 0.00001100 BTC) which I think is a bit more useful in allowing people to eyeball the size.
-Ryan
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On August 18, 2018 1:10 PM, Martin Damgaard via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> Hi bitcoin-dev@lists•linuxfoundation.org
>
> Here is my humble attempt to make a contribution to the impressive work that you all are doing.
>
> I am unfamiliar with the normal BIP procedures. I have therefore just tried to follow the example of BIP 176 by Jimmy Song, in order make something similar. I suggest a universal bitcoin value color scale, for tackling the same decimal problem, as identified by the BIP 176 proposal.
>
> I have attached the document in three different formats (*.rtf, *.pdf and *.docx) as I do not know your preferred format. I hope you will find my suggestion useful.
>
> Thank you and all the best
>
> Martin Damgaard
[-- Attachment #2: Type: text/html, Size: 2719 bytes --]
next prev parent reply other threads:[~2018-08-20 23:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-18 20:10 damgaard.martin
2018-08-19 11:42 ` Rodolfo Novak
[not found] ` <CAJS4p67a+47PimeSizBsAb9nanjaOdgB41hDQXoKFj9OxMqMFA@mail.gmail.com>
2018-08-19 14:21 ` damgaard.martin
2018-08-20 23:36 ` rhavar [this message]
2018-09-12 6:13 ` Karl-Johan Alm
2018-09-12 6:32 ` damgaard.martin
2018-09-12 14:54 ` Clark Moody
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='xlH72fF0W83RnOFpO_YJZg8i72LT5xIliO623-2AkwrB1FdxS7Z-wnV8F7OpYm5LXwcQqcfx3o_Z-Y-tP6Dt7GpNqDH9DFnjTekJtXa7oAI=@protonmail.com' \
--to=rhavar@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=damgaard.martin@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox