Back to Medium Spender
Executed
Requested:
2.04K KSM
#83 Subsquid integration with Polkascan block explorer
Description
AI Summary
Votes Bubble
Timeline
Evaluation
On Chain Info
Stats
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.
Show More
Please Log In to comment
Users are saying...
Based on all comments and repliesOverall 20 % of users are feeling optimistic. The Kusama Community has successfully integrated Subsquid into Polkascan Explorer, enhancing blockchain data access and providing open-source software solutions. The team expresses gratitude to the community for their support throughout this journey. Future upgrades will be considered based on feedback received from the community.
Overall 80 % of users are feeling neutral. The team is validating the need for a service to assist teams with treasury proposals and seeks feedback on their experience with OpenGov's process. They are also considering using Polkadot treasury funds for established projects while keeping Kusama Treasury for new ventures, as it has reached an equilibrium in staking.
AI-generated from comments
6Comments
0%
0%
50%
0%
50%
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
FnhB...7tNL
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.
FLKB...svZR
Ok, thanks, but I'm aware there are many blockchain explorers and since Subsquid already got treasury funding for development, what's to stop the parachain team from using Subsquid + Subscan as a blockchain explorer for example ? What are you doing different than Subscan and why should they use your explorer ? Thanks in advance.
FnhB...7tNL
A parachain team has multiple mainnets and testnets. With our solution, Parachain teams can host their own block explorer for all of their networks, without having to pay for each network. They can also customize the explorer to their needs, because it's open source software. It's very cost effective to use Subsquid+Polkascan and a good alternative to Subscan.
Subscan doesn't use Subquid, but they have their own data provider. Our software will use Subsquid as a data provider, with the added benefit of also being able to self-host our own (open source) data provider software. By combining multiple different data providers you get a bonus layer of verifiability to your data.
FLKB...svZR
Ok fair enough, thanks for explaining. It makes sense to me now. I've changed to Aye, good luck!
FnhB...7tNL
It's great that you've given it serious thought and asked critical questions. We're always happy to answer any questions. Thank you for your vote!
E5qF...tqrg
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?
FnhB...7tNL
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.
E5qF...tqrg
Hey no there aren't any rules about that. However the barriers are lower with Kusama Treasury funding and new projects and teams start here. It's also notable that the Kusama treasury has stopped growing with staking hovering around an equilibrium. Not a lot of people realize this yet. So all funds removed from it are unlikely to be replenished with inflation.
Established teams with a good proof of work and success can save these funds for others to follow in their footsteps if they're willing engage the Polkadot treasury. I have done this with my own project that worked its way up from Kusama tips. :)
FnhB...7tNL
I understand what you're saying. For our future software upgrades, we'll look into this.
FABq...ah6h
Hello team,
Your treasury proposal was approved and funded more than 3 months ago. Could you please take the time to share an update on your progress with the Community by posting a comment in this referendum post?
Please keep in mind that, as part of treasury proposals’ lifecycle, a final report is due at the completion of all milestones to evaluate the success of the initiative. You can find a template for the treasury proposal report here.
Thank you for your consideration.
FnhB...7tNL
Dear Kusama Community,
Three months have passed since our proposal was approved. We are excited to bring you up to speed on the progress we've made.
As it stands, we have invested around 150 hours out of the projected 428 hours for this proposal. We invite you to peruse the list of commits on our dedicated development branches at the following links:
Regrettably, development was temporarily suspended for two months, from late February to late April, due to unforeseen circumstances. We have since resumed progress and are aiming to complete and deliver the proposed outcomes before summer holidays commence.
Our primary focus has been developing version 2 of the PolkADAPT data retrieval and augmentation library. In our proposal document, we described the library's novel design, which uses an Observable stream-based approach with a new API abstraction layer. For those interested, we invite you to check our new unit tests that display PolkADAPT's functionalities. We have modernized the existing SubstrateRPCAdapter and PolkascanAdapter to use the fresh common API. Our next task is to create the SubsquidAdapter, designed to reveal its own API compatible with the other adapters. Simultaneously, we are transitioning the Polkascan Explorer UI to employ PolkADAPT v2, one step at a time.
We express our deepest gratitude for your ongoing support. Upon completion and delivery of our proposed enhancements to Polkascan, we promise to provide a comprehensive final report. Your patience and support are highly appreciated.
FnhB...7tNL
Dear Kusama Community,
We are pleased to share that we have completed the tasks as outlined in the Kusama Treasury Proposal Referendum #83. Our efforts have led to the successful integration of Subsquid into the Polkascan Explorer, which now provides users with more versatile and reliable access to blockchain data. You can check out the results of our work on the development version of the Explorer.
We want to take this opportunity to extend our thanks to the community for your support throughout this journey. We're happy to provide our delivery report that details the work we've done. Your support has been essential to our progress and we're grateful for the opportunity to contribute to the Kusama network. Thank you.
HUj6...GLD6
Hello,
We are in the process of validating a true need for a service to assist teams with crafting and completing successful treasury proposals, so they can focus on building. We would love to hear about your experience with this proposal. If you are willing to take a few minutes, please fill out this form about your experience with the OpenGov treasury proposal process: https://forms.gle/MwDij4adXEQd7Um79
Feel free to leave out any details that your team is not comfortable with sharing, but the more info you can provide, the better we will be able to assess the potential need for our services.
For more info, follow us on Twitter/X: https://twitter.com/OpenGovAssist
Discover similar proposals
Root
#507 Reducing inflation and setting a realistic target for coretime sales
EvoL...oVus
Reducing Inflation
Some time has passed since our wild cousin Polkadot successfully reduced its annual inflation to 8%(with gradual reduction), as a KSM token holder I believe our loved bird is due an adjustment of its inflation parameters as well. Instead of copy-pasting Polkadot's model, Kusama can try something different, some DOT holders were left wondering if inflation could be lower, I propose we reduce it to 5%. The high initial inflation was good for early bootstrapping and incentivizing participation, the ecosystem has matured enough to aim for long-term sustainability.
Changed parameters
- Setting
MaxInflation: From10%to5% UseAuctionSlots: Fromtruetofalse.
From the docs:With the move to agile-coretime, this parameter does not make much sense and should generally be set to false.
NOTE: As IdealStake is "75%", UseAuctionSlots = true had the effect of making the real target around 45%, this is intentional as it would increase the treasury income to around 10% with current staking levels.
Reducing ideal bulk coretime sales
The reduction of inflation should be balanced with an increased demand for the KSM, the main utility of KSM is to pay for coretime(which gets burned) but current prices are virtually 0 making it hard for the system to benefit from its main product offering. Elastic scaling will help grow demand for coretime and thus KSM, there might also be new sources of KSM demand like Kreivo's memberships but we need to adjust the core business model.
A while back I proposed setting a minimum price but it was pointed out by @seadanda that a better approach is to change the parameter that controls the ideal target for sales to a value that better reflects the expected demand of the Kusama cores to stop the price from further being driven to 0 and quite the opposite drive its price up to a more realistic value.
Note that this number is not set in stone, it's a starting point that can help us better discover coretime's true value.
Changed parameters
- Setting
ideal_builk_proportion: From100%to40%
The proportion of cores available for sale which should be sold. If more cores are sold than this, then further sales will no longer be considered in determining the sellout price. In other words the sellout price will be the last price paid, without going over this limit.
As self-proclaimed Kusama enthusiast#1, not only as KSM-only holder but as full-time exclusive builder on this network for several years, I hope this proposal well received and not seen as malicious as I only have the best intentions for this ecosystem :)
See More
Deciding
#509
E5qF...tqrg
Deciding
KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
See More
Treasurer
Treasurer
#509 KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
E5qF...tqrg
This RFP was adapted over several weeks on AAG to turn a treasury proposal in discussion to an RFP with refined scope and oversight. To apply for the prize pls fill out this form.
Prize Pool: $43,000
Finder’s Fee: $2,000 **
Supervisors: $5,000
Supervisors (Bounty Curators)
- Flipchan
- Byte (Erin)
- James Slusser
Excess or unused funds will be returned to the treasury by Bounty Curators.
Timeline
Monday, March 17 - AAG Discussion & this forum post! ✅
Monday, March 24 - Single-ref Bounty + Curators ✅
4 Weeks after Bounty Funding - Submission Deadline Thursday
July 31 - Project Completion (Pending Kusama Hub Launch)
Project Scope
Smart Contract Development
- A Solidity-based smart contract deployed on Kusama Hub
- ZK enabled for private deposits & withdrawals
- Compatibility with all Kusama Hub assets
User Interface
- Browser-based, mobile-ready UI hosted on IPFS
- Support for: Deposits, Withdrawals, Transfers, XCM Transfers
- Compatible with popular ecosystem wallets (Nova Wallet, Talisman, Subwallet)
Anti-correlation Attack Mitigations:
- Fixed deposit amounts (e.g. 1, 10, 100, 1000 units)
- Batch payouts for withdrawals to multiple users
Interoperability - Ability to receive assets via XCM from any Kusama-connected parachain and transfer them to Kusama Hub for use in shielded pool.
Open-Source Delivery
- All code (smart contracts and UI) published under the MIT license
- Publicly accessible repositories Project updates shared transparently via Polkassembly, Subsquare, or Polkadot Forum from Team with Milestone deliveries
- Developer & User documentation
Milestones
Milestone 1, Initial Pools & Basic UI:
$16,200 USD
1 month
- Tests - Smart contract test
- Smart contract - ZK shielded smart contract with KSM and multi asset support on Westend or Paseo
- Basic UI - A basic UI for interacting with the smart contract
Milestone 2, UI + XCM:
$9,900
1 month
- Tests - tests for all features
- User interface design - UI design
- XCM transfers - XCM transfer assets in UI
- Fixed amount transfer only - Allow fixed amount transfers in the UI
Milestone 3, Mainnet Deployment:
$16,900
1 - 1.5 months
- Contract Migration to Kusama Assethub - Migrate contract from Testnet to Kusama Hub
- Public documentation - Documentation for using Kusama shield and developer integration documentation
- Test - tests for contract
- V1 UI - User tested & something we can be proud of
** re: Finder’s Fee: this payment is set aside to incentivize a broad search for the right implementor. Finder’s Fees are paid out at time of team engagement. Teams that submit themselves can collect their own Finder’s Fee at completion of project.
See More
Deciding
Voted Aye