From: Clark Moody <clark@clarkmoody•com>
To: damgaard.martin@gmail•com,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Suggestion for a universal bitcoin value scale
Date: Wed, 12 Sep 2018 09:54:15 -0500 [thread overview]
Message-ID: <CAHGSxGuZyZYH-v8ZtjGNJX_2jiEAcpXe2i6OWw2CiJWpnNJdzg@mail.gmail.com> (raw)
In-Reply-To: <5b98b2e7.1c69fb81.2a827.102b@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 2445 bytes --]
This is the sort of thing I expect to emerge from the places that use
Bitcoin "on the street." We should be watching how local wallet software
displays bitcoin amounts, letting the standards write themselves over time.
The units debate (bits, millibits, etc) has been going on nearly as long as
I've known about Bitcoin and yet most tools display standard bitcoin
amounts (1 unit = 1e8 satoshi).
-Clark
On Wed, Sep 12, 2018 at 8:41 AM Martin Damgaard via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> A very good point. I have realized the immature nature of my suggestion
> due to this and a number of other good remarks, and will like to retract
> the initial suggestion.
>
> Thank you and all the best
>
> Martin Damgaard
>
>
>
> *Fra: *Karl-Johan Alm <karljohan-alm@garage•co.jp>
> *Sendt: *12. september 2018 08:14
> *Til: *damgaard.martin@gmail•com; Bitcoin Protocol Discussion
> <bitcoin-dev@lists•linuxfoundation.org>
> *Emne: *Re: [bitcoin-dev] Suggestion for a universal bitcoin value scale
>
>
>
> A potential problem is that it would be a new attack vector to simply
>
> color something to appear as e.g. 10x more than it really is, if
>
> everyone started using this system.
>
> On Sun, Aug 19, 2018 at 5:27 AM 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
>
> >
>
> > _______________________________________________
>
> > bitcoin-dev mailing list
>
> > 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
>
[-- Attachment #2: Type: text/html, Size: 4795 bytes --]
prev parent reply other threads:[~2018-09-12 14:54 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
2018-09-12 6:13 ` Karl-Johan Alm
2018-09-12 6:32 ` damgaard.martin
2018-09-12 14:54 ` Clark Moody [this message]
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=CAHGSxGuZyZYH-v8ZtjGNJX_2jiEAcpXe2i6OWw2CiJWpnNJdzg@mail.gmail.com \
--to=clark@clarkmoody$(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