Introduction
Silent Shard Network
Last updated
Silent Shard Network
Last updated
Traditional self-custody methods place the onus of safeguarding keys which can be overwhelming for users, often leading to avoidable errors and security breaches. And, in this constantly evolving landscape of digital assets, the phrase 'ease of use meets security' becomes more than a slogan; it's a necessity.
Even when MPC serves a case of distributed self-custody leveraging user-held devices, the problem of usability arises:
The user still holds one or more key shards. These key shards are meant to be kept safe and the loss of a few keys (< n-t) would mean the loss of funds.
Backup options involve trusting a centralised system in one way or another.
The user still has to verify every transaction, no matter the sensitivity manually.
Silent Network enables Distributed Delegated Custody which enables a keyless experience for the user while leveraging the security standards that accompany MPC.
Under this new paradigm, the delegated custodians work individually to verify the user requests and can sign messages when a threshold number of custodians cooperate.
This approach not only simplifies the user experience a great deal but also maintains a high level of security by distributing trust and responsibility, thereby reducing the risks associated with centralized control or individual mismanagement.
Since the nodes are programmatic, based on some preset 'non-mutable' conditions set by the user, this paradigm can also enable the automation of transactions, without compromising security at any stage.
Wallets have secret keys, which are used to sign messages. Silent Shard Network generates this secret for the authenticated users by having the network of nodes act in concert - in such a way that neither party can learn the secret key.
The newly generated Key can be assigned with programmatic permissions to limit the functionality of the key as the user desires: A true web2 style granular control, without the expensive, gas-intensive operations. The permissions are set during a new DKG and are validated by each node upon each user's request.
In order to create a signature, complex cryptographic computation needs to be done. We might assume that in order to do that computation, we would need the shards to come together so that both parties can learn the secret, but that isn't the case. Instead, by being careful about what information is sent and received by each party, it becomes possible to compute the signature for an arbitrary message without needing to learn any new information - the nodes just cooperate to run the algorithm.
We've put together some helpful guides for you to get set up with our product quickly and easily.
