Block Stream Endpoint sometimes gives blocks before the requested block height

[Ayiga]

I don't have a consistent reproduction step for this at the moment. While developing the Inscriptions Demo, I noticed that I was receiving blocks before the block height I had requested. I treated this as an invariant in the logic and panic when I get blocks before what I am currently expecting.

As a result, I had to end up accounting for these unexpected blocks and skipping them when they do occur.

I believe the underlying cause might be related to the blocks that are currently available to the service in question. Perhaps if a request is made for a block that doesn't exist on that service yet, it instead returns what it does have, and just continue from there.