Identifiers truncated in this published copy. The record behind every row is retained in full.
In 32 seconds on 2026-10-02, 30 wallets created 420 separate tokens carrying one byte-identical launch document. Over 58 days those same wallets created 2,471 launches under 67 names, 97.2% of them in bursts of five or more, each launch seconds after the last. 0 of the 2,471 with a recorded outcome completed a bonding curve. On the launch surface each one presented as a new token.
One launch document, 579 bytes, fingerprint c8555451…a50677, recorded under the name GOONAPE. Between 2026-10-02 00:43:47 and 2026-10-02 00:44:18 UTC, 420 separate tokens were created carrying it, byte for byte, by 30 wallets: exactly 14 launches from each wallet, inside 32 seconds. Every one of the 420 was recorded from its creation transaction.
The wallets in this exhibit are those that signed a launch carrying that one document, and nothing else decides who is listed. Between 2026-09-03 and 2026-11-01 those wallets created 2,471 launches under 67 names, using 72 distinct launch documents. 2,403 of the 2,471 (97.2%) arrived in 216 bursts: one name, five or more launches, each within five seconds of the one before. In 216 of the 216 bursts every launch carried a single identical document. Only 8 other wallets in the record ever launched with any of the 72 documents.
| Name, as recorded | Launches | Bursts | Wallets | First |
|---|---|---|---|---|
| GOONAPE | 420 | 1 | 30 | 2 Oct |
| Poke Options | 164 | 17 | 30 | 3 Sept |
| CHUD | 130 | 6 | 30 | 3 Sept |
| Shiny Pack | 90 | 7 | 30 | 25 Sept |
| ZCASH Virtual Machine | 85 | 5 | 30 | 26 Sept |
| ForkHood | 60 | 4 | 30 | 27 Sept |
| everybdy | 57 | 6 | 30 | 17 Sept |
| NOV19 | 50 | 9 | 5 | 8 Oct |
| RWA Debugger | 45 | 3 | 30 | 27 Sept |
| ANYWAYS | 40 | 4 | 30 | 17 Sept |
| Virus Chain Fork | 40 | 3 | 30 | 18 Sept |
| ALONG | 40 | 3 | 30 | 23 Sept |
| PAIRFUN | 40 | 2 | 30 | 28 Sept |
| TOOTIN | 40 | 7 | 5 | 9 Oct |
| PORT | 40 | 7 | 5 | 10 Oct |
The fifteen names with the most launches, of 67. Names are printed as the launches recorded them. First is the date of the first launch under that name, 2026, UTC.
Of the 2,471 launches with a recorded outcome, 0 completed a bonding curve. The creating wallet took less than a hundredth of one percent of supply in the creation block on 2,189 of 2,471 launches, and never more than 1.74%. 2,209 of the 2,471 launches where curve buyers are recorded had none; the most any had was 31.
Read together those figures describe volume: many launches, almost no creator share, almost no buyers and no completed curve. They are printed beside the count because a launch count on its own says nothing about what the launches did.
Under the register's published rule for connecting creator wallets, 416 of the 435 possible pairs among these 30 wallets are joined. The register nevertheless assigns them no group: none of the 30 carries a group label. Their files also join them to wallets outside this list, in 330 further pairs, and through those to a single component of 243,848 creator wallets, which is above the ceiling of 100 past which this register declines to name a group. So nothing on this page is a group the register asserts. It is one file, the wallets that launched it, and those wallets' other launches.
Counts are over launches this archive recorded from their creation transaction; launches discovered later or rebuilt from chain history are left out of every figure, which is why a count here can be lower than the same wallet's page. A document is identified by the SHA-256 of its bytes as captured. A burst is defined above and is a description of timing only. Creator share is the share of supply the creating wallet took in the creation block. Outcome and curve buyers are stated only where the record holds them, and a launch without one is left out of that sentence's denominator and never counted as zero.
This register records what it observed and does not call these launches coordinated, related or wrongful, and it does not say who controls any wallet named here or why the launches were made. A document carried by many launches establishes that the same file was used; it does not establish who used it. Launch tools that create tokens in batches exist and are used for many purposes, and nothing here distinguishes one purpose from another. No money trail between these wallets was traced for this exhibit, and the few wallets recorded as buyers were not examined. What is established is the file, the count, the second each launch was created, the wallet that signed it, and what the record holds of each launch's outcome.