Market Memory · Indexed from Hook Events
Every swap leaves a trace.
The hook's afterSwap emits a typed Signal event for every trade. An indexer reads those logs and reconstructs the protocol's live activity — buys, sells, cap-hits, stakes, claims, votes — into one chronological feed.
Thesis vote opened: sellCapBps 50 -> 75 (epoch 4)
0x7B..D2 claimed 0.0008 ETH from Pulse pool
0x9F..0c sold 4,820 ORCH — Sentinel pool +0.0024 ETH
0xF3..09 sold 1,420 ORCH for 0.0014 ETH
Thesis pool grew to 84,210 ORCH (+5,000)
0xA1..7C bought 2,184 ORCH for 0.0021 ETH
Placeholder data shown until the indexer is connected to mainnet Signal events. The indexer is a thin worker that reads logs from the hook contract and serves them via a static JSON endpoint.
Why on-chain events instead of a hosted API?
Because the feed is the protocol's public record. If our indexer disappears, anyone can rebuild it from the chain in an afternoon. There is no API key, no rate limit, no privileged access — just typed events that other tools can subscribe to.