Cool, makes more sense now.<p>At a high level it would be interesting to make it as durable as possible in situations where say F=2 but you have 30 nodes.<p>As I understand it, in this hypothetical case, the majority of the system would work fine if 3 nodes fail, but there could also be some percentage of transactions which are unfulfillable due to this scenario while there should be many that can still be answered with confidence.  ( if I&#x27;m understanding   correctly that data does not go into every node with a configuration like this and is consistently hashed across )<p>So was just curious how a prolonged period of this may turn into an unbounded problem when trying to digest your page on it.<p>Ultimately it sounds like it&#x27;s headed in a good path and embracing this partial-fail-but-that-doesn&#x27;t-mean-show-is-over with specifics is a good thing to get ironed out and would certainly be a key thing to get right early, even if it&#x27;s largely semantics and client behavior.<p>Good luck, will try to play with it soon