[State sync engine] Push channel for state diffs

[synzhu]

[State sync engine] Push channel for state diffs

[huitseeker]

's/execution results/execution receipts/' but otherwise this is correct.

If we implement this, we need to track the hashes of the state diffs that were eagerly requested, and the normal state requester engine should later verify these once the block containing those execution results is sealed.

I suspect this is about a logic that downloads the execution data before incoporation and sealing, as soon as it's available (through receipt broadcast)?

[synzhu]

I suspect this is about a logic that downloads the execution data before incoporation and sealing, as soon as it's available (through receipt broadcast)?

Yes, and my point in that sentence is that since we cannot be sure at that point that the execution data is correct, we need to check the hash again once it is actually sealed.

[peterargue]

@smnzhu is this still needed?