<h1 id="overview">Overview</h1>
MPC{dot}Snap&nbsp;is an innovative security suite that leverages Multiparty Computation to enhance account security beyond traditional hardware wallets. As exploits and attacks become increasingly sophisticated, keys with a single entry point are becoming more vulnerable. In the Polkadot ecosystem, hardware wallets don&rsquo;t fully support all pallet functions, leaving many community members who store their keys digitally at greater risk. Snaps was introduced to the public by Metamask in September 2023 and since then this architecture has been used for different use cases while providing users more functionalities with a similar experience and no learning curve. The biggest use case for Metamask Snaps so far is providing a compatibility layer for the non-EVM chains. We already have the &lsquo;Polkadot Wallet Snap by ChainSafe&rsquo; and &lsquo;Polkagate Snap&rsquo; in the ecosystem providing just the compatibility layer for Substrate chains on Metamask. MPC{dot}Snap goes a step further. Instead of merely offering wallet compatibility, MPC{dot}Snap introduces a comprehensive suite of Snap-Dapp-App, offering a robust alternative to traditional hardware wallets through the power of Multiparty Computation. Hardware wallets become vulnerable once their keys or seeds are exposed. In contrast, compromising the MPC.Snap would require an attacker to breach two separate devices or access keys and seeds stored through two distinct methods or channels.
&nbsp;
<h1 id="impact">Impact</h1>
As MPC.Snap will support all the functionalities from existing pallets, overall it could turn out to be a better choice than hardware wallets, especially for community members who are looking to utilize the full potential of Polkadot ecosystem chains.
Outside of the EVM ecosystem, no other blockchain networks currently offer MPC-based Snap solutions. This presents a significant opportunity for the Polkadot ecosystem to introduce a leading, easily accessible, and highly secure wallet management solution. By doing so, Polkadot can not only enhance security for its users but also attract new users from other ecosystems, thanks to the minimal learning curve of the snap architecture inherited from Metamask.
In many regions, the cost of a phone is significantly lower than that of purchasing or importing a hardware wallet. This disparity creates a substantial barrier to accessible security for community members from various demographics and countries. MPC.Snap addresses this challenge by offering a more secure solution without any additional cost, as it can be utilized across two devices, with only one needing a camera. By lowering the entry barrier, MPC.Snap ensures that robust security is within reach for all users, regardless of their location or financial resources.
&nbsp;
<h1 id="projectdetails">Project Details</h1>
<h3 id="mpcsnap">MPC.Snap</h3>
MPC.Snap features an intuitive in-snap UI for conducting transfers and signing data, offering users a streamlined and efficient experience with or without companion dApp/UI. It securely holds the first key of the TSS {2,2} MPC pair, playing a critical role in our advanced security framework. Additionally, MPC.Snap is designed to be chain-agnostic, ensuring Polkadot ecosystem-wide support for all the substrate chains.
&nbsp;
<h3 id="dapp">DApp</h3>
Our Dapp serves as the bridge between the MPC Snap and the mobile app, enabling a smooth pairing process. It&rsquo;s built with user-friendliness in mind, providing easy onboarding and a guided pairing experience to ensure that users can set up their secure wallets in just a few simple steps. The recovery mode will also provide a guided experience for account backup &amp; restore in case of device change. The DApp&rsquo;s &lsquo;Snap Store&rsquo; segment features all the snap-ready protocols from the Polkadot ecosystem, along with the support for convenient mini-apps.
&nbsp;
<h3 id="mobileappssdk">Mobile Apps &amp; SDK</h3>
The mobile apps, available on both Android and iOS, are designed for convenience and accessibility. Users can utilize either the front or back camera to scan the pairing QR code, ensuring a flexible and straightforward setup. With a focus on UX/UI, the app can support multiple accounts and holds the second key(s) of each TSS {2,2} MPC pair, working in tandem with MPC.Snap to provide unmatched security without a dedicated hardware requirement. The mobile SDK opens up a way for existing wallets to inherit the security of MPC.Snap with minimal effort.
&nbsp;
<h3 id="sr25519tssjsed25519tssjs">sr25519-tss-js &amp; ed25519-tss-js</h3>
This component is a powerful JavaScript library for two-party SR25519 MPC signing using FROST protocol, based on the proposed @noble/curves/sr25519 package by Paul Miller. The sr25519-tss-js library is not only crucial for our project but is also designed for reuse in other TSS {2,2} applications, making it a versatile tool for developers across the Polkadot ecosystem. Until the @noble/curves/sr25519 package by Paul Miller gets audited, we will use the existing @noble/curves/ed25519 to create the ed25519-tss-js package. So initially the MPC.Snap will be based on ed25519, while the sr25519 support will be added down the line before the public release.
&nbsp;
<h3 id="snapreadinessacceleratorasaservice">Snap-readiness accelerator as a service</h3>
Snaps are not widely adopted by the Polkadot ecosystem projects, and most people are under the impression that snaps can be only used as wallets (but they can also be used for different use cases like mpc, accessibility, zk proofs, meta txs, analytics/visualization, automation actions, scheduling, etc.). We will have a weekly public working hour call (cohort) where projects from the whole Polkadot ecosystem can join and request to make their projects snap-compatible. If we don&rsquo;t have any pending requests in a specific week, we will raise PRs ourselves to add snap compatibility to the remaining projects from the ecosystem.
&nbsp;
<h1 id="technicalflow">Technical Flow</h1>
<img src="https://i.ibb.co/nMpbHCK/MPC-Snap-Workflow-Diagram.png" alt="" width="1080" height="761" />
&nbsp;
<h1 id="team">Team</h1>
<h3 id="experience">Experience:</h3>
Edgetributor SubDAO is a collective of currently active solo contributors from the <a href="https://edgeware.io/">Edgeware DAO</a>, one of the oldest substrate projects from the Polkadot ecosystem. The Edgetributors SubDAO members bring 3-4 years of Polkadot/Substrate ecosystem experience and expertise from different domains.
Our recent contribution to the ecosystem includes the Universal Substrate Faucet, widely adopted by numerous Polkadot projects and actively maintained by the Edgetributors SubDAO. Additionally, we have voluntarily curated <a href="../referenda/1165">the proposal to integrate the Polkadot ecosystem&rsquo;s sr25519 curve into Paul Miller&rsquo;s @noble/curves package</a>, enhancing the scope for adoption by making the cryptographic capabilities more accessible in native JS/TS to developers.
Our expertise is further validated by our success in winning <a href="https://devfolio.co/projects/edgesnap-3cc5">the Consensys track at the ETHforAll 2023 hackathon</a> with our EdgeSnap project.
&nbsp;
Ethos of Edgetributors SubDAO:
<ul>
<li>Committed to developing generic/innovative substrate toolings and products.</li>
<li>Upholding impartiality, with no preferential treatment towards Edgeware DAO.</li>
</ul>
<h3 id="members">Members:</h3>
<ul>
<li><a href="https://www.linkedin.com/in/shankar-warang/">Shankar Warang</a></li>
<li><a href="https://www.linkedin.com/in/c-gagan-babu-0903b01b6/">C. Gagan Babu</a></li>
<li><a href="https://www.linkedin.com/in/pranavchandrakantpawar/">Pranav C Pawar</a></li>
<li><a href="https://www.linkedin.com/in/raj-raorane-45b2b4166/">Raj Raorane</a></li>
<li><a href="https://www.linkedin.com/in/rama-jha/">Rama Vats</a></li>
<li><a href="https://www.linkedin.com/in/zerom/">Ashutosh Sahu</a> </li>
</ul>
<h1 id="budgetandtimeline">Budget and Timeline</h1>
We plan to deliver the MPC Dot Snap within 6 months, ensuring full development and deployment. Post-launch, we will provide maintenance and support for an additional 6 months, all within the current budget framework.
The distribution as per the components:
<ul>
<li>MPC.Snap
<ul>
<li>Estimated duration: 2 Months</li>
<li>Costs: 60000 USD</li>
<li>Deliverables: MPC engine (initiator), In-snap UI, Ecosystem-wide support with network/metadata/types handlers</li>
</ul>
</li>
<li>DApp
<ul>
<li>Estimated duration: 1 Month</li>
<li>Costs: 28000 USD</li>
<li>Deliverables: Pairing engine with database handler, Recovery mode, Snap store</li>
</ul>
</li>
<li>Mobile Apps and SDK
<ul>
<li>Estimated duration: 2 Months</li>
<li>Costs: 54000 USD</li>
<li>Deliverables: Android and iOS apps, Mobile SDK, MPC engine (listener), extrinsic visualizer</li>
</ul>
</li>
<li>sr25519-tss-js and ed25519-tss-js packages
<ul>
<li>Estimated duration: 1 Month</li>
<li>Costs: 26000 USD</li>
<li>Deliverables: Split KeyGen/Signing/KeySharing/zkProofs, two-round FROST implementation</li>
</ul>
</li>
<li>Maintenance and snap-readiness accelerator as a service
<ul>
<li>Estimated duration: 6 Months (after development)</li>
<li>Costs: 24000 USD</li>
<li>Deliverables: Regular maintenance of all 4 components, weekly snap-readiness cohorts, commitment towards JAM &amp; Parachain-Service support</li>
</ul>
</li>
</ul>
To successfully execute this project, we request a total budget of 192K USD.
This budget will cover the entire development phase, as well as the 6-month maintenance period, ensuring the project's smooth operation and integration into the Polkadot ecosystem on different levels.
Total: 192000 USDT
Multisig: 14XNJmoUzkvmh9cYoqG4axBRR4BWzWRbnFP79oiZgKu7V9bz 
<h1 id="benefitstocommunity">Benefits to Community</h1>
<ul>
<li>Easily accessible security: Experience top-tier security without the cost barrier&mdash;better protection than hardware wallets, with zero expense. No need to worry about limited availability or steep import fees.</li>
<li>Familiar Metamask experience: For those transitioning into the Polkadot ecosystem, enjoy the familiar feel of Metamask, while also benefiting from seamless, human-readable decoded details for extrinsics directly on the app.</li>
<li>Priority assistance and custom feature implementations: The community gets priority support and tailored feature implementations at no extra cost&mdash;as we have done for the Universal Substrate Faucet our previous project for the Polkadot Ecosystem, whether it's chain-specific landing pages as requested by Integritee Network, permissioned chain support for Polymesh, or pre-filled address URLs, we've got you covered.</li>
<li>Modular reusability: The sr25519-tss-js and ed25519-tss-js packages can be used by any other ecosystem projects looking to implement the MPC(2,2) protocol. And the mobile SDK will allow any existing wallets to add support for MPC.Snap with minimal efforts, making the robust security accessible to their users. </li>
</ul>
<h1 id="calltoaction">Call to action</h1>
We invite the Polkadot community to support this initiative. Your feedback and suggestions are crucial to refining and successfully implementing this project. Please share your thoughts and let us know how we can make this project a valuable resource for everyone.

- **Problem Statement:** Enhancing account security in the Polkadot ecosystem beyond traditional hardware wallets due to increasing vulnerabilities and limited support for pallet functions.
- **Significance:** MPC{dot}Snap offers a comprehensive security suite through Multiparty Computation, providing a more secure and accessible alternative to hardware wallets, attracting new users and enhancing security for existing users.
- **Proposed Solution:** Introducing MPC{dot}Snap, a suite comprising MPC.Snap, DApp, Mobile Apps & SDK, sr25519-tss-js, and ed25519-tss-js packages, along with a snap-readiness accelerator service.
- **Expected Outcomes:** Improved security, enhanced user experience, increased accessibility to robust security solutions, and support for various Polkadot ecosystem projects through snap compatibility.

#2473 Development of MPC{dot}Snap

No Active Proposals