You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the ability to poll every X number of seconds to fetch all NFTs on a specific wallet address. Find all NFTs that belong to a specific contract from these NFTs. Match the NFTs from this new list with the list of NFTs from the original Minting process. If a NFT is in the original minting file, but it is not in the list retrieved, then the NFT should be revealed.
Once a NFT has been revealed, it should be recorded and future checks should not try to reveal the NFT again as it should first check the recorded files to check if it was revealed before or not.
Basic example
As a user, I have minted a 1000 NFT collection to contract ABC against wallet 12345.
Check wallet 12345 and find all NFTs available from contract ABC and add it into a list.
Loop through the minted NFT collection file and check if NFT in the list can be found in the list retrieved in the previous step.
If it can't be found, then reveal the NFT and write out a new reveal json file. If the NFT can be found in both lists, then skip the file as the NFT was not sold or transferred and still belongs to the original owner.
Motivation
Users can deploy a script that they leave running on a pc, laptop, cloud server that will manage their reveal processes. This will give users time to focus on the rest of the work like community building and not be concerned users' NFTs not being revealed once purchased.
The text was updated successfully, but these errors were encountered:
The Reveal script has been implemented from the codeSTACKr codebase into this code base. I have not been able to test this on my end as this does not work on Rinkeby network.
Summary
Add the ability to poll every X number of seconds to fetch all NFTs on a specific wallet address. Find all NFTs that belong to a specific contract from these NFTs. Match the NFTs from this new list with the list of NFTs from the original Minting process. If a NFT is in the original minting file, but it is not in the list retrieved, then the NFT should be revealed.
Once a NFT has been revealed, it should be recorded and future checks should not try to reveal the NFT again as it should first check the recorded files to check if it was revealed before or not.
Basic example
As a user, I have minted a 1000 NFT collection to contract ABC against wallet 12345.
Check wallet 12345 and find all NFTs available from contract ABC and add it into a list.
Loop through the minted NFT collection file and check if NFT in the list can be found in the list retrieved in the previous step.
If it can't be found, then reveal the NFT and write out a new reveal json file. If the NFT can be found in both lists, then skip the file as the NFT was not sold or transferred and still belongs to the original owner.
Motivation
Users can deploy a script that they leave running on a pc, laptop, cloud server that will manage their reveal processes. This will give users time to focus on the rest of the work like community building and not be concerned users' NFTs not being revealed once purchased.
The text was updated successfully, but these errors were encountered: