Year-end CSV preview

See the payout CSV before you commit a drive.

The host dashboard will eventually export a single CSV per year for accountants, with one row per payout. This page is that artifact in preview form — every column explained, six sample rows you can read inline, and the same data as a real .csv file you can open in a spreadsheet.

Column reference

What every column means.

Headers are written to the file verbatim. The order below matches the CSV header row byte-for-byte.

date: ISO weekday payout date Spillway initiated the transfer (`YYYY-MM-DD`). One row per initiated payout — a host with two devices on the same week gets two rows.
payout amount: Amount paid in the payout token, rounded to 6 dp (token-native precision, not USD). For ETH this is a fractional number; for USDC/USDT it’s a stable 1:1 figure.
payout token: Ticker of the token actually transferred (`USDC`, `USDT`, `ETH`, …). The host’s payout-token preference sets this; the same host can have different tokens in different weeks.
USD-equivalent at payout time: USD value frozen to the on-screen rate the moment the transfer left Spillway. Recorded at payout time so the export stays usable for year-end accounting even after token prices move.
source storage network: Which underlying storage network the payout’s earnings were sourced from (`Spillway primary`, `Spillway ↔ Storj bridge`, `Spillway ↔ Filecoin bridge`, …). A single payout can blend more than one.
device ID: Opaque Spillway device identifier of the host whose capacity generated this payout’s earnings. The per-device granularity is the entire point of this column — payouts never roll up across a fleet.

Inline sample

Six representative rows.

Hand-picked to show every shape an eventual export can hit: a small USDC week, a mixed-source payout, a USDT settlement, a fractional (idle-day) payout, an ETH payout, and a same-date payout on a separate device.

date	payout amount	payout token	USD-equivalent at payout time	source storage network	device ID
2026-01-08	14.273841	USDC	14.27	Spillway primary	dev_aB3x7Km2nQ9pR4vT8wY
2026-01-15	28.490215	USDC	28.49	Spillway primary + Storj bridge	dev_aB3x7Km2nQ9pR4vT8wY
2026-01-22	41.708920	USDT	41.71	Spillway primary	dev_cD5f1Gh6jL8mN2sP4qR
2026-01-29	3.184762	USDC	3.18	Spillway primary	dev_cD5f1Gh6jL8mN2sP4qR
2026-02-05	0.009247	ETH	27.83	Spillway primary	dev_eF7g3Hi9jK0lM5nO7pQ
2026-02-05	22.135840	USDC	22.14	Spillway primary	dev_sT1u3Vw4xY6zA8bC0dE

Numbers above are illustrative only — they’re sized to the column-1 storage rate band to look plausible, not pulled from any live host row.

Take it with you

Download the sample CSV.

The same six rows as a real .csv file. Open it in a spreadsheet and the column order, headers, and values will line up 1:1 with the inline table above.

Download sample CSVFile: spillway-payout-sample.csv

Why this shape

Built for year-end accounting.

The export is meant to drop straight into a spreadsheet for a year-end ledger: the payout token column preserves the on-chain token paid (USDC, USDT, ETH, …); the USD-equivalent at payout time column freezes the dollar value the moment the transfer left Spillway, so the ledger is reproducible even after token prices drift; and the device ID + source storage network columns let an accountant trace any single row back to the hardware and the network that generated it.

Convinced by the artifact?

Want to see one for your host?

Tell us about the drive you have in mind and we’ll come back with a payout range for the rate bucket your hardware would land in. The install comes after you’ve seen the estimate.

Tell us about your host See the 3-step host flow first