Every FWSS payer wallet with a live data set on PDP mainnet - one row per wallet, aggregated across its data sets,
with the wallet's live Filecoin Pay funding state. A data set that goes silent flags its wallet rather than hiding -
unless its provider has been dormant to the dealbot for 72h and the set itself has not advanced in 14 days.
One row per wallet, aggregated across its live data sets. Severity order, largest first.
Cards filter, columns sort. Terminated, dormant and deleted sets are collapsed per data set below the table.
Wallet health under the FWSS v1.4.0 pricing upgrade
Waiting for the network snapshot...
Last refresh: -Source: observer.yablu.net (indexed fwss_piece_added events, mainnet)
Second-copy onboarding progress
Four second-copy data sets for three Storacha-migration clients, onboarding to external SPs
(infrafolio, SP 7 and Mongo2Stor, SP 5). Progress = pieces committed on chain vs the client's known
piece total; every piece is exactly 1 GiB, so pieces = GiB. NFTs2Me is split across two datasets (one per SP)
and rolls up as one client.
Loading second-copy progress...
Data set health
The Network Health tab's per-set staleness view, applied to the four second-copy data sets on
infrafolio (SP 7) and Mongo2Stor (SP 5). Stale = no proving advance (possession proof or period roll)
for over 36 h with provable pieces on chain; a set that never proves flags 36 h after creation. Payer funding is the same
live Filecoin Pay state as Network Health (same payers, same accounts), shown with this tab's older freeze-horizon badge.