public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tamas Blummer <tamas@bitsofproof.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] "bits": Unit of account
Date: Sun, 20 Apr 2014 17:05:47 +0200	[thread overview]
Message-ID: <DFFB1B2C-F10B-4CF7-9D01-F6A27F9FA229@bitsofproof.com> (raw)
In-Reply-To: <CAPg+sBha=cUHOWcU29yLrC4WTy5EghOGpVGAcQ8S0fuMvpLeRw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 4001 bytes --]

Here is an earlier reference to bits:

https://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg04248.html

I forgot that Alan Reiner was also supporting a unit equals to bits :

https://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg04264.html

and here the earlier going back to March 2013 and a poll at that time pushing for XBT being 1 bit

https://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg04256.html

Regards,

Tamas Blummer
http://bitsofproof.com

On 20.04.2014, at 16:53, Pieter Wuille <pieter.wuille@gmail.com> wrote:

> I told him specifically to bring it here (on a pull request for
> Bitcoin Core), as there is no point in making such convention changes
> to just one client.
> 
> I wasn't aware of any discussion about the "bits" proposal here before.
> 
> On Sun, Apr 20, 2014 at 4:28 PM, Tamas Blummer <tamas@bitsofproof.com> wrote:
>> People on this list are mostly engineers who have no problem dealing with
>> magnitudes and have rather limited empathy for people who have a problem
>> with them.
>> They also tend to think, that because they invented money 2.0 they would not
>> need to care of finance's or people's current customs.
>> 
>> The importance of their decisions in these questions will fade as people
>> already use wallets other than the core.
>> 
>> Bring this particular discussion elsewhere, to the wallet developer.
>> 
>> BTW the topic was discussed here several times, you have my support and Jeff
>> Garzik's.
>> 
>> Regards,
>> 
>> Tamas Blummer
>> http://bitsofproof.com
>> 
>> On 20.04.2014, at 15:15, Rob Golding <rob.golding@astutium.com> wrote:
>> 
>> The average person is not going to be confident that the prefix they
>> are using is the correct one,
>> 
>> 
>> The use of any 'prefix' is one of choice and entirely unnecessary, and there
>> are already established 'divisions' in u/mBTC for those that feel they need
>> to use such things.
>> 
>> people WILL send 1000x more or less than
>> intended if we go down this road,
>> 
>> 
>> Exceptionally unlikely - I deal every day with currencies with 0, 2 and 3
>> dp's in amount ranging from 'under 1 whole unit' to tens of thousands - Not
>> once in 20 years has anyone ever 'sent' more or less than intended - oh,
>> they've 'intended' to underpay just fine, but never *unintended*.
>> 
>> I propose that users are offered a preference to denominate the
>> Bitcoin currency in a unit called a bit. Where one bitcoin (BTC)
>> equals one million bits (bits) and one bit equals 100 satoshis.
>> 
>> 
>> I propose that for people unable to understand what a bitcoin is, they can
>> just use satoshi's and drop this entire proposal.
>> 
>> Rob
>> 
>> 
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/NeoTech
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/NeoTech
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>> 
> 


[-- Attachment #1.2: Type: text/html, Size: 7734 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2014-04-20 15:05 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-20 12:35 [Bitcoin-development] "bits": Unit of account Mike Gehl
2014-04-20 13:15 ` Rob Golding
2014-04-20 14:28   ` Tamas Blummer
2014-04-20 14:52     ` Christophe Biocca
2014-04-21  8:52       ` Thomas Voegtlin
2014-04-21  9:34         ` Tamas Blummer
2014-04-22 14:55           ` Natanael
2014-04-20 14:53     ` Pieter Wuille
2014-04-20 15:05       ` Tamas Blummer [this message]
2014-04-20 15:50         ` Alan Reiner
2014-04-20 16:19           ` Chris Pacia
2014-04-20 16:27             ` Wladimir
2014-04-20 16:30               ` Chris Pacia
2014-04-22 13:51               ` Aaron Axvig
2014-04-23  9:44                 ` Danny Hamilton
2014-04-23  9:56                   ` Tamas Blummer
2014-04-23 11:48                     ` Chris D'Costa
2014-04-20 16:23           ` Erik Garrison
2014-04-20 16:30             ` Alan Reiner
2014-04-20 16:56               ` Mike Caldwell
2014-04-20 17:47                 ` Jannis Froese
2014-04-20 18:10                 ` Pavol Rusnak
2014-04-20 17:42 ` Arne Brutschy
2014-04-20 18:11   ` Mike Caldwell
2014-04-20 18:22     ` Arne Brutschy
2014-04-20 18:34       ` Mike Caldwell
2014-04-20 18:43     ` Oliver Egginger
2014-04-20 19:19       ` Christophe Biocca
2014-04-20 19:32         ` Gmail
2014-04-20 20:28         ` Mike Caldwell
2014-04-21  0:16           ` Justin A
2014-04-21  1:18             ` Mike Caldwell
2014-04-21  1:33               ` Un Ix
2014-04-21  3:34                 ` Mike Caldwell
2014-04-21  4:08                   ` Christopher Paika
2014-04-21  5:41                 ` Pieter Wuille
2014-04-21  5:51                   ` Tamas Blummer
2014-04-21  6:21                   ` Tamas Blummer
2014-04-21 12:14                     ` Un Ix
2014-04-21 12:24                       ` Tamas Blummer
2014-05-01 22:35 Aaron Voisine
2014-05-03  2:06 ` Gordon Mohr
2014-05-03  5:41   ` Aaron Voisine
2014-05-03 15:48     ` Christophe Biocca
2014-05-03 16:02       ` slush
2014-05-03 16:10         ` Tamas Blummer
2014-05-03 16:27       ` Mike Caldwell
2014-05-04  1:04         ` Chris Pacia
2014-05-04  5:18           ` Drak
2014-05-04  6:15             ` Aaron Voisine
2014-05-04  6:23               ` Un Ix
2014-05-04  6:27               ` Wladimir
2014-05-04  6:36                 ` Tamas Blummer
2014-05-04  6:59                   ` Wladimir
2014-05-04 14:42               ` Mike Caldwell
2014-05-05 22:33     ` Gordon Mohr

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=DFFB1B2C-F10B-4CF7-9D01-F6A27F9FA229@bitsofproof.com \
    --to=tamas@bitsofproof.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=pieter.wuille@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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