Crypto Data Scale Problems
substack.com Crypto Data Scale Problems |
AI summary of the linked articleThe author argues that crypto data is hard to use at scale, even though it is public: smart contracts act as separate schemas that each need to be understood individually, and fragmentation across new L2s and virtual machines multiplies that work. Because global questions, such as how much a user relies on bridges, require mapping every bridge and its contracts before any unified model can be built, the author says the ecosystem often lacks a clear picture of real activity, with inflated user counts and hard-to-detect sybils making on-chain metrics unreliable. |
Recommended by 1 curator |
2 comments I once spoke with the founder of Gilded (a crypto accounting firm), and he said that dealing with data from different blockchains was a big pain in the ass. I can only imagine that the "100+ L2s" future won't make it easier. BTW the author's comments about challenges coming up with scale reminded me of the article that we once had on Kiwi about the early days of Google: Not to be a shill, this is actually exactly the problem that we're trying to solve at SQD. Sure, we're just about 12% there, but it's quite incredible how much of the data backend is badly functioning/ patchy pipelines from more than one indexing service just because none cover all the L1s, L2s, 3s. Tbf, all the L2s are definitely a pain, and modularizing further does little to aid the data access and retrieval issues - but that's why it's fun to try and build something that does fix it. |
