Ryan J. Shaw
@rjs
Solana is... interesting Dune data has weird gaps in data and timeouts when you try to lookup a tx, nothing works like EVM, it's just all so strange... and yet look at those MCs...
9 replies
1 recast
19 reactions
Brock
@runninyeti.eth
"skills issue" Up to the data consumer to decide where in the stack that lies 😉 I'm super biased, but imo, most providers add Solana as an after thought / marketing ploy. Solana data is different, and large, but it's not inherently bad. Some of it is actually very good (e.g. balance snapshots with each tx)
1 reply
0 recast
1 reaction
Ryan J. Shaw
@rjs
Who's got the skills issue? Didn't say Solana data is bad -- I see the appeal in some of what they're doing, and IMO the EVM is way too low level and it seems like Solana is designed to tackle that. I'm commenting on my experience trying to do some stuff that is very simple on Dune with EVM-based data, but nowhere near as simple or intuitive with the Solana data. When you say you're biased, I was trying to identify what product you work on... is it envio? is envio data only accessible via graphql or can I run SQL queries over it?
1 reply
0 recast
1 reaction
Brock
@runninyeti.eth
lol sorry! Yeah I should've added more context I'm building indexing.co so heavily focused on the indexing side. From my pov, Dune and others struggle with Solana because they try to shoehorn it into data models and pipelines meant for EVM (or at least don't take the time to do something dedicated) All of which leaves consumers of that data struggling to make use of it --> I meant it all as standing in solidarity with your pain points there. I can definitely appreciate where you're coming from
1 reply
0 recast
1 reaction