Systems and methods for facilitating security authentication when blockchain operations using
By introducing some private key management services and encrypted communications in traditional blockchain systems, the security and availability of private key management in a multi-device environment is solved, and higher blockchain operation security and user experience are achieved.
Patent Information
- Application Number
- CN202380036688.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-26
- Filing Date
- 2023-02-24
- Publication Date
- 2024-12-06
AI Technical Summary
There is a risk of loss and leakage in traditional blockchain systems. Especially when interacting with third-party decentralized applications, users need to manage private keys themselves, which increases security vulnerabilities and management burdens, and cannot effectively prevent private keys. Loss or leakage in multi-device environments.
Adopt partial private key management service, users store part of private key on user equipment, another part of private key on remote server, and secure authentication and digital signature through encrypted communication and decentralized application browsers to ensure the security of private keys. and availability, allowing users to access and recover private keys in a multi-device environment.
Reduces the risk of private key loss and leakage, improves the security and user experience of blockchain operations, reduces management burden, and ensures the security of assets. Even if some private keys are lost or leaked, asset security can be ensured through recovery mechanisms. .
Smart Images

Figure CN119096521A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of priority to U.S. Patent Application No. 17 / 729,586, filed on April 26, 2022, and U.S. Patent Application No. 17 / 729,563, filed on April 26, 2022. The contents of the foregoing applications are incorporated herein by reference in their entirety.
[0003] background
[0004] In recent years, the use of blockchain and blockchain technology has grown exponentially. A blockchain includes a list of records called "blocks" that are "linked" together using cryptography. Each block can include data computed using a one-way function (e.g., a function that is virtually impossible to reverse or compute in reverse) of the previous block, a timestamp (e.g., indicating creation and / or modification time), and additional data (e.g., transaction or operation data related to the operation of the blockchain).
[0005] While the hype about blockchain and blockchain technology has focused on its use for cryptocurrencies and smart contracts, blockchain and blockchain technology may be applicable to many technical approaches. A common theme among technical approaches is that blockchain and blockchain technology are decentralized in a way that the promotion, management, and / or verification of blockchain-based operations are governed or managed not by any one institution but by a community of users. Thus, a blockchain can be maintained distributed (e.g., over a network of computers that communicate and coordinate their actions by passing messages to each other) and in many cases public by recording a digital ledger of a series of blocks that form a chain. Notably, because each block is dependent on the previous block, it may not be possible to edit an existing block in the chain without affecting subsequent blocks.
[0006] Furthermore, updates to the blockchain (e.g., adding new blocks) can include an incentive system that rewards community members for generating updates while also ensuring community consensus. By doing so, the proliferation of the blockchain can proceed indefinitely.
[0007] Overview
[0008] This article describes novel uses and / or improved methods and systems for blockchains and blockchain technology. As an example, this article describes methods and systems for facilitating blockchain operations in decentralized applications by providing enhanced security when using cryptography-based digital ledgers for blockchain operations. For example, because digital ledgers are immutable (or virtually immutable), blockchain operations, digital ledgers, and / or cryptocurrencies based on digital ledger technology provide a perfect mechanism for conducting transactions in decentralized applications because the use of blockchain operations can be performed without a central administrator.
[0009] In traditional systems, the security of digital ledgers and / or cryptocurrencies focuses on the use of cryptography-based storage applications (e.g., digital wallets). Each digital wallet is bound to a unique private key associated with the digital wallet. The loss of a private key may prevent a user from accessing any assets in the digital wallet. In addition, if the private key is leaked, unauthorized users can obtain digital assets with little recourse for the owner. To address this issue, traditional systems rely on users to manage their own private keys. While this adds security benefits (i.e., no third party can access the private key), it places the management burden on the user and exposes the user to the risk of (i) losing access to their assets if the private key is lost, or (ii) losing funds if the private key is compromised. These risks are exacerbated if the user wishes to use their digital wallet (and / or private key) to interact with third-party decentralized applications, as each interaction may be at risk of a security breach.
[0010] A potential alternative to this problem is to allow a trusted third party to manage the private key when interacting with other third-party decentralized applications to ensure that the private key is not lost and / or leaked. However, this alternative requires exposing the private key to a trusted third party and does not completely eliminate the risk of private keys being leaked during interactions with third-party decentralized applications.
[0011] In order to reduce the management burden on users while maintaining security during interactions with third-party decentralized applications, the system improves on traditional systems by using a partial private key management service. That is, the user will store a first share of the private key (e.g., stored in a first cryptography-based storage application on their user device), and the system will store a second share of the private key in a custodial digital wallet (e.g., a second cryptography-based storage application on a remote server). Only by using two partial private keys can blockchain operations occur. In this way, even if one partial private key is leaked, the user's assets are safe.
[0012] However, this presents additional technical problems, because if the user device (e.g., storing the partial key) is lost or the user wishes to use multiple devices for blockchain operations, the private key management service must have a mechanism for accessing and / or authenticating the user device and / or the first partial private key in the event that the user cannot access their funds. To account for such a scenario, the method and system may further allow the user to receive an encrypted communication for the first user device, wherein the encrypted communication includes instructions that, when executed by the first user device, cause the second partial private key to be stored on the first user device. That is, the private key management service may provide instructions that allow the user to recover a portion of their partial private key, even if the portion is not accessible by the private key management service itself. In addition, the private key management service may provide a decentralized application browser that allows the user to securely conduct blockchain operations with other third-party decentralized applications. This is provided by the system by triggering the authentication and digital signature signing process directly via the decentralized application browser, rather than the user generating a digitally signed communication directly on the user device and then processing the digitally signed communication through other third-party decentralized applications. Thus, methods and systems are described for managing portions of private keys of cryptography-based storage applications used in blockchain operations and / or facilitating secure authentication when conducting blockchain operations using cryptography-based storage applications.
[0013] In some aspects, the system may receive a first user request from a first user device to access a first user account corresponding to a first cryptography-based storage application, wherein the first cryptography-based storage application is used to perform multiple blockchain operations on a computer network based on a combined use of a first public key, a first portion of a private key, and a second portion of a private key, and wherein the second portion of the private key is inaccessible to a platform service that facilitates the first cryptography-based storage application. In response to receiving the first user request, the system may authenticate the first user device at a first remote device as corresponding to the first user account. In response to authenticating the first user device, the system may generate an encrypted communication for the first user device, wherein the encrypted communication includes an instruction that, when executed by the first user device, causes the second portion of the private key to be stored on the first user device. The system may transmit the encrypted communication to the first user device. The system may register the first user device at the platform service as corresponding to the first user account.
[0014] In some aspects, the system may receive a first user request to perform a blockchain operation corresponding to a first public key from a decentralized application browser implemented on a first user device. In response to receiving the first user request, the system may access a first user account corresponding to the first public key via an application programming interface ("API") implemented on a first remote device, wherein a first cryptography-based storage application corresponding to the first user account is accessible by the first remote device. The system may retrieve a first partial private key and a first user address from the first user account. The system may query the first user device to use a second partial private key when performing a blockchain operation, wherein the second partial private key is stored on the first user device. The system may generate a first digital signature based on the first partial private key and the second partial private key. The system may perform a blockchain operation based on the first digital signature and the first user address.
[0015] Through the detailed description of the present invention and the accompanying drawings, various other aspects, features and advantages of the present invention will be apparent. It should also be understood that the general description above and the detailed description below are examples and do not limit the scope of the present invention. As used in this specification and claims, unless the context clearly specifies otherwise, the singular forms "a", "an" and "the" include plural indicators. In addition, as used in this specification and claims, unless the context clearly specifies otherwise, the term "or" means "and / or". In addition, as used in this specification, unless the context clearly specifies otherwise, "a portion" refers to part or all (i.e., the entire portion) of a given item (e.g., data). BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Figure 1 An illustrative user interface for a decentralized application browser is shown according to one or more embodiments.
[0018] Figure 2 A schematic diagram for performing blockchain operations according to one or more embodiments is shown.
[0019] Figure 3 A schematic diagram of a decentralized application according to one or more embodiments is shown.
[0020] Figure 4 A schematic diagram for operating in a decentralized application using blockchain operations according to one or more embodiments is shown.
[0021] Figure 5 A schematic diagram of a blockchain indexer is shown in accordance with one or more embodiments.
[0022] Figure 6A flow diagram illustrating steps involved in managing partial private keys of a cryptography-based storage application used in blockchain operations in accordance with one or more embodiments.
[0023] Figure 7 A flow diagram illustrating steps involved in facilitating secure authentication when conducting blockchain operations using a cryptography-based storage application in accordance with one or more embodiments.
[0024] Detailed description of the drawings
[0025] In the following description, for the purpose of explanation, many specific details are set forth to provide a thorough understanding of the embodiments of the present invention. However, it will be appreciated by those skilled in the art that the embodiments of the present invention can be practiced without these specific details or with equivalent arrangements. In other cases, well-known structures and devices are shown in block diagram form to avoid unnecessarily obscuring the embodiments of the present invention.
[0026] Figure 1 Schematic user interfaces for decentralized application browsers according to one or more embodiments are shown. For example, user interface 100, user interface 150, and user interface 170 may represent decentralized browser applications for managing portions of private keys of cryptography-based storage applications used in blockchain operations and / or facilitating secure authentication when performing blockchain operations using cryptography-based storage applications. For example, Figure 1 A decentralized application browser implemented on a first user device is shown, configured to receive a user request for performing a plurality of blockchain operations on a computer network and access a second portion of a private key stored on the first user device. To provide security when performing blockchain operations, the system may also access an application programming interface ("API") implemented on a first remote device, the application programming interface being configured to receive a first user request to perform a blockchain operation corresponding to a first public key, and access a first user account corresponding to the first public key in response to receiving the first user request, wherein a first cryptography-based storage application corresponding to the first user account is accessible by the first remote device through a platform application, and wherein the first cryptography-based storage application is used to perform a plurality of blockchain operations.
[0027] For example, because the inherent characteristics of blockchain technology require that a digital wallet be linked to a specific blockchain address, assets in a custodial digital wallet (i.e., a digital wallet maintained at a remote server) can only be accessed via the remote server. Therefore, the system must provide a mechanism for receiving user requests and accessing user accounts. That is, the system must determine what account, device, and / or portion of a private key to request to facilitate a blockchain operation. In doing so, the system may retrieve a first portion of a private key and a first user address from a first user account, query the first user device to use a second portion of a private key when performing a blockchain operation, generate a first digital signature based on the first portion of the private key and the second portion of the private key, and perform a blockchain operation based on the first digital signature and the first user address.
[0028] For example, the system may allow a user accessing a user interface (e.g., user interface 100, user interface 150, and user interface 170) to use a decentralized application browser to perform operations such as Figure 1 Multiple blockchain operations are shown, such as monitoring the value of digital assets, transferring digital assets, and / or receiving referrals, rewards, and other content related to decentralized applications.
[0029] In addition, the decentralized application browser provides additional functionality to facilitate blockchain operations by communicating with a blockchain platform service, which is configured to access a first cryptography-based storage application and access a blockchain index service to perform blockchain operations. For example, a system (e.g., a private key management service) may provide a decentralized application browser (e.g., as shown in user interface 100, user interface 150, and user interface 170) that allows a user to securely perform blockchain operations with other third-party decentralized applications (which can be accessed via a decentralized application browser). The system does this by authenticating the user device when the user device accesses the decentralized application browser (or a user account on the decentralized application browser). The system then allows the user to perform functions within the decentralized application browser ecosystem, including performing blockchain operations. When performing blockchain operations, the system initiates a digital signing process by transmitting encrypted communications between the API layer and the user device (e.g., via a decentralized application browser). The system receives a response to its query to the user device to facilitate the digital signing process. During this process, no portion of the private key is exposed to either the counterparty device (e.g., the user device or a remote server hosting the private key management service) or to a third-party decentralized application with which the user wishes to interact. Thus, the system facilitates the digital signature signing process directly through the decentralized application browser, rather than the user generating a digitally signed communication directly on the user device and then processing the digitally signed communication through other third-party decentralized applications. For example, the platform service may include a cloud computing service that allows customers to provision, instantiate, run, and manage modular bundles that include a computing platform and one or more applications without the complexity of building and maintaining the infrastructure typically associated with developing and launching applications.
[0030] For example, the system may use a multi-party computation ("MPC") system. MPC involves the use of multiple parties, each of which holds corresponding private data that can be used to evaluate computations without ever exposing any of the private data held by each party. For example, each of the multiple parties may have private data (e.g., d1, d2, ..., d N ). The parties can use their respective private data together to compute the value of a public function: (e.g., F(d1, d2, …, d N )). When private data is used to compute a value based on a function, the private data remains private during the process.
[0031] The use of MPC-based keys reduces the risks involved in private key loss and / or private key access by unauthorized parties. For example, traditional key sharing systems rely on public-private key configurations, where the security of the system is associated with the private key remaining private. In some cases, these keys are stored in various cryptography-based digital repositories (or digital wallets). These digital wallets can have a variety of configurations, typically classified according to whether the private key is held online or offline. For example, hot storage wallets have private keys held online. Cold storage wallets have private keys held offline, and hardware wallets have private keys held offline and on physical devices (e.g., thumb drives). While holding private keys offline and / or binding private keys to physical devices is beneficial from a security perspective, this creates practical problems when attempting to operate using digital wallets. For example, in order to operate, the user must be able to access the private key from its offline location and / or physical device. This is particularly burdensome for MPC-based key operations because it requires each user (e.g., corresponding to the corresponding private key) to be available at a given time.
[0032] In addition, the use of private keys stored at offline locations and / or physical devices increases the risk that the offline location becomes inaccessible and / or the physical device is lost. In this case, the digital wallet and any digital assets therein may also be lost. This creates a key flaw in MPC-based key operations because the loss of any one key may result in the loss of digital assets for all parties. The methods and systems described herein overcome this problem by using threshold signature requirements, separate approval and signing policies, independent key recovery mechanisms, and group / group key creation. More specifically, the methods and systems described herein mitigate the flaws in MPC-based key operations by creating MPC-based key operations in which MPC relies on partial private keys. In this case, one partial private key is kept online (e.g., in a hot wallet) while other partial private keys can be kept offline. In addition, due to the use of partial private keys, the exposure of online partial private keys does not itself create a security risk (e.g., because multiple partial private keys are required to perform blockchain operations, including offline partial private keys), and the loss of offline partial private keys (e.g., stored on user devices) does not create a risk of digital asset loss (e.g., because online partial private keys can be used to recover offline partial private keys).
[0033] MPC-based key operations maintain flexibility in the algorithms used. For example, the system can use online MPC algorithms, such as the Gennaro and Goldfeder MPC algorithm and the MPC algorithm of Lindell et al. Online MPC algorithms have two limitations that constrain their use in traditional systems. First, they require users to wait for blockchain operations to go through up to eight to twelve rounds of signatures, which can create latency issues. Second, they require the use of online storage for private keys. Since partial private keys are used (e.g., including online and offline pairs), the system can use online MPC algorithms. In addition, assuming that the online partial private keys meet the online requirements of the online MPC algorithm, the system can use the online MPC algorithm while maintaining the offline partial private keys (e.g., increasing overall security).
[0034] Additionally, the MPC-based key operations used by the system may include offline and / or online hybrid MPC algorithms. For example, the system may use an MPC algorithm that includes dynamic key refreshes (e.g., private key shares may be dynamically updated / modified at given intervals) and / or dynamic approval and / or signing policies. Online partial private keys enable these dynamic policies. Thus, the system introduces the enhanced security of a dynamic system while still maintaining the security of an offline system (e.g., by using offline partial private keys).
[0035] Finally, MPC-based key operations can use a threshold key signing strategy where only a threshold number of users (e.g., corresponding to partial private keys of the users) are required. When the system determines that the threshold is met, the system can allow subsequent users (e.g., online users) to complete and execute the blockchain operation. Thus, the system allows the use of MPC-based key operations without requiring all parties to be online and / or available at the same time.
[0036] Figure 2 A schematic diagram for performing blockchain operations according to one or more embodiments is shown. For example, in some embodiments, the diagram presents various components that can be used to manage portions of private keys of a cryptography-based storage application used in blockchain operations and / or facilitate secure authentication when performing blockchain operations using a cryptography-based storage application.
[0037] Figure 2A user device 202 is included. The user device 202 may include a user interface. As referred to herein, a "user interface" may include mechanisms for human-computer interaction and communication in a device, and may include a display screen, a keyboard, a mouse, and a desktop appearance. For example, a user interface may include a way for a user to interact with an application or website in order to manage a portion of a private key of a cryptography-based storage application used in a blockchain operation and / or facilitate secure authentication when using a cryptography-based storage application for blockchain operations, and the user interface may display content related to managing a portion of a private key of a cryptography-based storage application used in a blockchain operation and / or facilitating secure authentication when using a cryptography-based storage application for blockchain operations. As referred to herein, "content" should be understood to mean an electronically consumable user asset, a representation of a good or service (including an unforgeable token), Internet content (e.g., streaming content, downloadable content, webcasting, etc.), video data, audio data, image data, and / or text data, etc.
[0038] like Figure 2 As shown, system 200 may include multiple user devices (e.g., user device 202, user device 208, and / or user device 210). For example, system 200 may include a distributed state machine, wherein Figure 2 Each component in acts as a client of system 200. For example, system 200 (and other systems described herein) may include a large data structure that not only holds all accounts and balances but also holds a state machine that can change between blocks according to a predefined set of rules and can execute arbitrary machine code. The specific rules for changing state between blocks can be maintained by the system's virtual machine (e.g., a computer file implemented on and / or accessible by a user device that behaves like an actual computer).
[0039] It should be noted that although Figure 2 200 are shown as smartphones, personal computers, and servers, but the user devices may be any type of computing device, including, but not limited to, laptop computers, tablet computers, handheld computers, and / or other computing devices (e.g., servers), including "smart", wireless, wearable, and / or mobile devices. It should be noted that the embodiments describing the system 200 for performing blockchain operations may be equally applicable to and correspond to individual user devices (e.g., user device 202, user device 208, and / or user device 210) that perform blockchain operations. That is, the system 200 may correspond to user devices (e.g., user device 202, user device 208, and / or user device 210) uniformly or individually.
[0040] Each of the user devices can be used by the system to perform blockchain operations and / or help manage partial private keys of cryptography-based storage applications used in blockchain operations and / or facilitate secure authentication when using cryptography-based storage applications to perform blockchain operations. As mentioned herein, "blockchain operations" may include any operations including and / or involving blockchain and blockchain technology. For example, blockchain operations may include conducting transactions, querying distributed ledgers, generating additional blocks for blockchains, transmitting unforgeable tokens related to communications, performing encryption / decryption, exchanging public / private keys, and / or other operations involving blockchain and blockchain technology. In some embodiments, blockchain operations may include creating, modifying, detecting, and / or executing smart contracts or programs stored on blockchains. For example, a smart contract may include a program stored on a blockchain that is executed (e.g., automatically, without any involvement or time loss of an intermediary) when one or more predetermined conditions are met. In some embodiments, blockchain operations may include creating, modifying, exchanging, and / or reviewing tokens (e.g., blockchains specific to digital assets), including unforgeable tokens. Unforgeable tokens may include tokens associated with goods, services, smart contracts, and / or other content that can be verified by blockchain technology and stored using blockchain technology.
[0041] In some embodiments, blockchain operations may also include actions related to mechanisms that facilitate other blockchain operations (e.g., actions related to metering activities of blockchain operations on a given blockchain network). For example, Ethereum is an open source, global decentralized computing infrastructure for executing smart contracts that uses blockchains to synchronize and store state changes of the system. Ethereum uses a network-specific cryptocurrency called ether to meter and constrain execution resource costs. The metering mechanism is called "gas". When the system executes a smart contract, the system considers each blockchain operation (e.g., calculation, data access, transaction, etc.). Each blockchain operation has a predetermined cost in units of fuel (e.g., as determined based on a set of predefined rules for the system). When a blockchain operation triggers the execution of a smart contract, the blockchain operation may include a certain amount of fuel that sets an upper limit on the fuel that can be consumed when running a smart contract. If the amount of fuel consumed by the calculation exceeds the fuel available in the blockchain operation, the system can terminate the execution of the smart contract. For example, in Ethereum, fuel includes a mechanism for allowing Turing-complete computations while limiting the resources that any smart contract and / or blockchain operation may consume.
[0042] In some embodiments, fuel may be obtained as part of a blockchain operation (e.g., purchase) using a network-specific cryptocurrency (e.g., Ether in the case of Ethereum). The system may require that fuel (or an amount of network-specific cryptocurrency corresponding to the amount of fuel required) be transmitted with the blockchain operation as an earmark for the blockchain operation. In some embodiments, if a certain amount remains unused after the computation is performed, the fuel earmarked for the blockchain operation may be returned to the initiator of the blockchain operation.
[0043] like Figure 2 As shown, one or more user devices may include a digital wallet (e.g., digital wallet 204) for performing blockchain operations. For example, a digital wallet may include a repository that allows users to store, manage, and trade their cryptocurrencies and assets, interact with the blockchain, and / or use one or more applications to perform blockchain operations. A digital wallet may be specific to a given blockchain protocol, or may provide access to multiple blockchain protocols. In some embodiments, the system may use various types of wallets, such as hot wallets and cold wallets. Hot wallets are connected to the internet, while cold wallets are not connected to the internet. Most digital wallet holders hold both hot wallets and cold wallets. Hot wallets are most commonly used to perform blockchain operations, while cold wallets are typically used to manage user accounts and may not be connected to the internet.
[0044] like Figure 2 As shown, one or more user devices may include a private key (e.g., key 212) and / or a digital signature. For example, the system 200 may use a cryptographic system to perform blockchain operations, such as managing a portion of a cryptography-based storage application used in blockchain operations and / or facilitating secure authentication when using a cryptography-based storage application to perform blockchain operations. For example, the system 200 may use public key cryptography, characterized by a pair of digital keys (e.g., which may include a data string). In this case, each pair includes a public key (e.g., which may be public) and a private key (e.g., which may remain private). The system 200 may use an encryption algorithm (e.g., characterized by a one-way function) to generate a key pair. The system 200 may then use the public key of the intended recipient to encrypt a message (or other blockchain operations) so that the encrypted message can be decrypted using only the corresponding private key of the recipient. In some embodiments, the system 200 may combine a message with a private key to create a digital signature on the message. For example, a digital signature may be used to verify the authenticity of a blockchain operation. As an illustration, when performing a blockchain operation, the system 200 may use a digital signature to prove to each node in the system that it is authorized to perform the blockchain operation.
[0045] For example, the system 200 may include a plurality of nodes for a blockchain network. Each node may correspond to a user device (e.g., user device 208). A node of a blockchain network may include an application or other software that records and / or monitors peer connections to other nodes and / or miners of the blockchain network. For example, a miner includes a node in a blockchain network that facilitates blockchain operations by validating blockchain operations on the blockchain, adding new blocks to an existing chain, and / or ensuring that these additions are accurate. A node may continuously record the state of a blockchain and respond to remote process requests for information about the blockchain.
[0046] For example, a user device 208 may request a blockchain operation (e.g., conduct a transaction). The blockchain operation may be authenticated by the user device 208 and / or another node (e.g., a user device in a community network of the system 200). For example, using cryptographic keys, the system 200 may identify users and grant access to their corresponding user accounts (e.g., corresponding digital wallets) within the system 200. Using a private key (e.g., known only to the corresponding user) and a public key (e.g., known to the community network), the system 200 may create a digital signature to authenticate the user.
[0047] After the blockchain operation is authenticated (e.g., using the key 212), the blockchain operation can be authorized. For example, after the blockchain operation is authenticated between users, the system 200 can authorize the blockchain operation before adding the blockchain operation to the blockchain. The system 200 can add the blockchain operation to the blockchain 206. The system 200 can perform this operation based on the consensus of the user devices within the system 200. For example, the system 200 can rely on the majority (or other metric) of the nodes (e.g., user device 202, user device 208, and / or user device 210) in the community network to determine that the blockchain operation is valid. In response to the validation of the block, the node user devices (e.g., user device 202, user device 208, and / or user device 210) in the community network (e.g., miners) can receive rewards (e.g., given cryptocurrency) as an incentive for validating the block.
[0048] To verify the blockchain operation, the system 200 may use one or more verification protocols and / or verification mechanisms. For example, the system 200 may use a proof-of-work mechanism, in which a user device must provide evidence that it has performed computational work to verify the blockchain operation, and thus the mechanism provides a way to achieve consensus in a decentralized manner and prevent fraudulent verification. For example, the proof-of-work mechanism may involve iterations of a hashing algorithm. Successful user devices aggregate and record blockchain operations from a storage pool (e.g., a collection of all valid blockchain operations waiting to be confirmed by the blockchain network) into the next block. Alternatively or in addition, the system 200 may use a proof-of-stake mechanism, in which a user account (e.g., corresponding to a node on the blockchain network) is required to have or "stake" a predetermined amount of tokens so that the system 200 recognizes the user account as a validator in the blockchain network.
[0049] In response to the validation of the block, the block is added to the blockchain 206 and the blockchain operation is completed. For example, to add a blockchain operation to the blockchain 206, the successful node (e.g., a successful miner) encapsulates the blockchain operation in a new block before transmitting the block throughout the system 200.
[0050] Figure 3 A schematic diagram of a decentralized application according to one or more embodiments is shown. For example, in some embodiments, system 300 can manage portions of private keys of cryptography-based storage applications used in blockchain operations and / or facilitate secure authentication when using cryptography-based storage applications for blockchain operations within a decentralized application environment. Decentralized applications can include applications that exist on a blockchain (e.g., blockchain 302) and / or a peer-to-peer network (e.g., network 306). That is, decentralized applications can include applications with a backend that is partially powered by a decentralized peer-to-peer network, such as a decentralized open source blockchain with smart contract functionality.
[0051] For example, network 306 may allow user devices (e.g., user device 304) within network 306 to share files and access. In particular, the peer-to-peer architecture of network 306 allows blockchain operations (e.g., corresponding to blockchain 302) to be performed between user devices in the network without the need for any intermediary or central authority.
[0052] In some embodiments, the user device of system 300 may include one or more cloud components. For example, the cloud component may be implemented as a cloud computing system and may be characterized by one or more component devices. It should also be noted that system 300 is not limited to four devices. For example, users may utilize one or more devices to interact with each other, with one or more servers, or with other components of system 300. It should be further noted that although one or more operations (e.g., blockchain operations) are described herein as being performed by a specific component of system 300 (e.g., user device 304), in some embodiments, those operations may be performed by other components of system 300. As an example, although one or more operations are described herein as being performed by a component of user device 304, in some embodiments, those operations may be performed by one or more cloud components. In some embodiments, the various computers and systems described herein may include one or more computing devices programmed to perform the described functions. Additionally or alternatively, multiple users may interact with system 300 and / or one or more components of system 300. For example, in one embodiment, a first user and a second user may use two different components (e.g., user device 304 and user device 308, respectively) to interact with system 300. Additionally or alternatively, a single user (and / or a user account linked to a single user) may use two different components (e.g., user device 304 and user device 308, respectively) to interact with system 300 and / or one or more components of system 300.
[0053] With respect to the components of system 300, each of these devices can receive content and data via input / output (hereinafter "I / O") paths using I / O circuitry. Each of these devices can also include a processor and / or control circuitry to send and receive commands, requests, and other suitable data using the I / O paths. The control circuitry can include any suitable processing, storage, and / or I / O circuitry. Each of these devices can also include a user input interface and / or a user output interface (e.g., a display) for receiving and displaying data. For example, Figure 3 As shown, user device 308 and user device 310 both include a display on which data (e.g., content related to one or more blockchain operations) is displayed.
[0054] Additionally, the devices in system 300 may run an application (or another suitable program). The application may cause the processor and / or control circuitry to perform operations related to managing portions of private keys of a cryptography-based storage application used in blockchain operations and / or facilitating secure authentication when performing blockchain operations using a cryptography-based storage application within a decentralized application environment.
[0055] Each of these devices may also include an electronic storage device. The electronic storage device may include a non-transitory storage medium that stores information electronically. The electronic storage medium of the electronic storage device may include one or both of the following: (i) a system storage device that is provided integrally with the server or client device (e.g., substantially non-removable), or (ii) a removable storage device that can be removably connected to the server or client device via, for example, a port (e.g., a USB port, a FireWire port, etc.) or a drive (e.g., a disk drive, etc.). The electronic storage device may include one or more optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., tapes, magnetic hard drives, floppy disk drives, etc.), charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drives, etc.), and / or other electronically readable storage media. The electronic storage device may include one or more virtual storage resources (e.g., cloud storage devices, virtual private networks, and / or other virtual storage resources). The electronic storage device may store software algorithms, information determined by a processor, information obtained from a server, information obtained from a client device, or other information that implements the functions described herein.
[0056] Figure 3 Also included is a network 306, which may include communication paths between user devices. The communication path may include the Internet, a mobile phone network, a mobile voice or data network (e.g., a 5G or LTE network), a cable network, a public switched telephone network, or other types of communication networks or combinations of communication networks. The communication path may include one or more communication paths, such as a satellite path, an optical fiber path, a cable path, a path supporting Internet communication (e.g., IPTV), a free space connection (e.g., for broadcast or other wireless signals), or any other suitable wired or wireless communication path or a combination of such paths, individually or together. The computing device may include additional communication paths linking multiple hardware, software, and / or firmware components that operate together. For example, the computing device may be implemented by a cloud that is a computing platform that operates together as a computing device.
[0057] Figure 4A schematic diagram for operating in a decentralized application using blockchain operations according to one or more embodiments is shown. For example, system 400 may include a user device 402. In addition, user device 402 may include an application (e.g., application 404) implemented on user device 402 and / or accessible by user device 402. For example, application 404 may interact with one or more other applications and / or application programming interfaces (APIs) to manage a portion of a cryptography-based storage application used in blockchain operations and / or facilitate secure authentication when using a cryptography-based storage application for blockchain operations. For example, application 404 may include a decentralized application digital wallet and / or wallet service that is capable of signing and sending transactions to transfer tokens and / or perform other blockchain operations, and is capable of interacting with one or more decentralized applications.
[0058] The system 400 also includes an API layer 406. In some embodiments, the API layer 406 can be implemented on the user device 402. Alternatively or in addition, the API layer 406 can reside on one or more cloud components (e.g., server 408). For example, the API layer 406 can reside on the server 408 and include platform services for custodial wallet services, decentralized applications, etc. The API layer 406 (which can be a REST or web service API layer) can provide a decoupled interface to the data and / or functionality of one or more applications.
[0059] The API layer 406 can provide various low-level and / or blockchain-specific operations to manage partial private keys of cryptography-based storage applications used in blockchain operations and / or facilitate secure authentication when using cryptography-based storage applications for blockchain operations. For example, the API layer 406 can provide blockchain operations such as blockchain writes. In addition, the API layer 406 can perform transfer verification before forwarding a blockchain operation (e.g., a transaction) to another service (e.g., an encryption service). The API layer 406 can then record the results. For example, by recording to the blockchain before forwarding, the API layer 406 can maintain internal records and balances without relying on external verification (e.g., based on blockchain update activity, which may take up to ten minutes).
[0060] API layer 406 may also provide information reading. For example, API layer 406 (or a platform service powered by API layer 406) may generate a blockchain operation log and write the results of the reading to an additional ledger (e.g., an internal record and / or indexer service). If this is done, users who access the information through other means can see consistent information, allowing downstream users to ingest the same data points as the user.
[0061] The API layer 406 may also provide a unified API to access balances, transaction histories, and / or other blockchain operational activity records between one or more decentralized applications and custodial user accounts. By doing so, the system maintains the security of sensitive information such as balances and transaction histories. Alternatively, the mechanism for maintaining such security would be to separate API access between decentralized applications and custodial user accounts using special logic. The introduction of special logic reduces the streamlining of the system, which may lead to system errors based on divergence and coordination.
[0062] The API layer 406 can provide a common, language-agnostic way to interact with applications. In some embodiments, the API layer 406 can include a web service API that provides a well-defined contract that describes the service in terms of its operations and the data types used to exchange information. REST APIs typically do not have this contract; instead, they are documented using client libraries for most common languages, including Ruby, Java, PHP, and JavaScript. SOAP web services are traditionally adopted in enterprises for publishing internal services and for exchanging information with partners in business-to-business (B2B) transactions.
[0063] API layer 406 can use various architectural arrangements. For example, system 400 can be based in part on API layer 406, so that there is strong adoption of SOAP and RESTful web services, using resources such as Service Repository and Developer Portal, but with low governance, standardization, and separation of concerns. Alternatively, system 400 can be based entirely on API layer 406, so that separation of concerns between layers such as API layer 406, services, and applications is in place.
[0064] In some embodiments, the system architecture can use a microservice approach. Such a system can use two types of layers: a front-end layer and a back-end layer where microservices reside. In this architecture, the role of the API layer 406 can be to provide integration between the front-end layer and the back-end layer. In such a case, the API layer 406 can use a RESTful API (exposed to the front-end or even the communication between microservices). The API layer 406 can use the Advanced Message Queuing Protocol (AMQP), which is an open standard for delivering business messages between applications or organizations. The API layer 406 can use an open source, high-performance remote procedure call (RPC) framework that can run in a decentralized application environment. In some embodiments, the system architecture can use an open API approach. In this case, the API layer 406 can use a commercial or open source API platform and its modules. The API layer 406 can use a developer portal. The API layer 406 can use strong security constraints of an application web application firewall, which protects decentralized applications and / or the API layer 406 from common web vulnerabilities, robots, and denial of service (DDoS) attacks. The API layer 406 can use RESTful API as a standard for external integration.
[0065] like Figure 4 As shown, system 400 can use API layer 406 to communicate with server 408 and / or facilitate blockchain operations on server 408. For example, server 408 can represent a custodial platform for blockchain operations. The custodial platform can manage private keys stored by a centralized service provider (e.g., server 408). In this case, server 408 can communicate with blockchain 410, a wallet service for blockchain 410, an indexer service for blockchain 410 (e.g., Figure 5 ) and / or other platform services.
[0066] For example, a wallet service may include an application and / or software-based system that securely stores a user's payment information, private keys, and / or passwords, thereby facilitating blockchain operations on websites, nodes, and / or other devices. In some embodiments, the wallet service may also provide additional ledger access (e.g., a second ledger). In addition, as described above, the second ledger may receive updates directly from the API layer 406, rather than relying on data extracted directly from the blockchain 410.
[0067] For example, the system 400 can maintain its records (e.g., real-time records and records used for accounting) in good order, separate from the balances on the blockchain 410. That is, the system 400 can maintain an architecture featuring a second ledger (on which balances are stored and updated) and a log of blockchain operations. While conventional systems may rely on directly referencing the blockchain 410, this reliance leads to additional technical issues because the blockchain is the system's source of truth.
[0068] First, there is a high probability of impedance mismatch between the format of the platform service and the API used to retrieve data from the blockchain (e.g., this may result in bookkeeping imbalances). For example, the system 400 may need to be able to generate bookkeeping entries that reflect changes in balances. However, while changes in balances can be tracked by checking the blockchain 410, this requires additional processing and computing power.
[0069] Second, accounting changes in a blockchain architecture should be irreversible. This is achieved in practice for current blockchain operations by waiting for a variable number of confirmations from a blockchain (e.g., blockchain 410). By waiting for a variable number of confirmations, the likelihood of errors in the blockchain becomes infinitesimally small. However, while blockchain services rely on this approach, this is not an inherent rule of the blockchain itself. That is, blockchains do not have an inherent authentication mechanism that relies on a large number of confirmations. Instead, blockchains rely on an absolute system - blockchain operations are either recorded on a specific node or they are not recorded.
[0070] Thus, forks in a blockchain are always possible. In the event of a fork, the system 400 may not follow the "right" fork for an indeterminate amount of time. If this occurs, and if the system 400 decides to move from one fork to another for the purpose of custody of the digital wallet, the system 400 may have a more direct mechanism to maintain an accurate history of the user's account location if the system 400 stores the user's account location independently of a given blockchain. In addition, in the event of a fork, the system 400 performs some internal remediation of the user's account, which is achieved by the system 400 maintaining an insulation layer from the blockchain for remediating blockchain operations. For example, the system 400 may have a separate storage device protected by a second ledger (e.g., a ledger service) for reading and protected by a transfer service for writing, which reflects the state of the blockchain relevant to the purposes of the system 400.
[0071] In some embodiments, the system may also use one or more application binary interfaces (ABIs). An ABI is an interface between two program modules (usually an operating system and a user program). An ABI may be specific to a blockchain protocol. For example, the Ethereum Virtual Machine (EVM) is a core component of the Ethereum network, and a smart contract may be a piece of code stored on the Ethereum blockchain that is executed on the EVM. Smart contracts written in high-level languages such as Solidity or Vyper may be compiled by the system into EVM executable bytecodes. When a smart contract is deployed, the bytecodes are stored on the blockchain and associated with an address. In order to access functions defined in a high-level language, the system translates the names and parameters into byte representations of the bytecode to work with it. In order to interpret the bytes sent in the response, the system converts back to a tuple of return values defined in a high-level language (e.g., a finite ordered list of elements). Languages compiled for the EVM maintain strict conventions about these conversions, but in order to execute them, the system must maintain precise names and types associated with the operations. The ABI accurately records these names and types in an easily parsable format, translating between human-expected method calls and discoverable and reliable smart contract operations.
[0072] For example, the ABI defines methods and structures for interacting with binary contracts similar to an API (but at a lower level). The ABI instructs the caller of a function to encode the required information (such as function signatures and variable declarations) in a format that the EVM can understand (e.g., ABI encoding) to call the function in bytecode. The ABI encoding can be performed automatically by the system using a compiler or wallet that interacts with the blockchain.
[0073] Figure 5 A schematic diagram of a blockchain indexer according to one or more embodiments is shown. For example, in some embodiments, the system can use the indexer service 500 to manage partial private keys of a cryptography-based storage application used in blockchain operations and / or facilitate secure authentication when using a cryptography-based storage application for blockchain operations. The indexer service 500 can obtain raw data (e.g., data related to the current state and / or instance of the blockchain 502) from a node of the blockchain network (e.g., as described above). The indexer service 500 can then process the data and store the data in a database and / or data structure in an efficient manner to provide fast access to the data. For example, the indexer 504 can publish and / or record a subset of blockchain operations that occur for the blockchain 502. Therefore, for subsequent blockchain operations, the indexer service 500 can reference the index at the indexer 504 (rather than the node of the blockchain 502) to provide various services at the user device 506.
[0074] For example, the indexer 504 may store a predetermined list of blockchain operations to monitor for an index and / or record per index. These may include blockchain operations (e.g., "operation included", "operation removed", "operation completed") associated with a given type of blockchain operation (e.g., "transaction", "external transfer", "internal transfer", "new contract metadata", "ownership change", etc.) and blockchain operations associated with a given protocol, protocol subgroup, and / or other feature (e.g., "ETH", "ERC20", and / or "ERC721"). Additionally and / or alternatively, various blockchain operations and metadata associated with those blockchain operations (e.g., block designations, user accounts, timestamps, etc.) and aggregations of multiple blockchain operations (e.g., total number of blockchain operations, rate of blockchain operations, rate of blockchain updates, etc.) may be monitored and / or recorded.
[0075] The indexer 504 may also provide navigation and search features (e.g., supporting Boolean operations) for the indexed blockchain operations. In some embodiments, the indexer 504 may apply one or more formatting protocols to generate representations of the indexed blockchain operations in a human-readable format. In some embodiments, the indexer 504 may also tag blockchain operations based on whether the blockchain operation originates from a local user account (e.g., a user account corresponding to a custodial account) and / or a locally hosted digital wallet. The indexer service 500 may determine whether a blockchain operation contains relevant information for a user of the indexer service 500 by storing information about whether an address is an internal address of the indexer service 500 or an address used in a digital wallet hosted by a predetermined wallet service.
[0076] Figure 6 A flow chart showing the steps involved in managing a portion of a private key of a cryptography-based storage application used in blockchain operations according to one or more embodiments. For example, a system may use process 600 (e.g., as implemented on one or more system components described above) to allow a user to perform blockchain operations on a third-party decentralized application in a secure manner.
[0077] At step 602, process 600 (e.g., using one or more components described above) may receive a first user request. For example, the system may receive a first user request from a first user device to access a first user account corresponding to a first cryptography-based storage application. For example, a server may store one or more user accounts, including a first user account corresponding to a first cryptography-based storage application, and a platform service (e.g., hosted on the server) may receive a first user request from the first user device to access the first user account. In some embodiments, the platform service is not hosted on the server. In some embodiments, the first cryptography-based storage application may be used to perform multiple blockchain operations on a computer network based on a combined use of a first public key, a first portion of a private key, and a second portion of a private key. In some embodiments, the second portion of a private key may be inaccessible to a platform service that facilitates the first cryptography-based storage application. For example, a server hosting the platform service may store the first portion of a private key, and may not store the second portion of a private key. By doing so, the system may ensure that users retain some autonomy when conducting blockchain operations and that digital assets are secure.
[0078] In some embodiments, the system can generate a first partial key and a second partial key. For example, the system can receive a public key encryption for a first device. The system can then generate a ciphertext for the public key encryption. The system can split the private key encryption for the first device to generate the first partial key and the second partial key. By doing so, the partial private keys remain hidden even if they are used in the digital signature process.
[0079] For example, in some embodiments, the system may input a public encryption to the key for use with any device to be authorized for the first user account: DK_h1, ..., DK_hn, DK_s0. The system may generate the following ciphertext, which is the encrypted user key for each user device in the devices authorized for the first user account: {BK_h}_DKh1, ..., {BK_h}_DKhn, {BK_h}_DKs0. The system may then split each private key using a 2-2 configuration and encrypt them with the corresponding block key. For example, if "t" separate signing keys are requested, the system generates the following ciphertext "t" times: {k0}_BKh, {k1}_BKs. The system may then generate the following ciphertext containing the encrypted Paillier secret key for each user device block: {PSK}_BKh, {PPK}_BKs. During revocation, the system may update the approved device list to exclude the revoked device's attestation key, and may remove the device's cryptographic co-signer key {CK_h}_DKi from the decentralized data storage.
[0080] At step 604, process 600 (e.g., using one or more components described above) can authenticate the first user device. For example, the system can authenticate the first user device as corresponding to the first user account in response to receiving the first user request at the first remote device. For example, the platform service can authenticate the first user device as corresponding to the first user account in response to receiving the first user request.
[0081] At step 606, process 600 (e.g., using one or more of the above components) can generate an encrypted communication for the first user device. For example, in response to authenticating the first user device, the system can generate an encrypted communication for the first user device. For example, the encrypted communication can include instructions that, when executed by the first user device, cause the second portion of the private key to be stored on the first user device. As another example, the platform service can generate an encrypted communication for the first user device in response to authenticating the first user device.
[0082] In some embodiments, the system can generate encrypted communications for the first user device based on the recovery key. For example, in some embodiments, the system can receive a third user request from the second user device to authorize the platform service to transmit encrypted communications to the first user device. The system can query the second user device to obtain a recovery key, where the recovery key corresponds to the first user account. The system can then determine to generate encrypted communications based on the recovery key. For example, in some embodiments, the system can receive requests from other devices that have been associated with a user account and / or a custodial cryptography-based, storage application. Since the device has been authorized, the system can allow these devices to add other devices to the user account.
[0083] In some embodiments, the recovery key may be incompatible with the first public key and / or the first partial private key of multiple blockchain operations. For example, the system may have different rules and access restrictions for each partial private key. That is, regardless of whether each partial private key corresponds to a user account, a public key, and / or a custodial cryptography-based storage application, each partial private key may have different available roles. For example, the system can enable a fast path to device recovery by establishing a client-controlled external backup on another device (e.g., on a cloud storage device). However, while a new device can be registered with the platform service and associated with a user account, a partial private key (e.g., a device key on another device) can be designated as a recovery key. Although the recovery key is still functionally equivalent to the device key, some rules about use are added because the device key is portable and therefore less secure. Therefore, the device key can be used to update the device corresponding to the user account, but the system can prevent the device key from being used for other blockchain operations (e.g., transaction signing). This means that the leakage of the client backup is not enough to access digital assets.
[0084] In some embodiments, the system can generate encrypted communications for the first user device by revoking access rights of a third user device. For example, the system can determine a third user device that currently has access to the first user account. The system can then revoke the third user device's access rights to the first user account. For example, even if there is no recovery key, the platform service can provide a new device key. If the device is lost, the system can put the user account into recovery mode without an existing recovery device. When the user account is in recovery mode, new device registration continues to register the new device (and generate a new recovery key) using the newly generated recovery key. After the new device is registered, the original recovery key and the old device key are revoked. The system can achieve this through platform services without the intervention of key management operations (e.g., without involving the private key of the blockchain wallet corresponding to the custodial cryptography-based storage application).
[0085] In some embodiments, the system may generate encrypted communications for a first user device based on a threshold number of multiple user devices that provide authorization. For example, the system may determine multiple user devices that currently have recovery rights for a first user account. The system may query the multiple user devices to obtain authorization to generate encrypted communications. Then, the system may determine whether a threshold number of user devices among the multiple user devices are provided with authorization to generate encrypted communications. For example, the system may contact a device group that may have recovery rights for a user account. In some embodiments, the system may also determine multiple user devices based on the social graph connectivity of multiple user devices with the first user device. For example, the system may determine whether a threshold number of social media connections approve authorization. Alternatively or in addition, the system may use social graph connectivity to determine other devices corresponding to the user. For example, the system may divide the recovery key into threshold shares and distribute these shares among trusted individuals. In this recovery scenario, the system may receive a request from the user to confirm that the user's device is lost (e.g., out of band). The system may send a message to multiple users indicating that the user is trying to recover the account, and the service prompts the individual to approve and provide a recovery share. After the combination, the recovery key will be rebuilt and the account will proceed normally.
[0086] In some embodiments, the system may generate an encrypted communication for the first user device based on a threshold time difference. For example, the system may determine the first time at which the first user request is received. In addition, the system may determine the current time. Then, the system may determine the difference between the first time and the current time. For example, the system may determine whether the difference satisfies the threshold time difference. For example, in some embodiments, the system may wait for a threshold amount of time before generating a recovery key and / or allowing a new user device to be associated with the first user device. By waiting for the threshold amount of time, the system enhances security and reduces the possibility of unauthorized network attacks. In some embodiments, the system may dynamically adjust the threshold time difference. For example, the system may maintain user profile information about a user account, information about current network conditions, and / or use other features to set the threshold time difference.
[0087] In some embodiments, the system may generate an encrypted communication for the first user device based on whether the number of user devices meets a threshold number of user devices. For example, the system may determine the number of user devices that are currently authorized to access the first user account. In some embodiments, the system may retrieve the threshold number of user devices, and the threshold number of devices may correspond to the maximum number of user devices that can be authorized for a single user account. The system may then determine whether the number of user devices meets the threshold number of user devices.
[0088] At step 608, process 600 (e.g., using one or more components described above) can transmit the encrypted communication. For example, the system can transmit the encrypted communication to the first user device. For example, the platform service can transmit the encrypted communication to the first user device.
[0089] At step 610, process 600 (e.g., using one or more components described above) can register the first user device. For example, the system can register the first user device at the platform service as corresponding to the first user account. For example, the platform service can register the first user device based on the transmitted encrypted communication.
[0090] In some embodiments, the system may perform a blockchain operation. For example, the system may receive a second request from a first user device to perform a blockchain operation corresponding to a first public key. The system may then retrieve a first partial private key and a first user address from the first user account. In some embodiments, the system may query the first user device to use a second partial private key when performing the blockchain operation. In some embodiments, the system may generate a first digital signature based on the first partial private key and the second partial private key. The system may then perform the blockchain operation based on the first digital signature and the first user address.
[0091] The system may use a combination of a public key, a first portion of a key, and a second portion of a key to perform a blockchain operation. For example, the system may use a user account corresponding to an account of a blockchain platform service. In contrast to a non-custodial cryptography-based storage application (which may correspond to a user without a third-party intermediary), the user account may correspond to a third-party intermediary (e.g., a platform service). By having a user account corresponding to a platform service (which is separate and distinct from the non-custodial cryptography-based storage application), the system may provide additional features that would not be possible for conventional blockchain operations. For example, the system may enhance and / or modify blockchain operations before completion in order to prevent fraud, verify user intent, and / or otherwise increase security. Additionally or alternatively, by having a user account corresponding to a platform service (which is separate and distinct from the non-custodial cryptography-based storage application), the system may provide a single user with access to multiple custodial cryptography-based storage applications using a single account of the platform service.
[0092] In some embodiments, the system may cause a private key to be used to sign a data block. For example, an instruction may cause a private key to be used to sign a data block or to verify a signed block within a secure enclave. The system may use a key management service to operate a recovery service. The recovery service may derive an encrypted public key and a user device recovery key, which are encrypted by the user device using public key encryption and have a persistently stored ciphertext. The recovery key may be decrypted within a secure enclave (e.g., a hardware-based key manager that is isolated from the main processor to provide an additional layer of security) and re-encrypted to an encryption key for a new device when recovery mode is triggered.
[0093] Conceived Figure 6 The steps or descriptions of can be used with any other embodiments of the present disclosure. Figure 6 The steps and descriptions described may be performed in alternative orders or in parallel to facilitate the purposes of the present disclosure. For example, each of these steps may be performed in any order or in parallel or simultaneously to reduce latency or increase the speed of the system or method. In addition, it should be noted that any component, device, or equipment discussed above with respect to the figures may be used to perform Figure 6 One or more steps in .
[0094] Figure 7 A flow chart of steps involved in facilitating secure authentication when performing blockchain operations using a cryptography-based storage application according to one or more embodiments is shown. For example, a system may use process 700 (e.g., as implemented on one or more system components described above) in order to perform blockchain operations without the risk of information becoming public or subject to cyber attacks. For example, a cryptography-based digital repository or a cryptography-based storage application may refer to a digital wallet. A digital wallet may include a software-based system that securely (and typically in an encrypted format) stores a user's confidential information, personal information, payment information, and / or passwords for numerous payment methods and websites. By using a digital wallet, a user can easily and securely complete communications, purchases, and / or other blockchain operations without the risk of information becoming public or subject to cyber attacks.
[0095] At step 702, process 700 (e.g., using one or more of the components described above) can receive a first user request. For example, the system can receive the first user request from a decentralized application browser implemented on a first user device. In some embodiments, the first user request can be a request to perform a blockchain operation corresponding to a first public key. For example, the decentralized application browser can receive a user request to perform a plurality of blockchain operations on a computer network. In some embodiments, an application programming interface ("API") implemented on a first remote device can receive (e.g., from a decentralized application browser) the first user request to perform a blockchain operation corresponding to the first public key.
[0096] In some embodiments, receiving the first user request may include receiving the current state of the blockchain. For example, the system may receive the current state of the blockchain corresponding to the blockchain operation from the second remote device. The system may determine a characteristic of the blockchain operation based on the current state. The system may then query the first user device to confirm the blockchain operation based on the characteristic. In some embodiments, the system may receive a second user request to confirm the execution of the blockchain operation based on the characteristic.
[0097] For example, the system may access a blockchain indexer and / or a blockchain estimation service to generate characteristics of a blockchain operation (e.g., transaction price, smart contract duration, etc.). The system may then generate a request to the user device to confirm the blockchain operation based on the characteristics.
[0098] At step 704, process 700 (e.g., using one or more of the components described above) can access a first user account. For example, in response to receiving the first user request, the system can access the first user account via an API implemented on a first remote device. In some embodiments, the first user account can correspond to a first public key, wherein a first cryptography-based storage application corresponding to the first user account is accessible by the first remote device. For example, in some embodiments, the first remote device can access the first cryptography-based storage application corresponding to the first user account through a platform application. In some embodiments, the first cryptography-based storage application can be used to perform a plurality of blockchain operations.
[0099] For example, a custodial cryptography-based storage application may be a cryptography-based storage application managed by a third-party exchange. For example, a custodial cryptography-based storage application may be a platform cryptography-based storage application, such that the custodial cryptography-based storage application is managed by a blockchain platform service. For a custodial cryptography-based storage application, an exchange (e.g., a blockchain platform service) may store and manage keys (e.g., private keys) corresponding to user accounts (e.g., corresponding to blockchain addresses). The task of the exchange may be to securely store funds (e.g., cryptocurrency) and / or facilitate blockchain operations based on funds. In some embodiments, the custodial cryptography-based storage application may be a cold storage hardware wallet. In this case, funds may be securely stored on designated hardware to provide additional security. Alternatively, some embodiments may use a non-custodial cryptography-based storage application, which may be browser-based (e.g., software installed on a mobile device).
[0100] At step 706, process 700 (e.g., using one or more components described above) can retrieve the first portion of the private key and the first user address. For example, the system can retrieve the first portion of the private key and the first user address from the first user account. For example, the API can retrieve the first portion of the private key and the first user address from the first user account.
[0101] For example, the system may use a user account corresponding to an account of a blockchain platform service. For example, the user account may correspond to a third-party intermediary (e.g., a platform service), as opposed to a non-custodial cryptography-based storage application (which may correspond to a user without a third-party intermediary). By having a user account corresponding to a platform service (which is separate and distinct from the non-custodial cryptography-based storage application), the system may provide additional features that would not be possible with conventional blockchain operations. For example, the system may enhance and / or modify blockchain operations before completion in order to prevent fraud, verify user intent, and / or otherwise increase security. Additionally or alternatively, by having a user account corresponding to a platform service (which is separate and distinct from the non-custodial cryptography-based storage application), the system may provide a single user with access to multiple custodial cryptography-based storage applications using a single account of the platform service.
[0102] As another example, a user address may correspond to a non-custodial cryptography-based storage application assigned by the blockchain. A non-custodial wallet may correspond to a private key and / or public key that allows blockchain operations to be performed using funds and / or information in the non-custodial wallet.
[0103] At step 708, process 700 (e.g., using one or more of the above components) can query the first user device to use the second portion of the private key. For example, the system can query the first user device to use the second portion of the private key when performing a blockchain operation. In some embodiments, the second portion of the private key can be stored on the first user device. As an example, the API can query the first user device to use the second portion of the private key when performing a blockchain operation. The API can send a request to a decentralized application browser (e.g., implemented on the first user device) to access the second portion of the private key stored on the first user device.
[0104] For example, the system may query the first user device to use its partial private key. For example, to maintain security, the first user device and the first remote device may not share their respective partial private keys. However, both devices may still need to use their partial private keys in order to perform blockchain operations. To achieve this, the system may use the Schnorr signature algorithm, the elliptic curve digital signature algorithm (ECDSA), the digital signature algorithm (DSA), and / or other suitable algorithms. For example, a key signing session may involve the setting of one or more parameters and a hash function.
[0105] For example, a threshold signature scheme may generate a secret key s during key generation and a random nonce k for each signing operation. In this case, a key signing session may require a minimum of four rounds for each signing operation (e.g., assuming that no round results in an error). For example, the system may use three rounds to obtain k, and the system may use one round to distribute signature shares and calculate the group signature.
[0106] In some embodiments, a key signing session can be established between the first user device and the first remote device. For example, querying the first user device to use the second partial private key can include the system establishing a key signing session between the first user device and the first remote device. In some embodiments, during the key signing session, the system can generate a random nonce value based on the first partial private key and the second partial private key, wherein the random nonce value is not shared with the first user device or the first remote device.
[0107] For example, a key signing session may involve the setting of one or more parameters and a hash function. The system may also select a random value. A random number may be any value that can be used once in a cryptographic communication. The system may determine the random number as a random or pseudo-random value. The random value may be selected by the system based on an authentication protocol to ensure that previous blockchain operations (and / or communications containing them) cannot be reused. The system may also use the random value to initialize a vector for a hash function. For example, the system may select a random value to adjust the difficulty level (e.g., the amount of work required) in a proof-of-work system.
[0108] At step 710, process 700 (e.g., using one or more of the components described above) can generate a first digital signature. For example, the system can generate the first digital signature based on the first partial private key and the second partial private key. For example, in some embodiments, the API can generate the first digital signature based on the first partial private key and the second partial private key.
[0109] For example, in some embodiments, the first digital signature can be based on multiple parameters. For example, the system can determine a first parameter that includes 32 bytes, determine a second parameter that includes 32 bytes, and determine a third parameter that includes 1 byte. The system can determine the parameters based on the blockchain protocol and / or a given standard. Additionally or alternatively, if the protocol allows customization, the system can select a given parameter (e.g., the number of bytes that comprise the digital signature). The system can increase the number of bytes in the digital signature to increase security.
[0110] In some embodiments, the first digital signature may be based on a characteristic of the first user device. For example, the system may determine a characteristic of the first user device. In some embodiments, the system may select a signature scheme for the first digital signature based on the characteristic. For example, in some embodiments, the system may select a signature scheme based on the processing power and / or geographic location of the first user device. For example, some devices may encounter problems with low processing power and / or low connectivity. In this way, the system can determine the characteristics of the user device and select a signature scheme based on the characteristics. For example, the system may select a flexible round optimized Schnorr threshold signature (FROST) protocol, which may use a two-round distributed key generation (DKG) protocol to generate the random number required for the signature.
[0111] At step 712, process 700 (e.g., using one or more of the components described above) can perform a blockchain operation. For example, the system can perform a blockchain operation based on the first digital signature and the first user address. For example, the API can perform a blockchain operation based on the first digital signature and the first user address. In some embodiments, a platform application (e.g., a blockchain platform service) can access a blockchain index service to perform a blockchain operation.
[0112] In some embodiments, performing a blockchain operation may include generating a modified blockchain operation. For example, in some embodiments, the system may perform a blockchain operation based on a first digital signature and a first user address by generating a modified blockchain operation based on a first user address. In some embodiments, the system may transmit the modified blockchain operation to a first cryptography-based storage application. For example, the system may determine a user address (e.g., corresponding to an account in a blockchain distributed ledger) that allows the blockchain operation to be performed using funds and / or information corresponding to the user address. The system may determine that a given user account (e.g., managed by a platform service) may correspond to a given user address. However, in order to facilitate additional features, the system may act as an intermediary. As part of this intermediary behavior, the system may modify the blockchain operation to reference from a user account to a user address.
[0113] In some embodiments, performing a blockchain operation may be based on a risk likelihood. For example, the system may perform a blockchain operation based on a first digital signature and a first user address by first determining a risk likelihood of the blockchain operation. The system may then generate a modified blockchain operation based on the risk likelihood. In some embodiments, the system may transmit the modified blockchain operation to the first cryptography-based storage application. In some embodiments, the modified blockchain operation causes the first cryptography-based storage application to transmit a warning to the first user device.
[0114] For example, the system can facilitate additional features by acting as an intermediary between a custodial cryptography-based storage application and a non-custodial cryptography-based storage application. Examples of these features can be determining risk likelihood. For example, risk likelihood can be a qualitative or quantitative measure of the likelihood of a given outcome of a blockchain operation. For example, the system can determine whether a blockchain operation is being performed using a prohibited address. In another example, the system can ensure that the blockchain operation is within a predetermined set of rules (e.g., based on one or more regulatory agency rulings). In yet another example, the system can determine whether a blockchain operation has a likelihood of completion.
[0115] In some embodiments, performing a blockchain operation may include determining a prohibited address. For example, the system may perform a blockchain operation based on a first digital signature and a first user address based on determining a second user address corresponding to the blockchain operation. In some embodiments, the system may determine that the second user address corresponds to a prohibited address. The system may then transmit an error message for the blockchain operation to the first user device in response to determining that the second user address corresponds to a prohibited address. Additionally or alternatively, the system may generate a modified blockchain operation based on determining that the second user address corresponds to a prohibited address. In some embodiments, the modified blockchain operation includes metadata corresponding to a read operation, wherein the read operation is performed by a blockchain indexing service.
[0116] For example, a read operation may cause the system to return tax, location, and / or other information corresponding to the address. In some embodiments, the system may prevent the blockchain operation from occurring. Alternatively, the system may generate a warning or other information (e.g., information related to the rationale for generating the warning) and transmit the generated information to the user device.
[0117] In some embodiments, the system may receive a third user request. For example, in some embodiments, the system may receive a third user request from a first user device. For example, the third user request may request access to the second partial private key. The system may then perform device authentication for the third user request. In some embodiments, the system may transmit data for the second partial private key to the first user device. The system may provide a cold storage mechanism for storing a partial private key of a user device and / or provide a mechanism for accessing a partial private key of a user device.
[0118] Conceived Figure 7 The steps or descriptions of can be used with any other embodiments of the present disclosure. Figure 7 The steps and descriptions described may be performed in alternative orders or in parallel to facilitate the purposes of the present disclosure. For example, each of these steps may be performed in any order or in parallel or simultaneously to reduce latency or increase the speed of the system or method. In addition, it should be noted that any component, device, or equipment discussed above with respect to the figures may be used to perform Figure 7 One or more steps in .
[0119] The above embodiments of the present disclosure are presented for the purpose of illustration and not limitation, and the present disclosure is limited only by the appended claims. In addition, it should be noted that the features and limitations described in any one embodiment can be applied to any embodiment herein, and the flowcharts or examples associated with one embodiment can be combined with any other embodiment in a suitable manner, completed in a different order, or completed in parallel. In addition, the systems and methods described herein can be executed in real time. It should also be noted that the above systems and / or methods can be applied to or used according to other systems and / or methods.
[0120] The present invention will be better understood with reference to the following embodiments:
[0121] A1. A method, the method comprising: receiving a first user request from a first user device to access a first user account corresponding to a first cryptography-based storage application, wherein the first cryptography-based storage application is used to perform multiple blockchain operations on a computer network based on a combined use of a first public key, a first portion of a private key, and a second portion of a private key, and wherein the second portion of the private key is inaccessible to a platform service that facilitates the first cryptography-based storage application; in response to receiving the first user request, authenticating the first user device as corresponding to the first user account at a first remote device; in response to authenticating the first user device, generating an encrypted communication for the first user device, wherein the encrypted communication includes instructions that, when executed by the first user device, cause the second portion of the private key to be stored on the first user device; transmitting the encrypted communication to the first user device; and registering the first user device as corresponding to the first user account at the platform service.
[0122] A2. The method described in embodiment A1 also includes: receiving a second request from a first user device to perform a blockchain operation corresponding to a first public key; retrieving a first partial private key and a first user address from a first user account; querying the first user device to use the second partial private key when performing the blockchain operation; generating a first digital signature based on the first partial private key and the second partial private key; and performing the blockchain operation based on the first digital signature and the first user address.
[0123] A3. A method according to any one of embodiments A1-A2, wherein generating encrypted communications for a first user device comprises: receiving a third user request from a second user device to authorize a platform service to transmit encrypted communications to the first user device; querying the second user device to obtain a recovery key, wherein the recovery key corresponds to a first user account; and determining to generate encrypted communications based on the recovery key.
[0124] A4. A method according to any one of embodiments A1-A3, wherein the recovery key is incompatible with the first public key and the first part of the private key of the plurality of blockchain operations.
[0125] A5. A method according to any one of embodiments A1-A4, wherein generating encrypted communications for the first user device includes: determining a third user device that currently has access to the first user account; and revoking the third user device's access to the first user account.
[0126] A6. A method according to any one of embodiments A1-A5, wherein generating encrypted communications for a first user device includes: determining a plurality of user devices that currently have recovery permissions for a first user account; querying the plurality of user devices to obtain authorization to generate encrypted communications; and determining whether a threshold number of user devices among the plurality of user devices provide authorization to generate encrypted communications.
[0127] A7. A method according to any one of embodiments A1-A6, wherein generating encrypted communication for a first user device includes: determining a first time when a first user request is received; determining a current time; determining a difference between the first time and the current time; and determining whether the difference satisfies a threshold time difference.
[0128] A8. A method according to any one of embodiments A1-A7, wherein generating encrypted communications for a first user device includes: determining the number of user devices currently authorized to access a first user account; retrieving a threshold number of user devices, wherein the threshold number of devices corresponds to a maximum number of user devices that can be authorized for a single user account; and determining whether the number of user devices meets the threshold number of user devices.
[0129] A9. The method of any one of embodiments A1-A8, wherein the instructions cause the private key to be used in signing the block of data or in verifying a signed block within the secure enclave.
[0130] A10. A method according to any one of embodiments A1-A9, wherein the first part key and the second part key are generated by: receiving public key encryption for the first device; generating ciphertext for the public key encryption; and splitting the private key encryption for the first device to generate the first part key and the second part key.
[0131] B1. A method, the method comprising: receiving a first user request to perform a blockchain operation corresponding to a first public key from a decentralized application browser implemented on a first user device; in response to receiving the first user request, accessing a first user account corresponding to the first public key via an application programming interface ("API") implemented on a first remote device, wherein a first cryptography-based storage application corresponding to the first user account is accessible to the first remote device; retrieving a first partial private key and a first user address from the first user account; querying the first user device to use a second partial private key when performing a blockchain operation, wherein the second partial private key is stored on the first user device; generating a first digital signature based on the first partial private key and the second partial private key; and performing the blockchain operation based on the first digital signature and the first user address.
[0132] B2. A method according to embodiment B1, wherein querying the first user device to use the second part of the private key includes establishing a key signing session between the first user device and the first remote device, wherein during the key signing session, a random nonce value is generated based on the first part of the private key and the second part of the private key, and wherein the random nonce value is not shared with the first user device or the first remote device.
[0133] B3. A method according to any one of embodiments B1-B2, wherein performing a blockchain operation based on the first digital signature and the first user address includes: generating a modified blockchain operation based on the first user address; and transmitting the modified blockchain operation to a first cryptography-based storage application.
[0134] B4. The method according to any one of embodiments B1-B3 further includes: determining a characteristic of the first user device; and selecting a signature scheme for the first digital signature based on the characteristic.
[0135] B5. A method according to any one of embodiments B1-B4, wherein performing a blockchain operation based on a first digital signature and a first user address includes: determining a risk potential of the blockchain operation; generating a modified blockchain operation based on the risk potential; and transmitting the modified blockchain operation to a first cryptography-based storage application, wherein the modified blockchain operation causes the first cryptography-based storage application to transmit a warning to the first user device.
[0136] B6. A method according to any one of embodiments B1-B5, wherein performing a blockchain operation based on the first digital signature and the first user address includes: determining a second user address corresponding to the blockchain operation; determining that the second user address corresponds to a prohibited address; and in response to determining that the second user address corresponds to the prohibited address, transmitting an error message for the blockchain operation to the first user device.
[0137] B7. A method according to any one of embodiments B1-B6, wherein performing a blockchain operation based on the first digital signature and the first user address includes: determining a second user address corresponding to the blockchain operation; determining that the second user address corresponds to a prohibited address; and generating a modified blockchain operation based on determining that the second user address corresponds to the prohibited address, wherein the modified blockchain operation includes metadata corresponding to a read operation, and wherein the read operation is performed by a blockchain indexing service.
[0138] B8. A method according to any one of embodiments B1-B7, wherein generating a first digital signature based on the first part of the private key and the second part of the private key includes: determining a first parameter comprising 32 bytes; determining a second parameter comprising 32 bytes; and determining a third parameter comprising 1 byte.
[0139] B9. A method according to any one of embodiments B1-B8, wherein receiving a first user request to perform a blockchain operation includes: receiving a current state of a blockchain corresponding to the blockchain operation from a second remote device; determining a characteristic of the blockchain operation based on the current state; querying the first user device to confirm the blockchain operation based on the characteristic; and receiving a second user request to confirm the execution of the blockchain operation based on the characteristic.
[0140] B10. The method according to any one of embodiments B1-B9 further includes: receiving a third user request from a first user device, wherein the third user request requests access to the second part of the private key; performing device authentication on the third user request; and transmitting data for the second part of the private key to the first user device.
[0141] C1. A tangible, non-transitory machine-readable medium storing instructions that, when executed by a data processing apparatus, cause the data processing apparatus to perform operations including those of any of embodiments A1-A10 or B1-B10.
[0142] C2. A system comprising: one or more processors; and a memory storing instructions that, when executed by the processor, cause the processor to implement operations including those of any of embodiments A1-A10 or B1-B10.
[0143] C3. A system comprising an apparatus for performing any of embodiments A1-A10 or B1-B10.
Claims
1. A system for managing partial private keys of a cryptographically based storage application used in blockchain operations of a decentralized application, the system comprising: The server is configured to: storing a first user account corresponding to a first cryptography-based storage application, wherein the first cryptography-based storage application is used to perform a plurality of blockchain operations on a computer network based on combined use of a first public key, a first partial private key, and a second partial private key; storing the first part of the private key; as well as not storing the second part of the private key; A platform service implemented on one or more processors, wherein the platform service is configured to: receiving, from a first user device, a first user request to access the first user account; in response to receiving the first user request, authenticating the first user device as corresponding to the first user account; generating an encrypted communication for the first user device in response to authenticating the first user device, wherein the encrypted communication includes instructions that, when executed by the first user device, cause the second portion of the private key to be stored on the first user device; transmitting the encrypted communication to the first user equipment; as well as The first user device is registered to correspond to the first user account.
2. A method comprising: receiving, from a first user device, a first user request to access a first user account corresponding to a first cryptography-based storage application, wherein the first cryptography-based storage application is used to perform a plurality of blockchain operations on a computer network based on combined use of a first public key, a first portion of a private key, and a second portion of a private key, and wherein the second portion of the private key is inaccessible to a platform service that facilitates the first cryptography-based storage application; authenticating, at a first remote device, the first user device as corresponding to the first user account in response to receiving the first user request; generating, in response to authenticating the first user device, an encrypted communication for the first user device, wherein the encrypted communication includes instructions that, when executed by the first user device, cause the second partial private key to be stored on the first user device; transmitting the encrypted communication to the first user equipment; as well as The first user device is registered at the platform service as corresponding to the first user account.
3. The method according to claim 2, further comprising: receiving, from the first user device, a second request to perform a blockchain operation corresponding to the first public key; retrieving the first partial private key and the first user address from the first user account; querying the first user device to use the second portion of the private key when performing the blockchain operation; generating a first digital signature based on the first partial private key and the second partial private key; as well as The blockchain operation is performed based on the first digital signature and the first user address.
4. The method according to claim 2, wherein: Generating the encrypted communication for the first user equipment includes: receiving, from a second user device, a third user request authorizing the platform service to transmit the encrypted communication to the first user device; querying the second user device to obtain a recovery key, wherein the recovery key corresponds to the first user account; Generating the encrypted communication is determined based on the recovery key.
5. The method according to claim 4, wherein: The recovery key is incompatible with the first public key and the first portion of the private key for the plurality of blockchain operations.
6. The method according to claim 2, wherein: Generating the encrypted communication for the first user equipment includes: determining a third user device that currently has access to the first user account; and Revoke the third user device's access to the first user account.
7. The method according to claim 2, wherein: Generating the encrypted communication for the first user equipment includes: determining a plurality of user devices that currently have restoration authority for the first user account; querying the plurality of user devices to obtain authorization to generate the encrypted communication; and A determination is made as to whether a threshold number of the plurality of user devices have provided authorization to generate the encrypted communication.
8. The method according to claim 2, wherein: Generating the encrypted communication for the first user equipment includes: determining a first time when the first user request is received; Determine the current time; determining a difference between the first time and the current time; and A determination is made as to whether the difference satisfies a threshold time difference.
9. The method according to claim 2, wherein: Generating the encrypted communication for the first user equipment includes: determining a number of user devices currently authorized to access the first user account; retrieving a threshold number of user devices, wherein the threshold number of devices corresponds to a maximum number of user devices that can be authorized for a single user account; and A determination is made as to whether the number of user devices satisfies a threshold number of user devices.
10. The method according to claim 2, wherein: The instructions cause the private key to be used when signing a block of data or verifying a signed block within a secure enclave.
11. The method according to claim 2, wherein: The first part of the key and the second part of the key are generated by: receiving a public key encryption for the first device; generating a ciphertext for encryption with the public key; and The private key encryption for the first device is split to generate the first partial key and the second partial key.
12. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause operations comprising: receiving, from a first user device, a first user request to access a first user account corresponding to a first cryptography-based storage application, wherein the first cryptography-based storage application is used to perform a plurality of blockchain operations on a computer network based on combined use of a first public key, a first portion of a private key, and a second portion of a private key, and wherein the second portion of the private key is inaccessible to a platform service that facilitates the first cryptography-based storage application; authenticating, at a first remote device, the first user device as corresponding to the first user account in response to receiving the first user request; generating, in response to authenticating the first user device, an encrypted communication for the first user device, wherein the encrypted communication includes instructions that, when executed by the first user device, cause the second partial private key to be stored on the first user device; transmitting the encrypted communication to the first user equipment; as well as The first user device is registered at the platform service as corresponding to the first user account.
13. The non-transitory computer readable medium of claim 12, wherein: The instruction causes further operations, the further operations comprising: receiving, from the first user device, a second request to perform a blockchain operation corresponding to the first public key; retrieving the first partial private key and the first user address from the first user account; querying the first user device to use the second portion of the private key when performing the blockchain operation; generating a first digital signature based on the first partial private key and the second partial private key; and The blockchain operation is performed based on the first digital signature and the first user address.
14. The non-transitory computer readable medium of claim 12, wherein: Generating the encrypted communication for the first user equipment includes: receiving, from a second user device, a third user request authorizing the platform service to transmit the encrypted communication to the first user device; querying the second user device to obtain a recovery key, wherein the recovery key corresponds to the first user account; Generating the encrypted communication is determined based on the recovery key.
15. The non-transitory computer readable medium of claim 14, wherein: The recovery key is incompatible with the first public key and the first portion of the private key for the plurality of blockchain operations.
16. The non-transitory computer readable medium of claim 12, wherein: Generating the encrypted communication for the first user equipment includes: determining a third user device that currently has access to the first user account; and Revoke the third user device's access to the first user account.
17. The non-transitory computer readable medium of claim 12, wherein: Generating the encrypted communication for the first user equipment includes: determining a plurality of user devices that currently have restoration authority for the first user account; querying the plurality of user devices to obtain authorization to generate the encrypted communication; and A determination is made as to whether a threshold number of the plurality of user devices have provided authorization to generate the encrypted communication.
18. The non-transitory computer readable medium of claim 12, wherein: Generating the encrypted communication for the first user equipment includes: determining a first time when the first user request is received; Determine the current time; determining a difference between the first time and the current time; and A determination is made as to whether the difference satisfies a threshold time difference.
19. The non-transitory computer readable medium of claim 12, wherein: Generating the encrypted communication for the first user equipment includes: determining a number of user devices currently authorized to access the first user account; retrieving a threshold number of user devices, wherein the threshold number of devices corresponds to a maximum number of user devices that can be authorized for a single user account; and A determination is made as to whether the number of user devices satisfies a threshold number of user devices.
20. The non-transitory computer readable medium of claim 12, wherein: The first part of the key and the second part of the key are generated by: receiving a public key encryption for the first device; generating a ciphertext for encryption with the public key; and The private key encryption for the first device is split to generate the first partial key and the second partial key.
21. A system for facilitating secure authentication when performing blockchain operations using a cryptography-based storage application, the system comprising: A decentralized application browser implemented on a first user device, wherein the decentralized application browser is configured to: receiving a user request to perform a plurality of blockchain operations on a computer network; as well as accessing a second portion of a private key stored on the first user device; an application programming interface ("API") implemented on a first remote device, the application programming interface being configured to: Receiving a first user request to perform a blockchain operation corresponding to a first public key; In response to receiving the first user request, accessing a first user account corresponding to the first public key, wherein a first cryptography-based storage application corresponding to the first user account is accessible by the first remote device via a platform application, and wherein the first cryptography-based storage application is used to perform the plurality of blockchain operations; retrieving a first partial private key and a first user address from the first user account; querying the first user device to use the second portion of the private key when performing the blockchain operation; generating a first digital signature based on the first partial private key and the second partial private key; and Executing the blockchain operation based on the first digital signature and the first user address; and A blockchain platform service, wherein the blockchain platform service is configured to: accessing the first cryptography-based storage application; and Accessing a blockchain index service to perform the blockchain operation.
22. A method comprising: receiving, from a decentralized application browser implemented on a first user device, a first user request to perform a blockchain operation corresponding to a first public key; in response to receiving the first user request, accessing a first user account corresponding to the first public key via an application programming interface ("API") implemented on a first remote device, wherein a first cryptography-based storage application corresponding to the first user account is accessible by the first remote device; retrieving a first partial private key and a first user address from the first user account; querying the first user device to use a second portion of a private key when performing the blockchain operation, wherein the second portion of the private key is stored on the first user device; generating a first digital signature based on the first partial private key and the second partial private key; and The blockchain operation is performed based on the first digital signature and the first user address.
23. The method according to claim 22, wherein: Querying the first user device to use the second partial private key includes establishing a key signing session between the first user device and the first remote device, wherein during the key signing session, a random nonce value is generated based on the first partial private key and the second partial private key, and wherein the random nonce value is not shared with the first user device or the first remote device.
24. The method according to claim 22, wherein: Executing the blockchain operation based on the first digital signature and the first user address includes: generating a modified blockchain operation based on the first user address; and Transmitting the modified blockchain operation to the first cryptography-based storage application.
25. The method of claim 22, further comprising: determining a characteristic of the first user equipment; as well as A signature scheme for the first digital signature is selected based on the characteristic.
26. The method of claim 22, wherein: Executing the blockchain operation based on the first digital signature and the first user address includes: Determining the risk potential of the blockchain operation; generating a modified blockchain operation based on the risk likelihood; and The modified blockchain operation is transmitted to the first cryptography-based storage application, wherein the modified blockchain operation causes the first cryptography-based storage application to transmit an alert to the first user device.
27. The method of claim 22, wherein: Executing the blockchain operation based on the first digital signature and the first user address includes: determining a second user address corresponding to the blockchain operation; determining that the second user address corresponds to a prohibited address; and In response to determining that the second user address corresponds to the prohibited address, transmitting an error message for the blockchain operation to the first user device.
28. The method of claim 22, wherein: Executing the blockchain operation based on the first digital signature and the first user address includes: determining a second user address corresponding to the blockchain operation; determining that the second user address corresponds to a prohibited address; and Generating a modified blockchain operation based on determining that the second user address corresponds to the prohibited address, wherein the modified blockchain operation includes metadata corresponding to a read operation, and wherein the read operation is performed by a blockchain indexing service.
29. The method of claim 22, wherein: Generating the first digital signature based on the first partial private key and the second partial private key includes: Determine a first parameter comprising 32 bytes; determining a second parameter comprising 32 bytes; and A third parameter including 1 byte is determined.
30. The method of claim 22, wherein: Receiving the first user request to perform the blockchain operation includes: receiving, from a second remote device, a current state of a blockchain corresponding to the blockchain operation; Determining a characteristic of the blockchain operation based on the current state; querying the first user device to confirm the blockchain operation based on the characteristic; and A second user request is received, the second user requesting confirmation of performance of the blockchain operation based on the characteristic.
31. The method of claim 22, further comprising: receiving a third user request from the first user device, wherein the third user request requests access to the second portion of the private key; performing device authentication for the third user request; as well as Data for the second partial private key is transmitted to the first user device.
32. A non-transitory computer-readable medium for facilitating secure authentication when performing blockchain operations using a cryptography-based storage application, the non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause operations comprising: receiving, from a decentralized application browser implemented on a first user device, a first user request to perform a blockchain operation corresponding to a first public key; in response to receiving the first user request, accessing a first user account corresponding to the first public key via an application programming interface ("API") implemented on a first remote device, wherein a first cryptography-based storage application corresponding to the first user account is accessible by the first remote device; retrieving a first partial private key and a first user address from the first user account; querying the first user device to use a second portion of a private key when performing the blockchain operation, wherein the second portion of the private key is stored on the first user device; generating a first digital signature based on the first partial private key and the second partial private key; and The blockchain operation is performed based on the first digital signature and the first user address.
33. The non-transitory computer readable medium of claim 32, wherein: Querying the first user device to use the second partial private key includes establishing a key signing session between the first user device and the first remote device, wherein during the key signing session, a random nonce value is generated based on the first partial private key and the second partial private key, and wherein the random nonce value is not shared with the first user device or the first remote device.
34. The non-transitory computer readable medium of claim 32, wherein: Executing the blockchain operation based on the first digital signature and the first user address includes: generating a modified blockchain operation based on the first user address; and Transmitting the modified blockchain operation to the first cryptography-based storage application.
35. The non-transitory computer readable medium of claim 32, wherein: The instruction causes further operations, the further operations comprising: determining a characteristic of the first user equipment; and A signature scheme for the first digital signature is selected based on the characteristic.
36. The non-transitory computer readable medium of claim 32, wherein: Executing the blockchain operation based on the first digital signature and the first user address includes: Determining the risk potential of the blockchain operation; generating a modified blockchain operation based on the risk likelihood; and The modified blockchain operation is transmitted to the first cryptography-based storage application, wherein the modified blockchain operation causes the first cryptography-based storage application to transmit an alert to the first user device.
37. The non-transitory computer readable medium of claim 32, wherein: Executing the blockchain operation based on the first digital signature and the first user address includes: determining a second user address corresponding to the blockchain operation; determining that the second user address corresponds to a prohibited address; and In response to determining that the second user address corresponds to the prohibited address, transmitting an error message for the blockchain operation to the first user device.
38. The non-transitory computer readable medium of claim 32, wherein: Executing the blockchain operation based on the first digital signature and the first user address includes: determining a second user address corresponding to the blockchain operation; determining that the second user address corresponds to a prohibited address; and Generating a modified blockchain operation based on determining that the second user address corresponds to the prohibited address, wherein the modified blockchain operation includes metadata corresponding to a read operation, and wherein the read operation is performed by a blockchain indexing service.
39. The non-transitory computer readable medium of claim 32, wherein: Receiving the first user request to perform the blockchain operation includes: receiving, from a second remote device, a current state of a blockchain corresponding to the blockchain operation; Determining a characteristic of the blockchain operation based on the current state; querying the first user device to confirm the blockchain operation based on the characteristic; and A second user request is received, the second user requesting confirmation of performance of the blockchain operation based on the characteristic.
40. The non-transitory computer readable medium of claim 32, wherein: The instruction causes further operations, the further operations comprising: receiving a third user request from the first user device, wherein the third user request requests access to the second portion of the private key; performing device authentication for the third user request; and Data for the second partial private key is transmitted to the first user device.
