Anonymous user
Talk:Bitcoin/address validation: Difference between revisions
→Task definition: Vague task
Line 9:
:::::I advise starting with “convert key system to bitcoin address”, which will include the ripemd160 step but not the key generation itself, as well as needing a base58 encoder. (This task has the decoder instead.) –[[User:Dkf|Donal Fellows]] 22:55, 28 November 2012 (UTC)
::::::Good idea. I'll do that. I'll call it "bitcoin/Public point to address".--[[User:Grondilu|Grondilu]] 02:44, 29 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)▼
===Vague task===
▲
: I would second that opinion of Dkf. The only way I could work out what to do was to run another solution and find out what the intermediate values were the nconvert that to Python 3! --[[User:Paddy3118|Paddy3118]] 04:48, 29 November 2012 (UTC)
| |||