Christopher Goes
Christopher Goes
> In IBC, a client's "local" clock is the BFT time of that chain (ie. the median timestamp of the last commit from the validator set ...), so this check...
Don't we just need for there to be _a_ block proposer with the appropriate data availability who we can somehow elect? In theory, couldn't the block proposer be part of...
Hmm, is there a reason we can't just keep the timeouts as-is when we aren't running consensus rounds? In "lazy mode", the acceptors shouldn't be sending any message at all...
It's not a hard requirement for the release candidate, but we should implement it ASAP.
@sug0 Which keys are you talking about specifically?
I see - do I understand correctly then that these keys are not currently used (they would be used for the Ethereum bridge)?
Let's just leave this issue for now.
@sug0 Is there a concrete case where we would need to do this?
@sug0 Are you referring to a node-local log here? Where are these 50k events being held? Can't they just be written to files or something?
@grarco Is this still applicable?