Common issues encountered using the Lamden wallet and how to solve them
Topics Covered:
- Lamden Wallet Basics
- Linking Telegram account to Lamden Wallet
- New Account created when connecting to dApp
- Transaction Errors:
- Transaction sender has too few stamps for this transaction.
- AssertionError(‘Not enough coins to send!’,)
- Retry attempts 10 hit while checking for Tx result
- Transaction timestamp is too old. Submit again.
- TypeError: Failed to fetch
Lamden Wallet Basics
Lamden wallet basics are covered here — Lamden Wallet Basics. Which deals with wallet design, navigation, transfers, stamps(gas), and backups.
Linking Telegram account to Lamden Wallet
A handy article on how to do this here
New account created when connecting to dApp
This usually happens when you use a new device, it does not recognise the device so creates a new account. To fix this proceed as follows:
1. Let the dApp create the new account. Skip the option to add funds as we will delete this whole account when we are done
2. In the Lamden Wallet click on the old account name
3. You will next screen at the top of the page, click Options.
4. A modal will open, from the dropdown Link This Account To, select the dApp you want to link to this account
5. Confirm the pop-up that appears to associate this ‘old’ account back to the application
6. You can now delete the empty account that was created at Step 1.
Transaction sender has too few stamps for this transaction.
This occurs when you don’t have enough TAU in the account to process the transaction. TAU is converted as needed to be used as stamps and each account you send from within your wallet needs some TAU for this.
If the concept of multiple accounts in 1 wallet is confusing you should read the Lamden Wallet Basics article which covers this design feature and how the Wallet and all accounts are visualised.
AssertionError(‘Not enough coins to send!’,)
The full error appears as: This transaction returned a non-zero status code AssertionError(‘Not enough coins to send!’,)
This appears when you tried to send tokens that are not in that account, or you tried to send too many which you don’t have. Check to make sure you have enough of that particular token in the account you are sending from.
Note: If transferring TAU, this error will appear if you try to send all your TAU and leave nothing behind for stamps (gas).
If the concept of multiple accounts in 1 wallet is confusing you should read the Lamden Wallet Basics article which covers this design feature and how the Wallet and all accounts are visualised.
Retry attempts 10 hit while checking for Tx result
There seems to be a bug in the webserver that is allowing invalid transactions through, such as those from wallets that do not have enough stamps. This bug does not affect security or performance. If you are seeing the “10 attempt tried” error, wait a few minutes and resubmit your transaction.
Transaction timestamp is too old. Submit again.
This occurs when the client time is out of sync with the server time by too much. A simple syncing of your PC clock is usually all that is needed.
Windows 10
1., Right-click clock bottom right of screen
2. Select Adjust date/time
3. Scroll to Synchronise your clock, click Sync Now
Note: On Windows devices this small app can help keep your clock synced if you run into this issue a few times: http://timesynctool.com/
Linux distros
From the command prompt type timedatectl
TypeError: Failed to fetch
This one does not occur often, but when it does it has been caused by the permissions for the wallet extension in your browser not allowing functions to be performed. If you are using pop-up blocking software make sure the wallet can operate freely. Similarly if using browsers like Brave, it has been known to cause instability with some dApps (disable ‘Shield’ for the particular dApp website).
Keep adding to this list to help others!
DM me (Clay99) in telegram if you have more errors to add to the list
