Peter Argue

We should do https://github.com/onflow/flow-go/issues/5185 as part of this project

@UlyanaAndrukhiv I looked at the code a bit more. I don't think we need a job queue for the receipts. They are indexed as they are received from ENs to...

> What about making the variables of the struct public, then we can create a gateway any way we like? My concern with this is that they should never be...

> This might be naive, but can we just increase the hardcoded max size to a larger value to maximize support? yea, that would work for now. we've had to...

Looks like the only errors that implement `errors.UserError` are new EVM errors. @janezpodhostnik should this be added to all of the non-failure `CodedErrors`?

@UlyanaAndrukhiv can you add details about how to set this up

I think the way to verify the data in the db is correct is to do something like this: 1. Get the node's root block using the `NodeVersionInfo` endpoint 2....

as discussed in standup, please test using `BlockExecutionData` instead of events.

I don't think this is going to work using json. you will need to use grpc to get the binary data from the GetExecutionDataByBlockID (or streaming version) with CCF encoded...

Looks like there are some compiler errors in the integration tests ``` Error: ../engine/execution/rpc/engine.go:120:51: cannot use eng.handler (variable of type *handler) as "github.com/onflow/flow/protobuf/go/flow/execution".ExecutionAPIServer value in argument to execution.RegisterExecutionAPIServer: *handler does...