CryptoRank's upcoming list holds 109 token sales as of November 10, 2026, and only three of them have a date. The rest are TBA. That split is the story of this month: a long queue of launches, almost none of which will tell you when they are coming until they are nearly here. For a node operator, that is not a market signal, it is a readiness problem. Dates land with little warning, traffic spikes on launch day, and the teams that survive it are the ones whose RPC, monitoring, and support were ready before the date was announced. This post reads the November cluster through that lens: what is actually dated, what the clusters are, and what to prepare.
All figures here are CryptoRank listing data as of November 10, 2026, and they may change. If you want the method behind this kind of read, our CryptoRank trending read and our TBA launch wave guide cover the same approach in more detail. This post is about the November list specifically, not about whether any token is worth buying. That is not a question infrastructure can answer.
The three dated launches
Only three sales on the list carry a date. KieDex, ticker KDX, has an IDO dated November 10 with a $500,000 raise listed. It is the nearest event on the board, dated today. Cineflicks, ticker CNF, has a pre-sale dated November 24, with no raise figure listed. Battle Town, ticker BTOWN, has an ICO dated January 1, 2027, with a $13.51 million raise listed. Everything else on the list is TBA, including several names that have been sitting there for weeks.
The dated three are useful because they give you a calendar to plan around, but they are also a warning about the rest of the list. A TBA listing is not a delayed launch, it is a launch that has not announced a date yet, and when the date lands it can land fast. The right response is not to watch the calendar, it is to be ready for a date to appear. That means capacity, failover, and monitoring that are already in place, not a plan to build them when the announcement drops.
The clusters: AI infra, GameFi, and the big ICOs
The TBA list clusters into three groups. The first is AI infrastructure. NOYA.ai, ticker NOYA, lists an IDO and pre-sale with a $1.55 million raise on Huostarter. Friendly Giant AI, ticker GIANTAI, lists an IDO with a $1.40 million raise across Eesee and other launchpads. SecantX AI, ticker SECA, lists a private sale and IDO with a $500,000 raise on KingdomStarter. These are infrastructure-adjacent projects, and they are the ones most likely to need nodes, RPC, and monitoring when they launch, because their products are services that run on infrastructure rather than games that run on hype.
The second cluster is GameFi. Hero Arena Play, ticker HAP, lists an IDO with a $300,000 raise on Poolz Pad. Rekt Games, ticker RKT, lists an IDO with a $300,000 raise on BinStarter. BOREDTOPIA, ticker BCT, lists an IDO with a $400,000 raise on GameFi. Game launches spike differently from infrastructure launches: the traffic comes in a burst at the moment the game opens, and it is mostly wallet connections and transaction submissions rather than steady RPC reads. If you serve a game launch, your rate limits and your failover matter more than your raw capacity, because the spike is short and sharp.
The third cluster is the larger ICOs. Dlicom, ticker DLI, lists an ICO with a $2.50 million raise. Chainers, ticker CHU, lists an ICO with a $2.00 million raise. These are the biggest raises on the board, and they are also TBA, which means their launch dates are the least predictable and their launch-day traffic is the hardest to forecast. A large raise does not mean a large launch-day load, and a small raise does not mean a small one. The raise is a fundraising figure, not a traffic forecast, and treating it as one is a mistake.
What TBA means for operators
A list that is mostly TBA is a list that rewards readiness over prediction. You cannot schedule around a date that does not exist, so you build for the pattern instead: launches happen, they spike, and the spike is short. The operators who handle this well keep a baseline of spare capacity at all times, keep their failover tested, and keep their alerts tuned so a spike pages a human instead of failing silently. The operators who handle it badly wait for a date, and then discover that the date arrived while they were waiting.
There is also a verification habit to build. Before you build anything for a listed project, check its own site and docs, not just the listing. Confirm the chain it runs on, whether it needs a node at all, and whether the launchpad and date on the listing match what the project itself says. Listings go stale, projects change launchpads, and dates move. A listing is a lead, not a fact. Our token unlocks guide makes the same point about unlock schedules: always check a second source before you quote a figure as fact.
The operator readiness checklist
Five things should be true before any launch date lands. One, your RPC has rate limits, so one client cannot take the endpoint down, and the limits are documented. Two, you have a tested failover, so a primary failure moves traffic to a synced fallback instead of dropping it. Three, your monitoring covers block lag, peer count, disk, and request rate, with alerts that reach a human. Four, your runbook names who does what in the first ten minutes of an incident, because launch-day incidents do not wait for a meeting. Five, your support channel has a status message ready, so users hear from you before they hear from each other. If all five are true, a surprise launch date is an ordinary Tuesday. If any of them is false, fix that one first.
The checklist is the same one we publish for every launch wave, because the work does not change when the names on the list change. What changes is the timing, and the timing is exactly what a TBA-heavy list takes away from you. That is why the checklist has to be done now, while nothing is launching, rather than later, while something is.
What not to do
Do not spin up infrastructure for every listing on the board. Most TBA projects will not need your node, and building for all of them is how you end up paying for idle servers. Do not treat a listing as a recommendation, and do not treat a high raise as a promise of traffic. Do not promise your users a launch-day experience you have not tested, and do not announce support for a launch before you have confirmed the chain, the date, and the requirements on the project's own site. And do not chase the list daily. Check it weekly, note what changed, and spend the rest of your time on the readiness work that does not depend on any single launch.
November's list is a good example of why this discipline matters. Three dated launches, three clusters, and a hundred TBA entries. The dated ones give you a calendar. The clusters give you a pattern. The TBA entries give you a reason to be ready rather than to predict. If your launch infrastructure needs a review before the next date lands, our launch consulting service covers nodes, RPC, and launch-week operations, and you can book a free infra audit with DevOpsBY. Our Web3 launch marketing checklist covers the non-infrastructure side of the same launch, if that is the part you are still planning.
Disclaimer: This post is educational only, not financial advice. Figures are listing or project data as of 2026-11-10 and may change - always confirm version numbers, requirements, and dates in the official docs before acting on them.
