Skip to content
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

Claim page #1333

Closed
3 tasks
gagdiez opened this issue Oct 17, 2024 · 0 comments · Fixed by #1341
Closed
3 tasks

Claim page #1333

gagdiez opened this issue Oct 17, 2024 · 0 comments · Fixed by #1341
Assignees

Comments

@gagdiez
Copy link
Collaborator

gagdiez commented Oct 17, 2024

Background

The developer portal now allows people to create linkdrops, but we still need to redirect people to "my near wallet" in order to claim them.

The problem is that "My NEAR Wallet" does not display the drops correctly, for example, if an NFT is to be claimed, it will only show that the user wants to "Claim 0 NEAR". On claiming, the user will receive the NFT, but this is very poor UX.

User Story

As a user I would like be able to see what I am about to claim, and be redirected to my preferred wallet to claim it.

Acceptance Criteria

  • A new /claim page needs to be created, which takes the claim private key as an URL fragment (e.g. /claim#
  • The claim page must show what is going to be claimed (the NFT image, or the tokens + amount)
  • The claim page must allow the user to choose which wallet to use to claim the linkdrop, and redirect accordingly

Resources & Additional Notes

Priority

  • 🟠 P1 : High
@github-project-automation github-project-automation bot moved this to NEW❗ in DevRel Oct 17, 2024
@gagdiez gagdiez moved this from NEW❗ to Backlog 🥶 in DevRel Oct 17, 2024
@thisisjoshford thisisjoshford moved this from Backlog 🥶 to In Progress 🏗️ in DevRel Oct 28, 2024
@gagdiez gagdiez moved this from In Progress 🏗️ to In Review 👀 in DevRel Nov 19, 2024
@github-project-automation github-project-automation bot moved this from In Review 👀 to Shipped 🚀 in DevRel Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants