Allen Day

Related issues, with emphasis on stream processing. https://github.com/blockchain-etl/ethereum-etl/issues/216 https://github.com/blockchain-etl/ethereum-etl/issues/215

Another related issue for indexing: https://github.com/blockchain-etl/ethereum-etl-airflow/issues/28 Here the proposal is to cluster/partition the results in BQ to reduce IO. I suggest we take this a step further to generally support...

@sinahab @epheph @jieyilong FYI we are designing a generic solution for ABI event generation in this issue and also blockchain-etl/ethereum-etl#216

I was thinking of this when reading @askeluv 's blog post: https://towardsdatascience.com/how-to-get-any-ethereum-smart-contract-into-bigquery-in-8-mins-bab5db1fdeee If we implement clustering/partitioning, it should be possible to reduce the query cost of using the `logs` table...

in many cases it will be enough to get the ABI, e.g. https://etherscan.io/address/0xbe6161704f1f5cd89f49f790137f33cef2bb8554#code

And #15 Polygon I'm not sure the overlap but the # of contracts is about 1/10 of what's on ETH Testnets I think we should ignore.

it's also a different API key 1. yes, works for me 2. either way - whatever is less work since I'll be using DBT to transform them post-load to BQ...

RE #9 we have Polygon in BQ but not yet BNBChain

this is probably the same as issue #29

```sql SELECT address FROM `bigquery-public-data.crypto_ethereum.contracts` WHERE DATE(block_timestamp) = "2022-11-23" ``` can run this once a day using a DATE interval instead of a specific day in WHERE clause. This will...