-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BlockSci v0.6 not recognizing ZCash t-addr
addresses
#246
Labels
Comments
jredondo
changed the title
BlockSci v0.6 not parsing ZCash
BlockSci v0.6 not recognizing ZCash Feb 4, 2019
t-addr
addressest-addr
addresses
Using |
I have implemented this small patch and it seems to work as expected using:
This is the git diff with commit
|
maltemoeser
added a commit
to maltemoeser/BlockSci
that referenced
this issue
May 1, 2019
Previously a default of 1 was used for nVersionBytes, resulting in addresses not being found when nVersionBytes was > 1 (e.g., for Zcash). Implementation assumes pubkeyPrefix and scriptPrefix have the same length. Fixes: citp#246
maltemoeser
added a commit
that referenced
this issue
May 7, 2019
Previously a default of 1 was used for nVersionBytes, resulting in addresses not being found when nVersionBytes was > 1 (e.g., for Zcash). Implementation assumes pubkeyPrefix and scriptPrefix have the same length. Fixes: #246
Thanks for fixing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Greetings.
I'm using BlockSci AMI with BlockSci v0.6 (commit
304e1ff7eb670e5fff161688e26e698c56f21e28
).It seems I have parsed successfully the ZCash blockchain since parser finished with the expected message and the data directory seems filled as expected.
Nonetheless, it seems BlockSci is not able to interpret ZCash
t-addr
addresses.I have this small code for testing:
After running it like this (ZCash):
And after running like (Litecoin):
Here are the config files used up there:
ZCash:
Litecoin:
Please let me know if there is anything else I could provide.
Thanks in advance.
The text was updated successfully, but these errors were encountered: