lfglabs-dev / lfglabs-dev/api.starknet.quest

Adding attributes based on quest to metadata

Open
#125 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🍒 Nice to have
Dominant language
Rust
Stars
10
Forks
58
PR merge metrics
No merged PRs in 30d

Description

Description

Adding attributes based on a quest will permit people to be able to filter easily. Ideally, we want an attribute for the campaign (the Element Campaign for example) and an attribute for the NFT on itself (NFTs are in general not in a particular campaign).

Capture d’écran 2023-11-02 à 10 05 49

TO DO

  • Check whatever is the standard for attributes and categories
  • Change the API accordingly
  • Deploy testnet/mainnet
  • Ask marketplaces to Refresh all Starknet Quest Metadata (to make it possible on previously minted NFTs)

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No files or tests are named in the issue. Start by locating the metadata API and checking the standard for campaign and NFT attributes, then confirm the required changes and deployment process with the maintainers. Done means the API exposes the agreed attributes, testnet and mainnet are deployed, and previously minted NFT metadata can be refreshed by marketplaces.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend-api-design, blockchain
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.