Thanks for the explanation, makes a lot of sense now understanding the concern with microforks.
What I wonder though, couldn't condenser itself bridge this delay with a cached estimate which then gets refined and solidified after 2-3 blocks of time? Basically having an instant response at the cost of a slight and momentary inaccuracy (payouts in $ are anyway in flux even if rshares don't change). I may miss problematic implications this can have but I consider it worth thinking in that direction since responsiveness is so critical for the user experience. Thanks!
Adding code to condenser to estimate it is possible, but if we're going to make hivemind faster soon, it's probably not worth it.
Sounds great.