This now captures all relevant info, parsed into structs, along with the path taken along each step. Should be good enough to move on to issue #2
For early debug output, try running go test -v . on 752717a
You can see the output format between fullNode and shortNode, ending with hashNode or valueNodes
This now captures all relevant info, parsed into structs, along with the path taken along each step. Should be good enough to move on to issue #2
For early debug output, try running
go test -v .on 752717a You can see the output format between fullNode and shortNode, ending with hashNode or valueNodes