open nav
Back to Medium Spender
Rejected
Requested:
1.19K KSM

#209 ParaSpell XCM SDK Maintenance funding for 5months

Proposer:
Dudo50 | ParaSpell
 
in General
Beneficiary:
(1.19K KSM)
27th May '23
(Edited)
treasury
xcm
research
+2

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.

Show More

Proposal Failed

The approval was lesser than the threshold for this track.
Summary
Failed
38.8%Aye
AyeNay
61.2%Nay
Ayes(96)
107.44K KSM
Nays(201)
169.29K KSM
Support
67.77K KSM
Issuance
15.93M KSM
Voting Details
Approval0.00%Threshold0.00%
Support0.00%Threshold0.00%
Please Log In to comment
Users are saying...
Based on all comments and replies

Overall 75 % of users are feeling optimistic. Join AAG this Monday at 3:30pm UTC with a team member to understand the proposal's importance to tokenholders! Reach out via Matrix for details and thank you @447368856cec4afcae909c71d. We appreciate your support, Team ParaSpell.

Overall 25 % of users are feeling against it. The text criticizes those voting against funding maintenance for Polkadot and parachain APIs, arguing that it will save developers time and effort by simplifying the implementation of XCM capabilities in applications. The author encourages voters to consider the benefits of interoperability between Kusama & Polkadot before casting their vote.

AI-generated from comments

4Comments
0%
0%
75%
0%
25%
Jay Chrawnna
 
 
30th May '23

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! 🙏

Hide replies
Dudo50 | ParaSpell
 
 
30th May '23

Dear @447368856cec4afcae909c71d,

thank you for the invite. We appreciate it and gladly accept.

We hope, that this will help the Kusama community with clarification of our proposal.

With kind regards,

Team ParaSpell

asteeber
 
 
1st Jun '23

Voted Aye

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.

Hide replies
Dudo50 | ParaSpell
 
 
1st Jun '23

@asteeber,

Thank you for being so supportive, we really appreciate, that you find our work valuable and even more so, that you took the time to actually read our proposal before voting.

As I've mentioned, the ParaSpell team is here to answer any questions regarding our project during this referenda period.

We will also present ParaSpell on AAG next Monday. Can't wait for it because we hope, that we will be able to bring more clarity to the Kusama community in regard to what our project does and why we believe, that it is very needed in the ecosystem. At least in its current state where XCM is so diverse to implement manually.

With kind regards, Team ParaSpell

Jay Chrawnna
 
 
6th Jun '23

A member of the team joined AAG on June 5, 2023. Watch the clip 👇 (8:46) https://twitter.com/TheKusamarian/status/1666094384629288961

OpenGovAssist
 
 
13th Aug '23

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

#508
KSM
Submitted

Remove Gabe from the fellowship

Members of the Fellowship Collective involved in projects flagged by the OG tracker should provide a proper explanation, return the funds to the Treasury, or face expulsion.

See More

24th Mar '25
50%
50%

Fellowship Admin

Fellowship Admin

#508 Remove Gabe from the fellowship
KSM
24th Mar '25
50%
50%

Members of the Fellowship Collective involved in projects flagged by the OG tracker should provide a proper explanation, return the funds to the Treasury, or face expulsion.

Invarch failed to provide the first two, so Gabe, a founding member of the team, does not meet the ethical standards required to have a voice in the Fellowship.

TENETS (extract from the fellowship manifesto)

"Members are expected to faithfully uphold the following tenets.
Clarifications to the rules should be in agreement with these tenets. Acting in clear breach of these tenets may be considered by voters as grounds for non-promotion, demotion or, in extreme cases, exclusion from the Fellowship.


(1) Sincerely uphold the interests of Polkadot and avoid actions which clearly work against it.
(2) Respect the philosophy and principles of Polkadot.
(3) Respect the operational procedures, norms and voting conventions of the Fellowship.
(4) Respect your fellow Members and the wider community"

See More

Submitted
#509
Jay Chrawnna
Deciding

KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!

See More

24th Mar '25
99%
50%
50%

Treasurer

Treasurer

#509 KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
Jay Chrawnna
24th Mar '25
99%
50%
50%

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

  1. Tests - Smart contract test
  2. Smart contract - ZK shielded smart contract with KSM and multi asset support on Westend or Paseo
  3. Basic UI - A basic UI for interacting with the smart contract

Milestone 2, UI + XCM:
$9,900
1 month

  1. Tests - tests for all features
  2. User interface design - UI design
  3. XCM transfers - XCM transfer assets in UI
  4. Fixed amount transfer only - Allow fixed amount transfers in the UI

Milestone 3, Mainnet Deployment:
$16,900
1 - 1.5 months

  1. Contract Migration to Kusama Assethub - Migrate contract from Testnet to Kusama Hub
  2. Public documentation - Documentation for using Kusama shield and developer integration documentation
  3. Test - tests for contract
  4. 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
#510
KSM
Submitted

Secure Funds

To prevent potential mismanagement of Youdle DAO treasury funds, we propose temporarily transferring these assets to the Kusama Treasury, which is now the safest option.

See More

30th Mar '25
50%
50%

Root

Root

#510 Secure Funds
KSM
30th Mar '25
50%
50%

To prevent potential mismanagement of Youdle DAO treasury funds, we propose temporarily transferring these assets to the Kusama Treasury, which is now the safest option.

Rationale:

The Invarch team, which currently controls the funds, has a history of questionable financial decisions, including the transfer of more than 200K ASTAR from the DAO to a CEX without transparency.

Community members have raised concerns and asked questions about fund management, but the team has not provided clear answers.

To ensure responsible management, these remaining funds (400 KSM) should be safeguarded under Kusama governance.

Next Steps:

The funds will later be returned to Youdle DAO holders through a transparent and verifiable process.

 

We urge the community to support this measure to protect DAO resources.

 

Evidence:

Rug on virtuals

image.png


image.png

 

Polkadot treasury rugs

image.png

 

Youdle DAO rug

Moving DAO funds to a CEX because it's a shared address instead of moving to another on chain address? No answers. 

image.pngimage.png

image.png

Pink rug

Pink distributed by the pink team to invarch was supposed to get distributed to the community

image.png

but instead 2000000 pink were allocated to xcastronaut (invarch founder) wallet

image.png

image.png

Then went to hydration and got sold.

VARCH rug

$VARCH token launched less than 30 days ago. ICO investors are down -96%
image.png


KSM partial rug

Not fully delivered. 

image.png

Tinkernet rug

Tinkernet (kusama parachain) was shutdown. Investors were given 4 VARCH for 1 TINKER. VARCH was later a rug so this converts Tinkernet in a rug. Before shuting down they made an LBP in Osmosis (Cosmos) which also was a rug. 



See More

Submitted