faster, compatible encoding scheme for []crypto.Hash
couldn't help myself. This should be a lot smaller (base64 instead of base16, no separators), compatible (loads the old method if the new load attempt fails), and faster (only encoding 1 object instead of N).
Benchmarking on a production Sia client.