Re: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses

2017-10-30 Thread Moral Agent via bitcoin-dev
Or like keyart: https://pthree.org/2014/04/18/the-drunken-bishop-for-openpgp-keys/ Images would definitely be quicker to verify by a human, but I don't think humans can RELIABLY verify anything close to 25 bytes through an image. Our visual processing system is designed wrong for this purpose, si

Re: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses

2017-10-30 Thread Danny Thorpe via bitcoin-dev
Humans are very visually oriented, recognizing differences in images more easily than differences in text. What about generating an image based on the bytes of an address, using something like identicon, used by gravatar? Any small change to the text input produces a significantly different image.

Re: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses

2017-10-30 Thread Moral Agent via bitcoin-dev
If you are going to rely on human verification of addresses, the best way might be map it to words. For example, with a 6000 word list, a 25 byte address (with a checksum) could be mapped to 16 words like this: vocally acquireremoved unfounded euphemismsanctuarysecti

Re: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses

2017-10-30 Thread Ben Thompson via bitcoin-dev
The last few bytes can be generated to be the same also. On Mon, 30 Oct 2017, 14:20 Ricardo Filipe via bitcoin-dev, < bitcoin-dev@lists.linuxfoundation.org> wrote: > start double checking the last few bytes instead? > > 2017-10-30 8:56 GMT+00:00 shiva sitamraju via bitcoin-dev > : > > Hi, > > > >

Re: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses

2017-10-30 Thread Pieter Wuille via bitcoin-dev
On Oct 30, 2017 15:21, "shiva sitamraju via bitcoin-dev" < bitcoin-dev@lists.linuxfoundation.org> wrote: For example bc1qeklep85ntjz4605drds6aww9u0qr46qzrv5xswd35uhjuj8ahfcqgf6hak in 461e8a4aa0a0e75c06602c505bd7aa06e7116ba5cd98fd6e046e8cbeb00379d6 is 62 bytes ! ... While I get the error/checksu

Re: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses

2017-10-30 Thread shiva sitamraju via bitcoin-dev
For example bc1qeklep85ntjz4605drds6aww9u0qr46qzrv5xswd35uhjuj8ahfcqgf6hak in 461e8a4aa0a0e75c06602c505bd7aa06e7116ba5cd98fd6e046e8cbeb00379d6 is 62 bytes ! This is very very long. This will create lot of usability problems in - Blockexplorers (atleast user should be visually able to compare in a

Re: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses

2017-10-30 Thread Ricardo Filipe via bitcoin-dev
start double checking the last few bytes instead? 2017-10-30 8:56 GMT+00:00 shiva sitamraju via bitcoin-dev : > Hi, > > When I copy and paste bitcoin address, I double check the first few bytes, > to make sure I copied the correct one. This is to make sure some rogue > software is not changing the

Re: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses

2017-10-30 Thread Ben Thompson via bitcoin-dev
Checking the first few bytes of a Bitcoin Address should not be considered sufficient for ensuring that it is correct as it takes less than a second to generate a 3 character vanity address that matches the first 3 characters of an address. On Mon, 30 Oct 2017, 11:44 shiva sitamraju via bitcoin-de

[bitcoin-dev] Visually Differentiable - Bitcoin Addresses

2017-10-30 Thread shiva sitamraju via bitcoin-dev
Hi, When I copy and paste bitcoin address, I double check the first few bytes, to make sure I copied the correct one. This is to make sure some rogue software is not changing the address, or I incorrectly pasted the wrong address. With Bech32 address, its seems like in this department we are tak