While the offer is appreciated, we took the liberty here on AAG to suggest trying out an RFP to slightly change the scope (to Kusama Hub only) and establish a more robust set of supervisors as the builders wish to remain anonymous.
It also allows us to experiment with tendering multiple offers for a Requested Proposal!
There is likely a LOT of room for improvement here. This post will be updated with suggestions. See the bones of this RFP and leave your suggestions to make it better (or even coherent) below!
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
Developer & User documentation
Milestones
Smart contract development & testing
UI development & integration
XCM functionality implementation
Final deployment & documentation
So, that’s it! If you read this and see room for improvements please let us know below! We’ll post what we have on chain to see if Kusama tokenholders wish to set these funds aside for the development of this project!
** 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.
I think one crucial part here is going to be the frontend/UI.
The dev component is mostly solved by Tornado Cash, but having a frontend up and stay up without getting people into prison is going to be more complex. I think that component should be more heavily advertised, since it is the more delicate part of the solution.
Is the Polkadot Legal Bounty that was executed a few months ago going to provide comprehensive free legal support to the successful tenderer(s)? If so what is the cap on how many hours they’ll provide to each tenderer?
Hey,
This can be solved in multiple ways, one way that was pitched in the original proposal is to auto deploy new UI releases to IPFS, since we can utilize PAPI and other polkadot javascript libs the site could pretty much be static and a React UI could be deployed on IPFS pretty easily without to much human interaction.
I would like to try my hand in the Supervisors track, what do I have to do to be apart of that? I would also like to attempt to be apart of the development track or talent seekers.
Hey Kusama crew, EagleDAO here—huge Polkadot fans and ambassadors excited to put our hat in the ring for the Shielded Kusama Hub Transfers RFP with a couple of ideas we think could shine. With Polkadot App (Pay) beta testing coming to an end, we’re cooking up an NFC-powered payment app for Kusama Hub—imagine tapping your phone to privately move KSM or other assets, all wrapped in ZK proofs and a mobile UI on IPFS. It’d play nice with Nova and Talisman, handling deposits, withdrawals, and XCM transfers smoothly. We’re not the biggest outfit, but we’re passionate about bringing Kusama into the real world, and we’d love to team up with folks who share that spark.
We’ve also got a $WHC (Wheelhouse Construction) concept—a Solidity smart contract for Kusama Hub’s EVM, blending multi-asset escrow with a construction twist. Picture shielded funds released in phases with client and manager sign-offs, tied into XCM for parachain flow, and built with the RFP’s fixed-amount, batch-payout smarts. It’s a rough gem we’re shaping, and we’re eager to collaborate with talented devs who can help polish it. Everything’s going open-source on GitHub—community first, always.
EagleDAO’s committed to giving this our all by July 31, chasing that $43k prize, but we know we’re stronger together. If you’re a team or dev itching to jump into privacy tech with us—whether it’s NFC, ZK, or Substrate—hit us up. Let’s make Kusama prouder than ever, side by side. Who’s game?
Thanks for this Jay, I think the RFP model is really important going forward and I really appreciate the effort and ideas gone into this.
I’ve spoken with flipchan and would be happy to accept the nomination as a supervisor, HOWEVER would strongly suggest someone who is very familiar with zk on a deeper technological level also be involved as well who can evaluate the soundness of the implementation - I’m not sure how comfortable I am without having someone who can evaluate the output more technically/architecturally. I’m happy to provide more general project services, frontend feedback, UX feedback, integrations, and promotion/ensuring everything stays on track, because of course I would very much like to see this happen.
