What's covered

Compound V3 on Base is a separate deployment from Compound V3 on Ethereum — five Comet markets of its own, with their own collateral rosters, their own risk parameters and their own accounts — so the two are separate explorers rather than a switch inside one. A Comet market is single-base and multi-collateral: one asset is both the lend and the borrow side, every collateral asset backs borrowing of that base alone, and nothing is cross-collateralised between markets. So a wallet has a separate standing and a separate liquidation line in each market it touches, and this explorer never states a combined one. It also never totals across them, because they do not all measure in the same unit: four quote in dollars and cWETHv3 quotes in ETH, which is the unit each market's own oracle answers in. That unit is a fact about the market rather than about its base asset — cAEROv3's base is the volatile asset and it still quotes in dollars. What sets this explorer apart from Compound V3 Ethereum's is where each figure comes from, and in one respect it reaches further. The Ethereum listing is a replay of an indexed event stream; this one is not a replay at all: every (market, account) pair that ever held a position is found from the five Comets' own events, and each row's base and collateral are read from that Comet at one named block by a chain sweep, so a listing figure is a fact the chain stated rather than a reconstruction — and the page states its own completeness, how far the history walk and the sweep have each got, rather than letting a partial roster look whole. Opening a row answers the whole wallet at once — every market in the roster asked about the account, and every Comet's own logs swept for the address from the earliest market's first block, so the history reaches each position's genesis rather than a recent window, and the economics tower can state lifetime flows and the interest inside the debt. Comet has no borrow or repay event — a withdrawal past the balance is the borrow and a supply against a negative balance is the repayment — so those flows are read off the running balance's zero crossings, as the protocol itself defines them. Because the sweep runs live rather than out of an index, its completeness is a property of each request rather than of the explorer, so every timeline states underneath itself which blocks it read and whether any of them would not answer. Two facts of this deployment are stated rather than smoothed over: one market's borrows stand above its supplies, which is the borrow index outrunning the supply index by the spread between the two rates rather than a shortfall, and four different proxies on Base answer to the name cUSDCv3, only one of which Compound governance deployed — so the roster here is settled from the Configurator's own deployment log rather than from a name.

Moonwell is a Compound v2 fork, and Base is where it actually runs: twenty-one markets against Ethereum's four, and tens of millions supplied against a few million. The two are separate deployments with separate contracts, so they are separate explorers rather than a switch inside one — a wallet's position on Base says nothing about its position on Ethereum. What sets this explorer apart from Moonwell Ethereum's is where each figure comes from. The Ethereum listing is a replay of an indexed event stream; this one is not a replay at all. Every wallet that ever held a position is found from the twenty-one markets' own events on the Base box — with a routed mint or redeem resolved to its real owner through the same-transaction transfer leg, the way the Ethereum index does it — and each row's balances, debt, exchange rates and dollar values are read from the mTokens, the Comptroller and its own oracle at one named block by a chain sweep that revisits accounts with new activity and never-read accounts first, then everything on a rolling schedule. So a listing figure here is a fact the chain stated at a block the row names, never a reconstruction, and the page states its own completeness — how far the history walk and the sweep have each got — rather than letting a partial roster look whole. Opening a position asks the chain for that one wallet's whole history live, though not in the way it is cheap on Aave: a Compound v2 market indexes nothing on its own events, so Rails anchors on the reward distributor — the one contract on this deployment that names the account on every action — and reads each transaction it names, from the Comptroller's first block, on every request. That is why the timeline reaches the position's genesis rather than a recent window, why the economics tower can state lifetime deposits, withdrawals and the interest inside the debt, and why the account surface can say which of a wallet's supplies are actually entered as collateral (minting alone does not enter a market, and an un-entered supply backs nothing) beside the Comptroller's own verdict on how far it sits from liquidation. Because the sweep runs live rather than out of an index, its completeness is a property of each request rather than of the explorer, so every timeline states underneath itself which blocks it read, whether any of them would not answer, and — on an account with more transactions than one request reads — from which date onward its history is drawn. Two facts of this deployment are stated rather than smoothed over: two markets carry a supply cap BELOW what they already hold, which is governance closing them to new deposits rather than a ceiling being breached, and two different markets both answer to the mToken symbol "mUSDC" (the bridged and the native USDC), so only an address identifies a market here.

Seamless is an Aave V3 fork on Base, verified as one by interface rather than by reputation: its Pool answers the identical account, reserve and configuration calls, which is what lets the same reader serve it. So the model is Aave's — one Pool, one cross-collateralised account per wallet, one health factor — and everything the Aave V3 Base explorer says about reading risk off each reserve's own configuration word holds here too. What is different is that this market is closed. All eighteen reserves were frozen in a single block on 15 April 2025, which is one governance action rather than a market fading asset by asset, and the freeze was read off the chain by binary search over the frozen bit rather than taken from an announcement. A frozen reserve still accrues interest, still liquidates, and still lets a holder repay and withdraw; what it will not accept is a new supply or a new borrow. So every rate and threshold this explorer shows is live and enforced, and none of it is an invitation — which is why the surfaces say so rather than leaving a reader to infer it from a borrow APR on a market nobody can borrow from. The listing here is not a replay: every account that ever touched the Pool is found from the Pool's own events, and each row's balances, health factor and dollar values are read from the Pool, its reserve tokens and its oracle at one named block by a chain sweep, so a listing figure is a fact the chain stated rather than a reconstruction — and the page states on its face how far the history walk and the sweep have each got, rather than letting a partial roster look whole. The census has an unusual shape here, and it is worth naming: because the Pool is frozen, the set of accounts that can ever hold a position on it is closed and can only shrink, so once taken it stays complete rather than going stale. That is true of no other explorer on this roster. Opening a position asks the chain for that one wallet's whole history live — Rails sweeps this Pool's own logs from its first block on every request — which is why the timeline reaches the position's genesis rather than a recent window.