DON'T TRUST THE BAG.
CHECK THE RECEIPTS.

Exact numbers, not rounded for a headline. Every rule in force, every data source, every security claim below links to where you can check it yourself.

Product receipts

Rules in force

v0.3.1

Archetypes, badges, verdicts. See the methodology.

Aura

v0.2

The Bag Aura score itself — unchanged by rules v0.3.

Data sources

Blockscout · Alchemy fallback

Blockscout for holdings and prices (bot-challenged without a key — treated as unavailable). Robinhood Chain's public RPC is keyless, working — it answers instantly over curl but is unreachable from Cloudflare's edge, so Alchemy (requires ALCHEMY_API_KEY) is asked first when configured; the public RPC stays the fallback either way.

Security

Read the architecture

Full write-up of what this app can and cannot touch.

read /security

Read-only guarantee

No signing, ever

Read-only. BAG CHECK never asks for your seed phrase, private keys, token approvals, or transaction signatures.

Report method

Large-holder sample

Sampled top holders per community, published with the method and the raw counts.

see /communities

EXACT COUNTS SINCE THE LEDGER STARTED

This page prints the exact count, however small — that is what it is for. The homepage shows the ruleset instead until a count would mean something. Same ledger, two jobs.

Addresses checked

20

Checks

29

Checks today

11

Community reports

4

Token receipts

Every $BAGGY fact below is labeled by how sure we are of it. PLANNED is a stated intention, not a fact. CONFIGURED means an operator set it, unverified. VERIFIED ONCHAIN means a trusted explorer or launchpad confirms it. A row with no source is not verified, no matter how confident it sounds.

Launchpad

Pons V2PLANNED

Paired with

ETHPLANNED

Supply

1,000,000,000PLANNED

Liquidity

permanently locked Uniswap v4 poolPLANNED

Contract

not decidedPLANNED

Pool

not decidedPLANNED

Launch tx

not decidedPLANNED

Launch time

not decidedPLANNED

Graduation time

not decidedPLANNED

Creator fee

not decidedPLANNED

Fee recipient

not decidedPLANNED

Buyback

not decidedPLANNED

Full plan and $BAGGY’s own page: /baggy.

Changelog

Every policy call, methodology change and correction, newest first. Entries are never deleted — a wrong entry gets a correction under it.

1. 2026-09-02methodology

   Composition is scored on what could be read, not on what carried a price

   "WHAT'S ACTUALLY IN THE BAG?" gated itself on priced positions ÷ all positions and refused to score below 80%. On Robinhood Chain that measured the wrong thing: most of what a real wallet holds is airdropped launchpad tokens that DEX Screener and GeckoTerminal were both asked about and both answered "no market" for. A token with no market anywhere is worth about nothing, which is an answer — not an unknown — but it dragged coverage to 6% or 65% on ordinary wallets and printed "composition not scored" on the module the product leads with. Fix: composition is scored unless the price providers failed to ANSWER (timeout, poisoned batch, exhausted budget) for more than 20% of positions, or pricing is unavailable outright; the unscored reason now names the count ("providers did not answer for N of M positions"). Marketless tokens are excluded from the value basis, counted, and printed under the breakdown as "N tokens with no market — excluded". Coverage is unchanged and still published as priced ÷ all positions — it is a transparency number now, not a gate. Community reports inherit this: more sampled wallets now have a scored composition and a scored concentration, and every report publishes the basis (compositionSampled) next to the medians it produced.

2. 2026-09-02policy

   Token policy revised before any official contract existed

   The earlier adoption gates for a token (25,000 wallets/week, 40% re-check, K ≥ 0.6, sewn drops, Genesis freeze, counsel opinion) are retired. They were written before the launch plan existed and were never conditions a chain token has met. BAG CHECK remains useful with no token; holding $BAGGY has zero influence on scores, reactions, reports or corrections. Planned launch: Robinhood Chain → Pons V2 → ETH. Creator economics are not decided.

3. 2026-09-02methodology

   Rules v0.3 — stock tokens classified; Aura v0.2 unchanged

   Rules v0.3 introduces "stock" as a first-class token classification, so official Robinhood Chain stock tokens (e.g. NVDA) stop being silently bucketed into meme and start being classified for what they are. This changes which archetype, badge and verdict rules fire — Wall Street Gremlin and THE SUIT now read stock + rwa instead of rwa alone, and meme-share reads exclude stock tokens — but it does not change how Bag Aura is computed: the composition component still counts stock tokens folded back into the legacy meme category, exactly as it did before v0.3. AURA_VERSION stays 0.2; RULES_VERSION moves to 0.3. A token classifies as stock only when it is on the committed allowlist, or its name ends in "• Robinhood Token" and the explorer marks its reputation ok — a token that merely contains a ticker or brand name does not qualify.

