The clerk, beside the filing cabinet

How it works

How an item file opens

An item file is a word, not a judgement about what an object is. The rule is mechanical and it is the whole rule:

  1. Each token’s name and symbol are lower-cased and split on anything that is not a letter or a digit.
  2. Words shorter than 3 characters, words that are only digits, and the 70 words on the list below are dropped.
  3. Tokens carrying the chain’s equity marker (“• Robinhood Token”) are not claimants: they are the chain’s own wrapped stocks, not tokens minted for an object.
  4. A word that at least 2 distinct token addresses put in their name or symbol opens a file.

Nothing in the rule knows what an object is, and that is deliberate: a curated list of objects would make this a curator’s product with a private reason for every inclusion. The cost of the mechanical rule is that a file can collect tokens that share a word by accident. Read the addresses, not the name — that is the point of the ledger.

STOPWORDS · the · and · for · you · your · our · not · with · from · this · that · all · any · was · are · coin · token · tokens · meme · memes · inu · dog · cat · moon · pepe · shib · elon · trump · robinhood · chain · wrapped · official · finance · protocol · network · swap · dao · usd · usdc · usdt · usdg · sgd · dollar · stable · weth · eth · btc · sol · bnb · stock · class · common · corp · inc · ltd · holdings · new · old · big · small · best · first · last · one · two · get · buy · sell · hodl · pump

What a claim is

We display only onchain claims verified through signed messages. Offchain chatter and sentiment are not included in the tally.

A claim is an off-chain signature. It moves no funds, costs no gas and touches no contract. The server issues a nonce tied to your wallet, the item file and the claimant; your wallet signs this exact text; the server checks the signature against the wallet that claims it and spends the nonce in the same step, so a claim cannot be pre-signed before a claimant existed and cannot be replayed into another file. One wallet holds one claim per file. Filing a new claim rewrites your mark and appends to the ledger, which is never rewritten.

Object Championship — back an entrant
chain: 4663
division: duo
entrant: 0x56aaa501fa9eb6670d6175d686957434c3d21e18
wallet: 0x0000000000000000000000000000000000000000
nonce: 8f2c…
This signature records where you stand. It moves no funds and costs no gas.

The signed text still opens with this product’s original internal name. It is left exactly as it is on purpose: every claim already signed in the ledger was signed against that string, and rewriting it would break the ability to recompute those signatures.

The crowd and the flow

The flow’s pick comes only from pool data: 24-hour volume, distinct buyers and sellers, liquidity, pool count and age, each stamped with the second it was read. The crowd’s pick comes only from signed claims. They are never mixed, averaged or reconciled. The claim this product exists to test is that the two picks differ often enough to carry information the screeners do not already have — and the measurement is published on Item files: how often the crowd’s pick in a file is not the flow’s. If they agree in nearly every file, this ledger is a slower screener and the framing has to go.

What the ledger cannot see

  • A wallet is not a person. One operator can claim from many wallets. Every number here counts wallets, and says so.
  • No holder counts. The chain’s Blockscout API answered a Cloudflare interstitial rather than JSON, so nothing in this product rests on holder data and no holder number is shown anywhere.
  • Unread is not zero. A claimant whose pools could not be read is printed as unread. Distinct buyers are read for the claimants at the top of a file only; the rest are unread rather than guessed.
  • A claim is not advice. It is a mark about which token a crowd stands on, not a claim that the token is safe or that its price will move.
  • Most claimants die within a day. The ledger keeps showing them rather than quietly dropping them, because a file that hides its losers is not a record of anything.

API

Read-only JSON, the same data these pages render, paged at 50 records: /api/v1/divisions?page=1&limit=50 and /api/v1/divisions/<word>. Every response carries items, page, per_page, total and next, plus the second the sources were read.