Go to file
Larry Ruane 4aa4e669a5 add v5 transactions (test vectors) 2022-08-27 23:39:19 -06:00
basic-reorg add tx-height-reorg/ (move tx to a different height) 2020-05-20 17:18:09 -06:00
shield-funds add v5 transactions (test vectors) 2022-08-27 23:39:19 -06:00
testnet-canopy canopy tests data set 2020-11-03 20:45:15 -03:00
transactions add v5 transactions (test vectors) 2022-08-27 23:39:19 -06:00
tx-height-reorg tx-8f064d23.txt was wrong (odd number of hex characters) 2020-05-21 18:55:00 -06:00
tx-incoming add tx-incoming directory (#266, 4 spendable transactions) 2020-06-01 11:57:40 -06:00
tx-index-reorg tx-8f064d23.txt was wrong (odd number of hex characters) 2020-05-21 18:55:00 -06:00
tx-remove-reorg tx-8f064d23.txt was wrong (odd number of hex characters) 2020-05-21 18:55:00 -06:00
LICENSE Initial commit 2020-05-03 08:02:07 -06:00
README.md Add directory structure information to the README 2020-05-05 16:56:55 -06:00

README.md

darksidewalletd-test-data

Test files (sample blocks and transactions) for full-suite integration zcash/lightwalletd-wallet tests

Directory Structure

The block sets contained in this repository are organized as follows:

  • Related block sets should live in the same directory. The directory name should indicate the type of testing that the block sets are useful for, e.g. basic-reorg for basic reorg testing.
  • Inside the directory, there should be one or more .txt files containing the block sets. There will usually be multiple block sets for reorg tests (before the reorg, after the reorg). The filenames should indicate what the blocks are useful for.
  • If the block sets were generated using the genblocks tool in lightwalletd, then there should be a generate.sh script for re-recreating the input to genblocks. This will save everyone time if the block sets need to be regenerated or modified.