Error Internal Service Error about anchor HOT 7 CLOSED

from anchor.

from anchor.

No worries. I love the wallet. A few suggestions:

1. This is more than a voter wallet so you might think about changing the name eos-voter?
2. As you can see from some of the errors above I didn't realize I needed to stake enough token in order to send. So, I'm not sure if you can check for the user before they try any of the functions like voting and sending EOS a head of time and pop up a warning that the need to stake for CPU and Bandwidth
3. Lastly it would be good if you can check for upper-case letters in account names so user knows that only lower-case works. or force a routine to auto lower-case?

Thanks again.
~S

from anchor.

A few answers for ya, based on the previous comments.

1. We are in the process of rebranding/renaming now, and having some art assets created.
2. It's a hard thing to nail down, because it depends on the usage on the entire network. We do see it as an issue though and are looking for ways to help notify users if their staked balance is too low (0.2.0 has warnings now if you try to unstake too much).
3. Good suggestion, we'll get that tied in to everywhere we allow username inputs.

If you ended up in a state with 0 staked in CPU/NET, you won't even be able to increase your stake, and will need another account to delegate some resources to fix the problem. It's a weird situation and some BPs have instructed people to set their stake to 0 (which we wouldn't recommend, since you can't do anything), so that's why we're now adding warnings on any actions that set the staked amount below 1.

from anchor.

Awesome. Look forward to the version update. Keep up the great work!
U rock!

from anchor.

The account name inputs are all lower case now - and I've opened issue #231 as a "catch all" for adding some sort of warnings to help guide users on resources within their account.

Closing this one out for housekeeping purposes!

from anchor.

U Rock!

from anchor.