📅 Original date posted:2021-08-21 📝 Original message:Good day Christopher, ...

npub16g0…hzyg

2023-06-07 22:58:08

in reply to nevent1q…uu76

📅 Original date posted:2021-08-21
📝 Original message:Good day Christopher,

Thanks for your comment! LifeHash looks indeed quite interesting. I can imagine some examples
where it would be very useful, and I guess it could be used as a visual verification for the
address in a wallet as well.

However, for my proposal (Human readable checksum (verification code) to avoid errors) it
could have the following disadvantages:

1. It would be only one standard instead of one standard per crypto network (it should be
different on each of them as described in the proposal). This could be solved with the
inclusion of a network identifier somehow, but would increase the complexity of the
implementation.

2. For this special use case, a simple 3 to 4 digit code is easier to implement than a
graphic, and easier to include in an existing app, with minimal layout changes. The simpler it
is, the more likely it will be for developers to actually implement it.

3. A graphic cannot be communicated by voice (in some situations this could be an easier way
to communicate the verification code)

Greetings,
TS

Christopher Allen wrote on 8/19/21 12:37 PM:
> As an alternative, you might want to consider LifeHash, which includes a visual indicator as
> well as a readable fingerprint value.
>
> LifeHash is an open source visual hashing algorithm that we use for all our projects. Lifehash
> has a number of desirable qualities, including high complexity, good aesthetics, a
> printer-friendly (CMYK) color gamut and robustness when transformed to grayscale.
>
> * [LifeHask Overview and links to reference
> code](https://github.com/BlockchainCommons/lifehash
> <https://github.com/BlockchainCommons/lifehash>;)
>
> * [LifeHash Explainer on YouTube](https://www.youtube.com/watch?v=cu0K__KLxKo
> <https://www.youtube.com/watch?v=cu0K__KLxKo>;)
>
> * [Our LifeHash UX best practices - The Object Identity
> Block](https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2021-002-digest.md#object-identity-block
> <https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2021-002-digest.md#object-identity-block>;)
>
> -- Christopher Allen
> Principal Architect, Blockchain Commons
>
>

Author Public Key

npub16g0u0er3urgenux4fa7gt2h8avvfa33r3657jcwne4naszvyq4qsv8hzyg

Seen on

wss://relay.noswhere.com

Show more details

Published at

2023-06-07 22:58:08

Kind type

1 Short Text Note

Event JSON

{ "id": "4864ecf81141d51142d5386beaf24af8572ee5f877bbd756c5d8550897f13614", "pubkey": "d21fc7e471e0d199f0d54f7c85aae7eb189ec6238ea9e961d3cd67d809840541", "created_at": 1686178688, "kind": 1, "tags": [ [ "e", "a33b3f0d53c98f3fc059fbd1e00cf1f7838bc50bfea2f6b6c05733132d02affb", "", "root" ], [ "e", "d68e0affc1a481474d01bbd433afc4ba674ff0a8aea14ad19d6d373eabe97c95", "", "reply" ], [ "p", "2a2be7532ec03e16fa6ff38360d30cc714893870cbd9fafbefeb1df2df858c4d" ] ], "content": "📅 Original date posted:2021-08-21\n📝 Original message:Good day Christopher,\n\nThanks for your comment! LifeHash looks indeed quite interesting. I can imagine some examples \nwhere it would be very useful, and I guess it could be used as a visual verification for the \naddress in a wallet as well.\n\nHowever, for my proposal (Human readable checksum (verification code) to avoid errors) it \ncould have the following disadvantages:\n\n1. It would be only one standard instead of one standard per crypto network (it should be \ndifferent on each of them as described in the proposal). This could be solved with the \ninclusion of a network identifier somehow, but would increase the complexity of the \nimplementation.\n\n2. For this special use case, a simple 3 to 4 digit code is easier to implement than a \ngraphic, and easier to include in an existing app, with minimal layout changes. The simpler it \nis, the more likely it will be for developers to actually implement it.\n\n3. A graphic cannot be communicated by voice (in some situations this could be an easier way \nto communicate the verification code)\n\nGreetings,\nTS\n\n\n\nChristopher Allen wrote on 8/19/21 12:37 PM:\n\u003e As an alternative, you might want to consider LifeHash, which includes a visual indicator as \n\u003e well as a readable fingerprint value.\n\u003e \n\u003e LifeHash is an open source visual hashing algorithm that we use for all our projects. Lifehash \n\u003e has a number of desirable qualities, including high complexity, good aesthetics, a \n\u003e printer-friendly (CMYK) color gamut and robustness when transformed to grayscale.\n\u003e \n\u003e * [LifeHask Overview and links to reference \n\u003e code](https://github.com/BlockchainCommons/lifehash \n\u003e \u003chttps://github.com/BlockchainCommons/lifehash\u003e)\n\u003e \n\u003e * [LifeHash Explainer on YouTube](https://www.youtube.com/watch?v=cu0K__KLxKo \n\u003e \u003chttps://www.youtube.com/watch?v=cu0K__KLxKo\u003e)\n\u003e \n\u003e * [Our LifeHash UX best practices - The Object Identity \n\u003e Block](https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2021-002-digest.md#object-identity-block \n\u003e \u003chttps://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2021-002-digest.md#object-identity-block\u003e)\n\u003e \n\u003e -- Christopher Allen\n\u003e Principal Architect, Blockchain Commons\n\u003e \n\u003e", "sig": "581d8bc5383738d8cf0aee39071c3ced9cc5fefd3d7f404fb8975a2374c1f4a0b338b60e1f0b0f4166081cc07eedf54f6aaade4b8b6ffcfb08a67205edb511a9" }