EQL is being designed to replace SQL for Ethereum - better, faster, stronger by memeplex.eth10 🥝 • 2y • | |
Recommended by 3 curators | |
Glad you think it’s cool! There’s a lot of new product features coming soon. Feel free to give feedback and share with others! I wonder, how are you going to solve this internally: Getting the data? In a previous project, attestate/crawler, I ended up writing an ETL pipeline to connect the various data points. We tried using it for crawling all music NFT data, so not only onchain ownership records, but we also had to crawl the tokenURI. It was actually really fun, engineering-wise, but a huge mess to get everything done correctly. As an aside, that crawler is still powering Kiwi News today, so I guess I did a decent job hehe Anyways, I feel like since then you‘ve been put into an even worse position than me with all these new L2s launching. For me it was just Mainnet and IPFS! Are you planning to just blanket index all of them or what‘s your strategy? I rarely—if ever—shill the project I work on, but in this case, it might actually be useful for accessing the data you need - without the constraints of RPC: https://sqd.dev/ We got most of the EVM chains &L2s integrated and can get someone from our team to help with setting it up :) It'd be very neat as a showcase. Thanks Tim, curious why you chose JavaScript was that for developer accessibility? Would assume there would be more performant languages for indexing. I write JS professionally for 10 years now so that‘s the most efficient path from concept to implementation | |
Characters remaining: 10,000 comment guidelines | |
