# Don’t Focus Only on Points: 3 Early-Stage Projects Hit Key Milestones Today

Today, we’re looking at Predict.fun, GenLayer, and Elyon Chain: one announced a 7% Season 1 allocation, one unexpectedly reopened registration, and one outlined an 8% allocation for the community and early participants.

They’re worth watching now because final points, a short-term registration window, and a public testnet are all coming together over the next few days—not because of vague rumors that they “might launch a token.”

The biggest risks also differ: the claim mechanism could reduce the nominal allocation, the registration window could close suddenly, and the testnet rules have not yet been fully disclosed.

## Predict.fun: Moving from speculation to “verifying results and choosing a claim option”

**In a nutshell**: The team has confirmed that Season 1 allocations will account for 7% of the fixed total supply. Final points and the claim date are expected to be announced soon. Existing users should focus on checking their status, not generating more trading volume.

**Why now**: The final Season 1 snapshot is complete, and Season 2 has begun. In the new season, LP points are no longer based solely on how long orders stay on the book; actual fills now count too. There are two claim options: claim 35% of your nominal allocation immediately, or receive 100% vested over 12 months. There’s also a Pre-TGE sale milestone on October 29, so fake checkers and impersonation pages are likely to proliferate.

**Metrics worth tracking**:

- Whether the final Season 1 points and official claim date are announced as expected;

- How the share of actual fills and time orders remain on the book jointly affect Season 2 points;

- Whether the terms and switching deadline for the two options remain unchanged once claims open.

**Pitfalls I’d avoid**: I wouldn’t take loss-making trades just to earn Season 2 points, or mistake “claim 35% immediately” for a full unlock. Directional, inventory, and slippage risks in prediction markets may far outweigh the value of the points themselves.

## GenLayer: The window has reopened, but focus on completing registration, not adding interactions

**In a nutshell**: Airdrop registration, originally set to close on October 26, was officially reopened for “a few days” on October 27, with no precise new deadline provided.

**Why now**: This is the most time-sensitive milestone of the three. For users with a history of testing, building, or community contributions, their registration status matters more than adding new interactions. For new wallets with no contribution history, a burst of last-minute activity may not make up for past contributions and could instead increase the risk of being linked to other wallets.

**Metrics worth tracking**:

- Whether registration is still open and whether the team provides a precise deadline;

- Whether eligibility confirmation, allocation results, or next-step notifications appear after registration;

- Whether the team provides further details on the TGE, claims, and regional restrictions.

**Pitfalls I’d avoid**: I wouldn’t access the registration page through DMs or search ads, and I wouldn’t transfer funds, enter a seed phrase, or grant unlimited approvals during registration. Successful registration doesn’t guarantee an allocation. Screenshots and timestamps are more useful than repeatedly connecting your wallet.

## Elyon Chain: The 8% figure is clear, but eligibility details are still missing

**In a nutshell**: The team has announced that 80 million ELN—8% of the total supply—will be allocated to the community and early participants, and has brought the public testnet, native bridge, and block explorer into focus.

**Why now**: The team has recently highlighted early network interactions, test RPCs, relay routing, and deploying test contracts. This makes participation more concrete than simply “following social media and waiting for a snapshot,” but the snapshot date, minimum requirements, points formula, and anti-Sybil rules have yet to be disclosed.

**Metrics worth tracking**:

- Whether the official task page, chain parameters, and eligibility criteria are published;

- The stability of the testnet bridge, RPC, and block explorer, and whether data gets reset;

- Whether a leaderboard, badge criteria, or clear snapshot rules are announced.

**Pitfalls I’d avoid**: I wouldn’t assume every task in a community guide is an official requirement, or use multiple linked wallets to repeat the same steps. A better approach is to use an isolated wallet for a small number of genuine tests, save transaction hashes, and submit reproducible bug reports.

## A Collectible Decision Framework

When you encounter a new airdrop signal, filter it through four checks: **Is the allocation explicitly confirmed by the official team? Is there a time-bound deadline? Can your actions leave verifiable records? Is the worst-case cost acceptable?** If only one or two checks pass, wait and observe. If you have a history of contributions and the window is about to close, prioritize checking your eligibility. For testnets whose rules haven’t been fully disclosed, stick to low-cost, genuine interactions. The projects worth acting on today aren’t necessarily the ones generating the most buzz, but those where “you can’t make up for missing the milestone later.”