rene

TODO: - [ ] #688 - [ ] https://github.com/celestiaorg/celestia-node/issues/853

Create a test in hive that spins up a few nodes and makes one of them mining, then checks to see if its new blocks are included in other nodes'...

I'm making a reference issue here to follow up on a couple of inconsistencies between the graphql tests and the [graphql spec](https://eips.ethereum.org/EIPS/eip-1767). I opened an [issue](https://github.com/hyperledger/besu/issues/1577) on Besu to discuss...

Seeing as wilma has already been added, here is a new addition.

nodebuilder/state: `CoreAccessor` should only restrict state writes, not reads, on fraud

3

Right now, we blanket stop the entire `CoreAccessor` upon receipt of a fraud proof, but it should only restrict **writes**, not **reads**, meaning the connection to core client should not...

If large ranges of headers are requested, split range into smaller ranges and spread the requests out among X amount of peers.

core/fetcher: Change `GetBlockInfo` implementation to take an int64 instead of *int64 to restrict potential `nil` case

1

Just noting that we always call this method with a concrete `&block.Height` taken from a block that was received via a new block event. So this will never be called...

Reconsider behaviour for `GetRangeByHeight`

3

**Current behaviour**: `GetRangeByHeight` goes from `to-1` -> `from`, meaning for a request of [200:300] where the node only has [200:299], no headers would be returned an an err code `ErrNotFound`...