tool for calculating FWSS volume per orchestrator

[wjmelements]

It should be possible for anyone to calculate the volume attributable to an orchestrator using a filecoin RPC.

Items to resolve / update in spec

• MIN_LOT formula. Agreed in #1270: MIN_LOT(Q) = max(FLOOR, α × BoundVolume(Q−1) × FEE_RATE / MAX_PRICE_PERIODS), FLOOR a small multiple of the gas cost to claim, α and FLOOR governance-settable.
• First-print anchoring. The first post-activation auction has no prior print for PRICE_BAND and no Q−1 volume for MIN_LOT, so it falls back to FLOOR. Needs a first-anchor rule, or a FLOOR chosen for bootstrap rather than for gas.
• When SRA state takes effect. The FPV determinism clause gives three rules: rail operator at rail creation, bindings at the settlement epoch, admitted contracts for the whole quarter. Intentional split or one retroactive rule for all three?
• MAX_PRICE_PERIODS merging. In #1270: order the quarter's N qualifying prints by epoch; if N ≤ M nothing merges, otherwise partition into M contiguous index groups, group k = floor(kN/M) to floor((k+1)N/M)−1, each converted at the lot-weighted mean of its prints.
• Binding lookup. No defined read path for (payer, operator) bindings. If attribution is per-settlement we also need a list that shows binding epochs as well as attribution.
• ReassignBinding mid-quarter. Define which orchestrator gets settlements either side of the reassignment.
• Print identity and ordering. Prints are referenced by epoch, but the merging rule orders them by epoch and two qualifying auctions can clear in the same one. Do we need canonical print references? Tx hashes?
• Conversion arithmetic. Implied price is lot face value over FIL burned, and a merged period price is a lot-weighted mean. Need to be specific about rounding rules.

[wjmelements]

This may belong in the governance repo (#8) but it can live here for now

[wjmelements]

The latest proposal (slack) is to denominate volume in FIL and use the FP auction to retroactively price the tokens. This resolves an incongruity between time-weighted average price (TWAP) and volume-adjusted price that would have incentivized orchestrators to settle rails at opportune moments.

[wjmelements]

Some of the code from the filecoin-pay explorer may be useful for this

[wjmelements]

This indexes burnForFees, the method that completes an auction.

[rvagg]

We have a couple of ways to do this - the easy one would be to just use foc-observer, but that has the property of being our hosted data source and our code; it's not complicated and anyone could run it, but it would be less of an "everyone can run this" than doing it in a subgraph. A key property we want is the "anyone can verify" and a published subgraph is probably a bit more along those lines--it's a standard way of measuring things on EVM, anyone can deploy their own, you could even run your own indexer but mostly you just trust that Goldsky or TheGraph (such as the glif hosted one) are doing it properly for you.
Even if we did the subgraph, we'll still probably be cross-checking it with foc-observer because we have had inconsistencies in the past with subgraph data collection.