Just like the title says, I'm mainly getting timeouts tho there were a couple of bad request errors, seems to be an issue with the node. One of the things I noticed that I thought was weird is that 'node url' is set to a specific IP address instead of a domain (159.65.11.55:9053)

as a user who creates a new wallet in the mobile app I want to be able to easily backup my 15-word mnemonic so that I can recover my wallet at a later date and not lose all my assets (after I damaged/lost my phone)

the wallet setup screen does require specific words from the mnemonic to be entered that should make the user backup/write down the mnemonic but often the mobile user will take a screenshot to do this b/c it's easiest but that's very bad. enabling copy of the mnemonic to the clipboard would help some users put this in a safe(r) place like a password manager which is also not-the-best-practice but it's sufficient for some and better than a screenshot. I know iOS put some privacy constraints recently on clipboard access - not sure if that adds complexity here or not. mnemonic phrase copy to the clipboard to me is very nice-to-have as I use a password manager for some light wallets for convenience outside my ledger/steel seed phrase). Anyways, many wallets out there enable this feature and many don't. if you don't like it / want to implement it I think that's just fine.

That said, I think that at a minimum, there should be a way for the user to back up the mnemonic post-wallet creation should the original mnemonic backup be lost. see Trust Wallet's implementation for a decent example of what I have in mind here: https://community.trustwallet.com/t/lost-recovery-phrase-or-private-key/221

Currently, the Android wallet can already be used as a cold wallet:

• Use a fresh (factory reset) Android device and don't set up any Wifi connections
• Use flight mode and don't insert a SIM card
• Install the Android app by sideload
• generate your wallet
• Done - you have a cold wallet

This works, but the experience is subpar because the app tries to connect to the network and shows zero balance. The UI could be improved: There could be a setting that switches to "Cold wallet" mode. In this mode, there is no attempt to retrieve information and the wallet list will not show any balances any more. Additionally, in this mode, a big warning can be shown when a network connection is detected.

These UI improvements can be done without problems, however, as soon as you want to access your funds, you need to connect and the wallet goes from cold to hot. In theorey, that is not necessary: A second - connected - device with only the public address could prepare the unsigned transaction, this transaction can be transferred to the cold wallet device by QR code, the transaction is then signed and transferred back by QR code and the cold wallet never needs to connect to the internet. Discussion with @aslesarenko : https://discord.com/channels/668903786361651200/669207683869573142/869136961904996382 A POC should be implemented to see if this is viable to add to the app and have a ledger alternative for people owning a second, not needed Android device.

In most of the cases full context data is not required, but in any case each input box requires proof (aka signature) to be generated, which is done by this method https://github.com/ScorexFoundation/sigmastate-interpreter/blob/de6220fefd5738ea7984ebb18e088d0da9f58f3c/sigmastate/src/main/scala/sigmastate/interpreter/ProverInterpreter.scala#L117 It is possible to implement optimised serialization/deserialization of the Context data storing only necessary data. Each ErgoTree can be analysed on which context data is actually used in the contract and only those data need to be serialized and passed to the Cold Wallet. In most of the cases the context data set is actually small, so the implementation can be generic (but may be quite involved). The first PoC version can support P2PK addresses only, in which case context data in not needed, and some dummy Context can be created in Cold Wallet App, to be passed in prove method above.

Open questions:

• Inboxes need to be serialized, sent to the cold wallet, and validated to show the user what is withdrawn
• How to determine which key is needed to sign? Easy for p2pk addresses, but for general scripts it is not apparent

Steps to reproduce:

• Send an amount of ERGs to any address
• While the transaction is not confirmed, do it again

The second transaction is discarded because it selected the same unspent boxes to spend.

Another feature that would be good to have is a way to cancel transactions waiting on the mempool.

Some users experience problems to connect to the primary mainnet node when sending funds:

Failed to connect to 213.239.193.208:9053

It is not clear what exactly causes the connection problem, but a setting to specify another node (and Explorer) could help and is desirable for decentralization.

https://discord.com/channels/668903786361651200/669989266478202917/856509660122447952

Let's start with the simplest P2S (ErgoScript "true" - anybody can spend the funds you send to that address) (mainnet):

4MQyML64GnzMxZgm

(testnet):

Ms7smJwLGbUAjuWQ

If it will work, you should try also a longer addresses, here's some proxy smartcontract p2s example (testnet):

