Graphene Airdrop Update #5

3 min readJun 27, 2022


Thanks to everyone in the Phore community who helped verify the corrected snapshots. Based on user feedback and follow up, we are confident that the snapshot data is now accurate, and we have adjusted the 4th airdrop BSC smart contract based on comparing the token values used in the first three airdrops with the corrected data to bring each Phore address allocation in line with what should have been given. The airdrop website has been updated to reflect these changes.

We are now preparing to release the 4th Graphene airdrop to Phore users, with a target date one week from now (July 3rd).

Before we mint the tokens to release this airdrop, we are allowing some time for the community to verify that the 4th airdrop looks correct for your address(es). To verify this, you can follow the airdrop instructions up to the Pre-Airdrop Summary screen (do not try to redeem the airdrop yet since that will not work until the tokens are minted), using airdrop 4 when generating your Phore wallet airdrop file.

As a reminder, each airdrop is intended to allocate 10 / 6 GFN tokens (1.666) for each PHR held on the snapshot block. As we stated in the last update, the blocks used for the snapshots were:

  • Snapshot 1 — Block 1,817,125
  • Snapshot 2 — Block 1,856,572
  • Snapshot 3 — Block 1,896,008
  • Snapshot 4 — Block 1,935,435
  • Snapshot 5 — Block 1,971,468
  • Snapshot 6 — Block 1,999,951

The result on the Pre-Airdrop Summary should now show that for any PHR addresses that did not receive enough cumulative GFN tokens in the first three airdrops, the 4th airdrop will receive extra tokens to grant the correct total number of tokens for airdrops 1–4 based on the corrected snapshots. If you think your airdrop 4 allocation looks incorrect, please open a ticket using the ticket tool in the Phore Discord.

Note that for addresses that received more than the intended tokens for airdrops 1–3, the airdrop 4 amounts have been reduced to bring the allocations for those addresses back to the intended amount as well, so some users may see a net reduction from the original airdrop 4 allocation.

Also note that we have not applied any adjustments to the smart contracts for airdrops 5 and 6 yet–once we see that airdrop 4 redemptions are going smoothly, we will correct those allocations, and assuming we don’t see significant issues with airdrop 4, we plan to proceed with those airdrops at two week intervals following airdrop 4.

These adjustments should address the issues some users have seen when they received the wrong number of GFN tokens. For any users that are unable to complete their airdrop 1–3 redemptions at all, we will work directly with those users to verify their airdrop information and get those issues resolved. To allow us to resolve those issues, we have added an allocation of 2 million GFN tokens to airdrop 4 so that we are able to send GFN tokens to users with verified issues of not being able to redeem tokens. If you have that type of issue, please open a ticket with the TicketTool in the Phore Discord and we will let you know the information we will need from you for verification.

Once our team has redeemed those tokens, we will provide the BSC address for transparency so that the community can see how many tokens have been awarded, and how many remain. The community can discuss and decide what we should do with any remaining tokens from this allocation after the redemption periods are completed–burning them is perhaps the default option, and we are open to other ideas as long as they do not create legal/regulatory issues.

We really appreciate your patience and support as we have been working through these issues, and please know that we have been as frustrated as anyone that it has taken as long as it has to get everything resolved. We want to do everything possible to help ensure the remaining airdrop redemptions go smoothly and provide accurate overall token allocations.




Scalable sharding Blockchain written in Go. Smart Contracts, Dapps, DeFi. Interoperable. Customized shards optimized for different use cases. Do it all.