Story: Lily should track Fault and Termination fees

[hsanjuan]

Description

There is currently no way of tracking fault and termination fee-events. The only way right now is to take the sum of gas burnt by messages, compare that with how f099 balance, and assume that the mismatch comes from fault and termination fees.

These fees are not explicit on chain and happen internally. For example, there is a fee on declare fault. There are fees when sectors transition to FAULTED, but on the 2nd day and onwards (I think they can recovered without penalty in the first 24h of fault).

Acceptance criteria

Fault/termination fee events are different from sector_events (a fault event not always triggers a fault fee event, and a fault fee event happens several times per sector fault).

Thus, I would like a table that tracks internal sends to f099 and that allows to track these events.

Unknowns to make informed decisions on:

• I don't know how many types of event are burning funds. Potentially there could be non-sector related events (perhaps market-related). Ideally, we would have a table for all of them but,
• Ideally, the table would allow me to list all the fault-fees/termination fees paid by a miner/sector pair. However, having that is probably incompatible with having a table for all types of fees, if there are several types of fees.

Where to begin

• Start figuring out what sends money to f099 that is not part of derived_gas_outputs already, decide on table/tables to be able to track that. Focus on delivering at least fault and termination fees tracking.

[frrist]

The miner actor uses the method burnFunds to pay/burn fees/penalties to the BurntFundsActorAddr.

The burnFunds method is called in a variety of places:

• DisputeWindowedPoSt

• PreCommitSectorBatch

• ProveCommitAggregate

• DeclareFaultsRecovered

• ApplyRewards

• ReportConsensusFault

• WithdrawBalance

• RepayDebt

• processEarlyTerminations

  • Invoked via TerminateSectors
  • Invoked at the end of the last epoch for each proving deadline and triggered by the Cron actor via miner method OnDeferredCronEvent

Fees/penalties paid by a miner can be tracked by inspecting internal messages that result from a call to the exported methods listed above. Note that the internal message table already tracks the top-level message that triggers internal messages, and once #795 lands these internal sends will be tracked.

[frrist]

blocked on #865

[frrist]

via #1027