Leonardo Yvens

The `as*` APIs for JSON seem useful, but they should be put directly under `JSONValue`.

I think this could be solved exclusively on graph-cli by manifest templating. Perhaps [networks.json](https://thegraph.com/docs/en/deploying/deploying-a-subgraph-to-hosted/#using-graph-cli) could support providing an array of addresses, and would then generate one data source definition for...

Hi @Chainode and @trader-payne. @trader-payne is correct you should entirely unset `GRAPH_ETH_CALL_BY_NUMBER`. And @Chainode you're also right that the node will continue to make eth_getBlockByNumber requests, but our use of...

We will eventually want imports by name, but I agree we should keep that as a future extension.

This is interesting. Generally the protocol would not care about this metadata, I'd suggest that it is all grouped under a `metadata:` top-level key to avoid any possibility of conflict...

On ballot stuffing: In a network like Ethereum any work can be readily assigned to any stake holder. So work, and therefore inflation rewards, can always be split in proportion...

@tarrencev expressed the wish to call contracts from the graphql client, so that he could get the latest state of the contract without having to index it. This can be...

I'm concerned about the proposed implementation strategy of basically indexing all of the data contained in an archive Ethereum node. That's currently [3 TBs of data](https://etherscan.io/chartsync/chainarchive) when stored as compressed...

I agree that blocks and accounts are something we should just ingest and have great query performance for. However I'd like to make a point that transaction receipts may be...

@Jannis Having the spent gas is fine, my concern is the logs. The logs in a block explorer are not decoded, so having all logs is not the same thing...