Skip to content
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

Properly handle a lack of unlocked balance in subaddresses #14

Open
sethforprivacy opened this issue Oct 15, 2024 · 0 comments
Open

Properly handle a lack of unlocked balance in subaddresses #14

sethforprivacy opened this issue Oct 15, 2024 · 0 comments

Comments

@sethforprivacy
Copy link
Contributor

When attempting to sweep_all, locked balance in subaddresses will trigger the following exception:

autoforward  | [2024-10-15 18:17:10] Error autoforwarding monero:
autoforward  | Traceback (most recent call last):
autoforward  |   File "/app/./src/autoforward.py", line 137, in <module>
autoforward  |     attempt_monero_autoforward()
autoforward  |   File "/app/./src/autoforward.py", line 123, in attempt_monero_autoforward
autoforward  |     sweep_all_monero(address)
autoforward  |   File "/app/./src/autoforward.py", line 63, in sweep_all_monero
autoforward  |     util.request_monero_rpc('sweep_all', params)
autoforward  |   File "/app/src/util.py", line 62, in request_monero_rpc
autoforward  |     raise Exception(response_json)
autoforward  | Exception: {'error': {'code': -4, 'message': 'No unlocked balance in the specified subaddress(es)'}, 'id': '0', 'jsonrpc': '2.0'}

This should be properly handled as it will happen frequently and isn't an error at all in many scenarios.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant