Implement eth_getLogs endpoint

[acolytec3]

Not 100% sure what all goes into this but at a minimum:

• Add support for transaction receipts to history network
• Look at EthereumJS client and see how getLogs is implemented
• Build out some sort of canonicalIndex for transaction -> block mapping
• Add getTransactionReceipt to history protocol
• Add getLogs method to history protocol
• Integrate getTransactionReceipt and getLogs in browser and cli clients

cc: @ScottyPoi this will serve as our tracking issue for receipts/logs. Feel free to add/update/whatever or comment here as we learn more

[acolytec3]

I've done some initial research on how receipts are handled in the ethjs monorepo and I think we might need to just copy some small bits of code. The receipts stuff is spread across vm and client. Since we're just handing the data structures, we definitely won't to bring in all the dependency bloat that would come from importing the client and vm just to get a few helper methods.

• A useful type example for the receipt
• Possibly useful helper method for constructing rpc formatted receipts

[ScottyPoi]

I started working it out in the browser client and came to similar conclusions.

Is the idea, generally, that the network will store receipts individually by transaction hash? Or are we trying to store whole blocks worth of receipts?

[acolytec3]

No, per [this][(https://github.com/ethereum/portal-network-specs/blob/master/history-network.md#receipts) the receipts are stored per block. So if a block has transactions, there should be a corresponding list of receipts that are passed around the network as one blob of data encoded per the typing in the spec.