4. From that byte[] to hash. You would be using a library here too so no need for test but tests are found in respective RFC docs or NIST also has a lot of hash tests.
I'd be cautious about assuming that third-party libraries have been fully checked with their own test vectors, because usually said test vectors do not exist. Some NIST function that's in a standard library and is maintained by Core developers, is more likely to have test vectors written for it than some library written by one guy.
To Golang'a credit, they do have test vectors for their built in hmac, sha256 and sha512 modules (is that what they're called in Go?
). Only RIPEMD160 tests, and the entire module, are missing which arguably is more important than everything else I mentioned because that influences the base58 tests and for those you'd want to pass actual hashes as input and not arbitrary text. It is also not defined by NIST which makes finding test vectors for it harder, since that place is where I believe most other implementations pull their tests from.However, OpenSSL source code does have some test inputs and outputs and they have some other goodies too like (language-agnostic) PBKDF and ECC inputs/outputs which can be used by someone trying to make their own tests
My point is some ripemd160 golang package out there probably won't have similar tests.