DeepLink Protocol Announces Airdrop for DBC Holders on DeepBrain Chain

DeepLink Protocol has unveiled an airdrop event targeting holders of DBC tokens on the DeepBrain Chain AI Public Chain. The initiative allows eligible participants to receive DLC tokens at a 1:1 ratio, reinforcing the protocol’s ecosystem.

Airdrop Details

The airdrop will follow a two-snapshot model:

• Snapshot 1: March 19, 2025, at 15:00 (Singapore Time)
• Snapshot 2: March 26, 2025, at 15:00 (Singapore Time)
• Distribution: DLC tokens will be distributed within one week after the second snapshot. The amount will be based on the lower of the two snapshots.

Eligibility Criteria

To qualify, participants must hold DBC tokens in a DBC EVM wallet (starting with 0x). Wallets on the DBC mainnet (addresses starting with 5) are not eligible.

Additionally, participants must hold at least 100,000 DBC and 100,000 DLC to receive the airdrop. They must also maintain a minimum of 20% DLC relative to their DBC holdings.

For example, a holder with 10,000,000 DBC needs at least 2,000,000 DLC to claim the full airdrop.

Token Vesting and Unlock Schedule

• First Unlock: Begins 180 days after the snapshot
• Unlock Period: Gradual release over 50 months
• Monthly Unlock Rate: 2% unlocked every 30 days

How to Participate

Participants must store their DBC EVM tokens in a decentralized wallet like MetaMask, ImToken, or TokenPocket. Tokens held in centralized exchanges, including Gate.io, will not qualify for the airdrop.

Users can obtain DBC EVM Chain tokens by either purchasing them on Gate.io and transferring them to an eligible wallet or migrating them from the DBC mainnet via the official dbcwallet.io platform.

Implications for Holders

The airdrop incentivizes long-term engagement within the DeepLink ecosystem, positioning DLC as a key asset in Web3, AI, and AAA gaming applications. By requiring a DBC-to-DLC holding ratio, the event also encourages balanced token distribution and sustained ecosystem growth.

Holders have until March 26, 2025, to position their tokens correctly before the final snapshot.