<oembed><type>rich</type><version>1.0</version><author_name>npub12rkw0jajmsck4uwdtksdvtswrlkypusfryjzera7m4fhqta6jhdsz3aqxc</author_name><author_url>https://nostr.ae/npub12rkw0jajmsck4uwdtksdvtswrlkypusfryjzera7m4fhqta6jhdsz3aqxc</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2013-11-15&#xA;📝 Original message:On 14 November 2013 23:01, Luke-Jr &lt;luke at dashjr.org&gt; wrote:&#xA;&#xA;&gt; I wonder if it might make sense to bundle some other terminology fixups at&#xA;&gt; the&#xA;&gt; same time.&#xA;&gt;&#xA;&#xA;A very good idea.&#xA;&#xA;&#xA;&gt; Right now, Bitcoin-Qt has been using the term &#34;confirmations&#34; (plural) to&#xA;&gt; refer to how many blocks deep a transaction is buried. We also use the term&#xA;&gt; &#34;confirmation&#34; to refer to the point where a transaction is accepted as&#xA;&gt; paid.&#xA;&gt; IMO, the latter use makes sense, but the former leads to confusion&#xA;&gt; especially&#xA;&gt; in light of scamcoins which abuse this confusion to claim they have &#34;faster&#xA;&gt; confirmations&#34;, implying that the actual confirmation occurs faster when it&#xA;&gt; really doesn&#39;t. &#34;5 blocks deep&#34; may not be more clear to laymen, but at&#xA;&gt; least&#xA;&gt; it makes it harder for people to confuse with actual confirmation.&#xA;&gt;&#xA;&#xA;I think people are more familiar with check clearance - &#34;the payment/check&#xA;has cleared&#34;.&#xA;&#xA;If &#34;confirmation&#34; and &#34;n confirmations&#34; together are problematic, I&#39;d talk&#xA;about &#34;cleared payments&#34; and &#34;n confirmations&#34;&#xA;&#xA;So &#34;a payment clears after one confirmation, but you might want to wait&#xA;until the payment has been confirmed n times&#34;.&#xA;Then at least you are not using the same word for two different meanings&#xA;and you&#39;re using stuff more familiar in popular lexicon.&#xA;I dont think it&#39;s helpful for users if we use the word &#34;blocks&#34;.&#xA;&#xA;Without the technical details, I just explain to normal bitcoin users that&#xA;the Bitcoin network checks and confirms the payment is valid (multiple&#xA;times).&#xA;&#xA;I think we all know the problems with the term &#34;address&#34;. People naturally&#xA;&gt; compare it to postal addresses, email addresses, etc, which operate&#xA;&gt; fundamentally different. I suggest that we switch to using &#34;invoice id&#34; to&#xA;&gt; refer to what is now known as addresses, as that seems to get the more&#xA;&gt; natural&#xA;&gt; understanding to people. On the other hand, with the advent of the payment&#xA;&gt; protocol, perhaps address/invoice id use will die out soon?&#xA;&gt;&#xA;&#xA;I think &#34;key id&#34; is a bit alien at user level - it&#39;s not something they are&#xA;used to.&#xA;For years, people had a problem with  &#34;email address&#34;, instead using &#34;email&#xA;number&#34; but they got there eventually. Most people nowadays use &#34;email&#xA;address&#34;&#xA;So &#34;payment address&#34; or &#34;bitcoin address&#34; make better sense here when&#xA;qualified as a &#34;&lt;foo&gt; address&#34; and not just an &#34;address&#34;&#xA;&#xA;You could also call it &#34;payment id&#34;, but I dont think &#34;invoice id&#34; since&#xA;no-one pays to an invoice id that&#39;s just a reference for a payment, not the&#xA;destination.&#xA;&#xA;People are very familiar with Paypal these days, and are familiar with&#xA;&#34;paypal address&#34; or their &#34;paypal id&#34; so again I think valid contenders are&#xA;&#34;bitcoin address&#34; or &#34;bitcoin id&#34;.&#xA;&#xA;Regards,&#xA;&#xA;Drak&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131116/4c212074/attachment.html&gt;</html></oembed>