For the first launch-priority team tokens, WC26 main-token holder eligibility can be checked through three unannounced snapshots before that team token goes live. There is no public countdown and no fixed date to farm; every allocation still needs a reviewed proposal and published evidence.
If the exact snapshot time is announced, wallets can farm the allocation window seconds before a launch. Random checks make eligibility depend on holding WC26 main token before the selected favorite team token is released.
First random holder check for the selected team-token allocation campaign. It can happen at any point before that team token goes live.
Second independent check for the same team-token campaign. The block is not announced before capture.
Final random check before the allocation proposal is reviewed. The exact capture point stays sealed until evidence is published.
Present in all three random checks. Strongest eligibility signal.
Present in two of three checks. Review weight remains active.
Only one check. Weak eligibility signal for review.
No random-check presence. Not eligible for this campaign review.
The exact snapshot block is not announced. A holder only sees the evidence after review, so last-second farming becomes unreliable.
Each priority team-token campaign can use three separate WC26 holder checks before that team goes live. Timing one moment is not enough.
Minimum WC26 platform-token thresholds can be required before scoring. Dust-wallet farming becomes capital-prohibitive.
Wallets funded from the same source within a narrow window are flagged and may be excluded at operator discretion. Movement patterns are audited before allocation.
Allocation proposals only move forward after review. Snapshot evidence, exclusions, and campaign rules are published before any allocation action.
Every snapshot record and allocation transaction is published when safe to reveal. The full eligibility JSON is released after review so third parties can replicate the scoring.