This is a further update on our progress resolving issues related to redeeming Graphene airdrops. If you missed the last update you can find it here. We are to work on resolving most of the reported issues before proceeding with the remaining airdrops.
One of the tools we were working on is completed, which now allows us to query which Phore addresses the system reports as being redeemed. This will help us narrow down the cause of some of the reported issues, especially the “high BNB fee” error which does not allow certain users to complete their redemption. We are gathering the affected Phore addresses from the TicketTool tickets that have been reported to us, and if you are one of these people, we may be asking you to provide a screenshot of the pre-airdrop screen for each airdrop you had issues with, and your Phore addresses that had balances on them during the snapshots (in text format so that we don’t have to try to decipher and type them in from a screenshot. This information will allow us to verify both the snapshot balances the system reported to you, and the airdrop redemption statuses the system is reporting.
We are working on another tool to allow us to send GFN tokens from the minted address. Currently the only way to move tokens from the original minted address is through the use of the full airdrop system and process, so if we verify a case where the airdrop was marked as redeemed but that the user did not receive the tokens, we will need that tool to be able to complete the transfer for the affected airdrop to resolve the issue.
For people who have an issue with the system reporting the wrong amount of GFN tokens for an airdrop, we are working on correcting any errors in the snapshot balances. As we explained in the last update, this is a very time consuming process so we appreciate your patience as we work through generating new snapshots, verifying each balance is correct, comparing them to the previous snapshots, and then making adjustments to the smart contracts to correct any issues with them. We will need to complete this process for all six airdrops since similar issues could exist for each of them, and at a minimum we would need to work through the first four before we can resume the remaining airdrops.
We are still investigating the cause and solutions to the errors a few people have received while trying to generate their airdrop proof file. If you are one of these people, we may be reaching out to you to ask you to try certain things to see what might correct the issue–since no one on our team experienced this issue, we will need your help to gather information and try out potential workarounds and solutions.
Once again, we appreciate your patience and support as we work through the remainder of this process, and I want to reiterate that our team is committed to helping each Phore user get the proper amount of GFN tokens they were supposed to receive.
