$SUBINDEX SAME BASKET · SUPPORTS INDEX 17-ASSET STRESS TEST

Payouts are keeper-driven, not autonomous. Every distribution step on every treasury is submitted by a single externally-owned wallet, in scripted bursts of five to seven transactions inside roughly sixteen seconds: harvest → claimProtocol → commit → finalize → payout. The bursts arrive one epoch apart, which is what a scheduled job looks like on chain.

Why that matters if you hold one of these. A treasury's epoch is therefore a minimum interval, not a guarantee. No holder can force a distribution, and if the keeper wallet runs out of gas or stops running, payouts pause across every coin at once. The protocol's own disclaimer names keeper availability as a dependency; it is rarely quantified, so we track this wallet's gas and time-since-last-run and treat them as the ecosystem's liveness signal.

The protocol fee is being collected. claimProtocol runs on the same cadence as the payouts and the proceeds arrive as tokenized stock in the keeper wallet, which forwards them onward. We have not observed a transfer from there to the $INDEX distributor or stock treasury, so any claim that the protocol's cut is recycled to $INDEX holders is, on the evidence we can see, unverified at the final hop. We will publish it either way when the trail resolves.

What is live, and what is a snapshot — the honest split

Prices, liquidity, volume, holder counts, keeper gas, keeper activity, pool creation, your wallet's transfers: all read live in your browser at load. The treasury registry — which coin is bound to which treasury, its basket, epoch, split and round count — is a scheduled snapshot, and its age is stamped in the header.

Why the registry is a snapshot, and not laziness

The treasury contracts on this chain are unverified: they publish no ABI, so their getters cannot be discovered from chain data alone. Reading them from your browser would mean guessing function selectors — we tried, and they return nothing. Publishing guessed numbers is worse than publishing a labelled snapshot, so we label it. We are deriving the same fields from treasury event logs, which removes the snapshot entirely.

Dividend attribution

Incoming token transfers to your address are matched against the treasury registry and the $INDEX distributor by sending contract. A payment from a treasury is attributed to that treasury's coin; that is why the SOURCE column can name a memecoin while the asset received is a stock.

Payout rounds and countdowns

Round counts come from finalized rounds. The countdown is last round + epoch. Because execution is keeper-dependent, a countdown past zero means a payout is due, not that one has failed.

Prices, market cap, liquidity, volume

DexScreener, deepest pool per token. Coins still on the bonding curve have no external pool and are marked CURVE rather than shown as zero — absent data is labelled absent, never rendered as a zero.

Wallet access

The connector requests your address only (eth_requestAccounts) and nothing else. We never request a signature, never construct a transaction, and never ask for a key or seed phrase. Watch-only mode needs no wallet at all — paste any address. Nothing is sent anywhere: the lookups go straight from your browser to public explorers.

What we will not do

We do not label projects as scams, do not publish accusations about identifiable people, and do not give buy or sell recommendations. Where a structure is unusual — a large creator cut, a concentrated holder, an unverified fee trail — we print the measurement and let it speak.

Corrections

If a figure here is wrong, it is wrong in public and we want to know. We have already retracted one of our own indicators after proving it could never fire; that record stays visible rather than being quietly deleted.