Topic: .001 vs .0001 as new standard unit - page 2. (Read 2964 times)
yeah uBTC and mBTC always get me confused... I like .00000001 BTC better
mBTC is good enough why change 
Because it's going to not be good enough so quickly. Once bitcoin gets to $10,000 even a mBTC is going to feel a bit expensive.
I think that we should use satochis !!!
mBTC is good enough why change
Because we have to change again when mBTC isn't enough also
mBTC is good enough why change
I'm all for 0.0001 but agree that I'm in a minority group and soon everybody will be using mBTC.
1 mBTC is small enough I think.
Only recently 1BTC was small enough. It's hard to move decimal places for people, we should try and do it as infrequent as possible. Better to go an order of magnitude smaller and save us from needing to do it again in a few years.
+1 i think that is better logic im with you rabbit
1 mBTC is small enough I think.
Only recently 1BTC was small enough. It's hard to move decimal places for people, we should try and do it as infrequent as possible. Better to go an order of magnitude smaller and save us from needing to do it again in a few years.
My prediction is that uBTC is just good enough. Just remember that there are only 12mil coins for 7 billion people. mBTC would be ok for now yes, but at the end we have to go to uBTC, so you better use uBTC now, so people can get used to it.
If you believe we should stick to BTC, vote other.
The mu confuses people.
It's not too high. If someone invests $100 a month, then that's 0.16 BTC right now. So, what? That's not too small. The software libraries that we use have not written to put thousands separators on the right side of the decimal place:
The following Python code (after the needed import statement prints "3.14159"
In QT:
locale = QLocale ("US")
print locale.toString(3.14159)
However 1000000 is printed as:
1,000,000
By default in both python, C, C++ commas are not put into the numbers.
The following Python code (after the needed import statement prints "3.14159"
In QT:
locale = QLocale ("US")
print locale.toString(3.14159)
However 1000000 is printed as:
1,000,000
By default in both python, C, C++ commas are not put into the numbers.
mBTC soon to reach dollar parity. Makes for quick and easy price understanding.
No, to get more investors we NEED to go to uBTC. The price is too high now for new investors. Normal people are scared now when they see the prices and don't understand that you also can buy 0.01BTC.
there have been quite a few topics on this, but i think to prevent confusion we just stick to BTC until we can go to Satoshi's
There's been a plethora of discussions on this. Consensus gravitated towards the following units:
.001 mBTC
.000001 µBTC or uBTC
.00000001 satoshi
I wish they'd alter the client as was done for the onecoin alt where you can set whatever scale of units you want to look at. Gaze in wonder at your millions of satoshis.
.001 mBTC
.000001 µBTC or uBTC
.00000001 satoshi
I wish they'd alter the client as was done for the onecoin alt where you can set whatever scale of units you want to look at. Gaze in wonder at your millions of satoshis.
I'm wondering what the consensus is on this issue. I'm not talking about a name for the unit, but rather which denomination is more ideal to use.
It seems like the main issue with this debate is whether or not the value of Bitcoin will 'outgrow' the .001 unit, just as we have 'outgrown' 1BTC.
What are your thoughts?
It seems like the main issue with this debate is whether or not the value of Bitcoin will 'outgrow' the .001 unit, just as we have 'outgrown' 1BTC.
What are your thoughts?
Jump to: