Methods, devices, and systems for creating and managing Web3 app credentials
Systems, devices, and methods for creating and managing web3 app credentials, including: determining a private key and a public key; encrypting the determined private key into a plurality of separate keys; transmitting the first key to a third party provider; transmitting the second key to a cloud storage device; encrypting the first key and the second key; decrypting the second key; transmitting the decrypted second key; transmitting a transaction sign request to a secure third-party trusted execution environment; performing a user identity verification; transmitting a request to the third party provider for the first key; performing reconstruction of the original private key based on the first key and the second key; and signing a digital wallet transaction based on the reconstructed original private key received from the trusted execution environment.
1. A system comprising:
a cloud storage device;
a secure third-party trusted execution environment;
a third-party provider; and
a user computing device having a processor and addressable memory, the user computing device in communication with the cloud storage device having a processor and addressable memory, the secure third-party trusted execution environment having a processor and addressable memory, and the third-party provider;
wherein the user computing device is configured to:
determine, via a Secure Web Sandbox being executed on the user computing device, a private key and a public key based on receiving a request from a user to create a digital wallet;
encrypt the determined private key into a plurality of separate keys, wherein the plurality of separate keys are split via encoding the private key into a first key and a second key;
transmit the first key to a third party provider; transmit the
second key to a cloud storage device; and
wherein the cloud storage device is configured to:
encrypt the second key via cloud encryption-at-rest;
store the encrypted second key for future retrieval and decryption; wherein the third party provider is a key management system configured to:
encrypt the first key via an individualized hardware security module encryption key; and
store the encrypted first key for future retrieval and decryption; wherein the cloud storage device is further configured to:
perform a multi-factor authentication verification based on a received request from the user computing device for the second key;
decrypt the second key based on a successful authentication, wherein the authentication is determined to be successful by a multi-factor authentication service;
transmit the decrypted second key to the user computing device;
wherein the user computing device is further configured to:
transmit a transaction sign request to the trusted execution environment wherein the request comprises transaction details and the decrypted second key;
wherein the trusted execution environment is further configured to:
perform a user identity verification;
transmit, if the user identify verification is successful, a request to the third-party provider for the first key via a secure access;
perform reconstruction of the original private key based on the first key received from the third-party provider and the second key received from the cloud storage device;
sign a digital wallet transaction based on the reconstructed original private key; and
return the signed digital wallet transaction to the user computing device; and
wherein the user computing device is further configured to: broadcast the signed transaction details, via a decentralized
application, to a blockchain.
2. The system of claim 1 further comprising an authentication system configured to provide an additional step of authenticating the user as part of the key management system.
3. The system of claim 2 , wherein the third-party provider is further configured to determine a user identity confirmation via the authentication system.
4. The system of claim 1 , wherein the multi-factor authentication service is controlled by at least one of: an authentication provider of an authentication system and a third-party entity.
5. The system of claim 1 , wherein each key of the plurality of separate keys is stored in a different location.
6. The system of claim 1 , wherein the user identity verification is further performed using an access token associated with the user, wherein the access token is a time-limited user access token.
7. The system of claim 1 , wherein the private key is a password.
8. The system of claim 1 , wherein the plurality of separate keys are split via encoding the private key into a first key, a second key, and a third key.
9. The system of claim 8 , wherein the third key is stored on at least one of: a local device and a different third-party provider.
10. The system of claim 1 , wherein biometric data is used as further authentication requirements to retrieve the first key or the second key.
11. A method comprising:
determining, by a user computing device having a processor and addressable memory, a private key and a public key based on receiving a request from a user to create a digital wallet;
encrypting, by the user computing device, the determined private key into a plurality of separate keys, wherein the plurality of separate keys are split via encoding the private key into a first key and a second key;
transmitting, by the user computing device, the first key to a third-party provider having a processor and addressable memory;
transmitting, by the user computing device, the second key to a cloud storage device having a processor and addressable memory;
encrypting, by the third-party provider executing a key management system, the first key;
storing, by the third-party provider executing the key management system, the encrypted first key for future retrieval and decryption;
encrypting, by the cloud storage device, the second key via cloud encryption-at-rest;
storing, by the cloud storage device, the encrypted second key for future retrieval and decryption;
performing, by the cloud storage device, a multi-factor authentication verification based on a received request from the user computing device for the second key;
decrypting, by the cloud storage device, the second key based on a successful authentication;
transmitting, by the cloud storage device, the decrypted second key to the user computing device;
transmitting, by the user computing device, a transaction sign request to a secure third-party trusted execution environment having a processor and addressable memory, wherein the request comprises transaction details and the decrypted second key;
performing, by the trusted execution environment, a user identity verification;
transmitting, by the trusted execution environment, if the user identify verification is successful, a request to the third-party provider for the first key;
performing, by the trusted execution environment, reconstruction of the original private key based on the first key received from the third-party provider and the second key received from the cloud storage device;
signing, by the trusted execution environment, a digital wallet transaction based on the reconstructed original private key;
returning, by the trusted execution environment, the signed digital wallet transaction to the user computing device; and
broadcasting, by the user computing device, the signed transaction details to a blockchain.
12. The method of claim 11 , wherein the user computing device is in communication with the cloud storage device, the secure third-party trusted execution environment, and the third-party provider.
13. The method of claim 11 , wherein transmitting, if the user identify verification is successful, a request to the third-party provider for the first key via a secure access.
14. The method of claim 11 , wherein determining a private key and a public key is via a Secure Web Sandbox being executed on the user computing device.
15. The method of claim 11 , wherein encrypting the first key is via an individualized hardware security module encryption key.
16. The method of claim 11 , wherein a successful authentication is determined to be successful by a multi-factor authentication service.
17. The method of claim 11 , wherein broadcasting the signed transaction details is via a decentralized application.