-
Notifications
You must be signed in to change notification settings - Fork 6
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
v0.0.0.74 GUI can't send to multiple addresses, incorrectly reports "insufficient funds" #206
Comments
Confirmed on Linux 22.04. |
The problem is stemming from where you add a new recipient, you have to select the asset you are sending individually. I have pre-populated the drop down, should be in next version |
multi-send send works just fine in GUI, it's console 'sendtomany' that will be a headache |
Oops, my bad. If we can pre-populate the dropdown in the GUI why can't we default to crown in the CLI? |
I refer to the conversation in dev chat, sending of any coins and assets is considered a deliberate action. Defaulting is always easier , no doubt there but we now have the ability to send things OTHER than CRW. If a user makes a send, they MUST stipulate what to send, otherwise all mistakes will be blamed on developers. The intentional nature of the send operation must remain so prevent users from sending a wrong asset. The nightmare of having sent 500 CRW when you wanted to send 500 BNH is to be avoided, because user will turn around and point at dev and say you defaulted to CRW whereas an ACTIVE choice is user error. This may require further discussion from members The GUI even gives you a warning and slows you down...console no such handbrake exists. We must look at both convenience and safety and pick a healthy balance. |
Just for accuracy of the issue, you actually can't select "Crown" in the dropdown since it's empty. So even if we knew the issue before, multisend would still be impossible. Look forward to the prepopulated version or even just the ability to select it from the dropdown in the first place. |
Fixed in 0.75 but now related to #214 |
Confirmed fixed. Thank you. |
Tried to send to 4 addresses at once, for a total of 21k with ~22k available:
Got this:
The text was updated successfully, but these errors were encountered: