Luke-Jr [ARCHIVE] on Nostr: 📅 Original date posted:2013-11-14 📝 Original message:On Thursday, November 14, ...
📅 Original date posted:2013-11-14
📝 Original message:On Thursday, November 14, 2013 11:11:26 PM Mark Friedenbach wrote:
> "key id" (thanks sipa).
>
> I know it's a more technical term, but that is rather the point. It
> was a fundamental error to call hashed-pubkeys "addresses" as people
> either associate this with "account" or physical addresses, which also
> rarely change.
>
> Security and privacy guarantees of the system are defeated when key
> pairs are reused. We should ideally adopt terminology that lead people
> to associations of ephemeral, temporary use. "key id" is at least
> neutral in this regard. Can anyone think of something better?
Keys are often reused, so not sure that conveys the single-use much better.
Reason I suggested invoice id is because nobody wants to pay the same invoice
twice.
Luke
📝 Original message:On Thursday, November 14, 2013 11:11:26 PM Mark Friedenbach wrote:
> "key id" (thanks sipa).
>
> I know it's a more technical term, but that is rather the point. It
> was a fundamental error to call hashed-pubkeys "addresses" as people
> either associate this with "account" or physical addresses, which also
> rarely change.
>
> Security and privacy guarantees of the system are defeated when key
> pairs are reused. We should ideally adopt terminology that lead people
> to associations of ephemeral, temporary use. "key id" is at least
> neutral in this regard. Can anyone think of something better?
Keys are often reused, so not sure that conveys the single-use much better.
Reason I suggested invoice id is because nobody wants to pay the same invoice
twice.
Luke