Tracking: Add tests using zcashd test vectors

[conradoplg]

Motivation

The zcashd repository has a bunch of test vectors.

We could add tests using them to increase the confidence in zebra correctness and compatibility.

Issues

• Move transaction test vectors into their own files #1107
• Test transaction verification on block test vectors #1378
• Test/fix signature hashes using sighash.json from zcashd #2215
• Use testnet blocks in the unit tests #683
• Import and test against Sinsemilla test vectors from zcash-hackworks #2079
• Create Sapling-only transaction v5 test vectors #2047

Related Work

#2215 is a subset of this issue, regarding sighashes. It raises the issue that since some test vectors are randomly generated, we may require changing zebra to accept invalid fields, which does not seem to be worth it. But it needs further investigation.

Create Sapling-only transaction v5 test vectors (#2047)
Import and test against Sinsemilla test vectors from zcash-hackworks (#2079)
Test transaction verification on block test vectors (#1378)
Move transaction test vectors into their own files (#1107)

[teor2345]

Thanks for opening this ticket, I added a bunch of related tickets.

@mpguerra do you think this task is more like an epic? It seems like there will be a smaller task for each module or feature, with different priorities.

[mpguerra]

Converted to github tracking issue

[teor2345]

We've completed or obsoleted all these tasks.