ParaSpell XCM SDK Maintenance funding for 5months
Dear Kusama community,
On behalf of our team , we propose the maintenance bounty of a common good tool enhancing experience on the Polkadot ecosystem - ParaSpell XCM SDK & XCM UI that will work to aid team that have been previously funded by Web3 Foundation (phase1,phase2,phase3) which also proposed the idea of Treasury maintenance funding for this project here: link
More information on previous project funding and achievements can be found in our official docs: link
We created XCM SDK that connects all 46 currently compatible Parachains together into a tiny package that is very simple to implement and saves a ton of time for developers looking to integrate XCM support into their dApp. As new Parachains keep integrating XCM support we need to keep XCM SDK maintained to satisfy the growing needs of developers that are integrating this package into their dApps.
This maintenance proposal is for maintaining repositories and performing continued operations to improve XCM SDK & XCM UI in many useful ways mentioned in our application document below.
We believe that this tool is needed in the Polkadot ecosystem and we are working very hard to prove this. Unification of XCM pallets which are currently very diverse can bring ease of integration and speed up dApp development significantly. This Polkadot forum post goes to show, that developers actively search for such tools. link
Links that might interest you:
Link to the pre-proposal discussion held between 20.May-27.May: Polkassembly, Subsquare
XCM SDK - link
An organization with all repositories - link
Our current metrics can be seen here - link , our SDK is also implemented by the biggest Polkadot NFT marketplace called KodaDot.
Comments (4)
Requested
Proposal Failed
3
of 3Summary
0%
Aye
0%
Nay
Aye (96)0.0 DOT
Support0.0 DOT
Nay (201)0.0 DOT
Hello! We invite a member of the team to join AAG this Monday at 3:30pm UTC to help us better understand this proposal and its importance to tokenholders! Please reach out on Matrix @ jay-chrawnna:matrix.org Thanks! 🙏
I would challenge anyone who's voting NAY to attempt to build a script using nothing but Polkadot & parachain APIs to XCM KSM to any parachain and back. Go ahead and build that script, make it open source, and I'll request a tip for you. Oh, and if your script doesn't work in 5 months I'll mercilessly blast you on Twitter, Element, and here on Polkassembly. Go ahead... Yeah, it's ridiculously tedious. Not to mention that you have to keep track of the documentation of both Polkadot API and whatever parachain API to make sure your script is always working. Dev tool kits like this make it very easy to implement XCM capabilities in applications. I have no idea why people are voting NAY for something that will save hundreds of devs many hours of banging their heads against the wall. Let's pay ParaSpell to bang their heads against the wall for all of us. This maintenance funding will allow devs to focus on the actual meat and potatoes of their applications rather than needlessly spending time implementing XCM raw dog. The easier it is to use Kusama & Polkadot's *flagship feature of interoperability*, the better it is for all of us. Try using your brains before you vote NAY. If you vote NAY on this, you're a buffoon to me.