Right now, I believe the client needs to avoid telling go-f3 about more than 99 (CHAIN_MAX_LEN-1) tipsets. Otherwise, we'll attempt to propose more than 100 tipsets in a single instance and fail the validity check.

We need to implement a rate-limit and, IMO, the right place to put this is in go-f3 itself. I.e., let the client tell go-f3 about as many tipsets as it wants but have go-f3 take chunks of at most CHAIN_MAX_LEN tipsets at a time.