Alex North

> Do you mean a fraction of pledge collateral? Yes. > Sounds like you're looking for specific numbers No, but I am seeking specific formulae, where the numbers can change...

While the spec leaves these undefined go-filecoin will implement each fee as a fraction of total pledge collateral, linear in the thing being penalised: 1. fault fee as the number...

I think (2) is the least worst. I think "Optimal" depends on your POV: (4) is the worst for me.

Separate to the bitfield representation, the spec needs content similar to @whyrusleeping's [comment above](https://github.com/filecoin-project/specs/issues/119#issuecomment-457766965). This was also quite opaque to me. Go-filecoin needs this to be specified so that the...

There are various footguns possible, and we have a trade-off to make about how much complexity to add _inside_ our systems in order to prevent avoidable misuse outside.In general, I...

I concur with your "cleanest way". I believe the special handling of `0` is part legacy (when account actors did not have any code at all) and part optimization for...

ArbitrateDeal currently looks to penalise both pledge and storage collateral, which doesn't match `faults.md`. While updating, could you clarify that too?

In general, collateral is only required to be posted by the miner when committing a sector. For the first sector a miner could post (but hasn't yet, hence the need...

Changing the worker address introduces complications for the deal protocol. In order to arbitrate a payment channel or deal, a client presents a deal signed by the miner (which was...

Hi all, I'm Alex. I was born in, and am currently still living in, Sydney Australia. I have a looong flight to join you. Breakfast today, as it is frequently,...