Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Approval timing issues

Open
  • Is something wrong?
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
blockchain, frontend

Research direction

Start by tracing the panel's pending state, the MetaMask transaction completion callback, and the core blockchain polling loop described in the issue. Reproduce approval timing with an unenabled GEN or NEC token, then ensure the panel does not return to the enable screen during approval and reaches the post-approval view once approval is detected.

Written by the indexing model from the issue text.

Description

Situation
  • The user has not enabled their token (GEN or NEC for the respective schemes)
  • The user presses the 'Enable' button on the 'Please enable' screen shown
  • The panel goes into the pending state
Issues
  • Panel can return from the pending view back to the 'Please enable' screen, confusing the user
  • The panel will update to post-approval view once the core blockchain polling loop returns new data.

This is due to how async operations are handled - the pending state is set when we start the TX in metamask, and stopped when that returns as done.

This can happen at a different time then the core polling loop, which checks if the user has enabled their token. If they have, it shows the post-approval view in the panel.

Perhaps ideally, we'd see if the transaction returned on the core polling loop.

As a stopgap, you could add in a call to see if the user has approved token after the metamask call, and then return pending after that.

Dominant language
TypeScript
Stars
1
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dOrgTech/NectarDAO-Bootstrapper

All issues in dOrgTech/NectarDAO-Bootstrapper

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.