-
Notifications
You must be signed in to change notification settings - Fork 154
adding faq/bug fix to bottom of delegation docs #84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey thanks! Suggested some edits to the explanation.
pages/en/delegating.mdx
Outdated
|
||
*When I try to delegate my transaction in MetaMask appears as "Pending" or "Queued" for longer than expected. What should I do?* | ||
|
||
At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts. For example, a user may attempt to delegate and run out of ETH to cover the gas costs to complete the transaction, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, subsequent transactions can be attempted by a user, which pushes the initial transaction into a queue and raises the most recent attempt(s) to "Pending" in place of the initial attempt. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful. The cheapest known fix to this bug is restarting the browsesr (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users that have encountered this issue and have reported successful transactions after restarting their browser and attempting to delegate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some edits for accuracy:
delegate and run out of ETH to cover the gas costs to complete the transaction
...delegate with an insufficient gas fee, given current prices...
which pushes the initial transaction into a queue and raises the most recent attempt(s) to "Pending" in place of the initial attempt
... but these will not be processed until the initial transaction is mined, as transactions for an address must be processed in order.
the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful
... the cancellation transactions will incur gas fees.
The cheapest known fix to this bug
A simpler resolution
Thank you, Adam. I've implemented these suggestions into the docs and pushed again. |
pages/en/delegating.mdx
Outdated
|
||
**When I try to delegate my transaction in MetaMask appears as "Pending" or "Queued" for longer than expected. What should I do?** | ||
|
||
At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts. For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, subsequent transactions can be attempted by a user, but these will not be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful. A simpler resolution to this bug is restarting the browsesr (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users that have encoA simpler resolutionuntered this issue and have reported successful transactions after restarting their browser and attempting to delegate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry last one on this - seems to be a typo
encoA simpler resolutionuntered
Hey Adam. I fixed the typo in that last sentence. I think we should be good to go, but let me know if there is anything else I can address. |
LGTM, thanks! |
Brandon (UX/Design) found this bug a couple weeks ago while attempting to delegate and while scanning Discord for other data. Brandon shared this with the Product Engineering team (Nas) in Asana and the Graphtronauts on Telegram before Adam Fuller suggested that this FAQ/Bug would be best shared on the docs page.