Ensuring browser extended cryptographic wallet security using hardware softdog

Abstract

Cryptocurrency transactions become more and more common. Important security practices for cryptocurrency transactions include maintaining an encrypted wallet with a private key for signing a cryptocurrency transaction. A hardware-based encrypted wallet with a secure element that retains a private key is highly secure. However, hardware-based encrypted wallets may be bulky due to the need to have a human-readable interface for verifying transaction details. An improved hardware-based encrypted wallet is provided that omits a human readable interface and provides a user with a display screen using a wirelessly connected authentication device, such as a smartphone. In this manner, transactions may be secured without the need for a hardware wallet of bulky or cumbersome dimensions.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based upon and claims the benefit and priority of U.S. Provisional Patent Application No. 63 / 410,583, filed on September 27, 2022, entitled “SECURING BROWSER EXTENSION CRYPTOWALLETS USING USB DONGLE,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present invention relates to crypto wallets (cryptowallets), and more particularly, the present disclosure relates to secure hardware for use with browser extension crypto wallets. Background Art

[0004] Crypto wallets are used to generate and store the cryptographic keys needed to perform cryptocurrency transactions. The private keys of crypto wallets are usually generated via a deterministic hierarchical scheme based on a master secret (called a seed value). In addition to the cryptographic seed value, the private key and / or wallet personal identification number (PIN) code are also important to maintain securely. If the seed value, private key and / or wallet PIN code are leaked or compromised, then hackers may gain control of the crypto wallet and / or initiate harmful transactions. Summary of the invention

[0005] A hardware wallet dongle is provided. The hardware wallet dongle can be used for a secure browser extension cryptographic wallet system to ensure the security of cryptocurrency transactions in a browser extension wallet. The hardware dongle may include a security element configured to protect a user's private key. The hardware dongle may include a first communication interface that connects the hardware wallet dongle to a browsing device running a browser extension wallet by electronic communication. The hardware dongle may include a second communication interface that connects the hardware wallet dongle to an authentication device by electronic communication. Both the first communication interface and the second communication interface may be connected to a security element. In response to a first authentication message from an authentication device being received by a second communication interface and verified as credible by a security element, the security element may sign a transaction and transmit a signed transaction to the first communication interface to supply to a browser extension wallet.

[0006] One or more additional features may also be included. In various embodiments, the authentication device is a smartphone. In various embodiments, the first communication interface is a wired interface. The wired interface may be a universal serial bus interface. The second communication interface may be a wireless interface. In various embodiments, the hardware wallet dongle does not include a screen display. In various embodiments, the hardware wallet dongle does not include a human-readable interface. In various embodiments, the first authentication message is a confirmation of the identity of the user by at least one biometric sensor.

[0007] A secure browser extension crypto wallet system is provided. The system can be used to ensure the security of cryptocurrency transactions in a browser extension wallet. The system can include a hardware wallet dongle. The hardware wallet dongle can be used in a secure browser extension crypto wallet system to ensure the security of cryptocurrency transactions in a browser extension wallet. The hardware wallet dongle can include a security element configured to protect a user's private key. The hardware wallet dongle can include a first communication interface that connects the hardware wallet dongle to a browsing device running a browser extension wallet in electronic communication. The hardware wallet dongle can include a second communication interface that connects the hardware wallet dongle to an authentication device in electronic communication. Both the first communication interface and the second communication interface are connected to a security element. In response to a first authentication message from an authentication device being received by the second communication interface and verified as credible by the security element, the security element signs the transaction and transmits the signed transaction to the first communication interface to supply to the browser extension wallet. The browsing device can run a browser extension wallet. The browsing device is connected to a network that can access a blockchain to write the signed transaction to the blockchain. The smartphone can run a smartphone application and can be an authentication device. The authentication device includes a biometric sensor. The first authentication message is the authentication of the user's identity by the biometric sensor.

[0008] One or more additional features may also be included. In various embodiments, the biometric sensor is a fingerprint sensor. In various embodiments, the biometric sensor is a facial recognition sensor. The sensor may be a touch screen for entering a PIN code. In various embodiments, the browsing device is a commodity PC. The authentication device may be a smartphone. The first communication interface may be a wired interface. The wired interface may be a universal serial bus interface. The second communication interface may be a wireless interface. In various embodiments, the hardware wallet dongle does not include a screen display. In various embodiments, the hardware wallet dongle does not include a human readable interface.

[0009] A method for performing cryptocurrency transactions is provided. The transaction may be performed using a secure browser extension crypto wallet system for ensuring the security of cryptocurrency transactions in a browser extension wallet. The method may include sending a cryptocurrency transaction to a hardware wallet dongle connected to the browser device via a first communication interface by a browser extension wallet running on a browser device. The method may include receiving a transaction, parsing the transaction, and generating a visible representation of the transaction by a secure element of the hardware wallet dongle. The method may include sending a visible representation by a secure element to a second communication interface that can be wirelessly connected to an authentication device. The method may include receiving a first authentication message from the second communication interface by the secure element, the first authentication message corresponding to the verification of the user's identity by the authentication device. The method may include signing the transaction by the secure element in response to the first authentication message. The method may include transmitting a signed transaction to the browser extension wallet by the secure element via the first communication interface, so that the signed transaction is written to the blockchain by the browser extension wallet. In various embodiments, the visible representation is the transaction amount and the recipient address. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] A more complete understanding of the invention may be obtained by referring to the detailed description and claims when considered in conjunction with the accompanying drawings, in which like reference numerals represent similar elements throughout the drawings, and:

[0011] Figure 1 is a schematic diagram of components of a secure browser-based crypto wallet system according to various embodiments;

[0012] Figure 2 is a schematic diagram of components of a hardware wallet dongle of a secure browser-based crypto wallet system according to various embodiments;

[0013] Figure 3 is a schematic diagram of components of a hardware wallet dongle of a secure browser-based crypto wallet system having a sensor on the hardware wallet dongle according to various embodiments;

[0014] Figure 4 Methods of configuring a system for secure transactions according to various embodiments are described; and

[0015] Figure 5 Methods of performing cryptocurrency transactions using a secure browser-based crypto wallet system according to various embodiments are described. DETAILED DESCRIPTION

[0016] The following description is only for various exemplary embodiments and is not intended to limit the scope, applicability or configuration of the present disclosure in any way. On the contrary, the following description is intended to provide a convenient description for implementing various embodiments including the best mode. It will be clear that various changes can be made to the function and arrangement of the elements described in these embodiments without departing from the scope of the appended claims.

[0017] Crypto wallets are used to generate and store the cryptographic keys needed to perform cryptocurrency transactions. Crypto wallets include at least two common types. A software wallet is a crypto wallet that is a smartphone or desktop application that stores cryptographic keys and also manages incoming and outgoing transactions. A hardware wallet is a crypto wallet with an embedded device (such as a secure element (SE)) that stores a private key for signing outgoing transactions. The hardware wallet communicates with a smartphone, desktop, or web application "watch-only wallet" that only stores the corresponding public key of the hardware wallet's private key. The watch wallet monitors incoming transactions and prepares unsigned outgoing transactions for the embedded device, but cannot sign outgoing transactions. The embedded device verifies transaction details, retrieves applicable signing keys, signs transactions, and sends signed transactions back to the smartphone, desktop, or web application to broadcast to a mining node.

[0018] Hardware crypto wallets are known to be more secure than software crypto wallets because software crypto wallets coexist with other applications on a smartphone or desktop and therefore private keys are vulnerable to software attacks on the shared platform, whereas keys in a hardware crypto wallet never leave the embedded device. Access to hardware crypto wallet operations is typically protected by a personal identification number (PIN) or a sensed biometric feature such as a fingerprint or facial recognition.

[0019] The private key of the crypto wallet can be generated via a deterministic hierarchical scheme based on a master secret. The master secret is called the seed value. The seed value is important and must be maintained securely. The private key must also be maintained securely. In addition, in some cases, the user may be required to enter a PIN code associated with the crypto wallet to authorize various transactions. The PIN code should also be maintained securely.

[0020] In parallel with these security requirements, wallet users also expect operational convenience. One way to increase convenience is to perform crypto wallet transactions on a web browser. However, while a web browser increases convenience, it also introduces security risks.

[0021] Therefore, performing crypto wallet transactions on a web browser is difficult for a variety of reasons. For example, browser software is built on an operating system (e.g., Windows or Apple), which controls and oversees the operation of applications (such as wallet software applications). Malware or malicious software may compromise the operation of applications and / or the operating system. Malicious firmware may compromise the operation and security of computer storage components (such as electronic memory) and user interface (UI) components (such as displays and touch controllers).

[0022] These attacks may result in the compromise of user inputs and outputs to / from the computer UI and the storage of wallet secrets in the smartphone electronic memory. Such compromise may result in a malicious attacker gaining access to the crypto wallet private key, seed phrase, and / or wallet PIN. An attacker may compromise user transaction inputs or outputs, allowing the attacker to change the cryptocurrency transaction recipient or the cryptocurrency transaction amount.

[0023] A popular form of cryptocurrency wallet is a browser extension wallet that runs software from within the browser. These wallets are typically run on a computer and enable an interactive Web3 user experience. One problem with this type of wallet is the security of protecting the storage of cryptographic private keys, signing transactions with keys, and confirming transactions. One reason is that computer platforms, especially web browsers, are vulnerable to cybersecurity attacks. A USB wallet with a screen on a USB wallet device is a solution. However, this device is inconvenient. First, the form factor requires that the USB wallet be connected to the computer using a USB cable and the wallet be placed on a table or suspended. This is inconvenient and limits the mobility of the laptop. In addition, it is costly to provide a screen on a USB device.

[0024] Therefore, the disclosure herein provides a security solution for browser extension cryptocurrency wallets, which has a small size specification that can be implemented in the form of a small USB dongle. The disclosure also provides a USB dongle's security element to store private keys and / or seed phrases, parse cryptocurrency transactions and / or generate visible representations of transactions to present to users on smartphone devices. The disclosure provides a Bluetooth low energy (BLE) radio, which connects the USB dongle to a smartphone running a corresponding application, which presents a visible representation of the transaction and facilitates the user to send confirmation or rejection of the transaction to the security element through Bluetooth low energy (BLE) communication. The disclosure also provides a touch button or fingerprint touch ID module connected to the security element, which proves to the security element that the appropriate user of the system is present and knows that the transaction is being performed. In some cases, the touch button or fingerprint touch ID module or another sensor is located on different devices, such as a separate authentication device. The disclosure includes a USB interface for communicating from a USB dongle to a browser extension wallet. The disclosure provides a visual indicator (such as a light emitting diode (LED)) that shows the user that an activity is occurring on the USB dongle.

[0025] The present disclosure includes systems and methods that address both convenience and security considerations while avoiding bulky or cumbersome hardware-based wallet devices. The present disclosure provides a hardware solution for isolating crypto wallet operations. The present disclosure preserves the current form factor of computers by avoiding the use of large or bulky USB devices or USB devices with large screen displays (e.g., traditional hardware wallets).

[0026] refer to Figure 1, a secure browser extension cryptographic wallet system 100 ("system" 100) is illustrated in block diagram form. System 100 includes a browsing device 106. Browsing device 106 can be a computer, or can be a handheld computer, or can be an application-specific integrated circuit (ASIC) device, or can be any other desired computing platform. Browsing device 106 can be connected to hardware wallet dongle 108. Hardware wallet dongle 108 includes a peripheral device that can be connected to browsing device 106, and provides a secure storage and / or secure execution environment for computer data or code to be stored or executed without potential interception, code injection, harmful access or other illegal damage. Hardware wallet dongle 108 can provide a secure element configured to protect the user's private key (such as an asymmetric cryptography key). Finally, system 100 can interoperate with authentication device 110. Authentication device 110 can include a smart phone device (such as a phone that can run an application), or authentication device 110 can be a dedicated computing device that only interacts with secure browser extension cryptographic wallet system 100. The authentication device 110 may wirelessly communicate with the hardware wallet dongle 108 and may provide a user-readable interface for the hardware wallet dongle 108. Thus, the authentication device 110 may have a display 212 ( Figure 2-Figure 3 ), wherein an application running on the authentication device 110 can interact with the hardware wallet dongle 108 so that the hardware wallet dongle 108 can provide data to the authentication device 110 for the user to display on a user-readable interface device (such as a display 212 ( Figure 2-Figure 3 In another example, the authentication device 110 may provide a mechanism for the user to approve or deny a proposed transaction associated with the data being reviewed on the user-readable interface device, and the authentication device 110 may transmit data representing the approval or denial to the hardware wallet dongle 108. For example, the display 212 ( Figure 2-Figure 3 ) may be a touch screen.

[0027] Continue to refer Figure 1 , but also refer to Figure 2 and Figure 3 As briefly mentioned, the system 100 includes a browsing device 106. The browsing device 106 may be a commodity personal computer (“PC”). The browsing device 106 may include a browser 102 and a browser extension wallet 104. The browser 102 may include a software application that allows the browsing device 106 to access network resources (such as websites, remote computers, Web3 applications, blockchain resources, etc.). The system 100 may also include a browser extension wallet 104. The browser extension wallet 104 is a software-based cryptocurrency wallet that is integrated into the browser 102 of the browsing device 106.

[0028] As also briefly mentioned, the system 100 includes a hardware wallet dongle 108. The hardware wallet dongle 108 includes a hardware device that connects to the browsing device 106. The hardware wallet dongle 108 can be connected via a universal serial bus (USB) or other connection type. Therefore, the hardware wallet dongle 108 can have a first communication interface 204. The first communication interface 204 can be a universal serial bus connection interface. The first communication interface 204 connects the hardware wallet dongle 108 to the browsing device 106 in electronic communication, and correspondingly, connects the hardware wallet dongle 108 to the browser extension wallet 104 of the browsing device 106 in electronic communication. The hardware wallet dongle 108 can also have a second communication interface 202. The second communication interface 202 connects the hardware wallet dongle 108 to the authentication device 110 in electronic communication. In this way, the hardware wallet dongle 108 can utilize the display 212 of the authentication device 110.

[0029] The hardware wallet dongle 108 may include a security element 206. A security element 206 (SE) is a tamper-proof platform that can securely host applications and their confidential and cryptographic data. For example, the security element 206 may have a memory and / or processor for storing seeds or private keys and for performing cryptographic operations using seeds or private keys. For example, one or more key pairs may be generated within the SE to enhance security so that the keys are hardware-supported and cannot be retrieved outside the SE. In various cases, one or more of the private keys are retained in the SE. This also helps to improve security. By retaining the keys within the SE, the keys can be protected from the threat of being retrieved outside the SE, but can still be used for cryptographic operations. The security element may store private keys (seed phrases), parse cryptocurrency transactions, generate visible representations of transactions to be presented to users, and / or receive user confirmation via buttons or other inputs connected to the security element.

[0030] Finally, the hardware wallet dongle 108 may have a sensor 210 . Figure 2 A hardware wallet dongle 108 is shown with a sensor 210. In other cases, Figure 3 The authentication device 110 is shown with a sensor 210. Referring now to Figure 2 and Figure 3 , the sensor 210 may include an authentication sensor, such as a biometric sensor or a code entry mechanism. The biometric sensor may be a fingerprint recognition touch sensor (e.g., Touch ID) or a facial recognition optical sensor (e.g., Face ID). In this way, the identity of a user interacting with a hardware wallet dongle 108 and / or authentication device 110 in connection with a transaction with the browser extension wallet 104 may be verified, thereby mitigating the risk of harmful or illicit transactions.

[0031] Notably, in various embodiments, the hardware wallet dongle 108 does not include a screen display. In various embodiments, the hardware wallet dongle 108 does not include a human-readable interface. In this way, the hardware wallet dongle 108 can be significantly more compact and convenient than a hardware wallet having a human-readable interface directly connected to a secure element.

[0032] Combinations of components can be used to interoperate in different ways. For example, Figure 4 An example method 400 of a system for secure transactions using the above system configuration is described. A user can link a hardware wallet dongle to a browser extension wallet (box 402). For example, a user can connect a dongle to a browsing device with a browser extension wallet. A user can connect an authentication device to a hardware wallet dongle (box 404). For example, a user can connect a smartphone to a hardware wallet dongle via Bluetooth Low Energy (BLE) or other wireless connection, and the smartphone has a smartphone application configured to communicate with the hardware wallet dongle. A user can establish a first transaction verification identifier (such as facial recognition, fingerprint recognition, or a passcode identifier) ​​for typing into a smartphone application configured to communicate with a hardware wallet dongle (or for typing directly into a sensor of a hardware wallet dongle) (box 406). The hardware wallet dongle can establish a private key (e.g., a seed phrase) on a secure element (box 408). In various cases, establishing a private key includes cryptographically generating a private key by a secure element. In other cases, establishing a private key can include a user loading a seed phrase onto a hardware wallet device via a USB connection to a browsing device or via a Bluetooth Low Energy (BLE) connection to a smartphone. Similarly, the key may be loaded via manual entry via BLE, USB, or near field communication. Optionally, the key is transmitted once to the authentication device for visual display to the user for manual backup (block 410). In other cases, the key is not transmitted.

