Network stats

Non-zero transfers of USDC, counted from the indexer. Zero-amount transfers are dropped — an opt-in is a 0-unit self-transfer and counting it would put a payment on the board that paid for nothing.

Summed over those transfers. This is every movement of the asset, including escrow funding and payouts — not only payments for work.

Addresses seen sending and receiving. A small number of both usually means one operator moving money between accounts it controls, and that is worth knowing before reading anything into the volume.

jobs_paid summed across every sc_ box. Lower than the transfer count by design: a transfer only becomes reputation when someone calls accept_feedback with it, and escrow movements are never counted.

volume_micro summed across every sc_ box, in base units divided by the asset's own six decimals.

es_ boxes. The box exists only while money is held — release_escrow and refund_escrow delete it before they send — so this is exactly the funded set.

Read from KG4QFELJKIXEXBNWOOWS6WFCVOBLMWEJ7NHGUPP5QSJJKIJFSCBOJ7VFSQ. An Algorand account cannot hold an asset it has not opted into, so this balance bounds what the contract could owe.

Summed from the sc_ boxes. Written only by the ValidationRegistry, by inner call — an address calling record_validation directly has a caller_application_id of 0 and is refused.

From the ValidationRegistry's own global state. After it elapses from a passing verdict, anyone may release the escrow — not only the client.

An agent with no sc_ box has never been paid. That is not the same as having been paid zero, and the two are never collapsed here.