# RakeIn Airdrop Ticket System Design **Published by:** [347098.eth](https://paragraph.com/@347098/) **Published on:** 2022-08-23 **URL:** https://paragraph.com/@347098/rakein-airdrop-ticket-system-design ## Content As last post said, we will open the airdrop registration on Sept 1st, the end date is around Sept 14th, so no hurry:) RakeIn Token(RAKE) Airdrop & Presale Schedule 🎉🎉🎉Collect tickets to gain the airdrop and presale🎉🎉🎉 medium.com Today we’d like to reveal more about our airdrop ticket system design. About RakeIn Airdrop The concept of airdrop in cryptocurrency is straightforward. RakeIn will drop small amounts of free tokens to people’s wallets. People can apply for the airdrop directly from our airdrop registration website. The RakeIn registration process is so simple, and there are no tedious steps as in specific tokens. Airdrop Registration Process The Airdrop Ticket System Design RakeIn airdrop event is for 3 purposes: Introduce more audience into our community Reward our early community members Reward the Chromia Ecosystem supporters With these purposes, we design the calculation formula as : Tickets= (1 + referral_count) * early_twitter_follower_factor * CHR_boost_factor referral_count : the times the applier referred the friends to join the airdrop event. (The applier will get the dedicated referral URL to spread when registration) early_twitter_follower_factor : the earlier the applier followed our twitter account @Rakein8 , the bigger factor the applier will get. The translation table is : How to calculate early_twitter_follower_factor CHR_boost_factor: The more $CHR the applier hold, the bigger factor the applier will get. We will scan BSC and ETH chain to get $CHR amount of the applier wallet address(including the staked amount) at the end of the registration at a specific time. ## Publication Information - [347098.eth](https://paragraph.com/@347098/): Publication homepage - [All Posts](https://paragraph.com/@347098/): More posts from this publication - [RSS Feed](https://api.paragraph.com/blogs/rss/@347098): Subscribe to updates