Thoughts on using ₿ as a suffix for notation instead of using "sats"?
100₿ = 100 sats
nostr:note1l48qyh8d90pxrhrjx07mfcu2xgwjg47deaqarg258rnze5f4u08smgy978
Discussion
That ship has sailed, sir. Sats, the standard.
If you’re dealing with sats, I think it should say sats. If you’re trying to help the noobs out, at least provide the option to change to unit display. My 2 sats. 😎
I am with fiatj on this one, found it confusing when I used broadwalk the first timr
I still hear new users saying they can never afford 1 Bitcoin, not knowing it is 100,000,000 sats
Not sure what the answer is here, you are free to build broadwalk how ever you like
Thx for the feedback. Yea i hear that too, which is the hurdle i'm trying to overcome with this notation. You can send 100₿ and the user knows its bitcoin and he know he didn't just receive $10m, so he does more research, learns about units and symbols and then buys more.
When bitcoin is the only money anyone uses it won’t need a symbol at all.
nostr:note1juh5dfzguvuafaplp9qjrq2dld327hvcfjyw54aemgc93qhhz3qq70fsdv
That'd be very confusing as this is the unit symbol for 1 BTC which is 100 m sats.
What about the three line 'pancake' stack symbol?
i like it, but didn't get adopted by any wallets that i know of
I appreciate the reasoning.
$
Yes, I'm doing the same in chachi.chat Sats are bitcoins, don't listen to the nerds.
Impatient solution to a non-problem long term. Sats should stay
µ₿ would be the correct way to do this technically, right? 1µ₿ = 100 sats
The difference in scale/format can make it work, like epoch seconds versus epoch milliseconds, and integer milliseconds versus floating point seconds. If an apple is 1000₿, or a house is 2.642344₿ it's easy to infer scale. It's less ideal for sending because you might want to send "one BTC", but the sending interface could confirm the amount in "sats" ₿ before sending. In general I find displaying whole BTC to be poor UX for most people, as does using the term "sats".
