BIP-177 can go suck a bag of sats.
If people want a doc to use sats, here ya go, here's BIP-188:
https://freakoverse.github.io/BIP-188/
Login to reply
Replies (4)
This is really cool :wolf_smile:
No unicode = non-starter.
The Bitcoin symbol didn't have unicode before, yet people recognized it overtime and then it was added. Did people at the time give up on the ₿ symbol because it wasn't in unicode? Nope.
It was added as a result of being used as non-unicode methods and the committee recognizing the proof of its use by multiple apps, sites, and general conversations. People used B or ฿ (or a symbol as part of a font package) as an alternative for its non-unicode existence before it was added.
The other criteria that the logo was public domain.
So basically, similar to the Bitcoin symbol, to have a Satoshi(s)/Sat(s) symbol in unicode, people must first start using it. They've already been using it by saying 'sats' mostly, and now there's this custom font for it, so basically it's a matter of time before it gets added to unicode, but similar to Bitcoin, it won't get added just because we want it, it has to actually be used and implemented it, a non-unicode version, until it does get added via a proposal with these proofs of usage.
The Bitcoin symbol was added to unicode 7 years ago, those were wildly different times. The Bitcoin symbol was the de-facto symbol of all digital money back then (eth had just been released a year prior). Also there was no arguing what symbol the Bitcoin symbol was.
It had a caché that we will never see again in the world of digital currency symbols, and it rode that caché in to unicode inclusion. A one off.
Now in 2026 (and moving forward) there is no way a Layer2 digital currency symbol is going to get in there. And definitely a symbol that doesn't have universal agreement for what it's supposed to be for. Even for Layer1, there's just no way, at least if we're being honest.
That's why Tether chose ₮, Tezos chose ꜩ, and so on.