FIL—
how it's measured

ultra sound storage

Filecoin's warm storage economy, in bytes, payments and proofs.

storage

billing storage

time frame
  • monitoring excluded

stored & billing now

—TiB
end of day — · bytes

FWSS data sets with a live payment rail, known monitoring excluded, every copy counted. Definition

net change

    every live FWSS piece

    —at checkpoint

    A positive billing rate means a rail is set to stream, not that cash moved or data can be fetched. Payments and proofs are below.

    non-FWSS PDP data sets in the registry

    payments

    cash that settled onchain, and rails still streaming

    time frame

    FWSS settled

    —

    all Filecoin Pay settled

    —

    daily settled, by service

    each row on its own scale

    top payer share

    —
    of FWSS settled gross came from one address

    how a payment moves

    1. depositpayer funds a Filecoin Pay account
    2. railoperator sets a per-epoch rate while the service runs
    3. settleaccrued amount settles onchain; counted here, gross
    4. payeereceives gross minus commission and network fee

    annualized run-rate

    Current rail rates × 2,880 epochs × 365. What's configured to stream, not revenue.

    FWSS

    —

    Filecoin Pay, eligible rails

    —

    run-rate, by service

    each row on its own scale
    reading notes

    proofs & probes

    is the data held, and can it be fetched?

    time frame
    pooled successes over attempts · each source ends on its own last day

    providers · last 30 days

    dimmed: fewer than 100 attempts

    proving isn't retrievalA PDP proof shows challenged data was held at a deadline. It says nothing about HTTP retrieval.

    faults count at closureMissed periods stay uncounted until closed. This isn't live health.

    probes aren't customersDealbot is synthetic monitoring. Its wallets are excluded from billing; its probes are the evidence.

    network

    the FIL supply storage orbits

    time frame

    circulating FIL

    —

    locked FIL

    —

    minted · daily

    —
    • SP rewards
    • service stream
    • burn allocation
    • no observation

    burned · daily

    —
    • SP cron
    • message fees
    • penalties
    • unattributed
    • emission
    • total only
    • not yet available
    sector power and FIL price

    Raw byte power is committed sector capacity across all providers. It isn't FWSS capacity or customer payload.

    raw byte power

    FIL price · daily average

    reading notes

    no supply waterfallCirculating = vested + mined + reserve disbursed − burnt − locked. FDP has no reserve-disbursed source, so supply change isn't decomposed, and minted − burned isn't a circulation change.

    coverage is explicitMinted is null on days with an unobservable tipset reward; burn is null until the next day's snapshot. Totals sum observed days only.

    unattributed burnNon-emission burn minus message burn, penalties and cron burn, only on days where every part is observed. Days missing a part show as outlined totals.

    method

    computed read-only from a Filecoin Data Portal snapshot. Nothing is fetched at view time.

    snapshot, cadence and source end dates
    known monitoring wallets
    billing storage reconstruction
    • Billing storage is the payload bytes of live pieces in FWSS data sets whose PDP rail streams a positive rate, known monitoring wallets excluded. Every stored copy counts. Net change mixes pieces added or removed and data sets entering or leaving billing; it is not upload volume.
    • Every FEVM event gets an ordinal block × 10⁶ + log index. Each UTC day closes at its end-of-day checkpoint ordinal (last decoded event on or before that day).
    • A piece is live at ordinal o iff added ≤ o and (removed is null or removed > o). Bytes are the PieceCIDv2 raw payload size; copies across data sets each count.
    • A data set is billing at o iff its PDP rail has a positive-rate interval with start ≤ o < end. Contiguous positive intervals are merged into spans. A termination call is not the end: rails keep streaming until their end epoch.
    • Each piece × billing-span overlap emits a +bytes event at its start and −bytes at its end; events are assigned to the first checkpoint that covers them and summed cumulatively.
    • History is restated with today's monitoring classification: a wallet later identified as monitoring is excluded from all past days.
    payments, tokens and annualization
    quality pooling and gaps
    • Rates are Σ successes / Σ attempts across providers and days in the window; never averages of daily or per-provider rates.
    • Sampled retrievals skipped because no candidate piece was found are reported but excluded from attempts.
    • Probe sources and onchain proving have different end dates; each window ends at its own last observed day.
    • Latency percentiles are omitted: daily per-provider p95s cannot be pooled into a true p95.
    sources and SQL assets
      why “ultra sound storage”?

      A borrowed name. ultrasound.money puts one supply number at the center; this page puts one storage number at the center (bytes under active billing) with payments, proofs and probes around it as evidence.

      It makes no claim that Filecoin storage, FWSS or FIL is economically sound or sustainable. There's no verdict, no subsidy ratio, and no comparison of storage payments with network rewards.

      Why exclude monitoring? Dealbot wallets create and pay for data sets to test providers. Their bytes are real but not external demand. The remaining payers are addresses, not verified customers.

      Why not all registered bytes? Non-FWSS PDP data sets can still register pieces without billing through FWSS. A registry record alone is not evidence of current possession.