-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
feat: Holder of drop page iteration #9027
Conversation
✅ Deploy Preview for koda-canary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
AI-Generated Summary: This pull request introduces changes that aim to enhance the NFT minting process. Some notable modifications include:
|
I have one account that had previously minted one chroma using a motherboard nft, then i asked Exez to lend me one of his motherboard NFTs to check if i could be eligible to mint another Chroma. my account: NFT he lended to me: https://canary.kodadot.xyz/ahp/gallery/50-357 yet it does not identify that i have a second motherboard nft: |
@prury from what I can see logic was ok, both nfts are claimed, as per the design check again also changed a bit chain balance code which affected thanks |
It is non-blocking - https://github.com/kodadot/private-workers/issues/43 |
Probably will go to another release or @hassnian if you can resolve conflicts under 30 min? :D |
on it |
Code Climate has analyzed commit bc2b1c8 and detected 2 issues on this pull request. Here's the issue category breakdown:
View more on Code Climate. |
|
Thanks! |
😍 Perfect, I’ve sent the payout 🪅 Let’s grab another issue and get rewarded! |
PR Type
Needs QA check
Needs Design check
Context
Did your issue had any of the "$" label on it?
Screenshot 📸
connect wallet
requirements not met
ready to mint