The discussion prior to proposal link
On behalf of our team, we propose the creation of a ParaSpell XCM SDK & XCM UI Maintenance Bounty that will work to aid team that have been previously funded by the Basilisk Parachain team and the Web3 Foundation which also proposed the idea of Treasury Bounty funding for this project here: link
More information on project funding and achievements can be found in our official docs: link
This bounty is for maintaining infrastructure and performing continued operations to improve SDK in many useful ways mentioned in our application document below.
Hence, the Maintenance Bounty is meant to be open-ended, with the funds being distributed through child bounties that cover work for team that will take care of the continued development of the essential infrastructure. The following proposed child bounties contain mainly the recurring tasks for checking XCM support, resolving issues raised by developers, and implementing new ideas that could further improve already very useful XCM SDK and UI.
We believe that this tool is needed in this ecosystem and we are working very hard to prove this. Unification can bring ease of integration and speed of dApp development significantly. This Polkadot forum post goes to show, that developers actively search for such tool. link
Links for repositories:
SDK - link
Organization with all repos - link
Further information on the bounty mechanism, management of the funds and budget can be found in the bounty proposal document.
No comments here