J3JuxbRZSTFQrWtXY997t5vCi3dgBqWQjvd8Y5deJxQfxNF9ieaVegSSF7KGh9neCwovYasneYcKkcNXey7xsZbkiRbYLyENpoB242v7T5DQKUPLBSPCQoAVW8PzjC7d5pwdRPt82XLhMyVr3mh6pSmHkaQDej7YB7eoT3CDwVBNztZdNL61ksaSwifZQywzG5nsHiLnkYF1aW4izEY7drZxoM2TB3eksaQoNjVq5yG5QkVeEBPAg7GqtusVWg2xMLzzAS824SBB5twybJUUsoYqLtapWSow2A2miYht5dVjZs88UmynNVwLs9rv4kDhte9VXGxmcELSAKPoNvevoCBzFasMKnjRCeFjjYVhq1HhPYnzGMGeVxKD41rcgjoddqoRwBqmkcodhT1ck6za1bBsn6nnEXREvM4Pzd6TxBVQkRhaBwgHv2c2NLD8guEp4FbXoWVgHVCSN417tM4M9Td5DEXito5jdBc9kEawUwDg2X9UJ3ypGyAgXENLmVtMDa6xnNLFW2toS1f8KzaUEon

The wallet should be able to handle this long p2s addresses al

A user got the error message "Cost of transaction exceeds limit" when trying to sign a transaction containing many inboxes.

The situation should be improved so that either signing completes successfully, or a hint that this will probably happen is shown before the transaction is transferred to the cold device.

Ergo Wallet App already calcs fiat amounds on send and receive screen.

When fiat amount is set (!= 0), a switch should be implemented to enter a fiat amount and calc the ERG amount to use. The setting should be saved for the next usage.

To not hold Strings containing the mnemonic in memory longer than needed, saving SigningSecrets into db should be changed. At the moment, SigningSecrets are:

• serialized to json with Gson - this was done to have more fields than mnemonic phrase saved in the future, but is not used at the moment
• returned as a String
• this String is converted into a Bytearray, encrypted and stored

The internal processing of Gson holds the mnemonic as a String as well as the json which means it can't be blanked immediately when not needed any more.

Processing should be changed as following:

• mnemonic is not serialized any more, but converted into a byte array by Signing Secrets. Warning: ByteArrayOutputStream cannot be used, use this method
• the byte array is blanked by AesEncryptionManager after encryption
• for reading the mnemonic, SigningSecrets should get a Bytearray as well and convert the mnemonic right into SecretString
• backwards compatibility for already stored secrets: if the Bytearray starts with {, the old deserialization method (Gson) should be applied

The backwards compatibility is important so that current users of the app do not need to restore their wallets but can continue using them.

Given I have a wallet that isn't currently synced When I have synced 1 minute before current time Then I see "synced 1 minute ago"

actual result: "synced 1 minutes ago"

English is hard. really

As a user, when I send tokens, I need the application to automatically enter the minimum ERG required to send a token, in order to simplify the process. If required I can amend the ERG that is sent.

Hello, could you look in to an option in the app on the wallets tab to toggle hide/show balance per individual wallet. I really like to show case the ergo wallet to friends, family and some times strangers and i would prefer to hide my balance.

On iOS - could you make the Copy Receive Address button responsive, so once it is clicked - you would feel it (haptic?). Also - and perhaps more importantly, when you click - it would immediately copy the address and a pop up will say "copied"

The connection to Explorer is not always reliable and times out for certain addresses while others work.

It makes sense to improve the data stored in app as following to improve situation when there was a timeout or other exception:

• [ ] time of last successful sync is stored and updated for every address
• [ ] the addresses are sorted by last sync time ascending for syncing so the oldest states get refreshed first
• [ ] the overall information when the last sync was performed shows the oldest address entry
• [ ] a display is added to the wallet details list showing the timestamp for the address displayed or the oldest of all for the whole wallet

On very low end devices (that might be used for cold wallet) decrypting and encrypting mnemonic takes its time, on a Moto G 4G it is about 5 seconds. When password protection is used, this is done on UI thread and the password request screen "hangs". Situation should be improved and password screen should show a progress bar as well es encryption/decryption should be done on a background thread. Biometrics should be checked how the behaviour looks like.

No problem on iOS due to devices being fast.