US20150262171A1 - Bitcoin private key splitting for cold storage - Google Patents
Bitcoin private key splitting for cold storageDownload PDFInfo
- Publication number
- US20150262171A1 US20150262171A1US14/660,331US201514660331AUS2015262171A1US 20150262171 A1US20150262171 A1US 20150262171A1US 201514660331 AUS201514660331 AUS 201514660331AUS 2015262171 A1US2015262171 A1US 2015262171A1
- Authority
- US
- United States
- Prior art keywords
- bitcoin
- vault
- processor
- wallet
- private key
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/04—Payment circuits
- G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
- G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/04—Payment circuits
- G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
- G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
- G06Q20/0658—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash e-cash managed locally
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/16—Payments settled via telecommunication systems
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
- G06Q20/363—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes with the personal data of a user
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
- G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
- G06Q20/3678—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes e-cash details, e.g. blinded, divisible or detecting double spending
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/381—Currency conversion
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3825—Use of electronic signatures
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/384—Payment protocols; Details thereof using social networks
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/386—Payment protocols; Details thereof using messaging services or messaging apps
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/388—Payment protocols; Details thereof using mutual authentication without cards, e.g. challenge-response
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for transactions
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
- H04L51/08—Annexed information, e.g. attachments
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q2220/00—Business processing using cryptography
Definitions
- This inventionrelates to a computer system and method for transacting bitcoin.
- the Bitcoin networkis a peer-to-peer payment system having a plurality of nodes that are connected to one another.
- Bitcoin exchange computer systemsallow for users to exchange local currency into or out of bitcoin. Users send payments by broadcasting digitally signed messages to the Bitcoin network. Users may, for example, send and receive payments using mobile applications on mobile devices, client software or a web browser.
- Bitcoin addressis derived from the public portion of one or more cryptographic key pairs. The private portion of a key pair is not disclosed to the public.
- a userbroadcasts a payment message that is digitally signed with the associated private key.
- minersat miner computer systems verify and timestamp transactions into a shared public database called a “block chain”. The miners are rewarded with transaction fees and newly minted bitcoin for their effort.
- the miner computer systemsare specialized computers that append blocks of transactions to the block chain. Solving a cryptographic puzzle required to append a block carries a reward plus fees included in transactions in the block.
- Host computer systemsreside at various nodes and may host accounts or “wallets” that allow users to make and accept payments using bitcoin.
- the walletstores the public key of the Bitcoin address and its associated private key.
- the transfer of Bitcoinmay be an onerous task if the entire public key of the Bitcoin address has to be copied and transmitted.
- a merchant computer systemoften has an online store and a website.
- a customer at a customer computer systemmay use a browser to access the online store via the website.
- Itemsare displayed for purchase in a local currency.
- Exchange rate between Bitcoin and local currencychanges over short periods of time. The price in local currency may thus change between the time that the local currency is displayed to the customer and the time that the customer decides to make the purchase.
- the customer or the merchantmay incur a loss in local currency.
- the customer or merchantmay then be reluctant to purchase using bitcoin.
- the usermay log into their account through the website using a user name and password. If the user name and password become compromised then it may be possible for bitcoin to be stolen out of the wallet. Users may therefore be reluctant to store bitcoin in their wallets without any additional security features.
- Bitcoin transactingrequires the use of a public key and a private key.
- the private keyis used to sign an authorization and the public key is used to verify the signature.
- Some usersmay require control over their private keys in order to ensure to such users that bitcoin transacting will not take place without their express authorization.
- the inventionprovides a host computer system for transacting bitcoin including a processor, a network interface device connected to the processor, a computer readable medium connected to the processor, a data store on the computer readable medium and a set of instructions on the computer readable medium that are executable by the processor.
- the set of instructionsincludes a wallet establishment module, a login module, a hosted email module and a wallet management.
- the wallet establishment moduleestablishes a first wallet in the data store, stores login details for the first wallet and storing a value representative of an amount of bitcoin held by the first wallet.
- the login modulereceives login credentials over the network interface device for the first wallet from a first user device, verifies whether the login credentials match the login details for the first wallet, and if the login credentials match the login details then logs the first user device into the first wallet.
- the hosted email moduleif the first user device is logged into the wallet, permits transmission of an email by a user of the first user device to an email address of a second user device.
- the wallet management modulein response to the transmission of the email, records a transfer in the first wallet for an amount of bitcoin from the first wallet to a second wallet identified by the email address.
- the inventionalso provides a method of transacting bitcoin.
- a processorestablishes a first wallet in a data store connected to the processor.
- the processorstores login details for the first wallet.
- the processorstores a value representative of an amount of bitcoin held by the first wallet.
- the processorreceives login credentials for the first wallet from a first user device.
- the processorverifies whether the login credentials match the login details for the first wallet.
- the processorif the login credentials match the login details then, logs the first user device into the first wallet.
- the processorif the first user device is logged into the wallet, permits transmission of an email by a user to the first user device to an email address of a second user device and in response to the transmission of the email.
- the processorrecords a transfer in the first wallet for an amount of bitcoin from the first wallet to a second wallet identified by the email address.
- the inventionfurther provides a non-transitory computer-readable medium having stored thereon a set of instructions that are executable by a processor to carry out a method of transacting bitcoin.
- the processorestablishes a first wallet in a data store connected to the processor.
- the processorstores login details for the first wallet.
- the processorstores a value representative of an amount of bitcoin held by the first wallet.
- the processorreceives login credentials for the first wallet from a first user device.
- the processorverifies whether the login credentials match the login details for the first wallet.
- the processorif the login credentials match the login details then, logs the first user device into the first wallet.
- the processorif the first user device is logged into the wallet, permits transmission of an email by a user to the first user device to an email address of a second user device and in response to the transmission of the email.
- the processorrecords a transfer in the first wallet for an amount of bitcoin from the first wallet to a second wallet identified by the email address.
- the inventionfurther provides a first host computer system for transacting bitcoin including a processor at a first node of the Bitcoin network, a network interface device connected to the processor, a computer readable medium connected to the processor, a data store on the computer readable medium and a set of instructions on the computer readable medium that are executable by the processor.
- the set of instructionsincludes a wallet establishment module.
- the wallet establishment moduleestablishes a first and second wallets in the data store and stores a value representative of an amount of bitcoin held by the first wallet.
- the wallet management modulereceives, over the network interface device, a first transfer instruction for an amount of bitcoin from the first wallet and an identifier of the second wallet, in response to the first transfer instruction, records a transfer in the first wallet for the amount of bitcoin in the first transfer instruction out of the first wallet and a transfer in the second wallet, identified by the identifier of the second wallet, for the amount of bitcoin in the first transfer instruction into the second wallet without paying a miner's fee for the first transfer.
- the wallet management modulereceives, over the network interface device, a second transfer instruction for an amount of Bitcoin from the first wallet and a bitcoin address associated with a second node of the Bitcoin network, and in response to the second transfer instruction, records a transfer in the first wallet for the amount of bitcoin in the second transfer instruction out of the first wallet, broadcasts a message to the Bitcoin network, including to the second node, to record a transfer associated with the bitcoin address associated with the second node, for the amount of bitcoin in the second transfer instruction, and pays a miner's fee for the second transfer.
- the inventionfurther provides a method of transacting bitcoin including.
- a processor of a first host computer system at a first node of the Bitcoin networkestablishes first and second wallets in a data store connected to the processor.
- the processorstores a value representative of an amount of bitcoin held by the first wallet.
- the processorreceives a first transfer instruction for an amount of bitcoin from the first wallet and an identifier of the second wallet.
- the processorin response to the first transfer instruction, records a transfer in the first wallet for the amount of bitcoin in the first transfer instruction out of the first wallet and a transfer in the second wallet, identified by the identifier of the second wallet, for the amount of bitcoin in the first transfer instruction into the second wallet without paying a miner's fee for the first transfer.
- the processorreceives a second transfer instruction for an amount of bitcoin from the first wallet and a bitcoin address associated with a second node of the bitcoin network.
- the processorin response to the second transfer instruction records a transfer in the first wallet for the amount of bitcoin in the second transfer instruction out of the first wallet, broadcasts a message to the Bitcoin network, including to the second node, to record a transfer associated with the bitcoin address associated with the second node, for the amount of bitcoin in the second transfer instruction and pays a miner's fee for the second transfer.
- the inventionfurther provides a non-transitory computer-readable medium having stored thereon a set of instructions that are executable by a processor of a first host computer system at a first node of the Bitcoin network to carry out a method of transacting bitcoin.
- the processorestablishes first and second wallets in a data store connected to the processor.
- the processorstores a value representative of an amount of bitcoin held by the first wallet.
- the processorreceives a first transfer instruction for an amount of bitcoin from the first wallet and an identifier of the second wallet.
- the processorin response to the first transfer instruction, records a transfer in the first wallet for the amount of bitcoin in the first transfer instruction out of the first wallet and a transfer in the second wallet, identified by the identifier of the second wallet, for the amount of bitcoin in the first transfer instruction into the second wallet without paying a miner's fee for the first transfer.
- the processorreceives a second transfer instruction for an amount of bitcoin from the first wallet and a bitcoin address associated with a second node of the bitcoin network.
- the processorin response to the second transfer instruction records a transfer in the first wallet for the amount of bitcoin in the second transfer instruction out of the first wallet, broadcasts a message to the Bitcoin network, including to the second node, to record a transfer associated with the Bitcoin address associated with the second node, for the amount of bitcoin in the second transfer instruction and pays a miner's fee for the second transfer.
- the inventionalso provides a host computer system for transacting bitcoin including a processor, a computer readable medium connected to the processor, a local storage on the computer readable medium and a set of instructions on the computer readable medium that are executable by the processor.
- the set of instructionsincludes a register, a Bitcoin address and an associated private key and value stored in the register, a local controller, a splitter, an offline distribution module, at least one restoration interface, and an assembler.
- the local controllertransfers a private key for a Bitcoin address of a vault, to a local storage connected to a processor and transfers the value of the Bitcoin address in the register to the vault.
- the splittersplits the private key of the Bitcoin address of the vault into a plurality of codes.
- the offline distribution moduledistributes the codes to remote distributed storage locations, removes the private key of the Bitcoin address of the vault from the local storage, and removes the value for the Bitcoin address of the register from the Bitcoin address of the register.
- the restoration interfacereceives at least some of the codes into which the private key for Bitcoin address of the vault has been split.
- the assemblerassembles the codes that have been received into the private key of the Bitcoin address of the vault.
- the local controllerrestores the private key of the Bitcoin address of the vault from the local storage, and restores the value for the Bitcoin address in the register from the vault.
- the inventionfurther provides a method of transacting bitcoin.
- a processortransfers a private key of the Bitcoin address of a vault to a local storage connected to the processor.
- the processorsplits the private key of the Bitcoin address of the vault into a plurality of codes.
- the processordistributes the codes to remote distributed storage locations.
- the processortransfers a value of a Bitcoin address in a register to the vault.
- the processorreceives at least some of the codes into which the private key of the Bitcoin address of the vault has been split.
- the processorassembles the codes that have been received into the private key of the Bitcoin address of the vault.
- the processorrestores the private key of the Bitcoin address of the vault to the vault.
- the processorrestores the value of the Bitcoin address in the register from the vault.
- the inventionalso provides a non-transitory computer-readable medium having stored thereon a set of instructions that are executable by a processor to carry out a method of transacting bitcoin.
- a processortransfers a private key of the Bitcoin address of a vault to a local storage connected to the processor.
- the processorsplits the private key of the Bitcoin address of the vault into a plurality of codes.
- the processordistributes the codes to remote distributed storage locations.
- the processortransfers a value of a Bitcoin address in a register to the vault.
- the processorreceives at least some of the codes into which the private key of the Bitcoin address of the vault has been split.
- the processorassembles the codes that have been received into the private key of the Bitcoin address of the vault.
- the processorrestores the private key of the Bitcoin address of the vault to the vault.
- the processorrestores the value of the Bitcoin address in the register from the vault.
- the inventionfurther provides a host computer system for transacting bitcoin including a processor, a network interface device connected to the processor, a computer readable medium connected to the processor, a local storage on the computer readable medium and a set of instructions on the computer readable medium that are executable by the processor.
- the set of instructionsincludes a wallet, a plurality of Bitcoin addresses stored in the wallet, a first vault, and a local controller.
- the local controlleris executable for selecting a first transfer set of the Bitcoin addresses for cold storage in the first vault, transferring at least a portion of each of the Bitcoin addresses of the first transfer set to a first vault while keeping the portions a first transaction set in the register, and restoring at least the portion of the Bitcoin addresses of the first transfer set from the first vault to the wallet and a wallet management module transacting using the Bitcoin addresses of the first transacting set without permitting transacting with the Bitcoin addresses of the first transfer set due to the portions thereof being restored to the first vault, and transacting using the Bitcoin addresses of the first transfer set due to the portions thereof being restored from the first vault to the wallet.
- the inventionalso provides a method of transacting bitcoin.
- a processorstores a plurality of Bitcoin addresses in a wallet.
- the processorselects a first transfer set of the Bitcoin addresses for cold storage in a first vault.
- the processortransfers at least a portion of each of the Bitcoin addresses of the first transfer set to the first vault while keeping the portions a first transaction set in the register.
- the processortransacts using the Bitcoin addresses of the first transacting set without permitting transacting with the Bitcoin addresses of the first transfer set due to the portions thereof being transferred to the first vault.
- the processorrestores the portion of the Bitcoin addresses of the first transfer set from the first vault to the wallet.
- the processortransacts using the Bitcoin addresses of the first transfer set due to the portions thereof being restored from the first vault to the wallet.
- the inventionfurther provides a non-transitory computer-readable medium having stored thereon a set of instructions that are executable by a processor to carry out a method of transacting.
- a processorstores a plurality of Bitcoin addresses in a wallet.
- the processorselects a first transfer set of the Bitcoin addresses for cold storage in a first vault.
- the processortransfers at least a portion of each of the Bitcoin addresses of the first transfer set to the first vault while keeping the portions a first transaction set in the register.
- the processortransacts using the Bitcoin addresses of the first transacting set without permitting transacting with the Bitcoin addresses of the first transfer set due to the portions thereof being transferred to the first vault.
- the processorrestores the portion of the Bitcoin addresses of the first transfer set from the first vault to the wallet.
- the processortransacts using the Bitcoin addresses of the first transfer set due to the portions thereof being restored from the first vault to the wallet.
- the inventionalso provides a method of effecting payment including receiving, by a host computer system, a request for payment from a merchant computer system, including an amount in a currency, determining, by the host computer system, a first exchange rate, wherein the first exchange rate fluctuates and the first exchange rate is determined at a first moment in time, converting, by the host computer system, the amount in the currency to an amount in bitcoin using the first exchange rate at the first moment in time, receiving, by the host computer system, a send instruction from the customer computer system, wherein the send instruction is at a second moment in time later than the first moment in time and the exchange rate at the second moment in time is a second exchange rate that is different than the first exchange rate at the first moment in time, receiving, by the host computer system, payment in bitcoin from the customer in an amount that is based on the amount in bitcoin and transmitting, by the host computer system, in response to receiving the send instruction from the customer computer system, a payment instruction to pay currency to the merchant, wherein the currency paid to the merchant is for an amount that is at
- the inventionfurther provides a host computer system for effecting payment including a processor, a computer readable medium connected to the processor and a set of instructions on the computer readable medium that are executable by the processor.
- the set of instructionsincludes an application programmable interface (API) receiving a request for payment from a merchant computer system, including an amount in a currency, a currency converter determining a first exchange rate, wherein the first exchange rate fluctuates and the first exchange rate is determined at a first moment in time, and converting, by the host computer system, the amount in the currency to an amount in bitcoin using the first exchange rate at the first moment in time, transaction processor receiving a send instruction from the customer computer system, wherein the send instruction is at a second moment in time later than the first moment in time and the exchange rate at the second moment in time is a second exchange rate that is different than the first exchange rate at the first moment in time, and receiving a payment in bitcoin from the customer in an amount that is based on the amount in bitcoin and a bank transfer module transmitting in response to receiving the send instruction
- the inventionalso provides a non-transitory computer-readable medium having stored thereon a set of instructions that are executable by a processor to carry out a method of transacting bitcoin including receiving, by a host computer system, a request for payment from a merchant computer system, including an amount in a currency, determining, by the host computer system, a first exchange rate, wherein the first exchange rate fluctuates and the first exchange rate is determined at a first moment in time, converting, by the host computer system, the amount in the currency to an amount in bitcoin using the first exchange rate at the first moment in time, receiving, by the host computer system, a send instruction from the customer computer system, wherein the send instruction is at a second moment in time later than the first moment in time and the exchange rate at the second moment in time is a second exchange rate that is different than the first exchange rate at the first moment in time, receiving, by the host computer system, payment in bitcoin from the customer in an amount that is based on the amount in bitcoin and transmitting, by the host computer system, in response to receiving the send instruction
- the inventionfurther provides a method of managing bitcoin, including establishing, by a host computer system, a vault and storing first and second electronic communication addresses in relation to the vault, storing, by the host computer system, bitcoin in the vault, receiving, by the host computer system, a request to transfer an amount of the bitcoin out of the vault, transmitting, by the host computer system, in response to the request, first and second messages over a network to the first and second addresses, detecting, by the host computer system, whether first and second authorization instructions are received due to one or more users reacting to the first and second messages sent to the first and second addresses and transferring, by the host computer system, the amount of bitcoin out of the vault only if both the first and second authorization instructions are detected.
- the inventionalso provides a non-transitory computer-readable medium having stored thereon a set of instructions which, when executed by a processor, executes a method including establishing, by a host computer system, a vault and storing first and second electronic communication addresses in relation to the vault, storing, by the host computer system, bitcoin in the vault, receiving, by the host computer system, a request to transfer an amount of the bitcoin out of the vault, transmitting, by the host computer system, in response to the request, first and second messages over a network to the first and second addresses, detecting, by the host computer system, whether first and second authorization instructions are received due to one or more users reacting to the first and second messages sent to the first and second addresses and transferring, by the host computer system, the amount of bitcoin out of the vault only if both the first and second authorization instructions are detected.
- the inventionfurther provides a bitcoin management system, including a processor, a computer-readable medium connected to the processor and a set of instructions on the computer readable medium that are executable by the processor.
- the set of instructionsincludes a vault establishment wizard establishing a vault and storing first and second electronic communication addresses in relation to the vault, transaction processor storing bitcoin in the vault and a vault management module receiving a request to transfer an amount of the bitcoin out of the vault, transmitting, in response to the request, first and second messages over a network to the first and second addresses, detecting whether first and second authorization instructions are received due to one or more users reacting to the first and second messages sent to the first and second addresses, and instructing the transaction processor to transfer the amount of bitcoin out of the vault only if both the first and second authorization instructions are detected.
- the inventionalso provides a method of transacting bitcoin including storing, by a host computer system, a public key, receiving, by the host computer system, a request from a user computer system to transact using a bitcoin address, transmitting, by the host computer system, a verification script to the user computer system, the verification script including an authorization and a signature algorithm that is executable on the user computer system to sign the authorization with a private key to obtain a signed authorization that includes the signature and transmit the signed authorization to the host computer system, receiving, by the host computer system, the signed authorization including the signature from the user computer system, verifying, by the host computer system, the signature of the signed authorization received from the user computer system using a public key; and transacting, by the host computer system, with the bitcoin address, the transacting being permitted due to a successful verification of the signature but not upon an unsuccessful verification of the signature.
- the inventionfurther provides a host computer system including a processor, a set of data and instructions on the computer-readable medium that are executable by the processor that are executable by the processor, a public key, a transaction processor receiving a request from a user computer system to transact using a bitcoin address, a verification script that is transmitted to the user computer system, the verification script including an authorization and a signature algorithm that is executable on the user computer system to sign the authorization with a private key to obtain a signed authorization that includes the signature and transmit the signed authorization to the host computer system, the host computer system receiving the signed authorization including the signature from the user computer system, and a verification module verifying the signature of the signed authorization received from the user computer system using a public key, the transaction processor transacting with the bitcoin address, the transacting being permitted due to a successful verification of the signature but not upon an unsuccessful verification of the signature.
- a host computer systemincluding a processor, a set of data and instructions on the computer-readable medium that are executable by the processor that are executable by the processor, a public
- the inventionalso provides a host computer system including a processor, a network interface device connected to the processor, a computer readable medium connected to the processor and a set of instructions on the computer readable medium that are readable and executable by the processor.
- the set of instructionsinclude an embedded code generator generating an embedded code for inclusion within a website of a partner computer system, the embedded code including a startup caller causing transmission of a startup call from the sender computer system to the host computer system, a startup call responder receiving the startup call from the sender computer system and transmitting, in response to the startup call, a tip button and a session script to the sender computer system, the session script being executable by the sender computer system to transmit a session call to the host computer system and a session responder transmitting, in response to the session call, at least one payment button and a payment script to the sender computer system, the payment button being selectable by the user of the sender computer system to execute the payment script, the payment script transmitting an instruction to a transaction processor to transfer funds from a send
- the inventionfurther provides a method of transferring funds including generating, by a host computer system, an embedded code for inclusion within a website of a partner computer system, the embedded code including a startup caller causing transmission of a startup call from the sender computer system to the host computer system, receiving, by the host computer system, the startup call from the sender computer system, transmitting, by the host computer system in response to the startup call, a tip button and a session script to the sender computer system, the session script being executable by the sender computer system to transmit a session call to the host computer system and transmitting, by the host computer system in response to the session call, at least one payment selection and a payment script to the sender computer system, the payment selection being selectable by the user of the sender computer system to execute the payment script, the payment script transmitting an instruction to a transaction processor to transfer funds from a sender account to a receiver account.
- the embedded codeincluding a startup caller causing transmission of a startup call from the sender computer system to the host computer system, receiving, by
- the inventionalso provides a method of transacting bitcoin including executing, by a host computer system, a trading algorithm, including receiving sell offers for bitcoin from a sellers, receiving a buy offers for bitcoin from a buyers, creating respective matches wherein each match includes one of the buy offers and one of the sell offers, broadcasting each respective match over a multicast pipeline, receiving each respective match with a clearing module and clearing the respective match by updating an exchange database to reflect the respective match by transferring a representation of bitcoin from the seller to the buyer and transferring a representation of currency from the buyer to the seller.
- a trading algorithmincluding receiving sell offers for bitcoin from a sellers, receiving a buy offers for bitcoin from a buyers, creating respective matches wherein each match includes one of the buy offers and one of the sell offers, broadcasting each respective match over a multicast pipeline, receiving each respective match with a clearing module and clearing the respective match by updating an exchange database to reflect the respective match by transferring a representation of bitcoin from the seller to the buyer and transferring a representation of currency from the buyer to the seller.
- the inventionfurther provides a system for transacting bitcoin including an order gateway receiving sell offers for bitcoin from a sellers and receiving a buy offers for bitcoin from a buyers, a matching engine creating respective matches wherein each match includes one of the buy offers and one of the sell offers, a multicast pipeline, the matching engine broadcasting each respective match over the multicast pipeline, an exchange database; and a clearing module receiving each respective and clearing the respective match by updating the exchange database to reflect the respective match by transferring a representation of bitcoin from the seller to the buyer and transferring a representation of currency from the buyer to the seller, thereby executing a trading algorithm.
- FIG. 1Ais a block diagram of a network environment that includes the Bitcoin network and a number of systems forming part thereof or connected thereto;
- FIG. 1Bis a block diagram of a first host computer system and a first and second user devices connected thereto;
- FIG. 2is diagrammatic view of a first wallet that is held within a first host computer system in FIG. 1 ;
- FIG. 3is a view similar to FIG. 2 , further illustrating a second wallet that has been established within the first host computer system;
- FIG. 4is a view of an email that is received by the second user device in FIG. 1 ;
- FIG. 5is a view of a browser displaying a user interface with fields for creating login details for the second wallet;
- FIGS. 6 to 30are views similar to FIG. 5 that step a user of the second user device through a wallet set up;
- FIGS. 31 to 33are views of the browser wherein the user interface discloses various tools that can be used by the user;
- FIGS. 34 to 37are views of the browser wherein the user interface is used by the user to purchase bitcoin from the first host computer system;
- FIG. 38is an email that is received by the second user device to confirm the purchase of the bitcoin from the first host computer system
- FIG. 39is an email that is received by the second user device with a notification that bitcoin has been added to their wallet as part of a referral bonus system
- FIG. 40is a view of the browser wherein the user interface displays “Limits and Verifications” associated with the second wallet;
- FIG. 41is a view similar to FIG. 3 displaying transfer of bitcoin from the second wallet to the first wallet;
- FIGS. 42 and 43are views of the browser when the user interface steps the user through the transfer of Bitcoin from the second wallet to the first wallet;
- FIG. 44is a view of the browser wherein the user interface displays Bitcoin addresses associated with transactions that have been completed;
- FIG. 45is a view similar to FIG. 40 further showing the transfer of bitcoin from the second wallet to a third wallet that is connected to a second host computer system;
- FIG. 46is a block diagram illustrating splitting of a private key of a vault and offline distribution
- FIG. 47is a block diagram illustrating removal of the private key of the vault.
- FIG. 48is a block diagram illustrating offline or “cold” storage of values of Bitcoin addresses of a wallet in the vault
- FIG. 49is a block diagram illustrating isolation of the vault with its private key removed
- FIG. 50is a block diagram illustrating how the private key of the vault and the value of the Bitcoin addresses are restored
- FIGS. 51 a to 51 dare block diagrams that illustrate how values of certain Bitcoin addresses in a wallet are removed and others are maintained;
- FIG. 52is a graph illustrating how the wallet is maintained within a range so that only a portion of the wallet is “hot” in the sense that a user of the wallet can use the “hot” portion for transacting with another user;
- FIG. 53is a block diagram that shows how an intermediate hot wallet is used to collect value from multiple wallets before transfer to a vault
- FIG. 54is a block diagram of a network environment that includes a customer computer system and merchant computer system;
- FIG. 55is a block diagram illustrating functioning for purposes of locking an exchange rate in when processing a transaction made by the customer computer system on the merchant computer system in FIG. 54 ;
- FIG. 56is a flow chart illustrating the establishment of a personal vault
- FIG. 57is a flow chart illustrating how bitcoin is transferred into and out of the vault
- FIG. 58is a block diagram of the first host computer system illustrating components that are used for establishing the vault and transferring bitcoin into and out of the vault;
- FIG. 59is an email that is transmitted to verify a secondary email address
- FIG. 60is a view of a browser wherein a user interface displays options for transferring bitcoin out of a vault
- FIGS. 61 and 62are emails that are transmitted to primary and secondary email addresses to approve a withdrawal
- FIG. 63is a view of the browser with the user interface displaying a transaction status window
- FIG. 64is a block diagram illustrating the establishment of a user-controlled vault
- FIG. 65is a block diagram illustrating the user of the user-controlled vault for authorizing a transaction
- FIG. 66is a block diagram of an address generator that is used by the user-controlled vault.
- FIG. 67 to FIG. 71are a block diagrams illustrating the functioning of a tip button
- FIG. 72is a block diagram of a system for transacting bitcoin according to an embodiment of the invention.
- FIGS. 73 a to 73 fillustrate the use of the system of FIG. 72 for executing transfer-in, trading and withdrawal algorithms
- FIG. 74is a block diagram of a machine in the form of a computer system forming part of the network environment.
- FIG. 1A of the accompanying drawingsillustrates a network environment 10 , including the Bitcoin network 12 , a first host computer system 14 within which the invention manifests itself, a second host computer system 16 , first and second user devices 18 and 20 connected over the Internet 22 to the first host computer system 14 , a third user device 24 connected to the second host computer system 16 , a bitcoin exchange computer system 26 and a miner computer system 28 .
- the Bitcoin network 12includes a host node 30 and a plurality of remote nodes 32 A to D that are connected to one another.
- the first host computer system 14is connected to the host node 30 .
- the bitcoin exchange computer system 26is connected to the remote node 32 A.
- the second host computer system 16is connected to the remote node 32 B.
- the miner computer system 28is connected to the remote node 32 D or could reside on the same computer system.
- the first host computer system 14is used primarily for transacting bitcoin and, as shown in FIG. 1B , includes a website 34 having a user interface 36 , a login module 38 , a wallet establishment module 40 , a plurality of wallets 42 , a wallet management module 44 and a hosted email module 46 .
- the login module 38is connected to the website 34 and the hosted email module 46 is connected to the login module 38 .
- the wallet establishment module 40is connected to the wallets 42 .
- the hosted email module 46is connected via the wallet management module 44 to the wallets 42 .
- the first user device 18is connected over the Internet 22 and the user interface 36 to the login module 38 .
- the hosted email module 46is connected over the Internet 22 to the second user device 20 and the second user device 20 is connected over the Internet 22 and the user interface 36 to the wallet establishment module 40 .
- the first host computer system 14already has one wallet (Wallet A) stored among the wallets 42 corresponding to the first user device 18 .
- the first wallet (Wallet A)includes an email address (email address A) and login details for the wallet.
- the first wallet (Wallet A)also includes a number of Bitcoin addresses (Bitcoin address 1; Bitcoin address 2) that have been created due to respective transfers or purchases (Transfer 1; Transfer 2).
- the first Bitcoin address (Bitcoin address 1)is created due to a purchase (Transfer 1) from a master wallet of the first host computer system 14 (First Host) and is recorded for a value in an amount in bitcoin.
- the second Bitcoin address(Bitcoin address 2) is created due to a transfer (Transfer 2) from another location within the Bitcoin network 12 having a network address outside of the first host computer system 14 and is recorded for a particular amount in bitcoin.
- the first wallet(Wallet A) was originally established by the wallet establishment module 40 in FIG. 1B .
- the email address (email address A) and login details of the first walletwere also recorded by the wallet establishment module 40 .
- the wallet establishment module 40 and wallet management module 44were used to record the transfers and purchases (Transfer 1; Transfer 2), their Bitcoin addresses (Bitcoin address 1; Bitcoin address 2), their values and other details within the wallet.
- a user of the first user device 18 in FIG. 1Bmay use a mobile application on the first user device 18 to communicate over the Internet 22 directly with the login module 38 or may use a browser on the first user device 18 to communicate via the Internet 22 and the website 34 with the login module 38 .
- a browser application on the first user device 18transmits a user interface request over the Internet 22 to the website 34 .
- the website 34responds to the user interface request by transmitting the user interface 36 over the Internet 22 to the first user device 18 .
- the user interface 36is then displayed on the first user device 18 .
- the user interface 36includes fields for entering login credentials, which are then transmitted from the first user device 18 over the Internet 22 to the login module 38 .
- the login module 38verifies whether the login credentials match the login details for the wallet (Wallet A). If the login credentials match the login details, then the login module 38 logs the first user device 18 into the wallet (Wallet A) in FIG. 2 . If the login credentials do not match the login details, then the first user device 18 is not logged
- the login module 38also provides access for the first user device 18 to the hosted email module 46 and transmission of an email by a user of the first user device 18 to an email address of the second user device 20 .
- the user interface 36provides a field for entering the email address of the second user device 20 .
- the user interface 36also includes a field for entering an amount in bitcoin (or an amount in local currency that is converted to bitcoin using an exchange rate) that is being transferred from the wallet (Wallet A) corresponding to the first user device 18 to a respective wallet among the wallets 42 corresponding to the second user device 20 that has not yet been established at this point in time.
- the user of the first user device 18then uses the hosted email module 46 to send an email at 50 to the second user device 20 .
- the hosted email module 46simultaneously at 52 instructs the wallet establishment module 40 to establish a wallet corresponding to the email address within the wallets 42 .
- the hosted email module 46simultaneously instructs the wallet management module 44 to record the amount of bitcoin that is being transferred from the wallet (Wallet A) within the wallet corresponding to the email address.
- FIG. 3illustrates further activity within the wallets 42 due to the email represented by a third transfer (Transfer 3).
- the systemuses an existing Bitcoin address (Bitcoin address 2) to which the outgoing transfer is charged.
- Associated with the transfer (Transfer 3)are the email address to which the email has been transmitted, the amount in bitcoin, a miner's fee of zero bitcoin that is paid by the first host computer system 14 to any miner computer system such as the miner computer system 28 in FIG. 1A , and a host fee of zero bitcoin that are charged to the wallet (Wallet A) for the transfer.
- a second wallet (Wallet B)is established by the wallet establishment module 40 and the email address (email address B) of the second user device 20 is recorded as an identifier of the wallet (Wallet B).
- a Bitcoin address (Bitcoin address 3)is recorded within the second wallet (Wallet B) for the transfer (Transfer 3).
- the transfer (Transfer 3)has the Bitcoin address (Bitcoin address 3), the identifier of the wallet (Wallet A) from where the funds are transferred associated therewith, and the amount in bitcoin that has been transferred.
- the amount in bitcoin corresponding to the transfer (Transfer 3) of both wallets (Wallet A; Wallet B)is the same, consistent with double entry accounting principles.
- the second wallet (Wallet B)so far has no login details or any other user information and has not been accessed by a user of the second user device 20 at this point in time.
- FIG. 4illustrates the email when it is received at the second user device 20 in FIG. 1B .
- the emailis received and viewed within an email application on the second user device 20 .
- the emailincludes a link (“Click here to sign in and claim this amount”) that, when selected by the user of the second user device 20 , transmits a user interface request from the browser on the second user device 20 over the Internet 22 to the website 34 .
- the website 34responds to the user interface request to transmit the user interface 36 over the Internet 22 to the second user device 20 for viewing within the browser.
- FIG. 5illustrates the user interface 36 as displayed on the second user device 20 in FIG. 1B .
- the user interface 36includes a plurality of fields for the user of the second user device 20 to enter login details for the second wallet (Wallet B), including a password and a confirmation of the password. After the user has entered a password, the user can access their wallet by selecting the button “Access My Wallet”.
- the wallet establishment module 40 in FIG. 1Bstores the login credentials in association with the second wallet (Wallet B).
- the login module 38also logs the second user device 20 into the second wallet (Wallet B).
- the usercan be provided with a login page where the user can enter login credentials that are compared with the login details in the second wallet (Wallet B) and then log into the second wallet (Wallet B) following a favorable match between the login credentials and the login details.
- FIG. 6shows a view that is displayed on the second user device 20 in FIG. 1B .
- the useris already logged into the wallet, as shown in the top right.
- the usercan accept or decline an agreement.
- FIG. 7displays the first page that is displayed to the user following acceptance of the agreement.
- the pageshows the current balance corresponding to the amount of Bitcoin at the Bitcoin address (Bitcoin address 4) in FIG. 3 .
- the usercan select various tools down the left margin, including sending or requesting bitcoin, buying or selling bitcoin, account settings and various merchant tools.
- FIG. 8illustrates a view that is displayed to the user if the user selects the “Buy/Sell” link in FIG. 7 .
- the useris prompted to add a bank account.
- FIGS. 9 through 15step the user through the entry of bank account details and verification of the bank account.
- the usercan also select a credit card as a backup payment.
- FIGS. 16 to 19step the user through the entry of a credit card number and a billing address
- FIGS. 20 and 21step the user through a verification process to verify that the user is in control of the credit card account.
- FIGS. 22 and 23request additional information from the user.
- FIG. 23also allows the user to verify a phone at a phone number and FIGS. 24 through 27 step the user through a process for verifying their phone and phone number.
- FIGS. 28 through 30illustrate a process for verifying an identity of the user of the second user device 20 .
- the top margin within the account settingsallow for additional tools such as referrals ( FIG. 31 ), viewing of Bitcoin addresses ( FIG. 32 ), and integration with an application programmable interface ( FIG. 33 ).
- FIG. 34illustrates a process that is initiated by the user to purchase bitcoin from a wallet of the first host computer system 14 .
- the userselects one (1) bitcoin (BTC) to purchase.
- FIGS. 35 and 36step the user through the process of purchasing the bitcoin. Once the bitcoin is purchased, the user can select on “History” tab in the top margin to display a view as shown in FIG. 37 wherein the transaction is displayed and is marked as “PENDING”.
- FIG. 38shows an email that is transmitted by the hosted email module 46 in FIG. 1B to the second user device 20 to confirm the purchase of the bitcoin following selection of a “Confirm” button in FIG. 35 .
- the emailalso has a link that, when selected by the user, opens the browser on the second user device 20 and allows the user to login to their wallet and view the transaction.
- FIG. 39shows an email that is transmitted by the hosted email module 46 in FIG. 1B to the second user device 20 with a notification that bitcoin has been added to their wallet as part of a referral bonus system.
- FIG. 40illustrates a view that is displayed when the user selects a “Limits and Verifications” tab in the top margin of the “Buy/Sell” page.
- FIG. 41illustrates further transfers or purchases (Transfer 4; Transfer 5; Transfer 6).
- the fourth transfer (Transfer 4)represents the purchase of bitcoin from the first host computer system's 14 master wallet.
- the fifth transferrepresents the transfer of bitcoin from the second wallet (Wallet B) to the first wallet (Wallet A).
- the second wallet (Wallet B)now has login details stored therein. If the second user device 20 in FIG. 1B has been logged out of the second wallet (Wallet B), then the second user device 20 is first directed to the login module 38 which receives login details for the second wallet (Wallet B) from the second user device 20 , verifies whether the login credentials for the second wallet (Wallet B) match the login details for the second wallet (Wallet B). If the login details match the login credentials, then the login module 38 logs the second user device 20 into the second wallet (Wallet B).
- the login module 38then provides the second user device 20 with access to the hosted email module 46 .
- the user of the second user device 20then enters the email address (email address A) of the user of the first wallet (Wallet A) and an amount of bitcoin that the user of the second user device 20 wishes to transfer from the second wallet (Wallet B) to the first wallet (Wallet A).
- the user of the second user device 20uses the hosted email module 46 to send an email via the Internet 22 to the first user device 18 .
- a transfer(Transfer 5) is recorded within the second wallet (Wallet B). Because one of the Bitcoin addresses (Bitcoin address 4) has funds associated therewith, it can be charged for the transfer (Transfer 4).
- the transfer (Transfer 4)has the email address (email address A) to which the email has been sent and the amount in bitcoin associated therewith.
- the miner's fee that is paid by the first host computer system 14 and the host fee that is charged for the transferare zero bitcoin because the first wallet (Wallet A) is stored within the wallets 42 of the first host computer system 14 .
- the user of the first user device 18receives the email indicating the transfer of bitcoin to their wallet (Wallet A).
- a Bitcoin address (Bitcoin address 5)is recorded within the first wallet (Wallet A) for the transfer (Transfer 5) together with the identifier of the second wallet (Wallet B) from which the transfer has been made and the amount in bitcoin.
- the amount in bitcoin corresponding to the transfer (Transfer 4) in the second wallet (Wallet B)is the same as the amount in bitcoin as in the first wallet (Wallet A).
- the user of the second walletcan opt to send Bitcoin to a Bitcoin address of the first wallet (Wallet A).
- the transferis the same as the preceding transfer (Transfer 5) in all other respects.
- FIG. 42shows a view that is displayed to the user of the second user device 20 in FIG. 1B in order to make the transfer from their wallet (Wallet B) to the first wallet (Wallet A).
- the viewincludes a field for the user to enter the email address (email address A) and fields for entering either an amount in bitcoin (BTC) or an amount in a local currency (USD—United States Dollar).
- BTCemail address
- USDUnited States Dollar
- the exchange rate between Bitcoin and the local currencyis shown in the top left corner.
- the viewalso includes a button “Send Money” which, when selected by the user, initiates the transfer of bitcoin.
- FIG. 43is a view that is displayed to the user indicating transactions that have been initiated or completed.
- the purchase of bitcoin discussed with reference to FIGS. 35 to 37is shown as “PENDING”.
- a block chain verification noticehas to be broadcast by the miner computer system 28 and be received by the first host computer system 14 in FIG. 1A before a determination is made to change the marker “PENDING” to “COMPLETE”.
- the other transactions representing transfers between the first and second wallets (Wallet A and Wallet B) in FIG. 41are shown as completed because they do not need block chain verification outside of the first host computer system 14 . No block chain verification notice is thus required for these transactions to be marked “COMPLETE”.
- FIG. 44shows a view that can be selected by the user by selecting a tab in the top margin wherein the user is shown the Bitcoin addresses associated with transactions that have been completed.
- FIG. 45illustrates a further transaction (Transfer 7) wherein bitcoin is transferred from the second wallet (Wallet B) to a third wallet (Wallet C) held by the second host computer system 16 in FIG. 1A .
- the user of the second user device 20enters a bitcoin address (Bitcoin address 6) that is located in the third wallet (Wallet C) and an amount of bitcoin to be transferred to the third wallet (Wallet C).
- a transfer (Transfer 7)is recorded within the second wallet (Wallet B).
- Associated with the transfer (Transfer 7)are the Bitcoin address (Bitcoin address 6), the amount in bitcoin that is being transferred and a miner's fee that is charged for the transfer and has to be paid by the first host computer system 14 to the miner computer system 28 in FIG. 1A . No fee is charged by the first host computer system 14 for a transfer to another Bitcoin address.
- a transfer instructionis created and is broadcast via the host node 30 to all remote nodes 32 A-D within the Bitcoin network 12 .
- the transfer instructionthus traverses the first node and the second remote node 32 B to reach the second host computer system 16 .
- the second host computer system 16 and all other computer systems connected to the remote nodes 32 A-Drecord the transfer (Transfer 7) with respect to the Bitcoin addresses (Bitcoin address 4; Bitcoin address 6).
- the transfer (Transfer 7)has associated therewith the amount in bitcoin.
- the transfer instruction that results in the transfer (Transfer 5)thus results in no miner's fee being charged to and paid by the first host computer system 14 .
- No host feeis charged to the second wallet (Wallet B) because the transfer (Transfer 7) is made to another wallet (Wallet A) within the wallets 42 of the first host computer system 14 .
- the transfer instruction that results in the transfer (Transfer 7) representing the transfer to the Bitcoin address (Bitcoin address 6) in the third wallet (Wallet C)results in a miner's fee that is paid by the first host computer system 14 to the miner computer system 28 .
- the miner computer system 28is responsible for verifying transfers of Bitcoin over the Bitcoin network 12 . In the present scenario, the miner computer system 28 verifies the transfer of bitcoin from the second wallet (Wallet B) to the third wallet (Wallet C).
- Another transfermay comprise that bitcoin is sent to one of the nodes, e.g. node 32 C.
- the node 32 Ccould be a fourth user device which is owned by the recipient of the Bitcoin transfer having its own Bitcoin address.
- FIG. 46illustrates components that are used for cold storage of value of bitcoin, including a local storage 56 , a local controller 58 , a vault 64 , a splitter 66 , one or more encryption algorithms 68 and 70 and an offline distribution module 72 .
- the vault 64has a Bitcoin address 80 with a private key 79 .
- the private key 79is, for purposes of illustration, shown as a nine digit sequence of characters that are provided to the splitter 66 .
- the splitter 66splits the nine digits of the private key 79 into seven overlapping codes (Codes 1 to 7).
- the encryption algorithm 68encrypts the first code (Code 1) into an encrypted code (Encrypted Code 1).
- the second code (Code 2)is encrypted by an encryption algorithm (not shown) into an encrypted code (Encrypted Code 2).
- Each one of the seven codesis encrypted into a separate encrypted code.
- a separate keymay be used for each one of seven codes.
- a separate encryption algorithmmay be used for each one of the seven codes.
- the offline distribution module 72transmits each one of the encrypted codes (Encrypted Code 1 to 7) to a separate location.
- the locationsare remote locations that are geographically separated from one another.
- the offline distribution module 72may also be used to print one or more of the encrypted codes for paper delivery to respective remote locations.
- FIG. 47illustrates functioning of the offline distribution module 72 following distribution of the encrypted codes in FIG. 46 .
- the offline distribution module 72removes the private keys 79 of the Bitcoin address 80 of the vault 64 .
- the offline distribution module 72also removes the private key 79 of the Bitcoin address 80 within the local storage 56 .
- a local register 60includes a plurality of wallets 42 , one of which is shown.
- the wallet 42has a plurality of Bitcoin addresses 74 , 76 and 78 associated therewith.
- Each Bitcoin address 74 , 76 and 78has a respective value and a respective private key.
- the local controller 58transfers the entire value of the Bitcoin addresses 76 and 78 into the vault 64 .
- the value relating to the Bitcoin address 74is not transferred into the vault 64 .
- the local controller 58calculates the total value of the Bitcoin addresses 76 and 78 that have been transferred into the vault 64 and records the total value in the local storage 56 in association with the Bitcoin address 80 .
- the value of the Bitcoin addresses 76 and 78are only held within the vault 64 and the local storage 56 .
- the private key 79is only held in a split and encrypted form at the distributed locations where the offline distribution module 72 in FIG. 46 has distributed them to. Unless access can be gained to the private key 79 that has now been split and distributed, it is not possible to access the value of the Bitcoin addresses 76 and 78 . It is now possible for a user to which the wallet 42 is registered to use the Bitcoin address 74 for transacting with another user via the wallet management module 44 in FIG. 1B .
- the Bitcoin addresses 76 and 78are not usable by the wallet management module 44 for purposes of transacting with another user at this time because their values, within the wallet 42 , have been removed.
- FIG. 50shows how the private keys of the vault 64 and the Bitcoin addresses 76 and 78 that were removed in FIG. 46 are restored.
- Components that are provided for restorationinclude a plurality of restoration interfaces 82 , 84 and 86 , one or more decryption algorithms 88 , 90 and 92 and an assembler 94 .
- the holder of the first encrypted code(Encrypted Code 1) is called upon to enter the encrypted code into the restoration interface 82 .
- the restoration interface 82may for example be a web page with a field for entry of the first encrypted code.
- the restoration interface 82may be an application programmable interface (API) and the first encrypted code can be entered into the API with or without human involvement.
- APIapplication programmable interface
- the second, third, fifth and sixth encrypted codesare not received at this time.
- the fourth and seventh encrypted codesare received through the restoration interfaces 84 and 86 , similar to the first encrypted code.
- the decryption algorithm 88decrypts the first encrypted code (Encrypted Code 1) into the first code (Code 1).
- the decryption algorithms 90 and 92decrypt the fourth and seventh encrypted codes (Encrypted Code 4 and Encrypted Code 7) into the fourth and seventh codes (Code 4 and Code 7) respectively.
- three codesare the minimum number of codes that are required in order to reassemble the private key 79 .
- the minimum number of codes required for reassembly in FIG. 48is thus less than the total number of codes into which the private key 79 has been split in FIG. 46 .
- the assembler 94assembles the private key 79 when the minimum number of codes has been received.
- the private key 79 of the Bitcoin address 80 in the local storage 56is used to access the vault 64 .
- the local controller 58then restores the private key 79 from the local storage into the vault for association with the Bitcoin address.
- the block chainwill know whether the private key 79 that has been restored is the same private key 79 that was previously associated with the Bitcoin address. Only upon confirmation from the block chain will it be possible to transfer the value from the vault 64 to the local register 60 .
- the local controller 58restores the respective value of the Bitcoin addresses 76 and 78 in the vault 64 to the Bitcoin addresses 76 and 78 in the wallet 42 . Because the values have been restored to the Bitcoin addresses 76 and 78 in the wallet 42 they are usable for transacting with other users.
- FIGS. 51 a to 51 dillustrate the use of a “hot” wallet in combination with “cold storage”.
- the wallet 42has the Bitcoin addresses 74 , 76 , 78 and a further Bitcoin address 98 , each having a respective value associated therewith.
- the local storage 56has first, second and third Bitcoin addresses 80 A to 80 C for first, second and third vaults 64 A to 64 C, respectively.
- the Bitcoin addresses 76 and 78form a first transfer set that is selected for cold storage.
- the Bitcoin addresses 74 and 98form a first transacting set.
- the values of the Bitcoin addresses 76 and 78 of the first transfer setare transferred into the first vault 64 A, as represented by “Value” in the first vault 64 A.
- the private key of the Bitcoin address 80 A of the first vault 64 Ais then transferred into the local storage 56 and is stored in association with the first Bitcoin address 80 A. As hereinbefore described with reference to FIG. 46 , the private key of the Bitcoin address 80 A in the local storage 56 is then split and distributed. As hereinbefore described with reference to FIGS. 47 and 48 , the private keys of the Bitcoin address 80 and the value of the Bitcoin address 76 and 78 are then removed. It is then not possible for a user of the wallet 42 to use the Bitcoin address 76 and 78 for transacting with another user. The user can still transact with another user using the Bitcoin addresses 74 and 98 of the first transacting set because their values are still associated with them within the wallet 42 .
- FIG. 51 bshows the Bitcoin addresses 76 and 78 within the wallet 42 with their values removed and the Bitcoin address 80 A within the local storage 56 with its private key removed.
- the private key of the Bitcoin address 80 B of second vault 64 Bis transferred into the local storage 56 and associated with the second Bitcoin address 80 B within the local storage 56 .
- the private key of the second Bitcoin address 80 B in the local storage 56is split and distributed and then removed from the local storage 56 .
- the Bitcoin address 98is selected as part of a second transfer set of one or more Bitcoin addresses.
- the value of the Bitcoin address 98is transferred from the wallet 42 into the second vault 64 B, as represented by “Value” in the second vault 64 B.
- the value of the Bitcoin address 98 within the wallet 42is thus removed.
- the user of the wallet 42can now not use the Bitcoin address 98 for purposes of transacting with another user because the value of the Bitcoin address 98 has been removed from the wallet 42 .
- the Bitcoin address 74forms part of a second transacting set that may include one or more Bitcoin addresses that can be used for transacting with another user.
- FIG. 51 cshows the Bitcoin address 98 having its value removed and the second Bitcoin address 80 B within the local storage 56 having its private key removed.
- the private key of the first Bitcoin address 80 A within the local storage 56is restored to the vault 64 as hereinbefore described with reference to FIG. 50 .
- the respective values of the Bitcoin addresses 76 and 78are then restored from the vault 64 A to the Bitcoin addresses 76 and 78 in the wallet 42 . Because the values of the Bitcoin addresses 76 and 78 are restored within the wallet 42 , the Bitcoin addresses 76 and 78 of the first transfer set can, at least for the time being, be used together with the second transacting set for transacting with another user.
- FIGS. 51 b and 51 cThe same Bitcoin addresses 74 , 76 , 78 and 98 that are shown in FIG. 51 a are also shown in FIGS. 51 b and 51 c . It should be understood that the Bitcoin addresses may change between the figures. The system allows for the value that was previously associated with one Bitcoin address to be restored to another Bitcoin address if necessary.
- the first vault 64 Ais discarded after the value therein is restored.
- the first Bitcoin address 80 A within the local storage 56 and the first vault 64 Awill never be used again.
- the Bitcoin address 78is selected as a third transfer set.
- the private key of the Bitcoin address 80 C of the third vault 64 Cis transferred into the local storage 56 and stored in association with a third Bitcoin address 80 C.
- the value of the Bitcoin address 78is transferred from the wallet 42 to the third vault 64 C.
- the user of the wallet 42can now not use the Bitcoin address 78 for transacting with another user.
- the Bitcoin address 76forms part of a third transacting set that could include one or more Bitcoin addresses.
- the Bitcoin address 76can be used by the user of the wallet 42 for transacting with another user because the value of the Bitcoin address 76 is associated therewith within the wallet 42 .
- the second and third transacting setscan thus be used by the user for transacting with another user.
- the second and third transfer setsare unusable for transacting with another user because their private keys have been removed.
- FIG. 52illustrates how the local controller 58 (see FIGS. 46 to 50 ) maintains transaction sets of a wallet 42 within a target range 101 . Should all the Bitcoin addresses of the wallet 42 have values associated therewith, the wallet 42 is said to be 100% hot and 0% cold. If all the Bitcoin addresses in a wallet 42 have their values removed, the wallet 42 is to be 0% hot and 100% cold.
- the target range 101 for the total Bitcoin value within the walletmay for example be 5% to 10% hot.
- the values of the first transacting setare transferred from the wallet 42 as described with reference to FIG. 51 a .
- the usertransacts with some of the Bitcoin addresses and the total value within the wallet 42 of the Bitcoin addresses that are hot is reduced.
- the values of the second transfer setare removed from the wallet 42 as described with reference to FIG. 51 b .
- the values of the first transfer setare restored as described with reference to FIG. 51 c .
- the usertransacts and gains further Bitcoin addresses for additional value within their wallet 42 .
- values of the third transfer setare transferred out of the wallet 42 as described with reference to FIG. 51 d . It can thus be seen that the local controller 58 in FIGS. 46 to 50 adjusts the total value of Bitcoin that is not within the target range 101 .
- the local controller 58typically recalculates the hot/cold value ratio of each wallet on a daily basis and automatically adjusts the value to the target range 101 .
- FIG. 53illustrates the use of an intermediate hot wallet 114 that is used to collect bitcoin values from a plurality of wallets 42 A to C.
- the wallet 42 Ais that same as the wallet 42 as described above.
- the wallet 42 Bhas bitcoin addresses 120 , 122 , 124 and 126 associated therewith.
- the wallet 42 Chas bitcoin addresses 128 , 130 , 132 and 134 associated therewith.
- Each wallet 42 A, B or Cis held within the target range 101 in FIG. 50 .
- the values of the bitcoin addresses 76 , 78 , 120 , 122 , 128 and 130are identified for transfer to the vault 64 A and are first transferred or “swept” to the intermediate hot wallet 114 from where they are transferred to the vault 64 A.
- FIG. 54illustrates a network environment 136 that, in addition to the first host computer system 14 , includes a customer computer system 138 and a merchant computer system 140 that are connected to one another over the Internet 142 .
- the merchant computer system 140has an online store 144 and a website 146 .
- the customer computer system 138has a browser 148 .
- a customer at the customer computer system 138can use the browser 148 to access the website 136 over the Internet 142 .
- the website 136is then displayed on the browser 148 .
- the website 136allows for the customer to make purchase on the online store 144 .
- the customermay, for example, purchase real goods, virtual goods or services from the online store 144 .
- the first host computer system 14includes an application programmable interface (API) 150 , a reference code generator 152 , a transaction processor 154 , a currency converter 156 and merchant, and customer and host wallets 158 , 160 and 162 .
- the wallets 158 , 160 and 162may be of the kind as hereinbefore described.
- the customeris shown a shopping cart with several payment options, including “Pay with Credit Card” and “Pay with bitcoin.”
- the customerPrior to being displayed the shopping cart, the customer has traveled through the shopping flow of the merchant computer system 140 , has selected one or more items to be purchased and has selected a shopping or checkout cart, which causes the display of the view shown in FIG. 55 .
- the merchant computer system 140When the user selects the button “Pay with bitcoin” the merchant computer system 140 , at 166 , transmits an API call to the first host computer system 14 .
- the API callincludes a request for payment.
- the request for paymentincludes an amount in a currency, in the present example $14.00, an order name (usually a number), order descriptions (usually items in the checkout cart in a single line-item entry separated by commas), and a success uniform resource locater (URL) if desired (a page to which the customer is redirected at checkout if the order completes).
- a currencyin the present example $14.00
- an order nameusually a number
- order descriptionsusually items in the checkout cart in a single line-item entry separated by commas
- URLsuccess uniform resource locater
- the reference code generator 152When the first host computer system 14 receives the API call at 166 , the reference code generator 152 generates a unique reference code for the specific order. The reference code is thus uniquely generated for each API call.
- the first host computer system 14then stores the reference code in its database.
- the first host computer system 14responds to the API call received at 166 to transmit the reference code to the merchant computer system 140 .
- the merchant computer system 140receives the reference code as reference code 170 .
- the merchant computer system 140stores the reference code as reference code 172 within its accounting system 173 and associates the reference code 172 with the particular order shown in the shopping cart.
- the merchant computer system 140also creates a URL 174 .
- the reference code 170is used as a reference code 176 within the URL 174 when the URL 174 is created.
- the first host computer system 14creates a URL 180 that includes a reference code 182 .
- the reference code 182 and the reference code 176are the same.
- the merchant computer system 140 at 178redirects the browser 148 ( FIG. 54 ) using the URL 174 .
- the browseris then redirected to the URL 180 of the first host computer system 14 .
- the URL 180may, for example, be the URL of a landing page, iFrame or modal window 184 .
- the landing page, iFrame or modal window 184presents checkout options to the customer, including to pay with the customer wallet 160 if one exists, to pay with bitcoin using an external account, or to create a wallet at the first host computer system 14 for purposes of completing the purchase.
- the customerinstead of being automatically redirected by the merchant computer system 140 to the first computer system 14 , the customer may be redirected to a different page at the merchant computer system 140 , which will then contain a link for the customer to navigate to the landing page, iFrame or modal window 184 .
- the first host computer system 14automatically generates a bitcoin address 186 specifically for the customer's order within the merchant wallet 158 .
- the first host computer system 14also creates a bitcoin price based on the price in local currency and displays the bitcoin price within the landing page/iFrame or modal window 184 within the browser 148 .
- the graphillustrates a fluctuating Bitcoin to dollar exchange rate.
- the exchange rate at minute 0is used at 190 to calculate the exchange rate.
- the local currency price in the present exampleis $14.00 which gives a Bitcoin price of 0.02 BTC.
- the price of 0.02 BTC that is based on the exchange rate at minute 0is maintained for a select period of time, in the present example 10 minutes, before it resets. The customer may not wish to immediately send the bitcoin, but may do so at any time before the price resets at minute 10 and the exchange rate remains locked in and the Bitcoin price thus remains unchanged at 0.02 BTC during that time.
- An optionis displayed to the customer to send the bitcoin together with the price in bitcoin at minute 0.
- the customer computer system 138transmits a send instruction to the first host computer system 14 .
- the first host computer system 14receives and at 192 detects the send instruction.
- the customermay for example request to send bitcoin from the customer wallet 160 or via another path as hereinbefore described.
- the first host computer system 14responds to the send instruction to transmit an order status message that includes the reference code for the transaction to the merchant computer system 140 .
- the merchant computer system 140receives the reference code as reference code 194 .
- the merchant computer system 140matches the reference code 194 to the reference code 172 within its accounting system 173 and marks the transaction as complete.
- the send instructionis processed at minute 6.
- the exchange ratehas in the present example changed between minute 0 and minute 6. Should the bitcoin price of 0.02 BTC be converted to local currency at this time it would result in a different price in local currency than the original transaction.
- the difference between the original price at minute 0 and minute 6represents either a loss or a gain for the first host computer system 14 .
- the loss and gainis used to calculate bitcoin replacement costs on a periodic basis.
- the first computer system 14responds to the send instruction received at 192 to transmit 0.02 BTC to the bitcoin address 186 associated with the merchant wallet 158 .
- the first host computer system 14at 196 , immediately purchases the bitcoin from the merchant wallet 158 , resulting in a transfer of the bitcoin from the merchant wallet 158 to the host wallet 162 .
- the first host computer system 14purchases the bitcoin at the exchange rate locked in at minute 0.
- the first host computer system 14Periodically, for example daily, calculates the total amount of bitcoin sold by the merchant wallet 158 that day at the locked in prices.
- the first host computer system 14has a bank transfer module 200 that, at 202 , transmits a payment instruction to a bank for the first host computer system 14 .
- the bank for the first host computer system 14communicates with a bank of the merchant computer system 140 . Such communication, at 204 , results in transfer of funds from a host bank account 206 to a merchant bank account 208 .
- the customeruses their customer wallet 160 to transfer funds in the form of bitcoin from the customer wallet 160 to the merchant wallet 158 and the funds are then transferred in the form of bitcoin from the merchant wallet 158 to the host wallet 162 .
- the merchant wallet 158can be bypassed such that the customer transfers funds in the form of bitcoin from the customer wallet 160 directly into the host wallet 162 .
- the funds that are received by the host wallet 162are used as a basis for calculating the amount of money in local currency that is transferred by the bank transfer module 200 , minus a fee that is held back by the first host computer system 14 for purposes of processing the transaction.
- the API 150sends and receives API calls at 166 , 168 and the order status message in response to the send instruction 192 in FIG. 55 .
- the currency converter 156is responsible for receiving and maintaining exchange rate for bitcoin to local currency and for calculating the bitcoin price based on the local currency price and the exchange rate at any particular moment in time.
- the transaction processor 154is responsible for transferring funds in the form of bitcoin or local currency from one wallet or bank account to another.
- the exchange rateis locked in when the customer accesses the landing page, iFrame or modal window 184 and is locked for ten minutes.
- the merchantstypically create a payment “button” or using the API, specifically the button API, of the first host computer system. Selection of the button by the customer results from the process described above wherein the customer is directed to the landing page, iFrame or modal window 184 .
- Such a buttondoes not need to look any different from the merchant's standard “submit order” button and the button API is linked into the standard “submit order” button of the merchant computer system 140 , which when clicked will direct the user directly to the landing page, iFrame or modal window 184 .
- the exchange rateis locked. The merchant “order” is thus not created—i.e., with locked in exchange rate—until the user clicks the payment button to land on our landing page.
- Another embodimentis used in white-label solutions.
- the useris not directed away from the merchant domain to a landing page such as the landing page, frame or modal window 184 to complete payment. Instead, the checkout information that would have otherwise shown on the landing page is displayed inside the merchant's browser checkout tool.
- Such an embodimentmay not allow “one-click” checkout for users who are already signed into their customer wallet 160 ; a user can only pay by QR code scan and/or manual entry of a bitcoin address.
- the merchant(1) creates a “button” when they post an item for sale to the website (the button includes the price in local currency, but not a bitcoin price and can be created at any time—e.g., weeks before a purchase); and (2) when the customer wishes to pay, e.g., by clicking on a “Place Order” button, the merchant computer system 140 sends an API call to the first host computer system 14 which responds by sending back a locked in exchange rate, which again is good for ten minutes. The merchant then displays the checkout information to the user—i.e., the proper bitcoin address and amount.
- This embodimentdiffers in that: (1) the “order” is created earlier in time, and the exchange rate follows on as a separate API call; and (2) the checkout information is hosted within the merchant's domain.
- FIG. 56illustrates a method of managing bitcoin wherein a personal vault is created for a user.
- the useralready has an account that the user can log into using a website.
- the accounthas a first email (electronic communication) address.
- the first email addressmay be john.smith@gmail.com.
- the accountalso has a phone number associated therewith and one or more wallets as herein before described.
- the websiteprovides the user with a link to create a vault.
- the useris provided an option to create an individual vault or a group vault. In an individual vault the user will be required to respond to two emails in order to transfer bitcoin out of the vault. In a group vault multiple users are required to respond to emails in order for the user of the account represented at 220 to transfer the bitcoin out of the vault.
- the usermay, at 224 , select an individual vault.
- an interface of the websiteis presented with a field for the user to enter a second email address.
- the second email addressmay for example be john.smith@hotmail.com.
- the userenters the second email address and selects a button to transmit the second email address from their device to the first host computer system 14 .
- the first host computer system 14receives the second email address
- the first host computer system 14transmits a confirmation email with a confirmation link to the second email address.
- the purpose of the email that is transmitted at 228is to confirm the second email address.
- the first host computer system 14waits for the confirmation.
- the first host computer system 14does not proceed to create a vault if the confirmation is not received.
- the userselects the confirmation link, which causes transmission of the confirmation from the device of the user to the first host computer system 14 .
- the first host computer system 14proceeds at 232 to register a vault within the same account shown at 220 .
- the vaultincludes the first and second email addresses.
- the vaultalso includes the phone number of the account.
- the first host computer system 14updates the interface of the website to provide a summary.
- the summaryindicates that, in order to transfer bitcoin out of the vault, emails will be sent to the first and second email addresses, and the summary includes the phone number associated with the vault and that the bitcoin will not be transferred out of the vault for a period of 48 hours.
- the interfacealso includes a “Finish” button. When the user selects the “Finish” button, the browser used by the user, at 238 , lands in the vault. The vault looks like a wallet, but has a security feature that limits transfer of bitcoin out of the vault.
- the usermay, at 240 , select a group vault.
- the first host computer system 14provides the user with an option whether 2 out of 3 confirmations are required or 3 out of 5 confirmations are required. If the user selects that 2 out of 3 confirmations are required, then the user is required to enter two email addresses in addition to their own email address shown in the account at 220 . If the user selects that 3 out of 5 confirmations are required, then the user is required to enter four email addresses in addition to their email address shown in the account at 220 .
- the interface of the websiteis updated to request the additional email addresses from the user.
- the interfacetypically includes fields for the user to enter the additional email addresses.
- the first host computer system 14makes a determination whether all the additional email addresses are associated with other accounts within the first host computer system 14 . If all the additional email addresses are associated with other accounts, then the first host computer system 14 proceeds at 248 to update the account represented at 220 with a vault that includes the first email address, the additional email addresses and the phone number associated therewith.
- the first host computer system 14transmits an email to the additional email address that is not associated with an account to create an account.
- a user receiving the email transmitted at 250can proceed at 252 to create an account with the second email address associated with the account. Only after all the additional email addresses are associated with accounts does the first host computer system 14 , at 248 , proceed to register a vault.
- the first host computer system 14then at 254 provides a summary through the interface of the website.
- the summaryshows that in order to transfer bitcoin, emails will be sent to and confirmations will be required from the first email address and the minimum of the additional email addresses.
- the summaryalso includes the phone number associated with the vault and states the waiting period before the bitcoin is transferred.
- the websitealso includes a “Finish” button which, when selected by the user at 238 , lands the browser used by the user in the vault.
- FIG. 57illustrates how bitcoin is transferred into and out of the vault.
- the userfirst transfers bitcoin into the vault.
- the usermay transfer the bitcoin from one of their wallets associated with their account into the vault or may transfer the bitcoin into the vault from an external source.
- the bitcoinis then stored within the vault.
- the userrequests a transfer out of the vault using the website.
- the userincludes the amount of bitcoin to be transferred, the reason for the transfer and selects a wallet to which the bitcoin is to be transferred.
- the useralso includes a two-factor code which the user may obtain through a mobile application or via SMS communication with the first host computer system 14 .
- the first host computer system 14determines whether the two-factor code is correct. If the two-factor code is incorrect, then the first host computer system 14 , at 266 , makes no change to the website interface.
- the first host computer system 14proceeds at 268 to transmit all emails.
- emailsare sent to the first and second email addresses represented in the account at 234 in FIG. 56 .
- emailsare transmitted to the first email address and the additional email addresses represented in the account at 248 in FIG. 56 .
- the first host computer system 14updates the transaction list within the website to represent that approval is being awaited.
- Each one of the emailshas a respective link that can be selected by a recipient.
- a user receiving one of the emailsreacts to the email by clicking on the link.
- Selection of the linkcauses an authorization instruction to be transmitted from a device of the respective user to the first host computer system 14 .
- the first host computer system 14detects the authorization instruction received in response to one of the emails that have been transmitted.
- Selection of the link on the emailopens a browser on the recipient's device and displays a message that the authorization has been successfully approved.
- the recipient of a second one of the emailsreacts to the email by clicking the link on the second email to send an authorization instruction.
- the first host computer system 14detects the authorization instruction transmitted at 276 and displays a web page indicating that the authorization has been successfully approved.
- the first host computer system 14proceeds, at 280 , to update the transaction list to indicate that clearance is being awaited.
- the first host computer system 14starts a countdown timer and sends an email to the user of the account informing the user that the bitcoin will be transferred after 48 hours.
- Block 284represents the transmission of three email reminders to the user during the 48 hour waiting period. Each email includes the time remaining before the 48 hours will have elapsed and the amount of bitcoin that will be transferred out of the vault. Each email also includes a “Cancel” link. The user can select the “Cancel” link, which caused the transmission of a cancel instruction to the first host computer system 14 . The cancel instruction will cancel the transfer of the bitcoin and therefore the request that was transmitted at 262 .
- the first host computer system 14detects an end of the time period. The first host computer system 14 then transfers the amount of bitcoin out of the vault and in to the destination selected at 262 . The first host computer system 14 also updates the transaction list on the website to indicate that the transaction has been cleared.
- FIG. 58illustrates components of the first host computer system 14 that are used for carrying out the method shown in FIGS. 56 and 57 , including an account 290 of a user, a website 292 , a vault establishment wizard 294 , a vault management module 296 and the transaction processor 154 hereinbefore described.
- the vault establishment wizard 294is programmed to execute the establishment of the vault as described with reference to FIG. 56 .
- the vault management module 296is programmed to manage the vault as described with reference to FIG. 57 .
- a useraccesses the website 292 and downloads an interface so as to interact via the website 292 with the vault establishment wizard 294 and the vault management module 296 .
- the vault management module 296provides instructions to the transaction processor 154 to transfer the bitcoin out of the vault.
- FIG. 59shows the email that is transmitted at 228 in FIG. 56 .
- FIG. 60shows an interface of the website 292 in FIG. 58 when the user requests a transfer out of a vault at 262 in FIG. 57 .
- FIGS. 61 and 62show the emails that are transmitted at 268 in FIG. 57 .
- FIG. 63shows the interface of the website after the minimum number of approvals are received and the countdown clock has been started at 282 in FIG. 57 .
- Email addressesare used in the exemplary embodiment for electronic communication via email. Another embodiment may make use of other electronic communication addresses such as text messages to phone numbers or messages through social networks. Such messages may include authorization links as described or authorization may be obtained otherwise such as sending a reply message and including “Y” or “Yes” in the reply message.
- a secondary electronic communication addressmay be an individual address or a group address.
- FIG. 64illustrates the establishment of a user-controlled vault.
- a user at the first user device 18transmits a request for a user-controlled vault to the first host computer system 14 .
- the first host computer system 14responds to the request to initiate key generation.
- the first host computer system 14generates a seed for a master key.
- the first host computer system 14uses the seed generated at 306 to generate a master key.
- the master keyincludes a public key for the master key and a private key for the master key.
- the first host computer system 14stores the public key for the master key and, at 312 , stores the private key for the master key. The combination of the keys stored at 310 and 312 form a master key set 314 .
- a generation script 316initially resides on the first host computer system 14 .
- the first host computer system 14transmits the generation script 316 to the first user device 18 .
- the first user device 18receives the generation script 316 , which is executable on the first user device 18 .
- the generation script 316generates a seed for a shared key.
- the generation script 316includes a key generation algorithm.
- the key generation algorithmuses the seed generated at 320 to generate a shared key.
- the shared keyincludes a public key and a private key.
- the private key for the shared keyis shown at 322 .
- the generation script 316also includes an interface with a field for a user to enter a password via a keyboard. At 324 , the user enters the password into the interface.
- the generation script 316also includes an encryption algorithm. At 326 , the encryption algorithm generates an encrypted seed from the private key shown at 322 and the password entered at 324 .
- the key generation algorithm and encryption algorithmrespectively send the public key of the shared key and the encrypted seed to the first host computer system 14 .
- the first host computer system 14stores the public key for the shared key and, at 334 , stores the encrypted seed for the shared key.
- the public key stored at 332 and the encrypted seed 334can be viewed as a shared key set 336 .
- the private key shown at 322forms part of the shared key set 336 .
- the private key shown at 322is however never transmitted from the first user device 18 to the first host computer system 14 .
- the generation script 316further generates a seed for a user key.
- the key generation algorithmuses the seed generated at 338 to generate a user key.
- the user keyincludes a public key for the user key and a private key for the user key.
- the key generation algorithmtransmits only the public key for the user key to the first host computer system 14 .
- the first host computer system 14stores the public key for the user key.
- the generation script 316displays the private key for the user key to the user.
- the usercan then store the private key manually on the first user device 18 or write it down for later use.
- the first user device 18never transmits the private key displayed at 346 to the first host computer system 14 .
- the combination of the public key for the user key stored at 344 and the private key for the user key displayed at 346form a user key set 348 .
- FIG. 65illustrates how the user-controlled vault is used by the user.
- the user of the first user device 18creates and transmits a request to transact using bitcoin of the user-controlled vault.
- the requestreaches the transaction processor 154 hereinbefore described.
- the first host computer system 14creates an authorization for the transaction.
- the master key set 312 , shared key set 336 and user key set 334are replicated from FIG. 64 and the same reference numerals apply. It should however be understood that these keys are stored or displayed in FIG. 64 and that the stored and displayed keys are not stored but only retrieved and used in FIG. 65 .
- the first host computer system 14signs the authorization 364 with the private key for the master key. Such signature then allows for an authorization to transact at 368 . As shown in 370 , two out of three authorizations are required in order to transact and the authorization provided at 368 may form one of the two authorizations.
- a verification script 372initially resides on the first host computer system 14 .
- the first host computer system 14initiates key collection by transmitting the verification script 372 to the first user device 18 .
- the verification script 372is executable on the first user device 18 .
- Both the generation script 316 in FIG. 64 and the verification script 372 in FIG. 65may be in the form of JavaScriptTM that is executable by a browser on the first user device 18 .
- the encrypted seed stored at 334 on the first host computer system 14is transmitted together with the verification script 372 and is received at 374 by the first user device 18 .
- the verification script 372further includes an interface with a field for entering a password.
- the userenters the same password that the user entered at 324 in FIG. 64 into the field provided in the interface using a keyboard.
- the verification script 372further includes a decryption algorithm.
- the decryption algorithmuses the encrypted seed and the password to decrypt the encrypted seed and obtain the private key.
- the encryption at 326 in FIG. 64 and decryption at 378 in FIG. 65may follow the BIP38 protocol which is commonly understood by those skilled in the art of bitcoin encryption.
- the authorization 364is transmitted together with the verification script 372 to the first user device 18 .
- the verification script 372further has a signature algorithm.
- the signature algorithmsigns the authorization with the private key.
- the signature algorithmthen transmits the signed authorization (together with the signature) to the first host computer system 14 .
- the first host computer system 14has a verification module.
- a verification moduleis an algorithm that verifies a signature that was created with a private key using a public key.
- the verification moduleverifies the signature using the same public key stored at 332 for the shared key in the shared key set 336 that also includes the encrypted seed stored at 334 .
- the verification moduledetermines whether the signature is correct. If the signature is not correct, then the first computer system 14 returns to 374 where the encrypted key is received and the user enters a password. If, at 384 , a determination is made that the signature is correct, then the first host computer system 14 proceeds to 386 to provide an authorization due to the signature being correct.
- the authorization at 386may be one of the authorizations required at 370 in order to authorize the transaction.
- the verification script 372further includes an interface for entering the private key of the user key that was previously displayed at 346 to the user.
- the userenters the private key into the field provided therefor.
- a signature algorithmforming part of the verification script 372 signs the authorization with the private key that has been entered by the user. The signature algorithm then transmits the signed authorization (together with the signature) to the first host computer system 14 .
- a verification moduleverifies the signature using the public key that was stored at 344 .
- the verification moduledetermines whether the signature is correct. If the signature is incorrect, then the first host computer system 14 instructs the verification script 372 to return to 390 where the user is again asked for the private key for the user key. If the signature is correct, then the first host computer system 14 proceeds to 398 to provide an authorization for the transaction due to the signature being correct.
- the authorization provided at 398may be one of the authorizations required at 370 .
- the password entered at 376is never transmitted to the first host computer system 14 .
- the private key entered at 390is never transmitted to the first host computer system 14 .
- the user's control over the password and private keyeffectively disallows the transaction from being processed outside of the user's control.
- the first host computer system 14proceeds at 400 to authorize the transaction with the transaction processor 154 .
- FIG. 66illustrates an address generator 402 that is used to generate addresses such as the bitcoin address that are used for the transaction requested at 360 in FIG. 65 .
- a master key seed 404 , shared key seed 406 and user key seed 408are generated.
- the master key seed 404is used to generate a master public key 410 and a master private key 412 .
- the shared key seed 406is used to generate a shared public key 414 and a shared private key 416 .
- the user key seed 408is used to generate a user public key 418 and user private key 420 .
- Each one of the keys 410 to 420may be used to generate child keys M/0, M/1 . . . .
- the shared keys at each levelmay then be combined to generate an address.
- the M/0 keys of the master public key 410 , shared public key 414 and user public key 418may be used to generate an address (Address 0).
- the M/0 levelmay for example be the public keys stored at 310 , 332 and 334 in FIG. 64 .
- the address (Address 0)may for example be the bitcoin address for the transaction.
- the M/1 level keys of the master public key 410 , shared public key 414 and user public key 418may be used to generate another address (Address 1).
- the further addressesmay be generated to create further bitcoin addresses of for other purposes.
- FIG. 67 of the accompanying drawingsillustrates the first host computer system 14 , a partner computer system 422 and a receiver computer system 424 .
- the receiver computer system 424includes a receiver browser 426 .
- the partner computer system 422has a website, in the present example a blog with a blog post 428 that has a blog post URL 430 .
- a user of the receiver computer system 424uses the receiver browser 426 to create the blog post 428 .
- the first host computer system 14has a wallet in the form of receiver account 434 , an embedded code generator and a button ID generator 438 .
- the user of the receiver computer system 424creates the receiver account 434 .
- the receiver account 434has login details 442 and a receiver account identifier (ID) 444 .
- IDreceiver account identifier
- the user of the receiver computer system 424logs into the receiver account 434 and enters the blog post URL 430 through the user interface 36 ( FIG. 1B ).
- the blog post URL 430is then stored in association with the particular receiver account 434 with the wallet management module 44 ( FIG. 1B ).
- the first host computer system 14provides the blog post URL 430 to the embedded code generator and button ID generator 438 .
- the embedded code generator 438then generates an embedded code 450 and, at 452 , transmits the embedded code 450 to the receiver browser 426 .
- the embedded code 450includes the blog post URL 430 , receiver account ID 444 and a startup caller 454 .
- the blog post 428 on the partner computer system 422has a frame for pasting the embedded code 450 due to prior agreement between operators of the first host computer system 14 and the partner computer system 422 .
- the user of the receiver computer system 424copies the embedded code 450 received at 452 and pastes the embedded code 450 into the frame of the blog post 428 .
- the embedded code 450is then embedded and forms part of the HyperText Markup Language (HTML) of the blog post 428 .
- HTMLHyperText Markup Language
- a blog post 428is used herein to describe the invention by way of example. It should however be understood that the invention may have broader application.
- a URL of a pagemay for example have a video, song or news article. Such a page will typically have a frame for pasting the embedded code 450 . Alternatively, media content such as a video may not have a separate frame for pasting the embedded code. Instead, another manner of activating payment features of the invention may be provided, such as a separate URL link, voice activation, detection of human gestures of a user, etc.
- the button ID generator(see 438 ) generates a unique button ID.
- the button ID generatorstores the button ID as button ID 460 within a data store of the first host computer system 14 .
- the button ID generator 438stores the button ID 460 in association with the particular receiver account ID 444 and particular blog post URL 430 .
- Multiple receiver accountsmay exist within the first host computer system 14 .
- a receiver accountmay have multiple blog post URL's associated therewith. Each pair of a respective receiver account ID and respective blog post URL have a unique button ID.
- FIG. 68shows the first host computer system 14 , the partner computer system 422 and a sender computer system 464 .
- the sender computer system 464has a sender browser (not shown).
- the sender browserdownloads the blog post 428 from the partner computer system 422 .
- the startup caller 454is a script, e.g. JavaScript®, that automatically executes on the sender computer system 464 .
- the startup caller 454retrieves all sender cookies 472 on the sender computer system 464 .
- the startup caller 454transmits a startup call to the first host computer system 14 .
- the startup callincludes the cookies 472 , the blog post URL 430 and the receiver account ID 444 .
- the first host computer system 14includes a startup call responder 476 that receives the startup call 474 .
- the startup call responder 476uses the blog post URL 430 and receiver account ID 444 received in the startup call 474 to identify the particular button ID 460 .
- the button ID 460 in storagemay have bits 480 representing all payments made in association with the button ID 460 .
- the startup call responder 476retrieves the bits 480 associated with the button ID 460 from the data store.
- the startup call responder 476transmits a startup call response to the sender computer system 464 .
- the startup call response transmitted at 483is in response to the startup call received at 474 .
- the startup call responseincludes a button 484 , the bits 480 , a session script 486 and the button ID 460 .
- a display 490 of the sender computer system 464displays the blog post 428 .
- the embedded code 450has added the button 484 and the bits 480 to the blog post 428 .
- the button 484is a two-dimensional button that is selectable by a user of the sender computer system 464 .
- the session script 486is associated with the button 484 so as to be executable when the user selects the button 484 .
- the embedded code 450stores the button ID 460 within the sender cookies 472 .
- the button ID 460 stored within the sender cookies 472can now be used to identify the button ID 460 within the first host computer system 14 .
- the userhas selected the button 484 which, at 492 , initiates the session script 486 .
- the session script 486retrieves the sender cookies 472 and, at 496 , makes a session call to the first host computer system 14 .
- the session call 496includes the cookies 472 .
- the first host computer system 14includes a session responder 498 that receives the session call 496 .
- the session responder 498checks all data for the button ID 460 that has been received in the session call 496 .
- the data associated with the button ID 460may include a bitcoin address 502 , although no bitcoin address may be included within the cookies 472 of the session call 496 .
- the session responder 498determines whether a bitcoin address was received in the cookies 472 of the session call 496 . If no bitcoin address was received, the first host computer system 14 executes a bitcoin address generator 506 .
- the bitcoin address generator 506then generates a bitcoin address and, at 508 , stores the Bitcoin address in association with the button ID 460 .
- the newly saved Bitcoin addressis represented as bitcoin address 510 .
- the session responder 498transmits the Bitcoin address 510 that has been generated by the bitcoin address generator 506 to the sender computer system 464 .
- the session script 486stores the Bitcoin address 510 in association with the button ID 460 within the sender cookies 472 .
- the process started at 466 in FIG. 68is restarted and all cookies are stored from earlier browser sessions are collected and transmitted by the startup caller 454 .
- the session responder 498determines whether the sender computer system 464 is signed into a sender account. The determination is made based on whether a signed-in cookie is found among the cookies transmitted in the session call 496 . If no signed-in cookie is found, then the session responder 498 proceeds to 518 .
- the session responder 498sends a sign-in panel 520 , a sign-in script 522 , a listen code 524 , a third party payment script 526 , and a pull code 528 to the sender computer system 464 .
- the session script 486creates an overlay window that includes the sign-in panel 520 with a sign-in button 530 having the sign-in script 522 associated therewith.
- the usercan select the sign-in button 530 which, at 532 , initiates the sign-in script 522 .
- the sign-in script 522creates and opens a further window (not shown) that allows the sender of the sender computer system 464 to enter login details 534 of a sender account 536 .
- the sign-in script 522signs the sender computer system 464 into the sender account 536 using the login details 534 .
- the sign-in script 522at 548 , stores a signed-in cookie 549 within the sender cookies 472 .
- the sign-in panel 520further includes two payment selections, including a third party wallet button 544 , and a Quick Response (QR) code 546 .
- QRQuick Response
- the third party payment script 526is stored in association with the third party wallet button 544 .
- the listen code 524 and pull code 528are stored in an executable manner within the sender computer system 464 .
- the session script 486retrieves the bitcoin address 510 from the sender cookies 472 and displays the bitcoin address 510 within the sign-in panel 520 .
- the session responder 498proceeds to 550 .
- the session responder 498transmits a signed-in panel 552 , the listen code 524 , the third party payment script 526 , the pull code 528 and a host account payment script 554 to the sender computer system 464 .
- the signed-in panel 552is the same as the sign-in panel 520 with the exception that it includes a host account button 556 instead of the sign-in button 530 .
- the third party payment script 526is stored in association with the third party wallet button 544 .
- the host account payment script 554is stored in association with host account button 556 .
- Selection by the user of the host account button 556initiates at 560 the host account payment script 554 .
- the host account payment script 554transmits an instruction to the transaction processor 154 of the selection.
- the transaction processor 154makes a payment out of the sender account 536 to the receiver account 434 as hereinbefore described without going through the bitcoin network or the block chain.
- the transaction processor 154updates the bits 480 by adding the bits of the present transaction to the bits 480 already stored within the data store.
- the bits 480 within the data storethus represent an ongoing tally of all payments made in association with the button ID 460 .
- the bitcoin addresses 502 and 510represent bitcoin addresses that are generated for different sender computer systems 464 using the same button ID 460 .
- the host account payment script 554After the host account payment script 554 transmits the instruction to the transaction processor 15 , the host account payment script 554 initiates the pull code 528 .
- the pull code 528at 574 , pulls the new bit count from the bits 480 in the storage of the first host computer system 14 .
- the pull code 528updates the bits 480 in the blog post 428 based on the bits that have been pulled by the pull code 528 in FIG. 70 .
- the userselects the third party wallet button 544 which, at 560 , causes execution of the third party payment script 526 .
- the third party payment script 526then transmits a transaction (of bitcoin to the bitcoin address 510 ) to a third party transaction processor 562 .
- the third party transaction processor 562is hosted by a host computer system other than the first host computer system 14 .
- the third party transaction processor 562broadcasts the transaction to the bitcoin network 12 and it is picked up by the blockchain.
- the first host computer system 14further includes a block chain checker 567 and a bit updater 568 .
- the block chain checker 567periodically checks the block chain. For purposes of this discussion, the block chain checker 567 checks the block chain to determine whether there are any new transactions for the bitcoin addresses 502 and 510 stored in association with the button ID 460 . If the block chain checker 567 finds any further transactions, the block chain checker 567 notifies the bit updater 568 .
- the bit updater 568updates the bits 480 that are associated with the respective bitcoin address 502 or 510 . The bits 480 are updated by adding bits for any new transactions that have been picked up by the block chain checker 567 .
- the bit updater 568transmits a push update notification to the sender computer system 464 .
- the listen code 524receives the push update notification. Websocket technology may for example be used for the push update notification in order to open an interactive communication link.
- the listen code 524is continuously active and therefore continuously listens for push update notifications.
- the listen code 524initiates the pull code 528 .
- the pull code 528pulls the new bit count from the bits 480 in storage.
- the pull code 528updates the bits 480 in the blog post 428 based on the bits that have been pulled by the pull code 528 in FIG. 70 .
- the QR code 546may be scanned by an app on a mobile phone.
- the bitcoin address 510is encoded in the QR code 546 .
- the appcan decode the QR code 546 to extract the bitcoin address 510 and transmit a transaction (of bitcoin to the bitcoin address 510 ) to a third party transaction processor such as the third party transaction processor 562 .
- the button 484 shown in FIG. 69can be used as a Tip button.
- a user of the sender computer system 464can use the button 484 to make a small discrete payment to the user of the receiver computer system 424 .
- Such a paymentmay, for example, be as a reward for the content of the blog post 428 .
- FIG. 72shows a system 600 for transacting bitcoin.
- An Internet interface 602allows for user computers (user computers A to C) to connect to the system 600 over the Internet.
- Order gateways 604are connected to the Internet interface 602 to receive buy and sell offers via the Internet interface 602 from the user computers A to C.
- a matching engine 606is connected to the order gateways 604 . The matching engine 606 can receive the buy and sell offers from the order gateways 604 .
- a feed generator 608is connected to the Internet interface 602 .
- the matching engine 606provides an output to a multicast pipeline 610 .
- the feed generator 608is connected to the multicast pipeline 610 .
- the feed generator 608receives the buy and sell offers from the multicast pipeline 610 and displays any buy and sell offers via the Internet interface 602 to the user computers A to C. Users can thus view any buy and sell offers already in the system before making their own buy and sell offers.
- the matching engine 606can match buy and sell offers and broadcast the matches to the multicast pipeline 610 .
- the feed generator 608displays the matches via the Internet interface 602 to the user computers A to C.
- An exchange database 612includes records of bitcoin and currency held by users A to C corresponding to the user computers A to C.
- a clearing module 614is connected to the multicast pipeline 610 and receives matches from the multicast pipeline 610 .
- An exchange 616is connected to the clearing module 614 .
- the exchange 616is also connected to the Internet interface 602 . Users at the user computers A to C can provide instructions via the Internet interface 602 to the exchange 616 to transfer bitcoin or currency.
- the exchange 616has a number of functions, including calculating total amounts of Bitcoin and currency as represented in the exchange database 612 , cross checking bitcoin and currency totals between the exchange database 612 and an exchange user 618 , transferring bitcoin and currency between wallets A to C that correspond respectively to the users A to C in the exchange database 612 , updating bitcoin and currency amounts of the users A to C in the exchange database 612 , and may receive and execute instructions from the clearing module 614 to transfer bitcoin and currency between the users A to C in the exchange database 612 .
- the exchangeis connected to a ledger 620 .
- the ledger 620hold records of wallets A to C and further functions to cross-check balances between the exchange database 612 and exchange user 618 .
- FIG. 73 ashows the beginning of a transfer-in algorithm that is executed by the system 600 .
- a user at user computer Ahas $10 of currency in the exchange database 612 .
- the exchange 616calculates the total amount of currency and Bitcoin within the exchange database 612 and records the total amount as $10 and 0 bitcoin.
- the exchange user 618has $10, representing a previous transfer from wallet A to the exchange user 618 .
- a user at user computer Brequests a transfer via the Internet interface 602 .
- the transfermay for example be to transfer $20 from wallet B to the exchange user 618 .
- the Internet interface 602provides the transfer request to the exchange 616 .
- the exchange 616sends a cross-check request to the ledger 620 and at 2 b the ledger 620 cross checks the totals in the exchange database 612 and the exchange user 618 before proceeding with a transfer.
- the exchange database 612has $10 and 0 bitcoin and the exchange user 618 has $10 and 0 bitcoin. The totals therefore match. If either the currency or Bitcoin totals do not match, the exchange 616 does not make any further transfers and provides an alert to an operator. The operator will then remedy any mismatches and then reactivate the exchange 616 . Because the totals match, the exchange 616 proceeds with the transfer.
- the exchange 616transfers $20 from wallet B to the exchange user 618 .
- the exchange user 618calculates the total amount held by the exchange user 618 as $30, representing the $10 that was there before the transfer plus another $20 because of the transfer.
- the exchange 616records $20 for user B in the exchange database 612 .
- the exchange 616updates the totals and records a total amount of $30, representing the $10 held by user A and the $20 that has been added for user B.
- FIG. 73 cillustrates the totals in the exchange database 612 and the exchange user 618 after a further transfer wherein a user at the user computer C has requested a transfer of 5 Bitcoin from wallet C to the exchange user 618 .
- the exchange user 618now holds 5 Bitcoin and $30.
- User C, within the exchange database 612now holds 5 bitcoin.
- the totals held with the exchange database 612are $30 and 5 bitcoin. For purposes of discussion, this ends the transfer-in algorithm that was started in FIG. 73 a.
- FIG. 73 dshows a trading algorithm that is carried out after the transfer-in algorithm if FIGS. 73 a to 73 c .
- a user (buyer) at user computer Asubmits a buy offer of 2 bitcoin at $5 each ($10 total).
- all offersare transmitted via the Internet interface 602 , one of the order gateways 604 , the matching engine 606 and the multicast pipeline 610 to the feed generator 608 which displays the offers on the Internet interface 602 .
- a user at user computer Ccan thus see the buy offer submitted by the user at user computer A.
- the user (seller) at user computer Csubmits a sell offer for 2 Bitcoin at $5 each to the Internet interface 602 .
- the buy and sell offersare submitted by the Internet interface 602 to one of the order gateways 604 .
- the order gateway 604provides the buy and sell offers sequentially to the matching engine 606 .
- the user at user computer Ccan see the buy offer of the user at user computer A before submitting the sell offer.
- the user at user computer Ccan first submit the sell offer and the sell offer can be seen by the user at user computer A.
- the buy and sell offerswill typically be received by the matching engine 606 at different times.
- the matching engine 606attempts to match the buy and sell offers to one another. At 6 , the matching engine 606 has matched the buy and sell offers received from users at the user computers A and C.
- the matching engine 606then provides a broadcast of the match over the multicast pipeline 610 discussed with reference to FIG. 72 .
- the feed generator 608receives a multicast that includes the match.
- the clearing module 614receives the same multicast that includes the match.
- the feed generator 608provides a feed to the Internet interface 602 that includes the match. As previously mentioned, the feed generator 608 also provides a feed of buy and sell offers to the Internet interface 602 .
- the clearing module 614updates user A within the exchange database 612 by adding 2 bitcoin and subtracting $10 from user A.
- the clearing module 614updates user C by subtracting 2 bitcoin from and adding $10 to user C.
- the clearing module 614makes the updates directly to the exchange database 612 .
- FIG. 73 eshows a withdrawal algorithm that can be carried out after the trading algorithm in FIG. 73 d .
- a user at user computer Crequests a withdrawal of, for example, $10.
- the requestis received via the Internet interface 602 and is passed on to the exchange 616 at 10 b.
- the exchange 616sends a cross-check request to the ledger 620 and at 11 b the ledger 620 cross checks the totals before proceeding.
- the amount of Bitcoin in the exchange user 618 and the total amount of bitcoin represented in the exchange database 612are the same and the total currency amount in the exchange user 618 and in the exchange database 612 are the same. Should either of these two comparisons result in a mismatch, the exchange 616 will not make any withdrawal and create an alarm for an operator.
- the exchange 616transfers $10 from the exchange user 618 to the wallet C.
- the exchange user 618now has $20, representing the $30 in FIG. 73 e minus the $10 that has been transferred out.
- the exchange 616adds a representation for user C in the exchange database 612 showing a withdrawal of $10.
- the exchange 616updates the totals. Because user C has made a withdrawal of $10, the total currency amount within the exchange database 612 amounts to $20. The amount of bitcoin is still the same. The total amounts in the exchange user 618 and in the exchange database 612 are thus the same.
- a user at user computer Amay request a withdrawal of 1 bitcoin.
- the exchange 616then cross checks the total amounts, makes a transfer of 1 Bitcoin from the exchange user 618 to wallet A and updates the exchange database 612 by deducting 1 Bitcoin from user A and updates the total amount of Bitcoin to 4 Bitcoin.
- FIG. 74shows a diagrammatic representation of a machine in the exemplary form of a computer system 900 within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
- the machineoperates as a standalone device or may be connected (e.g., networked) to other machines.
- the machinemay operate in the capacity of a server or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.
- the machinemay be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
- PCpersonal computer
- PDAPersonal Digital Assistant
- STBset-top box
- WPAPersonal Digital Assistant
- the exemplary computer system 900includes a processor 930 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), a main memory 932 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), and a static memory 934 (e.g., flash memory, static random access memory (SRAM, etc.), which communicate with each other via a bus 936 .
- a processor 930e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both
- main memory 932e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.
- DRAMdynamic random access memory
- SDRAMsynchronous DRAM
- RDRAMRambus DRAM
- static memory 934e.g., flash
- the computer system 900may further include a video display 938 (e.g., a liquid crystal displays (LCD) or a cathode ray tube (CRT)).
- the computer system 900also includes an alpha-numeric input device 940 (e.g., a keyboard), a cursor control device 942 (e.g., a mouse), a disk drive unit 944 , a signal generation device 946 (e.g., a speaker), and a network interface device 948 .
- a video display 938e.g., a liquid crystal displays (LCD) or a cathode ray tube (CRT)
- the computer system 900also includes an alpha-numeric input device 940 (e.g., a keyboard), a cursor control device 942 (e.g., a mouse), a disk drive unit 944 , a signal generation device 946 (e.g., a speaker), and a network interface device 948 .
- the disk drive unit 944includes a machine-readable medium 950 on which is stored one or more sets of instructions 952 (e.g., software) embodying any one or more of the methodologies or functions described herein.
- the softwaremay also reside, completely or at least partially, within the main memory 932 and/or within the processor 930 during execution thereof by the computer system 900 , the memory 932 and the processor 930 also constituting machine readable media.
- the softwaremay further be transmitted or received over a network 954 via the network interface device 948 .
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Engineering & Computer Science (AREA)
- Finance (AREA)
- Theoretical Computer Science (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Technology Law (AREA)
- Signal Processing (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
- This patent application claims priority from U.S. Provisional Patent Application No. 61/954,434, filed on Mar. 17, 2014; U.S. Provisional Patent Application No. 61/990,017, filed on May 7, 2014; U.S. Provisional Patent Application No. 62/042,676, filed on Aug. 27, 2014; U.S. Provisional Patent Application No. 62/056,100, filed on Sep. 26, 2014; U.S. Provisional Patent Application No. 62/086,669, filed on Dec. 2, 2014 and U.S. Provisional Patent Application No. 62/099,992, filed on Jan. 5, 2015, each of which is incorporated herein by reference in its entirety.
- 1). Field of the Invention
- This invention relates to a computer system and method for transacting bitcoin.
- 2). Discussion of Related Art
- The Bitcoin network is a peer-to-peer payment system having a plurality of nodes that are connected to one another. Bitcoin exchange computer systems allow for users to exchange local currency into or out of bitcoin. Users send payments by broadcasting digitally signed messages to the Bitcoin network. Users may, for example, send and receive payments using mobile applications on mobile devices, client software or a web browser.
- Transactions do not explicitly identify the payor and payee by name or wallet. Instead, a bitcoin transaction transfers ownership to a new address, referred to as a “Bitcoin address”. The Bitcoin address is derived from the public portion of one or more cryptographic key pairs. The private portion of a key pair is not disclosed to the public. To send bitcoin sent to an address, a user broadcasts a payment message that is digitally signed with the associated private key.
- Participants known as “miners” at miner computer systems verify and timestamp transactions into a shared public database called a “block chain”. The miners are rewarded with transaction fees and newly minted bitcoin for their effort. The miner computer systems are specialized computers that append blocks of transactions to the block chain. Solving a cryptographic puzzle required to append a block carries a reward plus fees included in transactions in the block.
- Host computer systems reside at various nodes and may host accounts or “wallets” that allow users to make and accept payments using bitcoin. The wallet stores the public key of the Bitcoin address and its associated private key.
- The transfer of bitcoin may be an onerous task if the entire public key of the Bitcoin address has to be copied and transmitted.
- When a transaction is made between two wallets at the same or different host computer systems, the transaction is broadcast to the Bitcoin network for block chain verification. Such a block chain verification may take a long time to complete. Miner fees are also associated with such a transfer and have to be paid by a host computer system requesting the transfer.
- It may be a security concern for users that their Bitcoin addresses may be stolen from their wallets. Existing systems do not provide a solution for maintaining security of Bitcoin addresses while still allowing the users to use Bitcoin addresses within their wallets for transacting with other users.
- A merchant computer system often has an online store and a website. A customer at a customer computer system may use a browser to access the online store via the website. Items are displayed for purchase in a local currency. Exchange rate between bitcoin and local currency changes over short periods of time. The price in local currency may thus change between the time that the local currency is displayed to the customer and the time that the customer decides to make the purchase. As a result, the customer or the merchant may incur a loss in local currency. The customer or merchant may then be reluctant to purchase using bitcoin.
- In order for a user to access their wallet, the user may log into their account through the website using a user name and password. If the user name and password become compromised then it may be possible for bitcoin to be stolen out of the wallet. Users may therefore be reluctant to store bitcoin in their wallets without any additional security features.
- Bitcoin transacting requires the use of a public key and a private key. The private key is used to sign an authorization and the public key is used to verify the signature. Some users may require control over their private keys in order to ensure to such users that bitcoin transacting will not take place without their express authorization.
- Content creators often put a lot of time and energy into their blog posts. These efforts are rarely rewarded because efficient technology does not exist for rewarding bloggers for their efforts.
- The invention provides a host computer system for transacting bitcoin including a processor, a network interface device connected to the processor, a computer readable medium connected to the processor, a data store on the computer readable medium and a set of instructions on the computer readable medium that are executable by the processor. The set of instructions includes a wallet establishment module, a login module, a hosted email module and a wallet management. The wallet establishment module establishes a first wallet in the data store, stores login details for the first wallet and storing a value representative of an amount of bitcoin held by the first wallet. The login module receives login credentials over the network interface device for the first wallet from a first user device, verifies whether the login credentials match the login details for the first wallet, and if the login credentials match the login details then logs the first user device into the first wallet. The hosted email module, if the first user device is logged into the wallet, permits transmission of an email by a user of the first user device to an email address of a second user device. The wallet management module, in response to the transmission of the email, records a transfer in the first wallet for an amount of bitcoin from the first wallet to a second wallet identified by the email address.
- The invention also provides a method of transacting bitcoin. A processor establishes a first wallet in a data store connected to the processor. The processor stores login details for the first wallet. The processor stores a value representative of an amount of bitcoin held by the first wallet. The processor receives login credentials for the first wallet from a first user device. The processor verifies whether the login credentials match the login details for the first wallet. The processor, if the login credentials match the login details then, logs the first user device into the first wallet. The processor, if the first user device is logged into the wallet, permits transmission of an email by a user to the first user device to an email address of a second user device and in response to the transmission of the email. The processor records a transfer in the first wallet for an amount of bitcoin from the first wallet to a second wallet identified by the email address.
- The invention further provides a non-transitory computer-readable medium having stored thereon a set of instructions that are executable by a processor to carry out a method of transacting bitcoin. The processor establishes a first wallet in a data store connected to the processor. The processor stores login details for the first wallet. The processor stores a value representative of an amount of bitcoin held by the first wallet. The processor receives login credentials for the first wallet from a first user device. The processor verifies whether the login credentials match the login details for the first wallet. The processor, if the login credentials match the login details then, logs the first user device into the first wallet. The processor, if the first user device is logged into the wallet, permits transmission of an email by a user to the first user device to an email address of a second user device and in response to the transmission of the email. The processor records a transfer in the first wallet for an amount of bitcoin from the first wallet to a second wallet identified by the email address.
- The invention further provides a first host computer system for transacting bitcoin including a processor at a first node of the Bitcoin network, a network interface device connected to the processor, a computer readable medium connected to the processor, a data store on the computer readable medium and a set of instructions on the computer readable medium that are executable by the processor. The set of instructions includes a wallet establishment module. The wallet establishment module establishes a first and second wallets in the data store and stores a value representative of an amount of bitcoin held by the first wallet. The wallet management module receives, over the network interface device, a first transfer instruction for an amount of bitcoin from the first wallet and an identifier of the second wallet, in response to the first transfer instruction, records a transfer in the first wallet for the amount of bitcoin in the first transfer instruction out of the first wallet and a transfer in the second wallet, identified by the identifier of the second wallet, for the amount of bitcoin in the first transfer instruction into the second wallet without paying a miner's fee for the first transfer. In order to execute a subsequent on-block chain transaction, the wallet management module receives, over the network interface device, a second transfer instruction for an amount of bitcoin from the first wallet and a bitcoin address associated with a second node of the Bitcoin network, and in response to the second transfer instruction, records a transfer in the first wallet for the amount of bitcoin in the second transfer instruction out of the first wallet, broadcasts a message to the Bitcoin network, including to the second node, to record a transfer associated with the bitcoin address associated with the second node, for the amount of bitcoin in the second transfer instruction, and pays a miner's fee for the second transfer.
- The invention further provides a method of transacting bitcoin including. A processor of a first host computer system at a first node of the Bitcoin network establishes first and second wallets in a data store connected to the processor. The processor stores a value representative of an amount of bitcoin held by the first wallet. The processor receives a first transfer instruction for an amount of bitcoin from the first wallet and an identifier of the second wallet. The processor, in response to the first transfer instruction, records a transfer in the first wallet for the amount of bitcoin in the first transfer instruction out of the first wallet and a transfer in the second wallet, identified by the identifier of the second wallet, for the amount of bitcoin in the first transfer instruction into the second wallet without paying a miner's fee for the first transfer. The processor receives a second transfer instruction for an amount of bitcoin from the first wallet and a bitcoin address associated with a second node of the bitcoin network. The processor, in response to the second transfer instruction records a transfer in the first wallet for the amount of bitcoin in the second transfer instruction out of the first wallet, broadcasts a message to the Bitcoin network, including to the second node, to record a transfer associated with the bitcoin address associated with the second node, for the amount of bitcoin in the second transfer instruction and pays a miner's fee for the second transfer.
- The invention further provides a non-transitory computer-readable medium having stored thereon a set of instructions that are executable by a processor of a first host computer system at a first node of the Bitcoin network to carry out a method of transacting bitcoin. The processor establishes first and second wallets in a data store connected to the processor. The processor stores a value representative of an amount of bitcoin held by the first wallet. The processor receives a first transfer instruction for an amount of bitcoin from the first wallet and an identifier of the second wallet. The processor, in response to the first transfer instruction, records a transfer in the first wallet for the amount of bitcoin in the first transfer instruction out of the first wallet and a transfer in the second wallet, identified by the identifier of the second wallet, for the amount of bitcoin in the first transfer instruction into the second wallet without paying a miner's fee for the first transfer. The processor receives a second transfer instruction for an amount of bitcoin from the first wallet and a bitcoin address associated with a second node of the bitcoin network. The processor, in response to the second transfer instruction records a transfer in the first wallet for the amount of bitcoin in the second transfer instruction out of the first wallet, broadcasts a message to the Bitcoin network, including to the second node, to record a transfer associated with the bitcoin address associated with the second node, for the amount of bitcoin in the second transfer instruction and pays a miner's fee for the second transfer.
- The invention also provides a host computer system for transacting bitcoin including a processor, a computer readable medium connected to the processor, a local storage on the computer readable medium and a set of instructions on the computer readable medium that are executable by the processor. The set of instructions includes a register, a Bitcoin address and an associated private key and value stored in the register, a local controller, a splitter, an offline distribution module, at least one restoration interface, and an assembler. The local controller transfers a private key for a Bitcoin address of a vault, to a local storage connected to a processor and transfers the value of the Bitcoin address in the register to the vault. The splitter splits the private key of the Bitcoin address of the vault into a plurality of codes. The offline distribution module distributes the codes to remote distributed storage locations, removes the private key of the Bitcoin address of the vault from the local storage, and removes the value for the Bitcoin address of the register from the Bitcoin address of the register. The restoration interface receives at least some of the codes into which the private key for Bitcoin address of the vault has been split. The assembler assembles the codes that have been received into the private key of the Bitcoin address of the vault. The local controller restores the private key of the Bitcoin address of the vault from the local storage, and restores the value for the Bitcoin address in the register from the vault.
- The invention further provides a method of transacting bitcoin. A processor transfers a private key of the Bitcoin address of a vault to a local storage connected to the processor. The processor splits the private key of the Bitcoin address of the vault into a plurality of codes. The processor distributes the codes to remote distributed storage locations. The processor transfers a value of a Bitcoin address in a register to the vault. The processor receives at least some of the codes into which the private key of the Bitcoin address of the vault has been split. The processor assembles the codes that have been received into the private key of the Bitcoin address of the vault. The processor restores the private key of the Bitcoin address of the vault to the vault. The processor restores the value of the Bitcoin address in the register from the vault.
- The invention also provides a non-transitory computer-readable medium having stored thereon a set of instructions that are executable by a processor to carry out a method of transacting bitcoin. A processor transfers a private key of the Bitcoin address of a vault to a local storage connected to the processor. The processor splits the private key of the Bitcoin address of the vault into a plurality of codes. The processor distributes the codes to remote distributed storage locations. The processor transfers a value of a Bitcoin address in a register to the vault. The processor receives at least some of the codes into which the private key of the Bitcoin address of the vault has been split. The processor assembles the codes that have been received into the private key of the Bitcoin address of the vault. The processor restores the private key of the Bitcoin address of the vault to the vault. The processor restores the value of the Bitcoin address in the register from the vault.
- The invention further provides a host computer system for transacting bitcoin including a processor, a network interface device connected to the processor, a computer readable medium connected to the processor, a local storage on the computer readable medium and a set of instructions on the computer readable medium that are executable by the processor. The set of instructions includes a wallet, a plurality of Bitcoin addresses stored in the wallet, a first vault, and a local controller. The local controller is executable for selecting a first transfer set of the Bitcoin addresses for cold storage in the first vault, transferring at least a portion of each of the Bitcoin addresses of the first transfer set to a first vault while keeping the portions a first transaction set in the register, and restoring at least the portion of the Bitcoin addresses of the first transfer set from the first vault to the wallet and a wallet management module transacting using the Bitcoin addresses of the first transacting set without permitting transacting with the Bitcoin addresses of the first transfer set due to the portions thereof being restored to the first vault, and transacting using the Bitcoin addresses of the first transfer set due to the portions thereof being restored from the first vault to the wallet.
- The invention also provides a method of transacting bitcoin. A processor stores a plurality of Bitcoin addresses in a wallet. The processor selects a first transfer set of the Bitcoin addresses for cold storage in a first vault. The processor transfers at least a portion of each of the Bitcoin addresses of the first transfer set to the first vault while keeping the portions a first transaction set in the register. The processor transacts using the Bitcoin addresses of the first transacting set without permitting transacting with the Bitcoin addresses of the first transfer set due to the portions thereof being transferred to the first vault. The processor restores the portion of the Bitcoin addresses of the first transfer set from the first vault to the wallet. The processor transacts using the Bitcoin addresses of the first transfer set due to the portions thereof being restored from the first vault to the wallet.
- The invention further provides a non-transitory computer-readable medium having stored thereon a set of instructions that are executable by a processor to carry out a method of transacting. A processor stores a plurality of Bitcoin addresses in a wallet. The processor selects a first transfer set of the Bitcoin addresses for cold storage in a first vault. The processor transfers at least a portion of each of the Bitcoin addresses of the first transfer set to the first vault while keeping the portions a first transaction set in the register. The processor transacts using the Bitcoin addresses of the first transacting set without permitting transacting with the Bitcoin addresses of the first transfer set due to the portions thereof being transferred to the first vault. The processor restores the portion of the Bitcoin addresses of the first transfer set from the first vault to the wallet. The processor transacts using the Bitcoin addresses of the first transfer set due to the portions thereof being restored from the first vault to the wallet.
- The invention also provides a method of effecting payment including receiving, by a host computer system, a request for payment from a merchant computer system, including an amount in a currency, determining, by the host computer system, a first exchange rate, wherein the first exchange rate fluctuates and the first exchange rate is determined at a first moment in time, converting, by the host computer system, the amount in the currency to an amount in bitcoin using the first exchange rate at the first moment in time, receiving, by the host computer system, a send instruction from the customer computer system, wherein the send instruction is at a second moment in time later than the first moment in time and the exchange rate at the second moment in time is a second exchange rate that is different than the first exchange rate at the first moment in time, receiving, by the host computer system, payment in bitcoin from the customer in an amount that is based on the amount in bitcoin and transmitting, by the host computer system, in response to receiving the send instruction from the customer computer system, a payment instruction to pay currency to the merchant, wherein the currency paid to the merchant is for an amount that is at least in part based on the amount in the currency that is converted to bitcoin at the first moment in time even though the exchange rate is different at the second moment in time.
- The invention further provides a host computer system for effecting payment including a processor, a computer readable medium connected to the processor and a set of instructions on the computer readable medium that are executable by the processor. The set of instructions includes an application programmable interface (API) receiving a request for payment from a merchant computer system, including an amount in a currency, a currency converter determining a first exchange rate, wherein the first exchange rate fluctuates and the first exchange rate is determined at a first moment in time, and converting, by the host computer system, the amount in the currency to an amount in bitcoin using the first exchange rate at the first moment in time, transaction processor receiving a send instruction from the customer computer system, wherein the send instruction is at a second moment in time later than the first moment in time and the exchange rate at the second moment in time is a second exchange rate that is different than the first exchange rate at the first moment in time, and receiving a payment in bitcoin from the customer in an amount that is based on the amount in bitcoin and a bank transfer module transmitting in response to receiving the send instruction from the customer computer system, a payment instruction to pay currency to the merchant, wherein the currency paid to the merchant is for an amount that is at least in part based on the amount in the currency that is converted to bitcoin at the first moment in time even though the exchange rate is different at the second moment in time.
- The invention also provides a non-transitory computer-readable medium having stored thereon a set of instructions that are executable by a processor to carry out a method of transacting bitcoin including receiving, by a host computer system, a request for payment from a merchant computer system, including an amount in a currency, determining, by the host computer system, a first exchange rate, wherein the first exchange rate fluctuates and the first exchange rate is determined at a first moment in time, converting, by the host computer system, the amount in the currency to an amount in bitcoin using the first exchange rate at the first moment in time, receiving, by the host computer system, a send instruction from the customer computer system, wherein the send instruction is at a second moment in time later than the first moment in time and the exchange rate at the second moment in time is a second exchange rate that is different than the first exchange rate at the first moment in time, receiving, by the host computer system, payment in bitcoin from the customer in an amount that is based on the amount in bitcoin and transmitting, by the host computer system, in response to receiving the send instruction from the customer computer system, a payment instruction to pay currency to the merchant, wherein the currency paid to the merchant is for an amount that is at least in part based on the amount in the currency that is converted to bitcoin at the first moment in time even though the exchange rate is different at the second moment in time.
- The invention further provides a method of managing bitcoin, including establishing, by a host computer system, a vault and storing first and second electronic communication addresses in relation to the vault, storing, by the host computer system, bitcoin in the vault, receiving, by the host computer system, a request to transfer an amount of the bitcoin out of the vault, transmitting, by the host computer system, in response to the request, first and second messages over a network to the first and second addresses, detecting, by the host computer system, whether first and second authorization instructions are received due to one or more users reacting to the first and second messages sent to the first and second addresses and transferring, by the host computer system, the amount of bitcoin out of the vault only if both the first and second authorization instructions are detected.
- The invention also provides a non-transitory computer-readable medium having stored thereon a set of instructions which, when executed by a processor, executes a method including establishing, by a host computer system, a vault and storing first and second electronic communication addresses in relation to the vault, storing, by the host computer system, bitcoin in the vault, receiving, by the host computer system, a request to transfer an amount of the bitcoin out of the vault, transmitting, by the host computer system, in response to the request, first and second messages over a network to the first and second addresses, detecting, by the host computer system, whether first and second authorization instructions are received due to one or more users reacting to the first and second messages sent to the first and second addresses and transferring, by the host computer system, the amount of bitcoin out of the vault only if both the first and second authorization instructions are detected.
- The invention further provides a bitcoin management system, including a processor, a computer-readable medium connected to the processor and a set of instructions on the computer readable medium that are executable by the processor. The set of instructions includes a vault establishment wizard establishing a vault and storing first and second electronic communication addresses in relation to the vault, transaction processor storing bitcoin in the vault and a vault management module receiving a request to transfer an amount of the bitcoin out of the vault, transmitting, in response to the request, first and second messages over a network to the first and second addresses, detecting whether first and second authorization instructions are received due to one or more users reacting to the first and second messages sent to the first and second addresses, and instructing the transaction processor to transfer the amount of bitcoin out of the vault only if both the first and second authorization instructions are detected.
- The invention also provides a method of transacting bitcoin including storing, by a host computer system, a public key, receiving, by the host computer system, a request from a user computer system to transact using a bitcoin address, transmitting, by the host computer system, a verification script to the user computer system, the verification script including an authorization and a signature algorithm that is executable on the user computer system to sign the authorization with a private key to obtain a signed authorization that includes the signature and transmit the signed authorization to the host computer system, receiving, by the host computer system, the signed authorization including the signature from the user computer system, verifying, by the host computer system, the signature of the signed authorization received from the user computer system using a public key; and transacting, by the host computer system, with the bitcoin address, the transacting being permitted due to a successful verification of the signature but not upon an unsuccessful verification of the signature.
- The invention further provides a host computer system including a processor, a set of data and instructions on the computer-readable medium that are executable by the processor that are executable by the processor, a public key, a transaction processor receiving a request from a user computer system to transact using a bitcoin address, a verification script that is transmitted to the user computer system, the verification script including an authorization and a signature algorithm that is executable on the user computer system to sign the authorization with a private key to obtain a signed authorization that includes the signature and transmit the signed authorization to the host computer system, the host computer system receiving the signed authorization including the signature from the user computer system, and a verification module verifying the signature of the signed authorization received from the user computer system using a public key, the transaction processor transacting with the bitcoin address, the transacting being permitted due to a successful verification of the signature but not upon an unsuccessful verification of the signature.
- The invention also provides a host computer system including a processor, a network interface device connected to the processor, a computer readable medium connected to the processor and a set of instructions on the computer readable medium that are readable and executable by the processor. The set of instructions include an embedded code generator generating an embedded code for inclusion within a website of a partner computer system, the embedded code including a startup caller causing transmission of a startup call from the sender computer system to the host computer system, a startup call responder receiving the startup call from the sender computer system and transmitting, in response to the startup call, a tip button and a session script to the sender computer system, the session script being executable by the sender computer system to transmit a session call to the host computer system and a session responder transmitting, in response to the session call, at least one payment button and a payment script to the sender computer system, the payment button being selectable by the user of the sender computer system to execute the payment script, the payment script transmitting an instruction to a transaction processor to transfer funds from a sender account to a receiver account.
- The invention further provides a method of transferring funds including generating, by a host computer system, an embedded code for inclusion within a website of a partner computer system, the embedded code including a startup caller causing transmission of a startup call from the sender computer system to the host computer system, receiving, by the host computer system, the startup call from the sender computer system, transmitting, by the host computer system in response to the startup call, a tip button and a session script to the sender computer system, the session script being executable by the sender computer system to transmit a session call to the host computer system and transmitting, by the host computer system in response to the session call, at least one payment selection and a payment script to the sender computer system, the payment selection being selectable by the user of the sender computer system to execute the payment script, the payment script transmitting an instruction to a transaction processor to transfer funds from a sender account to a receiver account.
- The invention also provides a method of transacting bitcoin including executing, by a host computer system, a trading algorithm, including receiving sell offers for bitcoin from a sellers, receiving a buy offers for bitcoin from a buyers, creating respective matches wherein each match includes one of the buy offers and one of the sell offers, broadcasting each respective match over a multicast pipeline, receiving each respective match with a clearing module and clearing the respective match by updating an exchange database to reflect the respective match by transferring a representation of bitcoin from the seller to the buyer and transferring a representation of currency from the buyer to the seller.
- The invention further provides a system for transacting bitcoin including an order gateway receiving sell offers for bitcoin from a sellers and receiving a buy offers for bitcoin from a buyers, a matching engine creating respective matches wherein each match includes one of the buy offers and one of the sell offers, a multicast pipeline, the matching engine broadcasting each respective match over the multicast pipeline, an exchange database; and a clearing module receiving each respective and clearing the respective match by updating the exchange database to reflect the respective match by transferring a representation of bitcoin from the seller to the buyer and transferring a representation of currency from the buyer to the seller, thereby executing a trading algorithm.
- The invention is further described by way of example with reference to the accompanying drawings, wherein:
FIG. 1A is a block diagram of a network environment that includes the Bitcoin network and a number of systems forming part thereof or connected thereto;FIG. 1B is a block diagram of a first host computer system and a first and second user devices connected thereto;FIG. 2 is diagrammatic view of a first wallet that is held within a first host computer system inFIG. 1 ;FIG. 3 is a view similar toFIG. 2 , further illustrating a second wallet that has been established within the first host computer system;FIG. 4 is a view of an email that is received by the second user device inFIG. 1 ;FIG. 5 is a view of a browser displaying a user interface with fields for creating login details for the second wallet;FIGS. 6 to 30 are views similar toFIG. 5 that step a user of the second user device through a wallet set up;FIGS. 31 to 33 are views of the browser wherein the user interface discloses various tools that can be used by the user;FIGS. 34 to 37 are views of the browser wherein the user interface is used by the user to purchase bitcoin from the first host computer system;FIG. 38 is an email that is received by the second user device to confirm the purchase of the bitcoin from the first host computer system;FIG. 39 is an email that is received by the second user device with a notification that bitcoin has been added to their wallet as part of a referral bonus system;FIG. 40 is a view of the browser wherein the user interface displays “Limits and Verifications” associated with the second wallet;FIG. 41 is a view similar toFIG. 3 displaying transfer of bitcoin from the second wallet to the first wallet;FIGS. 42 and 43 are views of the browser when the user interface steps the user through the transfer of bitcoin from the second wallet to the first wallet;FIG. 44 is a view of the browser wherein the user interface displays Bitcoin addresses associated with transactions that have been completed;FIG. 45 is a view similar toFIG. 40 further showing the transfer of bitcoin from the second wallet to a third wallet that is connected to a second host computer system;FIG. 46 is a block diagram illustrating splitting of a private key of a vault and offline distribution;FIG. 47 is a block diagram illustrating removal of the private key of the vault;FIG. 48 is a block diagram illustrating offline or “cold” storage of values of Bitcoin addresses of a wallet in the vault;FIG. 49 is a block diagram illustrating isolation of the vault with its private key removed;FIG. 50 is a block diagram illustrating how the private key of the vault and the value of the Bitcoin addresses are restored;FIGS. 51 ato51dare block diagrams that illustrate how values of certain Bitcoin addresses in a wallet are removed and others are maintained;FIG. 52 is a graph illustrating how the wallet is maintained within a range so that only a portion of the wallet is “hot” in the sense that a user of the wallet can use the “hot” portion for transacting with another user;FIG. 53 is a block diagram that shows how an intermediate hot wallet is used to collect value from multiple wallets before transfer to a vault;FIG. 54 is a block diagram of a network environment that includes a customer computer system and merchant computer system;FIG. 55 is a block diagram illustrating functioning for purposes of locking an exchange rate in when processing a transaction made by the customer computer system on the merchant computer system inFIG. 54 ;FIG. 56 is a flow chart illustrating the establishment of a personal vault;FIG. 57 is a flow chart illustrating how bitcoin is transferred into and out of the vault;FIG. 58 is a block diagram of the first host computer system illustrating components that are used for establishing the vault and transferring bitcoin into and out of the vault;FIG. 59 is an email that is transmitted to verify a secondary email address;FIG. 60 is a view of a browser wherein a user interface displays options for transferring bitcoin out of a vault;FIGS. 61 and 62 are emails that are transmitted to primary and secondary email addresses to approve a withdrawal;FIG. 63 is a view of the browser with the user interface displaying a transaction status window;FIG. 64 is a block diagram illustrating the establishment of a user-controlled vault;FIG. 65 is a block diagram illustrating the user of the user-controlled vault for authorizing a transaction;FIG. 66 is a block diagram of an address generator that is used by the user-controlled vault;FIG. 67 toFIG. 71 are a block diagrams illustrating the functioning of a tip button;FIG. 72 is a block diagram of a system for transacting bitcoin according to an embodiment of the invention;FIGS. 73 ato73fillustrate the use of the system ofFIG. 72 for executing transfer-in, trading and withdrawal algorithms; andFIG. 74 is a block diagram of a machine in the form of a computer system forming part of the network environment.FIG. 1A of the accompanying drawings illustrates anetwork environment 10, including theBitcoin network 12, a firsthost computer system 14 within which the invention manifests itself, a secondhost computer system 16, first andsecond user devices Internet 22 to the firsthost computer system 14, a third user device24 connected to the secondhost computer system 16, a bitcoinexchange computer system 26 and aminer computer system 28.- The
Bitcoin network 12 includes ahost node 30 and a plurality ofremote nodes 32A to D that are connected to one another. The firsthost computer system 14 is connected to thehost node 30. The bitcoinexchange computer system 26 is connected to theremote node 32A. The secondhost computer system 16 is connected to theremote node 32B. Theminer computer system 28 is connected to theremote node 32D or could reside on the same computer system. - The first
host computer system 14 is used primarily for transacting bitcoin and, as shown inFIG. 1B , includes awebsite 34 having auser interface 36, alogin module 38, awallet establishment module 40, a plurality ofwallets 42, awallet management module 44 and a hostedemail module 46. Thelogin module 38 is connected to thewebsite 34 and the hostedemail module 46 is connected to thelogin module 38. Thewallet establishment module 40 is connected to thewallets 42. The hostedemail module 46 is connected via thewallet management module 44 to thewallets 42. As illustrated in the drawing, thefirst user device 18 is connected over theInternet 22 and theuser interface 36 to thelogin module 38. As further illustrated in the drawing, the hostedemail module 46 is connected over theInternet 22 to thesecond user device 20 and thesecond user device 20 is connected over theInternet 22 and theuser interface 36 to thewallet establishment module 40. - As shown in
FIG. 2 , the firsthost computer system 14 already has one wallet (Wallet A) stored among thewallets 42 corresponding to thefirst user device 18. The first wallet (Wallet A) includes an email address (email address A) and login details for the wallet. The first wallet (Wallet A) also includes a number of Bitcoin addresses (Bitcoin address 1; Bitcoin address 2) that have been created due to respective transfers or purchases (Transfer 1; Transfer 2). The first Bitcoin address (Bitcoin address 1) is created due to a purchase (Transfer 1) from a master wallet of the first host computer system14 (First Host) and is recorded for a value in an amount in bitcoin. The second Bitcoin address (Bitcoin address 2) is created due to a transfer (Transfer 2) from another location within theBitcoin network 12 having a network address outside of the firsthost computer system 14 and is recorded for a particular amount in bitcoin. The first wallet (Wallet A) was originally established by thewallet establishment module 40 inFIG. 1B . The email address (email address A) and login details of the first wallet were also recorded by thewallet establishment module 40. Thewallet establishment module 40 andwallet management module 44 were used to record the transfers and purchases (Transfer 1; Transfer 2), their Bitcoin addresses (Bitcoin address 1; Bitcoin address 2), their values and other details within the wallet. - A user of the
first user device 18 inFIG. 1B may use a mobile application on thefirst user device 18 to communicate over theInternet 22 directly with thelogin module 38 or may use a browser on thefirst user device 18 to communicate via theInternet 22 and thewebsite 34 with thelogin module 38. A browser application on thefirst user device 18 transmits a user interface request over theInternet 22 to thewebsite 34. Thewebsite 34 responds to the user interface request by transmitting theuser interface 36 over theInternet 22 to thefirst user device 18. Theuser interface 36 is then displayed on thefirst user device 18. Theuser interface 36 includes fields for entering login credentials, which are then transmitted from thefirst user device 18 over theInternet 22 to thelogin module 38. Thelogin module 38 verifies whether the login credentials match the login details for the wallet (Wallet A). If the login credentials match the login details, then thelogin module 38 logs thefirst user device 18 into the wallet (Wallet A) inFIG. 2 . If the login credentials do not match the login details, then thefirst user device 18 is not logged in to the wallet. - If the
first user device 18 inFIG. 1B is logged in to the wallet, thelogin module 38 also provides access for thefirst user device 18 to the hostedemail module 46 and transmission of an email by a user of thefirst user device 18 to an email address of thesecond user device 20. Theuser interface 36 provides a field for entering the email address of thesecond user device 20. Theuser interface 36 also includes a field for entering an amount in bitcoin (or an amount in local currency that is converted to bitcoin using an exchange rate) that is being transferred from the wallet (Wallet A) corresponding to thefirst user device 18 to a respective wallet among thewallets 42 corresponding to thesecond user device 20 that has not yet been established at this point in time. The user of thefirst user device 18 then uses the hostedemail module 46 to send an email at50 to thesecond user device 20. The hostedemail module 46 simultaneously at52 instructs thewallet establishment module 40 to establish a wallet corresponding to the email address within thewallets 42. The hostedemail module 46 simultaneously instructs thewallet management module 44 to record the amount of bitcoin that is being transferred from the wallet (Wallet A) within the wallet corresponding to the email address. FIG. 3 illustrates further activity within thewallets 42 due to the email represented by a third transfer (Transfer 3). When the user of the first wallet (Wallet A) transmits the email, the system uses an existing Bitcoin address (Bitcoin address 2) to which the outgoing transfer is charged. Associated with the transfer (Transfer 3) are the email address to which the email has been transmitted, the amount in bitcoin, a miner's fee of zero bitcoin that is paid by the firsthost computer system 14 to any miner computer system such as theminer computer system 28 inFIG. 1A , and a host fee of zero bitcoin that are charged to the wallet (Wallet A) for the transfer. A second wallet (Wallet B) is established by thewallet establishment module 40 and the email address (email address B) of thesecond user device 20 is recorded as an identifier of the wallet (Wallet B). A Bitcoin address (Bitcoin address 3) is recorded within the second wallet (Wallet B) for the transfer (Transfer 3). Within the second wallet (Wallet B), the transfer (Transfer 3) has the Bitcoin address (Bitcoin address 3), the identifier of the wallet (Wallet A) from where the funds are transferred associated therewith, and the amount in bitcoin that has been transferred. The amount in bitcoin corresponding to the transfer (Transfer 3) of both wallets (Wallet A; Wallet B) is the same, consistent with double entry accounting principles. The second wallet (Wallet B) so far has no login details or any other user information and has not been accessed by a user of thesecond user device 20 at this point in time.FIG. 4 illustrates the email when it is received at thesecond user device 20 inFIG. 1B . The email is received and viewed within an email application on thesecond user device 20. The email includes a link (“Click here to sign in and claim this amount”) that, when selected by the user of thesecond user device 20, transmits a user interface request from the browser on thesecond user device 20 over theInternet 22 to thewebsite 34. Thewebsite 34 responds to the user interface request to transmit theuser interface 36 over theInternet 22 to thesecond user device 20 for viewing within the browser.FIG. 5 illustrates theuser interface 36 as displayed on thesecond user device 20 inFIG. 1B . Theuser interface 36 includes a plurality of fields for the user of thesecond user device 20 to enter login details for the second wallet (Wallet B), including a password and a confirmation of the password. After the user has entered a password, the user can access their wallet by selecting the button “Access My Wallet”. Thewallet establishment module 40 inFIG. 1B stores the login credentials in association with the second wallet (Wallet B). Thelogin module 38 also logs thesecond user device 20 into the second wallet (Wallet B). If the user is logged out, the user can be provided with a login page where the user can enter login credentials that are compared with the login details in the second wallet (Wallet B) and then log into the second wallet (Wallet B) following a favorable match between the login credentials and the login details.FIG. 6 shows a view that is displayed on thesecond user device 20 inFIG. 1B . The user is already logged into the wallet, as shown in the top right. The user can accept or decline an agreement.FIG. 7 displays the first page that is displayed to the user following acceptance of the agreement. The page shows the current balance corresponding to the amount of bitcoin at the Bitcoin address (Bitcoin address 4) inFIG. 3 . The user can select various tools down the left margin, including sending or requesting bitcoin, buying or selling bitcoin, account settings and various merchant tools.FIG. 8 illustrates a view that is displayed to the user if the user selects the “Buy/Sell” link inFIG. 7 . The user is prompted to add a bank account.FIGS. 9 through 15 step the user through the entry of bank account details and verification of the bank account. The user can also select a credit card as a backup payment.FIGS. 16 to 19 step the user through the entry of a credit card number and a billing address, andFIGS. 20 and 21 step the user through a verification process to verify that the user is in control of the credit card account.FIGS. 22 and 23 request additional information from the user.FIG. 23 also allows the user to verify a phone at a phone number andFIGS. 24 through 27 step the user through a process for verifying their phone and phone number.FIGS. 28 through 30 illustrate a process for verifying an identity of the user of thesecond user device 20. As illustrated inFIGS. 31 to 33 , the top margin within the account settings allow for additional tools such as referrals (FIG. 31 ), viewing of Bitcoin addresses (FIG. 32 ), and integration with an application programmable interface (FIG. 33 ).FIG. 34 illustrates a process that is initiated by the user to purchase bitcoin from a wallet of the firsthost computer system 14. In the present example, the user selects one (1) bitcoin (BTC) to purchase.FIGS. 35 and 36 step the user through the process of purchasing the bitcoin. Once the bitcoin is purchased, the user can select on “History” tab in the top margin to display a view as shown inFIG. 37 wherein the transaction is displayed and is marked as “PENDING”.FIG. 38 shows an email that is transmitted by the hostedemail module 46 inFIG. 1B to thesecond user device 20 to confirm the purchase of the bitcoin following selection of a “Confirm” button inFIG. 35 . The email also has a link that, when selected by the user, opens the browser on thesecond user device 20 and allows the user to login to their wallet and view the transaction.FIG. 39 shows an email that is transmitted by the hostedemail module 46 inFIG. 1B to thesecond user device 20 with a notification that bitcoin has been added to their wallet as part of a referral bonus system.FIG. 40 illustrates a view that is displayed when the user selects a “Limits and Verifications” tab in the top margin of the “Buy/Sell” page.- When the user selects the “Send/Request” link in the left margin in
FIG. 40 , the user is provided an option to send bitcoin from their wallet (Wallet B) inFIG. 3 to another wallet (e.g. the first wallet (Wallet A)) inFIG. 3 . FIG. 41 illustrates further transfers or purchases (Transfer 4;Transfer 5; Transfer 6). The fourth transfer (Transfer 4) represents the purchase of bitcoin from the first host computer system's14 master wallet.- The fifth transfer (Transfer 5) represents the transfer of bitcoin from the second wallet (Wallet B) to the first wallet (Wallet A). The second wallet (Wallet B) now has login details stored therein. If the
second user device 20 inFIG. 1B has been logged out of the second wallet (Wallet B), then thesecond user device 20 is first directed to thelogin module 38 which receives login details for the second wallet (Wallet B) from thesecond user device 20, verifies whether the login credentials for the second wallet (Wallet B) match the login details for the second wallet (Wallet B). If the login details match the login credentials, then thelogin module 38 logs thesecond user device 20 into the second wallet (Wallet B). - The
login module 38 then provides thesecond user device 20 with access to the hostedemail module 46. The user of thesecond user device 20 then enters the email address (email address A) of the user of the first wallet (Wallet A) and an amount of bitcoin that the user of thesecond user device 20 wishes to transfer from the second wallet (Wallet B) to the first wallet (Wallet A). The user of thesecond user device 20 then uses the hostedemail module 46 to send an email via theInternet 22 to thefirst user device 18. As soon as the email is sent, a transfer (Transfer 5) is recorded within the second wallet (Wallet B). Because one of the Bitcoin addresses (Bitcoin address 4) has funds associated therewith, it can be charged for the transfer (Transfer 4). Within the second wallet (Wallet B) the transfer (Transfer 4) has the email address (email address A) to which the email has been sent and the amount in bitcoin associated therewith. - As indicated, the miner's fee that is paid by the first
host computer system 14 and the host fee that is charged for the transfer are zero bitcoin because the first wallet (Wallet A) is stored within thewallets 42 of the firsthost computer system 14. The user of thefirst user device 18 receives the email indicating the transfer of bitcoin to their wallet (Wallet A). A Bitcoin address (Bitcoin address 5) is recorded within the first wallet (Wallet A) for the transfer (Transfer 5) together with the identifier of the second wallet (Wallet B) from which the transfer has been made and the amount in bitcoin. The amount in bitcoin corresponding to the transfer (Transfer 4) in the second wallet (Wallet B) is the same as the amount in bitcoin as in the first wallet (Wallet A). - As illustrated by the next transfer (Transfer 6), the user of the second wallet (Wallet B) can opt to send bitcoin to a Bitcoin address of the first wallet (Wallet A). The transfer (Transfer 6) is the same as the preceding transfer (Transfer 5) in all other respects.
FIG. 42 shows a view that is displayed to the user of thesecond user device 20 inFIG. 1B in order to make the transfer from their wallet (Wallet B) to the first wallet (Wallet A). The view includes a field for the user to enter the email address (email address A) and fields for entering either an amount in bitcoin (BTC) or an amount in a local currency (USD—United States Dollar). The exchange rate between bitcoin and the local currency is shown in the top left corner. The view also includes a button “Send Money” which, when selected by the user, initiates the transfer of bitcoin.FIG. 43 is a view that is displayed to the user indicating transactions that have been initiated or completed. The purchase of bitcoin discussed with reference toFIGS. 35 to 37 is shown as “PENDING”. A block chain verification notice has to be broadcast by theminer computer system 28 and be received by the firsthost computer system 14 inFIG. 1A before a determination is made to change the marker “PENDING” to “COMPLETE”. The other transactions representing transfers between the first and second wallets (Wallet A and Wallet B) inFIG. 41 are shown as completed because they do not need block chain verification outside of the firsthost computer system 14. No block chain verification notice is thus required for these transactions to be marked “COMPLETE”.FIG. 44 shows a view that can be selected by the user by selecting a tab in the top margin wherein the user is shown the Bitcoin addresses associated with transactions that have been completed.FIG. 45 illustrates a further transaction (Transfer 7) wherein bitcoin is transferred from the second wallet (Wallet B) to a third wallet (Wallet C) held by the secondhost computer system 16 inFIG. 1A . The user of thesecond user device 20 enters a bitcoin address (Bitcoin address 6) that is located in the third wallet (Wallet C) and an amount of bitcoin to be transferred to the third wallet (Wallet C). A transfer (Transfer 7) is recorded within the second wallet (Wallet B). Associated with the transfer (Transfer 7) are the Bitcoin address (Bitcoin address 6), the amount in bitcoin that is being transferred and a miner's fee that is charged for the transfer and has to be paid by the firsthost computer system 14 to theminer computer system 28 inFIG. 1A . No fee is charged by the firsthost computer system 14 for a transfer to another Bitcoin address.- When the user of the
second user device 20 inFIG. 1A completes the purchase, a transfer instruction is created and is broadcast via thehost node 30 to allremote nodes 32A-D within theBitcoin network 12. The transfer instruction thus traverses the first node and the secondremote node 32B to reach the secondhost computer system 16. The secondhost computer system 16 and all other computer systems connected to theremote nodes 32A-D record the transfer (Transfer 7) with respect to the Bitcoin addresses (Bitcoin address 4; Bitcoin address 6). The transfer (Transfer 7) has associated therewith the amount in bitcoin. - The transfer instruction that results in the transfer (Transfer 5) thus results in no miner's fee being charged to and paid by the first
host computer system 14. No host fee is charged to the second wallet (Wallet B) because the transfer (Transfer 7) is made to another wallet (Wallet A) within thewallets 42 of the firsthost computer system 14. By contrast, the transfer instruction that results in the transfer (Transfer 7) representing the transfer to the Bitcoin address (Bitcoin address 6) in the third wallet (Wallet C) results in a miner's fee that is paid by the firsthost computer system 14 to theminer computer system 28. Theminer computer system 28 is responsible for verifying transfers of bitcoin over theBitcoin network 12. In the present scenario, theminer computer system 28 verifies the transfer of bitcoin from the second wallet (Wallet B) to the third wallet (Wallet C). - Another transfer may comprise that bitcoin is sent to one of the nodes,
e.g. node 32C. Thenode 32C could be a fourth user device which is owned by the recipient of the bitcoin transfer having its own bitcoin address. FIG. 46 illustrates components that are used for cold storage of value of bitcoin, including alocal storage 56, alocal controller 58, avault 64, asplitter 66, one ormore encryption algorithms - The
vault 64 has aBitcoin address 80 with aprivate key 79. Theprivate key 79 is, for purposes of illustration, shown as a nine digit sequence of characters that are provided to thesplitter 66. For purposes of illustration, thesplitter 66 splits the nine digits of theprivate key 79 into seven overlapping codes (Codes 1 to 7). Theencryption algorithm 68 encrypts the first code (Code 1) into an encrypted code (Encrypted Code 1). In a similar manner, the second code (Code 2) is encrypted by an encryption algorithm (not shown) into an encrypted code (Encrypted Code 2). Each one of the seven codes is encrypted into a separate encrypted code. A separate key may be used for each one of seven codes. Alternatively, a separate encryption algorithm may be used for each one of the seven codes. - Once all the codes have been encrypted, the offline distribution module72 transmits each one of the encrypted codes (Encrypted
Code 1 to 7) to a separate location. The locations are remote locations that are geographically separated from one another. The offline distribution module72 may also be used to print one or more of the encrypted codes for paper delivery to respective remote locations. FIG. 47 illustrates functioning of the offline distribution module72 following distribution of the encrypted codes inFIG. 46 . The offline distribution module72 removes theprivate keys 79 of theBitcoin address 80 of thevault 64. The offline distribution module72 also removes theprivate key 79 of theBitcoin address 80 within thelocal storage 56.- As shown in
FIG. 48 , alocal register 60 includes a plurality ofwallets 42, one of which is shown. Thewallet 42 has a plurality of Bitcoin addresses74,76 and78 associated therewith. EachBitcoin address local controller 58 transfers the entire value of the Bitcoin addresses76 and78 into thevault 64. The value relating to theBitcoin address 74 is not transferred into thevault 64. Thelocal controller 58 calculates the total value of the Bitcoin addresses76 and78 that have been transferred into thevault 64 and records the total value in thelocal storage 56 in association with theBitcoin address 80. - As shown in
FIG. 49 , following removal of the value of the Bitcoin addresses76 and78 within thewallet 42, the value of the Bitcoin addresses76 and78 are only held within thevault 64 and thelocal storage 56. Theprivate key 79 is only held in a split and encrypted form at the distributed locations where the offline distribution module72 inFIG. 46 has distributed them to. Unless access can be gained to theprivate key 79 that has now been split and distributed, it is not possible to access the value of the Bitcoin addresses76 and78. It is now possible for a user to which thewallet 42 is registered to use theBitcoin address 74 for transacting with another user via thewallet management module 44 inFIG. 1B . The Bitcoin addresses76 and78 are not usable by thewallet management module 44 for purposes of transacting with another user at this time because their values, within thewallet 42, have been removed. FIG. 50 shows how the private keys of thevault 64 and the Bitcoin addresses76 and78 that were removed inFIG. 46 are restored. Components that are provided for restoration include a plurality ofrestoration interfaces more decryption algorithms assembler 94. The holder of the first encrypted code (Encrypted Code 1) is called upon to enter the encrypted code into therestoration interface 82. Therestoration interface 82 may for example be a web page with a field for entry of the first encrypted code. Alternatively, therestoration interface 82 may be an application programmable interface (API) and the first encrypted code can be entered into the API with or without human involvement.- In the given example, the second, third, fifth and sixth encrypted codes are not received at this time. The fourth and seventh encrypted codes are received through the restoration interfaces84 and86, similar to the first encrypted code.
- The
decryption algorithm 88 decrypts the first encrypted code (Encrypted Code 1) into the first code (Code 1). In the given example, thedecryption algorithms Code 4 and Encrypted Code 7) into the fourth and seventh codes (Code 4 and Code 7) respectively. In the given example, three codes are the minimum number of codes that are required in order to reassemble theprivate key 79. The minimum number of codes required for reassembly inFIG. 48 is thus less than the total number of codes into which theprivate key 79 has been split inFIG. 46 . Theassembler 94 assembles theprivate key 79 when the minimum number of codes has been received. - The
private key 79 of theBitcoin address 80 in thelocal storage 56 is used to access thevault 64. Thelocal controller 58 then restores theprivate key 79 from the local storage into the vault for association with the Bitcoin address. The block chain will know whether theprivate key 79 that has been restored is the sameprivate key 79 that was previously associated with the Bitcoin address. Only upon confirmation from the block chain will it be possible to transfer the value from thevault 64 to thelocal register 60. - The
local controller 58 restores the respective value of the Bitcoin addresses76 and78 in thevault 64 to the Bitcoin addresses76 and78 in thewallet 42. Because the values have been restored to the Bitcoin addresses76 and78 in thewallet 42 they are usable for transacting with other users. FIGS. 51 ato51dillustrate the use of a “hot” wallet in combination with “cold storage”. As shown inFIG. 51 a, thewallet 42 has the Bitcoin addresses74,76,78 and afurther Bitcoin address 98, each having a respective value associated therewith. Thelocal storage 56 has first, second and third Bitcoin addresses80A to80C for first, second andthird vaults 64A to64C, respectively. The Bitcoin addresses76 and78 form a first transfer set that is selected for cold storage. The Bitcoin addresses74 and98 form a first transacting set. The values of the Bitcoin addresses76 and78 of the first transfer set are transferred into thefirst vault 64A, as represented by “Value” in thefirst vault 64A.- The private key of the
Bitcoin address 80A of thefirst vault 64A is then transferred into thelocal storage 56 and is stored in association with thefirst Bitcoin address 80A. As hereinbefore described with reference toFIG. 46 , the private key of theBitcoin address 80A in thelocal storage 56 is then split and distributed. As hereinbefore described with reference toFIGS. 47 and 48 , the private keys of theBitcoin address 80 and the value of theBitcoin address wallet 42 to use theBitcoin address wallet 42. FIG. 51 bshows the Bitcoin addresses76 and78 within thewallet 42 with their values removed and theBitcoin address 80A within thelocal storage 56 with its private key removed. The private key of theBitcoin address 80B ofsecond vault 64B is transferred into thelocal storage 56 and associated with thesecond Bitcoin address 80B within thelocal storage 56. The private key of thesecond Bitcoin address 80B in thelocal storage 56 is split and distributed and then removed from thelocal storage 56. TheBitcoin address 98 is selected as part of a second transfer set of one or more Bitcoin addresses. The value of theBitcoin address 98 is transferred from thewallet 42 into thesecond vault 64B, as represented by “Value” in thesecond vault 64B. The value of theBitcoin address 98 within thewallet 42 is thus removed. The user of thewallet 42 can now not use theBitcoin address 98 for purposes of transacting with another user because the value of theBitcoin address 98 has been removed from thewallet 42. TheBitcoin address 74 forms part of a second transacting set that may include one or more Bitcoin addresses that can be used for transacting with another user.FIG. 51 cshows theBitcoin address 98 having its value removed and thesecond Bitcoin address 80B within thelocal storage 56 having its private key removed. At this stage it may be desirable to restore the values of the Bitcoin addresses76 and78. The private key of thefirst Bitcoin address 80A within thelocal storage 56 is restored to thevault 64 as hereinbefore described with reference toFIG. 50 . The respective values of the Bitcoin addresses76 and78 are then restored from thevault 64A to the Bitcoin addresses76 and78 in thewallet 42. Because the values of the Bitcoin addresses76 and78 are restored within thewallet 42, the Bitcoin addresses76 and78 of the first transfer set can, at least for the time being, be used together with the second transacting set for transacting with another user.- The same Bitcoin addresses74,76,78 and98 that are shown in
FIG. 51 aare also shown inFIGS. 51 band51c. It should be understood that the Bitcoin addresses may change between the figures. The system allows for the value that was previously associated with one Bitcoin address to be restored to another Bitcoin address if necessary. - As shown in
FIG. 51 d, thefirst vault 64A is discarded after the value therein is restored. Thefirst Bitcoin address 80A within thelocal storage 56 and thefirst vault 64A will never be used again. - The
Bitcoin address 78 is selected as a third transfer set. The private key of theBitcoin address 80C of thethird vault 64C is transferred into thelocal storage 56 and stored in association with athird Bitcoin address 80C. The value of theBitcoin address 78 is transferred from thewallet 42 to thethird vault 64C. The user of thewallet 42 can now not use theBitcoin address 78 for transacting with another user. TheBitcoin address 76 forms part of a third transacting set that could include one or more Bitcoin addresses. TheBitcoin address 76 can be used by the user of thewallet 42 for transacting with another user because the value of theBitcoin address 76 is associated therewith within thewallet 42. The second and third transacting sets can thus be used by the user for transacting with another user. The second and third transfer sets are unusable for transacting with another user because their private keys have been removed. FIG. 52 illustrates how the local controller58 (seeFIGS. 46 to 50 ) maintains transaction sets of awallet 42 within atarget range 101. Should all the Bitcoin addresses of thewallet 42 have values associated therewith, thewallet 42 is said to be 100% hot and 0% cold. If all the Bitcoin addresses in awallet 42 have their values removed, thewallet 42 is to be 0% hot and 100% cold. Thetarget range 101 for the total bitcoin value within the wallet may for example be 5% to 10% hot. At102, the values of the first transacting set are transferred from thewallet 42 as described with reference toFIG. 51 a. At104, the user transacts with some of the Bitcoin addresses and the total value within thewallet 42 of the Bitcoin addresses that are hot is reduced. At106, the values of the second transfer set are removed from thewallet 42 as described with reference toFIG. 51 b. At108, the values of the first transfer set are restored as described with reference toFIG. 51 c. At110, the user transacts and gains further Bitcoin addresses for additional value within theirwallet 42. At112, values of the third transfer set are transferred out of thewallet 42 as described with reference toFIG. 51 d. It can thus be seen that thelocal controller 58 inFIGS. 46 to 50 adjusts the total value of bitcoin that is not within thetarget range 101. Thelocal controller 58 typically recalculates the hot/cold value ratio of each wallet on a daily basis and automatically adjusts the value to thetarget range 101.FIG. 53 illustrates the use of an intermediatehot wallet 114 that is used to collect bitcoin values from a plurality ofwallets 42A to C. Thewallet 42A is that same as thewallet 42 as described above. Thewallet 42B has bitcoin addresses120,122,124 and126 associated therewith. Thewallet 42C has bitcoin addresses128,130,132 and134 associated therewith. Eachwallet 42A, B or C is held within thetarget range 101 inFIG. 50 . The values of the bitcoin addresses76,78,120,122,128 and130 are identified for transfer to thevault 64A and are first transferred or “swept” to the intermediatehot wallet 114 from where they are transferred to thevault 64A.FIG. 54 illustrates anetwork environment 136 that, in addition to the firsthost computer system 14, includes a customer computer system138 and amerchant computer system 140 that are connected to one another over theInternet 142. Themerchant computer system 140 has anonline store 144 and awebsite 146. The customer computer system138 has abrowser 148. A customer at the customer computer system138 can use thebrowser 148 to access thewebsite 136 over theInternet 142. Thewebsite 136 is then displayed on thebrowser 148. Thewebsite 136 allows for the customer to make purchase on theonline store 144. The customer may, for example, purchase real goods, virtual goods or services from theonline store 144.- The first
host computer system 14 includes an application programmable interface (API)150, areference code generator 152, atransaction processor 154, acurrency converter 156 and merchant, and customer andhost wallets wallets - As shown in
FIG. 55 , the customer is shown a shopping cart with several payment options, including “Pay with Credit Card” and “Pay with bitcoin.” Prior to being displayed the shopping cart, the customer has traveled through the shopping flow of themerchant computer system 140, has selected one or more items to be purchased and has selected a shopping or checkout cart, which causes the display of the view shown inFIG. 55 . When the user selects the button “Pay with bitcoin” themerchant computer system 140, at166, transmits an API call to the firsthost computer system 14. The API call includes a request for payment. The request for payment includes an amount in a currency, in the present example $14.00, an order name (usually a number), order descriptions (usually items in the checkout cart in a single line-item entry separated by commas), and a success uniform resource locater (URL) if desired (a page to which the customer is redirected at checkout if the order completes). - When the first
host computer system 14 receives the API call at166, thereference code generator 152 generates a unique reference code for the specific order. The reference code is thus uniquely generated for each API call. The firsthost computer system 14 then stores the reference code in its database. At168, the firsthost computer system 14 responds to the API call received at166 to transmit the reference code to themerchant computer system 140. Themerchant computer system 140 then receives the reference code asreference code 170. Themerchant computer system 140 stores the reference code asreference code 172 within itsaccounting system 173 and associates thereference code 172 with the particular order shown in the shopping cart. Themerchant computer system 140 also creates aURL 174. Thereference code 170 is used as areference code 176 within theURL 174 when theURL 174 is created. - The first
host computer system 14 creates aURL 180 that includes a reference code182. The reference code182 and thereference code 176 are the same. - The
merchant computer system 140 at178 redirects the browser148 (FIG. 54 ) using theURL 174. The browser is then redirected to theURL 180 of the firsthost computer system 14. - The
URL 180 may, for example, be the URL of a landing page, iFrame ormodal window 184. The landing page, iFrame ormodal window 184 presents checkout options to the customer, including to pay with the customer wallet160 if one exists, to pay with bitcoin using an external account, or to create a wallet at the firsthost computer system 14 for purposes of completing the purchase. In a different embodiment, instead of being automatically redirected by themerchant computer system 140 to thefirst computer system 14, the customer may be redirected to a different page at themerchant computer system 140, which will then contain a link for the customer to navigate to the landing page, iFrame ormodal window 184. - When the
browser 148 of the customer computer system138 downloads the landing page, iFrame ormodal window 184, the firsthost computer system 14 automatically generates abitcoin address 186 specifically for the customer's order within themerchant wallet 158. - The first
host computer system 14 also creates a bitcoin price based on the price in local currency and displays the bitcoin price within the landing page/iFrame ormodal window 184 within thebrowser 148. The graph illustrates a fluctuating bitcoin to dollar exchange rate. In the present example, the exchange rate atminute 0 is used at190 to calculate the exchange rate. The local currency price in the present example is $14.00 which gives a bitcoin price of 0.02 BTC. The price of 0.02 BTC that is based on the exchange rate atminute 0 is maintained for a select period of time, in the present example 10 minutes, before it resets. The customer may not wish to immediately send the bitcoin, but may do so at any time before the price resets atminute 10 and the exchange rate remains locked in and the bitcoin price thus remains unchanged at 0.02 BTC during that time. - An option is displayed to the customer to send the bitcoin together with the price in bitcoin at
minute 0. When the customer selects the option to send the bitcoin, the customer computer system138 transmits a send instruction to the firsthost computer system 14. The firsthost computer system 14 receives and at192 detects the send instruction. The customer may for example request to send bitcoin from the customer wallet160 or via another path as hereinbefore described. The firsthost computer system 14 responds to the send instruction to transmit an order status message that includes the reference code for the transaction to themerchant computer system 140. Themerchant computer system 140 receives the reference code asreference code 194. Themerchant computer system 140 then matches thereference code 194 to thereference code 172 within itsaccounting system 173 and marks the transaction as complete. - In the present example, the send instruction is processed at
minute 6. The exchange rate has in the present example changed betweenminute 0 andminute 6. Should the bitcoin price of 0.02 BTC be converted to local currency at this time it would result in a different price in local currency than the original transaction. The difference between the original price atminute 0 andminute 6 represents either a loss or a gain for the firsthost computer system 14. The loss and gain is used to calculate bitcoin replacement costs on a periodic basis. - In the present example the
first computer system 14 responds to the send instruction received at192 to transmit 0.02 BTC to thebitcoin address 186 associated with themerchant wallet 158. When the bitcoin reaches thebitcoin address 186, the firsthost computer system 14, at196, immediately purchases the bitcoin from themerchant wallet 158, resulting in a transfer of the bitcoin from themerchant wallet 158 to thehost wallet 162. The firsthost computer system 14 purchases the bitcoin at the exchange rate locked in atminute 0. - Periodically, for example daily, the first
host computer system 14 calculates the total amount of bitcoin sold by themerchant wallet 158 that day at the locked in prices. The firsthost computer system 14 has abank transfer module 200 that, at202, transmits a payment instruction to a bank for the firsthost computer system 14. The bank for the firsthost computer system 14 communicates with a bank of themerchant computer system 140. Such communication, at204, results in transfer of funds from ahost bank account 206 to amerchant bank account 208. - In the present example, the customer uses their customer wallet160 to transfer funds in the form of bitcoin from the customer wallet160 to the
merchant wallet 158 and the funds are then transferred in the form of bitcoin from themerchant wallet 158 to thehost wallet 162. In another embodiment, themerchant wallet 158 can be bypassed such that the customer transfers funds in the form of bitcoin from the customer wallet160 directly into thehost wallet 162. In either embodiment the funds that are received by thehost wallet 162 are used as a basis for calculating the amount of money in local currency that is transferred by thebank transfer module 200, minus a fee that is held back by the firsthost computer system 14 for purposes of processing the transaction. - Referring again to
FIG. 54 , theAPI 150 sends and receives API calls at166,168 and the order status message in response to thesend instruction 192 inFIG. 55 . Thecurrency converter 156 is responsible for receiving and maintaining exchange rate for bitcoin to local currency and for calculating the bitcoin price based on the local currency price and the exchange rate at any particular moment in time. Thetransaction processor 154 is responsible for transferring funds in the form of bitcoin or local currency from one wallet or bank account to another. - In the embodiment above, the exchange rate is locked in when the customer accesses the landing page, iFrame or
modal window 184 and is locked for ten minutes. In such an embodiment the merchants typically create a payment “button” or using the API, specifically the button API, of the first host computer system. Selection of the button by the customer results from the process described above wherein the customer is directed to the landing page, iFrame ormodal window 184. Such a button does not need to look any different from the merchant's standard “submit order” button and the button API is linked into the standard “submit order” button of themerchant computer system 140, which when clicked will direct the user directly to the landing page, iFrame ormodal window 184. When the user hits the landing page the exchange rate is locked. The merchant “order” is thus not created—i.e., with locked in exchange rate—until the user clicks the payment button to land on our landing page. - Another embodiment is used in white-label solutions. In these instances, the user is not directed away from the merchant domain to a landing page such as the landing page, frame or
modal window 184 to complete payment. Instead, the checkout information that would have otherwise shown on the landing page is displayed inside the merchant's browser checkout tool. Such an embodiment may not allow “one-click” checkout for users who are already signed into their customer wallet160; a user can only pay by QR code scan and/or manual entry of a bitcoin address. In order for this information to be incorporated into the merchant's webpage, the merchant (1) creates a “button” when they post an item for sale to the website (the button includes the price in local currency, but not a bitcoin price and can be created at any time—e.g., weeks before a purchase); and (2) when the customer wishes to pay, e.g., by clicking on a “Place Order” button, themerchant computer system 140 sends an API call to the firsthost computer system 14 which responds by sending back a locked in exchange rate, which again is good for ten minutes. The merchant then displays the checkout information to the user—i.e., the proper bitcoin address and amount. This embodiment differs in that: (1) the “order” is created earlier in time, and the exchange rate follows on as a separate API call; and (2) the checkout information is hosted within the merchant's domain. FIG. 56 illustrates a method of managing bitcoin wherein a personal vault is created for a user. At220, the user already has an account that the user can log into using a website. The account has a first email (electronic communication) address. The first email address may be john.smith@gmail.com. The account also has a phone number associated therewith and one or more wallets as herein before described. The website provides the user with a link to create a vault. At222, the user is provided an option to create an individual vault or a group vault. In an individual vault the user will be required to respond to two emails in order to transfer bitcoin out of the vault. In a group vault multiple users are required to respond to emails in order for the user of the account represented at220 to transfer the bitcoin out of the vault.- The user may, at224, select an individual vault. At226, an interface of the website is presented with a field for the user to enter a second email address. The second email address may for example be john.smith@hotmail.com. The user enters the second email address and selects a button to transmit the second email address from their device to the first
host computer system 14. When the firsthost computer system 14 receives the second email address, the firsthost computer system 14, at228, transmits a confirmation email with a confirmation link to the second email address. The purpose of the email that is transmitted at228 is to confirm the second email address. At230, the firsthost computer system 14 waits for the confirmation. The firsthost computer system 14 does not proceed to create a vault if the confirmation is not received. At232, the user selects the confirmation link, which causes transmission of the confirmation from the device of the user to the firsthost computer system 14. When the firsthost computer system 14 receives the confirmation, the firsthost computer system 14 proceeds at232 to register a vault within the same account shown at220. The vault includes the first and second email addresses. The vault also includes the phone number of the account. - At236, the first
host computer system 14 updates the interface of the website to provide a summary. The summary indicates that, in order to transfer bitcoin out of the vault, emails will be sent to the first and second email addresses, and the summary includes the phone number associated with the vault and that the bitcoin will not be transferred out of the vault for a period of 48 hours. The interface also includes a “Finish” button. When the user selects the “Finish” button, the browser used by the user, at238, lands in the vault. The vault looks like a wallet, but has a security feature that limits transfer of bitcoin out of the vault. - The user may, at240, select a group vault. At242, the first
host computer system 14 provides the user with an option whether 2 out of 3 confirmations are required or 3 out of 5 confirmations are required. If the user selects that 2 out of 3 confirmations are required, then the user is required to enter two email addresses in addition to their own email address shown in the account at220. If the user selects that 3 out of 5 confirmations are required, then the user is required to enter four email addresses in addition to their email address shown in the account at220. - At224, the interface of the website is updated to request the additional email addresses from the user. The interface typically includes fields for the user to enter the additional email addresses.
- At246, the first
host computer system 14 makes a determination whether all the additional email addresses are associated with other accounts within the firsthost computer system 14. If all the additional email addresses are associated with other accounts, then the firsthost computer system 14 proceeds at248 to update the account represented at220 with a vault that includes the first email address, the additional email addresses and the phone number associated therewith. - If one or more of the additional email addresses are not associated with any accounts within the first
host computer system 14, then the firsthost computer system 14, at250, transmits an email to the additional email address that is not associated with an account to create an account. A user receiving the email transmitted at250 can proceed at252 to create an account with the second email address associated with the account. Only after all the additional email addresses are associated with accounts does the firsthost computer system 14, at248, proceed to register a vault. - The first
host computer system 14 then at254 provides a summary through the interface of the website. The summary shows that in order to transfer bitcoin, emails will be sent to and confirmations will be required from the first email address and the minimum of the additional email addresses. The summary also includes the phone number associated with the vault and states the waiting period before the bitcoin is transferred. The website also includes a “Finish” button which, when selected by the user at238, lands the browser used by the user in the vault. FIG. 57 illustrates how bitcoin is transferred into and out of the vault. At260, the user first transfers bitcoin into the vault. The user may transfer the bitcoin from one of their wallets associated with their account into the vault or may transfer the bitcoin into the vault from an external source. The bitcoin is then stored within the vault.- At262, the user requests a transfer out of the vault using the website. The user includes the amount of bitcoin to be transferred, the reason for the transfer and selects a wallet to which the bitcoin is to be transferred. The user also includes a two-factor code which the user may obtain through a mobile application or via SMS communication with the first
host computer system 14. - At264, the first
host computer system 14 determines whether the two-factor code is correct. If the two-factor code is incorrect, then the firsthost computer system 14, at266, makes no change to the website interface. - If the determination is made at264 that the two-factor code is correct, then the first
host computer system 14 proceeds at268 to transmit all emails. In the case of an individual vault, emails are sent to the first and second email addresses represented in the account at234 inFIG. 56 . In the case of a group vault, then emails are transmitted to the first email address and the additional email addresses represented in the account at248 inFIG. 56 . At270, the firsthost computer system 14 updates the transaction list within the website to represent that approval is being awaited. - Each one of the emails has a respective link that can be selected by a recipient. At272, a user receiving one of the emails reacts to the email by clicking on the link. Selection of the link causes an authorization instruction to be transmitted from a device of the respective user to the first
host computer system 14. At274, the firsthost computer system 14 detects the authorization instruction received in response to one of the emails that have been transmitted. Selection of the link on the email opens a browser on the recipient's device and displays a message that the authorization has been successfully approved. - At276, the recipient of a second one of the emails reacts to the email by clicking the link on the second email to send an authorization instruction. At278, the first
host computer system 14 detects the authorization instruction transmitted at276 and displays a web page indicating that the authorization has been successfully approved. - When all the predetermined approvals have been received, the first
host computer system 14 proceeds, at280, to update the transaction list to indicate that clearance is being awaited. At282, only if the minimum number of approvals are detected, the firsthost computer system 14 starts a countdown timer and sends an email to the user of the account informing the user that the bitcoin will be transferred after 48 hours.Block 284 represents the transmission of three email reminders to the user during the 48 hour waiting period. Each email includes the time remaining before the 48 hours will have elapsed and the amount of bitcoin that will be transferred out of the vault. Each email also includes a “Cancel” link. The user can select the “Cancel” link, which caused the transmission of a cancel instruction to the firsthost computer system 14. The cancel instruction will cancel the transfer of the bitcoin and therefore the request that was transmitted at262. - At286, the first
host computer system 14 detects an end of the time period. The firsthost computer system 14 then transfers the amount of bitcoin out of the vault and in to the destination selected at262. The firsthost computer system 14 also updates the transaction list on the website to indicate that the transaction has been cleared. FIG. 58 illustrates components of the firsthost computer system 14 that are used for carrying out the method shown inFIGS. 56 and 57 , including anaccount 290 of a user, awebsite 292, avault establishment wizard 294, avault management module 296 and thetransaction processor 154 hereinbefore described. Thevault establishment wizard 294 is programmed to execute the establishment of the vault as described with reference toFIG. 56 . Thevault management module 296 is programmed to manage the vault as described with reference toFIG. 57 . A user accesses thewebsite 292 and downloads an interface so as to interact via thewebsite 292 with thevault establishment wizard 294 and thevault management module 296. Thevault management module 296 provides instructions to thetransaction processor 154 to transfer the bitcoin out of the vault.FIG. 59 shows the email that is transmitted at228 inFIG. 56 .FIG. 60 shows an interface of thewebsite 292 inFIG. 58 when the user requests a transfer out of a vault at262 inFIG. 57 .FIGS. 61 and 62 show the emails that are transmitted at268 inFIG. 57 .FIG. 63 shows the interface of the website after the minimum number of approvals are received and the countdown clock has been started at282 inFIG. 57 .- Email addresses are used in the exemplary embodiment for electronic communication via email. Another embodiment may make use of other electronic communication addresses such as text messages to phone numbers or messages through social networks. Such messages may include authorization links as described or authorization may be obtained otherwise such as sending a reply message and including “Y” or “Yes” in the reply message. A secondary electronic communication address may be an individual address or a group address.
FIG. 64 illustrates the establishment of a user-controlled vault. At302, a user at thefirst user device 18 transmits a request for a user-controlled vault to the firsthost computer system 14. At304, the firsthost computer system 14 responds to the request to initiate key generation.- At306, the first
host computer system 14 generates a seed for a master key. At308, the firsthost computer system 14 uses the seed generated at306 to generate a master key. The master key includes a public key for the master key and a private key for the master key. At310, the firsthost computer system 14 stores the public key for the master key and, at312, stores the private key for the master key. The combination of the keys stored at310 and312 form a master key set314. - A
generation script 316 initially resides on the firsthost computer system 14. At318, the firsthost computer system 14 transmits thegeneration script 316 to thefirst user device 18. Thefirst user device 18 receives thegeneration script 316, which is executable on thefirst user device 18. - At320, the
generation script 316 generates a seed for a shared key. Thegeneration script 316 includes a key generation algorithm. At321, the key generation algorithm uses the seed generated at320 to generate a shared key. The shared key includes a public key and a private key. - The private key for the shared key is shown at322. The
generation script 316 also includes an interface with a field for a user to enter a password via a keyboard. At324, the user enters the password into the interface. Thegeneration script 316 also includes an encryption algorithm. At326, the encryption algorithm generates an encrypted seed from the private key shown at322 and the password entered at324. - At328 and330, the key generation algorithm and encryption algorithm respectively send the public key of the shared key and the encrypted seed to the first
host computer system 14. At332, the firsthost computer system 14 stores the public key for the shared key and, at334, stores the encrypted seed for the shared key. The public key stored at332 and theencrypted seed 334 can be viewed as a sharedkey set 336. Additionally, the private key shown at322 forms part of the sharedkey set 336. The private key shown at322 is however never transmitted from thefirst user device 18 to the firsthost computer system 14. - At338, the
generation script 316 further generates a seed for a user key. At340, the key generation algorithm uses the seed generated at338 to generate a user key. The user key includes a public key for the user key and a private key for the user key. At342, the key generation algorithm transmits only the public key for the user key to the firsthost computer system 14. At344, the firsthost computer system 14 stores the public key for the user key. - At346, the
generation script 316 displays the private key for the user key to the user. The user can then store the private key manually on thefirst user device 18 or write it down for later use. Thefirst user device 18 never transmits the private key displayed at346 to the firsthost computer system 14. The combination of the public key for the user key stored at344 and the private key for the user key displayed at346 form a user key set348. FIG. 65 illustrates how the user-controlled vault is used by the user. At360, the user of thefirst user device 18 creates and transmits a request to transact using bitcoin of the user-controlled vault. At362, the request reaches thetransaction processor 154 hereinbefore described. At364, the firsthost computer system 14 creates an authorization for the transaction.- The master key set312, shared
key set 336 and user key set334 are replicated fromFIG. 64 and the same reference numerals apply. It should however be understood that these keys are stored or displayed inFIG. 64 and that the stored and displayed keys are not stored but only retrieved and used inFIG. 65 . - At366, the first
host computer system 14 signs theauthorization 364 with the private key for the master key. Such signature then allows for an authorization to transact at368. As shown in370, two out of three authorizations are required in order to transact and the authorization provided at368 may form one of the two authorizations. - A verification script372 initially resides on the first
host computer system 14. At373, the firsthost computer system 14 initiates key collection by transmitting the verification script372 to thefirst user device 18. The verification script372 is executable on thefirst user device 18. Both thegeneration script 316 inFIG. 64 and the verification script372 inFIG. 65 may be in the form of JavaScript™ that is executable by a browser on thefirst user device 18. - The encrypted seed stored at334 on the first
host computer system 14 is transmitted together with the verification script372 and is received at374 by thefirst user device 18. The verification script372 further includes an interface with a field for entering a password. At376, the user enters the same password that the user entered at324 inFIG. 64 into the field provided in the interface using a keyboard. The verification script372 further includes a decryption algorithm. At378, the decryption algorithm uses the encrypted seed and the password to decrypt the encrypted seed and obtain the private key. The encryption at326 inFIG. 64 and decryption at378 inFIG. 65 may follow the BIP38 protocol which is commonly understood by those skilled in the art of bitcoin encryption. - The
authorization 364 is transmitted together with the verification script372 to thefirst user device 18. The verification script372 further has a signature algorithm. At380, the signature algorithm signs the authorization with the private key. The signature algorithm then transmits the signed authorization (together with the signature) to the firsthost computer system 14. - The first
host computer system 14 has a verification module. As will be commonly understood as those skilled in the art, a verification module is an algorithm that verifies a signature that was created with a private key using a public key. At382, the verification module verifies the signature using the same public key stored at332 for the shared key in the sharedkey set 336 that also includes the encrypted seed stored at334. At384, the verification module determines whether the signature is correct. If the signature is not correct, then thefirst computer system 14 returns to374 where the encrypted key is received and the user enters a password. If, at384, a determination is made that the signature is correct, then the firsthost computer system 14 proceeds to386 to provide an authorization due to the signature being correct. The authorization at386 may be one of the authorizations required at370 in order to authorize the transaction. - The verification script372 further includes an interface for entering the private key of the user key that was previously displayed at346 to the user. At390, the user enters the private key into the field provided therefor. At392, a signature algorithm forming part of the verification script372 signs the authorization with the private key that has been entered by the user. The signature algorithm then transmits the signed authorization (together with the signature) to the first
host computer system 14. At394, a verification module verifies the signature using the public key that was stored at344. At396, the verification module determines whether the signature is correct. If the signature is incorrect, then the firsthost computer system 14 instructs the verification script372 to return to390 where the user is again asked for the private key for the user key. If the signature is correct, then the firsthost computer system 14 proceeds to398 to provide an authorization for the transaction due to the signature being correct. The authorization provided at398 may be one of the authorizations required at370. - What should be noted this time is that the password entered at376 is never transmitted to the first
host computer system 14. Similarly, the private key entered at390 is never transmitted to the firsthost computer system 14. The user's control over the password and private key effectively disallows the transaction from being processed outside of the user's control. - After two out of the three authorizations have been received at370, the first
host computer system 14 proceeds at400 to authorize the transaction with thetransaction processor 154. FIG. 66 illustrates anaddress generator 402 that is used to generate addresses such as the bitcoin address that are used for the transaction requested at360 inFIG. 65 . Amaster key seed 404, sharedkey seed 406 and user key seed408 are generated. Themaster key seed 404 is used to generate a masterpublic key 410 and a masterprivate key 412. The sharedkey seed 406 is used to generate a sharedpublic key 414 and a sharedprivate key 416. The user key seed408 is used to generate a user public key418 and user private key420.- Each one of the
keys 410 to420 may be used to generate child keys M/0, M/1 . . . . The shared keys at each level may then be combined to generate an address. For example, the M/0 keys of the masterpublic key 410, sharedpublic key 414 and user public key418 may be used to generate an address (Address 0). The M/0 level may for example be the public keys stored at310,332 and334 inFIG. 64 . The address (Address 0) may for example be the bitcoin address for the transaction. Similarly, the M/1 level keys of the masterpublic key 410, sharedpublic key 414 and user public key418 may be used to generate another address (Address 1). The further addresses may be generated to create further bitcoin addresses of for other purposes. FIG. 67 of the accompanying drawings illustrates the firsthost computer system 14, apartner computer system 422 and areceiver computer system 424. Thereceiver computer system 424 includes areceiver browser 426. Thepartner computer system 422 has a website, in the present example a blog with ablog post 428 that has ablog post URL 430. At432, a user of thereceiver computer system 424 uses thereceiver browser 426 to create theblog post 428.- The first
host computer system 14 has a wallet in the form ofreceiver account 434, an embedded code generator and abutton ID generator 438. At440, the user of thereceiver computer system 424 creates thereceiver account 434. Thereceiver account 434 haslogin details 442 and a receiver account identifier (ID)444. At446, the user of thereceiver computer system 424 logs into thereceiver account 434 and enters theblog post URL 430 through the user interface36 (FIG. 1B ). Theblog post URL 430 is then stored in association with theparticular receiver account 434 with the wallet management module44 (FIG. 1B ). At448, the firsthost computer system 14 provides theblog post URL 430 to the embedded code generator andbutton ID generator 438. The embeddedcode generator 438 then generates an embeddedcode 450 and, at452, transmits the embeddedcode 450 to thereceiver browser 426. The embeddedcode 450 includes theblog post URL 430,receiver account ID 444 and astartup caller 454. - The
blog post 428 on thepartner computer system 422 has a frame for pasting the embeddedcode 450 due to prior agreement between operators of the firsthost computer system 14 and thepartner computer system 422. At456, the user of thereceiver computer system 424 copies the embeddedcode 450 received at452 and pastes the embeddedcode 450 into the frame of theblog post 428. The embeddedcode 450 is then embedded and forms part of the HyperText Markup Language (HTML) of theblog post 428. - A
blog post 428 is used herein to describe the invention by way of example. It should however be understood that the invention may have broader application. A URL of a page may for example have a video, song or news article. Such a page will typically have a frame for pasting the embeddedcode 450. Alternatively, media content such as a video may not have a separate frame for pasting the embedded code. Instead, another manner of activating payment features of the invention may be provided, such as a separate URL link, voice activation, detection of human gestures of a user, etc. - The button ID generator (see438) generates a unique button ID. At458, the button ID generator stores the button ID as
button ID 460 within a data store of the firsthost computer system 14. At462, thebutton ID generator 438 stores thebutton ID 460 in association with the particularreceiver account ID 444 and particularblog post URL 430. Multiple receiver accounts may exist within the firsthost computer system 14. In addition, a receiver account may have multiple blog post URL's associated therewith. Each pair of a respective receiver account ID and respective blog post URL have a unique button ID. FIG. 68 shows the firsthost computer system 14, thepartner computer system 422 and asender computer system 464. Thesender computer system 464 has a sender browser (not shown). At466, the sender browser downloads theblog post 428 from thepartner computer system 422. Thestartup caller 454 is a script, e.g. JavaScript®, that automatically executes on thesender computer system 464. At470, thestartup caller 454 retrieves allsender cookies 472 on thesender computer system 464. Thestartup caller 454, at474, transmits a startup call to the firsthost computer system 14. The startup call includes thecookies 472, theblog post URL 430 and thereceiver account ID 444.- The first
host computer system 14 includes astartup call responder 476 that receives thestartup call 474. Thestartup call responder 476, at478, uses theblog post URL 430 andreceiver account ID 444 received in thestartup call 474 to identify theparticular button ID 460. - The
button ID 460 in storage may havebits 480 representing all payments made in association with thebutton ID 460. At482, thestartup call responder 476 retrieves thebits 480 associated with thebutton ID 460 from the data store. - At483, the
startup call responder 476 transmits a startup call response to thesender computer system 464. The startup call response transmitted at483 is in response to the startup call received at474. The startup call response includes abutton 484, thebits 480, asession script 486 and thebutton ID 460. Adisplay 490 of thesender computer system 464 displays theblog post 428. The embeddedcode 450 has added thebutton 484 and thebits 480 to theblog post 428. Thebutton 484 is a two-dimensional button that is selectable by a user of thesender computer system 464. Thesession script 486 is associated with thebutton 484 so as to be executable when the user selects thebutton 484. - The embedded
code 450, at491, stores thebutton ID 460 within thesender cookies 472. Thebutton ID 460 stored within thesender cookies 472 can now be used to identify thebutton ID 460 within the firsthost computer system 14. - In
FIG. 69 , the user has selected thebutton 484 which, at492, initiates thesession script 486. Thesession script 486, at494, retrieves thesender cookies 472 and, at496, makes a session call to the firsthost computer system 14. The session call496 includes thecookies 472. - The first
host computer system 14 includes asession responder 498 that receives thesession call 496. At500, thesession responder 498 checks all data for thebutton ID 460 that has been received in thesession call 496. The data associated with thebutton ID 460 may include abitcoin address 502, although no bitcoin address may be included within thecookies 472 of thesession call 496. At504, thesession responder 498 determines whether a bitcoin address was received in thecookies 472 of thesession call 496. If no bitcoin address was received, the firsthost computer system 14 executes abitcoin address generator 506. Thebitcoin address generator 506 then generates a bitcoin address and, at508, stores the bitcoin address in association with thebutton ID 460. The newly saved bitcoin address is represented asbitcoin address 510. At512, thesession responder 498 transmits thebitcoin address 510 that has been generated by thebitcoin address generator 506 to thesender computer system 464. At514, thesession script 486 stores thebitcoin address 510 in association with thebutton ID 460 within thesender cookies 472. Upon a browser refresh, the process started at466 inFIG. 68 is restarted and all cookies are stored from earlier browser sessions are collected and transmitted by thestartup caller 454. - At516, the
session responder 498 determines whether thesender computer system 464 is signed into a sender account. The determination is made based on whether a signed-in cookie is found among the cookies transmitted in thesession call 496. If no signed-in cookie is found, then thesession responder 498 proceeds to518. At518, thesession responder 498 sends a sign-inpanel 520, a sign-inscript 522, alisten code 524, a thirdparty payment script 526, and apull code 528 to thesender computer system 464. Thesession script 486 creates an overlay window that includes the sign-inpanel 520 with a sign-inbutton 530 having the sign-inscript 522 associated therewith. The user can select the sign-inbutton 530 which, at532, initiates the sign-inscript 522. The sign-inscript 522 creates and opens a further window (not shown) that allows the sender of thesender computer system 464 to enterlogin details 534 of asender account 536. At540, the sign-inscript 522 signs thesender computer system 464 into thesender account 536 using the login details534. The sign-inscript 522, at548, stores a signed-incookie 549 within thesender cookies 472. The sign-inpanel 520 further includes two payment selections, including a thirdparty wallet button 544, and a Quick Response (QR)code 546. The thirdparty payment script 526 is stored in association with the thirdparty wallet button 544. Thelisten code 524 and pullcode 528 are stored in an executable manner within thesender computer system 464. Thesession script 486 retrieves thebitcoin address 510 from thesender cookies 472 and displays thebitcoin address 510 within the sign-inpanel 520. - As shown in
FIG. 70 , if the determination at516 is made that thesender computer system 464 is signed-in to thesender account 436, or after thesender computer system 464 signs-in at540 inFIG. 69 , thesession responder 498 proceeds to550. At550, thesession responder 498 transmits a signed-inpanel 552, thelisten code 524, the thirdparty payment script 526, thepull code 528 and a hostaccount payment script 554 to thesender computer system 464. The signed-inpanel 552 is the same as the sign-inpanel 520 with the exception that it includes ahost account button 556 instead of the sign-inbutton 530. The thirdparty payment script 526 is stored in association with the thirdparty wallet button 544. The hostaccount payment script 554 is stored in association withhost account button 556. - Selection by the user of the
host account button 556 initiates at560 the hostaccount payment script 554. The hostaccount payment script 554 transmits an instruction to thetransaction processor 154 of the selection. At561, thetransaction processor 154 makes a payment out of thesender account 536 to thereceiver account 434 as hereinbefore described without going through the bitcoin network or the block chain. - At564, the
transaction processor 154 updates thebits 480 by adding the bits of the present transaction to thebits 480 already stored within the data store. Thebits 480 within the data store thus represent an ongoing tally of all payments made in association with thebutton ID 460. The bitcoin addresses502 and510 represent bitcoin addresses that are generated for differentsender computer systems 464 using thesame button ID 460. - After the host
account payment script 554 transmits the instruction to thetransaction processor 15, the hostaccount payment script 554 initiates thepull code 528. Thepull code 528, at574, pulls the new bit count from thebits 480 in the storage of the firsthost computer system 14. At566, thepull code 528 updates thebits 480 in theblog post 428 based on the bits that have been pulled by thepull code 528 inFIG. 70 . - As shown in
FIG. 71 , the user selects the thirdparty wallet button 544 which, at560, causes execution of the thirdparty payment script 526. The thirdparty payment script 526 then transmits a transaction (of bitcoin to the bitcoin address510) to a thirdparty transaction processor 562. The thirdparty transaction processor 562 is hosted by a host computer system other than the firsthost computer system 14. At564, the thirdparty transaction processor 562 broadcasts the transaction to thebitcoin network 12 and it is picked up by the blockchain. - The first
host computer system 14 further includes ablock chain checker 567 and abit updater 568. Theblock chain checker 567, at570, periodically checks the block chain. For purposes of this discussion, theblock chain checker 567 checks the block chain to determine whether there are any new transactions for the bitcoin addresses502 and510 stored in association with thebutton ID 460. If theblock chain checker 567 finds any further transactions, theblock chain checker 567 notifies thebit updater 568. At572, thebit updater 568 updates thebits 480 that are associated with therespective bitcoin address bits 480 are updated by adding bits for any new transactions that have been picked up by theblock chain checker 567. - At574, the
bit updater 568 transmits a push update notification to thesender computer system 464. Thelisten code 524 receives the push update notification. Websocket technology may for example be used for the push update notification in order to open an interactive communication link. Thelisten code 524 is continuously active and therefore continuously listens for push update notifications. When thelisten code 524 receives the push update notification, thelisten code 524 initiates thepull code 528. Thepull code 528, at574, pulls the new bit count from thebits 480 in storage. At566, thepull code 528 updates thebits 480 in theblog post 428 based on the bits that have been pulled by thepull code 528 inFIG. 70 . - The
QR code 546 may be scanned by an app on a mobile phone. Thebitcoin address 510 is encoded in theQR code 546. The app can decode theQR code 546 to extract thebitcoin address 510 and transmit a transaction (of bitcoin to the bitcoin address510) to a third party transaction processor such as the thirdparty transaction processor 562. - The
button 484 shown inFIG. 69 can be used as a Tip button. A user of thesender computer system 464 can use thebutton 484 to make a small discrete payment to the user of thereceiver computer system 424. Such a payment may, for example, be as a reward for the content of theblog post 428. FIG. 72 shows asystem 600 for transacting bitcoin. AnInternet interface 602 allows for user computers (user computers A to C) to connect to thesystem 600 over the Internet.Order gateways 604 are connected to theInternet interface 602 to receive buy and sell offers via theInternet interface 602 from the user computers A to C. Amatching engine 606 is connected to theorder gateways 604. Thematching engine 606 can receive the buy and sell offers from theorder gateways 604.- A
feed generator 608 is connected to theInternet interface 602. Thematching engine 606 provides an output to amulticast pipeline 610. Thefeed generator 608 is connected to themulticast pipeline 610. Thefeed generator 608 receives the buy and sell offers from themulticast pipeline 610 and displays any buy and sell offers via theInternet interface 602 to the user computers A to C. Users can thus view any buy and sell offers already in the system before making their own buy and sell offers. - The
matching engine 606 can match buy and sell offers and broadcast the matches to themulticast pipeline 610. Thefeed generator 608 displays the matches via theInternet interface 602 to the user computers A to C. - An
exchange database 612 includes records of bitcoin and currency held by users A to C corresponding to the user computers A to C. Aclearing module 614 is connected to themulticast pipeline 610 and receives matches from themulticast pipeline 610. Anexchange 616 is connected to theclearing module 614. Theexchange 616 is also connected to theInternet interface 602. Users at the user computers A to C can provide instructions via theInternet interface 602 to theexchange 616 to transfer bitcoin or currency. Theexchange 616 has a number of functions, including calculating total amounts of bitcoin and currency as represented in theexchange database 612, cross checking bitcoin and currency totals between theexchange database 612 and an exchange user618, transferring bitcoin and currency between wallets A to C that correspond respectively to the users A to C in theexchange database 612, updating bitcoin and currency amounts of the users A to C in theexchange database 612, and may receive and execute instructions from theclearing module 614 to transfer bitcoin and currency between the users A to C in theexchange database 612. - The exchange is connected to a
ledger 620. Theledger 620 hold records of wallets A to C and further functions to cross-check balances between theexchange database 612 and exchange user618. FIG. 73 ashows the beginning of a transfer-in algorithm that is executed by thesystem 600. A user at user computer A has $10 of currency in theexchange database 612. For purposes of discussion, no other users have any bitcoin or currency. Theexchange 616 calculates the total amount of currency and bitcoin within theexchange database 612 and records the total amount as $10 and 0 bitcoin. The exchange user618 has $10, representing a previous transfer from wallet A to the exchange user618.- At1a, a user at user computer B requests a transfer via the
Internet interface 602. The transfer may for example be to transfer $20 from wallet B to the exchange user618. At1b, theInternet interface 602 provides the transfer request to theexchange 616. At2a, theexchange 616 sends a cross-check request to theledger 620 and at2btheledger 620 cross checks the totals in theexchange database 612 and the exchange user618 before proceeding with a transfer. In the present example, theexchange database 612 has $10 and 0 bitcoin and the exchange user618 has $10 and 0 bitcoin. The totals therefore match. If either the currency or bitcoin totals do not match, theexchange 616 does not make any further transfers and provides an alert to an operator. The operator will then remedy any mismatches and then reactivate theexchange 616. Because the totals match, theexchange 616 proceeds with the transfer. - As shown in
FIG. 73 b, theexchange 616, at3, transfers $20 from wallet B to the exchange user618. The exchange user618 calculates the total amount held by the exchange user618 as $30, representing the $10 that was there before the transfer plus another $20 because of the transfer. - At4a, the
exchange 616 records $20 for user B in theexchange database 612. At4b, theexchange 616 updates the totals and records a total amount of $30, representing the $10 held by user A and the $20 that has been added for user B. FIG. 73 cillustrates the totals in theexchange database 612 and the exchange user618 after a further transfer wherein a user at the user computer C has requested a transfer of 5 bitcoin from wallet C to the exchange user618. The exchange user618 now holds 5 bitcoin and $30. User C, within theexchange database 612, now holds 5 bitcoin. The totals held with theexchange database 612 are $30 and 5 bitcoin. For purposes of discussion, this ends the transfer-in algorithm that was started inFIG. 73 a.FIG. 73 dshows a trading algorithm that is carried out after the transfer-in algorithm ifFIGS. 73 ato73c. At5a, a user (buyer) at user computer A submits a buy offer of 2 bitcoin at $5 each ($10 total). As noted previously, all offers are transmitted via theInternet interface 602, one of theorder gateways 604, thematching engine 606 and themulticast pipeline 610 to thefeed generator 608 which displays the offers on theInternet interface 602. A user at user computer C can thus see the buy offer submitted by the user at user computer A. At5b, the user (seller) at user computer C submits a sell offer for 2 bitcoin at $5 each to theInternet interface 602. At5c, the buy and sell offers are submitted by theInternet interface 602 to one of theorder gateways 604. At5d, theorder gateway 604 provides the buy and sell offers sequentially to thematching engine 606.- As mentioned, the user at user computer C can see the buy offer of the user at user computer A before submitting the sell offer. In another example, the user at user computer C can first submit the sell offer and the sell offer can be seen by the user at user computer A. The buy and sell offers will typically be received by the
matching engine 606 at different times. - Multiple users may submit one or more buy and sell offers. The
matching engine 606 attempts to match the buy and sell offers to one another. At6, thematching engine 606 has matched the buy and sell offers received from users at the user computers A and C. - The
matching engine 606 then provides a broadcast of the match over themulticast pipeline 610 discussed with reference toFIG. 72 . At7a, thefeed generator 608 receives a multicast that includes the match. At7b, theclearing module 614 receives the same multicast that includes the match. At8, thefeed generator 608 provides a feed to theInternet interface 602 that includes the match. As previously mentioned, thefeed generator 608 also provides a feed of buy and sell offers to theInternet interface 602. - At9a, the
clearing module 614 updates user A within theexchange database 612 by adding 2 bitcoin and subtracting $10 from user A. At9b, theclearing module 614 updates user C by subtracting 2 bitcoin from and adding $10 to user C. Theclearing module 614 makes the updates directly to theexchange database 612. - There is no need for recalculating the totals within the
exchange database 612 at this stage. The same amount of currency or bitcoin that has been subtracted from one user has been added to another user. Theexchange database 612 thus still indicates totals of $30 and 5 bitcoin. FIG. 73 eshows a withdrawal algorithm that can be carried out after the trading algorithm inFIG. 73 d. At10a, a user at user computer C requests a withdrawal of, for example, $10. The request is received via theInternet interface 602 and is passed on to theexchange 616 at10b.- At11a, the
exchange 616 sends a cross-check request to theledger 620 and at11btheledger 620 cross checks the totals before proceeding. In the present example, the amount of bitcoin in the exchange user618 and the total amount of bitcoin represented in theexchange database 612 are the same and the total currency amount in the exchange user618 and in theexchange database 612 are the same. Should either of these two comparisons result in a mismatch, theexchange 616 will not make any withdrawal and create an alarm for an operator. - As shown in
FIG. 73 f, at12, theexchange 616 transfers $10 from the exchange user618 to the wallet C. The exchange user618 now has $20, representing the $30 inFIG. 73 eminus the $10 that has been transferred out. At13a, theexchange 616 adds a representation for user C in theexchange database 612 showing a withdrawal of $10. At13b, theexchange 616 updates the totals. Because user C has made a withdrawal of $10, the total currency amount within theexchange database 612 amounts to $20. The amount of bitcoin is still the same. The total amounts in the exchange user618 and in theexchange database 612 are thus the same. - Other users may submit similar withdrawal requests. For example, a user at user computer A may request a withdrawal of 1 bitcoin. The
exchange 616 then cross checks the total amounts, makes a transfer of 1 bitcoin from the exchange user618 to wallet A and updates theexchange database 612 by deducting 1 bitcoin from user A and updates the total amount of bitcoin to 4 bitcoin. FIG. 74 shows a diagrammatic representation of a machine in the exemplary form of acomputer system 900 within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a network deployment, the machine may operate in the capacity of a server or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.- The
exemplary computer system 900 includes a processor930 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), a main memory932 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), and a static memory934 (e.g., flash memory, static random access memory (SRAM, etc.), which communicate with each other via abus 936. - The
computer system 900 may further include a video display938 (e.g., a liquid crystal displays (LCD) or a cathode ray tube (CRT)). Thecomputer system 900 also includes an alpha-numeric input device940 (e.g., a keyboard), a cursor control device942 (e.g., a mouse), adisk drive unit 944, a signal generation device946 (e.g., a speaker), and anetwork interface device 948. - The
disk drive unit 944 includes a machine-readable medium 950 on which is stored one or more sets of instructions952 (e.g., software) embodying any one or more of the methodologies or functions described herein. The software may also reside, completely or at least partially, within themain memory 932 and/or within theprocessor 930 during execution thereof by thecomputer system 900, thememory 932 and theprocessor 930 also constituting machine readable media. The software may further be transmitted or received over anetwork 954 via thenetwork interface device 948. - While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative and not restrictive of the current invention, and that this invention is not restricted to the specific constructions and arrangements shown and described since modifications may occur to those ordinarily skilled in the art.
Claims (17)
1-36. (canceled)
37. A host computer system for transacting bitcoin comprising:
a processor;
a computer readable medium connected to the processor;
a local storage on the computer readable medium; and
a set of instruction on the computer readable medium that are executable by the processor, including:
a register;
a Bitcoin address and an associated private key and value stored in the register;
a local controller transferring a private key for a Bitcoin address of a vault, to a local storage connected to a processor and transferring the value of the Bitcoin address in the register to the vault;
a splitter that splits the private key of the Bitcoin address of the vault into a plurality of codes;
an offline distribution module distributing the codes to remote distributed storage locations, removing the private key of the Bitcoin address of the vault from the local storage, and removing the private key for the Bitcoin address of the register from the Bitcoin address of the register;
at least one restoration interface receiving at least some of the codes into which the private key for Bitcoin address of the vault has been split; and
an assembler that assembles the codes that have been received into the private key of the Bitcoin address of the vault, the local controller restoring the private key of the Bitcoin address of the vault from the local storage, and restoring the value for the Bitcoin address in the register from the vault.
38. The host computer system37, wherein the value is transferred from the register to the vault after the codes have been distributed.
39. The host computer system37, further comprising:
a wallet establishment module establishing a plurality of wallets in the local storage, the local controller storing at least one Bitcoin address for a value in association with each wallet, the local controller selecting at least a subset of the Bitcoin addresses in all the wallets, and storing the values of the subset of Bitcoin addresses to the vault.
40. The host computer system37, further comprising:
an encryption algorithm encrypting each code before being distributed; and
a decryption algorithm decrypting the code after receiving the code.
41. The host computer system37, wherein the number of codes that are distributed is more than the number of codes that are received before assembling the private key of the Bitcoin address.
42. The host computer system41, wherein a minimum number of codes is required before the private key of the Bitcoin address can be assembled.
43. The host computer system37, wherein the Bitcoin address for the register is a first Bitcoin address for the register, the codes are first codes, and the vault is a first vault, wherein the local controller transfers a private key for a second Bitcoin address of a second vault to the local storage connected to the processor, transfers the value of the second Bitcoin address in the register to the second vault, splits the private key for the Bitcoin address of the second vault into a plurality of second codes, the offline distribution module distributing the second codes to remote distributed storage locations, and the local controller removing the private key of the Bitcoin address of the second vault from the local storage, removing the private key for the second Bitcoin address of the register from the Bitcoin address of the register, the restoration interface receives at least some of the second codes into which the private key for Bitcoin address of the second vault has been split, the assembler assembles the second codes that have been received into the private key of the Bitcoin address of the second vault, and the local controller restores the private key of the second vault from the local storage, and restores the value for the second Bitcoin address in the register from the second vault.
44. A method of transacting bitcoin comprising:
transferring, by the processor, a private key of the Bitcoin address of a vault to a local storage connected to the processor;
splitting, by the processor, the private key of the Bitcoin address of the vault into a plurality of codes;
distributing the codes to remote distributed storage locations;
transferring, by the processor, a value of a Bitcoin address in a register to the vault;
receiving, by the processor, at least some of the codes into which the private key of the Bitcoin address of the vault has been split;
assembling, by the processor, the codes that have been received into the private key of the Bitcoin address of the vault;
restoring, by the processor, the private key of the Bitcoin address of the vault to the vault; and
restoring, by the processor, the value of the Bitcoin address in the register from the vault.
45. The method ofclaim 44 , wherein the value is transferred from the register to the vault after the codes have been distributed.
46. The method ofclaim 44 , further comprising:
establishing, by the processor, a plurality of wallets in the local register;
storing, by the processor, at least one Bitcoin address for a value in association with each wallet;
selecting, by the processor, at least a subset of the Bitcoin addresses in all the wallets; and
storing, by the processor, the values of the subset of Bitcoin addresses in the vault.
47. The method ofclaim 44 , further comprising:
encrypting, by the processor, each code before being distributed; and
decrypting, by the processor, the code after receiving the code.
48. The method ofclaim 44 , wherein the number of codes that are distributed is more than the number of codes that are received before assembling the private key.
49. The method ofclaim 48 , wherein a minimum number of codes is required before the private key of the Bitcoin address can be assembled.
50. The method ofclaim 44 , wherein the Bitcoin address for the register is a first Bitcoin address for the register, the codes are first codes, and the vault is a first vault, further comprising:
transferring, by the processor, a private key of the Bitcoin address of a second vault to a local storage connected to the processor;
splitting, by the processor, the private key of the Bitcoin address of the second vault into a plurality of second codes;
distributing the second codes to remote distributed storage locations;
transferring, by the processor, a value of a second Bitcoin address in the register to the vault;
receiving, by the processor, at least some of the second codes into which the private key for Bitcoin address of the second vault has been split;
assembling, by the processor, the second codes that have been received into the private key for Bitcoin address of the second vault;
restoring, by the processor, the private key of the second vault to the vault; and
restoring, by the processor, the value of the second Bitcoin address in the register from the second vault.
51. A non-transitory computer-readable medium having stored thereon a set of instructions that are executable by a processor to carry out a method of transacting bitcoin comprising:
transferring, by the processor, a private key of a Bitcoin address of a vault to a local storage connected to the processor;
splitting, by the processor, the private key of the Bitcoin address of the vault into a plurality of codes;
distributing the codes to remote distributed storage locations;
transferring, by the processor, a value of a Bitcoin address in a register to the vault;
receiving, by the processor, at least some of the codes into which the private key of the Bitcoin address of the vault has been split;
assembling, by the processor, the codes that have been received into the private key of the Bitcoin address of the vault;
restoring, by the processor, the private key of the Bitcoin address of the vault to the vault; and
restoring, by the processor, the value of the Bitcoin address in the register from the vault.
52-141. (canceled)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US14/660,331US20150262171A1 (en) | 2014-03-17 | 2015-03-17 | Bitcoin private key splitting for cold storage |
Applications Claiming Priority (7)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US201461954434P | 2014-03-17 | 2014-03-17 | |
| US201461990017P | 2014-05-07 | 2014-05-07 | |
| US201462042676P | 2014-08-27 | 2014-08-27 | |
| US201462056100P | 2014-09-26 | 2014-09-26 | |
| US201462086669P | 2014-12-02 | 2014-12-02 | |
| US201562099992P | 2015-01-05 | 2015-01-05 | |
| US14/660,331US20150262171A1 (en) | 2014-03-17 | 2015-03-17 | Bitcoin private key splitting for cold storage |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| US20150262171A1true US20150262171A1 (en) | 2015-09-17 |
Family
ID=54069270
Family Applications (12)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US14/660,331AbandonedUS20150262171A1 (en) | 2014-03-17 | 2015-03-17 | Bitcoin private key splitting for cold storage |
| US14/660,427Active2036-12-18US10891600B2 (en) | 2014-03-17 | 2015-03-17 | User private key control |
| US14/660,307AbandonedUS20150262137A1 (en) | 2014-03-17 | 2015-03-17 | Off-block chain transactions in combination with on-block chain transactions |
| US14/660,432ActiveUS9436935B2 (en) | 2014-03-17 | 2015-03-17 | Computer system for making a payment using a tip button |
| US14/660,422AbandonedUS20150262141A1 (en) | 2014-03-17 | 2015-03-17 | Personal vault |
| US14/660,296Active2036-07-15US10510053B2 (en) | 2014-03-17 | 2015-03-17 | Send cryptographic currency to email address |
| US14/660,440Active2037-01-19US10229396B2 (en) | 2014-03-17 | 2015-03-17 | Bitcoin exchange |
| US14/660,014Active2035-08-23US10614430B2 (en) | 2014-03-17 | 2015-03-17 | Instant exchange |
| US14/660,418Active2037-01-23US10755241B2 (en) | 2014-03-17 | 2015-03-17 | Hot wallet for holding bitcoin |
| US16/243,688Active2035-08-09US10878389B2 (en) | 2014-03-17 | 2019-01-09 | Cryptographic currency exchange |
| US16/952,539ActiveUS11741438B2 (en) | 2014-03-17 | 2020-11-19 | Cryptographic currency exchange |
| US18/350,731PendingUS20230368158A1 (en) | 2014-03-17 | 2023-07-11 | Cryptographic currency exchange |
Family Applications After (11)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US14/660,427Active2036-12-18US10891600B2 (en) | 2014-03-17 | 2015-03-17 | User private key control |
| US14/660,307AbandonedUS20150262137A1 (en) | 2014-03-17 | 2015-03-17 | Off-block chain transactions in combination with on-block chain transactions |
| US14/660,432ActiveUS9436935B2 (en) | 2014-03-17 | 2015-03-17 | Computer system for making a payment using a tip button |
| US14/660,422AbandonedUS20150262141A1 (en) | 2014-03-17 | 2015-03-17 | Personal vault |
| US14/660,296Active2036-07-15US10510053B2 (en) | 2014-03-17 | 2015-03-17 | Send cryptographic currency to email address |
| US14/660,440Active2037-01-19US10229396B2 (en) | 2014-03-17 | 2015-03-17 | Bitcoin exchange |
| US14/660,014Active2035-08-23US10614430B2 (en) | 2014-03-17 | 2015-03-17 | Instant exchange |
| US14/660,418Active2037-01-23US10755241B2 (en) | 2014-03-17 | 2015-03-17 | Hot wallet for holding bitcoin |
| US16/243,688Active2035-08-09US10878389B2 (en) | 2014-03-17 | 2019-01-09 | Cryptographic currency exchange |
| US16/952,539ActiveUS11741438B2 (en) | 2014-03-17 | 2020-11-19 | Cryptographic currency exchange |
| US18/350,731PendingUS20230368158A1 (en) | 2014-03-17 | 2023-07-11 | Cryptographic currency exchange |
Country Status (2)
| Country | Link |
|---|---|
| US (12) | US20150262171A1 (en) |
| WO (1) | WO2015142765A1 (en) |
Cited By (74)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017044554A1 (en) | 2015-09-11 | 2017-03-16 | Aware, Inc. | Biometric verification of a blockchain database transaction contributor |
| US9672499B2 (en) | 2014-04-02 | 2017-06-06 | Modernity Financial Holdings, Ltd. | Data analytic and security mechanism for implementing a hot wallet service |
| US9892460B1 (en) | 2013-06-28 | 2018-02-13 | Winklevoss Ip, Llc | Systems, methods, and program products for operating exchange traded products holding digital math-based assets |
| CN108352009A (en)* | 2015-11-09 | 2018-07-31 | 日本电信电话株式会社 | Block chain generating means, block chain generation method, block chain verification device, block chain verification method and program |
| US10068228B1 (en) | 2013-06-28 | 2018-09-04 | Winklevoss Ip, Llc | Systems and methods for storing digital math-based assets using a secure portal |
| CN109155034A (en)* | 2016-04-29 | 2019-01-04 | 区块链控股有限公司 | Implementing logic gate functions using blockchains |
| US10269009B1 (en) | 2013-06-28 | 2019-04-23 | Winklevoss Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
| US10339523B2 (en) | 2015-07-14 | 2019-07-02 | Fmr Llc | Point-to-point transaction guidance apparatuses, methods and systems |
| US10354325B1 (en) | 2013-06-28 | 2019-07-16 | Winklevoss Ip, Llc | Computer-generated graphical user interface |
| WO2019143850A1 (en)* | 2018-01-17 | 2019-07-25 | Medici Ventures, Inc. | Multi-approval system using m of n keys to generate a transaction address |
| US10373158B1 (en) | 2018-02-12 | 2019-08-06 | Winklevoss Ip, Llc | System, method and program product for modifying a supply of stable value digital asset tokens |
| US10373129B1 (en) | 2018-03-05 | 2019-08-06 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
| US10402823B1 (en)* | 2018-12-30 | 2019-09-03 | Alexander Vladimirovich Vlasov | System for exchanging private keys for mutual settlements between users of a cryptocurrency outside blockchains |
| US10438290B1 (en) | 2018-03-05 | 2019-10-08 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
| WO2019204426A1 (en)* | 2018-04-17 | 2019-10-24 | Coinbase, Inc. | Offline storage system and method of use |
| US10484376B1 (en) | 2015-01-26 | 2019-11-19 | Winklevoss Ip, Llc | Authenticating a user device associated with a user to communicate via a wireless network in a secure web-based environment |
| WO2019221956A1 (en)* | 2018-05-17 | 2019-11-21 | Conio Inc. | Methods and systems for safe creation, custody, recovery, and management of a digital asset |
| US20190354971A1 (en)* | 2018-05-15 | 2019-11-21 | Mfe Capital, Llc | Systems and methods for cold payment solution |
| US20190356484A1 (en)* | 2018-05-15 | 2019-11-21 | Mfe Capital, Llc | Device for off-line storage and usage of digital assets |
| US10504179B1 (en) | 2015-12-08 | 2019-12-10 | Fmr Llc | Social aggregated fractional equity transaction partitioned acquisition apparatuses, methods and systems |
| US10510053B2 (en) | 2014-03-17 | 2019-12-17 | Coinbase, Inc. | Send cryptographic currency to email address |
| US10516527B1 (en)* | 2015-04-17 | 2019-12-24 | EMC IP Holding Company LLC | Split-key based cryptography system for data protection and synchronization across multiple computing devices |
| US10540654B1 (en) | 2018-02-12 | 2020-01-21 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
| US10547441B2 (en) | 2016-09-02 | 2020-01-28 | Conio Inc. | Method and apparatus for restoring access to digital assets |
| US20200127817A1 (en)* | 2017-08-28 | 2020-04-23 | Alibaba Group Holding Limited | Key data processing method and apparatus, and server |
| US10644885B2 (en) | 2015-07-14 | 2020-05-05 | Fmr Llc | Firmware extension for secure cryptocurrency key backup, restore, and transaction signing platform apparatuses, methods and systems |
| US10693632B1 (en) | 2015-03-16 | 2020-06-23 | Winklevoss Ip, Llc | Autonomous devices |
| US10698885B2 (en) | 2017-05-25 | 2020-06-30 | Alibaba Group Holding Limited | Method and device for writing service data in block chain system |
| US10762235B2 (en)* | 2018-06-12 | 2020-09-01 | Mcafee, Llc | Methods, systems, and media for storing and retrieving data from distributed vaults |
| US10778439B2 (en) | 2015-07-14 | 2020-09-15 | Fmr Llc | Seed splitting and firmware extension for secure cryptocurrency key backup, restore, and transaction signing platform apparatuses, methods and systems |
| US20200320458A1 (en)* | 2019-04-04 | 2020-10-08 | Sony Corporation | System, method, and computer-readable medium for tracking information exchange |
| US10903991B1 (en) | 2019-08-01 | 2021-01-26 | Coinbase, Inc. | Systems and methods for generating signatures |
| US10915891B1 (en) | 2015-03-16 | 2021-02-09 | Winklevoss Ip, Llc | Autonomous devices |
| US10929842B1 (en) | 2018-03-05 | 2021-02-23 | Winklevoss Ip, Llc | System, method and program product for depositing and withdrawing stable value digital assets in exchange for fiat |
| US20210119781A1 (en)* | 2019-10-16 | 2021-04-22 | Coinbase, Inc. | Systems and methods for re-using cold storage keys |
| US10992469B2 (en) | 2015-07-14 | 2021-04-27 | Fmr Llc | Seed splitting and firmware extension for secure cryptocurrency key backup, restore, and transaction signing platform apparatuses, methods and systems |
| US20210224797A1 (en)* | 2018-08-27 | 2021-07-22 | Fireblocks Ltd. | System and method for securing crypto-asset transactions |
| US11074663B2 (en) | 2015-12-31 | 2021-07-27 | Camelot Uk Bidco Limited | System and method of facilitating intellectual property transactions |
| US11139955B1 (en) | 2018-02-12 | 2021-10-05 | Winklevoss Ip, Llc | Systems, methods, and program products for loaning digital assets and for depositing, holding and/or distributing collateral as a token in the form of digital assets on an underlying blockchain |
| US11196566B2 (en)* | 2014-05-09 | 2021-12-07 | Reginald Middleton | Devices, systems, and methods for facilitating low trust and zero trust value transfers |
| US11200569B1 (en) | 2018-02-12 | 2021-12-14 | Winklevoss Ip, Llc | System, method and program product for making payments using fiat-backed digital assets |
| US11218295B2 (en) | 2015-05-19 | 2022-01-04 | Coinbase, Inc. | Private key decryption system and method of use |
| US11282139B1 (en) | 2013-06-28 | 2022-03-22 | Gemini Ip, Llc | Systems, methods, and program products for verifying digital assets held in a custodial digital asset wallet |
| US11308487B1 (en) | 2018-02-12 | 2022-04-19 | Gemini Ip, Llc | System, method and program product for obtaining digital assets |
| US11334883B1 (en) | 2018-03-05 | 2022-05-17 | Gemini Ip, Llc | Systems, methods, and program products for modifying the supply, depositing, holding and/or distributing collateral as a stable value token in the form of digital assets |
| US11394543B2 (en) | 2018-12-13 | 2022-07-19 | Coinbase, Inc. | System and method for secure sensitive data storage and recovery |
| US11436598B2 (en) | 2017-12-15 | 2022-09-06 | Fmr Llc | Social data tracking datastructures, apparatuses, methods and systems |
| US11444779B2 (en) | 2018-08-02 | 2022-09-13 | Paypal, Inc. | Techniques for securing application programming interface requests using multi-party digital signatures |
| US11475442B1 (en) | 2018-02-12 | 2022-10-18 | Gemini Ip, Llc | System, method and program product for modifying a supply of stable value digital asset tokens |
| US11488147B2 (en) | 2015-07-14 | 2022-11-01 | Fmr Llc | Computationally efficient transfer processing and auditing apparatuses, methods and systems |
| US11501370B1 (en) | 2019-06-17 | 2022-11-15 | Gemini Ip, Llc | Systems, methods, and program products for non-custodial trading of digital assets on a digital asset exchange |
| US11522700B1 (en) | 2018-02-12 | 2022-12-06 | Gemini Ip, Llc | Systems, methods, and program products for depositing, holding and/or distributing collateral as a token in the form of digital assets on an underlying blockchain |
| US11538063B2 (en) | 2018-09-12 | 2022-12-27 | Samsung Electronics Co., Ltd. | Online fraud prevention and detection based on distributed system |
| US11587072B2 (en) | 2021-05-20 | 2023-02-21 | Bank Of America Corporation | System for secure resource transfer integration |
| US11632244B2 (en) | 2020-09-14 | 2023-04-18 | Paypal, Inc. | Techniques for single round multi-party computation for digital signatures |
| US11636471B2 (en) | 2017-12-15 | 2023-04-25 | Fmr Llc | Social data tracking datastructures, apparatuses, methods and systems |
| US11687885B2 (en) | 2015-02-27 | 2023-06-27 | Visa International Service Association | Transaction signing utilizing asymmetric cryptography |
| US11736290B1 (en) | 2022-11-07 | 2023-08-22 | Ledgerdomain Inc. | Management of recipient credentials leveraging private keys on keystores read by provisioned devices |
| US11741216B1 (en) | 2022-11-07 | 2023-08-29 | Ledgerdomain Inc. | Credential revocation leveraging private keys on keystores read by provisioned devices |
| US11741215B1 (en)* | 2022-11-07 | 2023-08-29 | Ledgerdomain Inc. | Recipient credentialing leveraging private keys on keystores read by provisioned devices |
| US11769577B1 (en) | 2020-01-15 | 2023-09-26 | Ledgerdomain Inc. | Decentralized identity authentication framework for distributed data |
| US11829510B2 (en) | 2020-01-15 | 2023-11-28 | Ledgerdomain Inc. | Secure messaging in a machine learning blockchain network |
| US11848754B1 (en) | 2022-11-07 | 2023-12-19 | Ledgerdomain Inc. | Access delegation leveraging private keys on keystores read by provisioned devices |
| US11909860B1 (en) | 2018-02-12 | 2024-02-20 | Gemini Ip, Llc | Systems, methods, and program products for loaning digital assets and for depositing, holding and/or distributing collateral as a token in the form of digital assets on an underlying blockchain |
| US11915314B2 (en) | 2019-11-22 | 2024-02-27 | Conio Inc. | Method and apparatus for a blockchain-agnostic safe multi-signature digital asset management |
| US11922403B2 (en) | 2021-03-31 | 2024-03-05 | Paypal, Inc. | Using an internal ledger with blockchain transactions |
| US11989720B2 (en) | 2020-10-14 | 2024-05-21 | Mobilecoin Inc. | System and method for oblivious information retrieval |
| US12088701B2 (en) | 2018-12-06 | 2024-09-10 | Galaxy Digital Trading Llc | Secure consensus over a limited connection |
| US12093942B1 (en) | 2019-02-22 | 2024-09-17 | Gemini Ip, Llc | Systems, methods, and program products for modifying the supply, depositing, holding, and/or distributing collateral as a stable value token in the form of digital assets |
| US12105842B1 (en) | 2020-01-15 | 2024-10-01 | Ledgerdomain Inc. | Verifiable credentialling and message content provenance authentication |
| US12141871B1 (en) | 2018-02-12 | 2024-11-12 | Gemini Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
| US12225127B2 (en) | 2015-07-14 | 2025-02-11 | Fmr Llc | Address verification, seed splitting and firmware extension for secure cryptocurrency key backup, restore, and transaction signing platform apparatuses, methods and systems |
| US12271898B1 (en) | 2018-03-05 | 2025-04-08 | Gemini Ip, Llc | System, method and program product for modifying a supply of stable value digital asset tokens |
| US12323524B2 (en) | 2015-07-14 | 2025-06-03 | Fmr Llc | Social aggregating, fractionally efficient transfer guidance, conditional triggered transaction, datastructures, apparatuses, methods and systems |
Families Citing this family (328)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10521776B2 (en)* | 2002-10-01 | 2019-12-31 | Andrew H B Zhou | UN currency (virtual payment cards) issued by central bank or other issuer for mobile and wearable devices |
| US10521777B2 (en)* | 2002-10-01 | 2019-12-31 | World Award Foundation Inc, Ab Stable Group Llc, Mobile Pay, Inc | Crypto digital currency (virtual payment cards) issued by central bank or other issuer for mobile and wearable devices |
| AU2011316955B2 (en) | 2010-10-20 | 2016-12-01 | Playspan Inc. | Flexible monetization service apparatuses, methods and systems |
| US10438176B2 (en) | 2011-07-17 | 2019-10-08 | Visa International Service Association | Multiple merchant payment processor platform apparatuses, methods and systems |
| US10318941B2 (en) | 2011-12-13 | 2019-06-11 | Visa International Service Association | Payment platform interface widget generation apparatuses, methods and systems |
| WO2013090611A2 (en)* | 2011-12-13 | 2013-06-20 | Visa International Service Association | Dynamic widget generator apparatuses, methods and systems |
| US10102510B2 (en)* | 2012-11-28 | 2018-10-16 | Hoverkey Ltd. | Method and system of conducting a cryptocurrency payment via a mobile device using a contactless token to store and protect a user's secret key |
| US9547622B1 (en) | 2013-07-02 | 2017-01-17 | Inphi Corporation | Monolithically integrated system on chip for silicon photonics |
| US10733138B2 (en)* | 2013-07-02 | 2020-08-04 | Inphi Corporation | Silicon photonics based module for storing cryptocurrency and executing peer-to-peer transaction |
| US20150178819A1 (en)* | 2013-12-23 | 2015-06-25 | @Pay Ip Holdings Llc | Alternative email-based website checkouts |
| WO2015123691A1 (en) | 2014-02-14 | 2015-08-20 | Boemi Andrew A | Mobile device payment system and method |
| US11270298B2 (en)* | 2014-04-14 | 2022-03-08 | 21, Inc. | Digital currency mining circuitry |
| US11164164B2 (en)* | 2014-05-15 | 2021-11-02 | Uphold Global Foundation | System and method for converting cryptocurrency to virtual assets whose value is substantiated by a reserve of assets |
| US10565645B1 (en) | 2014-05-20 | 2020-02-18 | Wells Fargo Bank, N.A. | Systems and methods for operating a math-based currency exchange |
| US11176524B1 (en) | 2014-05-20 | 2021-11-16 | Wells Fargo Bank, N.A. | Math based currency credit card |
| US11037110B1 (en) | 2014-05-20 | 2021-06-15 | Wells Fargo Bank, N.A. | Math based currency point of sale systems and methods |
| US11170351B1 (en) | 2014-05-20 | 2021-11-09 | Wells Fargo Bank, N.A. | Systems and methods for identity verification of math-based currency account holders |
| US11270274B1 (en) | 2014-05-20 | 2022-03-08 | Wells Fargo Bank, N.A. | Mobile wallet using math based currency systems and methods |
| US11062278B1 (en)* | 2014-05-20 | 2021-07-13 | Wells Fargo Bank, N.A. | Systems and methods for math-based currency credit transactions |
| US20150363769A1 (en)* | 2014-06-16 | 2015-12-17 | Bank Of America Corporation | Cryptocurrency Real-Time Conversion System |
| US11699148B2 (en) | 2014-12-23 | 2023-07-11 | Swoop Ip Holdings Llc | Email address token integration |
| US9413735B1 (en)* | 2015-01-20 | 2016-08-09 | Ca, Inc. | Managing distribution and retrieval of security key fragments among proxy storage devices |
| US11216468B2 (en) | 2015-02-08 | 2022-01-04 | Visa International Service Association | Converged merchant processing apparatuses, methods and systems |
| CN112565181A (en) | 2015-02-09 | 2021-03-26 | 缇零集团股份有限公司 | Encryption integration platform |
| US20160260091A1 (en)* | 2015-03-04 | 2016-09-08 | THC Farmaceuticals, Inc. | Universal wallet for digital currency |
| HK1249791A1 (en)* | 2015-03-31 | 2018-11-09 | Nasdaq, Inc. | Systems and methods of blockchain transaction recordation |
| KR101628009B1 (en)* | 2015-04-20 | 2016-06-13 | 주식회사 코인플러그 | System for dealing a digital currency with block chain |
| US20160321751A1 (en)* | 2015-04-28 | 2016-11-03 | Domus Tower, Inc. | Real-time settlement of securities trades over append-only ledgers |
| US20220237696A1 (en)* | 2015-04-28 | 2022-07-28 | Domus Tower, Inc. | Settlement of securities trades using append only ledgers |
| US10007913B2 (en) | 2015-05-05 | 2018-06-26 | ShoCard, Inc. | Identity management service using a blockchain providing identity transactions between devices |
| US9876646B2 (en) | 2015-05-05 | 2018-01-23 | ShoCard, Inc. | User identification management system and method |
| US11392955B2 (en) | 2015-05-20 | 2022-07-19 | Ripple Luxembourg S.A. | Temporary consensus networks in a resource transfer system |
| US11392944B2 (en) | 2015-05-20 | 2022-07-19 | Ripple Luxembourg S.A. | Transfer costs in a resource transfer system |
| US10740732B2 (en) | 2015-05-20 | 2020-08-11 | Ripple Luxembourg S.A. | Resource transfer system |
| US11367072B2 (en)* | 2015-05-20 | 2022-06-21 | Ripple Luxembourg S.A. | Private networks and content requests in a resource transfer system |
| US20160342977A1 (en)* | 2015-05-20 | 2016-11-24 | Vennd.io Pty Ltd | Device, method and system for virtual asset transactions |
| US11481771B2 (en) | 2015-05-20 | 2022-10-25 | Ripple Luxembourg S.A. | One way functions in a resource transfer system |
| US11386415B2 (en) | 2015-05-20 | 2022-07-12 | Ripple Luxembourg S.A. | Hold condition in a resource transfer system |
| US9870562B2 (en)* | 2015-05-21 | 2018-01-16 | Mastercard International Incorporated | Method and system for integration of market exchange and issuer processing for blockchain-based transactions |
| CN107851252B (en)* | 2015-05-26 | 2022-07-19 | 缇零知识产权有限责任公司 | Obfuscating intent in a transaction using encryption techniques |
| US11232415B2 (en)* | 2015-05-28 | 2022-01-25 | OX Labs Inc. | Method for cryptographically managing title transactions |
| US11436575B2 (en)* | 2015-06-05 | 2022-09-06 | Arris Enterprises Llc | Virtual wallet for customer premise equipment device |
| US10558996B2 (en)* | 2015-06-09 | 2020-02-11 | Fidelity National Information Services, Llc | Methods and systems for regulating operation of units using encryption techniques associated with a blockchain |
| US11069000B1 (en) | 2015-06-16 | 2021-07-20 | BitPagos, Inc. | Payment processing service utilizing a distributed ledger digital asset |
| WO2017004527A1 (en) | 2015-07-02 | 2017-01-05 | Nasdaq, Inc. | Systems and methods of secure provenance for distributed transaction databases |
| US10552904B2 (en)* | 2015-07-24 | 2020-02-04 | Castor Pollux Holdings SARL | Device, system, and method for transfer of commodities |
| US11657386B2 (en)* | 2015-08-21 | 2023-05-23 | Samsung Electronics Co., Ltd. | Reference-based card enrollment for secondary devices |
| US10504080B2 (en)* | 2015-09-14 | 2019-12-10 | OX Labs Inc. | Cryptographically managingtelecommunications settlement |
| PL3362970T3 (en)* | 2015-10-17 | 2025-01-07 | Banqu, Inc. | Blockchain-based identity and transaction platform |
| WO2017070469A1 (en)* | 2015-10-22 | 2017-04-27 | Align Commerce Corporation | System and method for payment processing using crypto currencies |
| US20170132625A1 (en)* | 2015-11-05 | 2017-05-11 | Mastercard International Incorporated | Method and system for use of a blockchain in a transaction processing network |
| US20170132626A1 (en)* | 2015-11-05 | 2017-05-11 | Mastercard International Incorporated | Method and system for processing of a blockchain transaction in a transaction processing network |
| US11941588B2 (en) | 2015-11-06 | 2024-03-26 | Cable Television Laboratories, Inc. | Systems and methods for blockchain virtualization and scalability |
| US11494761B2 (en)* | 2015-11-06 | 2022-11-08 | Cable Television Laboratories, Inc. | Systems and methods for digital asset security ecosystems |
| US20170132630A1 (en)* | 2015-11-11 | 2017-05-11 | Bank Of America Corporation | Block chain alias for person-to-person payments |
| DE102015222347B4 (en)* | 2015-11-12 | 2017-07-06 | Bundesdruckerei Gmbh | Electronic payment method and server computer |
| US10719816B1 (en) | 2015-11-19 | 2020-07-21 | Wells Fargo Bank, N.A. | Systems and methods for math-based currency escrow transactions |
| US10586062B1 (en) | 2015-11-23 | 2020-03-10 | United Services Automobile Association (Usaa) | Systems and methods to track, store, and manage events, rights and liabilities |
| KR102351720B1 (en)* | 2015-11-25 | 2022-01-13 | 주식회사 케이티 | Data backhaul device for providing opportunistic connectivity and method for data transmission |
| US11210663B2 (en)* | 2015-11-30 | 2021-12-28 | Shapeshift Ag | Digital asset zero-custody switch |
| US11270299B2 (en) | 2015-12-07 | 2022-03-08 | Visa International Service Association | Methods and systems of using a cryptocurrency system to manage payments and payment alternatives |
| US10818170B1 (en) | 2016-01-20 | 2020-10-27 | United Services Automobile Association | Systems and methods for traffic management via inter-party resource allocation |
| US10108812B2 (en) | 2016-01-28 | 2018-10-23 | Nasdaq, Inc. | Systems and methods for securing and disseminating time sensitive information using a blockchain |
| EP3200167A1 (en)* | 2016-01-29 | 2017-08-02 | Mastercard International Incorporated | Information transaction infrastructure |
| AU2017216289A1 (en) | 2016-02-04 | 2018-09-27 | Nasdaq Technology Ab | Systems and methods for storing and sharing transactional data using distributed computer systems |
| US11374935B2 (en) | 2016-02-11 | 2022-06-28 | Bank Of America Corporation | Block chain alias person-to-person resource allocation |
| US10762504B2 (en) | 2016-02-22 | 2020-09-01 | Bank Of America Corporation | System for external secure access to process data network |
| US10496989B2 (en) | 2016-02-22 | 2019-12-03 | Bank Of America Corporation | System to enable contactless access to a transaction terminal using a process data network |
| US10636033B2 (en) | 2016-02-22 | 2020-04-28 | Bank Of America Corporation | System for routing of process authorizations and settlement to a user in a process data network |
| US10387878B2 (en) | 2016-02-22 | 2019-08-20 | Bank Of America Corporation | System for tracking transfer of resources in a process data network |
| US10475030B2 (en) | 2016-02-22 | 2019-11-12 | Bank Of America Corporation | System for implementing a distributed ledger across multiple network nodes |
| BR112018016234A2 (en) | 2016-02-23 | 2019-01-02 | Nchain Holdings Ltd | computer-implemented method for controlling access to a resource, computer-based systems and method for controlling access to a digital wallet |
| MX2018010050A (en) | 2016-02-23 | 2019-01-21 | Nchain Holdings Ltd | Agent-based turing complete transactions integrating feedback within a blockchain system. |
| CN115641131A (en) | 2016-02-23 | 2023-01-24 | 区块链控股有限公司 | Method and system for secure transfer of entities over a blockchain |
| JP6511201B1 (en) | 2016-02-23 | 2019-05-15 | エヌチェーン ホールディングス リミテッドＮｃｈａｉｎ Ｈｏｌｄｉｎｇｓ Ｌｉｍｉｔｅｄ | Registry and Automated Management Method for Sophisticated Trading Enforced by Blockchain |
| CN116957790A (en) | 2016-02-23 | 2023-10-27 | 区块链控股有限公司 | Method and system for realizing universal certification of exchange on blockchain |
| BR112018016821A2 (en) | 2016-02-23 | 2018-12-26 | Nchain Holdings Ltd | computer-implemented system and methods |
| BR112018016819A2 (en) | 2016-02-23 | 2018-12-26 | Nchain Holdings Ltd | method and systems for protecting a controlled digital resource using a distributed scatter table and ledger and a blockchain |
| AU2017223138B2 (en) | 2016-02-23 | 2022-02-10 | nChain Holdings Limited | Method and system for efficient transfer of cryptocurrency associated with a payroll on a blockchain that leads to an automated payroll method and system based on smart contracts |
| CN108292402B (en) | 2016-02-23 | 2022-10-04 | 恩链控股有限公司 | Determination of a common secret and hierarchical deterministic keys for the secure exchange of information |
| SG11201806702XA (en) | 2016-02-23 | 2018-09-27 | Nchain Holdings Ltd | Personal device security using elliptic curve cryptography for secret sharing |
| EP3748903A1 (en) | 2016-02-23 | 2020-12-09 | Nchain Holdings Limited | Universal tokenisation system for blockchain-based cryptocurrencies |
| GB2562622A (en) | 2016-02-23 | 2018-11-21 | Nchain Holdings Ltd | Cryptographic method and system for secure extraction of data from a blockchain |
| EP4235552A3 (en)* | 2016-02-23 | 2023-09-13 | nChain Licensing AG | Methods and systems for efficient transfer of entities on a peer-to-peer distributed ledger using the blockchain |
| MX2018010052A (en)* | 2016-02-23 | 2019-01-21 | Nchain Holdings Ltd | System and method for controlling asset-related actions via a blockchain. |
| IL261210B (en)* | 2016-02-23 | 2022-08-01 | Nchain Holdings Ltd | An exchange based on a 'block chain' with tokenization |
| EP3424179B1 (en) | 2016-03-04 | 2022-02-16 | Ping Identity Corporation | Method and system for authenticated login using static or dynamic codes |
| US10007826B2 (en) | 2016-03-07 | 2018-06-26 | ShoCard, Inc. | Transferring data files using a series of visual codes |
| US10509932B2 (en) | 2016-03-07 | 2019-12-17 | ShoCard, Inc. | Large data transfer using visual codes with feedback confirmation |
| WO2017161417A1 (en)* | 2016-03-21 | 2017-09-28 | National Ict Australia Limited | Business process execution on a blockchain platform |
| US9985964B2 (en)* | 2016-03-28 | 2018-05-29 | Black Gold Coin, Inc. | Systems and methods for providing block chain-based multifactor personal identity verification |
| KR102859519B1 (en)* | 2016-04-11 | 2025-09-17 | 엔체인 라이센싱 아게 | A method for secure peer to peer communication on a blockchain |
| WO2017189027A1 (en) | 2016-04-29 | 2017-11-02 | Digital Asset Holdings | Digital asset modeling |
| US10135616B2 (en)* | 2016-05-07 | 2018-11-20 | Keir Finlow-Bates | Revocation of cryptographic keys in the absence of a trusted central authority |
| AU2017263465B9 (en)* | 2016-05-11 | 2021-01-28 | Nasdaq, Inc. | Application framework using blockchain-based asset ownership |
| MX2018013617A (en) | 2016-05-13 | 2019-04-25 | Nchain Holdings Ltd | A method and system for verifying integrity of a digital asset using a distributed hash table and a peer-to-peer distributed ledger. |
| US11270303B2 (en)* | 2016-05-20 | 2022-03-08 | Fujitsu Limited | Cryptocurrency-based event participation verification |
| US11361316B2 (en)* | 2016-06-06 | 2022-06-14 | Refinitiv Us Organization Llc | Systems and methods for providing a personal distributed ledger |
| US20170357966A1 (en)* | 2016-06-09 | 2017-12-14 | Mastercard International Incorporated | Method and system for use of a proprietary private blockchain |
| US10289991B1 (en)* | 2016-06-13 | 2019-05-14 | Square, Inc. | Utilizing APIs to facilitate open ticket synchronization |
| US10341309B1 (en) | 2016-06-13 | 2019-07-02 | Allstate Insurance Company | Cryptographically protecting data transferred between spatially distributed computing devices using an intermediary database |
| CN106101242B (en)* | 2016-06-24 | 2019-08-06 | 深圳前海微众银行股份有限公司 | Construction method and device of block chain cloud service platform |
| US20170372417A1 (en)* | 2016-06-28 | 2017-12-28 | Sivanarayana Gaddam | Digital asset account management |
| TWI588763B (en)* | 2016-07-19 | 2017-06-21 | 富邦金融控股股份有限公司 | Virtual currency crediting system based on physical assets and method thereof |
| KR102665646B1 (en)* | 2016-07-25 | 2024-05-10 | 티비씨에이소프트, 인코포레이티드 | Digital asset management on a decentralized trading consensus network |
| US10679267B2 (en)* | 2016-08-03 | 2020-06-09 | Raise Marketplace, Llc | Method and system for consumption based redemption in an exchange item marketplace network |
| US20180046992A1 (en)* | 2016-08-10 | 2018-02-15 | Jpmorgan Chase Bank, N.A. | Systems and methods for account reconciliation using a distributed ledger |
| US10628807B2 (en)* | 2016-08-16 | 2020-04-21 | Visa International Service Association | Techniques for transaction management |
| CN106357604B (en)* | 2016-08-18 | 2019-07-23 | 苏州超块链信息科技有限公司 | A kind of consistent data accumulation collaboration assemble method |
| TWI651671B (en)* | 2016-08-25 | 2019-02-21 | 第一商業銀行股份有限公司 | Fast blockchain trading method |
| US10402796B2 (en)* | 2016-08-29 | 2019-09-03 | Bank Of America Corporation | Application life-cycle transition record recreation system |
| US11551207B2 (en)* | 2016-08-30 | 2023-01-10 | Paypal, Inc. | Expedited virtual currency transaction system |
| CN106357405A (en)* | 2016-09-19 | 2017-01-25 | 弗洛格（武汉）信息科技有限公司 | Method and system for managing data on basis of block chain technology consistency algorithms |
| US11455642B1 (en)* | 2016-09-19 | 2022-09-27 | United Services Automobile Association (Usaa) | Distributed ledger based interchange |
| EP4492729A3 (en) | 2016-10-25 | 2025-04-09 | nChain Licensing AG | Blockchain-based method and system for specifying the recipient of an electronic communication |
| CN106528746B (en)* | 2016-10-26 | 2019-07-16 | 江苏通付盾科技有限公司 | Transaction Information querying method, apparatus and system |
| US10628491B2 (en)* | 2016-11-09 | 2020-04-21 | Cognitive Scale, Inc. | Cognitive session graphs including blockchains |
| JP6533771B2 (en)* | 2016-11-15 | 2019-06-19 | 富士通株式会社 | Communication method, apparatus and program |
| CN106506505A (en)* | 2016-11-15 | 2017-03-15 | 深圳银链科技有限公司 | A kind of list based on block chain is close to be chatted and group close merely method and its system |
| US10749685B2 (en)* | 2016-12-02 | 2020-08-18 | First Data Corporation | Network provisioning systems and methods |
| US11823089B2 (en)* | 2016-12-02 | 2023-11-21 | Christian Günther | System and method for managing transactions in dynamic digital documents |
| US10387684B2 (en) | 2016-12-09 | 2019-08-20 | International Business Machines Corporation | Interlocked blockchains to increase blockchain security |
| MX2019007003A (en)* | 2016-12-15 | 2019-11-28 | Walmart Apollo Llc | Apparatus and method for collaborative shopping. |
| US10419225B2 (en) | 2017-01-30 | 2019-09-17 | Factom, Inc. | Validating documents via blockchain |
| US10498541B2 (en) | 2017-02-06 | 2019-12-03 | ShocCard, Inc. | Electronic identification verification methods and systems |
| USRE49968E1 (en) | 2017-02-06 | 2024-05-14 | Ping Identity Corporation | Electronic identification verification methods and systems with storage of certification records to a side chain |
| CA3090944A1 (en) | 2017-02-08 | 2018-08-16 | Upstream Data Inc. | Blockchain mine at oil or gas facility |
| US10560268B2 (en) | 2017-02-13 | 2020-02-11 | International Business Machines Corporation | Node characterization in a blockchain |
| US10411897B2 (en) | 2017-02-17 | 2019-09-10 | Factom, Inc. | Secret sharing via blockchains |
| US10817873B2 (en) | 2017-03-22 | 2020-10-27 | Factom, Inc. | Auditing of electronic documents |
| US11151553B2 (en) | 2017-03-23 | 2021-10-19 | At&T Intellectual Property I, L.P. | Time and geographically restrained blockchain services |
| US11157900B2 (en)* | 2017-03-24 | 2021-10-26 | Mastercard International Incorporated | Method and system for offline data transfer via machine-readable code |
| CN107395557B (en) | 2017-03-28 | 2020-05-15 | 创新先进技术有限公司 | A service request processing method and device |
| US10685399B2 (en) | 2017-03-31 | 2020-06-16 | Factom, Inc. | Due diligence in electronic documents |
| US11538031B2 (en) | 2017-03-31 | 2022-12-27 | Vijay Madisetti | Method and system for identity and access management for blockchain interoperability |
| US10270599B2 (en) | 2017-04-27 | 2019-04-23 | Factom, Inc. | Data reproducibility using blockchains |
| CN107277781B (en)* | 2017-05-03 | 2019-03-22 | 上海点融信息科技有限责任公司 | Block chain multicast network, block chain equipment and its communication means under mobile broadband network |
| CN107317672A (en)* | 2017-05-10 | 2017-11-03 | 广东网金控股股份有限公司 | A kind of light weight terminating machine block catenary system |
| US20180330342A1 (en)* | 2017-05-11 | 2018-11-15 | Gyan Prakash | Digital asset account management |
| US10447770B2 (en)* | 2017-05-30 | 2019-10-15 | Verizon Patent And Licensing Inc. | Blockchain micro-services framework |
| CN107248076A (en)* | 2017-06-24 | 2017-10-13 | 北京天德科技有限公司 | A kind of core algorithm of the double-chain block chain the Internet model merchandised across chain |
| US10608910B2 (en) | 2017-06-26 | 2020-03-31 | Myomega Systems Gmbh | Using blockchain to track information for devices on a network |
| WO2019000087A1 (en)* | 2017-06-28 | 2019-01-03 | Kitaru Innovations Inc. | Method of operating and using a cryptocurrency |
| US11416832B2 (en)* | 2017-07-18 | 2022-08-16 | nChain Holdings Limited | Systems and methods for blockchain-dependent operation sets |
| FR3069356A1 (en)* | 2017-07-19 | 2019-01-25 | Infinity Space | METHOD AND SYSTEM FOR MANAGING PAYMENT BY ELECTRONIC WALLET |
| CN107920052B (en)* | 2017-08-02 | 2020-11-17 | 唐盛（北京）物联技术有限公司 | Encryption method and intelligent device |
| CN107249009B (en)* | 2017-08-02 | 2020-02-21 | 广东工业大学 | A method and system for data verification based on blockchain |
| US11461768B2 (en)* | 2017-08-21 | 2022-10-04 | American Express Travel Related Services Company, Inc. | Systems and methods for data file transfer balancing and control on blockchain |
| CN107507091A (en)* | 2017-09-07 | 2017-12-22 | 复旦大学 | Enhanced data Right protection method based on block chain and intelligent contract |
| US20190080402A1 (en)* | 2017-09-11 | 2019-03-14 | Templum, Llc | System and method for providing a regulatory-compliant token |
| US10873457B1 (en) | 2017-09-13 | 2020-12-22 | Inveniam.io, LLC | Data structure having internal self-references suitable for immutably representing and verifying data generated over time |
| US11449887B2 (en) | 2017-10-09 | 2022-09-20 | American Express Travel Related Services Company, Inc. | Systems and methods for loyalty point distribution |
| US11699166B2 (en) | 2017-10-09 | 2023-07-11 | American Express Travel Related Services Company, Inc. | Multi-merchant loyalty point partnership |
| US10567320B2 (en) | 2017-10-17 | 2020-02-18 | American Express Travel Related Services Company, Inc. | Messaging balancing and control on blockchain |
| US10469248B2 (en) | 2017-10-17 | 2019-11-05 | Amrican Express Travel Related Services Company, Inc. | API request and response balancing and control on blockchain |
| WO2019099357A1 (en)* | 2017-11-14 | 2019-05-23 | Worldcast Live Inc. | Computing technologies for musical performances |
| CN109840766B (en)* | 2017-11-27 | 2024-03-29 | 华为终端有限公司 | Equipment control method and related equipment |
| CN107945020B (en)* | 2017-11-28 | 2021-11-12 | 浙江师范大学 | Block chain sustainable mining method and system |
| US11836717B2 (en) | 2017-12-04 | 2023-12-05 | Vijay Madisetti | System and method for processing payments in fiat currency using blockchain and tethered tokens |
| US20190311357A1 (en)* | 2018-04-04 | 2019-10-10 | Vijay Madisetti | Method and System for Exchange of Value or Tokens Between Blockchain Networks |
| US10853772B2 (en)* | 2018-04-04 | 2020-12-01 | Vijay K. Madisetti | Method and system for exchange of value or tokens between blockchain networks |
| US10320843B1 (en) | 2017-12-08 | 2019-06-11 | Symbiont.Io, Inc. | Methods, systems, and devices for encrypted electronic storage and confidential network transfer of private data through a trustless distributed ledger technology system |
| EP4120620A1 (en) | 2017-12-08 | 2023-01-18 | Ping Identity Corporation | Methods and systems for recovering data using dynamic passwords |
| US10476847B1 (en) | 2017-12-08 | 2019-11-12 | Symbiont.Io, Inc. | Systems, methods, and devices for implementing a smart contract on a distributed ledger technology platform |
| CN109936601B (en)* | 2017-12-18 | 2022-10-25 | 本无链科技(深圳)有限公司 | Block chain duplex communication method based on WebSocket connection |
| WO2019127278A1 (en)* | 2017-12-28 | 2019-07-04 | 深圳达闼科技控股有限公司 | Safe access blockchain method, apparatus, system, storage medium, and electronic device |
| US11164181B2 (en)* | 2018-01-12 | 2021-11-02 | Visa International Service Association | Techniques for conducting transactions utilizing cryptocurrency |
| US11010233B1 (en) | 2018-01-18 | 2021-05-18 | Pure Storage, Inc | Hardware-based system monitoring |
| US20190236564A1 (en)* | 2018-01-31 | 2019-08-01 | Walmart Apollo, Llc | System and method for digital currency via blockchain |
| US10439812B2 (en)* | 2018-02-02 | 2019-10-08 | SquareLink, Inc. | Technologies for private key recovery in distributed ledger systems |
| US11188897B2 (en)* | 2018-02-13 | 2021-11-30 | Bank Of America Corporation | Multi-tiered digital wallet security |
| CN108335206B (en) | 2018-02-14 | 2020-12-22 | 创新先进技术有限公司 | Asset management method and device and electronic equipment |
| CN108416675A (en)* | 2018-02-14 | 2018-08-17 | 阿里巴巴集团控股有限公司 | Asset management method and device, electronic equipment |
| CN108335207B (en) | 2018-02-14 | 2020-08-04 | 阿里巴巴集团控股有限公司 | Asset management method and device and electronic equipment |
| CN108492180B (en) | 2018-02-14 | 2020-11-24 | 创新先进技术有限公司 | Asset management method and device and electronic equipment |
| CN108389118B (en) | 2018-02-14 | 2020-05-29 | 阿里巴巴集团控股有限公司 | Asset management system, method and device and electronic equipment |
| CA3034098A1 (en) | 2018-02-20 | 2019-08-20 | Intercontinental Exchange Holdings, Inc. | Offline crypto asset custodian |
| US12401518B2 (en)* | 2018-02-27 | 2025-08-26 | Anchor Labs, Inc. | Cryptoasset custodial system with different rules governing access to logically separated cryptoassets |
| CN108389129B (en) | 2018-02-27 | 2020-12-04 | 创新先进技术有限公司 | Blockchain-based transaction execution method and device, and electronic device |
| WO2019169378A1 (en)* | 2018-03-02 | 2019-09-06 | Griffith Nicholas B | Central registry system for cryptocurrencies |
| US11790470B1 (en) | 2018-03-16 | 2023-10-17 | Block, Inc. | Storage service for sensitive customer data |
| US11863659B2 (en)* | 2018-03-23 | 2024-01-02 | Accenture Global Solutions Limited | Shipping platform |
| CN110324285A (en)* | 2018-03-30 | 2019-10-11 | 武汉斗鱼网络科技有限公司 | A kind of mobile terminal auth method and device |
| US11157898B2 (en)* | 2018-03-30 | 2021-10-26 | Health Alliance Management, LLC | Systems and methods for peer-to-peer transmission of digital assets |
| CA3038757A1 (en)* | 2018-04-02 | 2019-10-02 | Royal Bank Of Canada | System and method for cryptographic transactions |
| GB201806112D0 (en)* | 2018-04-13 | 2018-05-30 | Nchain Holdings Ltd | Computer-implemented system and method |
| US10783545B2 (en)* | 2018-04-19 | 2020-09-22 | American Express Travel Related Services Company, Inc. | Reward point redemption for cryptocurrency |
| KR102264942B1 (en)* | 2018-04-20 | 2021-06-14 | 이청종 | Domain-digital asset interworking method |
| US20190333048A1 (en)* | 2018-04-27 | 2019-10-31 | Social Wallet, Inc. | Systems and methods for zero knowledge crypto-asset exchange |
| KR20190125200A (en) | 2018-04-27 | 2019-11-06 | 주식회사 오투오컨티뉴엄 | CRYPTOCURRENCY CIRCULATION METHOD AND SYSTEM USING DATA BASED ON IoT |
| KR20190125201A (en) | 2018-04-27 | 2019-11-06 | 주식회사 오투오컨티뉴엄 | Cryptocurrency circulation method and system using personal data |
| US20190332691A1 (en)* | 2018-04-30 | 2019-10-31 | Robert Dale Beadles | Universal subscription and cryptocurrency payment management platforms and methods of use |
| US20190340586A1 (en)* | 2018-05-04 | 2019-11-07 | Smart Worldwide Financial Technology | Conducting optimized cross-blockchain currency transactions using machine learning |
| CN108737536B (en)* | 2018-05-14 | 2021-11-09 | 百度在线网络技术（北京）有限公司 | Method, device, equipment and storage medium for realizing block chain system |
| JP7121810B2 (en)* | 2018-05-15 | 2022-08-18 | ケルビン ゼロ インコーポレーテッド | Systems, methods, devices and terminals for secure blockchain transactions and sub-networks |
| US10783164B2 (en) | 2018-05-18 | 2020-09-22 | Factom, Inc. | Import and export in blockchain environments |
| US11134120B2 (en) | 2018-05-18 | 2021-09-28 | Inveniam Capital Partners, Inc. | Load balancing in blockchain environments |
| US11170366B2 (en) | 2018-05-18 | 2021-11-09 | Inveniam Capital Partners, Inc. | Private blockchain services |
| US11429565B2 (en) | 2018-05-24 | 2022-08-30 | International Business Machines Corporation | Terms of service platform using blockchain |
| CN108898483A (en)* | 2018-05-29 | 2018-11-27 | 阿里巴巴集团控股有限公司 | Publication, exchanging method and its device, the electronic equipment of block chain assets |
| CN108876606B (en) | 2018-05-29 | 2021-02-09 | 创新先进技术有限公司 | Asset transfer method and device and electronic equipment |
| CN108805712B (en) | 2018-05-29 | 2021-03-23 | 创新先进技术有限公司 | Asset transfer rollback processing method and device and electronic equipment |
| CN108876572A (en)* | 2018-05-29 | 2018-11-23 | 阿里巴巴集团控股有限公司 | The account checking method and device, electronic equipment of block chain transaction |
| CN109035636A (en) | 2018-06-04 | 2018-12-18 | 阿里巴巴集团控股有限公司 | A kind of Cash collecting equipment, a kind of cashing method and device |
| US20190378119A1 (en)* | 2018-06-12 | 2019-12-12 | Fressets Inc. | Wallet device for cryptocurrency and method of signature for the use thereof |
| US11379824B2 (en)* | 2018-06-20 | 2022-07-05 | International Business Machines Corporation | Privacy preserving transactions with probabilistic transaction fees |
| EP3821387A4 (en)* | 2018-07-13 | 2022-05-04 | Elbaite Holdings Pty Limited | PROCEDURES TO FACILITATE TRANSACTIONS BETWEEN USERS |
| CN109003081B (en)* | 2018-07-13 | 2021-11-02 | 北京创世智链信息技术研究院 | Transaction method, system and storage medium based on block chain |
| JP2020016980A (en)* | 2018-07-24 | 2020-01-30 | 弘樹 松平 | Settlement auxiliary system and settlement auxiliary method |
| US11276059B2 (en)* | 2018-07-31 | 2022-03-15 | Molten Inc. | System and method for autonomous sustenance of digital assets |
| US10929545B2 (en) | 2018-07-31 | 2021-02-23 | Bank Of America Corporation | System for providing access to data stored in a distributed trust computing network |
| CN109033403B (en)* | 2018-08-03 | 2020-05-12 | 上海点融信息科技有限责任公司 | Method, apparatus and storage medium for searching blockchain data |
| CN109033406B (en)* | 2018-08-03 | 2020-06-05 | 上海点融信息科技有限责任公司 | Method, apparatus and storage medium for searching blockchain data |
| US11348097B2 (en) | 2018-08-06 | 2022-05-31 | Inveniam Capital Partners, Inc. | Digital contracts in blockchain environments |
| US11164250B2 (en) | 2018-08-06 | 2021-11-02 | Inveniam Capital Partners, Inc. | Stable cryptocurrency coinage |
| US11328290B2 (en) | 2018-08-06 | 2022-05-10 | Inveniam Capital Partners, Inc. | Stable cryptocurrency coinage |
| US11989208B2 (en) | 2018-08-06 | 2024-05-21 | Inveniam Capital Partners, Inc. | Transactional sharding of blockchain transactions |
| US11044095B2 (en) | 2018-08-06 | 2021-06-22 | Factom, Inc. | Debt recordation to blockchains |
| US11716614B2 (en)* | 2018-08-16 | 2023-08-01 | Comcast Cable Communications, Llc | Secured data derivation for user devices |
| WO2020039645A1 (en)* | 2018-08-23 | 2020-02-27 | 寛 鳥居 | Money transfer instruction device, money transfer instruction method, money transfer instruction program, and money transfer instruction system |
| US12062090B2 (en)* | 2018-08-28 | 2024-08-13 | Cboe Exchange, Inc. | Blockchain-enabled electronic futures trading system with optional computerized delivery of cryptocurrency |
| US11769147B2 (en) | 2018-08-30 | 2023-09-26 | International Business Machines Corporation | Secure smart note |
| US11893554B2 (en)* | 2018-08-30 | 2024-02-06 | International Business Machines Corporation | Secure smart note |
| WO2020069491A1 (en) | 2018-09-28 | 2020-04-02 | Strike Derivatives Inc. | Electronic trade processing system and method |
| CN109242458A (en)* | 2018-09-30 | 2019-01-18 | 深圳市元征科技股份有限公司 | Approaches to IM and relevant device based on block chain |
| JP6522842B1 (en)* | 2018-10-05 | 2019-05-29 | さくら情報システム株式会社 | INFORMATION PROCESSING APPARATUS, METHOD, AND PROGRAM |
| CN109544127A (en)* | 2018-10-10 | 2019-03-29 | 北京番茄大陆科技有限公司 | Transfer account method, device and the equipment of stored value card |
| US11082221B2 (en) | 2018-10-17 | 2021-08-03 | Ping Identity Corporation | Methods and systems for creating and recovering accounts using dynamic passwords |
| US10979227B2 (en) | 2018-10-17 | 2021-04-13 | Ping Identity Corporation | Blockchain ID connect |
| CN113015991A (en)* | 2018-10-19 | 2021-06-22 | 贝尔识别有限公司 | Secure digital wallet processing system |
| TWI685801B (en)* | 2018-10-25 | 2020-02-21 | 恩旺股份有限公司 | Online and offline virtual currency transfer method and system |
| WO2020092222A1 (en)* | 2018-10-28 | 2020-05-07 | PennyPay, Inc. | Systems and methods for a micropayment solution for media applications |
| WO2020107033A1 (en)* | 2018-11-25 | 2020-05-28 | Tunnel International Inc. | Methods, systems, and devices for on-chain stable transaction in decentralized cryptocurrencies |
| US20200175503A1 (en) | 2018-11-29 | 2020-06-04 | Paypal, Inc. | Resource-based distributed public ledger system |
| SG11201906838QA (en) | 2018-12-19 | 2019-08-27 | Alibaba Group Holding Ltd | Data isolation in a blockchain network |
| WO2020132330A1 (en)* | 2018-12-20 | 2020-06-25 | Lukka, Inc. | Gain and loss computation for cryptocurrency transactions |
| US12014360B2 (en) | 2018-12-20 | 2024-06-18 | Lukka, Inc. | Gain and loss computation for cryptocurrency transactions |
| US11588643B2 (en)* | 2018-12-27 | 2023-02-21 | Paypal, Inc. | Blockchain management system |
| CN110032882A (en) | 2018-12-29 | 2019-07-19 | 阿里巴巴集团控股有限公司 | Card method and apparatus are deposited based on block chain |
| CN109741183A (en)* | 2018-12-29 | 2019-05-10 | 北京金山安全软件有限公司 | Information acquisition method and device |
| EP3903267A4 (en)* | 2018-12-30 | 2022-08-31 | Tunnel International Inc. | Methods, devices, and systems for secure payments |
| US11461565B2 (en)* | 2019-01-03 | 2022-10-04 | Blockchain Innovation, Llc | Apparatus and methods for remote controlled cold storage of digital assets using near field communication tags |
| CN109801068A (en)* | 2019-01-04 | 2019-05-24 | 深圳银链科技有限公司 | Digital cash management system, method, cold wallet and the hot money packet of wallet is isolated |
| US11329826B2 (en)* | 2019-01-09 | 2022-05-10 | Datchat, Inc. | Blockchain-based communication systems and methods |
| CN109547218B (en)* | 2019-01-18 | 2021-10-15 | 北京工业大学 | A Consortium Chain Node Key Distribution and Backup System Based on Improved BIP Protocol |
| US11270541B2 (en)* | 2019-03-04 | 2022-03-08 | Mastercard International Incorporated | Method and system for secure product delivery using cryptography |
| US11038878B2 (en)* | 2019-03-14 | 2021-06-15 | Hector Hoyos | Computer system security using a biometric authentication gateway for user service access with a divided and distributed private encryption key |
| JP6650543B1 (en)* | 2019-03-25 | 2020-02-19 | さくら情報システム株式会社 | Information processing apparatus, method and program |
| EP3953834A4 (en) | 2019-04-12 | 2023-01-04 | Symbiont.io, Inc. | SYSTEMS, DEVICES AND METHODS ASSOCIATED WITH DLT-BASED DATA MANAGEMENT PLATFORMS AND DATA PRODUCTS |
| KR20200124369A (en)* | 2019-04-23 | 2020-11-03 | 주식회사 커먼컴퓨터 | Method and system for providing reward by using a user interface on a display of an electronic device |
| CA3139776A1 (en) | 2019-05-15 | 2020-11-19 | Upstream Data Inc. | Portable blockchain mining system and methods of use |
| CN110189124A (en)* | 2019-05-24 | 2019-08-30 | 杭州复杂美科技有限公司 | Anti-attack method, equipment and storage medium |
| US11475439B2 (en)* | 2019-06-03 | 2022-10-18 | Visa International Service Association | System, method, and apparatus for securely transmitting data via a third-party webpage |
| CN110351276B (en)* | 2019-07-12 | 2021-11-23 | 全链通有限公司 | Data processing method, device and computer readable storage medium |
| US12008549B2 (en) | 2019-07-22 | 2024-06-11 | Visa International Service Association | Federated custodian |
| US11296887B2 (en)* | 2019-08-02 | 2022-04-05 | Unisys Corporation | Blockchain mechanism for safety-critical systems |
| KR20210023601A (en) | 2019-08-23 | 2021-03-04 | 삼성전자주식회사 | Electronic device for providing blockchain account information and method of operating the same |
| GB2587202A (en)* | 2019-09-17 | 2021-03-24 | Nchain Holdings Ltd | Allocation of a digital asset using blockchain transactions |
| US20210110382A1 (en)* | 2019-10-13 | 2021-04-15 | MobileCoin | System and method for providing auxiliary curve cold storage |
| EP3812991A1 (en) | 2019-10-21 | 2021-04-28 | Joachim Walser | Cryptocurrency cash gateway |
| US11341236B2 (en) | 2019-11-22 | 2022-05-24 | Pure Storage, Inc. | Traffic-based detection of a security threat to a storage system |
| US11625481B2 (en) | 2019-11-22 | 2023-04-11 | Pure Storage, Inc. | Selective throttling of operations potentially related to a security threat to a storage system |
| US11755751B2 (en) | 2019-11-22 | 2023-09-12 | Pure Storage, Inc. | Modify access restrictions in response to a possible attack against data stored by a storage system |
| US11500788B2 (en) | 2019-11-22 | 2022-11-15 | Pure Storage, Inc. | Logical address based authorization of operations with respect to a storage system |
| US11657155B2 (en) | 2019-11-22 | 2023-05-23 | Pure Storage, Inc | Snapshot delta metric based determination of a possible ransomware attack against data maintained by a storage system |
| US12067118B2 (en) | 2019-11-22 | 2024-08-20 | Pure Storage, Inc. | Detection of writing to a non-header portion of a file as an indicator of a possible ransomware attack against a storage system |
| US12204657B2 (en) | 2019-11-22 | 2025-01-21 | Pure Storage, Inc. | Similar block detection-based detection of a ransomware attack |
| US12248566B2 (en)* | 2019-11-22 | 2025-03-11 | Pure Storage, Inc. | Snapshot deletion pattern-based determination of ransomware attack against data maintained by a storage system |
| US12153670B2 (en) | 2019-11-22 | 2024-11-26 | Pure Storage, Inc. | Host-driven threat detection-based protection of storage elements within a storage system |
| US11520907B1 (en)* | 2019-11-22 | 2022-12-06 | Pure Storage, Inc. | Storage system snapshot retention based on encrypted data |
| US11675898B2 (en) | 2019-11-22 | 2023-06-13 | Pure Storage, Inc. | Recovery dataset management for security threat monitoring |
| US12079502B2 (en) | 2019-11-22 | 2024-09-03 | Pure Storage, Inc. | Storage element attribute-based determination of a data protection policy for use within a storage system |
| US12411962B2 (en) | 2019-11-22 | 2025-09-09 | Pure Storage, Inc. | Managed run-time environment-based detection of a ransomware attack |
| US12050683B2 (en) | 2019-11-22 | 2024-07-30 | Pure Storage, Inc. | Selective control of a data synchronization setting of a storage system based on a possible ransomware attack against the storage system |
| US11941116B2 (en) | 2019-11-22 | 2024-03-26 | Pure Storage, Inc. | Ransomware-based data protection parameter modification |
| US11645162B2 (en) | 2019-11-22 | 2023-05-09 | Pure Storage, Inc. | Recovery point determination for data restoration in a storage system |
| US11615185B2 (en) | 2019-11-22 | 2023-03-28 | Pure Storage, Inc. | Multi-layer security threat detection for a storage system |
| US20210382992A1 (en)* | 2019-11-22 | 2021-12-09 | Pure Storage, Inc. | Remote Analysis of Potentially Corrupt Data Written to a Storage System |
| US11687418B2 (en) | 2019-11-22 | 2023-06-27 | Pure Storage, Inc. | Automatic generation of recovery plans specific to individual storage elements |
| US11720692B2 (en) | 2019-11-22 | 2023-08-08 | Pure Storage, Inc. | Hardware token based management of recovery datasets for a storage system |
| US12079333B2 (en) | 2019-11-22 | 2024-09-03 | Pure Storage, Inc. | Independent security threat detection and remediation by storage systems in a synchronous replication arrangement |
| US11720714B2 (en) | 2019-11-22 | 2023-08-08 | Pure Storage, Inc. | Inter-I/O relationship based detection of a security threat to a storage system |
| US12079356B2 (en) | 2019-11-22 | 2024-09-03 | Pure Storage, Inc. | Measurement interval anomaly detection-based generation of snapshots |
| US12050689B2 (en) | 2019-11-22 | 2024-07-30 | Pure Storage, Inc. | Host anomaly-based generation of snapshots |
| US11651075B2 (en) | 2019-11-22 | 2023-05-16 | Pure Storage, Inc. | Extensible attack monitoring by a storage system |
| US11784799B2 (en) | 2019-12-16 | 2023-10-10 | The Toronto-Dominion Bank | Secure distribution and management of cryptographic keys within a computing environment using distributed ledgers |
| US11343075B2 (en) | 2020-01-17 | 2022-05-24 | Inveniam Capital Partners, Inc. | RAM hashing in blockchain environments |
| US12099997B1 (en) | 2020-01-31 | 2024-09-24 | Steven Mark Hoffberg | Tokenized fungible liabilities |
| CA3076653A1 (en) | 2020-03-21 | 2021-09-21 | Upstream Data Inc. | Portable blockchain mining systems and methods of use |
| US20210357918A1 (en)* | 2020-05-18 | 2021-11-18 | RocketFuel Blockchain, Inc. | Commerce systems having integrated delivery feature |
| US11715149B2 (en)* | 2020-05-18 | 2023-08-01 | RocketFuel Blockchain, Inc. | Commerce systems having integrated electronic delivery features |
| WO2021257826A1 (en)* | 2020-06-17 | 2021-12-23 | Coinbase, Inc. | Systems and methods for converting cryptocurrency |
| US11587071B2 (en)* | 2020-06-24 | 2023-02-21 | Mastercard Asia/Pacific Pte. Ltd. | Method and system for merchant acceptance of cryptocurrency via payment rails |
| GB2598301A (en)* | 2020-08-21 | 2022-03-02 | Nchain Holdings Ltd | Alert account |
| USD946022S1 (en)* | 2020-10-19 | 2022-03-15 | Splunk Inc. | Display screen or portion thereof having a graphical user interface for a work table-based presentation of information |
| WO2022125851A1 (en)* | 2020-12-11 | 2022-06-16 | Seaver Jesse Thomas | Automated blockchain address creation and transfers by uniform resource locator generation and execution |
| US12033140B2 (en) | 2020-12-16 | 2024-07-09 | Bakkt Marketplace, LLC | Efficient, accurate, and secure processing of conversions between digital assets |
| US11880826B2 (en) | 2020-12-16 | 2024-01-23 | Bakkt Marketplace, LLC | Efficient, accurate, and secure processing of digital asset conversion to fiat currency |
| US11961136B2 (en) | 2020-12-16 | 2024-04-16 | Bakkt Marketplace, LLC | Efficient, accurate, and secure transfers of internally-custodied digital assets |
| US20220237597A1 (en)* | 2021-01-22 | 2022-07-28 | Bakkt Marketplace, LLC | Alternative digital asset conversion choices |
| AU2022223747A1 (en)* | 2021-02-16 | 2023-09-07 | Novatti Group Limited | Secure and compliant multi-cryptocurrency payment gateway |
| US20220300951A1 (en)* | 2021-03-16 | 2022-09-22 | Premashanth Kumalarasan | Cryptocurrency Reward System |
| US12008526B2 (en) | 2021-03-26 | 2024-06-11 | Inveniam Capital Partners, Inc. | Computer system and method for programmatic collateralization services |
| US11170130B1 (en) | 2021-04-08 | 2021-11-09 | Aster Key, LLC | Apparatus, systems and methods for storing user profile data on a distributed database for anonymous verification |
| USD1074691S1 (en)* | 2021-05-29 | 2025-05-13 | Adp, Inc. | Display screen with a graphical user interface |
| US12007972B2 (en) | 2021-06-19 | 2024-06-11 | Inveniam Capital Partners, Inc. | Systems and methods for processing blockchain transactions |
| US12137179B2 (en) | 2021-06-19 | 2024-11-05 | Inveniam Capital Partners, Inc. | Systems and methods for processing blockchain transactions |
| CN113378095B (en)* | 2021-06-30 | 2023-08-04 | 抖音视界有限公司 | Dynamic loading method, device, equipment and storage medium of signature algorithm |
| CO2021008982A1 (en)* | 2021-07-07 | 2023-01-16 | Banco Davivienda S A | Data transfer method over a blockchain network for p2p digital transactions |
| US12355771B2 (en) | 2021-07-29 | 2025-07-08 | Raytheon Company | Auditable and tamper-resistant remote zero trust access |
| US11924350B2 (en) | 2021-07-29 | 2024-03-05 | Digital Asset (Switzerland) GmbH | Cryptographically enforced partial blinding for distributed system |
| US12033147B2 (en) | 2021-09-20 | 2024-07-09 | Bank Of America Corporation | System for containerization of non-fungible tokens |
| US20230101940A1 (en)* | 2021-09-29 | 2023-03-30 | Flexa Network Inc. | Reoccurring digital asset-based interaction |
| US20230098324A1 (en)* | 2021-09-29 | 2023-03-30 | Flexa Network Inc. | Key code share interaction mode of a digital asset-based interaction system |
| US12093934B2 (en) | 2021-10-22 | 2024-09-17 | Bank Of America Corporation | System for implementing layered authorization platform using non-fungible tokens |
| US20230177500A1 (en)* | 2021-12-07 | 2023-06-08 | Whistle Systems, Inc. | Method of conducting financial transactions |
| US12248936B2 (en)* | 2021-12-08 | 2025-03-11 | Paypal, Inc. | User activity detection for locking cryptocurrency conversions |
| US11948144B2 (en)* | 2022-02-07 | 2024-04-02 | Capital One Services, Llc | Knowledge-based authentication for asset wallets |
| US20230351432A1 (en)* | 2022-04-27 | 2023-11-02 | Hongwei Zhu | Systems And Methods Of Facilitating Merchant Coupon Distribution On A Blockchain Network |
| US20230367662A1 (en)* | 2022-05-12 | 2023-11-16 | Google Llc | Connecting an application with a digital asset holder to process a blockchain transaction |
| US12423678B2 (en) | 2022-05-20 | 2025-09-23 | Mastercard International Incorporated | Method and system for authorization for cryptocurrency on distributed ledger |
| US11966375B2 (en) | 2022-05-25 | 2024-04-23 | Hop.dev, Inc. | Enabling communication between multiple databases having disparate indices |
| CN115098837B (en)* | 2022-06-21 | 2024-05-24 | 马上消费金融股份有限公司 | Data processing method and device |
| US20240013197A1 (en)* | 2022-07-07 | 2024-01-11 | Bank Of America Corporation | System for obfuscation of network identity to prevent data exfiltration |
| WO2024186642A1 (en)* | 2023-03-03 | 2024-09-12 | Concentrix Cvg Customer Management Delaware Llc | Digital wallet management |
| WO2025056986A1 (en) | 2023-09-12 | 2025-03-20 | Wgc (Uk) Limited | Method and system to digitize the value of a commodity |
| WO2025106492A1 (en)* | 2023-11-15 | 2025-05-22 | Propitious Technical Services | Mobile applications for identification |
| JP7717881B1 (en)* | 2024-03-19 | 2025-08-04 | 佑太 山根 | Information processing system and information processing method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20010050990A1 (en)* | 1997-02-19 | 2001-12-13 | Frank Wells Sudia | Method for initiating a stream-oriented encrypted communication |
| US6959394B1 (en)* | 2000-09-29 | 2005-10-25 | Intel Corporation | Splitting knowledge of a password |
| US20150033301A1 (en)* | 2012-03-02 | 2015-01-29 | Alcatel Lucent | Decentralized electronic transfer system |
Family Cites Families (122)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US2634738A (en) | 1948-12-27 | 1953-04-14 | Charles E Fuller | Bearing washer |
| JP3141080B2 (en) | 1994-06-22 | 2001-03-05 | ケイディディ株式会社 | Semiconductor functional element |
| US5884274A (en)* | 1996-11-15 | 1999-03-16 | Walker Asset Management Limited Partnership | System and method for generating and executing insurance policies for foreign exchange losses |
| US6125186A (en)* | 1996-11-28 | 2000-09-26 | Fujitsu Limited | Encryption communication system using an agent and a storage medium for storing that agent |
| US7290288B2 (en) | 1997-06-11 | 2007-10-30 | Prism Technologies, L.L.C. | Method and system for controlling access, by an authentication server, to protected computer resources provided via an internet protocol network |
| US7644037B1 (en) | 1999-08-16 | 2010-01-05 | Vladimir Ostrovsky | Method and system for transferring electronic funds |
| US6873974B1 (en)* | 1999-08-17 | 2005-03-29 | Citibank, N.A. | System and method for use of distributed electronic wallets |
| AU2965801A (en) | 2000-01-21 | 2001-07-31 | Hoffman Group Ltd., The | Three-tiered portal |
| WO2001077868A2 (en) | 2000-04-05 | 2001-10-18 | Ruesch International, Inc. | System, method and apparatus for international financial transactions |
| WO2001084906A2 (en) | 2000-05-11 | 2001-11-15 | Virtual Assets Incorporated | Advanced asset management systems |
| WO2001090861A2 (en) | 2000-05-25 | 2001-11-29 | Echarge Corporation | Secure transaction protocol |
| US6952683B1 (en) | 2000-10-11 | 2005-10-04 | Ubs Ag | System and method for hedging against foreign exchange risk associated with securities transactions |
| US20020116611A1 (en) | 2000-10-31 | 2002-08-22 | Cornell Research Foundation, Inc. | Secure distributed on-line certification authority |
| US7187772B2 (en) | 2001-08-31 | 2007-03-06 | Hewlett-Packard Development Company, L.P. | Anonymous transactions based on distributed processing |
| US20130282580A1 (en) | 2003-02-28 | 2013-10-24 | Payment Pathways, Inc. | SYSTEMS AND METHODS FOR EXTENDING IDENTITY ATTRIBUTES AND AUTHENTICATION FACTORS IN AN ePAYMENT ADDRESS REGISTRY |
| GB2400699B (en) | 2003-04-17 | 2006-07-05 | Hewlett Packard Development Co | Security data provision method and apparatus and data recovery method and system |
| US7742985B1 (en)* | 2003-06-26 | 2010-06-22 | Paypal Inc. | Multicurrency exchanges between participants of a network-based transaction facility |
| US8139770B2 (en) | 2003-12-23 | 2012-03-20 | Wells Fargo Bank, N.A. | Cryptographic key backup and escrow system |
| US20140019352A1 (en) | 2011-02-22 | 2014-01-16 | Visa International Service Association | Multi-purpose virtual card transaction apparatuses, methods and systems |
| US8121944B2 (en) | 2004-06-24 | 2012-02-21 | Jpmorgan Chase Bank, N.A. | Method and system for facilitating network transaction processing |
| US7970823B2 (en) | 2004-09-02 | 2011-06-28 | Broadway Technology, Llc | System for sharing data objects among applications |
| JP2007109002A (en)* | 2005-10-13 | 2007-04-26 | Snk Playmore Corp | Electronic money monitoring program and electronic money monitoring system |
| US8055575B2 (en) | 2005-10-14 | 2011-11-08 | Financial Intergroup Holdings, Ltd. | Central counterparty for data management |
| US8989390B2 (en) | 2005-12-12 | 2015-03-24 | Qualcomm Incorporated | Certify and split system and method for replacing cryptographic keys |
| US7689500B2 (en) | 2006-10-02 | 2010-03-30 | Liffe Administration And Management | System and method for facilitating trading in an electronic market |
| EP2122900A4 (en) | 2007-01-22 | 2014-07-23 | Spyrus Inc | Portable data encryption device with configurable security functionality and method for file encryption |
| ZA200905539B (en) | 2007-02-08 | 2010-10-27 | Xg Technology Inc | Heterogeneous mac protocol for forwarding VOIP traffic on wireless networks |
| WO2008099682A1 (en) | 2007-02-16 | 2008-08-21 | Panasonic Corporation | Shared information distributing device, holding device, certificate authority device, and system |
| US8457317B2 (en) | 2007-05-07 | 2013-06-04 | Hitachi Data Systems Corporation | Method for data privacy in a fixed content distributed data storage |
| US10231077B2 (en) | 2007-07-03 | 2019-03-12 | Eingot Llc | Records access and management |
| US7689550B2 (en) | 2007-07-31 | 2010-03-30 | Oracle International Corporation | Adaptive cursor sharing |
| US7640212B2 (en)* | 2007-08-28 | 2009-12-29 | The Western Union Company | Methods and systems for executing a plurality of money transfers having a fluctuating parameter |
| US8839386B2 (en) | 2007-12-03 | 2014-09-16 | At&T Intellectual Property I, L.P. | Method and apparatus for providing authentication |
| US8117648B2 (en) | 2008-02-08 | 2012-02-14 | Intersections, Inc. | Secure information storage and delivery system and method |
| CA2946778A1 (en) | 2008-02-22 | 2009-08-27 | Security First Corp. | Systems and methods for secure workgroup management and communication |
| US8600896B2 (en) | 2008-03-28 | 2013-12-03 | Panasonic Corporation | Software updating apparatus, software updating system, invalidation method, and invalidation program |
| US8855318B1 (en) | 2008-04-02 | 2014-10-07 | Cisco Technology, Inc. | Master key generation and distribution for storage area network devices |
| US8675877B2 (en) | 2008-08-29 | 2014-03-18 | Red Hat, Inc. | Sharing a secret via linear interpolation |
| RU2012118388A (en) | 2009-10-09 | 2013-11-20 | Инстинет Глоубал Пропертиз Инк. | METHOD AND SYSTEM OF ASSISTANCE TO TRADE IN INTERNATIONAL SECURITIES |
| US8280788B2 (en) | 2009-10-29 | 2012-10-02 | Visa International Service Association | Peer-to-peer and group financial management systems and methods |
| CN106230872A (en) | 2009-11-25 | 2016-12-14 | 安全第公司 | To moving medial according to the system and method protected |
| US8458088B2 (en) | 2010-04-08 | 2013-06-04 | The Western Union Company | Money transfer smart phone methods and systems |
| US8666860B2 (en)* | 2010-07-06 | 2014-03-04 | International Monetary Specialists | Method and system for currency exchange by point of conversion |
| WO2012054785A1 (en) | 2010-10-20 | 2012-04-26 | Playspan Inc. | Latency payment settlement apparatuses, methods and systems |
| US9596237B2 (en) | 2010-12-14 | 2017-03-14 | Salt Technology, Inc. | System and method for initiating transactions on a mobile device |
| US9691055B2 (en)* | 2010-12-17 | 2017-06-27 | Google Inc. | Digital wallet |
| US9191813B2 (en)* | 2010-12-30 | 2015-11-17 | Mozido Corfire—Korea, Ltd. | System and method for managing OTA provisioning applications through use of profiles and data preparation |
| US20130218657A1 (en)* | 2011-01-11 | 2013-08-22 | Diane Salmon | Universal value exchange apparatuses, methods and systems |
| JP5682527B2 (en) | 2011-03-28 | 2015-03-11 | ソニー株式会社 | Cryptographic processing apparatus, cryptographic processing method, and program |
| US9569771B2 (en)* | 2011-04-29 | 2017-02-14 | Stephen Lesavich | Method and system for storage and retrieval of blockchain blocks using galois fields |
| US9355393B2 (en) | 2011-08-18 | 2016-05-31 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
| US8917872B2 (en) | 2011-07-06 | 2014-12-23 | Hewlett-Packard Development Company, L.P. | Encryption key storage with key fragment stores |
| US10318941B2 (en)* | 2011-12-13 | 2019-06-11 | Visa International Service Association | Payment platform interface widget generation apparatuses, methods and systems |
| US8449378B2 (en)* | 2011-09-13 | 2013-05-28 | Igt | Gaming system, gaming device and method for utilizing bitcoins |
| US20130166455A1 (en)* | 2011-12-23 | 2013-06-27 | Douglas Feigelson | Creating and using digital currency |
| US10621809B2 (en) | 2012-01-19 | 2020-04-14 | Christopher M. Smolen | Digital currency enabled vending machine |
| US9065637B2 (en) | 2012-01-25 | 2015-06-23 | CertiVox Ltd. | System and method for securing private keys issued from distributed private key generator (D-PKG) nodes |
| US8788819B2 (en)* | 2012-04-27 | 2014-07-22 | Yahoo! Inc. | System and method for a cloud-based electronic communication vault |
| US9710805B2 (en)* | 2012-06-18 | 2017-07-18 | Paypal, Inc. | Prepaid wallet for merchants |
| US20140025473A1 (en) | 2012-07-19 | 2014-01-23 | RocketHub Inc. | Crowdfunding based on actions |
| GB2505211B (en) | 2012-08-22 | 2014-10-29 | Vodafone Ip Licensing Ltd | Communications device authentication |
| US9424432B2 (en) | 2012-09-20 | 2016-08-23 | Nasdaq, Inc. | Systems and methods for secure and persistent retention of sensitive information |
| WO2014056185A1 (en) | 2012-10-12 | 2014-04-17 | Empire Technology Development Llc | Notarization based on currency transactions |
| US10102510B2 (en)* | 2012-11-28 | 2018-10-16 | Hoverkey Ltd. | Method and system of conducting a cryptocurrency payment via a mobile device using a contactless token to store and protect a user's secret key |
| US20140156512A1 (en) | 2012-12-04 | 2014-06-05 | Pangea Universal Holdings, Inc. | Providing money transfer using a money transfer platform |
| US10504163B2 (en) | 2012-12-14 | 2019-12-10 | Mastercard International Incorporated | System for payment, data management, and interchanges for use with global shopping cart |
| US20140172630A1 (en) | 2012-12-14 | 2014-06-19 | Mastercard International Incorporated | Social media interface for use with a global shopping cart |
| US10210341B2 (en) | 2013-02-12 | 2019-02-19 | Amazon Technologies, Inc. | Delayed data access |
| US8961300B2 (en) | 2013-03-13 | 2015-02-24 | Game Play Network, Inc. | System and method of providing wagering opportunities based on promotional content |
| US9495679B2 (en) | 2013-03-15 | 2016-11-15 | @Pay Ip Holdings Llc | Automated application programming interface (API) system and method |
| US9536232B2 (en) | 2013-03-15 | 2017-01-03 | Square, Inc. | Transferring money using email |
| US8606703B1 (en) | 2013-03-15 | 2013-12-10 | Square, Inc. | Method for transferring money using email |
| US10339506B2 (en) | 2013-03-25 | 2019-07-02 | Swoop Ip Holdings Llc | Method and system for a secure registration |
| US20140304171A1 (en) | 2013-04-03 | 2014-10-09 | Kudoo BV | Method and system to facilitate social ecommerce |
| US9071429B1 (en) | 2013-04-29 | 2015-06-30 | Amazon Technologies, Inc. | Revocable shredding of security credentials |
| US9495668B1 (en) | 2013-05-10 | 2016-11-15 | EMC IP Holding Company LLC | Computing solutions to a problem involving inversion of a one-way function |
| WO2014190323A1 (en) | 2013-05-24 | 2014-11-27 | Degaugue Fabien Ghislain | System and method for facilitating transactions as conversations between participants |
| US20160085955A1 (en) | 2013-06-10 | 2016-03-24 | Doosra, Inc. | Secure Storing and Offline Transferring of Digitally Transferable Assets |
| US9898782B1 (en)* | 2013-06-28 | 2018-02-20 | Winklevoss Ip, Llc | Systems, methods, and program products for operating exchange traded products holding digital math-based assets |
| US10269009B1 (en) | 2013-06-28 | 2019-04-23 | Winklevoss Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
| US10068228B1 (en) | 2013-06-28 | 2018-09-04 | Winklevoss Ip, Llc | Systems and methods for storing digital math-based assets using a secure portal |
| US10332205B1 (en) | 2013-07-16 | 2019-06-25 | Mark Russell | Bitcoin kiosk/ATM device and system and method of using the same |
| US9245284B2 (en) | 2013-07-31 | 2016-01-26 | Ryan Hardin | Application of dynamic tokens |
| US20150050987A1 (en) | 2013-08-13 | 2015-02-19 | Igt | System and method for determining current or future users of a virtual currency |
| US20160203572A1 (en) | 2013-08-21 | 2016-07-14 | Ascribe Gmbh | Method to securely establish, affirm, and transfer ownership of artworks |
| US20150120569A1 (en) | 2013-10-31 | 2015-04-30 | Bitgo, Inc. | Virtual currency address security |
| US20150170112A1 (en) | 2013-10-04 | 2015-06-18 | Erly Dalvo DeCastro | Systems and methods for providing multi-currency platforms comprising means for exchanging and interconverting tangible and virtual currencies in various transactions, banking operations, and wealth management scenarios |
| US20150127495A1 (en) | 2013-11-01 | 2015-05-07 | Cyril Houri | Method, system and computer program for monetizing digital or virtual currency |
| US10127528B2 (en) | 2013-12-20 | 2018-11-13 | Movocash, Inc. | Financial services ecosystem |
| WO2015117029A1 (en) | 2014-01-30 | 2015-08-06 | Edwards Kingsley | Gaming platform system and method for interactive participation by players with successes and losses transacted using bitcoin |
| US20150220928A1 (en) | 2014-01-31 | 2015-08-06 | Robert Allen | Platform for the purchase and sale of digital currency |
| US20150228004A1 (en) | 2014-02-07 | 2015-08-13 | Kristin Kaye Bednarek | Smart Device Apps and Incentives For Encouraging The Creation and Sharing Electronic Lists To Imrpove Targeted Marketing While Preserving User Anonymity |
| US20150227897A1 (en) | 2014-02-11 | 2015-08-13 | Anthony Loera | Method of Making, Securing, and Using a Cryptocurrency Wallet |
| US20150262173A1 (en) | 2014-03-17 | 2015-09-17 | Bank Of America Corporation | System and Method for Wire Transfers Using Cryptocurrency |
| WO2015142765A1 (en) | 2014-03-17 | 2015-09-24 | Coinbase, Inc | Bitcoin host computer system |
| US9672499B2 (en)* | 2014-04-02 | 2017-06-06 | Modernity Financial Holdings, Ltd. | Data analytic and security mechanism for implementing a hot wallet service |
| US9135787B1 (en) | 2014-04-04 | 2015-09-15 | Mark Russell | Bitcoin kiosk/ATM device and system integrating enrollment protocol and method of using the same |
| US11270298B2 (en) | 2014-04-14 | 2022-03-08 | 21, Inc. | Digital currency mining circuitry |
| US20150302401A1 (en) | 2014-04-18 | 2015-10-22 | Ebay Inc. | Distributed crypto currency unauthorized transfer monitoring system |
| US9830593B2 (en) | 2014-04-26 | 2017-11-28 | Ss8 Networks, Inc. | Cryptographic currency user directory data and enhanced peer-verification ledger synthesis through multi-modal cryptographic key-address mapping |
| US20150324789A1 (en)* | 2014-05-06 | 2015-11-12 | Case Wallet, Inc. | Cryptocurrency Virtual Wallet System and Method |
| US11164164B2 (en) | 2014-05-15 | 2021-11-02 | Uphold Global Foundation | System and method for converting cryptocurrency to virtual assets whose value is substantiated by a reserve of assets |
| US10255600B2 (en) | 2014-06-16 | 2019-04-09 | Bank Of America Corporation | Cryptocurrency offline vault storage system |
| US9836790B2 (en)* | 2014-06-16 | 2017-12-05 | Bank Of America Corporation | Cryptocurrency transformation system |
| US20160005033A1 (en)* | 2014-07-03 | 2016-01-07 | 8Exchange, LLC | Systems and methods for a currency exchange platform |
| WO2016051591A1 (en) | 2014-10-03 | 2016-04-07 | 株式会社 東芝 | Re-encryption key generation device, re-encryption device, encryption device, decryption device and program |
| US9639687B2 (en) | 2014-11-18 | 2017-05-02 | Cloudfare, Inc. | Multiply-encrypting data requiring multiple keys for decryption |
| US10256983B1 (en) | 2015-03-25 | 2019-04-09 | National Technology & Engineering Solutions Of Sandia, Llc | Circuit that includes a physically unclonable function |
| US10778439B2 (en) | 2015-07-14 | 2020-09-15 | Fmr Llc | Seed splitting and firmware extension for secure cryptocurrency key backup, restore, and transaction signing platform apparatuses, methods and systems |
| US20180191503A1 (en) | 2015-07-14 | 2018-07-05 | Fmr Llc | Asynchronous Crypto Asset Transfer and Social Aggregating, Fractionally Efficient Transfer Guidance, Conditional Triggered Transaction, Datastructures, Apparatuses, Methods and Systems |
| US11329980B2 (en) | 2015-08-21 | 2022-05-10 | Veridium Ip Limited | System and method for biometric protocol standards |
| US10325107B2 (en) | 2015-09-23 | 2019-06-18 | Salesforce.Com, Inc. | Systems and methods for securing data using encryption |
| US10180912B1 (en) | 2015-12-17 | 2019-01-15 | Amazon Technologies, Inc. | Techniques and systems for data segregation in redundancy coded data storage systems |
| US10469309B1 (en) | 2016-04-28 | 2019-11-05 | Servicenow, Inc. | Management of computing system alerts |
| EP3293653A1 (en) | 2016-09-09 | 2018-03-14 | Nagravision S.A. | A system for decrypting and rendering content |
| US10832247B2 (en) | 2016-09-15 | 2020-11-10 | American Express Travel Related Services Company, Inc. | Systems and methods for blockchain based payment networks |
| US10979234B2 (en) | 2017-02-24 | 2021-04-13 | Sera4 Ltd. | Secure locking of physical resources using asymmetric cryptography |
| US10586057B2 (en) | 2017-11-16 | 2020-03-10 | Intuit Inc. | Processing data queries in a logically sharded data store |
| US11431494B2 (en) | 2018-03-15 | 2022-08-30 | Atakama LLC | Passwordless security system for data-at-rest |
| US10733291B1 (en) | 2018-06-11 | 2020-08-04 | Square, Inc. | Bi-directional communication protocol based device security |
| WO2020049357A1 (en) | 2018-09-06 | 2020-03-12 | Bank Of Montreal | Systems and methods for encryption of data on a blockchain |
| US12248936B2 (en)* | 2021-12-08 | 2025-03-11 | Paypal, Inc. | User activity detection for locking cryptocurrency conversions |
- 2015
- 2015-03-16WOPCT/US2015/020840patent/WO2015142765A1/enactiveApplication Filing
- 2015-03-17USUS14/660,331patent/US20150262171A1/ennot_activeAbandoned
- 2015-03-17USUS14/660,427patent/US10891600B2/enactiveActive
- 2015-03-17USUS14/660,307patent/US20150262137A1/ennot_activeAbandoned
- 2015-03-17USUS14/660,432patent/US9436935B2/enactiveActive
- 2015-03-17USUS14/660,422patent/US20150262141A1/ennot_activeAbandoned
- 2015-03-17USUS14/660,296patent/US10510053B2/enactiveActive
- 2015-03-17USUS14/660,440patent/US10229396B2/enactiveActive
- 2015-03-17USUS14/660,014patent/US10614430B2/enactiveActive
- 2015-03-17USUS14/660,418patent/US10755241B2/enactiveActive
- 2019
- 2019-01-09USUS16/243,688patent/US10878389B2/enactiveActive
- 2020
- 2020-11-19USUS16/952,539patent/US11741438B2/enactiveActive
- 2023
- 2023-07-11USUS18/350,731patent/US20230368158A1/enactivePending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20010050990A1 (en)* | 1997-02-19 | 2001-12-13 | Frank Wells Sudia | Method for initiating a stream-oriented encrypted communication |
| US6959394B1 (en)* | 2000-09-29 | 2005-10-25 | Intel Corporation | Splitting knowledge of a password |
| US20150033301A1 (en)* | 2012-03-02 | 2015-01-29 | Alcatel Lucent | Decentralized electronic transfer system |
Non-Patent Citations (4)
| Title |
|---|
| Bitcoin Explained, https://chrispacia.wordpress.com/2013/09/29/bitcoin-explained-like-youre-five-part-4-securing-your-wallet/ Attached as pdf.* |
| blockchainCreate (http://blockchain.info:80/wallet/faq, dated 1/9/2012, attached as pdf)* |
| ComputerArch (http://www.math.uaa.alaska.edu/~afkjm/cs101/handouts/ComputerArch.pdf attached as pdf, dated 9/10/2009)* |
| NIST (Archived NIST Technical Series Publication, dated July 2012, "sp800-57_part1_rev3_general.pdf", attached as pdf.)* |
Cited By (152)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11928732B1 (en) | 2013-06-28 | 2024-03-12 | Gemini Ip, Llc | Computer-generated graphical user interface |
| US11615404B1 (en) | 2013-06-28 | 2023-03-28 | Gemini Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
| US9892460B1 (en) | 2013-06-28 | 2018-02-13 | Winklevoss Ip, Llc | Systems, methods, and program products for operating exchange traded products holding digital math-based assets |
| US9898782B1 (en) | 2013-06-28 | 2018-02-20 | Winklevoss Ip, Llc | Systems, methods, and program products for operating exchange traded products holding digital math-based assets |
| US9965805B1 (en) | 2013-06-28 | 2018-05-08 | Winklevoss Ip, Llc | Systems, methods, and program products for operating exchange traded products holding digital math-based assets |
| US9965804B1 (en) | 2013-06-28 | 2018-05-08 | Winklevoss Ip, Llc | Systems, methods, and program products for operating exchange traded products holding digital math-based assets |
| US10002389B1 (en) | 2013-06-28 | 2018-06-19 | Winklevoss Ip, Llc | Systems, methods, and program products for an application programming interface generating a blended digital math-based assets index |
| US11164251B1 (en) | 2013-06-28 | 2021-11-02 | Winklevoss Ip, Llc | Computer-generated graphical user interface |
| US11087313B1 (en) | 2013-06-28 | 2021-08-10 | Winklevoss Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
| US11017381B1 (en) | 2013-06-28 | 2021-05-25 | Winklevoss Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
| US10255635B1 (en) | 2013-06-28 | 2019-04-09 | Winklevoss Ip, Llc | Systems, methods, and program products for an application programming interface generating a blended digital math-based assets index |
| US10269009B1 (en) | 2013-06-28 | 2019-04-23 | Winklevoss Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
| US10325257B1 (en) | 2013-06-28 | 2019-06-18 | Winklevoss Ip, Llc | Systems and methods for storing digital math-based assets using a secure portal |
| US10650376B1 (en) | 2013-06-28 | 2020-05-12 | Winklevoss Ip, Llc | Systems and methods for storing digital math-based assets using a secure portal |
| US11282139B1 (en) | 2013-06-28 | 2022-03-22 | Gemini Ip, Llc | Systems, methods, and program products for verifying digital assets held in a custodial digital asset wallet |
| US10929929B1 (en) | 2013-06-28 | 2021-02-23 | Winklevoss Ip, Llc | Systems for purchasing shares in an entity holding digital math-based assets |
| US10068228B1 (en) | 2013-06-28 | 2018-09-04 | Winklevoss Ip, Llc | Systems and methods for storing digital math-based assets using a secure portal |
| US11995720B1 (en) | 2013-06-28 | 2024-05-28 | Gemini Ip, Llc | Systems for purchasing shares in an entity holding digital math-based assets |
| US11783417B1 (en) | 2013-06-28 | 2023-10-10 | Gemini Ip, Llc | Systems for redeeming shares in an entity holding digital math-based assets |
| US11423482B1 (en) | 2013-06-28 | 2022-08-23 | Gemini Ip, Llc | Systems, methods, and program products for an application programming interface generating a blended digital math-based assets index |
| US10984470B1 (en) | 2013-06-28 | 2021-04-20 | Winklevoss Ip, Llc | Systems for redeeming shares in an entity holding digital math-based assets |
| US10984472B1 (en) | 2013-06-28 | 2021-04-20 | Winklevoss Ip, Llc | Systems, methods, and program products for an application programming interface generating a blended digital math-based assets index |
| US10354325B1 (en) | 2013-06-28 | 2019-07-16 | Winklevoss Ip, Llc | Computer-generated graphical user interface |
| US11580532B1 (en) | 2013-06-28 | 2023-02-14 | Gemini Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
| US11568398B1 (en) | 2013-06-28 | 2023-01-31 | Gemini Ip, Llc | Systems and methods for storing digital math-based assets using a secure portal |
| US11741438B2 (en) | 2014-03-17 | 2023-08-29 | Coinbase, Inc. | Cryptographic currency exchange |
| US10510053B2 (en) | 2014-03-17 | 2019-12-17 | Coinbase, Inc. | Send cryptographic currency to email address |
| US10755241B2 (en) | 2014-03-17 | 2020-08-25 | Coinbase, Inc. | Hot wallet for holding bitcoin |
| US10891600B2 (en) | 2014-03-17 | 2021-01-12 | Coinbase, Inc. | User private key control |
| US10614430B2 (en) | 2014-03-17 | 2020-04-07 | Coinbase, Inc. | Instant exchange |
| US10878389B2 (en) | 2014-03-17 | 2020-12-29 | Coinbase, Inc. | Cryptographic currency exchange |
| US9672499B2 (en) | 2014-04-02 | 2017-06-06 | Modernity Financial Holdings, Ltd. | Data analytic and security mechanism for implementing a hot wallet service |
| US11196566B2 (en)* | 2014-05-09 | 2021-12-07 | Reginald Middleton | Devices, systems, and methods for facilitating low trust and zero trust value transfers |
| US20220052857A1 (en)* | 2014-05-09 | 2022-02-17 | Reginald Middleton | Devices, systems, and methods for facilitating low trust and zero trust value transfers |
| US11895246B2 (en)* | 2014-05-09 | 2024-02-06 | Reginald Middleton | Devices, systems, and methods for facilitating low trust and zero trust value transfers |
| US20240179011A1 (en)* | 2014-05-09 | 2024-05-30 | Veritaseum, Inc. | Devices, systems, and methods for facilitating low trust and zero trust value transfers |
| US12231579B2 (en)* | 2014-05-09 | 2025-02-18 | Veritaseum, Inc. | Devices, systems, and methods for facilitating low trust and zero trust value transfers |
| US10778682B1 (en) | 2015-01-26 | 2020-09-15 | Winklevoss Ip, Llc | Authenticating a user device associated with a user to communicate via a wireless network in a secure web-based environment |
| US11283797B2 (en) | 2015-01-26 | 2022-03-22 | Gemini Ip, Llc | Authenticating a user device associated with a user to communicate via a wireless network in a secure web-based environment |
| US10484376B1 (en) | 2015-01-26 | 2019-11-19 | Winklevoss Ip, Llc | Authenticating a user device associated with a user to communicate via a wireless network in a secure web-based environment |
| US12143382B1 (en) | 2015-01-26 | 2024-11-12 | Gemini Ip, Llc | Authenticating a user device associated with a user to communicate via a wireless network in a secure web-based environment |
| US11687885B2 (en) | 2015-02-27 | 2023-06-27 | Visa International Service Association | Transaction signing utilizing asymmetric cryptography |
| US10693632B1 (en) | 2015-03-16 | 2020-06-23 | Winklevoss Ip, Llc | Autonomous devices |
| US12393929B1 (en) | 2015-03-16 | 2025-08-19 | Gemini Ip, Llc | Autonomous device multi-transfer methodology |
| US11783323B1 (en) | 2015-03-16 | 2023-10-10 | Gemini Ip, Llc | Autonomous devices |
| US11362814B1 (en) | 2015-03-16 | 2022-06-14 | Gemini Ip, Llc | Autonomous devices |
| US12284288B1 (en) | 2015-03-16 | 2025-04-22 | Gemini Ip, Llc | Autonomous devices for authorizing and performing transactions of digital assets |
| US10915891B1 (en) | 2015-03-16 | 2021-02-09 | Winklevoss Ip, Llc | Autonomous devices |
| US10516527B1 (en)* | 2015-04-17 | 2019-12-24 | EMC IP Holding Company LLC | Split-key based cryptography system for data protection and synchronization across multiple computing devices |
| US11218295B2 (en) | 2015-05-19 | 2022-01-04 | Coinbase, Inc. | Private key decryption system and method of use |
| US11488147B2 (en) | 2015-07-14 | 2022-11-01 | Fmr Llc | Computationally efficient transfer processing and auditing apparatuses, methods and systems |
| US12225127B2 (en) | 2015-07-14 | 2025-02-11 | Fmr Llc | Address verification, seed splitting and firmware extension for secure cryptocurrency key backup, restore, and transaction signing platform apparatuses, methods and systems |
| US10778439B2 (en) | 2015-07-14 | 2020-09-15 | Fmr Llc | Seed splitting and firmware extension for secure cryptocurrency key backup, restore, and transaction signing platform apparatuses, methods and systems |
| US10992469B2 (en) | 2015-07-14 | 2021-04-27 | Fmr Llc | Seed splitting and firmware extension for secure cryptocurrency key backup, restore, and transaction signing platform apparatuses, methods and systems |
| US10644885B2 (en) | 2015-07-14 | 2020-05-05 | Fmr Llc | Firmware extension for secure cryptocurrency key backup, restore, and transaction signing platform apparatuses, methods and systems |
| US12323524B2 (en) | 2015-07-14 | 2025-06-03 | Fmr Llc | Social aggregating, fractionally efficient transfer guidance, conditional triggered transaction, datastructures, apparatuses, methods and systems |
| US10339523B2 (en) | 2015-07-14 | 2019-07-02 | Fmr Llc | Point-to-point transaction guidance apparatuses, methods and systems |
| WO2017044554A1 (en) | 2015-09-11 | 2017-03-16 | Aware, Inc. | Biometric verification of a blockchain database transaction contributor |
| US10666423B2 (en) | 2015-09-11 | 2020-05-26 | Aware, Inc. | Biometric verification of a blockchain database transaction contributor |
| US11108546B2 (en) | 2015-09-11 | 2021-08-31 | Aware, Inc. | Biometric verification of a blockchain database transaction contributor |
| CN108352009A (en)* | 2015-11-09 | 2018-07-31 | 日本电信电话株式会社 | Block chain generating means, block chain generation method, block chain verification device, block chain verification method and program |
| US10504179B1 (en) | 2015-12-08 | 2019-12-10 | Fmr Llc | Social aggregated fractional equity transaction partitioned acquisition apparatuses, methods and systems |
| US11074663B2 (en) | 2015-12-31 | 2021-07-27 | Camelot Uk Bidco Limited | System and method of facilitating intellectual property transactions |
| CN109155034A (en)* | 2016-04-29 | 2019-01-04 | 区块链控股有限公司 | Implementing logic gate functions using blockchains |
| US10547441B2 (en) | 2016-09-02 | 2020-01-28 | Conio Inc. | Method and apparatus for restoring access to digital assets |
| US10698885B2 (en) | 2017-05-25 | 2020-06-30 | Alibaba Group Holding Limited | Method and device for writing service data in block chain system |
| US11074245B2 (en) | 2017-05-25 | 2021-07-27 | Advanced New Technologies Co., Ltd. | Method and device for writing service data in block chain system |
| US11356250B2 (en)* | 2017-08-28 | 2022-06-07 | Advanced New Technologies Co., Ltd. | Key data processing |
| US11095437B2 (en) | 2017-08-28 | 2021-08-17 | Advanced New Technologies Co., Ltd. | Key data processing method and apparatus, and server |
| US20200127817A1 (en)* | 2017-08-28 | 2020-04-23 | Alibaba Group Holding Limited | Key data processing method and apparatus, and server |
| US10873449B2 (en)* | 2017-08-28 | 2020-12-22 | Advanced New Technologies Co., Ltd. | Key data processing method and apparatus, and server |
| US10797865B2 (en)* | 2017-08-28 | 2020-10-06 | Alibaba Group Holding Limited | Key data processing method and apparatus, and server |
| US11636471B2 (en) | 2017-12-15 | 2023-04-25 | Fmr Llc | Social data tracking datastructures, apparatuses, methods and systems |
| US11436598B2 (en) | 2017-12-15 | 2022-09-06 | Fmr Llc | Social data tracking datastructures, apparatuses, methods and systems |
| US11392940B2 (en) | 2018-01-17 | 2022-07-19 | Tzero Ip, Llc | Multi-approval system using M of N keys to perform an action at a customer device |
| US11429959B2 (en) | 2018-01-17 | 2022-08-30 | Tzero Ip, Llc | Multi-approval system using M of N keys to generate a transaction address |
| US11216809B2 (en) | 2018-01-17 | 2022-01-04 | Tzero Ip, Llc | Multi-approval system using M of N keys to restore a customer wallet |
| WO2019143850A1 (en)* | 2018-01-17 | 2019-07-25 | Medici Ventures, Inc. | Multi-approval system using m of n keys to generate a transaction address |
| JP2021511595A (en)* | 2018-01-17 | 2021-05-06 | メディチ・ベンチャーズ，インコーポレーテッド | Multi-authorization system that uses M out of N keys to generate transaction addresses |
| US11531985B2 (en) | 2018-01-17 | 2022-12-20 | Tzero Ip, Llc | Multi-approval system using M of N keys to generate a sweeping transaction at a customer device |
| JP7269944B2 (en) | 2018-01-17 | 2023-05-09 | ティーゼロ・アイピー，エルエルシー | A multi-authorization system that uses M out of N keys to generate transaction addresses |
| US11308487B1 (en) | 2018-02-12 | 2022-04-19 | Gemini Ip, Llc | System, method and program product for obtaining digital assets |
| US11139955B1 (en) | 2018-02-12 | 2021-10-05 | Winklevoss Ip, Llc | Systems, methods, and program products for loaning digital assets and for depositing, holding and/or distributing collateral as a token in the form of digital assets on an underlying blockchain |
| US12277554B1 (en) | 2018-02-12 | 2025-04-15 | Gemini Ip, Llc | Systems, method, and program product for making payments using fiat-backed digital assets |
| US12141871B1 (en) | 2018-02-12 | 2024-11-12 | Gemini Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
| US10540653B1 (en) | 2018-02-12 | 2020-01-21 | Winklevoss Ip, Llc | System, method and program product for modifying a supply of stable value digital asset tokens |
| US11909860B1 (en) | 2018-02-12 | 2024-02-20 | Gemini Ip, Llc | Systems, methods, and program products for loaning digital assets and for depositing, holding and/or distributing collateral as a token in the form of digital assets on an underlying blockchain |
| US11200569B1 (en) | 2018-02-12 | 2021-12-14 | Winklevoss Ip, Llc | System, method and program product for making payments using fiat-backed digital assets |
| US11475442B1 (en) | 2018-02-12 | 2022-10-18 | Gemini Ip, Llc | System, method and program product for modifying a supply of stable value digital asset tokens |
| US10373158B1 (en) | 2018-02-12 | 2019-08-06 | Winklevoss Ip, Llc | System, method and program product for modifying a supply of stable value digital asset tokens |
| US10540654B1 (en) | 2018-02-12 | 2020-01-21 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
| US11522700B1 (en) | 2018-02-12 | 2022-12-06 | Gemini Ip, Llc | Systems, methods, and program products for depositing, holding and/or distributing collateral as a token in the form of digital assets on an underlying blockchain |
| US10540640B1 (en) | 2018-03-05 | 2020-01-21 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
| US11562333B1 (en) | 2018-03-05 | 2023-01-24 | Gemini Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
| US10373129B1 (en) | 2018-03-05 | 2019-08-06 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
| US10929842B1 (en) | 2018-03-05 | 2021-02-23 | Winklevoss Ip, Llc | System, method and program product for depositing and withdrawing stable value digital assets in exchange for fiat |
| US12271898B1 (en) | 2018-03-05 | 2025-04-08 | Gemini Ip, Llc | System, method and program product for modifying a supply of stable value digital asset tokens |
| US10438290B1 (en) | 2018-03-05 | 2019-10-08 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
| US11727401B1 (en) | 2018-03-05 | 2023-08-15 | Gemini Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
| US11017391B1 (en) | 2018-03-05 | 2021-05-25 | Winklevoss Ip, Llc | System, method and program product for generating and utilizing stable value digital assets |
| US11334883B1 (en) | 2018-03-05 | 2022-05-17 | Gemini Ip, Llc | Systems, methods, and program products for modifying the supply, depositing, holding and/or distributing collateral as a stable value token in the form of digital assets |
| US11720887B1 (en) | 2018-03-05 | 2023-08-08 | Gemini Ip, Llc | System, method and program product for depositing and withdrawing stable value digital assets in exchange for fiat |
| US12243057B2 (en) | 2018-04-17 | 2025-03-04 | Coinbase, Inc. | Offline storage system and method of use |
| WO2019204426A1 (en)* | 2018-04-17 | 2019-10-24 | Coinbase, Inc. | Offline storage system and method of use |
| US20190354971A1 (en)* | 2018-05-15 | 2019-11-21 | Mfe Capital, Llc | Systems and methods for cold payment solution |
| US11381392B2 (en)* | 2018-05-15 | 2022-07-05 | Mfe Capital, Llc | Device for off-line storage and usage of digital assets |
| US20190356484A1 (en)* | 2018-05-15 | 2019-11-21 | Mfe Capital, Llc | Device for off-line storage and usage of digital assets |
| US11176548B2 (en)* | 2018-05-15 | 2021-11-16 | Mfe Capital, Llc | Systems and methods for cold payment solution |
| US11164182B2 (en) | 2018-05-17 | 2021-11-02 | Conio Inc. | Methods and systems for safe creation, custody, recovery, and management of a digital asset |
| WO2019221956A1 (en)* | 2018-05-17 | 2019-11-21 | Conio Inc. | Methods and systems for safe creation, custody, recovery, and management of a digital asset |
| US10762235B2 (en)* | 2018-06-12 | 2020-09-01 | Mcafee, Llc | Methods, systems, and media for storing and retrieving data from distributed vaults |
| EP3807753A4 (en)* | 2018-06-12 | 2022-03-02 | McAfee, LLC | METHODS, SYSTEMS AND MEDIA FOR STORING AND RETRIEVING DATA FROM DISTRIBUTED VAULTS |
| US11818275B2 (en) | 2018-08-02 | 2023-11-14 | Paypal, Inc. | Techniques for securing application programming interface requests using multi-party digital signatures |
| US11444779B2 (en) | 2018-08-02 | 2022-09-13 | Paypal, Inc. | Techniques for securing application programming interface requests using multi-party digital signatures |
| US11689371B2 (en) | 2018-08-02 | 2023-06-27 | Paypal, Inc. | Techniques for securing digital signatures using multi-party computation |
| US20210224797A1 (en)* | 2018-08-27 | 2021-07-22 | Fireblocks Ltd. | System and method for securing crypto-asset transactions |
| US11900366B2 (en)* | 2018-08-27 | 2024-02-13 | Fireblocks Ltd. | System and method for securing crypto-asset transactions |
| US20240211937A1 (en)* | 2018-08-27 | 2024-06-27 | Fireblocks Ltd. | System and method for securing crypto-asset transactions |
| US11538063B2 (en) | 2018-09-12 | 2022-12-27 | Samsung Electronics Co., Ltd. | Online fraud prevention and detection based on distributed system |
| US12088701B2 (en) | 2018-12-06 | 2024-09-10 | Galaxy Digital Trading Llc | Secure consensus over a limited connection |
| US11394543B2 (en) | 2018-12-13 | 2022-07-19 | Coinbase, Inc. | System and method for secure sensitive data storage and recovery |
| US10402823B1 (en)* | 2018-12-30 | 2019-09-03 | Alexander Vladimirovich Vlasov | System for exchanging private keys for mutual settlements between users of a cryptocurrency outside blockchains |
| US12093942B1 (en) | 2019-02-22 | 2024-09-17 | Gemini Ip, Llc | Systems, methods, and program products for modifying the supply, depositing, holding, and/or distributing collateral as a stable value token in the form of digital assets |
| US11995596B2 (en)* | 2019-04-04 | 2024-05-28 | Sony Corporation | System, method, and computer-readable medium for tracking information exchange |
| US20200320458A1 (en)* | 2019-04-04 | 2020-10-08 | Sony Corporation | System, method, and computer-readable medium for tracking information exchange |
| US11501370B1 (en) | 2019-06-17 | 2022-11-15 | Gemini Ip, Llc | Systems, methods, and program products for non-custodial trading of digital assets on a digital asset exchange |
| US12354163B1 (en) | 2019-06-17 | 2025-07-08 | Gemini Ip, Llc | Systems, methods, and program products for non-custodial trading of digital assets on a digital asset exchange |
| US10903991B1 (en) | 2019-08-01 | 2021-01-26 | Coinbase, Inc. | Systems and methods for generating signatures |
| US11552792B2 (en) | 2019-08-01 | 2023-01-10 | Coinbase, Inc. | Systems and methods for generating signatures |
| US11943350B2 (en)* | 2019-10-16 | 2024-03-26 | Coinbase, Inc. | Systems and methods for re-using cold storage keys |
| US20210119781A1 (en)* | 2019-10-16 | 2021-04-22 | Coinbase, Inc. | Systems and methods for re-using cold storage keys |
| US11915314B2 (en) | 2019-11-22 | 2024-02-27 | Conio Inc. | Method and apparatus for a blockchain-agnostic safe multi-signature digital asset management |
| US11829510B2 (en) | 2020-01-15 | 2023-11-28 | Ledgerdomain Inc. | Secure messaging in a machine learning blockchain network |
| US12105842B1 (en) | 2020-01-15 | 2024-10-01 | Ledgerdomain Inc. | Verifiable credentialling and message content provenance authentication |
| US12314437B2 (en) | 2020-01-15 | 2025-05-27 | Ledgerdomain Inc. | Secure messaging in a machine learning blockchain network |
| US11848758B1 (en) | 2020-01-15 | 2023-12-19 | Ledgerdomain Inc. | Secure messaging in a blockchain network |
| US11769577B1 (en) | 2020-01-15 | 2023-09-26 | Ledgerdomain Inc. | Decentralized identity authentication framework for distributed data |
| US12300371B1 (en) | 2020-01-15 | 2025-05-13 | Ledgerdomain Inc. | Decentralized identity authentication framework for distributed data |
| US12388633B2 (en) | 2020-09-14 | 2025-08-12 | Paypal, Inc. | Techniques for single round multi-party computation for digital signatures |
| US11943346B2 (en) | 2020-09-14 | 2024-03-26 | Paypal, Inc. | Techniques for single round multi-party computation for digital signatures |
| US11632244B2 (en) | 2020-09-14 | 2023-04-18 | Paypal, Inc. | Techniques for single round multi-party computation for digital signatures |
| US11989720B2 (en) | 2020-10-14 | 2024-05-21 | Mobilecoin Inc. | System and method for oblivious information retrieval |
| US12354085B2 (en) | 2021-03-31 | 2025-07-08 | Paypal, Inc. | Using an internal ledger with blockchain transactions |
| US11922403B2 (en) | 2021-03-31 | 2024-03-05 | Paypal, Inc. | Using an internal ledger with blockchain transactions |
| US11587072B2 (en) | 2021-05-20 | 2023-02-21 | Bank Of America Corporation | System for secure resource transfer integration |
| US11848754B1 (en) | 2022-11-07 | 2023-12-19 | Ledgerdomain Inc. | Access delegation leveraging private keys on keystores read by provisioned devices |
| US12323520B1 (en) | 2022-11-07 | 2025-06-03 | Ledgerdomain Inc. | Management of recipient credentials leveraging private keys on keystores read by provisioned devices |
| US11736290B1 (en) | 2022-11-07 | 2023-08-22 | Ledgerdomain Inc. | Management of recipient credentials leveraging private keys on keystores read by provisioned devices |
| US12271464B1 (en) | 2022-11-07 | 2025-04-08 | Ledgerdomain Inc. | Credential revocation leveraging private keys on keystores read by provisioned devices |
| US11741216B1 (en) | 2022-11-07 | 2023-08-29 | Ledgerdomain Inc. | Credential revocation leveraging private keys on keystores read by provisioned devices |
| US11741215B1 (en)* | 2022-11-07 | 2023-08-29 | Ledgerdomain Inc. | Recipient credentialing leveraging private keys on keystores read by provisioned devices |
| US12141267B1 (en)* | 2022-11-07 | 2024-11-12 | Ledgerdomain Inc. | Recipient credentialing leveraging private keys on keystores read by provisioned devices |
Also Published As
| Publication number | Publication date |
|---|---|
| US20150262172A1 (en) | 2015-09-17 |
| US20190156303A1 (en) | 2019-05-23 |
| US10614430B2 (en) | 2020-04-07 |
| US20150262168A1 (en) | 2015-09-17 |
| WO2015142765A1 (en) | 2015-09-24 |
| US20150262138A1 (en) | 2015-09-17 |
| US11741438B2 (en) | 2023-08-29 |
| US10891600B2 (en) | 2021-01-12 |
| US20210073753A1 (en) | 2021-03-11 |
| US20150262176A1 (en) | 2015-09-17 |
| US10510053B2 (en) | 2019-12-17 |
| US10229396B2 (en) | 2019-03-12 |
| US9436935B2 (en) | 2016-09-06 |
| US10755241B2 (en) | 2020-08-25 |
| US20150262140A1 (en) | 2015-09-17 |
| US20150262137A1 (en) | 2015-09-17 |
| US20150262139A1 (en) | 2015-09-17 |
| US10878389B2 (en) | 2020-12-29 |
| US20150262141A1 (en) | 2015-09-17 |
| US20230368158A1 (en) | 2023-11-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11741438B2 (en) | Cryptographic currency exchange | |
| US20250299169A1 (en) | Token-based email authentication for secure peer-to-peer financial transactions without user login | |
| US11222316B2 (en) | Real time virtual draft system and method | |
| US12073384B2 (en) | Requesting payments for selected items or services using payment tokens | |
| US20230351499A1 (en) | System and method for integrated application and provisioning | |
| US20190005497A1 (en) | Method and system for facilitating online payments based on an established payment agreement | |
| US10089667B2 (en) | E-mail invoked electronic commerce | |
| US20170286951A1 (en) | Dynamic Delivery Authorization for Cryptographic Payments | |
| US20180089655A1 (en) | Real time virtual draft system and method | |
| US20160005043A1 (en) | Apparatus and method for purchasing a product using an electronic device | |
| CN104021492A (en) | On-line purchasing method for protecting secretes of customer and system thereof | |
| KR20040010510A (en) | System and method for third-party payment processing | |
| US20200294045A1 (en) | Interaction processing system and method | |
| JP2019519861A (en) | A secure way to provide a shipping address during a tokenized transaction | |
| KR20230000595A (en) | Electronic purchasing system and method connected with erp | |
| US12373823B2 (en) | Facilitating cryptocurrency-based transactions with time constraint | |
| KR20010090032A (en) | Online direct settlement systems and the methods thereof | |
| JP2021512435A (en) | Online transaction information protection system and online transaction information protection method | |
| CN115082050A (en) | Transaction method, system, device, equipment and medium for third party payment | |
| AU2020102852A4 (en) | Online transaction information security system and online transaction information security method | |
| EP2959441A1 (en) | Apparatus and method for purchasing a product using an electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| AS | Assignment | Owner name:COINBASE, INC., CALIFORNIA Free format text:ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LANGSCHAEDEL, JULIAN;ARMSTRONG, BRIAN D.;EHRSAM, FRED E.;SIGNING DATES FROM 20150313 TO 20150317;REEL/FRAME:035185/0950 | |
| STPP | Information on status: patent application and granting procedure in general | Free format text:DOCKETED NEW CASE - READY FOR EXAMINATION | |
| STPP | Information on status: patent application and granting procedure in general | Free format text:NON FINAL ACTION MAILED | |
| STPP | Information on status: patent application and granting procedure in general | Free format text:RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER | |
| STPP | Information on status: patent application and granting procedure in general | Free format text:FINAL REJECTION MAILED | |
| STPP | Information on status: patent application and granting procedure in general | Free format text:DOCKETED NEW CASE - READY FOR EXAMINATION | |
| STPP | Information on status: patent application and granting procedure in general | Free format text:NON FINAL ACTION MAILED | |
| STCB | Information on status: application discontinuation | Free format text:ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |