A framework to build any data applications entirely on the decentralized Web3 infrastructures

Community & Grants Grants & RFPs
13

Hey thanks so much for this write up! Lots of good points here.

  1. This loading is from the subgraph endpoint on the fly? Is the bulk of that time pulling the individual entities out of the subgraph? Definitely seems like better support for analytical functionality would help here.
  2. Interesting use case, I replied on that thread about logs.
  3. This point is related to sync speed? (Which is definitely a focus area). Or also the ability to do more custom calculations on the fly?
  4. Interesting - I think we could maybe expose the getCode function in graph-ts to check for contracts, though there are some edge cases to consider (contracts might be destroyed, and I don’t know if you can getCode as of a given block height)
  5. This is an interesting point - I think we have previously discussed some of the functionality required here (e.g. subgraph composition). One thing that does occur to me is that the msg.value won’t always capture ETH transfers, if you’re using a multisig (for example). I think there is potential to use the upcoming introduction of the Firehose in Graph Node to solve some of those problems
  6. Better indexing off-chain data is also top of mind at the moment - we are working on a better model for content addressable data (IPFS, Arweave), but arbitrary HTTP endpoints make deterministic indexing impossible. I think we could apply some of the same patterns to support that in Graph Node, but that opens up a wider discussion cc @Brandon

There are quite a few areas there where we have stuff in flight, so will come back to this thread, but thanks again for sharing all the above and excited to see the progress on Bubbletea!

3 Likes