Fix the HTTP-bridge chain-producer

[KtorZ]

Issue Number

Overview

• I have fixed the http-bridge chain producer

Comments

The listen function now entirely relies on the previous block hash to fetch next blocks (in order to avoid having to do any sort of slotting arithmetic). So in practice, we always wait for at least two blocks, consume all of them but the last one, and use the last one as a starting point. However, in the current implementation, we only get remaining blocks of an epoch from a starting point, so, if we hold and give the last block of an epoch, we never cross it to the next epoch.

I've added a little change so that, we always try to fetch some arbitrary batch size (here 1k) and fetch the next epoch this way. This is probably not 100% ideal since we'll be fetching two epochs pretty much all the time but, probably good-enough for the http-bridge.

[rvl]

When I apply this patch it does fix the listen function.

But wouldn't it have been easier to just use the slotting functions?
We could rip them out once we no longer need HttpBridge.

[KtorZ]

I am afraid that if we start using the slotting arithmetic, we get into thinking that we can. As long as we can avoid them, we remove a big burden from our business logic (not the slotting arithmetic so-to-speak, but the tracking of various protocol parameters related to this) :/

[KtorZ]

included in #137