Graphene Airdrop Update #1
Based on community feedback, we have decided to postpone the remaining Graphene airdrops while we continue resolving a few types of airdrop issues that a fraction of users have had while trying to redeem their airdrops. We will provide the community with an progress update within 7 days.
We will make another announcement once the remaining airdrops have been rescheduled.
NOTE: While troubleshooting these issues with the community, we have determined one common reason for the high BNB fee error (e.g., 0.7 BNB) is not including the correct airdrop number in the command used to generate the airdrop proof file. Trying to redeem the same airdrop twice, or trying to redeem an airdrop that has not been released will not work and would show the high BNB fee estimate on the last step (and fails if it is attempted).
While this may not be the root cause for all users seeing this type of error, if you are experiencing this, please try generating the airdrop proof file again, making sure you include the correct airdrop number for each redemption. Here are examples for the first three airdrops:
For airdrop 1: makeairdropfile “0xxxxxxxxxxxxxxxxxx” 1 “airdrop1.txt”
For airdrop 2: makeairdropfile “0xxxxxxxxxxxxxxxxxx” 2 “airdrop2.txt”
For airdrop 3: makeairdropfile “0xxxxxxxxxxxxxxxxxx” 3 “airdrop3.txt”
As outlined in the airdrop guide, you can specify the full path and filename to set the location for it to be created, but it is not required, and if you omit the path, the file would be created in your Phore data directory. The Phore Core Wallet troubleshooting FAQ shows the default location by platform for the Phore data directory.
Thank you for your patience and feedback, and we will continue to work on resolving each issue. If you are having an airdrop redemption issue and have not yet done so, please open a ticket using the TicketTool system we set up in the Phore Discord, and we will follow up with you to help get your issue resolved.