# Don’t just watch the points: the real nodes of these 3 early projects today

Today we look at **Canopy Network, Gyndore, Flop Labs**: one that has entered the points submission phase, one that has just launched public testing with the season closing soon, and one that first laid out the Q4 testnet and its participating roles.

Why now: all three have shown verifiable new nodes in the past few days—not just a “possible token launch.”

The maximum risk is also different: Canopy is missing registration or entering a fake portal by mistake; Gyndore is mistaking test quantity for allocation criteria; and Flop is spending too much time or using too much hardware before the rules are set.

## Canopy Network: What existing users need to do now is register, not make up刷（top-up）

**Key takeaway in one sentence:** The testnet points submission entry is now open. Submitting is a necessary step for potential allocation evaluation, but it does not mean you will receive an allocation.

**Why now:** On August 26, the official explicitly required using the original testnet EVM wallet, choosing the Canopy receiving wallet, and submitting points; newly earned points can be submitted again. The snapshot only confirms the mainnet phase and there is no precise time yet, so existing users who actually have points should not keep delaying.

**Metrics worth tracking:** First, whether there are records that can be verified after points submission; second, whether the official publishes the deadline or snapshot time; third, the sybil (witch) filtering, the mainnet date, and the final redemption rules.

**Pitfalls I will avoid:** I won’t enter the claim page via search ads or DMs, and I won’t do high-frequency interactions just temporarily to “qualify.” This step matters for existing users, but may not have the same value for brand-new wallets with no history.

## Gyndore: The public test has just started, yet the season is already in a phase of consolidation and observation

**Key takeaway in one sentence:** The overlap between the Base Sepolia public test and the tail end of DropWave Season 1 means that fully covering product features carries more informational value than trying to manufacture a single transaction volume.

**Why now:** Recently, the official has launched redemption, concentrated liquidity, staking, asset portfolio and unlocking flows, and disclosed that within the past 24 hours the test volume exceeded 100 million and participation wallets exceeded 1,500. Hype is already building, but when points will be redeemed and how inheritance works are still not fully disclosed.

**Metrics worth tracking:** First, whether different functions unlock Chips; second, GynPoints updates and daily limits; third, the clear end of Season 1 and the rules for redemption and data reset.

**Pitfalls I will avoid:** I won’t buy so-called test tokens, nor will I loop to amplify meaningless transaction volume. Testnet assets may be reset, and transaction volume is not the same as future allocation. Naturally completing mint, swap, LP, and stake and submitting real feedback will leave a clearer trail.

## Flop Labs: It’s worth establishing contribution records now, but not worth placing heavy early bets

**Key takeaway in one sentence:** For the first time, the project puts together the Q4 testnet airdrop, Agent DID identity, the roles of miners/validators/agents, and the initial allocation framework.

**Why now:** In the past few days, the official required agents to create unique DIDs, make useful verifiable contributions, and explicitly outlined the direction of the Q4 2026 testnet. The initial framework provides airdrop categories for different network roles, but it is still labeled as a draft.

**Metrics worth tracking:** First, the full testnet dates and node thresholds; second, how DID, code, or tool contributions are verified; third, whether draft allocation, locking, and anti-sybil rules are adjusted.

**Pitfalls I will avoid:** I won’t copy templates to spam social tasks, and I won’t buy servers when hardware requirements are unknown. A DID is just a continuous identity, not a qualification credential; what you should truly accumulate are traceable tools, documentation, bug reports, or agent workflows.

## A collectible decision framework

When you encounter new points or a testnet, ask four things first: **Are the nodes from the official, what was newly added today, can the action be kept as proof at low cost, and what is the maximum loss if it fails.** For existing users encountering a query tool or a submission window, prioritize verifying eligibility; for new testnets, prioritize going through the full product journey; for projects whose rules haven’t been published yet, only make contributions that are reusable. If the answers are only “the hype is high, there are lots of points, everyone is doing it,” but there’s no deadline, product changes, or verification methods, keep observing—don’t replace judgment with transaction volume.