Here’s to doing away with all the reasons why enterprises and protocols don’t adopt secure ways of signatures through a unique fusion of multi-party computation (MPC) based cryptography and Signal Processing: Silent Shard.

<aside> 💡 Silent Shard is an MPC-based TSS complemented by Silent Auth for much usable, secure, and truly decentralized support for digital wallets, exchanges, and Sign Ins for Web3/Web2

</aside>

What is a short one-sentence description of your Snap idea?

Enabling any Web Service to safely use threshold signatures through MetaMask Snaps - The Silent Snap Shard

What category do you think your Snap idea falls under? You can select more than one.

Accounts and Key Management

What specific user problem is your Snap trying to solve?

Our Snap Shard aims to remove single points of failures of dependencies on private keys and seed phrases i.e. in current designs private keys are stored in a single location, the local browser storage. Users have been losing access to wallets’ accounts and associated services due to phishing scams and private key theft through this attack vector for years. This has resulted in a loss of approximately USD $14 billion in 2021 alone, a blot in the face of self-sovereign non-custodial wallets which is one of the core tenets of crypto. The Silent Snap Shard aims to remove this entirely with our AuthSec module.

How will your Snap work from a user's perspective? This is your chance to describe your Snap's user journey and provide any links to designs and related resources.

Welcome to Snap based Multi-Party Distributed Authentication (MPDAuth): Your Silent friend, in our Silent Shard: Using Snap, allows us to prove how Multi-Party Computation-based signature schemes can be built at the core of wallets like MetaMask. Users will be able to get access to any WebApps using MetaMask as one shard node wherein Snap provides a way to extend MetaMask’s functionality- provide DAapps with JSON-RPC API methods for MPC. Essentially, SilentShard_Snap.js comprises of the core threshold signature functions and WebApps would be provided with functionality to make necessary calls and handling UI elements.

Do you foresee any technical challenges in the creation of your Snap? If so, please describe them here.

We understand the sandboxing-based design of the Snap might need further contextualization of the exact functions and libraries developed by Silence Laboratories. But we will figure them out with close communication with the Snap Team (which we have been doing).

Who will be working on creating your Snap? Please provide names of team members, % time commitment to the project, and external links to GitHub/LinkedIn profiles. If the personnel and structure of your team is likely to change, that's fine, we're just looking for an indication at this stage.

The core applied cryptography and engineering team of Silence Laboratories would be working on this project.

1. Design and Concept:
   1. Jay Prakash [https://www.linkedin.com/in/jayprakashiitbhu/], [30% of the time]
   2. Andrei Bytes [30% of the time]
   3. Siddhant Shrivastava [ https://sidcode.github.io/ ], [30% of the time]