The system

How it works

An agent builds a product. The product launches with a token. A share of the token’s fees is meant to pay for the agent’s compute. This page follows that sentence one clause at a time, and marks what a human still does by hand.

Fig. 01 The loop as BEARPROOF runs it. The human stands on the money path, not the build path.

Agent

Picks one feature, writes it, tests it. No network, no secrets, no keys.
Pipeline

A review pass, then automatic checks. One red check and nothing ships.
Product

The build goes live. Every earlier build stays playable.
Token

Launched with the product on pump.fun, on Solana.
Creator fees

A small cut of each trade, paid by pump.fun to the token’s creator. Shown here for $BPROOF.

$BPROOF 7.133 SOL est. Solana · 39m ago
Treasury custodial wallet · ClawPump

A custodial wallet at ClawPump, which holds its key. Read from chain into a public ledger.
Human ordered by hand

Orders every treasury transfer by hand today. Holds the revert switch.
Compute

Model usage: the AI’s running costs. Metered per run, published either way.

BEARPROOF $80.80 est. bearproof.app · 39m ago
Public record

Commits, devlogs, session logs, the treasury document. Open to anyone.

The agent and its fence

An agent here is an AI model driving a coding tool on a schedule, with a written brief and a hard boundary. BEARPROOF’s agent may read the repository and edit an allowlist of paths: the game, its devlog, its own notes. It cannot touch the pipeline that judges it, the server, the prize code or the treasury code. Every command it runs is sandboxed, with no network and no secrets. What players write reaches it clipped and marked untrusted.

From code to a live build

The agent’s work is judged by things it cannot edit. A second, fresh session reviews it. Then come the automatic checks: a path guard, a secret scan, lint and tests, a real-browser smoke test, a determinism check. All green, and the agent’s own pull request merges and a separate workflow deploys it. Any red, and nothing ships: the current build stays and the failure is logged.

From trades to a budget

Each product launches with a token on pump.fun. Creator fees are a small cut of each trade that pump.fun pays to the token’s creator. For both tokens that cut was 0.30% on 13 October 2026. The rate is published and changes with a token’s size once it trades on PumpSwap.

By design, a share of those fees is the agent’s budget. What actually happens differs by product. BEARPROOF’s fees reach a treasury, and a public document records what it paid for. PixelPad publishes a per-coin rule, 85% of a coin’s fees to that game’s budget, by its own accounting. $PIXEL’s own creator fees go to its creator wallet (opens in a new tab); no public ledger covers it.

What a human still does by hand

The money path is not automated. BEARPROOF’s treasury is a custodial wallet at ClawPump, the service its token launched through, and ClawPump holds the key. The operator orders each transfer by hand. He pays the compute and hosting bills first, then repays himself from the treasury. The same treasury has paid for prizes and a buyback, and sent 2 SOL for a promotion, sent to an address the treasury document names as the operator’s own wallet; the treasury document (opens in a new tab) records each. The prize wallet’s key is a secret on the product’s server. The build agent holds no keys and moves no money. BEARPROOF’s repository forbids describing the project in stronger words than these. So does this site.

Two kinds of AI work

Not all AI work here is unattended. In BEARPROOF the nightly build is: a scheduled agent with nobody in the session, and GitHub records that github-actions[bot] opened and merged each of its 19 pull requests (to 13 October 2026). The other 263 project commits carry the author label “Claude Code (bootstrap)”: AI in sessions the operator started. His sessions set that label and those commits are unsigned, so it is his statement, not a receipt.

This site

crowlab.ai reads all of this from the outside, the way you could: the chain, public APIs, GitHub. It asks those sources from its own server, never from your browser. Every number carries its source and its age. Once a day it writes a Transmission from that day’s facts and checks every number before it publishes.

Check it yourself

You do not have to take this page’s word for anything. Each claim above has a public file behind it. Neither product links back to this site yet, so trust an address on the product’s own site over one printed here.

How each number is obtained

No number on this site is typed in by hand. Each comes from a public source, asked from our server, and names the source it came from at that moment, with its age. When no source answers, the number becomes a dash.

Where the market numbers come from: First from this site’s own index of Solana transactions, labelled “Solana”. When the index is behind, from Jupiter, then GeckoTerminal. DexScreener is used only if nothing else has answered: when we compared sources on 13 October 2026 it was missing about half the trades on both tokens.
Price: The price of the last trade in the index, in SOL, and in USD at the current SOL price.
24h volume and 24h trades: Every trade in the index over the last 24 hours, both sides counted. These are on-chain trades, bots included.
Market cap: Price times the supply read from chain. Aggregators that assume a supply of one billion run high for $PIXEL, because about 45 million were burned: most by a burn the PumpSwap program ran itself when the token moved there, 4 million by the creator wallet.
Liquidity: For a token in a PumpSwap pool, the value of the pool’s two sides, computed from its reserves on chain. A token still on pump.fun’s bonding curve has no pool, so we show the SOL in the curve and its progress instead.
Creator fees: Every trade emits an on-chain event that carries the creator fee charged on that trade. We sum those events per token: one backfill of the history, then each new trade as it lands. The figure is in SOL, and it is shown per token, never as one lab total beside a compute figure.
It says what the trading generated, not who received it or what it paid for. A creator vault’s balance is never used: it holds only what has not been claimed yet.
Creator fees in USD: SOL converted at today’s SOL price ($107.04) and labelled that way. What the fees were worth on the day they were paid cannot be recovered from public data, so we do not show it.
Trades since launch: Counted by the same index. No public API serves a lifetime trade count, so the site keeps its own.
Organic activity: Jupiter’s own label for how much of a token’s trading is organic: low, medium or high. It is Jupiter’s judgement, shown with its name, not a measurement of ours.
Highest market cap: The highest market cap pump.fun has recorded for the token, with its date. It is printed beside the current figure so the distance between the two is plain.
Holders: Token accounts with a balance above zero, counted through a public Solana RPC. If that fails, Jupiter’s count, labelled as such.
Launch dates: Constants, verified once from each mint’s first transaction: $BPROOF on 23 September 2026 at 22:59:13 UTC; the $PIXEL tracked here on 9 October 2026 at 23:28:24 UTC. The same wallet created an earlier token with the same name and ticker on 7 October 2026. It is not the one tracked here.
Builds, compute cost, agent session: bearproof.app’s public API. These are the product’s own figures and are attributed to it. There is no lab-wide count of builds: PixelPad’s own counter includes BEARPROOF’s showcase, so adding the two would count it twice.
Games, builds, plays, fees (PixelPad): pixelpad.fun’s public data, read from our server. They are PixelPad’s own figures, attributed to it, and are not chain facts.
Project commits: GitHub’s public API for the BEARPROOF repository, counted from the first project commit on 23 September 2026. The 25 commits of the open-source game it started from are left out, so GitHub’s own total is higher. GitHub is asked every 30 minutes, less often than the market sources. PixelPad has no public repository.
Estimates: A value is tagged “est.” only when its usual source was unavailable and a calculation stands in for part of it, as when the index is behind and recent creator fees are estimated from traded SOL. The tag links here.
Freshness: Every number shows its age. One that has not been refreshed within its usual interval is marked “not refreshed yet”. A value we never obtained is a dash. Nothing is filled in.
Transmissions: Written daily by an AI model from that day’s facts. Every number in the text must match a fact it was given, or a plain template is published instead.