You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 1, 2024. It is now read-only.
Describe the bug
TLP token claim can be initiated multiple times leading to loss of user's gas fee.
'claim' button should be pressable only once.
Video below↓
To Reproduce
Steps to reproduce the behavior:
Go to 'My investment'.
Click on 'claim'.
Complete the transaction with metamask.
After metamask confirmation is done, press 'claim' again.
Complete the transaction with metamask.
Expected behavior
The TLP 'claim' button should be pressable only once.
Screenshots
Screen.Recording.2021-01-14.at.1.29.21.mp4
↑Transaction No1.
↑Transaction No2.
Desktop (please complete the following information):
OS: Mac OS
Browser Chrome
Version Version 87.0.4280.141 (Official Build) (x86_64)
Additional context
First transaction: 0x2c59407e93835f3083d8a2f1dbc0b7b3f9a305abc8363abc14070465832b41f7
Second transaction: 0x081969f8f5bea42baa45388f80a08575f1593f97d2dca9a3f070b9f7fb648f64
the ↑Transaction No2. is not giving you more Link token.
"play with fire and you'll get burned"
you can use the withdrawal investment function as many times as you want.. but you get the assets only one time.
but we can lock the button with some logic later.
thanks for the report.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
TLP token claim can be initiated multiple times leading to loss of user's gas fee.
'claim' button should be pressable only once.
Video below↓
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The TLP 'claim' button should be pressable only once.
Screenshots
Screen.Recording.2021-01-14.at.1.29.21.mp4
↑Transaction No1.
↑Transaction No2.
Desktop (please complete the following information):
Additional context
First transaction: 0x2c59407e93835f3083d8a2f1dbc0b7b3f9a305abc8363abc14070465832b41f7
Second transaction: 0x081969f8f5bea42baa45388f80a08575f1593f97d2dca9a3f070b9f7fb648f64
Wallet address
0x348c0a7a93F86E451971DFC89D2A74519bBaEBfd
The text was updated successfully, but these errors were encountered: