Second Airdrop Distribution Schedule for Eligible IOST Holders on 27 August 2025 at 05:00 PM (GMT+7)

Modified on Tue, 26 Aug at 1:04 PM

To align with the operations plan issued by the IOST issuer (reference), Bitkub Exchange will distribute the IOST second airdrop to eligible participants who met the criteria set by the IOST team. Please see the details below.


Eligibility for Airdrop Participation


Eligible participants are those who held 1,000 IOST or more in their Bitkub wallets at the snapshot time which took place at 07:00 AM (GMT+7) on 15 March 2025.


Schedule

  • Bitkub Exchange processes the second IOST airdrop to the eligible participants
    27 August 2025 from 05:00 PM (GMT+7) onwards*


IOST Airdrop Distribution Details

  1. * Due to the large number of eligible users, the airdrop distribution process may take up to 7 days to complete from the aforementioned distribution schedule.

    • If you do not receive the tokens from the airdrop after the 7-day distribution period, please contact Bitkub Support for further assistance.

  2. Bitkub Exchange will distribute IOST tokens to holders who met the eligibility criteria set by the IOST issuer. The tokens will be distributed gradually according to the allocation received from the IOST team over a total period of 48 months.

  3. Bitkub Exchange may issue further announcements regarding the distribution details for subsequent distributions. Please follow our announcements closely for any updates.


Remarks:

  • The distribution schedule and allocation ratio are subject to change based on the IOST team's operations and processes.

  • Bitkub Exchange reserves the right in its sole discretion to amend or change these announcement details, and we will notify you further if there are any changes.


Thank you for your continued support.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article