Two new bugs in 1.4.0

[Gegegega]

          Hello again!

Yes, using the same account with an older version of Hugin Mobile might be a factor, so please let us know if this is indeed an old account and if you are facing the same issues when using a brand new account.

Thanks.

Originally posted by @f-r00t in #54 (comment)

[Gegegega]

I created a new wallet using the new Hugin app and recharged enough XKR. This time there is no longer a prompt for sending failure, and there are two new issues:

1. I recharged 10000 XKR for the first time, but after only chatting about more than 20 messages, I pledged all of them and cannot continue to send them; What is the pledge mechanism and is it related to the frequency of sending messages?

2. When I finish sending a message through the hub on my phone, there is a 10-20% chance that the message will not be displayed after being sent on my phone, but the recipient can see it. This problem occurs repeatedly;

Looking forward to a reply

[f-r00t]

Hi!

The "pledging" mechanism, as you call it works like this:
Whenever money is received to the account, or a message is sent, an optimizing function is run, which does the following:

1. Ensure that a subwallet exists that should hold the "pledged" XKR
2. Check whether the subwallet contains at least 10 inputs (small amounts of XKR that can be used to send messages).
3. If the amount if inputs is less than 10, send a transaction with 10 new inputs from the mainwallet to the subwallet.

The amounts of these inputs are 0.01 XKR, so every time you run out of available inputs 0.1 XKR is "pledged" into 10 smaller inputs that will be used to send more messages. So whenever this function is the reason for "Message failed to send" is when you run out of unlocked "pledged inputs" (the 0.01 XKR "bills" used to send messages). At this point a new wave of inputs should be sent from the main wallet which should arrive in 90s (the average block time for XKR).

There might be some bugs that can cause the app to forget that it has sent an input, at which point it will try to send the same input over and over, even though it is already locked and thus unavailable for use. We are investigating that possibility.

As for the second issue we will have to investigate that bug.

[Gegegega]

Thank you for your reply. If necessary, I can provide my wallet key to reproduce these problems. Please let me know if you need my wallet, I'll provide it.

[Gegegega]

I have 30,000 of xkr in my wallet, but less than 100 messages have been sent, and the xkr are locked. It is a new account.

[Gegegega]

I would like to report a new issue. Since all my 30,000 xkr were locked, until now, about 48 hours, they are still locked and have not been unlocked back to the wallet. Check, please.

[Gegegega]

Combined with the various problems that have arisen recently, it seems that there is a problem with the staking and decompression mechanism of this version, and at the same time, there is a problem with a certain staking and decompression mechanism related to the message display.I hope a version can be fixed as soon as possible. Currently, the Android version is basically paralyzed. If you use it every day, you will know that it is currently unavailable. Please increase the priority of this issue.