Subsquid integration with Polkascan block explorer
3 years ago
Executed
Team Polkascan has had conversations with the people from Subsquid in which we agreed that their blockchain data archivers and public API's (Squids) are a good fit for our Polkascan Explorer. We would like to combine their efforts with ours and expand our data library and explorer with the public Subsquid services. After doing research, we've created a new proposal to make this possible.
You can find all details in our proposal document.
Comments (6)
Requested
203.90K DOT
Proposal Passed
Summary
0%
Aye
0%
Nay
Aye (256)0.0 DOT
Support0.0 DOT
Nay (25)0.0 DOT
Sorry but I voted no for this because I find some of the lingo for non technical people very hard to decipher. While I used to work with databases myself and am somewhat techy. I don't really understand what you're trying to do and I'm sure anyone else who hasn't got blockchain development experience is likely confused. I'd consider changing my vote if the description would clearly explain in a non technical way what benefits this funding actually brings to Kusama / Polkadot from the Polkascan team ? Thanks
Hi, Thank you for your feedback. One benefit is cost savings for (para)chain teams. They will be able to use Subsquid's managed data providers for their self-hosted Polkascan block explorer. This removes the burden of hosting and maintaining Polkascan backend software (database, harvester, GraphQL API) on their own servers. Another benefit is that application developers won't have to write different code for different data providers - each having its own call structure and data types. Instead, our improved software package will provide one API that retrieves and transforms data from multiple providers in a consistent/coherent manner. I hope this clears it up for you. I've added it to the top of our document.
Hello! I guess I am late to asking this if I missed the discussion. But, in good faith, as an established team, is there any reason why the Polkadot treasury can't be used for ongoing development saving the Kusama treasury for new teams and experimental building?
Hey there, thanks for your question. With all respect, do you have a source that says Kusama treasury spending is only for new teams and experimental building? Our work benefits the Kusama community just as much as the Polkadot community. I understand your rationale, but the new open source Polkascan Explorer stack has always been funded by the Kusama treasury. Continuing development on this track would be the logical step for us.