BUYPress room Public case file / July 30, 2026 Review request

Robinhood Chain / community-builder case study

A button became
a public instrument.

The Buy Button turns public Robinhood Chain activity into a cultural object, an auditable five-minute record, a permissioned history project, and read-only infrastructure for people and agents.

Independent and unaffiliated with Robinhood. No endorsement, partnership, listing, or official status is stated or implied.

Evidence before interpretation.

This is a compact review packet for a community project built on a public network. It separates what is onchain, what is measured, what is permissioned, and where the operator has a financial conflict.

It is not a request for token endorsement or price promotion. The final request is simply to review the work as a community-builder case study—or route it to the correct owner.

One contract. Public controls.

Creation transaction
0x3fbea3…6bb4aJuly 1, 2026 at 19:49:01 UTC
Main liquidity pool
0x8e8fa1…6Bb18Uniswap V3 / 1% fee tier
Initial allocation
999,999,999.999999999999987736 BUY entered public liquidity.No separate team mint at token generation; minute factory rounding residue is disclosed.
Position custody
Source-verified LaunchLocker ↗Uniswap V3 position NFT 1014
Liquidity and control disclosure

At the dated disclosure block, the source-verified, non-proxy locker held the position NFT. Its verified source exposes fee collection and owner-controlled protocol-fee settings, but no entry point to transfer the position NFT, decrease its liquidity, or withdraw the position. The owner can change the protocol-fee share and recipient and authorize fee collectors. These controls affect fee collection, not LP-position custody. This is a dated source-level disclosure, not a guarantee about future chain state or external contracts.

Liquidity disclosure / JSON Supply record / JSON Full proof pack

Addresses,
not people.

The holder total is Blockscout’s count of current nonzero token addresses. It can include pools, contracts, automated systems, or multiple addresses controlled by one person. The project does not turn this number into a claim about unique humans.

Inspect the live address list ↗
Current nonzero addresses 670
Explorer head at read
23,260,823
Block timestamp
2026-07-30 10:57:06 UTC
Source
Blockscout API
Captured fallback / refreshing live observation

Five minutes at a time.

What enters the archive

One buy is one transaction in which a tracked token leaves a tracked Uniswap pool. A buyer is the transaction sender, using the swap recipient only when the sender is unavailable. The final matching swap log is retained once per tracked token and transaction hash.

What a bucket means

Activity is sealed into exact five-minute UTC intervals using block timestamps. Each snapshot pins the classifier definition, tracked registry, block range, totals, and the preceding snapshot hash.

What missing means

Coverage is published. Missing time remains unknown rather than becoming a fabricated zero. Wallet counts are normalized addresses observed in a period; they are not asserted to be people.

Trailing 24-hour archive Checking coverage Five-minute source buckets
Previous hash reading… Latest proof hash reading…
Sealed interval
Reading latest snapshot
Block range
Reading chain proof
Definition
buy-v2-uniswap-v4
Proof gaps
Checking

History with permission attached.

The archive preserves first-person recollections and contemporaneous public posts from January 2021. It is designed to keep memory, documentary evidence, and project promotion separate.

Read only means read only.

The route API and MCP server expose public chain identity, pool discovery, registry resolution, and route comparisons for Robinhood Chain community tokens. They do not authenticate to Robinhood or a brokerage account.

HTTPGET /api/v1/routes?token=0x…&amount=100
MCPhttps://www.hoodbuybutton.com/mcp

Route outputs are read-only estimates with source links—not transactions, investment instructions, security audits, or guarantees.

Please review this as a Robinhood Chain community-builder case study—or route us to the correct owner.

The useful subject is the work itself: public identity, observable activity, source-linked history, consent infrastructure, and read-only tooling built around the chain. We are not asking for token endorsement, market support, or an implied relationship.

Respond or request the source packet