[0033] Now, the device is configured to perform a cryptographic transaction. To perform a cryptographic transaction, further steps may be performed. For example, now referring to Figure 5, a method 500 for performing cryptocurrency transactions using a secure browser extension crypto wallet system may be provided. Method 500 may include a user typing a cryptocurrency transaction on a browser extension wallet running on a browser device (box 502). The browser extension wallet running on the browser device may send a cryptocurrency transaction to a hardware wallet dongle connected to the browser device via a first communication interface (box 504). The secure element of the hardware wallet dongle receives the transaction, parses the transaction, and generates a visible representation of the transaction (box 506). In various embodiments, the visible representation includes the transaction amount and the recipient address. Then, the secure element causes the hardware wallet dongle to send a notification to the authentication device (box 508). For example, the hardware wallet dongle may send an application push notification to a smartphone, and may send a visible representation to the smartphone. In response, the user opens the application notification on the authentication device so that the user can view the visible representation (box 510). The user may interact with the sensor to confirm that the visual representation of the transaction on the authentication device is accurate (box 512). This interaction may take various forms. For example, the user may press a button. The user may type a PIN code on the authentication device via the touch screen of the authentication device. The user may provide biometric information, such as touching the sensor to confirm a fingerprint or looking at the sensor to confirm facial recognition. The sensor may be on the authentication device. The sensor may be on the hardware wallet dongle. In response to the interaction, the transaction is confirmed to be accurate, and in various embodiments, the identity of the user is confirmed to be authorized. Therefore, in response to the interaction, the sensor of the authentication device (e.g., a smart phone application) sends a signature confirmation to the hardware wallet dongle, more specifically, to the security element of the hardware wallet dongle. In other words, the security element receives a first authentication message from the second communication interface, which corresponds to the verification of the user's identity by the authentication device (box 514). In response to the first authentication message, the security element may sign the transaction using a private key (box 516). The security element may transmit the signed transaction to the browser extension wallet via the first communication interface, so that the browser extension wallet writes the signed transaction to the blockchain (box 518). The browser extension wallet receives the signed transaction and publishes the signed transaction to the blockchain to complete the transaction (box 520).

[0034] In addition, users can also establish signing policies for hardware wallet dongles, such as including recipient whitelists or blacklists, transaction amount limits, destination address selection criteria, or other requirements.

[0035] The present disclosure has been described with reference to various embodiments. However, those skilled in the art recognize that various modifications and changes may be made without departing from the scope of the present disclosure. For example, features of different embodiments may be combined. Therefore, the description should be regarded as illustrative rather than restrictive, and all such modifications are intended to be included within the scope of the present disclosure.

[0036] For the sake of brevity, the conventional techniques of manufacture and construction may not be described in detail herein. In addition, the connecting lines shown in the various figures contained herein are intended to represent exemplary functional relationships and / or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may exist in the actual construction method. As used herein, mechanical communication means any engagement, connection, combination or arrangement, thereby maintaining, retaining or fixing an article in a relatively static spatial relationship with another article. As used herein, electronic communication means any wired, wireless, analog, digital or other mechanism, thereby transmitting information between a machine, circuit or device.

[0037] Benefits, other advantages, and solutions to problems have been described herein with respect to various embodiments. However, these benefits, advantages, solutions to problems, and any elements that may cause any benefit, advantage, or solution to appear or become more apparent, should not be construed as key, required, or essential features or elements of the invention. In addition, when a phrase similar to "at least one of A, B, and C" or "at least one of A, B, or C" is used in a claim or specification, it is intended that the phrase be interpreted to mean that A can exist alone in an embodiment, B can exist alone in an embodiment, C can exist alone in an embodiment, or any combination of elements A, B, and C can exist in a single embodiment; for example, A and B, A and C, B and C, or A and B and C.

[0038] As used herein, the singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise. As used herein, the terms "for example," "for example," "such as," or "including" are meant to introduce examples that further illustrate a more general subject matter. Unless otherwise noted, these examples are embodiments of the present disclosure and are not meant to be limiting in any way.

[0039] In addition, regardless of whether the elements, components or method steps in the present disclosure are explicitly recorded in the claims, these elements, components or method steps are not intended to be dedicated to the public. Unless any claim element herein is explicitly recorded using the phrase "parts for...", these elements shall not be interpreted in accordance with the provisions of 35 U.S.C. 112 (f). As used herein, the terms "comprises", "includes" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including the list of elements includes not only these elements, but also other elements that are not explicitly listed or inherent in such a process, method, article or device.

