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

[Spike] NFT Whitelist/Allowlist/Less spam -- ("Make NFT"s highly regarded only") #7763

Open
twblack88 opened this issue Sep 18, 2024 · 0 comments

Comments

@twblack88
Copy link
Contributor

Overview

Problem: Our NFT's just keep getting bombarded with spam instead of the handful of users who may want a vanity avatar. It also likely expands costs in some way that's annoying.

Solution: There are a Couple paths

  1. Make NFT's on request only, in which case we need an NFT import UX for that tab and we don't render them on default. Probably a performance improvement too.
  • one way is just use whitelist only and then make users manually click "auto-detect" and select the ones they want from outside the list from alchemy API.
  • we hit a collection and then use a modified JSON script passing the excludeFilters[]=SPAM
     --url 'https://eth-mainnet.g.alchemy.com/nft/v3/docs-demo/getCollectionsForOwner?owner=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045&pageSize=100&withMetadata=true&excludeFilters[]=SPAM' \

so only pass collections and then let them choose ones they own.

  1. Make NFT"s filtered only

References and additional details

Wallet Connected

something kind of along these lines. what data can we plug into this modal, how scalable is that for many NFT types. Do we do it per chain etc.

Acceptance Criteria

Spike into the data types
play with the best UX path

Need By Date

No response

Screenshots/Mockups

No response

Estimated effort

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant