Talk:Bitcoin/address validation: Difference between revisions
→Task definition
Line 6:
::::I've added more details in the description of the task. I'll add an example of a correct bitcoin address later. (a wrong one is easy to forge).--[[User:Grondilu|Grondilu]] 10:46, 28 November 2012 (UTC)
::: Of more interest though is whether there will be other bitcoin-related tasks in the future (specifically, the next 3 months; there's no point trying to plan further ahead than that). If not, the name of this one should change. That's independent of whether this is draft or not. –[[User:Dkf|Donal Fellows]] 09:09, 28 November 2012 (UTC)
::::I was thinking of making a "create a bitcoin address and its private key" task, but on second thought I'm not sure it can be done in a short program. It would require [[wp:elliptic curve]] arithmetic so I may have to create a task about that first.--[[User:Grondilu|Grondilu]] 10:50, 28 November 2012 (UTC)
: Looking at this further (and peeking at the proposed solutions) the task appears to be to verify that the data is base58-encoded and that the computed check-digits match the supplied ones (which is basically following the bottom of [https://en.bitcoin.it/w/images/en/9/9b/PubKeyToAddr.png this diagram], i.e., after the ripemd160 step). If this is the case, it is important to '''spell this out''' in the task definition rather than leaving it to people to guess. –[[User:Dkf|Donal Fellows]] 09:40, 28 November 2012 (UTC)
| |||