Claims

1. A hardware wallet dongle for a secure browser extension crypto wallet system, for ensuring the security of cryptocurrency transactions in a browser extension wallet, the hardware wallet dongle comprising: a secure element configured to protect a user's private key; a first communication interface that connects the hardware wallet dongle to a browsing device running the browser extension wallet in electronic communication; as well as a second communication interface, the second communication interface connecting the hardware wallet dongle to the authentication device by electronic communication, wherein the first communication interface and the second communication interface are both connected to the security element, and wherein in response to a first authentication message from the authentication device being received by the second communication interface and verified as authentic by the secure element, the secure element signs a transaction and transmits the signed transaction to the first communication interface for provision to the browser extension wallet.

2. The hardware wallet dongle of claim 1 , wherein the authentication device is a smartphone.

3. The hardware wallet dongle of claim 1 , wherein the first communication interface is a wired interface.

4. The hardware wallet dongle of claim 3, wherein the wired interface is a Universal Serial Bus interface.

5. The hardware wallet dongle of claim 1 , wherein the second communication interface is a wireless interface.

6. The hardware wallet dongle of claim 1, wherein the hardware wallet dongle does not include a screen display.

7. The hardware wallet dongle of claim 1, wherein the hardware wallet dongle does not include a human-readable interface.

8. The hardware wallet dongle of claim 1, wherein the first authentication message comprises confirmation of a user's identity by at least one biometric sensor.

9. A secure browser extension crypto wallet system for ensuring the security of cryptocurrency transactions in a browser extension wallet, the system comprising: A hardware wallet dongle, the hardware wallet dongle comprising: a secure element configured to protect a user's private key; a first communication interface that connects the hardware wallet dongle in electronic communication with a browsing device running the browser extension wallet; and a second communication interface, the second communication interface connecting the hardware wallet dongle to the authentication device by electronic communication, wherein the first communication interface and the second communication interface are both connected to the security element, wherein in response to a first authentication message from the authentication device being received by the second communication interface and verified as authentic by the secure element, the secure element signs a transaction and transmits the signed transaction to the first communication interface for provision to the browser extension wallet; the browsing device, the browsing device being configured to run the browser extension wallet, wherein the browsing device is connected to a network capable of accessing a blockchain to write the signed transaction to the blockchain; and A smartphone configured to run a smartphone application including the authentication device, wherein the authentication device includes a sensor, and wherein the first authentication message is an authentication of the identity of the user by the sensor.

10. The secure browser extension crypto wallet system of claim 9, wherein the sensor is a fingerprint sensor.

11. The secure browser extension crypto wallet system of claim 9, wherein the sensor is a facial recognition sensor.

12. The secure browser extension crypto wallet system of claim 9, wherein the browsing device is a commodity PC.

13. The secure browser extension crypto wallet system of claim 9, wherein the sensor is a touch screen for entering a PIN code.

14. The secure browser extension crypto wallet system of claim 9, wherein the first communication interface is a wired interface.

15. The secure browser extension crypto wallet system of claim 14, wherein the wired interface is a Universal Serial Bus interface.

16. The secure browser extension crypto wallet system of claim 9, wherein the second communication interface is a wireless interface.

17. The secure browser extension crypto wallet system of claim 9, wherein the hardware wallet dongle does not include a screen display.

18. The secure browser extension crypto wallet system of claim 9, wherein the hardware wallet dongle does not include a human readable interface.

19. A method of performing cryptocurrency transactions using a secure browser extension crypto wallet system for securing cryptocurrency transactions in a browser extension wallet, the method comprising: Sending the cryptocurrency transaction by the browser extension wallet running on the browser device to a hardware wallet dongle connected to the browser device via a first communication interface; receiving, by a secure element of the hardware wallet dongle, the cryptocurrency transaction, parsing the cryptocurrency transaction, and generating a visible representation of the cryptocurrency transaction; sending, by the secure element, the visible representation to a second communication interface wirelessly connectable to an authentication device; receiving, by the security element, a first authentication message from the second communication interface, the first authentication message corresponding to verification of a user identity by the authentication device; In response to the first authentication message, signing, by the secure element, the cryptocurrency transaction; as well as The signed cryptocurrency transaction is transmitted by the secure element to the browser extension wallet via the first communication interface to write the signed cryptocurrency transaction to a blockchain by the browser extension wallet.

20. The method of claim 19, wherein the visible representation includes a transaction amount and a recipient address.

Images