-
Notifications
You must be signed in to change notification settings - Fork 10
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
Transparent tx in the unfinalised chain are not served by Zebrad in Regtest mode. #145
Comments
Relevant test can be found here: [https://github.com/zingolabs/zaino/blob/37435441ebd577b8a21ab794794222c85e981fc2/integration-tests/tests/wallet_to_validator.rs#L153] |
I'm working to fix this on the fix-get-addr-tx-ids branch, I think the problem is that the provided addresses are parsed as |
Let me see if I am tracking this correctly, is regtest mode in zebrad unable to test certain conditions because of this issue? |
It could make it more difficult to test features around address balances and available spends - it's a bug I was hoping to eventually fix by enabling configurable address prefixes on custom Testnets and Regtest. The b58 address prefixes on Regtest are the same as Testnet, but were being stored in the non-finalized state as I thought the changes in fix-get-addr-tx-ids would solve the problem, and perhaps they did and uncovered a new problem, but now the test is still panicking (and sooner, in |
We've just merged the fix into main if you want to try this again |
The following is the log from the
send_to_transparent
tests (running on both zcashd and zebrad) inintegration-tests::wallet_to_validator::wallet_basic
. Currently zebrad is not returning transparent tx data until it hits the finalised chain.The text was updated successfully, but these errors were encountered: