---
name: netnet-capital
description: NetNet Capital ($NET, @NetNetCap) on Robinhood Chain — the "integration over listings" post that moved the narrative, what the account has and has not actually claimed about Robinhood, and its published fund mechanics. Read whenever NET, NetNet, NetNetCap or the Robinhood-integration rumour comes up.
sources: [cowork]
aliases: [NET, NetNet, NetNetCap, NetNet Capital Management]
---
Related: [[rh-chain-radar]], [[crypto-token-research]]

## The "integration over listings" post, found 30 Aug 2026
- [stated] Ben asked me to find the post where NetNet says exchange listings as an endpoint are outdated and integration is the future, because many people read it as implying a Robinhood Chain integration
- THE POST: https://x.com/NetNetCap/status/2092673546644500483 — 26 Aug 2026 18:00:28 UTC (renders as 1:00 AM Aug 27 in Bangkok). Full text, verbatim and complete, it is a four-line post with nothing omitted:
  "Shareholders, / Getting your token listed as the end all be all is an outdated mindset. Tokens are easier to find and buy than ever before. / Getting your product integrated is the new unlock. / More soon."
- 91K views, 724 likes, 141 reposts, 57 replies, 38 quotes as of 30 Aug 10:15 UTC
- IT DOES NOT NAME ROBINHOOD, or any partner, product or chain. The Robinhood reading is entirely the audience's, seeded by "More soon"
- Where the reading came from, from the quote tweets: @infinitybanyan "If this gets integrated into the RH app... $net", @CryptoHawk19 "Robinhood Wallet is about to hit nothing but $NET me thinks", @_0xghost_ "Integration > Listing", @OGDfarmer "HOLY FUCK"
- AS OF 30 Aug 10:15 UTC THE "MORE SOON" HAS NOT LANDED. No follow-up names an integration partner. The account's only Robinhood mention since is 28 Aug 16:07 UTC, https://x.com/NetNetCap/status/2093369896499601763, "The NetNet Capital Management Treasury now holds over $1,000,000 of NVDA Shares on @Robinhood" — that is the treasury holding tokenised equity, NOT a product integration, and conflating the two is the obvious way to get this wrong
- Nearest thing to a self-description of the strategy, 28 Aug 19:06 UTC reply to @arbitrooper: "Every game built so far (and in the future) utilizes new native primitives that can be used as lego blocks to build more games upon. We are not a AAA game studio, we are on-chain devs building net new decentralized financial infrastructure"

## What the account actually publishes
- Fund framing throughout: posts open "Shareholders,", it reports NAV per share and treasury composition. Opened with $52,000 of reserves at a NAV of $2.41 per share; the 23 Aug "Quarterly Earnings Report" (https://x.com/NetNetCap/status/2091525781000434080) is the first full accounting, 37 days in
- Built its own CASHCAT oracle because CASHCAT has no external price feed, aggregating each Uniswap v3 pool's own on-chain trading history (22 Jul thread)
- Run by an autonomous agent: "The fund is already run by an autonomous agent. Our keeper converts fees, swe..." (20 Jul, https://x.com/NetNetCap/status/2079297241337225713)
- Live products as of 30 Aug: winNET (lottery, $10,000 pot, 1,001 participants) and a "Red Button" a shareholder paid $1 to press. Both are on-chain games, which is consistent with the "integration" framing being about product surfaces rather than a Robinhood deal
- Ansem @blknoiz06 posted a "$NET Thesis | $1057 | $57M FDV" on 26 Aug and again around 29 Aug; NetNet quote-tweeted both

## Method note
- Harvesting @NetNetCap needed the Chrome bridge on Ben's Mac. get_page_text on an X search returns only the FIRST article, so it silently looks like one result. The working pattern: inject a collector over article[data-testid="tweet"] keyed by status id, autoscroll with ~900ms waits, then print via javascript_tool in slices under 1,700 chars. Appending a <pre> dump to the page does NOT help, because get_page_text prioritises <article> and ignores it
- /quotes on a status URL is the fastest way to read how an ambiguous post was interpreted, and it loaded cleanly where the reply thread under the post itself returned only the root tweet
