Blockchain web browser interface

Abstract

A computer-implemented method records and maintains a record of browser events in a blockchain using a peer-to-peer network. One or more processors detect one or more browser events for a browser on a computer. One or more processors then transmit transactions that are associated with the one or more browser events from the computer to a peer-to-peer network of devices that create a blockchain, which includes one or more blocks that describe the one or more browser events, such that the blockchain records and maintains a record of browser events that occur at the computer.

What is claimed is: 
     
       1. A computer-implemented method of recording and maintaining a record of browser events in a blockchain, the computer-implemented method comprising:
 detecting, by one or more processors, one or more browser events for a browser on a computer; 
 transmitting, by one or more processors, transactions associated with the one or more browser events from the computer to a peer-to-peer network of devices that create a blockchain, wherein the blockchain comprises one or more blocks that describe the one or more browser events for the browser on the computer, wherein the blockchain records and maintains a record of browser events that occur at the computer, wherein the record of browser events maintained in the blockchain comprises records of uniform resource locators (URLs) browsed by the user, bookmarks added to the browser, and search terms searched by the user, wherein the peer-to-peer network is a system of networked computers that are in communication with the browser, and wherein the blockchain is accessible to the computer on which the browser is operating in order to provide a private and secure copy of the browser events for the browser; and 
 adjusting, by one or more processors, a frequency of transmitting the transactions associated with the one or more browser events from the computer to the peer-to-peer network of devices according to types of webpages being browsed by the computer, wherein webpages that contain highly transitory information of the browser events and that is scrubbed from the webpages at predefined intervals have their transactions sent to the peer-to-peer network at sub-intervals of the predefined intervals. 
 
     
     
       2. The computer-implemented method of  claim 1 , further comprising:
 receiving, by the computer, the blockchain from the peer-to-peer network; and 
 merging, by the computer, blocks from the blockchain into a ledger of browser events in the computer. 
 
     
     
       3. The computer-implemented method of  claim 1 , wherein the record of browser events maintained in the blockchain comprises a record of security patches added to the browser. 
     
     
       4. The computer-implemented method of  claim 1 , wherein the record of browser events maintained in the blockchain comprises a record of cookies sent to the computer, wherein the cookies are files that hold data specific to the computer and websites visited by the computer. 
     
     
       5. The computer-implemented method of  claim 1 , further comprising:
 adjusting, by one or more processors, a frequency of transmitting the transactions associated with the one or more browser events from the computer to the peer-to-peer network of devices according to a current geolocation of the computer. 
 
     
     
       6. The computer-implemented method of  claim 1 , further comprising:
 performing, by one or more processors, a vulnerability analysis for the computer, wherein the vulnerability analysis determines how vulnerable the computer and the browser are to a malicious attack; and 
 adjusting, by one or more processors, a frequency of transmitting the transactions associated with the one or more browser events from the computer to the peer-to-peer network of devices according to how vulnerable the computer and the browser are to the malicious attack. 
 
     
     
       7. The computer-implemented method of  claim 1 , wherein the peer-to-peer network selectively generates blocks to be incorporated into the blockchain for only predefined types of browser events that are extracted from the transactions associated with the one or more browser events that are received from the computer. 
     
     
       8. The computer-implemented method of  claim 1 , further comprising:
 transmitting, by one or more processors, the transactions that are associated with the one or more browser events to a validation module in the peer-to-peer network, wherein the one or more blocks are not added to the blockchain until the validation module validates the transactions that are associated with the one or more browser events. 
 
     
     
       9. The computer-implemented method of  claim 1 , further comprising:
 obtaining, by one or more processors, a historical block identifier from a browser historic blockchain representative of historical activities that the user conducted with respect to the browser; 
 receiving, by one or more processors, one or more validation requirements with respect to the user activities on the browser; 
 obtaining, by one or more processors, a validation token indicative of a validity of user actions of the user and based on a set of browser tokens comprising one or more inputs related to activities of the user; and 
 computing, by one or more processors, a chaincode block for a transaction against said one or more validation requirements as a function of browser parameters that are based on the validation token, a historical browser's block identifier, and the set of browser tokens. 
 
     
     
       10. The computer-implemented method of  claim 1 , further comprising:
 receiving, by one or more processors, a signal activating a blockchain enabling button on a toolbar on the computer, wherein transmitting the transactions that are associated with the one or more browser events from the computer to the peer-to-peer network of devices that create the blockchain is in response to receiving the signal activating the blockchain enabling button. 
 
     
     
       11. A computer program product for recording and maintaining a record of browser events in a blockchain, the computer program product comprising a non-transitory computer readable storage device having program instructions embodied therewith, the program instructions readable and executable by a computer to perform a set of steps, the steps comprising:
 detecting one or more browser events for a browser on a computer; 
 transmitting descriptions of the one or more browser events from the computer to a peer-to-peer network of devices that create a blockchain, wherein the blockchain comprises one or more blocks that describe the one or more browser events, wherein the blockchain records and maintains a record of browser events that occur at the computer, wherein the record of browser events maintained in the blockchain comprises records of uniform resource locators (URLs) browsed by user bookmarks added to the browser and search terms searched by the user, wherein the peer-to-peer network is a system of networked computers that are in communication with the browser, and wherein the blockchain is accessible to the computer on which the browser is operating in order to provide a private and secure copy of the browser events for the browser; and 
 adjusting a frequency of transmitting the transactions associated with the one or more browser events from the computer to the peer-to-peer network of devices according to types of webpages being browsed by the computer, wherein webpages that contain highly transitory information of the browser events and that is scrubbed from the webpages at predefined intervals have their transactions sent to the peer-to-peer network at sub-intervals of the predefined intervals. 
 
     
     
       12. The computer program product of  claim 10 , wherein the steps further comprise:
 receiving, by the computer, the blockchain from the peer-to-peer network; and 
 merging, by the computer, blocks from the blockchain into a ledger of browser events in the computer. 
 
     
     
       13. The computer program product of  claim 10 , wherein the record of browser events maintained in the blockchain comprises a record of a browser version of the browser. 
     
     
       14. The computer program product of  claim 10 , wherein the record of browser events maintained in the blockchain comprises a record of cookies sent to the computer, wherein the cookies are files that hold data specific to the computer and web sites visited by the computer. 
     
     
       15. The computer program product of  claim 10 , wherein the steps further comprise:
 adjusting a frequency of transmitting the transactions that are associated with the one or more browser events from the computer to the peer-to-peer network of devices according to a current geolocation of the computer. 
 
     
     
       16. The computer program product of  claim 10 , wherein the steps further comprise:
 performing a vulnerability analysis for the computer, wherein the vulnerability analysis determines how vulnerable the computer and the browser are to a malicious attack; and 
 adjusting a frequency of transmitting the transactions that are associated with the one or more browser events from the computer to the peer-to-peer network of devices according to how vulnerable the computer and the browser are to the malicious attack. 
 
     
     
       17. The computer program product of  claim 10 , wherein the peer-to-peer network selectively generates a block to be incorporated into the blockchain for only predefined types of browser events that are extracted from a transaction that is received from the computer. 
     
     
       18. A computer-implemented method of tracking and maintaining a record of disparate browser events, the computer-implemented method comprising:
 detecting, by one or more processors, browser events for a browser on a computer, wherein the browser events comprises uniform resource locators (URLs) browsed by the browser, user bookmarks added to the browser by a user, and search terms searched by the user; 
 transmitting, by one or more processors, transactions that are associated with the browser events from the computer to a trans-vendor service, wherein the trans-vendor service operates across disparate browsers, devices, and operating systems, wherein the trans-vendor service generates a blockchain that comprises one or more blocks that comprise the transactions that are associated with the browser events from the computer and blocks that describe browser events from the disparate browsers, devices, and operating systems, wherein the trans-vendor service utilizes a system of networked computers that are in communication with the browser, and wherein the blockchain is accessible to the computer on which the browser is operating in order to provide a private and secure copy of the browser events for the browser to the computer; and 
 adjusting, by one or more processors, a frequency of transmitting the transactions associated with the browser events from the computer to the trans-vendor service according to types of webpages being browsed by the computer, wherein webpages that contain highly transitory information of the browser events and that is scrubbed from the webpages at predefined intervals have their transactions sent to the trans-vendor service at sub-intervals of the predefined intervals.