grasshook
Robinhood Chain
Using Grasshook

Your rows and their fees

What the My rows page reads, where the numbers come from, and why some fields are blank.

Where rows come from

Rows are enumerated from the v3 position manager contract, not from a database. Any v3 row you minted on any interface appears here, because the source of truth is the chain rather than our records.

v4 rows do not appear yet. The v4 position manager cannot be listed the same way, so finding them means scanning its history and checking who owns each one now — part of season 12, together with opening and closing them.

The cost of that choice is speed — reading the chain is slower than reading a table — and it is worth paying, because a list of your rows that only knows the rows it created is not a list of your rows.

Fees owed

Each row stores a counter of fees owed. Reading it is one cheap call, and it is wrong: the counter only updates when the row is touched, so it reports zero for rows that genuinely have fees waiting.

Grasshook instead simulates a collection as though you were performing it, which returns exactly what would arrive if you did. This is one call per row rather than one batched call for all of them, because the collection function checks who is calling and a batching contract is not you.

Range status

A row is in range — earning — when the pool's current step falls between its boundaries. Out of range means it holds a single token and is earning nothing. Closed means its liquidity is zero but the token still exists, usually with fees still claimable inside it.

Profit against entry

Shown for rows opened through Grasshook, where the deposit was recorded at the time. For rows opened elsewhere it says so instead.

It would be possible to reconstruct an approximate entry from historical events, and that reconstruction would be wrong often enough to be worse than nothing. A blank you can trust beats a number you cannot.

Very large holders

Enumeration is capped. At least one address on this chain holds over a quarter of a million position tokens — a contract, not a person — and without a cap the page would attempt hundreds of thousands of calls. When the cap is hit, the interface says so and reports the real total.