Reverse-engineering sites with Grok Bot to rebuild data layers
The author switched reverse-engineering work from Opus 5.5 to Grok Bot, capturing network calls and screen states to rebuild Bubblemaps' wallet map with strict observed/inferred/assumed labeling.
GROK BOT IN REVERSE MODE IS THE MOST DANGEROUS THING I'VE SET UP THIS YEAR I got so sick of Opus 5.5 refusing every time I typed "reverse engineer" that I moved the whole job over to Grok Bot now I paste one prompt, drop in any website, app or API, and walk away → first it records everything the product loads, every network call, every screen state → then it has to prove where each piece of data comes from and what logic runs in the browser → only after that does it rebuild the thing and check it against the original my first real target was Bubblemaps. I wanted their wallet map inside my research app @reagent_rwa and wasn't going to pay $850 a month for their API → it checked the REA package before running anything → went through four live maps on Ethereum, Base and Solana → found the requests that pull holders, wallet links and prices → rebuilt the data side on public blockchain data, so my version doesn't depend on their servers at all and the part I'd never cut is the labels. every claim gets marked OBSERVED, INFERRED or ASSUMED, and anything without a screenshot, a request log or a few lines of code behind it gets thrown out. without that rule it starts guessing how features work and presents the guess as fact heavy obfuscation and WebAssembly still trip it up. it maps the shape fine but misses a lot of the actual behavior. a run like this took me about 20 minutes on Bubblemaps. on bigger apps I just leave it and come back when it's done that's how my app got its own wallet map, and Bubblemaps never saw a cent of that $850 bot template and prompt are below ↓
This post quotes another post: x.com/monokern/status/2090490444224331787