Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

only address disappeared from wallet #148

Open
brechindo opened this issue Dec 23, 2017 · 3 comments
Open

only address disappeared from wallet #148

brechindo opened this issue Dec 23, 2017 · 3 comments

Comments

@brechindo
Copy link

About 2 weeks ago, first installed, created first address, did first tx to it from binance.com
Tx appeared after about 48 hours, as Pending.
Stayed Pending for about another 48 hours.
Next morning, tx is gone because the address itself has vanished from the wallet.

Lost $4,300! Yeah yeah Im a fool for trusting a beta client in the first place. Regardless, any thoughts on how the address might be salvaged? I've not reinstalled the app, not created any other addresses, so hopefully there's some deterministic PRNG magick to regen the one-and-only lost address?

Currently wallet 0.9.109-32eabfb installed from Play Store.
Currently Android 8.0.0 with 12/1/17 patch. Rooted but not doing anything with root.
Google Nexus 6P

@hannesa2
Copy link
Contributor

Yes, this app (or iota) has a huge network problem and I don't know if it's bad nodes, or the system 'iota' is bad. At least I reduced my engagement in iota because of this

But just whine is to less, what can be improved ?

The node selection with separated protocol, ip, and port can be improved easily !
I see at least a predefined (working) node list in the app as a big step in the right direction.
An a more advanced solution would be a user count who uses right now this node, or a rating for this node

@pinpong
Copy link
Collaborator

pinpong commented Dec 23, 2017

Sorry about this but the node is stuck with an older solid milestone. Let's wait for a bug fix. Andreas has already the log from the deadlock.

@hannesa2
Copy link
Contributor

It's good to see someone takes care about this.
My positive benchmark is, when I can send a friend of my 1 IOTA within seconds, but currently IOTA has a failure of 100% on my side.
As I see, when the infrastructure fails, just by one node, the system fails.
That's bad !

What's about this: when the wallet recognize a non-synced node, it's iterate all known nodes till it's find a valid one.
Currently it's just suck, and that's not a valid option in my point of view

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

No branches or pull requests

3 participants