From maximillian.george at gmail.com Wed Jan 2 10:31:37 2019 From: maximillian.george at gmail.com (Maximillian George) Date: Wed, 2 Jan 2019 11:31:37 +0100 Subject: [Lightning-dev] visual identification of payee node id In-Reply-To: <87r2e0nwai.fsf@jb55.com> References: <462eedc1-39bb-48fc-6ab6-c83e56736d23@satoshilabs.com> <87r2e0nwai.fsf@jb55.com> Message-ID: <6046a837-b260-4e58-be91-42a451dbb2d8@Spark> Why not a confirmation phrase of a few words? This should be easier to implement and fit into a pre-existing design programme. Given a pool of enough words this would surely be as reliable as an identicon, no? Best regards, Max On 29 Dec 2018, 17:23 +0100, William Casarin , wrote: > Pavol Rusnak via Lightning-dev writes: > > > Hi all! > > > > Currently, when I perform a payment via QR code, I usually check the > > payee node id (public key) in the send dialog. However, this is a rather > > long hex value, so for example Eclair app shows just the beginning and > > the end of the value. > > > > Idea: Can we show an identicon (for example https://jdenticon.com/) of > > payee node id (= public key) next to the QR code, so user can visually > > quickly check whether the recipient is correct? > > I think it would be interesting if someone came up with a visual hashing > algorithm, where small changes in the inputs had uniformly random visual > outputs. I was testing jdenticon with my node id: > > 03f3c108ccd536b8526841f0a5c58212bb9e6584a1eb493080e7c1cc34f82dad71 > > I was surprised to see that small changes to the first digit didn't > change the visual output at all. Whether or not this is a useful > property in this use case, it's something to keep in mind. > > Cheers, > Will > > -- > https://jb55.com > _______________________________________________ > Lightning-dev mailing list > Lightning-dev at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: