-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
sweep_below / sweep_all frequently breaks, causes intensecoind to throw an error #107
Comments
I did a "sweep_all" to myself, on a wallet with many outputs, and it worked pretty fine. |
sweep_all error doesn't always work , sometimes takes place , but often error, |
are you sure that's the right PR? it seems to be the one fixing double transaction value in the wallet, not the sweep_something commands. |
this makes the problem worse, as I was told, and I have a copy of your code, and I have the same problem as you do valiant1X is busy probably here I'm also looking for a way out |
Most of that PR doesn't apply to intensecoin, as we don't have secondary addresses. |
uint64_t const CRYPTONOTE_PUBLIC_ADDRESS_BASE58_PREFIX = 0xfb; |
whatever it is . there is a problem . if the network is weak then writes transaction to be large and not enough outputs to use, in RPC and cli and gui wallet |
This seems solved at this point. I no longer run into the OUTPUT_DNE errors. The only situation where this is now failing is where I believe that it is supposed to fail. For example, on one of my wallets sweep_below fails because it can't find any mixable outputs for one of my outputs on the blockchain. Resulting in:
When attempting sweep_unmixable, that fails because the single unmixable output is so small that it errors with:
Just kind of stuck in that situation for that wallet due to that output. Although, spit balling here, wasn't RingCT supposed to make it so that outputs didn't have to mix with same-value outputs on the chain? I thought RingCT hides output values which negated the possibility for an output to ever be unmixable. Unless I am grossly misunderstanding that. |
Poked around in the Monero github. Looks like there is a fix for this state that effectively "breaks" sweep_below/sweep_all when there's an unmixable output. Original Issue: monero-project/monero#3202 |
Version: Monero 'Belaya' (v2.0.2.1-2f32f28)
Tested On: Win & Mac (intense-wallet-cli), Linux (intensecoind)
Description: Attempting to use 'sweep_all' or 'sweep_below' results in the wallet displaying an error that suggests the daemon broke connection or experienced a failure, preventing use of the sweep commands.
Steps to Reproduce:
Note: On rare occurrence I can get this to succeed, so it's not 100% reproducible at all times. But 9 out of 10 at least.
sweep_all <YOURWALLETADDR>
Error: failed to get output: possibly lost connection to daemon
orError: failed to get blockchain height: possibly lost connection to daemon
displays and the sweep fails to continuesweep_below 5 <YOURWALLETADDR>
Error: failed to get output: possibly lost connection to daemon
orError: failed to get blockchain height: possibly lost connection to daemon
displays and the sweep fails to continueAdditionally, you may observe in both cases that an error is produced in intensecoind's log when the sweep is attempted, such as:
Resolution Attempted:
On the assumption that
OUTPUT_DNE
from intensecoind's log means "Output Does Not Exist", I have runrescan_bc
and evenrescan_spent
just for kicks. I also regenerated the wallet from scratch with mnemonic seed. No change.I have attempted this with 4 total nodes as well: My 3 pool nodes and also HashVault's remote node.
This leads me to believe it does not seem to be a corrupt/bad wallet file or a node with a corrupt/bad blockchain.
The text was updated successfully, but these errors were encountered: