Still optimistic about this. I'm now thinking back to that partial spend test transaction I ran earlier—suspect it might've left the balance at zero when it should've shown around 0.2 ZEC remaining. Yeah, I know what you're about to say: not the cleanest test if you didn't verify the output. Fair point. But here's the thing, sometimes spotting these discrepancies is half the debugging process.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
21 Likes
Reward
21
4
Repost
Share
Comment
0/400
RadioShackKnight
· 01-11 19:29
Haha, isn't this just talking about those tricks on the chain? Just a 0.2 ZEC difference and they can come up with so many tricks.
View OriginalReply0
WealthCoffee
· 01-09 12:56
Debugging and finding bugs is like this; the differences themselves are clues. However, we still need to figure out where the 0.2 ZEC went.
View OriginalReply0
SigmaBrain
· 01-09 12:55
Debugging is like this, impatience won't do. The difference of 0.2 ZEC is quite interesting; I need to find out where the problem is.
View OriginalReply0
MerkleDreamer
· 01-09 12:35
Debugging these small differences can be really annoying, but on the other hand, it's often these "dirty" areas where the problems can be spotted.
Still optimistic about this. I'm now thinking back to that partial spend test transaction I ran earlier—suspect it might've left the balance at zero when it should've shown around 0.2 ZEC remaining. Yeah, I know what you're about to say: not the cleanest test if you didn't verify the output. Fair point. But here's the thing, sometimes spotting these discrepancies is half the debugging process.