From: <damgaard.martin@gmail•com>
To: "Adán Sánchez de Pedro Crespo" <adan@stampery•co>,
"bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Suggestion for a universal bitcoin value scale
Date: Sun, 19 Aug 2018 16:21:55 +0200 [thread overview]
Message-ID: <5b797d04.1c69fb81.c5a5.9f78@mx.google.com> (raw)
In-Reply-To: <CAJS4p67a+47PimeSizBsAb9nanjaOdgB41hDQXoKFj9OxMqMFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1830 bytes --]
Hi
I have made a GitHub version of the suggestion:
https://github.com/damse0045/Universal-bitcoin-value-color-scale./tree/master
where I have collected the commons made to the first version in a remarks-file.
I will try to make a new version incorporation the different commons, and if anyone would like to help they will be more than welcome to join.
All kind of suggestions are more than welcome, and thank you for the good points made so far.
All the best
Martin
Fra: Adán Sánchez de Pedro Crespo
Sendt: 19. august 2018 11:11
Til: damgaard.martin@gmail•com; bitcoin-dev@lists•linuxfoundation.org
Emne: Re: [bitcoin-dev] Suggestion for a universal bitcoin value scale
It would be great if you could submit this as a markdown document published somewhere with version control, such as GitHub. That'd make life easier for anyone willing to contribute to your proposal.
On Sat, 18 Aug 2018 22:26 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
[-- Attachment #2: Type: text/html, Size: 5459 bytes --]
next prev parent reply other threads:[~2018-08-19 14:21 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 [this message]
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
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=5b797d04.1c69fb81.c5a5.9f78@mx.google.com \
--to=damgaard.martin@gmail$(echo .)com \
--cc=adan@stampery$(echo .)co \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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