From: Jakub Szwedo <jakubszwedo@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] BIP Proposal: Define Bitcoin Subunits as Satoshis/Sats
Date: Fri, 2 May 2025 13:54:26 -0700 (PDT) [thread overview]
Message-ID: <3339434d-6a10-4ccf-b1dd-2aa9afee5864n@googlegroups.com> (raw)
In-Reply-To: <CAHNPRA3mpSCVnNwX_utLY9Fyb4sC+RS=0YsCk7wRtooT4vftzw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 4902 bytes --]
Hi,
If the author of the BIP would like to add some accessibility and voice/UI
guidance mentioned by Lucas, a great open source resource created by
Bitcoin Design community exists on the topic:
https://bitcoin.design/guide/designing-products/units-and-symbols/
I hope it helps.
Best,
Jakub
On Thursday, 1 May 2025 at 11:24:17 UTC+2 Lucas André wrote:
> Maranatha!
>
> I propose a small addition that could improve this, particularly for users
> relying on assistive technologies (like our boi Hal Finney once did).
>
> Specifically, I suggest adding a short section on *accessibility and
> voice/UI guidance*. Your proposal does a solid job, but it doesn't yet
> cover how these should be handled in screen readers, voice assistants, or
> accessible interfaces. Below is a proposed section that could be added
> under "specification" or introduced as a new non-normative section.
>
> To ensure clarity and inclusiveness in UIs and assistive technologies, the
>> following recommendations apply:
>>
>> Pronunciation:
>> The abbreviation "sat" should be pronounced as /sæt/, and "sats" (plural)
>> should be pronounced as /sæts/ (rhyming with "cats") by screen readers and
>> voice assistants. "Satoshi" (singular) is pronounced /səˈtoʊʃi/. "Satoshis"
>> (plural) is pronounced /səˈtoʊʃiz/.
>
>
>
> Singular vs. Plural:
>> "1 sat" should be read as "one satoshi" and "100 sats" as "one hundred
>> satoshis" to preserve correct pluralization and meaning. When reading
>> aloud:
>
>
>
> "1 sat" → "one satoshi" → /wʌn səˈtoʊʃi/
>> "100 sats" → "one hundred satoshis" → /wʌn ˈhʌndrəd səˈtoʊʃiz/
>>
>> Readable Formats:
>> Prefer full terms in accessibility modes (e.g., "satoshis" instead of
>> "sats"), and group digits to assist parsing (e.g., "12,345" instead of
>> "12345").
>>
>> Contextual Labels:
>> Interfaces should use clear alt-text or aria-labels such as: *alt="Transaction
>> fee: 14 satoshis per virtual byte". * This enables screen readers and
>> other assistive technologies to accurately interpret and communicate the
>> content.
>
>
> If this makes sense, I'd be happy to help refine it or adjust to fit the
> structure if necessary.
>
> References:
> https://www.internationalphoneticalphabet.org
> https://tophonetics.com
>
> Peace,
> Lucas.
>
> On Tue, Apr 29, 2025 at 11:16 AM 'OceanSlim' via Bitcoin Development
> Mailing List <bitco...@googlegroups•com> wrote:
>
>> To the Bitcoin developer community,
>>
>> I'm writing to propose a new Bitcoin Improvement Proposal (BIP) aimed at
>> formally standardizing terminology for Bitcoin's smallest unit. This is an
>> informational BIP that seeks to officially recognize "satoshi" (singular)
>> or "satoshis" (plural) as the standard term for 1/100,000,000 of a bitcoin,
>> with "sats" as the standard abbreviation.
>>
>> While this terminology is already widely used throughout the Bitcoin
>> ecosystem, no formal standard exists, leading to inconsistent usage across
>> applications, documentation, and communications. This BIP seeks to
>> formalize what has organically become common practice.
>>
>> The BIP can already be viewed here:
>> https://github.com/bitcoin/bips/pull/1841
>> <https://deref-gmx.com/mail/client/rgLlibWjbIA/dereferrer/?redirectUrl=https%3A%2F%2Fgithub.com%2Fbitcoin%2Fbips%2Fpull%2F1841>
>>
>> I'd like to note that this proposal differs from BIP-176 (Bits
>> Denomination) and the recent BIP-177 proposal (Redefine Bitcoin's Base
>> Unit). While those proposals suggest changing or adding denomination
>> schemes, this BIP simply formalizes existing widely-used terminology
>> without changing the underlying unit structure.
>>
>> I look forward to your feedback and suggestions.
>>
>> Thank you,
>>
>> OceanSlim
>> npub1zmc6qyqdfnllhnzzxr5wpepfpnzcf8q6m3jdveflmgruqvd3qa9sjv7f60
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Bitcoin Development Mailing List" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to bitcoindev+...@googlegroups•com.
>> To view this discussion visit
>> https://groups.google.com/d/msgid/bitcoindev/17076438-87eb-4531-81a1-e1850dffe277n%40googlegroups.com
>> <https://groups.google.com/d/msgid/bitcoindev/17076438-87eb-4531-81a1-e1850dffe277n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/3339434d-6a10-4ccf-b1dd-2aa9afee5864n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 8365 bytes --]
prev parent reply other threads:[~2025-05-03 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 12:18 'OceanSlim' via Bitcoin Development Mailing List
2025-04-29 22:10 ` Lucas André
2025-05-02 20:54 ` Jakub Szwedo [this message]
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=3339434d-6a10-4ccf-b1dd-2aa9afee5864n@googlegroups.com \
--to=jakubszwedo@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/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