4. 2026-08-26correction

   Community reports were re-run after a pricing-budget gap misfiled Mid-Curve wallets

   The first three community reports (Cash Cat, PONS, TENDIES) were sampled under a 40-token pricing budget. Wallets holding more tokens than that had their concentration left unscored and were filed as Mid-Curve by default, so the PONS and TENDIES "Mid-Curve" headlines were mostly an artifact of coverage, not a reading of the wallets. The Cash Cat report was less affected (8 of 32 Mid-Curves unscored). Fix: Budget raised so every observable token is priced (pricing coverage v2) and activity measured outbound (aura v0.2); the same frozen cohorts were re-run (docs/reports/sensitivity-2026-08-26.md). None of the three narratives survived: Cash Cat was 42% One-Bag Maxi / median 6,131 and is now 75% Dust Lord / median 5,733 with a median largest position of 99% (they picked one bag and kept every receipt); PONS was 47% Mid-Curve / 4,509, now 68% Dust Lord / 5,651; TENDIES was 53% Mid-Curve / 4,714, now 55% Dust Lord / 6,028. Old verdicts, retired: "Cash Cat's biggest holders didn't diversify. They picked." · "PONS's biggest holders don't pick. They collect." · "Tendies holders hold a hundred tokens. Tendies is one of them." The reports were not distribution-ready and were not distributed.

5. 2026-08-26correction

   Backdated ledger roots removed; the ledger no longer computes past days

   Rendering a 7-day ledger-root series on this page asked the ledger for past days it had never computed, and the ledger answered by computing roots from today's records and storing them under the old dates — six backdated roots (Aug 20–25) that were never anchored, and the chain pointer moved to the oldest of them. Caught within the hour by the identical hashes on this page. Fix: The six backdated roots were deleted and the chain pointer restored to today's root. The ledger now refuses to compute a root for any day but today; a past day with no stored root shows as empty, never as fabricated.

6. 2026-08-26correction

   "Keep my Block Tag" disabled until proof of control exists

   "Keep my Block Tag" trusted the card's key as proof of ownership. The key only proves someone ran the check, so a stranger could have kept a tag for a wallet they do not control. The two tags kept so far were written by the operator while testing. Fix: Keep is switched off until a proof-of-control step exists. Until then nothing per-wallet is written by anyone: checking is not claiming.

7. 2026-08-26correction

   Operator-token hook removed from the verdict engine

   The verdict engine carried a hook keyed to holdings of a hypothetical operator token ("holds only BAGCHECK"). It never touched Aura, but a judge whose lines depend on its own coin is a conflict whichever way it points. Fix: Hook and line removed; the engine takes no input about any operator asset, by type.

8. 2026-08-26correction

   Chain age and token age are now stated separately

   The Cash Cat report and our research notes dated the chain from the Jul 1 public mainnet announcement ("chain is 56d old") and called the token "deployed day-of-mainnet." Robinhood Chain's block 1 is dated 2026-04-30 and the CASHCAT contract was deployed 2026-06-18 (block 88,836), 13 days before the announcement. Fix: Two clocks, both stated: the chain has existed since block 1 (2026-04-30) and the product anchors chain age to the public launch (2026-07-01) because nobody outside could use earlier blocks; reports now show token age (CASHCAT: 69d at sampling), which is the real Diamond Duffel constraint — no holder can have held 90 days yet.

9. 2026-08-25correction

   Community report timestamps now state UTC

   Community report timestamps were shown as a bare date; a late-evening US sample read as a future date. Fix: All report timestamps now state UTC.

10. 2026-08-25correction

    Community nomination rule widened past the 90-day chain-age trap

    The community nomination rule (≥90 days of history) disqualified every community on a chain younger than 90 days, including the one already reported. Fix: Rule is now ≥1,000 holders AND (≥90 days OR top-3 by holders on the chain); the exception is stated on the page.

11. 2026-08-24correction

    First-check records limited to explicit "Keep my Block Tag" writes

    First-check records were written for any pasted address, including wallets pasted by someone else. Fix: Only the owner's explicit "Keep my Block Tag" writes a record; an erasure endpoint removes anything written before the fix.