I think this is a great idea and I will support including it in the official client.
Apologies if I posted this already - why can't we just add a check digit instead of changing the account number to alphabetti-spaghetti, not perfect but i would catch the majority of errors.
http://en.wikipedia.org/wiki/Luhn_algorithmcause if you look at two strings: DatS7 and opKrN you instantly see the difference, the lesser the alphabet, the less difference is visible on two words over that alphabet...
I agree but the current proposal is not restricted to alphanumerics based on the examples I tried, it gets special characters like #$ etc which makes things harder especially on a smart phone.
Anyway I agree with xyzzyx that this is low level stuff and once its stored then we will use pin access, although I assume we would load the ECC version of the account number into the phone with a QR scan so I guess it really doesn't matter - the important thing is the account gets set correctly.
correct
We need a layer above current unprotected accts and might as well go with best possible method, which is undoubtedly an ECC layer.
https://forums.nxtcrypto.org/viewtopic.php?f=17&t=524 has a great discussion on the reed solomon method ricot proposed.
Once we have that, we can build more user friendly layers such as allowing people to use their cellphones and scan QRcodes to send/recv payments.
One step at a time. Or since we are decentralized, all steps all the time! As soon as Reed Solomon accts are defined, no reason cellphone QRcodes can't be implemented on top of ECC accts
James