HUSH PROTOCOL
There is a problem that has lingered in web3 since its beginning which is how can you store you wallet keys on a chain securely in such a manner that only you can access it?
What Hush Protocol brings to you is a mechanism to securely store secrets on-chain which could be your private keys or anything else, which can only be accessed by you.
How does it Work?
So we achieve all of this by utilizing Internet Computer Protocol's(ICP) VETKD (Verifiably Encrypted Threshold Key Derivation) which is a new cryptographic primitive for encrypting Data which is developed by ICP, with the help of Vet Keys and ICP's threshold signatures which are natively calculated between ICP nodes, we are utilizing IBE (identity-Based Encryption) for verifying the user's Identity and then giving access to his data. IBE typically involves a trusted environment that acts as a verifier of your identity and also stores your private and public keys on your behalf, we replicated this in ICP by using ICP's native MPC (Multi-Party Computation).
So when you register your private keys with us the protocol will ask you to provide multiple authentication methods (such as GitHub, Email, and Govt. IDs), and unless you provide all those authentication methods at the time of accessing the key and prove that you are the one who wants to take a look at your keys, ICP canister won't share the data with you.
You can refer to this White Paper to know exactly the tech behind Hush Protocol.
UseCases
- Storing wallet private keys and seed phrases on-Chain.
- Storing private data on-Chain.
- End to End encrypted smart contracts
HUSH PROTOCOL
There is a problem that has lingered in web3 since its beginning which is how can you store you wallet keys on a chain securely in such a manner that only you can access it?
What Hush Protocol brings to you is a mechanism to securely store secrets on-chain which could be your private keys or anything else, which can only be accessed by you.
How does it Work?
So we achieve all of this by utilizing Internet Computer Protocol's(ICP) VETKD (Verifiably Encrypted Threshold Key Derivation) which is a new cryptographic primitive for encrypting Data which is developed by ICP, with the help of Vet Keys and ICP's threshold signatures which are natively calculated between ICP nodes, we are utilizing IBE (identity-Based Encryption) for verifying the user's Identity and then giving access to his data. IBE typically involves a trusted environment that acts as a verifier of your identity and also stores your private and public keys on your behalf, we replicated this in ICP by using ICP's native MPC (Multi-Party Computation).
So when you register your private keys with us the protocol will ask you to provide multiple authentication methods (such as GitHub, Email, and Govt. IDs), and unless you provide all those authentication methods at the time of accessing the key and prove that you are the one who wants to take a look at your keys, ICP canister won't share the data with you.
You can refer to this White Paper to know exactly the tech behind Hush Protocol.
UseCases