For platforms · The week on chain · Method
How each figure is read.
In plain words, per platform: what counts as a pack, a sell-back, a buy-back and a card leaving the vault; what a public chain proves and what it does not; which platforms publish their certs; and why some platforms are not measured.
The words
The same four things on every platform.
- A pack
- One purchase of a pack, play or spin, counted from the platform's own program or contract at the moment it is paid. Where a platform records a payment but not the number of packs it covers, the column says payments, not packs, and is not added to the pack total.
- A sell-back
- The pulled card going straight back to the platform for cash: the platform's own buy-back program, exchange or pool paying the holder and taking the card. Each pack is followed to its own sell-back, so the share is of the week's packs, however late the sell-back came, up to the date the run was followed to.
- Time to sell-back
- The block time of the first buy-back of a pack's card minus the block time of its opening. The median is the middle pack; the 90th percentile is the time within which nine packs in ten had sold back.
- Left the vault
- A card token burned in a transaction the platform marks as a shipment, or a token the platform lists in a redemption request. Where the chain carries no such mark, the cell says so rather than guessing.
- Spend and buy-back value
- Stablecoin paid into the platform's own wallet or contract for the week's packs, and stablecoin paid out by its buy-back program for the same packs. Card-rail payments that do not touch the chain are not visible and are said to be missing.
- Exact and estimate
- Exact means every event in the week was read. Estimate means a seeded random sample of the week's transactions, scaled to the week's full count, and the cell carries its 95% interval; the samples exist because the only public node holding week-old Solana history serves about one transaction a second.
Per platform
How each public record was read.
As read for the week of 11 to 17 October 2026, on 21 and 22 October 2026. Each week’s file carries its own sentences, so a change of method is written down with the week it starts.
01
Collector Crypt
Solana
Exact counts from memos; dollars from a seeded random sample of 1,000 of the week's packs. Read 21 and 22 October 2026.
Every signature of the gacha wallet, the cc_buyback program and the shipping co-signer from the run time back to one day before the window, with their SPL memos. A pack is the first ':open' leg of a uuid in the window; a sell-back is any ':buyback' leg of that uuid up to the run time; time to sell-back is the first buy-back leg's block time minus the open's. Redemptions are Burn instructions in 'cc shipment' transactions co-signed by the shipping key in the window, all read. Dollars: a seeded random sample of the week's opens, each priced from its open transaction (USDC into the gacha wallet) and every buy-back leg (USDC out); spend = packs times mean price; returned share is a ratio estimate.
02
Collector Crypt
Robinhood Chain
Exact, from contract events. Read 21 and 22 October 2026.
All logs of the gacha contract and the card contract for the window plus three days: Paid(payer, token, amount, memo) is the pack; the card is minted to the payer a few blocks later (matched first in, first out per payer, in memory only); SoldBack(seller, tokenId, amount, nonce) is the sell-back; burns are Transfer to zero; a separate event lists tokens in redemption requests.
03
Courtyard
Polygon
Exact, from contract events. Read 21 and 22 October 2026.
TokenPurchasedAndMinted on the registry's minters (wallet-paid packs carry the price), TradeExecuted on the registry's trusted exchanges with the operations wallet as bidder (sell-backs), Transfer to zero (burns), all from eth_getLogs and eth_call on public Polygon RPC; sell-backs followed to the run time. Chain events only: Courtyard's API and metadata are not read.
04
Phygitals
Solana
Sample estimates: random samples of 750 and 300 of the week's transactions, scaled to the week's counts. Read 21 and 22 October 2026.
Pack payments land on the settlement wallet's USDC account, not on the wallet itself, so both are read: every successful transaction in the window is counted and a seeded random sample of each is opened. A payment is stablecoin into the platform from outside; a sell-back is stablecoin out with the Core card returning to the settlement wallet; an award is a Core card leaving it. Time to sell-back is the sell-back's block time minus the card's previous transaction.
05
Gacha Pull
Abstract
Exact, from contract events. Read 21 and 22 October 2026.
All logs of the pack contract, which is also the card ERC-721: Purchased (pack, USDC.e), Transfer from zero (card minted, one per pack), Buyback(player, cardIds[], token, amount) (sell-back; value split evenly across the cards in one event), Transfer to zero (burn). Times are block differences times the window's mean block time.
06
Beezie
Solana
Sample estimates: a random sample of 200 of the week's 14,679 pool transactions, scaled to the week. Read 21 and 22 October 2026.
The claw pool wallet: every successful transaction in the window is counted and a seeded random sample is opened. Play payments are stablecoin into the pool; sell-backs pay stablecoin out while Core cards move. A play payment can cover several plays, so pulls are not counted.
07
Raflux
Solana
Sample estimates: a random sample of 100 of the week's 6,364 pool transactions, scaled to the week. Read 21 and 22 October 2026.
The Super Gacha pool: every successful transaction in the window is counted and a seeded random sample is opened. Spin payments in; payouts out with no token moving (Raflux mints a token only if the buyer keeps the item), so sold-back share cannot be separated from cash-outs.
What the chain shows
Every claim, with its time.
A public chain records every token minted, every payment into the platform’s own wallet or contract, every buy-back paid out and every token burned, each with a block time that no one can edit afterwards. Counting those is counting the platform’s own record of its claims.
Where the platform writes a pack id, a memo or an event name into the transaction, the legs of one pack can be joined: opened, card sent, sold back, shipped. Where it does not, the join is made from the card token itself.
Where grader and cert number sit in permanent public metadata, the item behind a token can be named and can join a public cert index. That is the case on one platform in this reading.
What the chain does not show
The shelf.
No chain shows the cards. No platform in this reading publishes an independent count of the items behind its tokens, so the link between a token and a card rests on the platform’s own word and on the vault it names.
Card-rail payments that never touch the chain are not visible, so a platform’s spend can be larger than the chain shows. A buy-back paid from a wallet the platform does not name is not counted as one.
A sample is a sample. An estimate carries its interval because the figure sits somewhere inside it, and a sample figure without an interval is not shown. None of this is a verdict on a platform, a token or an item, and none of it is a forecast.
Certs
Which platforms publish grader and cert, and which keep them.
Where a token’s grader and cert number sit, as read on 21 October 2026. A platform that keeps them on its own server is not read by a program, and its cert record is marked not readable in the table. This describes where the record sits; it says nothing else about the platform.
Published in permanent public metadata
- Collector Crypt (Solana, Base, Robinhood Chain)Grader and cert number in permanent public metadata on Arweave, on every chain read. The only platform whose items can join a public cert index from the chain alone.
Kept on the platform’s own server, or none
- Courtyard (Polygon)Token metadata on the platform's own server; its terms bar automated reading.
- Phygitals (Solana)The on-chain asset holds a name and a URI only; certs sit on the platform's metadata host, whose terms bar bots.
- Beezie (Flow EVM, Base, Solana)Metadata on the platform's own API, which answered with a challenge page.
- Renaiss (BNB Chain)Certs on the platform's own site; its terms bar automated extraction.
- Gacha Pull (Abstract)Metadata on the platform's own API.
- Shiny (Base, Abstract, Solana)Metadata on the platform's own API.
- Ready Cards (Solana)Metadata on the platform's own API.
- rip.fun (Base)Raw cards and sealed product: no grader or cert by design.
- Raflux (Solana, Base)A token is minted only when the buyer keeps the item; the card collection was not identified.
- Arena Club (Polygon)Token metadata on IPFS, not retrievable from our network when read.
Not measured
Why a platform is left out of a week.
Each week names the platforms it could not measure, with the reason. For the week of 11 to 17 October 2026: Collector Crypt on Base; Beezie on Base; Beezie on Flow EVM; rip.fun, DYLI; Shiny on Base, Abstract, Solana; Renaiss; Ready Cards; BAXUS; Arianee; OpenVino.
- The endpoint does not serve the week
- Public Base endpoints serve only about the last nine hours without a key, and public BNB Chain endpoints refused historical log reads. A platform on those chains is read only when a keyless endpoint serves the whole week.
- The contract carried too little
- Where a platform's contract shows a handful of transfers and no purchases in the week, the week is named with its counts rather than measured.
- The record is not on a public chain
- Platforms that take payments and requests without a card token, and platforms whose contract is published only in part, have nothing a public read can count.
- Never a company API
- No platform's own API, dashboard or export is used, and no page whose terms bar automated reading is read by a program. A platform that keeps its record on its own server is measured from the chain only, or not at all.
The method as used for the week of 11 to 17 October 2026, signed 23 October 2026. It describes how a public record is read; it is not a verdict on any platform or item, not a forecast and not investment advice. Platform and chain names belong to their owners, who do not endorse this page.