-
Notifications
You must be signed in to change notification settings - Fork 86
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
does not receive transparent transactions on zingo darkside test #455
Comments
This is because zingo relies on the RPC lightwalletd/common/darkside.go Lines 597 to 600 in 8003d7f
|
We could implement a darkside RPC that actually sets an in memory list of TxIDs for the test to set up, and then this RPC would return that info, would that work? What other things would be needed? |
@pacu - what you suggest is probably the best way. I think the interface to this darkside test-only gRPC would be a list of ("hex", integer) pairs (32-byte hex string (64 characters), and a height). These would be saved internally and returned by (production) As Pacu asked, what else would be needed? A test-only method to clear the list? The ability to clear individual items? We can do either or both, or whatever you prefer. I did look briefly into trying to "really" implement this in the darkside server (i.e., return results based on the current fake blockchain), but it would be a lot of work. The |
What is the bug?
heres what ive got
https://github.com/fluidvanadium/zingolib/tree/darkside_foray
running
cargo test --package zingo-cli --test integration_tests --features darkside_tests -- sync_transparent --nocapture
results in a test failure because no transparent transaction is picked up by the reciever.
sending to "unified" or "sapling" instead of "transparent" comes through. transparent also works in production.
Additional context
lightwalletd version: v0.4.16-7-g8003d7f
from commit: 8003d7f
"Ubuntu"="20.04.6 LTS (Focal Fossa)"
The text was updated successfully, but these errors were encountered: