Anonymous user
Talk:Bitcoin/address validation: Difference between revisions
C-based validators (and possibly others) are broken. They need to keep track of 0x00 bytes to ensure that address is 25 bytes.
m (→Vague task) |
(C-based validators (and possibly others) are broken. They need to keep track of 0x00 bytes to ensure that address is 25 bytes.) |
||
Line 24:
:::::Indeed there is barely any crypto in this task, apart from the use of sha-256. It mainly consists in big integer arithmetic (and somehow the C code manages not to use big integer, I have to check it out) and byte string manipulations.--[[User:Grondilu|Grondilu]] 11:25, 29 November 2012 (UTC)
===C-based code (and possibly others) improperly validates===
Much of the code here does not check to make sure that the bitcoin addresses are 25-bytes. Hence, testing using the C-based code shows that it validates the invalid six-character bitcoin address "BZbvjr". However, trying to send to this address using the standard bitcoin client will naturally produce an error. I have edited the Perl implementation to make it work correctly, but someone who is a better coder than I should do it for the other languages too.
| |||