Thanks - I'll try that
Or maybe I won't... :|
I know exactly which 20 bytes you mean, I could probably handle some simple crypto myslef, but my god... version concatenated with the RIPEMD SHA256 of it, then concatenated with 4 bytes of SHA256 of SHA256 of the RIPEMD stuff... just so it could finally be base58 encoded....
It couldn't be more complicated, could it?
Though, I guess some test vectors with intermediate steps would help me a lot
This is exactly why I made the following charts: https://bitcointalk.org/index.php?topic=29416.0
The address construction process is illustrated at the bottom. Tx-serialization at the top. And when you're finally an expert at those, you can take a shot at OP_CHECKSIG (don't forget to reverse endian before signing!). Yeah, this stuff is complicated, but it's really a one-time investment. I printed out a couple of these diagrams and keep them nearby when coding...