Hey @huangkuan, sorry for the slow response. Returning to the original list:
- Logs in transactions: this is currently blocked by Graph Node <> Firehose integration for Ethereum (in progress, tracked at a high level here). Logs are part of the receipt in the Firehose type, so will be readily available. Though the challenge might be parsing those logs (would need ABIs for all the relevant contracts, or at least a means of parsing them somehow)
- Performance: a few of your issues relate to the time taken to sync. We are currently working on performance for token-based subgraphs specifically. Nothing to track here yet, but there will be.
- #Wallet: this is tracked here, though this hasn’t been prioritised, and I think this may actually be better served by tracking contract creation via the Firehose, once available.
- Token sales: one quick note on sales, it’s not enough to rely on
transaction.value, as in certain cases (e.g. multisigs) there will be ETH value transfer for a transaction, even if the transaction itself has zero value. - Off-chain data: work has started on File Data Sources, which would be the first requirement for the arbitrary HTTP data that you require.
Your specific use-case (on-the-fly analytics) does encounter some issues with the existing subgraph API. I will be in touch with you directly to discuss the latest thinking on changing that.