Jannis Pohlmann

I'm getting it on Linux as well, in other projects (usually after a few `reload`s or test reruns inside the same boot process). Having said that, I'm not interested in...

## Rationale / Use Cases I think Yaniv's original description covers this. We need this for users to be able to query blockchain-intrinsic data from Ethereum (blocks, transactions, accounts, transaction...

@Zerim Thanks for all the comments, I've incorporated them into the `@import` design and as decisions under the open questions. About the other feedback/questions: 1. I think it'll just have...

@leoyvens I'll come up with an estimate of the storage this would occupy. A rough guess based on 10M blocks with 150 transactions each would involve maybe - 10M block...

@leoyvens I agree with that, although I expect a few of the transaction receipts fields to be crucial enough so that we have to pull them in (thinking about the...

@leoyvens There is one argument for storing logs though: almost every subgraph today defines entities that correspond to the event types and series the events almost 1:1. If we can...

Revised plan without [subgraph composition](#1202). ## Requirements * Supports at least: - blocks - transactions - transaction receipts - internal transactions - logs - contracts (with balances) - accounts (with...

> @Jannis Has this project been tabled/abandoned. It has been paused but not abandoned permanently. Adding transaction indexing to the existing codebase wouldn't actually be that hard. The difficult part...

It looks like we could depend on https://github.com/ewasm/ewasm-precompiles/blob/36dce2e652cc0687bbd5ecff7d74c7e39e8fb914/ecrecover/src/lib.rs#L20 to provide this method.

We could easily provide a helper to generate unique IDs, e.g. ``` let entity = new Entity() ... store.set('MyEntity', store.uniqueId(), entity) ``` Would that be sufficient and good developer experience...