CN113498592A

CN113498592A - Digital property authentication and management system

Info

Publication number: CN113498592A
Application number: CN202080015833.9A
Authority: CN
Inventors: L·C·李; D·克劳斯; D·C·安德鲁斯; S·C·弗莱明; L·B·李; S·J·德斯蒙德
Original assignee: Aon Risk Services Inc of Maryland
Current assignee: Aon Risk Services Inc of Maryland
Priority date: 2019-02-20
Filing date: 2020-02-20
Publication date: 2021-10-12
Anticipated expiration: 2040-02-20
Also published as: CN113498592B; EP3928465A1; WO2020172382A1; EP3928465A4

Abstract

Systems and methods for digital property authentication and management are disclosed. A registration of a document representing a trade secret with a trade secret registry may be requested. A document obfuscation value corresponding to the document may be generated and may be registered with the blockchain. A record of the enrollment may be generated for the trade secret enrollment station. The registry may be searchable and/or provide functions such as valuation, insurance and/or validation, among other benefits and functions.

Description

Digital property authentication and management system

Cross Reference to Related Applications

This application claims U.S. patent application No. 16/280,557 entitled "Digital Property Authentication and Management System" filed on 20.2.2019, U.S. patent application No. 16/280,622 entitled "Digital Property Authentication and Management System" filed on 20.2.2019, U.S. patent application No. 16/280,670 entitled "Digital Property Authentication and Management System" filed on 20.2.2019, U.S. patent application No. 16/280,703 entitled "Digital Property Authentication and Management System" filed on 20.2.2019, and U.S. patent application No. 16/280,766 entitled "Digital Property Authentication and Management System" filed on 20.2.2.2019, the entire contents of which are incorporated herein by reference.

Background

Trade secrets can be valuable assets of companies and individuals. However, unlike intellectual property in other forms, no government registration and/or grant of trade secret rights is provided. Described herein are technological improvements and solutions to technical problems that may be used to assist in protecting business secrets and the like.

Drawings

A detailed description is given below with reference to the accompanying drawings. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items. The systems depicted in the drawings are not drawn to scale and the elements within the drawings may be depicted as not being to scale with respect to each other.

FIG. 1 illustrates a schematic diagram of an exemplary environment for a digital property authentication and management system.

FIG. 2 illustrates an exemplary user interface displaying a trade secret enrollment function in accordance with the digital property authentication and management system.

FIG. 3 illustrates an exemplary user interface displaying trade secret maintenance functionality in accordance with the digital property authentication and management system.

FIG. 4 illustrates an exemplary user interface displaying a trade secret verification function in accordance with the digital property authentication and management system.

FIG. 5 illustrates an exemplary user interface displaying insurance policy functionality in accordance with the digital property authentication and management system.

FIG. 6 illustrates an exemplary user interface displaying valuation functions in accordance with the digital property authentication and management system.

FIG. 7 illustrates an exemplary user interface displaying access control functions in accordance with the digital property authentication and management system.

FIG. 8 depicts a flowchart of an exemplary process for trade secret enrollment in accordance with the digital property authentication and management system.

FIG. 9 depicts a flowchart of an exemplary process for commercial secret verification in accordance with a digital property authentication and management system.

FIG. 10 shows a flowchart of an exemplary process for digital property authentication.

FIG. 11 shows a flow diagram of another exemplary process for digital property authentication.

FIG. 12 depicts a flowchart of another example process for digital property authentication.

FIG. 13 shows a flowchart of another exemplary process for digital property authentication.

FIG. 14 depicts a flowchart of an exemplary process for identifying differences between documents associated with a digital property authentication and management system.

FIG. 15 depicts a flowchart of an exemplary process associated with a user interface in accordance with the digital property authentication and management system.

FIG. 16 depicts a flowchart of another exemplary process associated with a user interface in accordance with the digital property authentication and management system.

FIG. 17 sets forth a flow chart illustrating an exemplary process for digital property management including document version control.

FIG. 18 shows a flowchart of an exemplary process for digital property management including trade secret valuation.

FIG. 19 shows a flowchart of an exemplary process for digital property management including access control.

FIG. 20 shows a flowchart of an exemplary process for valuing an asset in accordance with a digital asset authentication and management system.

FIG. 21 shows a flowchart of an exemplary process for providing an insurance policy in accordance with the digital property authentication and management system.

FIG. 22 depicts a flowchart of an exemplary process for enrollment verification in accordance with the digital property authentication and management system.

FIG. 23 depicts a flowchart of another exemplary process for enrollment verification in accordance with the digital property authentication and management system.

Detailed Description

Systems and methods for digital property authentication and management are disclosed. Take as an example a company or individual that owns one or more intellectual property assets described herein as an entity. Although some of these intellectual property assets may be registerable by a governmental entity, such as a patent and trademark applied and issued by the U.S. patent and trademark office or a copyright registered by the U.S. copyright office, other types of intellectual property such as trade secrets may not be registerable by a governmental entity. Additionally, information (sometimes referred to as confidential information or proprietary technology) that may not conform to a particular (e.g., legal) definition of a business secret and/or may not conform to a variety of different definitions of a business secret may still be valuable to an entity. In these and other examples, a system that allows such properties (collectively referred to herein as "trade secrets") to be registered in a manner that establishes ownership flags, possession confidence, or other information that helps evaluate protection, insurance, or enforcement of such properties would be beneficial to such entities.

The innovations described herein provide a digital property authentication and management system that, among other things, can register information, documents, and/or other properties, provide a user interface for registering and managing such properties, can verify the registration and/or analysis of properties that may be misappropriated, assist in asset valuation, assist in providing insurance, and augment functionality associated with registered properties with data generated by and/or made available to the system.

For example, a client-side device and/or system described herein as an electronic device may include an application that enables a user of the device and/or system to provide input to the device. For example, the input may indicate a document that represents or is descriptive of the business secret, and/or has been designated as a document of significance to the entity. A client-side device and/or system can include an obfuscation component that can receive data representative of a document and can generate a document obfuscation value corresponding to the document. For example, a document obfuscation value may include a string of numbers and/or letters, and may be based at least in part on the content of the document and/or one or more information fields associated with the document. It should be noted that although document obfuscation value generation and use is described in this disclosure by way of example, one or more other forms of digital obfuscation may be utilized in addition to or in place of document obfuscation value generation. Given the same input data (such as the same document), digital obfuscation techniques may allow for repeatable production of output data.

The client-side device and/or system may send the document obfuscation value and, in an example, request data indicating a request to register the document obfuscation value in association with a business secret registry to a registration system. The registration system may receive the document obfuscation value and/or the request data and may initiate a process of registering the document obfuscation value in association with the commercial secret registry. For example, the registration system may send a document obfuscation value and/or request data to a blockchain system that manages one or more blockchains. In other examples, the client-side device may send a document obfuscation value and/or request data to the blockchain system, as described more fully elsewhere herein. In other examples, the registration system and the client-side device may send instances of document obfuscation values and/or request data to the blockchain system in parallel or near parallel. The request data may indicate a request to register a document obfuscation value and/or identification information associated with the document and/or document at the blockchain. The blockchain system may register document obfuscation values and/or other information described herein in association with the blocks of the blockchain. The encrypted document obfuscation value may be generated by an enrollment system that may represent a tile in a tile chain. Additionally or alternatively, a time value may be determined that indicates a time and/or date at which the document obfuscation value and/or other information described herein was registered with the blockchain. The blockchain system may then send the encrypted document obfuscation value to an enrollment system associated with the trade secret registry. The blockchain system may additionally or alternatively send an encrypted document obfuscation value to the client-side device, particularly if request data is received from the client-side device to register the document obfuscation value.

The enrollment system may generate a record in a trade secret registry. The record may include information associated with the trade secret. For example, a record may include data indicating an identifier of the record, a naming indicator associated with a business secret, a description of the business secret, a naming indicator associated with a document, one or more tags associated with the business secret, a status indicator of the business secret, a document obfuscation value, a block number associated with a block of a chain of blocks in which the document obfuscation value is registered, an encrypted document obfuscation value, a time value, and/or one or more other types of data associated with registration of the business secret and/or the business secret, such as an estimate, policy information, versioning information, and so forth. In an example, the registration system may generate confirmation data indicating that the record has been generated, and may transmit the confirmation data to the client-side device and/or system for display via the user interface.

Additionally or alternatively, the enrollment system may be configured to identify, determine, and/or generate one or more tokens of the undisclosed business secret. For example, a user of the registration system may provide information and/or documents indicating that a trade secret has not been disclosed. In an example, the client-side device may be configured to analyze documents and/or information corresponding to the trade secret, and may be configured to perform a search of publicly available databases and/or resources (such as internet browsing and/or search resources) to determine whether information and/or documents corresponding to the trade secret have been disclosed. If the client-side device and/or the registration system determines that the trade secret has not been disclosed, the registration system may record such an undisclosed token. In an example, these indicia can be used for insurance applications and/or offerings and/or for legal instruments.

Additionally or alternatively, the enrollment system may be configured to determine whether a document to be enrolled with the trade secret registry is unique relative to other documents enrolled with the trade secret registry. For example, the registration system may compare the document obfuscation value to one or more other document obfuscation values representing other documents registered with the trade secret registry. The registration system may determine that the document is not unique if the document obfuscation value is the same as at least one other registered document obfuscation value. In other examples, a similarity between the document confusion value and the registered document confusion value may be determined, and if the similarity is greater than a threshold similarity, the document may be determined not to be unique.

Additionally or alternatively, a comparison of the document obfuscation value to be registered with the registered document obfuscation value may be used to determine whether the document associated with the business secret registry is a different version of the same document, such as, for example, a different version of the source code. For example, the registration system may determine that a similarity between two document confusion values is greater than a threshold similarity. Additionally, in an example, the registration system may determine that the entity identifiers indicating the entities associated with the documents are the same. In these and other examples, the registration system may determine that two documents are different versions of the same document. The registration system may provide an indication of the determination to the client-side device and/or system. Additionally or alternatively, the registration system may generate a record of the document to be registered and may associate the record with a record of the registered document. The selectable link may be associated with a record such that upon selection of the link via the user interface, the associated record may be displayed.

In an example, the functionality described herein may be provided, at least in part, via a user interface. The user interface may include one or more selectable portions that, when selected, may cause the one or more processors to perform the operations described herein. For example, the user interface may include a selectable portion that indicates an option to register the trade secret in association with the trade secret registry, enables a user to select and/or identify a document corresponding to the trade secret, enables a user to view a record of the trade secret registry, enables a user to obtain and/or view information associated with an insurance policy for the trade secret, enables evaluation of the trade secret, enables entry of text to generate tag data, enables search of records associated with the trade secret registry and/or records associated with an entity, enables verification that a document is registered with respect to the trade secret registry, and/or displays a link and/or association between records.

Additionally or alternatively, the enrollment system may be configured to determine the value of the trade secret and/or record information related to such valuations. For example, during and/or after registration of the trade secret with the trade secret registry, an option to determine the value of the trade secret and/or to record information related to such valuations may be displayed, such as via a user interface of the client-side device and/or system. One or more dialog boxes and/or input fields may be caused to be displayed, and the dialog boxes may request information associated with the trade secret to assist in evaluating the trade secret. For example, such information may include the type of trade secret, the importance of the trade secret to the entity, the entity's revenue and profits (including revenue and profits generated, among other things, by the entity using the trade secret), the cost of developing the trade secret, the entity's value, the trade secret creation date, the expected life of the trade secret, and so forth. Additionally, in an example, the input field may include a request for a support document that includes information that may be related to an evaluation of the business secret. In these examples, the user may identify the supporting document. A document obfuscation value may be generated for a given support document and/or the support document and/or document obfuscation value may be registered in association with the blockchain. The record of the business secret may include information associated with the support document, such as a corresponding document obfuscation value and/or an encrypted document obfuscation value corresponding to a tile in a blockchain in which the support document is registered. The enrollment system may utilize some or all of this information to generate a value associated with the business secret.

Additionally or alternatively, the registration system may be configured to utilize access controls to restrict access to certain records and/or portions of records. For example, the access control data may be stored in association with the registration system. The access control data may indicate who is authorized to view a given record and/or given information associated with the record. In these examples, for example, a user accessing the record may need to authenticate the user's identity, such as by entering a username and/or password, and may need to confirm and determine the sensitive nature of the record and the user obligations associated with the access. Thus, the registration system may generate an access log that may indicate a user identifier of the user accessing a given record, a time value associated with the access of the record, and/or which information the user displayed and/or manipulated. The access log may be used by the registration system to assist in maintaining confidentiality and/or confidentiality of the business secret. For example, an alert may be generated and/or sent upon accessing the record and/or upon detecting abnormal activity. In other examples, when a user leaves a company, the access records may be used to determine which sensitive information the user viewed and which privacy obligations should be reminded to the departing user. In other examples, such as when a trade secret is associated with an insurance policy, the access log may be used to satisfy one or more conditions of the insurance policy, such as, for example, periodic reminders about confidentiality for users who accessed the record.

The present disclosure provides an overall understanding of the principles of the structure, function, manufacture, and use of the systems and methods disclosed herein. One or more examples of the present disclosure are illustrated in the accompanying drawings. Those of ordinary skill in the art will understand that the systems and methods specifically described herein and illustrated in the accompanying drawings are non-limiting embodiments. Features illustrated or described in connection with one embodiment may be combined with features of other embodiments, both as systems and methods. Such modifications and variations are intended to be included herein within the scope of the appended claims.

Additional details are described below with reference to several exemplary embodiments.

FIG. 1 shows a schematic diagram of an exemplary architecture 100 for digital property authentication and management. The architecture 100 may include, for example, one or more client-side devices, also described herein as electronic devices 102, that allow clients to register and manage their trade secrets or other intangible assets or digital assets. The architecture 100 includes a first or trade secret enrollment system 104 associated with a trade secret enrollment office that is remote from, but in communication with, the client-side electronic device. The architecture 100 also includes a second or distributed ledger system 106 that is remote from, but in communication with, the client-side device 102 and the trade secret registry 104. The distributed ledger system 106 utilizes blockchain techniques to accept entries, such as document obfuscation values associated with a trade secret or other digital asset registered with a trade secret registry, in a secure, verifiable manner. The architecture also has an insurer system 108, which may also be described herein as a third remote system associated with the insurer. The insurer system 108 can utilize information from the check-in system 104 and/or the distributed ledger system 106, for example, to issue insurance policies associated with the trade secrets and/or other digital assets registered by the trade secret registry. Some or all of the devices and systems may be configured to communicate with each other via network 110.

The electronic device 102 may include components such as, for example, one or more processors 112, one or more network interfaces 114, and/or memory 116. The memory 116 may include components such as, for example, one or more obfuscation components 118, a tag data generator 120, a communication component 122, a firewall 124, and/or one or more user interfaces 126. As shown in fig. 1, the electronic device 102 may include, for example, a computing device, a mobile phone, a tablet, a laptop, and/or one or more servers. The components of the electronic device 102 will be described below by way of example. It should be understood that the examples provided herein are illustrative and should not be considered as the only examples of components of the electronic device 102.

For example, the user interface 126 may include a selectable portion that, when selected, may identify a document that represents a trade secret. For example, the selectable portion and/or another portion of the user interface 126 may include text requesting that a user of the user interface 126 select the selectable portion to identify a document that includes information to be registered as a trade secret in association with a trade secret registry. The user may provide input to the electronic device 102 indicating information and/or documents to be registered as a trade secret. The input may include selecting a naming designator for the document.

The obfuscation component 118 may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic apparatus 102 and/or a remote storage device accessible to the electronic apparatus 102. The obfuscation component 118 may then generate a document obfuscation value corresponding to the document. The obfuscation component 118 may also be described herein as a hash function and may be configured to map data of any size to data of a fixed size. Document obfuscation values may also be described herein as hash codes, digests, and/or hashes. The hash function may utilize one or more algorithms to generate the document obfuscation value. The algorithm may include, for example, a trivial hash function, a perfect hash, a minimum perfect hash, hashing evenly distributed data, hashing scattered data with other distributions, hashing variable length data, a specialized hash function, a rolling hash, a universal hash, hashing with a checksum function, a multiplicative hash, a non-linear look-up table hash, an efficient hash of a string, and/or one or more other hashing algorithms. In general, the obfuscation component 118 may receive as input text data, image data, formatting data, and/or other data corresponding to a document, and may generate as output a document obfuscation value corresponding to the input. In an example, the electronic device 102 may include multiple obfuscation components, each employing a different hashing algorithm. In these examples, each obfuscation component may output a different document obfuscation value for the same document.

The tag data generator 120 may be configured to generate tag data associated with a document. For example, one or more input fields may be caused to be displayed via user interface 126. The input field may include a request to "tag" or otherwise provide a keyword for the document. For example, a document corresponding to source code for operating a sewing machine may be associated with a keyword such as "source code", "sewing machine", "version 1.1.20", and the like. A user of the electronic device 102 can input text corresponding to the tags, and the tag data generator 120 can utilize such input to generate tag data. Additionally or alternatively, the tag data generator 120 may automatically generate the tag data. For example, the tag data generator 120 may analyze a document to be registered in association with a trade secret registry to identify keywords associated with the document. For example, the tag data generator 120 may identify one or more fields of the document and/or values associated with the fields. Illustratively, the tag data generator 120 may identify a title field, a document type field, one or more sections of a document, and/or the like. The values associated with these fields (such as text data) may be used to generate the tags. Additionally or alternatively, the text data of the document may be analyzed to determine which words in the document are common, where the user can examine, edit, and/or delete the determined words, for example to ensure that particularly sensitive terms (e.g., important elements of a commercial secret compound) are not further processed. These words may be recognized as keywords and may be used to generate tag data.

The communication component 122 can be configured to enable communication between the electronic device 102 and other components of the architecture 100, such as the check-in system 104, the distributed ledger system 106, and/or the insurer system 108. The communications component 122 can also generate data to be transmitted and/or can format already generated data for transmission to one or more of the remote systems. The communications component 122 may also be configured to receive data from one or more of the remote systems.

The firewall 124 may be configured to receive data from the communication component 122 and/or from one or more other components of the electronic device 102. The firewall 124 may be described as a network security system that may monitor and/or control incoming and outgoing data based on security rules. The security rules may indicate that the electronic device 102 is configured to send certain data to the check-in system 104 and/or the distributed ledger system 106 and/or the insurer system 108. The security rules may also indicate that the electronic device 102 is configured to receive certain data from the check-in system 104 and/or the distributed ledger system 106 and/or the insurer system 108. For example, the security rule may indicate that the electronic device 102 is allowed to send document obfuscation values to the registration system 104, but is not allowed to send documents to the registration system 104. The firewall 124 may be used to control the distribution of sensitive information, particularly when the architecture 100 is used to register confidential documents with a trade secret registry.

Registration system 104 may include components such as, for example, one or more processors 128, one or more network interfaces 130, and memory 132. The memory 132 can include components such as, for example, one or more obfuscation components 134, tag data generator 136, communication component 138, record generator 140, trade secret registry 142, comparison component 144, grouping component 146, evaluation component 148, policy component 150, one or more wizards 152, verification component 154, trade secret classifier 156, linking component 158, access database 160, access control component 162, and/or version control component 164. The following description will proceed, by way of example, to describe the components of the registration system 104. It should be understood that the examples provided herein are illustrative and should not be considered the only examples of components of the registration system 104. It should be understood that when systems and/or devices are described herein as "remote systems" and/or "remote devices," the systems and/or devices may be located in a different location than, for example, electronic device 102.

For example, the obfuscation component 134 may perform the same or similar operations as the obfuscation component 118 of the electronic device 102. For example, the registration system 104 can generate one or more document obfuscation values using the obfuscation component 134 instead of or in addition to the electronic device 102 using the obfuscation component 118. In these examples, the electronic device 102 may send data corresponding to the document representing the business secret to the registration system 104. The registration system 104 can receive the data and can utilize the data to generate a document obfuscation value via an obfuscation component 134. The document obfuscation value may be generated in the same or similar manner as the document obfuscation value generated by the obfuscation component 118. In an example, the enrollment system 104 may include a plurality of obfuscation components 134, each employing a different hashing algorithm. In these examples, each obfuscation component 134 may output a different document obfuscation value for the same document. Each of these document obfuscation values may be sent to a different blockchain system for registration, as described elsewhere herein.

In an example, a document may be segmented and a document obfuscation value may be generated with each segment regardless of where the hashing is performed in the system. For example, two or more portions of a document may be identified and/or determined and a document obfuscation value may be generated for each portion. To illustrate, the document may be partitioned into four portions and the obfuscation component 134 may generate a document obfuscation value for each of the four portions. The obfuscation component 134 may then utilize the four document obfuscation values to generate a document obfuscation value for the document.

The tag data generator 136 may perform the same or similar functions as the tag data generator 120 described with respect to the electronic device 102. For example, enrollment system 104 may receive input data indicative of one or more tags associated with a given business secret. Additionally or alternatively, the registration system 104 may utilize data representative of the document to generate tag data, such as described above with respect to the electronic device 102. Registration system 104 may also generate tag data reflecting additional processing performed by the system. In an example, the tag data can be used for a search function. In these examples, a search may be requested for one or more records associated with the trade secret registry 142. The search may include text data representing terms to be searched, and the text data may be used by the registration system 104 to search at least the tag data for the same or similar terms. The search results may be returned to the electronic device 102 for display, such as via the user interface 126. Additionally or alternatively, the user interface 126 may display the tags generated by the tag data generator 136. The user interface 126 may also display selectable portions that, when selected, may allow a user to manipulate and/or alter the tabs.

The communication component 138 can be configured to enable communication between the check-in system 104 and other components of the architecture 100, such as the electronic device 102, the distributed ledger system 106, and/or the insurer system 108. The communications component 138 can also generate data to be communicated and/or can format already generated data for transmission to other components of the architecture 100. The communication component 138 may also be configured to receive data from one or more of the other remote systems and/or the electronic device 102.

For example, the communication component 138 can be configured to generate request data indicating a request to register a business secret in association with a blockchain (such as a blockchain associated with the distributed ledger system 106). The request data may be sent to the distributed ledger system 106, for example, along with a document obfuscation value, and/or an identifier of the document and/or the trade secret, and/or other information associated with the document and/or the trade secret. The distributed ledger system 106 can receive request data and document obfuscation values (or other data) and can register document obfuscation values (or other data) in association with tiles of the blockchain. The distributed ledger system 106 can generate an encrypted document obfuscation value that represents a tile in the blockchain and/or the distributed ledger system 106 can generate a time value that indicates a time and/or date at which the document obfuscation value (or other data) was registered with the blockchain. The distributed ledger system 106 can send encrypted document obfuscation values, time values, and/or other information (such as, for example, block numbers) to the registration system 104 and/or the electronic device 102.

As used herein, a blockchain is a list and/or ledger of records that are linked using cryptography, also described as a block. A chunk in the blockchain contains the cryptographic hash of the previous chunk, a time value or timestamp, and, in an example, transaction data. The blockchain may be used to record transactions between two entities and/or systems. In these examples, the blockchain may be used to record transactions between the electronic device 102 and the enrollment system 104 that enroll the trade secret at the trade secret enrollment. As described in more detail elsewhere herein, blockchains may also be used to register valuation documents, insurance policy documents, and/or other information associated with a trade secret registry. The blockchain may be managed by a peer-to-peer network that collectively adheres to protocols for inter-node communication and validates new blocks. Once recorded in a block, the data cannot be changed without changing all subsequent blocks, which would require consent by most people of the network.

In an example, a plurality of blockchain systems may be utilized to register transactions between the registration system 104 and the electronic device 102. For example, a document obfuscation value may be sent to multiple blockchain systems, and each blockchain system may return encrypted document obfuscation values corresponding to the tiles in its respective blockchain. As described more fully below, the record indicating that the commercial secret was registered with the commercial secret registry 142 may include a plurality of encrypted document obfuscation values and/or other information associated with registering the tile in a plurality of tile chains.

The record generator 140 of the enrollment system 104 may then generate a record in the trade secret registry 142. For example, a record may include an identifier of the record, a naming indicator of a business secret, a description of the business secret, a naming indicator of a document, one or more tags, a status identifier of the record, a document obfuscation value, an encrypted document obfuscation value, a block number, a time value (also described as a block timestamp), insurance policy details, valuation details, and/or other information associated with the business secret. The record may be stored in the trade secret registry 142 along with one or more other records. In an example, the registration system 104 may generate confirmation data indicating that the record has been generated, and may transmit the confirmation data along with the record itself to the electronic device 102 for display via the user interface 126. In an example, an audit of access and/or edit history associated with a record may be performed such that if a user interacts with the record, data indicating the user's interaction with information associated with the record may be displayed and/or reported. In addition, audit logs and/or data can be logged to the distributed ledger to verify when an audit is performed.

In an example, the trade secret registry 142 may be searchable. For example, an interface may be generated and configured to allow access to at least a portion of the trade secret registry 142 via the electronic device 102 and/or a remote archiving system associated with other intellectual property assets. As described more fully herein with respect to the access control component 162, the access information may be sent for accessing the interface. Registration system 104 may receive a request to perform a search of a trade secret registry 142, such as from a remote archiving system. In these examples, the request may include text data for searching the trade secret registry 142. The text data may be used to identify results of the search, and result data representing the results may be transmitted to the remote archiving system and/or the electronic device 102.

The comparison component 144 may be configured to analyze the document confusion value and determine a similarity and/or a difference between the document confusion value and/or the documents corresponding to the document confusion value. For example, as described above, the obfuscation component 134 may generate a document obfuscation value corresponding to a document representing a business secret. Similar documents may have similar document confusion values. Accordingly, the comparison component 144 can analyze the document obfuscation values to determine a similarity therebetween. A threshold similarity may be identified and/or determined and the similarity between document confusion values may be compared to the threshold similarity. Document confusion values with a similarity that meets or exceeds a threshold similarity may be determined to be similar, while hash value pairs below the threshold similarity may be determined to be dissimilar. Additionally, the document obfuscation value may be segmented and the segments may be compared to determine similar and dissimilar portions of the document obfuscation value. The number of similar and dissimilar document confusion values may be used to determine an overall similarity between the document confusion values.

In other examples, the comparison component 144 may associate the feature vector with some or all of the document obfuscation values. The feature vector may correspond to a document obfuscation value and/or a characteristic of the document. For example, the presence or absence of text data and/or image data from a document may affect the feature vectors. In other examples, the text data and/or the image data itself may affect the feature vectors. Other factors such as the length of the document, the entity associated with the document, the type of information contained (e.g., source code, chemical formula, customer listing), creation date, modification date, and/or other metadata may affect the feature vector. For example, a feature may be described as an individual measurable property or characteristic of a document. The given feature may be a number and/or may be considered a string and/or a graphic. A set of such features may be described as a feature vector. Thus, similar feature vectors indicate similar characteristics and/or properties of the documents they represent. A similarity and/or popularity score may be determined for a given pair of feature vectors, with a better score indicating a high degree of similarity between documents.

In other examples, comparison component 144 may utilize a Levenshtein distance to determine a similarity between the trade secrets. A levens distance between two document confusion values and/or documents may be determined. A shorter levenstein distance may indicate more similarity than a longer levenstein distance. As used herein, the levenstein distance (also referred to as the edit distance) can be described as a string metric for measuring the difference between two sequences. For example, the levenstein distance between two words may be considered the minimum number of single character edits to change one word to another. Thus, the levens distance between two very similar words will be shorter than the levens distance between two very different words. In these examples, a lewy distance between two documents and/or two document obfuscation values representing the documents may be determined, with a shorter lewy distance indicating more similarity between documents.

The comparison component 144 may also be configured to determine whether the commercial secret to be enrolled is unique relative to other commercial secrets enrolled in association with the commercial secret enrollee 142. For example, document obfuscation values and/or documents may be analyzed as described herein to determine whether a given document obfuscation value differs from one or more stored document obfuscation values associated with registered business secrets. If the document obfuscation values are different, the business secret to be enrolled may be identified or determined to be unique relative to other business secrets associated with the business secret registry 142. In an example, determining that the document confusion value differs from the stored document confusion value may include determining a similarity between the document confusion values and determining that the similarity does not exceed a threshold similarity.

The grouping component 146 can be configured to group records and/or document obfuscation values corresponding to documents. For example, grouping component 146 can utilize results from comparison component 144 to determine whether to group two or more records, document obfuscation values, and/or documents. For example, documents with a certain degree of similarity may be grouped together. The document group may also be grouped with other document groups based at least in part on the results from the comparison component 144. Additionally or alternatively, the grouping component 146 can receive an indication that an identifier of the electronic device 102 and/or the entity is the same across multiple documents and/or records. In these examples, grouping component 146 can associate records with the same entity and/or device identifier with each other. In other examples, grouping component 146 can group records that have a common entity and/or device identifier and meet or exceed a threshold degree of similarity.

The evaluation component 148 can be configured to identify and/or determine a value associated with a given business secret. For example, during and/or after registration of the trade secret with the trade secret registry 142, an option to determine the value of the trade secret or otherwise save information related to the valuation may be displayed, such as via the user interface 126 of the electronic device 102. One or more dialog boxes and/or input fields may be caused to be displayed, and the dialog boxes may request information associated with the trade secret to assist in evaluating the trade secret. For example, such information may include the type of trade secret, the importance of the trade secret to the entity, the entity's revenue and profits (including revenue and profits generated, among other things, by the entity using the trade secret), the cost of developing the trade secret information, the entity's value, the trade secret creation date, the expected life of the trade secret, and so forth.

Additionally, in an example, the input field may include a request for a support document that includes information that may be related to an evaluation of the business secret. In these examples, the user may identify the supporting document. A document obfuscation value may be generated for a given support document and/or the support document and/or document obfuscation value may be registered in association with the blockchain. The record of the business secret may include information associated with the support document, such as a corresponding document obfuscation value and/or an encrypted document obfuscation value corresponding to a tile in a blockchain in which the support document is registered.

In other examples, tag data generated as described herein may be used to determine some or all of the data described herein for determining the value of a business secret. For example, the tag data may be used to determine a type of commercial secret. Business secrets of the same or similar type may be analyzed to determine the value of the business secret in question. The remote system 104 may utilize some or all of this information to generate a value associated with the business secret.

For example, the business secret may be identified and/or determined to be the source code and may be indicated as being very valuable to an entity associated with the source code. The input data received from the electronic device 102 may indicate that the value of the entity is $ 5,000,000 and the annual income of the entity is $ 1,500,000. The profit generated by the use of trade secrets is $ 400,000 per year. The development cost of the trade secret is $ 1,000,000. The life expectancy of the trade secret is 10 years. Additionally, the entity may have uploaded a document to confirm some or all of the information. Based at least in part on this information, evaluation component 148 can determine the value of the trade secret. In an example, a cash flow posting analysis of attributable profit flows over an expected lifetime may be determined. Comparisons can be made with estimates of other registered business secrets, such as other source codes identified as important, and with corporate statistics similar to that identified for the entity. Development costs may be considered. These alternatives can be combined to produce the current and projected estimate ranges. In an example, the evaluation component 148 can set one or more guardrails and/or limits on the value of the trade secret. For example, if the total value of an entity is $ 5,000,000, a limit may be set where the value of the trade secret cannot exceed $ 5,000,000. Additionally or alternatively, data may be used to affect an evaluation of the trade secret, the data indicating that the trade secret has been enrolled with the trade secret enrollee 142, licensed to a third party, insured by an underwriter, and/or made more valuable as reflected by updates to information associated with the trade secret by the user since the enrollee was first established.

In other examples, quantitative analysis of one or more factors may be used for the evaluation. For example, factors such as the industry of interest, the type of information, the scope of intellectual property, the duration of intellectual property, the specificity and/or uniqueness of intellectual property, the degree and/or measure of privacy implemented, the reproducibility of intellectual property, the likelihood of theft, the detectability and/or theft of trade secrets, and/or overlap with other intellectual property and/or known assets. Other information may also be utilized, such as the geographic extent of intellectual property. Values corresponding to these factors may be identified, determined, and/or generated, and may be used to determine the value of the business secret, as for example, via a machine learning algorithm.

The policy component 150 may be configured to assist in applying, underwriting, and providing one or more policies for a given trade secret. For example, upon registering with the trade secret registry 142, an option to obtain an insurance scope for the trade secret may be presented. For example, a selectable portion of the user interface 126 may provide an option to apply for an insurance policy. When selected, the user interface 126 may display one or more dialog boxes and/or input fields configured to receive user input regarding applying for an insurance policy. This information may include, for example, information related to the applicant, the type or category of trade secret, the value of the trade secret (determined from above or identified by the user), the expected warranty period, the expected warranty restrictions and reservations, the entity value, the date of creation of the trade secret, and/or the portion of the document that enables the upload of the support document and/or the requested document. In an example of providing a support document, the support document may be registered with the blockchain in the same or similar manner as described above with respect to the support document for business secret valuation.

The policy component 150 and/or the communication component 138 can be configured to receive input data corresponding to user input and can transmit the input data to an insurer system 108 associated with the insurer. The insurer system 108 can process the input data and in an example underwrite and/or issue a policy, for example, to ensure that trade secrets are not stolen. In these examples, confirmation data indicating that the policy has been issued and information associated with the policy may be received from the insurer system 108. This information may be incorporated into a record associated with the trade secret and may be displayed via user interface 126 in an example. Some non-limiting examples of information associated with a policy may include a policy type, an obligation limit, a reserve value, a policy premium, a policy form, a policy number, a policy life, an obligation share limit, and/or an estimate of a trade secret. Additionally or alternatively, the information may include one or more payment values associated with amounts to be paid to the entity associated with the business secret upon the occurrence of different categories of events, including different levels of unauthorized access or use. In these examples, the policy component 150 may receive non-compliance data indicating that the entity is not in compliance with the conditions of the insurance policy and may cause display of updated insurance policy information, including an indication that a therapeutic action is required and/or an updated payment value. In these examples, the updated payment value may be less than the original payment value. When the condition is satisfied, the payment value may be updated to reflect compliance with the policy condition.

In an example, one or more intelligent contracts can be used in association with policy component 150. For example, an insurance policy may be associated with a given business secret using an intelligent contract associated with the blockchain. As described herein, an intelligent contract may be a computer protocol that digitally facilitates, validates, and/or enforces the negotiation and/or fulfillment of a contract. Transactions involving smart contracts may be traceable and irreversible. Intelligent contracts may utilize, for example, a byzantine fault tolerance algorithm that may enable digital security through decentralization of contracts. The intelligent contracts may be initiated, hosted, and/or implemented at least in part by the distributed ledger system 106 associated with the blockchain. In these examples, the smart contract may indicate conditions for validating the insurance policy, such as a continued investment by the sponsor in numerical threshold levels and/or physical security, and may receive validation data indicating that the conditions have been met. In these examples, the validation data may be sent to the distributed ledger system 106, which may cause the intelligent contract to validate the insurance policy.

The wizard 152 described herein may be a set of dialog boxes and/or input fields configured to be displayed, such as via the electronic device 102. For example, wizard 152 may be utilized to receive user input for commercial secret valuation determination or support. Additionally or alternatively, the wizard 152 may be used to receive user input for insurance policy application, underwriting, and offering. In examples where the wizard 152 is used to provide an insurance policy, the wizard 152 and/or information associated with the wizard 152 may be provided by and/or may be specific to a given insurer. Additionally or alternatively, the wizard 152 may be utilized to submit notifications of potential theft events and/or insurance claims, as described more fully herein.

The verification component 154 may be configured to verify that information contained in a particular document has been registered with the trade secret registry 142. For example, once registered, the verification component 154 can be used to determine whether other information (such as information that is purportedly stolen) matches or is similar to information contained in the registered document and/or verify that other information (such as information that is purportedly stolen) matches or is similar to information contained in the registered document. In these examples, the stolen information (e.g., in the form of a directed document) may be identified, such as via the user interface 126 of the electronic device 102, as part of the user authentication request. Document obfuscation values may be generated for the directed document in the same or similar manner as described above with respect to the obfuscation components 118, 134. The verification component 154 can be used to analyze the document confusion value of the commanded document relative to other document confusion values of registered documents or document segments. If the verification component 154 determines that at least one of the registered document obfuscation values matches the document obfuscation value of the directed document or document segment, the verification component 154 may determine that the directed document is the same as or similar to the registered document or document segment. In other examples, verification component 154 can determine a similarity between the commanded document and one or more registered documents. Determining the similarity may be performed as described above with respect to comparing component 144. In these examples, the directed document may be determined to be similar to the registered document when the similarity meets or exceeds a threshold similarity. In other examples, the verification component 154 can be configured to determine which portions of the indexed document match or are similar to at least one registered document. An indication of the matching or similar portion may be displayed, such as via user interface 126. Additionally, where multiple versions of a document have been registered, the verification component 154 may be configured to determine which of the multiple versions is most similar to the commanded document, and may provide an indication of the most similar version.

Commercial secret classifier 156 may be configured to determine the type and/or classification of a commercial secret being and/or having been registered. For example, input data received from the electronic device 102 that indicates one or more properties of a given commercial secret may be used by the commercial secret classifier 156 to determine the type of commercial secret. In other examples, tag data may be received, identified, determined, and/or generated as described elsewhere herein. The tag data may be used to determine the type of commercial secret. Additionally or alternatively, the results of comparison component 144 can be utilized to determine the type of trade secret. For example, a match of similar registered trade secrets may be utilized to determine the trade secret type for a given trade secret. For example, determining the type of business secret may be useful for one or more of the operations described elsewhere herein, such as for grouping, valuation, insurance policy provisioning, wizard display, record linking, and document version determination.

The linking component 158 can be configured to associate one record with one or more other records of the trade secret registry 142. For example, the link component 158 can be utilized to generate associations between records when the records are determined to be different versions of the same document and/or when the records are associated with the same entity identifier. Generating the association may include storing data indicating that the records are associated. Generating the association may also or alternatively include generating a link or other similar functionality that may be displayed with the record via the user interface 126. For example, the link may correspond to a selectable portion of the user interface 126 that, when selected, may cause the display of the linked record and/or a portion thereof.

The access database component 160 can be configured to store data indicating details of accessing one or more records associated with the trade secret registry 142. For example, the access control data may be stored in association with the registration system 104. The access control data may indicate who is authorized to view a given record and/or given information associated with the record. In these examples, for example, the access control component 162 may be configured to require the user to authenticate the user's identity for accessing the record, such as by entering a username and/or password. Thus, the registration system 104 may generate an access log that may indicate a user identifier of the user accessing a given record, a time value associated with the access of the record, and/or what information the user displayed and/or manipulated. The access log may be used by registration system 104 to assist in maintaining confidentiality and/or confidentiality of business secrets. For example, an alert may be generated and/or sent upon accessing the record and/or upon detecting abnormal activity. In other examples, when a user leaves a company, the access records may be used to determine which sensitive information the user viewed and which privacy obligations should be reminded to the departing user. In other examples, such as when a trade secret is associated with an insurance policy, the access log may be used to satisfy one or more conditions of the insurance policy, such as, for example, periodic reminders about confidentiality for users who accessed the record. It should be appreciated that the systems and/or user interfaces described herein may be used to assist in auditing the confidentiality of maintaining business secrets and/or to comply with policies and/or rules associated with business secret maintenance, such as for insurance policy purposes. Predetermined, periodic, and/or random alerts may be sent to devices associated with the entity registering the given business secret. The reminder may request that certain tasks be performed and/or that certain information be verified to comply with such policies and/or rules. Additionally or alternatively, the user interfaces described herein may provide functionality that allows a user of the device to display the user interface to identify one or more priority layers that may otherwise be described as priority levels to associate with a given business secret. For example, if a user specifies a business secret with a high priority level, certain operations may be prohibited, access control may be more stringent, security measures may be more robust, and/or a given unpublished protocol (which may be an informal and/or informal unpublished protocol) is identified, determined, and/or generated when the business secret is published. As another example, if a user specifies a business secret with a low priority layer, certain actions may be enabled that are not enabled for higher layers, access control may be less stringent than those for higher layers, and/or when the business secret is disclosed, a formal and/or standard undisclosed protocol may be identified, determined, and/or generated.

In the example of linking two records, access control data may be utilized to enable or disable access to the linked records and/or portions of the linked records, as described more fully with respect to linking component 158. For example, a given user may have been provided access to a first record instead of having linked a second record. In these examples, the first record may be displayed to the user, but the access control data may be utilized to avoid displaying the second record when the user attempts to select a portion of the user interface 126 corresponding to a link to the second record. In other examples, the user may have been authorized to access some information associated with the first record, but not authorized to access other information associated with the first record. Thus, only a portion of the first recording may be displayed to the user, while other portions of the recording may be edited, removed from display, or otherwise not displayed to the user.

Version control component 164 may be configured to determine that two or more documents and/or business secrets are versions of the same document and/or business secret. For example, as described more fully above, the results from comparison component 144 can be used to determine that two documents are similar but not identical in one or more respects. Version control component 164 may also receive, identify, determine, and/or generate information indicating that two documents are associated with the same and/or related entity identifiers. Version control component 164 may also receive, identify, determine, and/or generate information indicating that the two documents are associated with the same or similar types of business secrets. With some or all of this information, version control component 164 can determine that the two documents are versions of the same document. An indication of this version control may be stored relative to the record associated with the document and/or a visual indication may be displayed via user interface 126.

The version control component 164 may also be configured to generate alerts and/or reminders for document version control. For example, version control component 164 may determine that, for a given entity, a version of a particular business secret was enrolled at a given time historically and/or within a given time frame. If the version is not registered in a manner that is consistent with historical trends, an alert and/or reminder for registering the document version may be generated and sent to the electronic device 102. Additionally or alternatively, if a given trade secret is of a type that is typically registered in multiple versions at a given time and/or within a given time frame, version control component 164 may determine whether a version has been registered in a manner that conforms to the trend. If the version is not so registered, an alert and/or reminder may be generated and sent.

As shown in fig. 1, several components of the check-in system 104, the distributed ledger system 106, and/or the insurer system 108, and the associated functions of those components as described herein, can be performed by one or more of the other remote systems and/or by the electronic device 102. Additionally or alternatively, some or all of the components and/or functions associated with the electronic device 102 may be performed by the check-in system 104, the distributed ledger system 106, and/or the insurer system 108.

It should be noted that the exchange of such information can only be performed if the user agrees to exchange data and/or information as described herein. For example, a user may be provided with an opportunity to opt-in and/or opt-out of data exchange between devices and/or with a remote system and/or perform the functions described herein. Additionally, when one of the devices is associated with a first user account and another of the devices is associated with a second user account, user consent may be obtained prior to performing some, any, or all of the operations and/or processes described herein.

It should be understood that wherever the term "trade secret" is used in this disclosure, it should be noted that it includes not only trade secrets, but also any documents and/or data and/or information including confidential information, proprietary technology, and other information, and not necessarily documents, data, and/or information conforming to the legal definition of the term "trade secret".

As used herein, a processor (such as processor 112 and/or 128) may include multiple processors and/or processors with multiple cores. Further, a processor may include one or more cores of different types. For example, a processor may include an application processor unit, a graphics processing unit, and so on. In one implementation, the processor may include a microcontroller and/or a microprocessor. Processors 112 and/or 128 may include a Graphics Processing Unit (GPU), a microprocessor, a digital signal processor, or other processing units or components known in the art. Alternatively or additionally, the functions described herein may be performed, at least in part, by one or more hardware logic components. By way of example, and not limitation, illustrative types of hardware logic components that may be used include Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like. Additionally, each of processors 112 and/or 128 may include its own local memory, which may also store program components, program data, and/or one or more operating systems.

Memory 116 and/or 132 may include volatile and nonvolatile memory, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program elements, or other data. Such memory 116 and/or 132 includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, RAID storage systems, or any other medium which can be used to store the desired information and which can be accessed by a computing device. Memory 116 and/or 132 may be implemented as a computer-readable storage medium ("CRSM"), which may be any available physical medium that may be accessed by processors 112 and/or 128 to execute instructions stored on memory 116 and/or 132. In one basic implementation, the CRSM may include random access memory ("RAM") and flash memory. In other implementations, the CRSM may include, but is not limited to, read only memory ("ROM"), electrically erasable programmable read only memory ("EEPROM"), or any other tangible medium that can be used to store the desired information and that can be accessed by the processor.

Furthermore, the functional components may be stored in respective memories, or the same functions may alternatively be implemented in hardware, firmware, an application specific integrated circuit, a field programmable gate array, or as a system on chip (SoC). Further, although not shown, each respective memory discussed herein, such as memory 116 and/or 132, may include at least one Operating System (OS) component configured to manage hardware resource devices, such as network interfaces, I/O devices of the respective devices, and the like, and provide various services to applications or components executing on the processor. Such OS components may implement: a variant of the FreeBSD operating system as published by the FreeBSD project; other UNIX or UNIX-like variants; a variant of the Linux operating system distributed by Linus Torvalds; the FireOS operating system from Amazon. com, Seattle, Washington, USA; windows operating system from Microsoft corporation of Redmond, Washington, USA; such as LynxOS, distributed by Lynx Software Technologies, inc, san jose, california; such as the embedded operating system (ENEA OSE) published by ENEA AB, sweden, etc.

Network interfaces 114 and/or 130 can enable messaging between components and/or devices shown in architecture 100 and/or with one or more other remote systems and other networked devices. Such network interfaces 114 and/or 130 may include one or more Network Interface Controllers (NICs) or other types of transceiver devices to send and receive messages over the network 110.

For example, each of the network interfaces 114 and/or 130 may include a Personal Area Network (PAN) component to enable messages over one or more short-range wireless messaging channels. For example, the PAN component may enable messages that conform to at least one of the following standards IEEE 802.15.4(ZigBee), IEEE 802.15.1 (bluetooth), IEEE 802.11(WiFi), or any other PAN messaging protocol. Further, each of network interfaces 114 and/or 130 may include a Wide Area Network (WAN) component to enable messaging over a wide area network.

In some cases, the registration system 104 may be local to the environment associated with the electronic device 102. For example, the remote system 104 may be located within the electronic device 102. In some cases, some or all of the functions of the remote system 104 may be performed by the electronic device 102. Further, while various components of the remote system 104 have been labeled and named in this disclosure, and each component has been described as being configured to cause a processor to perform certain operations, it should be understood that the operations described may be performed by some or all of the components and/or other components not specifically illustrated.

FIG. 2 illustrates an exemplary user interface 202 displaying a trade secret enrollment function in accordance with the digital property authentication and management system. The user interface 202 may be displayed on a display of an electronic device, such as the electronic device 102 described with respect to fig. 1. The user interface 202 may be the same as or similar to the user interface 126 described with respect to fig. 1. Fig. 2 shows the progression from left to right and top to bottom of the information displayed on and/or interaction with the user interface 202.

For example, at step 1, the user interface 202 may include a first selectable portion 204 that indicates an option to enroll a trade secret at a trade secret registry. The user interface 202 may also include a second selectable portion 206 indicating options for managing the registered trade secret and/or a third selectable portion 208 indicating options for verifying that the document has been registered in association with the trade secret registry. To illustrate the use and functionality of the user interface 202, a user may provide an input indicating a selection of the first selectable part 204.

Selection of the first selectable part 204 may cause the user interface 202 to display, at step 2, a fourth selectable part 210 indicating an option for identifying a document representing a trade secret to be registered with the trade secret registry. For example, identification of the document may include input, such as a naming indicator of the document and/or selection of the document from a database of the electronic device displaying the user interface 202. The document can be identified and the electronic device can cause generation of a document obfuscation value corresponding to the document. For example, the obfuscation component may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic apparatus and/or a remote storage device accessible to the electronic apparatus. The obfuscation component may then generate a document obfuscation value corresponding to the document. In general, the obfuscation component may receive as input text data, image data, formatting data, and/or other data corresponding to a document, and may generate as output a document obfuscation value corresponding to the input. In an example, an electronic device may include a plurality of obfuscating components, each employing a different hashing algorithm. In these examples, each obfuscation component may output a different document obfuscation value for the same document.

At step 3, the user interface 202 may include a naming indicator 212 for the document. The user interface 202 may also include a document obfuscation value 214 generated based at least in part on the document. As shown in FIG. 2, for example, the document's naming designator 212 is "document 1" and the document obfuscation value 214 is "0 xaafede 662b084f7378f1ad91bfe08bdb34de1e801efb61103043fc62bd8963 f".

At step 4, the user interface 202 may include one or more dialog boxes and/or input fields 216 associated with the business secret. Input field 216 may include text requesting information about the trade secret from the user. As shown in FIG. 2, for example, input field 216 may request information such as a name of the trade secret, a description of the trade secret, and/or one or more tags of the trade secret. For example, a document corresponding to source code for operating a sewing machine may be associated with a keyword such as "source code", "sewing machine", "version 1.1.20", and the like. A user of the electronic device can input text corresponding to the tags, and the tag data generator can utilize such input to generate the tag data. Additionally or alternatively, the tag data generator may automatically generate the tag data. For example, the tag data generator may analyze a document to be registered in association with a trade secret registry to identify keywords associated with the document. For example, the tag data generator may identify one or more fields of the document and/or values associated with the fields. By way of illustration, the tag data generator can identify a title field, a document type field, one or more sections of a document, and/or the like. The values associated with these fields (such as text data) may be used to generate the tags. Additionally or alternatively, the text data of the document may be analyzed to determine which words are common in the document. These words may be recognized as keywords and may be used to generate tag data.

At step 5, the user interface 202 may display text indicating the status of the enrollment process and/or a description of the operations performed by a remote system, such as one associated with a trade secret enrollment and/or one associated with a blockchain. For example, the text may indicate that a transaction is pending and may indicate that a trade secret and/or document obfuscation value is being submitted to the blockchain. Upon displaying the text, the communication component may generate request data indicating a request to register the business secret in association with the blockchain. The request data may be sent to a remote system associated with the blockchain, for example, along with a document obfuscation value, and/or an identifier of the document and/or the trade secret, and/or other information associated with the document and/or the trade secret. The remote system may receive the request data and the document obfuscation value (or other data) and may register the document obfuscation value (or other data) in association with a tile of the blockchain. The remote system may generate an encrypted document obfuscation value representing a tile in the blockchain and/or the remote system may generate a time value indicating a time and/or date at which the document obfuscation value (or other data) was registered with the blockchain. The remote system may send the encrypted document obfuscation value, time value, and/or other information (such as, for example, block number) to a remote system associated with the trade secret registry.

In an example, a plurality of blockchain systems may be utilized to register transactions between a trade secret registration system and an electronic device. For example, a document obfuscation value may be sent to multiple blockchain systems, and each blockchain system may return encrypted document obfuscation values corresponding to the tiles in its respective blockchain. As described more fully below, the record indicating registration of the commercial secret with the commercial secret registry may include a plurality of encrypted document obfuscation values and/or other information associated with registering the tile in a plurality of tile chains.

At step 6, the user interface 202 may display a record indicating that the trade secret has been registered with the trade secret registry. The record may include a record identifier 218, trade secret details 220, and/or transaction details 222. Record identifier 218 may include a number and/or letter that identifies the record relative to the trade secret registry. For example, the business secret details 220 can include a naming designator for the business secret, a description of the business secret, a naming designator for a document representing the business secret, and/or a tag generated as described elsewhere herein. The transaction details 222 may include a status registered with the trade secret registry, a document obfuscation value, a block number associated with a block in which the trade secret is registered to the blockchain, an encrypted document obfuscation value (also described as a blockdocument obfuscation value), and/or a block timestamp. Other information that may be included in the record and displayed relative to the user interface 202 may include insurance policy details, valuation details, and/or other information associated with the trade secret, as described more fully elsewhere herein.

The record may be generated by a record generator of a remote system associated with the trade secret registry. The record may be stored in a trade secret registry with one or more other records. In an example, the remote system may generate confirmation data indicating that the record has been generated, and may transmit the confirmation data to the electronic device for display via the user interface 202.

FIG. 3 illustrates an exemplary user interface 302 displaying a trade secret maintenance function in accordance with the digital property authentication and management system. The user interface 302 may be displayed on a display of an electronic device, such as the electronic device 102 described with respect to fig. 1. The user interface 302 may be the same as or similar to the user interface 126 described with respect to fig. 1. Fig. 3 shows the progression from left to right and top to bottom of the information displayed on and/or interaction with the user interface 302.

For example, at step 1, the user interface 302 may include a first selectable portion 304 that indicates an option to enroll a trade secret at a trade secret registry. The user interface 302 may also include a second selectable portion 306 indicating options for managing the registered trade secret and/or a third selectable portion 308 indicating options for verifying that the document has been registered in association with the trade secret registry. To illustrate the use and functionality of the user interface 302, a user may provide an input indicating a selection of the second selectable part 306. It should be appreciated that, in an example, the first, second, and third

selectable portions

304, 306, 308 of the user interface 302 may be the same as or similar to (and may be functionally similar to) the first, second, and third

selectable portions

204, 206, 208 of the user interface 202 described with respect to fig. 2.

Selection of the second selectable part 306 may cause the user interface 302 to display, at step 2, information associated with a trade secret that has been enrolled in association with the trade secret enrolment. In an example, a commercial secret indicator 310 may be displayed. Commercial secret indicator 310 may include information describing and/or summarizing a given commercial secret. As shown in fig. 3, the information may include, for example, a name of the trade secret, a date the trade secret was registered in association with the trade secret registry, and/or a tag associated with the trade secret. In this manner, the trade secret indicator 310 provides an indication of the trade secret associated with the trade secret registry, and does not provide all of the information of each record of the trade secret in the example. In an example, the commercial secret indicator 310 may be limited to only those commercial secrets associated with a given entity and/or entity identifier. Additionally or alternatively, the trade secret indicator 310 may be limited to only those trade secrets that a user logged in with certain access credentials has access to view.

In an example, the trade secret indicator 310 may be selectable, and when selected, may cause a record associated with the trade secret indicator 310 to be displayed at step 3. As shown in fig. 3, the user may provide an input corresponding to a selection of "trade secret 1". Selection of the trade secret indicator may cause a record associated with "trade secret 1" to be displayed at step 3. As shown in fig. 3, the record may include the same or similar information as the record described with respect to fig. 2, including a record identifier, trade secret details, and/or transaction details.

In addition to the details of the above-described display, the trade secret indicator 310 and/or record may include a link 312 to one or more other records associated with the trade secret registry. For example, the linking component can be configured to associate one record with one or more other records in the trade secret registry. For example, when records are determined to be different versions of the same document and/or when records are associated with the same entity identifier, a linking component can be utilized to generate an association between the records. Generating the association may include storing data indicating that the records are associated. Generating the association may also or alternatively include generating a link 312 or other similar functionality that may be displayed with the record via the user interface 302. For example, link 312 may correspond to a selectable portion of user interface 302 that, when selected, may cause display of the linked record and/or a portion thereof.

FIG. 4 illustrates an exemplary user interface 402 displaying a trade secret verification function in accordance with the digital property authentication and management system. The user interface 402 may be displayed on a display of an electronic device, such as the electronic device 102 described with respect to fig. 1. The user interface 402 may be the same as or similar to the user interface 126 described with respect to fig. 1. Fig. 4 illustrates a left-to-right progression of information displayed on and/or interaction with the user interface 402.

For example, at step 1, user interface 402 may include a first selectable portion 404 that indicates an option to enroll a trade secret at a trade secret registry. The user interface 402 may also include a second selectable portion 406 indicating options for managing the registered trade secret and/or a third selectable portion 408 indicating options for verifying that the document has been registered in association with the trade secret registry. To illustrate the use and functionality of the user interface 402, a user may provide an input indicating a selection of the third selectable part 306.

Selection of the third selectable portion 306 may cause the user interface 302 to display a fourth selectable portion 410 at step 2 that indicates an option for identifying, for example, a compromised document. In these examples, the document may be obtained from a third party who may be compromised or otherwise obtain the trade secret without permission. For example, identification of the commanded document may include input, such as a naming designator for the document and/or selection of the document from a database of the electronic device, for example, displaying the user interface 402. The document can be identified and the electronic device can cause generation of a document obfuscation value corresponding to the document. For example, the obfuscation component may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic apparatus and/or a remote storage device accessible to the electronic apparatus. The obfuscation component may then generate a document obfuscation value corresponding to the document. In general, the obfuscation component may receive as input text data, image data, video data, formatting data, and/or any other data corresponding to documents and/or files that represent business secrets, and may generate as output a document obfuscation value corresponding to the input. In an example, an electronic device may include a plurality of obfuscating components, each employing a different hashing algorithm. In these examples, each obfuscation component may output a different document obfuscation value for the same document.

At step 3, user interface 402 may display verification status 412, similarity indicator 414, and/or identifier 416 that determines a registered business secret that matches and/or is similar to the commanded document. For example, the verification component may be configured to verify that a particular document has been registered with the trade secret registry. For example, once registered, the verification component can be used to determine whether another document (such as a document that has been compromised) matches or is similar to the registered document and/or verify that another document (such as a document that has been compromised) matches or is similar to the registered document. The verification component may be operative to analyze the document confusion value of the commanded document relative to other document confusion values of the registered documents. The verification component may determine that the directed document is the same as or similar to the registered document if the verification component determines that at least one of the registered document confusion values matches the document confusion value of the directed document. In other examples, the verification component may determine a similarity between the commanded document and one or more registered documents.

Determining similarity may be performed as described above with respect to comparing component 144 of fig. 1. In these examples, the directed document may be determined to be similar to the registered document when the similarity meets or exceeds a threshold similarity. In other examples, the verification component may be configured to determine which portions of the commanded document match or are similar to the at least one registered document. An indication of the matching or similar portion may be displayed, such as via user interface 402. Additionally, where multiple versions of a document have been registered, the validation component may be configured to determine which of the multiple versions is most similar to the commanded document, and may provide an indication of the most similar version.

As shown in the example in FIG. 4, verification status 412 is "document verified," indicating that the commanded document matches or is similar to at least one registered business secret. The similarity indicator 414 is "97% match with registered documents," indicating that the commanded document has a 97% similarity with at least one of the registered documents. It should be appreciated that the specific writing of verification status 412 and/or similarity indicator 414 is provided by way of example, and not by way of limitation. Other forms of verification status and/or similarity indicators may be provided. Additionally, although the similarities are expressed as percentages in fig. 4, other forms of describing the similarities are included in the present disclosure. Additionally, the identifier 416 of the registered business secret is "name: commercial secret 1 ". This may provide an indication to the user of the registered trade secret similar to the commanded document.

In an example, the user interface 402 can display a dialog box and/or input field that includes text associated with submitting an insurance coverage claim in association with an insurance policy for a trade secret. In these examples, one or more wizards may be launched to assist in proposing insurance coverage claims, given that claims or other legitimate claims of commercial secret theft may exist in view of the similarity between the commanded document and the registered commercial secret. Input data representing a response to the dialog box can be received, and the input data can be formatted and/or transmitted to a remote system associated with the insurer indicating that a claim is to be filed and/or that potential theft and/or other legitimate action is to be notified to the insurer based at least in part on receiving the input data.

FIG. 5 illustrates an exemplary user interface 502 displaying insurance policy functionality in accordance with the digital property authentication and management system. The user interface 502 may be displayed on a display of an electronic device, such as the electronic device 102 described with respect to fig. 1. The user interface 502 may be the same as or similar to the user interface 126 described with respect to fig. 1. Fig. 5 illustrates a left-to-right progression of information displayed on and/or interaction with user interface 502.

At step 1, the user interface 502 may display a record indicating the trade secret that has been registered with the trade secret registry. The record may include a record identifier 504, trade secret details 506, and/or transaction details 508. Record identifier 504 may include a number and/or letter that identifies the record relative to the trade secret registry. For example, the business secret details 506 may include a naming designator for the business secret, a description of the business secret, a naming designator for a document representing the business secret, and/or a tag generated as described elsewhere herein. The transaction details 508 may include a status registered with the trade secret registry, a document obfuscation value, a block number associated with a block in which the trade secret is registered to the blockchain, an encrypted document obfuscation value (also described as a blockdocument obfuscation value), and/or a block timestamp. Additionally, the user interface 502 may include a selectable portion 510 indicating options for applying for and/or obtaining an insurance policy associated with the trade secret.

At step 2, based at least in part on the selection of selectable portion 510, user interface 502 may display a series of dialog boxes and/or input fields 512 requesting information associated with applying for an insurance policy. For example, the policy component may be configured to assist in providing one or more policies for a given trade secret. The information requested via input field 512 may include, for example, a type or category of business secret, a value of the business secret (determined from above or identified by the user), a warranty period, an entity value, a creation date of the business secret, and/or a portion of the document requested and/or the implementation upload support document. In an example of providing a support document, the support document may be registered with the blockchain in the same or similar manner as described above with respect to the support document for business secret valuation.

The policy component and/or another component of the electronic device and/or the trade secret enrollment system may be configured to receive input data corresponding to the user input and may transmit the input data to a remote system associated with the insurer. The remote system may process the input data and, in an example, issue a policy, for example, to ensure that trade secrets are not compromised. In these examples, confirmation data indicating that the policy has been issued and information associated with the policy may be received from the remote system. This information, depicted as policy details 514, may be incorporated into the record associated with the trade secret and may be displayed at step 3 via the user interface 502 in an example. Some non-limiting examples of policy details 514 may include policy type, liability limits, reserve value, policy premium, policy form, policy number, policy life, liability share limits, and/or an estimate of trade secrets. Additionally or alternatively, the policy details 514 may include a payment value associated with an amount to be paid to an entity associated with the trade secret at the time of the event. In these examples, the policy component may receive compliance data indicating that the entity is not in compliance with the conditions of the insurance policy and may cause display of updated insurance policy information, including the updated payment value. In these examples, the updated payment value may be less than the original payment value. When the condition is satisfied, the payment value may be updated to reflect compliance with the policy condition.

In an example, one or more intelligent contracts can be utilized in association with a policy component. For example, an insurance policy may be associated with a given business secret using an intelligent contract associated with the blockchain. As described herein, an intelligent contract may be a computer protocol that digitally facilitates, validates, and/or enforces the negotiation and/or fulfillment of a contract. Transactions involving smart contracts may be traceable and irreversible. Intelligent contracts may utilize, for example, a byzantine fault tolerance algorithm that may enable digital security through decentralization of contracts. The intelligent contracts may be initiated, hosted, and/or implemented at least in part by a remote system associated with the blockchain. In these examples, the smart contract may indicate a condition for validating the insurance policy, and may receive validation data indicating that the condition has been satisfied. In these examples, the validation data may be sent to the distributed ledger system 106, which may cause the intelligent contract to validate the insurance policy.

FIG. 6 illustrates an exemplary user interface 602 displaying valuation functions in accordance with the digital property authentication and management system. The user interface 602 may be displayed on a display of an electronic device, such as the electronic device 102 described with respect to fig. 1. The user interface 602 may be the same as or similar to the user interface 126 described with respect to fig. 1. Fig. 6 illustrates a left-to-right progression of information displayed on and/or interaction with a user interface 602.

At step 1, the user interface 602 may display a record indicating the trade secret that has been registered with the trade secret registry. The record may include a record identifier 604, trade secret details 606, and/or transaction details 608. The record identifier 604 may include a number and/or letter that identifies the record relative to the trade secret registry. For example, the business secret details 606 can include a naming designator for the business secret, a description of the business secret, a naming designator for a document representing the business secret, and/or a tag generated as described elsewhere herein. The transaction details 608 may include a status registered with the trade secret registry, a document obfuscation value, a block number associated with a block in which the trade secret is registered to the blockchain, an encrypted document obfuscation value (also described as a blockdocument obfuscation value), and/or a block timestamp. Additionally, user interface 602 may include a selectable portion 610 that indicates an option for determining the value of the trade secret.

At step 2, based at least in part on the selection of selectable portion 610, user interface 602 may display a series of dialog boxes and/or input fields 612 requesting information associated with determining the value of the trade secret. For example, the valuation component can be configured to identify and/or determine a value associated with a given business secret. The information requested by input field 612 may include, for example, the type of business secret, the importance of the business secret to the entity, the entity's revenue, the entity's value, the business secret creation date, and the like.

Additionally, in an example, input field 612 may include a request for a support document that includes information that may be relevant to an evaluation of a business secret. In these examples, the user may identify the supporting document. A document obfuscation value may be generated for a given support document and/or the support document and/or document obfuscation value may be registered in association with the blockchain. The record of the business secret may include information associated with the support document, such as a corresponding document obfuscation value and/or an encrypted document obfuscation value corresponding to a tile in a blockchain in which the support document is registered.

For example, the business secret may be identified and/or determined to be the source code and may be indicated as being very valuable to an entity associated with the source code. The input data received from the electronic device may indicate that the value of the entity is $ 5,000,000 and the annual revenue of the entity is $ 350,000. Additionally, the entity may have uploaded a document to confirm some or all of the information. Based at least in part on this information, the evaluation component can determine the value of the trade secret. In an example, a comparison may be made between other registered business secrets, such as other source codes identified as important, and corporate statistics similar to corporate statistics identified for an entity. In an example, the valuation component can set one or more guardrails and/or limits on the value of the trade secret. For example, if the total value of an entity is $ 5,000,000, a limit may be set where the value of the trade secret cannot exceed $ 5,000,000. Additionally or alternatively, data indicating that the trade secret has been registered with the trade secret registry and/or an amount of time since the trade secret has been registered may be used to affect the evaluation of the trade secret.

Confirmation data indicating the determined value and information associated with the valuation may be received from the remote system. This information, depicted as valuation details 614, can be incorporated into a record associated with the business secret and can be displayed at step 3 in an example via the user interface 602. Some non-limiting examples of valuation details 614 can include a value, a type of business secret, a business secret creation date, an entity value, an entity revenue value, and/or one or more selectable links that, when selected, can cause a support document (if any) provided for valuation purposes to be displayed.

FIG. 7 illustrates an exemplary user interface 702 displaying access control functions in accordance with the digital property authentication and management system. The user interface 702 may be displayed on a display of an electronic device, such as the electronic device 102 described with respect to fig. 1. The user interface 702 may be the same as or similar to the user interface 126 described with respect to fig. 1. Fig. 7 shows the progression from left to right and top to bottom of the information displayed on and/or interaction with the user interface 702.

At step 1, the user interface 702 may include an authentication screen requesting user input to authenticate access to records associated with the trade secret registry. For example, a username 704 and password 706 may be requested. The user may provide input and corresponding input data may be analyzed by the electronic device displaying user interface 702 and/or a remote system associated with the business secret registry.

Upon authenticating the user input, at step 2, the user interface 702 may include a first selectable portion 708 that indicates an option to register the trade secret with the trade secret registry. The user interface 702 may also include a second selectable portion 710 indicating options for managing the registered trade secret and/or a third selectable portion 712 indicating options for verifying that the document has been registered in association with the trade secret registry. To illustrate the use and functionality of the user interface 702, a user may provide an input indicating a selection of the second selectable part 710. It is to be appreciated that, in an example, the first, second, and third

selectable portions

708, 710, 712 of the user interface 702 can be the same as or similar to (and can be functionally similar to) the first, second, and third

selectable portions

204, 206, 208 of the user interface 202 described with respect to fig. 2.

Selection of the second selectable portion 710 may cause the user interface 702 to display, at step 3, information associated with a trade secret that has been enrolled in association with the trade secret enrolment. In an example, commercial secret indicator 714 can be displayed. Commercial secret indicator 714 may include information describing and/or summarizing a given commercial secret. As shown in fig. 7, the information may include, for example, a name of the trade secret, a date the trade secret was registered in association with the trade secret registry, and/or a tag associated with the trade secret. In this manner, the trade secret indicator 714 provides an indication of the trade secret associated with the trade secret registry, and does not provide all of the information of each record of the trade secret in the example. In an example, business secret indicator 714 can be limited to only those business secrets associated with a given entity and/or entity identifier. Additionally or alternatively, business secret indicator 714 may be limited to only those business secrets that a user logged in with certain access credentials has rights to view.

In an example, commercial secret indicator 714 may be selectable, and when selected, may cause a record associated with the commercial secret indicator 714 to be displayed at step 4. As shown in fig. 7, the user may provide an input corresponding to a selection of "trade secret 1". Selection of the trade secret indicator may cause a record associated with "trade secret 1" to be displayed at step 4. As shown in fig. 7, the record may include the same or similar information as the record described with respect to fig. 2, including a record identifier, trade secret details, and/or transaction details.

As shown in step 4, one or more access controls may be implemented to limit access to the record and/or to a portion of the record based at least in part on access control data associated with authentication information provided by the user to access the system. For example, as shown in FIG. 7, access control data associated with a user viewing a record indicates that the user has access to the record identifier, the trade secret details, and the transaction details, but does not have access to certain valuation details. For example, the access control data indicates that access is authorized for the type of business secret and the creation date, but access is prohibited for the value, entity value, and/or revenue value. Thus, an entity associated with the system may set access authorization and determine which information will be available for a given individual. Additionally or alternatively, the access control data may indicate that a given individual is authorized to utilize certain functions of the trade secret registry but is prohibited from utilizing other functions. For example, an individual may be authorized to view certain records and/or information associated with the records but may be prohibited from manipulating and/or changing the records, such as adding, removing, and/or changing tags.

At step 5, the user interface may again display commercial secret indicator 714. In this example, the access control data may indicate that access to "trade secret 1" is authorized and access to "trade secret 2" is prohibited. Thus, upon selection of the trade secret indicator 714 corresponding to "trade secret 2," the user interface 702 may display information indicating that access is prohibited or otherwise denied at step 6. Additionally, where records have been linked and links have been provided between records as described elsewhere herein, access control data may be utilized to determine whether to display linked records when a link is selected.

8-23 illustrate a process for digital property authentication and management. The processes described herein are illustrated as a collection of blocks in a logical flow graph, which represents a sequence of operations, some or all of which may be implemented in hardware, software, or a combination thereof. In the context of software, the blocks may represent computer-executable instructions stored on one or more computer-readable media, which, when executed by one or more processors, program the processors to perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, etc. that perform particular functions or implement particular data types. The order in which the blocks are described should not be construed as a limitation, unless otherwise specified. Any number of the described blocks may be combined in any order and/or in parallel to implement a process or an alternative process, and not all blocks need be performed. For purposes of discussion, the processes are described with reference to the environments, architectures, and systems described in the examples herein, such as those described with respect to fig. 1-7, for example, but the processes may be implemented in a wide variety of other environments, architectures, and systems.

FIG. 8 depicts a flowchart of an exemplary process 800 for trade secret enrollment in accordance with the digital property authentication and management system. The order in which operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement process 800. The operations described with respect to process 800 are described as being performed by an electronic device, and/or a check-in system associated with a trade secret check-in, and/or a distributed ledger system associated with a blockchain. However, it should be understood that some or all of these operations may be performed by some or all of the components, devices, and/or systems described herein.

At block 802, process 800 may include an electronic device receiving a document representing a trade secret. For example, the user interface may include a selectable portion that, when selected, may identify a document that represents a trade secret. For example, the selectable portion and/or another portion of the user interface may include text requesting that a user of the user interface select the selectable portion to identify a document to be registered as a trade secret in association with the trade secret registry. The user may provide input to the electronic device indicating a document to be registered as a trade secret. The input may include selecting a naming designator for the document.

At block 804, the process 800 may include the electronic device generating a document obfuscation value corresponding to the document. For example, the obfuscation component may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic apparatus and/or a remote storage device accessible to the electronic apparatus. The obfuscation component may then generate a document obfuscation value corresponding to the document. In general, the obfuscation component may receive as input text data, image data, formatting data, and/or other data corresponding to a document, and may generate as output a document obfuscation value corresponding to the input. In an example, an electronic device may include a plurality of obfuscating components, each employing a different hashing algorithm. In these examples, each obfuscation component may output a different document obfuscation value for the same document.

At block 806, process 800 may include the registration system receiving the document obfuscation value and request data indicating a request to register the trade secret with a trade secret registry. For example, a document obfuscation value may be received from the electronic device, such as via a firewall. Additionally, the electronic device may have generated and transmitted request data indicating a request to register the trade secret with the trade secret registry.

Based at least in part on receiving the document obfuscation value and/or the request data, a communication component of the enrollment system may be configured to generate request data indicative of a request to enroll the business secret in association with a blockchain (such as a blockchain associated with a distributed ledger system). The request data may be sent to the distributed ledger system, for example, along with a document obfuscation value, and/or an identifier of the document and/or the trade secret, and/or other information associated with the document and/or the trade secret.

At block 808, the process 800 may include the distributed ledger system generating an encrypted document obfuscation value corresponding to a tile in the tile chain. For example, the distributed ledger system can receive request data and a document obfuscation value (or other data) and can register the document obfuscation value (or other data) in association with a block of the block chain. The distributed ledger system can generate an encrypted document obfuscation value that represents a tile in the blockchain and/or the distributed ledger system can generate a time value that indicates a time and/or date at which the document obfuscation value (or other data) was registered with the blockchain. The distributed ledger system can send encrypted document obfuscation values, time values, and/or other information (such as, for example, block numbers) to the registration system and/or the electronic device. At block 810, the process 800 may include the check-in system receiving an encrypted document obfuscation value from the distributed ledger system.

At block 812, process 800 may include the enrollment system generating a record corresponding to the trade secret in the trade secret registry. For example, a record generator of the enrollment system may then generate a record in the trade secret registry. For example, a record may include an identifier of the record, a naming indicator of a business secret, a description of the business secret, a naming indicator of a document, one or more tags, a status identifier of the record, a document obfuscation value, an encrypted document obfuscation value, a block number, a time value (also described as a block timestamp), insurance policy details, valuation details, and/or other information associated with the business secret. The record may be stored in a trade secret registry with one or more other records.

At block 814, process 800 may include the registration system may generate tag data associated with the document. For example, the tag data generator may be configured to generate tag data associated with a document. In an example, one or more input fields may be caused to be displayed via a user interface of an electronic device. The input field may include a request to "tag" or otherwise provide a keyword for the document. For example, a document corresponding to source code for operating a sewing machine may be associated with a keyword such as "source code", "sewing machine", "version 1.1.20", and the like. A user of the electronic device can input text corresponding to the tags, and the tag data generator can utilize such input to generate the tag data. Additionally or alternatively, the tag data generator may automatically generate the tag data. For example, the tag data generator may analyze a document to be registered in association with a trade secret registry to identify keywords associated with the document. For example, the tag data generator may identify one or more fields of the document and/or values associated with the fields. By way of illustration, the tag data generator can identify a title field, a document type field, one or more sections of a document, and/or the like. The values associated with these fields (such as text data) may be used to generate the tags. Additionally or alternatively, the text data of the document may be analyzed to determine which words are common in the document. These words may be recognized as keywords and may be used to generate tag data.

At block 816, process 800 may include the enrollment system associating the trade secret with one or more other trade secrets enrolled against the trade secret registry. For example, the linking component can be configured to associate one record with one or more other records in the trade secret registry. When records are determined to be different versions of the same document and/or when records are associated with the same entity identifier, an association between the records may be generated using a linking component. Generating the association may include storing data indicating that the records are associated. Generating the association may also or alternatively include generating a link or other similar functionality that may be displayed with the record via a user interface. For example, the link may correspond to a selectable portion of the user interface that, when selected, may cause the display of the linked record and/or a portion thereof.

At block 818, the process 800 may include the electronic device receiving confirmation data indicating that a record has been generated. In an example, the registration system may generate confirmation data indicating that the record has been generated, and may transmit the confirmation data to the electronic device.

At block 820, the process 800 may include the electronic device causing display of information associated with the record. Displaying information associated with the record may include information such as described herein, e.g., with respect to fig. 1-7.

FIG. 9 depicts a flowchart of an exemplary process 900 for commercial secret verification in accordance with a digital property authentication and management system. The order in which operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement process 900. The operations described with respect to process 900 are described as being performed by an electronic device, and/or a check-in system associated with a trade secret check-in, and/or a distributed ledger system associated with a blockchain. However, it should be understood that some or all of these operations may be performed by some or all of the components, devices, and/or systems described herein.

At block 902, process 900 may include the electronic device receiving the directed document and/or an identifier of the directed document. For example, a selectable portion of the user interface may be displayed on the electronic device that indicates an option for identifying documents that are directed, e.g., stolen. In these examples, the document may be obtained from a third party who may be compromised or otherwise obtain the trade secret without permission. For example, identification of the commanded document may include input, such as a naming designator for the document and/or selection of the document from a database of the electronic device displaying the user interface.

At block 904, the process 900 may include the electronic device generating a document obfuscation value corresponding to the commanded document. For example, a document may be identified and the electronic device may cause generation of a document obfuscation value corresponding to the document. For example, the obfuscation component may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic apparatus and/or a remote storage device accessible to the electronic apparatus. The obfuscation component may then generate a document obfuscation value corresponding to the document. In general, the obfuscation component may receive as input text data, image data, formatting data, and/or other data corresponding to a document, and may generate as output a document obfuscation value corresponding to the input. In an example, an electronic device may include a plurality of obfuscating components, each employing a different hashing algorithm. In these examples, each obfuscation component may output a different document obfuscation value for the same document.

At block 906, process 900 may include the registration system receiving the document obfuscation value and request data indicating a request to identify one or more trade secrets similar to the commanded document registered with the trade secret registry. For example, a document obfuscation value may be received from the electronic device, such as via a firewall. Additionally, the electronic device may have generated and transmitted request data indicating a request to identify one or more trade secrets similar to the commanded document that are registered with the trade secret registry.

At block 908, process 900 may include the enrollment system analyzing the document obfuscation value relative to other document obfuscation values associated with one or more other business secrets enrolled with the business secret registry. For example, the verification component may be configured to verify that a particular document has been registered with the trade secret registry. For example, once registered, the verification component can be used to determine whether another document (such as a document that has been compromised) matches or is similar to the registered document and/or verify that another document (such as a document that has been compromised) matches or is similar to the registered document. The verification component may be operative to analyze the document confusion value of the commanded document relative to other document confusion values of the registered documents.

At block 910, the process 900 may include the registration system identifying similar document confusion values. For example, if the validation component determines that at least one of the registered document obfuscation values matches the document obfuscation value of the directed document, the validation component may determine that the directed document is the same as or similar to the registered document. In other examples, the verification component may determine a similarity between the commanded document and one or more registered documents.

Determining similarity may be performed as described above with respect to comparing component 144 of fig. 1. In these examples, the directed document may be determined to be similar to the registered document when the similarity meets or exceeds a threshold similarity. In other examples, the verification component may be configured to determine which portions of the commanded document match or are similar to the at least one registered document. An indication of the matching or similar portion may be displayed, such as via a user interface. Additionally, where multiple versions of a document have been registered, the validation component may be configured to determine which of the multiple versions is most similar to the commanded document, and may provide an indication of the most similar version.

At block 912, the process 900 may include the distributed ledger system verifying that similar document obfuscation values have been registered with the blockchain. For example, it may be determined that the commanded document confusion value matches the registered document confusion value. In these examples, it may be advantageous to verify that the registered document obfuscation value corresponds to a business secret that has been registered with the blockchain. Thus, the directed document obfuscation value may be submitted to a distributed ledger system that may search for a matching registered document obfuscation value in the blockchain and/or a corresponding encrypted document obfuscation value representing a block in the blockchain in which the business secret is registered.

At block 914, process 900 may include the enrollment system generating verification data identifying similar business secrets, and in an example verifying enrollment with the blockchain. The enrollment system may receive data from the distributed ledger system indicating that the indexed document obfuscation value matches the registered document obfuscation value. In these and other examples, the registration system may generate verification data to be sent to the electronic device.

At block 916, the process 900 may include the electronic device receiving the verification data. For example, the verification status of the verification data may indicate that the commanded document matches or is similar to the at least one registered business secret. The similarity indicator may indicate that the directed document is similar to at least one of the registered documents, such as up to a percentage. Additionally, an identifier of the registered trade secret may be provided. This may provide an indication to the user of the registered trade secret similar to the commanded document.

At block 918, the process 900 can include the electronic device launching a claim submission wizard to initiate a process to propose an insurance claim associated with the trade secret. In an example, the user interface can display a dialog box and/or an input field that includes text associated with submitting an insurance coverage claim in association with an insurance policy for a trade secret. In these examples, one or more wizards may be launched to assist in proposing insurance coverage claims, given that claims or other legitimate claims of commercial secret theft may exist in view of the similarity between the commanded document and the registered commercial secret. Input data representing a response to the dialog box can be received, and the input data can be formatted and/or transmitted to a remote system associated with the insurer indicating that a claim is to be filed and/or that potential theft and/or other legitimate action is to be notified to the insurer based at least in part on receiving the input data.

FIG. 10 shows a flowchart of an exemplary process for digital property authentication. The order in which operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement process 1000.

At block 1002, process 1000 may include receiving, at an electronic device, data representing a document, the document representing a business secret. For example, the user interface may include a selectable portion that, when selected, may identify a document that represents a trade secret. For example, the selectable portion and/or another portion of the user interface may include text requesting that a user of the user interface select the selectable portion to identify a document to be registered as a trade secret in association with the trade secret registry. The user may provide input to the electronic device indicating a document to be registered as a trade secret. The input may include selecting a naming designator for the document.

At block 1004, process 1000 may include receiving, at an electronic device, input indicating that a document is to be enrolled at a trade secret enrolment associated with an enrollment system, which may also be described herein as a first remote system. For example, input may be received via a user interface having one or more selectable portions. At least one of the selectable portions may be selectable by a user to indicate that the document is to be registered with the trade secret registry.

At block 1006, process 1000 may include generating a document obfuscation value representing the document based at least in part on receiving the input. For example, the obfuscation component may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic apparatus and/or a remote storage device accessible to the electronic apparatus. The obfuscation component may then generate a document obfuscation value corresponding to the document. In general, the obfuscation component may receive as input text data, image data, formatting data, and/or other data corresponding to a document, and may generate as output a document obfuscation value corresponding to the input. In an example, an electronic device may include a plurality of obfuscating components, each employing a different hashing algorithm. In these examples, each obfuscation component may output a different document obfuscation value for the same document.

At block 1008, the process 1000 may include sending the document obfuscation value and first request data indicating a first request to generate a block in a blockchain associated with a distributed ledger system, which may also be described herein as a second remote system. For example, a communication component of the electronic device can format and/or transmit the document obfuscation value to a registration system, and can generate request data for transmission to the registration system and/or the distributed ledger system.

At block 1010, the process 1000 may include receiving an encrypted document obfuscation value representing a tile in a tile chain from a second remote system. For example, based at least in part on receiving the document obfuscation value and/or the request data, the registration system and/or a communication component of the electronic device may be configured to generate request data indicative of a request to register the business secret in association with a blockchain (such as a blockchain associated with a distributed ledger system). The request data may be sent to the distributed ledger system, for example, along with a document obfuscation value, and/or an identifier of the document and/or the trade secret, and/or other information associated with the document and/or the trade secret.

The distributed ledger system can receive request data and document obfuscation values (or other data) and can register document obfuscation values (or other data) in association with tiles of the blockchain. The distributed ledger system can generate an encrypted document obfuscation value that represents a tile in the blockchain and/or the distributed ledger system can generate a time value that indicates a time and/or date at which the document obfuscation value (or other data) was registered with the blockchain. The distributed ledger system can send encrypted document obfuscation values, time values, and/or other information (such as, for example, block numbers) to the registration system and/or the electronic device. The enrollment system and/or the electronic device may receive an encrypted document obfuscation value from the distributed ledger system.

At block 1012, the process 1000 may include sending, from the electronic device and to the first remote system, second request data representing a second request to register the document with respect to the business secret registry. The request data may be sent before or after receiving the encrypted document obfuscation value.

At block 1014, process 1000 may include generating, by the first remote system, a record in the trade secret registry, the record: indicating that a trade secret has been registered at a trade secret registry; including an encrypted document obfuscation value; and indicating a time value associated with at least one of the generation of the encrypted document obfuscation value or the generation of the record. For example, a record generator of the enrollment system may then generate a record in the trade secret registry. For example, a record may include an identifier of the record, a naming indicator of a business secret, a description of the business secret, a naming indicator of a document, one or more tags, a status identifier of the record, a document obfuscation value, an encrypted document obfuscation value, a block number, a time value (also described as a block timestamp), insurance policy details, valuation details, and/or other information associated with the business secret. The record may be stored in a trade secret registry with one or more other records.

At block 1016, the process 1000 may include generating confirmation data indicating that the record has been generated. In an example, the registration system may generate confirmation data indicating that a record has been generated.

At block 1018, the process 1000 may include sending confirmation data from the first remote system to the electronic device. Receipt of the confirmation data may cause display of information via the user interface indicating that the trade secret has been registered.

Additionally or alternatively, process 1000 may include identifying a first portion and a second portion of a document and generating a second document obfuscation value representing the first portion of the document and a third document obfuscation value representing the second portion of the document. In these examples, generating the first document obfuscation value may be based at least in part on the second document obfuscation value and the third document obfuscation value. For example, the first document obfuscation value may be generated by generating a document obfuscation value of the second and third document obfuscation values. Alternatively, the first document obfuscation value may be generated by combining the second and third document obfuscation values.

Additionally or alternatively, the process 1000 may include sending the document obfuscation value and third request data indicative of a third request to generate a second tile in a second tile chain associated with the insurer system to the insurer system. Process 1000 may also include receiving a second encrypted document obfuscation value representing a second tile in a second tile chain from the insurer system. In an example where the electronic device receives the second encrypted document obfuscation value, the electronic device may send the second encrypted document obfuscation value to the registration system. In these and other examples, the record may associate the second encrypted document obfuscation value with the business secret and may indicate a second time value associated with generation of the second encrypted document obfuscation value.

Additionally or alternatively, process 1000 may include generating tag data indicative of a property associated with the document. The properties may include at least one of: a title, a type of business secret, and/or an identifier of at least one of a person or entity associated with the document. Process 1000 may also include storing the tag data in a database associated with the registration system. The tag data may be associated with a document obfuscation value and/or a business secret. Process 1000 may also include receiving, at an enrollment system, input data requesting a search for a trade secret associated with a trade secret enrollment. In these examples, the input data may include search terms. Process 1000 may also include causing search of tag data for the search term based at least in part on receiving the input data.

FIG. 11 shows a flow diagram of another exemplary process for digital property authentication. The order in which operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement process 1100.

At block 1102, process 1100 may include receiving data representing a document that represents a business secret. For example, the user interface may include a selectable portion that, when selected, may identify a document that represents a trade secret. For example, the selectable portion and/or another portion of the user interface may include text requesting that a user of the user interface select the selectable portion to identify a document to be registered as a trade secret in association with the trade secret registry. The user may provide input to the electronic device indicating a document to be registered as a trade secret. The input may include selecting a naming designator for the document.

At block 1104, process 1100 may include receiving input indicating that a document is to be registered at a trade secret registry associated with a registration system. For example, input may be received via a user interface having one or more selectable portions. At least one of the selectable portions may be selectable by a user to indicate that the document is to be registered with the trade secret registry.

At block 1106, process 1100 may include generating a document obfuscation value representing the document based at least in part on receiving the input. For example, the obfuscation component may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic apparatus and/or a remote storage device accessible to the electronic apparatus. The obfuscation component may then generate a document obfuscation value corresponding to the document. In general, the obfuscation component may receive as input text data, image data, formatting data, and/or other data corresponding to a document, and may generate as output a document obfuscation value corresponding to the input. In an example, an electronic device may include a plurality of obfuscating components, each employing a different hashing algorithm. In these examples, each obfuscation component may output a different document obfuscation value for the same document.

At block 1108, process 1100 may include sending, to the enrollment system, the document obfuscation value and request data indicating a request to enroll the trade secret in association with the trade secret registry. For example, a communication component of the electronic device may format and/or transmit the document obfuscation value to a registration system. Additionally, the communication component may generate request data for transmission to the registration system.

At block 1110, process 1100 may include receiving confirmation data from the registration system indicating that: the trade secret has been registered in association with a trade secret registry; and the business secret has been associated with an encrypted document obfuscation value representing a tile in a blockchain associated with the distributed ledger system. For example, based at least in part on receiving the document obfuscation value and/or the request data, the registration system and/or a communication component of the electronic device may be configured to generate request data indicative of a request to register the business secret in association with a blockchain (such as a blockchain associated with a distributed ledger system). The request data may be sent to the distributed ledger system, for example, along with a document obfuscation value, and/or an identifier of the document and/or the trade secret, and/or other information associated with the document and/or the trade secret.

The enrollment system may then generate a record in the trade secret registry. For example, a record generator of the enrollment system may then generate a record in the trade secret registry. For example, a record may include an identifier of the record, a naming indicator of a business secret, a description of the business secret, a naming indicator of a document, one or more tags, a status identifier of the record, a document obfuscation value, an encrypted document obfuscation value, a block number, a time value (also described as a block timestamp), insurance policy details, valuation details, and/or other information associated with the business secret. The record may be stored in a trade secret registry with one or more other records.

Additionally or alternatively, process 1100 may include identifying a first portion and a second portion of a document and generating a second document obfuscation value representing the first portion of the document and a third document obfuscation value representing the second portion of the document. In these examples, generating the first document obfuscation value may be based at least in part on the second document obfuscation value and the third document obfuscation value. For example, the first document obfuscation value may be generated by generating a document obfuscation value of the second and third document obfuscation values. Alternatively, the first document obfuscation value may be generated by combining the second and third document obfuscation values.

Additionally or alternatively, process 1100 can include receiving confirmation data indicating that the commercial secret has been associated with a second encrypted document obfuscation value representing a second tile in a second chain of tiles associated with the insurer system.

Additionally or alternatively, process 1100 may include generating a second document obfuscation value representing the document based at least in part on receiving the input. In these examples, the second document obfuscation value may be generated using a second hash value generator different from the first hash value generator. Process 1100 may also include sending the second document obfuscation value to a registration system. In these examples, the validation data may indicate that the commercial secret has been associated with a second encrypted document obfuscation value associated with a second document obfuscation value, and the second encrypted document obfuscation value represents a second tile in a second tile chain associated with a third system.

Additionally or alternatively, the process 1100 may include receiving a second input indicative of at least one of: a title associated with the document, a type of business secret associated with the document, and/or identifying information of at least one of a person or entity associated with the document. Process 1100 may also include generating tag data based at least in part on the second input and transmitting the tag data to the registration system. Process 1100 may also include receiving a third input requesting a search of the trade secret registry, wherein the third input includes a search term, and sending an indication of the third input to the registry system. Process 1100 may also include receiving response data indicating results of a search performed by the registration system for at least the tag data.

Additionally or alternatively, process 1100 may include identifying fields of a document, wherein individual ones of the fields may be associated with field types. The process 1100 may also include identifying field values associated with respective ones of the fields and generating tag data associated with the document based at least in part on the field type and/or the field value of the respective ones of the fields.

Additionally or alternatively, process 1100 may include storing security rules associated with a firewall. In these examples, sending the document obfuscation value and the request data may be based at least in part on a security rule that allows the document obfuscation value and the request data to be transmitted to the registration system. And in these examples, receiving the confirmation data may be based at least in part on a security rule that allows the confirmation data to be received from the registration system.

FIG. 12 depicts a flowchart of another example process for digital property authentication. The order in which operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement process 1200.

At block 1202, process 1200 may include receiving, from an electronic device, a document obfuscation value representing a document corresponding to a business secret. For example, the obfuscation component of the electronic apparatus may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic apparatus and/or a remote storage device accessible to the electronic apparatus. The obfuscation component may then generate a document obfuscation value corresponding to the document. In general, the obfuscation component may receive as input text data, image data, formatting data, and/or other data corresponding to a document, and may generate as output a document obfuscation value corresponding to the input. In an example, an electronic device may include a plurality of obfuscating components, each employing a different hashing algorithm. In these examples, each obfuscation component may output a different document obfuscation value for the same document.

At block 1204, the process 1200 may include receiving input data indicating that a trade secret is to be registered in a trade secret registry. For example, a communication component of the electronic device may format and/or transmit input data to the system.

At block 1206, process 1200 may include sending the document obfuscation value and request data indicating a request to generate a tile in a tile chain associated with the remote system to the remote system. For example, a communication component of the electronic device may format and/or transmit the document obfuscation value to the system and may generate request data for transmission to the system and/or a remote system.

At block 1208, the process 1200 may include receiving an encrypted document obfuscation value representing a tile in the tile chain from the remote system. For example, based at least in part on receiving the document obfuscation value and/or the request data, a communication component of the system and/or the electronic device may be configured to generate request data indicative of a request to register the business secret in association with a blockchain (such as a blockchain associated with a remote system). The request data may be sent to the remote system with, for example, a document obfuscation value, and/or an identifier of the document and/or the trade secret, and/or other information associated with the document and/or the trade secret.

The remote system may receive the request data and the document obfuscation value (or other data) and may register the document obfuscation value (or other data) in association with a tile of the blockchain. The remote system may generate an encrypted document obfuscation value representing a tile in the blockchain and/or the remote system may generate a time value indicating a time and/or date at which the document obfuscation value (or other data) was registered with the blockchain. The remote system may send the encrypted document obfuscation value, time value, and/or other information (such as, for example, block number) to the system and/or the electronic device. The system and/or electronic device may receive an encrypted document obfuscation value from a remote system.

At block 1210, process 1200 may include generating a record in a trade secret registry, the record: indicating that a trade secret has been registered in a trade secret registry; and includes an encrypted document obfuscation value. For example, a record generator of the system may then generate a record in a trade secret registry. For example, a record may include an identifier of the record, a naming indicator of a business secret, a description of the business secret, a naming indicator of a document, one or more tags, a status identifier of the record, a document obfuscation value, an encrypted document obfuscation value, a block number, a time value (also described as a block timestamp), insurance policy details, valuation details, and/or other information associated with the business secret. The record may be stored in a trade secret registry with one or more other records.

Additionally or alternatively, the process 1200 may include receiving, from the electronic device, a second document obfuscation value representing the document, and sending, to the distributed ledger system, the second document obfuscation value and second request data indicating a second request to generate a second tile in a second tile chain associated with the distributed ledger system. The process 1200 may also include receiving, from the distributed ledger system, a second encrypted document obfuscation value representing a second tile in the second tile chain. In these examples, the record may associate the second encrypted document obfuscation value with the business secret.

Additionally or alternatively, the process 1200 may include receiving an identifier corresponding to at least one of the electronic device and/or an entity associated with the electronic device. The process 1200 may also include associating an identifier with the first record and determining that a second record associated with the trade secret registry is associated with the identifier. The process 1200 may also include associating the first record with the second record based at least in part on determining that the first record and the second record are associated with the identifier.

Additionally or alternatively, the process 1200 may include sending the document obfuscation value and second request data to the distributed ledger system, the second request data indicating a second request to generate a second block in a second block chain associated with the distributed ledger system. The process 1200 may also include receiving, from the distributed ledger system, a second encrypted document obfuscation value representing a second tile in the second tile chain. In these examples, the record may associate the second encrypted document obfuscation value with the business secret.

Additionally or alternatively, the process 1200 may include receiving second input data indicative of at least one of: a title associated with the document, a type of business secret associated with the document, or an identifier of at least one of a person or entity associated with the document. Process 1200 may also include generating tag data based at least in part on the second input data. The process 1200 may also include receiving third input data requesting a search for a trade secret associated with the trade secret registry, where the third input data may include a search term. Process 1200 may also include causing search of tag data for the search term based at least in part on receiving the third input data.

Additionally or alternatively, process 1200 may include identifying fields of a document, wherein individual ones of the fields may be associated with field types. The process 1200 may also include identifying field values associated with respective ones of the fields and generating tag data associated with the document based at least in part on the field type and/or the field value of the respective ones of the fields.

FIG. 13 shows a flowchart of another exemplary process for digital property authentication. The order in which operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement process 1300.

At block 1302, process 1300 may include receiving data representing a document corresponding to a trade secret from an electronic device. For example, the user interface may include a selectable portion that, when selected, may identify a document that represents a trade secret. For example, the selectable portion and/or another portion of the user interface may include text requesting that a user of the user interface select the selectable portion to identify a document to be registered as a trade secret in association with the trade secret registry. The user may provide input to the electronic device indicating a document to be registered as a trade secret. The input may include selecting a naming designator for the document.

At block 1304, process 1300 may include receiving input data indicating that the document is to be registered in a trade secret registry. For example, input may be received via a user interface having one or more selectable portions. At least one of the selectable portions may be selectable by a user to indicate that the document is to be registered with the trade secret registry.

At block 1306, process 1300 may include generating a document obfuscation value representing the document based at least in part on receiving the input data. For example, a obfuscation component of the electronic apparatus and/or a system associated with the business secret registry may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic apparatus and/or system, and/or a remote storage accessible to the electronic apparatus and/or system. The obfuscation component may then generate a document obfuscation value corresponding to the document. In general, the obfuscation component may receive as input text data, image data, formatting data, and/or other data corresponding to a document, and may generate as output a document obfuscation value corresponding to the input. In an example, an electronic device may include a plurality of obfuscating components, each employing a different hashing algorithm. In these examples, each obfuscation component may output a different document obfuscation value for the same document.

At block 1308, process 1300 may include removing the document from the system. For example, once a document obfuscation value is generated, the document may be removed from the system so that it is not stored or otherwise made available to anyone having access to the system, except for the electronic device from which the document was received, for security reasons and the like.

At block 1310, process 1300 may include sending to the remote system a document obfuscation value and request data indicating a request to generate a tile in a tile chain associated with the remote system. For example, a communication component of the system may format and/or transmit the document obfuscation value and the request data to a remote system.

At block 1312, process 1300 may include receiving an encrypted document obfuscation value representing a block in a block chain from a remote system. For example, based at least in part on receiving the document obfuscation value and/or the request data, a communication component of the system and/or the electronic device may be configured to generate request data indicative of a request to register the business secret in association with a blockchain (such as a blockchain associated with a remote system). The request data may be sent to the remote system with, for example, a document obfuscation value, and/or an identifier of the document and/or the trade secret, and/or other information associated with the document and/or the trade secret.

At block 1314, process 1300 may include generating a record in the trade secret registry that: indicating that a trade secret has been registered in a trade secret registry; including an encrypted document obfuscation value; and indicating a time value associated with at least one of the generation of the encrypted document obfuscation value or the generation of the record. For example, a record generator of the system may then generate a record in a trade secret registry. For example, a record may include an identifier of the record, a naming indicator of a business secret, a description of the business secret, a naming indicator of a document, one or more tags, a status identifier of the record, a document obfuscation value, an encrypted document obfuscation value, a block number, a time value (also described as a block timestamp), insurance policy details, valuation details, and/or other information associated with the business secret. The record may be stored in a trade secret registry with one or more other records.

Additionally or alternatively, process 1300 may include generating a second document obfuscation value representative of the document based at least in part on receiving the input data, the second document obfuscation value being generated using a second hash value generator different from the first hash value generator. The process 1300 may also include sending a second document obfuscation value and second request data to the distributed ledger system, the second request data indicating a second request to generate a second block in a second block chain associated with the distributed ledger system. The process 1300 may also include receiving a second encrypted document obfuscation value representing a second tile in a second tile chain from the distributed ledger system. In these examples, the record may associate the second encrypted document obfuscation value with the business secret.

Additionally or alternatively, the process 1300 may include receiving an identifier corresponding to at least one of the electronic device and/or an entity associated with the electronic device. Process 1300 may also include associating an identifier with the first record and determining that the second record associated with the trade secret registry is associated with the identifier. The process 1300 may also include associating the first record with the second record based at least in part on determining that the first record and the second record are associated with the identifier.

Additionally or alternatively, process 1300 may include identifying a first portion and a second portion of a document and generating a second document obfuscation value representing the first portion of the document and a third document obfuscation value representing the second portion of the document. In these examples, generating the first document obfuscation value may be based at least in part on the second document obfuscation value and the third document obfuscation value. For example, the first document obfuscation value may be generated by generating a document obfuscation value of the second and third document obfuscation values. Alternatively, the first document obfuscation value may be generated by combining the second and third document obfuscation values.

Additionally or alternatively, the process 1300 may include sending the document obfuscation value and second request data to the distributed ledger system, the second request data indicating a second request to generate a second block in a second block chain associated with the distributed ledger system. The process 1300 may also include receiving a second encrypted document obfuscation value representing a second tile in a second tile chain from the distributed ledger system. In these examples, the record may associate the second encrypted document obfuscation value with the business secret.

Additionally or alternatively, the process 1300 may include receiving second input data indicative of at least one of: a title associated with the document, a type of business secret associated with the document, or an identifier of at least one of a person or entity associated with the document. Process 1300 may also include generating tag data based at least in part on the second input data. Process 1300 may also include receiving third input data requesting a search for a trade secret associated with the trade secret registry, where the third input data may include a search term. Process 1300 may also include causing search of tag data for the search term based at least in part on receiving the third input data.

Additionally or alternatively, process 1300 may include identifying fields of a document, wherein individual ones of the fields may be associated with field types. The process 1300 may also include identifying field values associated with respective ones of the fields and generating tag data associated with the document based at least in part on the field type and/or the field value of the respective ones of the fields.

Additionally or alternatively, process 1300 may include storing security rules associated with a firewall. In these examples, receiving the data representative of the document may be based at least in part on a security rule that allows the data to be received from the electronic device. Additionally, sending the document obfuscation value and the request data may be based at least in part on a security rule that allows the document obfuscation value and the request data to be transmitted to a remote system. Additionally, sending the confirmation data may be based at least in part on a security rule that allows transmission of the confirmation data to the electronic device.

FIG. 14 depicts a flowchart of an exemplary process for identifying differences between documents associated with a digital property authentication and management system. The order in which operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement process 1400.

At block 1402, process 1400 may include receiving a document obfuscation value representing a document corresponding to the business secret from the electronic device. For example, the obfuscation component of the electronic apparatus may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic apparatus and/or a remote storage device accessible to the electronic apparatus. The obfuscation component may then generate a document obfuscation value corresponding to the document. In general, the obfuscation component may receive as input text data, image data, formatting data, and/or other data corresponding to a document, and may generate as output a document obfuscation value corresponding to the input. In an example, an electronic device may include a plurality of obfuscating components, each employing a different hashing algorithm. In these examples, each obfuscation component may output a different document obfuscation value for the same document.

At block 1404, process 1400 may include receiving first request data indicating a request to register a trade secret in association with a trade secret registry. For example, a communication component of the electronic device may format and/or transmit input data to the system.

At block 1406, process 1400 may include analyzing the document obfuscation value against a stored document obfuscation value stored in association with the business secret registry. For example, the comparison component may be configured to analyze the document confusion value and determine a similarity and/or a difference between the document confusion value and/or the documents corresponding to the document confusion value. For example, as described above, the obfuscation component may generate a document obfuscation value corresponding to a document representing a business secret. Similar documents may have similar document confusion values. Thus, the comparison component can analyze the document confusion values to determine the similarity between them. A threshold similarity may be identified and/or determined and the similarity between document confusion values may be compared to the threshold similarity. Document confusion values with a similarity that meets or exceeds a threshold similarity may be determined to be similar, while hash value pairs below the threshold similarity may be determined to be dissimilar. Additionally, the document obfuscation value may be segmented and the segments may be compared to determine similar and dissimilar portions of the document obfuscation value. The number of similar and dissimilar document confusion values may be used to determine an overall similarity between the document confusion values.

In other examples, the feature vectors may be associated with some or all of the document obfuscation values. The feature vector may correspond to a document obfuscation value and/or a characteristic of the document. For example, the presence or absence of text data and/or image data from a document may affect the feature vectors. In other examples, the text data and/or the image data itself may affect the feature vectors. Other factors such as document length, entity associated with the document, creation date, modification date, and/or other metadata may affect the feature vector. For example, a feature may be described as an individual measurable property or characteristic of a document. The given feature may be a number and/or may be considered a string and/or a graphic. A set of such features may be described as a feature vector. Thus, similar feature vectors indicate similar characteristics and/or properties of the documents they represent. A similarity and/or popularity score may be determined for a given pair of feature vectors, with a better score indicating a high degree of similarity between documents.

In other examples, the similarity between trade secrets may be determined using the levenstein distance. A levens distance between two document confusion values and/or documents may be determined. A shorter levenstein distance may indicate more similarity than a longer levenstein distance. As used herein, the levenstein distance (also referred to as the edit distance) can be described as a string metric for measuring the difference between two sequences. For example, the levenstein distance between two words may be considered the minimum number of single character edits to change one word to another. Thus, the levens distance between two very similar words will be shorter than the levens distance between two very different words. In these examples, a lewy distance between two documents and/or two document obfuscation values representing the documents may be determined, with a shorter lewy distance indicating more similarity between documents.

The comparison component may be configured to determine whether the trade secret to be enrolled is unique relative to other trade secrets enrolled in association with the trade secret enrolment. For example, document obfuscation values and/or documents may be analyzed as described herein to determine whether a given document obfuscation value differs from one or more stored document obfuscation values associated with registered business secrets. If the document obfuscation values are different, the business secret to be enrolled may be identified or determined to be unique relative to other business secrets associated with the business secret registry. In an example, determining that the document confusion value differs from the stored document confusion value may include determining a similarity between the document confusion values and determining that the similarity does not exceed a threshold similarity.

At block 1408, the process 1400 may include determining that the document obfuscation value is different from the stored document obfuscation value based at least in part on analyzing the document obfuscation value relative to the stored document obfuscation value. For example, determining that the document obfuscation value is different from the stored document obfuscation value may be based at least in part on results from a comparison component as described with respect to block 1406.

At block 1410, process 1400 may include receiving an encrypted document obfuscation value associated with a document obfuscation value representing a tile in a tile chain from a remote system. For example, based at least in part on receiving the document obfuscation value and/or the request data, a communication component of the system and/or the electronic device may be configured to generate request data indicative of a request to register the business secret in association with a blockchain (such as a blockchain associated with a remote system). The request data may be sent to the remote system with, for example, a document obfuscation value, and/or an identifier of the document and/or the trade secret, and/or other information associated with the document and/or the trade secret.

At block 1412, process 1400 may include generating a record in the business secret registry based at least in part on determining that the document obfuscation value is different from the stored document obfuscation value, the record: indicating that a trade secret has been registered in a trade secret registry; and associating the encrypted document obfuscation value with the business secret. For example, a record generator of the system may then generate a record in a trade secret registry. For example, a record may include an identifier of the record, a naming indicator of a business secret, a description of the business secret, a naming indicator of a document, one or more tags, a status identifier of the record, a document obfuscation value, an encrypted document obfuscation value, a block number, a time value (also described as a block timestamp), insurance policy details, valuation details, and/or other information associated with the business secret. The record may be stored in a trade secret registry with one or more other records.

Additionally or alternatively, process 1400 may include associating the business secret with at least one business secret associated with at least one of the stored document obfuscation values based at least in part on determining that a similarity between the document obfuscation value and the stored document obfuscation values is greater than a threshold similarity and/or determining that an entity identifier associated with the document obfuscation value is associated with the stored document obfuscation values.

Additionally or alternatively, process 1400 may include generating validation data that indicates that the record has been associated with the trade secret registry and/or that the document has been determined to be unique relative to other documents registered in association with the trade secret registry. Process 1400 may also include sending the confirmation data to the electronic device, such as for display via a user interface.

FIG. 15 depicts a flowchart of an exemplary process associated with a user interface in accordance with the digital property authentication and management system. The order in which the operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the process 1500.

At block 1502, the process 1500 may include causing display of a user interface including a first selectable portion indicating an option to enroll a trade secret at a trade secret registry associated with a remote system. For example, the user interface may be caused to be displayed on a screen of the electronic device. The selectable portions may be displayed via the user interface in a manner such that the user may provide an input to select the first selectable portion. In an example, the first selectable part may include text such as "check-in," which may provide an indication of the function associated with the selection of the first selectable part.

At block 1504, the process 1500 may include receiving, via the user interface, a first input indicating a selection of the first selectable portion. Input may be received via touch input on a screen of the electronic device and/or by tactile and/or audible input using, for example, a tool such as a mouse or keyboard.

At block 1506, process 1500 may include causing, based at least in part on receiving the first input, a display request to identify a second selectable portion of the document to be registered as a business secret. Causing the second selectable portion to be displayed may be the same as or similar to causing the first selectable portion to be displayed, as described with respect to block 1502.

At block 1508, the process 1500 may include receiving a second input identifying the document with a second selectable portion of the user interface. For example, identification of the document may include input, such as a naming indicator of the document and/or selection of the document from a database of the electronic device displaying the user interface. The document can be identified and the electronic device can cause generation of a document obfuscation value corresponding to the document. For example, the obfuscation component may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic apparatus and/or a remote storage device accessible to the electronic apparatus. The obfuscation component may then generate a document obfuscation value corresponding to the document. In general, the obfuscation component may receive as input text data, image data, formatting data, and/or other data corresponding to a document, and may generate as output a document obfuscation value corresponding to the input. In an example, an electronic device may include a plurality of obfuscating components, each employing a different hashing algorithm. In these examples, each obfuscation component may output a different document obfuscation value for the same document.

At block 1510, process 1500 may include causing, based at least in part on the second input, display of a record associated with the trade secret registry, the record indicating: a document obfuscation value generated based at least in part on the document has been registered in association with a trade secret registry; the encrypted document obfuscation values associated with the tiles of the tile chain have been registered in association with the commercial secret registry; and a time value associated with at least one of the generation of the encrypted document obfuscation value or the generation of the record. The record may include a record identifier, trade secret details, and/or transaction details. The record identifier may include a number and/or letter that identifies the record relative to the trade secret registry. For example, the details of the business secret may include a naming designator for the business secret, a description of the business secret, a naming designator for a document representing the business secret, and/or a tag generated as described elsewhere herein. The transaction details may include a status registered with the trade secret registry, a document obfuscation value, a block number associated with a block in which the trade secret is registered to the blockchain, an encrypted document obfuscation value (also described as a blockdocument obfuscation value), and/or a block timestamp. Other information that may be included in the record and displayed relative to the user interface may include insurance policy details, valuation details, and/or other information associated with the trade secret, as described more fully elsewhere herein.

The record may be generated by a record generator of a remote system associated with the trade secret registry. The record may be stored in a trade secret registry with one or more other records. In an example, the remote system may generate confirmation data indicating that the record has been generated, and may transmit the confirmation data to the electronic device for display via the user interface.

Additionally or alternatively, the process 1500 may include causing display of a third selectable portion indicating a second option to acquire the insurance policy associated with the trade secret and receiving, via the user interface, a third input indicating selection of the third selectable portion. The process 1500 may also include causing display of one or more requests for information associated with at least one of an insurance policy or a trade secret based at least in part on receiving the third input. Further, one or more input fields configured to receive text input in response to one or more requests for information may be caused to be displayed. The process 1500 may also include receiving, via the user interface, text input for each of the one or more input fields and receiving an indication from the distributed ledger system associated with the insurer that the insurance policy has been issued. The process 1500 may also include causing display of insurance policy information associated with the insurance policy via the user interface.

Additionally or alternatively, process 1500 may include causing display of input fields associated with the document via a user interface. In these examples, the input field may include at least one of a document name field, a document description field, and/or a tag field. The process 1500 may also include causing display, via the user interface, of a third selectable portion indicating a second option to automatically populate at least one of the input fields. The process 1500 may also include receiving, via the user interface, a third input indicating a selection of the third selectable portion and causing display of text in at least one of the input fields based at least in part on the third input.

Additionally or alternatively, process 1500 may include causing display, via the user interface, of a third selectable option indicating a second option to associate the information document with the trade secret. In these examples, the information document may indicate information associated with the value of the business secret. Process 1500 may also include receiving a third input identifying the information document using a third selectable portion of the user interface. Process 1500 may also include causing a value determined by the remote system based at least in part on the information document to be displayed via the user interface. In these examples, the record may indicate a second encrypted document obfuscation value associated with a second tile of the tile chain to which the information document has been registered.

FIG. 16 depicts a flowchart of another exemplary process associated with a user interface in accordance with the digital property authentication and management system. The order in which operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement process 1600.

At block 1602, the process 1600 may include causing display of a user interface including a first selectable portion indicating an option to enroll a trade secret in a trade secret registry. For example, the user interface may be caused to be displayed on a screen of the electronic device. The selectable portions may be displayed via the user interface in a manner such that the user may provide an input to select the first selectable portion. In an example, the first selectable part may include text such as "check-in," which may provide an indication of the function associated with the selection of the first selectable part.

At block 1604, the process 1600 may include receiving first input data indicating a selection of the first selectable portion. Input may be received via touch input on a screen of the electronic device and/or by tactile and/or audible input using, for example, a tool such as a mouse or keyboard.

At block 1606, process 1600 may include causing the display request to identify a second selectable portion of the document to be registered as the business secret. Causing the second selectable portion to be displayed may be the same as or similar to causing the first selectable portion to be displayed, as described with respect to block 1602.

At block 1608, the process 1600 may include receiving second input data identifying the document. For example, identification of the document may include input, such as a naming indicator of the document and/or selection of the document from a database of the electronic device displaying the user interface. The document can be identified and the electronic device can cause generation of a document obfuscation value corresponding to the document. For example, the obfuscation component may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic apparatus and/or a remote storage device accessible to the electronic apparatus. The obfuscation component may then generate a document obfuscation value corresponding to the document. In general, the obfuscation component may receive as input text data, image data, formatting data, and/or other data corresponding to a document, and may generate as output a document obfuscation value corresponding to the input. In an example, an electronic device may include a plurality of obfuscating components, each employing a different hashing algorithm. In these examples, each obfuscation component may output a different document obfuscation value for the same document.

At block 1610, the process 1600 may include causing display of an encrypted document obfuscation value associated with a tile of a blockchain in which an identifier of a document has been registered. The encrypted document obfuscation value may be part of a record, which may also include a record identifier, trade secret details, and/or transaction details. The record identifier may include a number and/or letter that identifies the record relative to the trade secret registry. For example, the details of the business secret may include a naming designator for the business secret, a description of the business secret, a naming designator for a document representing the business secret, and/or a tag generated as described elsewhere herein. The transaction details may include a status registered with the trade secret registry, a document obfuscation value, a block number associated with a block in which the trade secret is registered to the blockchain, an encrypted document obfuscation value (also described as a blockdocument obfuscation value), and/or a block timestamp. Other information that may be included in the record and displayed relative to the user interface may include insurance policy details, valuation details, and/or other information associated with the trade secret, as described more fully elsewhere herein.

Additionally or alternatively, the process 1600 may include causing display of a third selectable portion indicating a second option to acquire the insurance policy associated with the trade secret and receiving, via the user interface, a third input indicating selection of the third selectable portion. The process 1600 may also include causing display of one or more requests for information associated with at least one of an insurance policy or a trade secret based at least in part on receiving the third input. Further, one or more input fields configured to receive text input in response to one or more requests for information may be caused to be displayed. The process 1600 may also include receiving, via the user interface, text input for each of the one or more input fields and receiving an indication from the distributed ledger system associated with the insurer that the insurance policy has been issued. The process 1600 may also include causing insurance policy information associated with the insurance policy to be displayed via the user interface.

Additionally or alternatively, process 1600 may include causing display of input fields associated with the document via a user interface. In these examples, the input field may include at least one of a document name field, a document description field, and/or a tag field. The process 1600 may also include causing display, via the user interface, of a third selectable portion indicating a second option to automatically populate at least one of the input fields. The process 1600 may also include receiving, via the user interface, a third input indicating a selection of the third selectable portion and causing display of text in at least one of the input fields based at least in part on the third input.

Additionally or alternatively, the process 1600 may include receiving input data representing user input to manipulate text from an input field. The process 1600 may also include causing display of the manipulated text relative to the input field based at least in part on the fourth input data. The process 1600 may also include causing display of a fourth selectable portion via the user interface requesting confirmation of the manipulated text as displayed in the input field. The process 1600 may also include receiving, via the user interface, input data indicating a selection of the selectable portion and associating the manipulated text with an identifier of the document based at least in part on the input data.

Additionally or alternatively, process 1600 may include causing display, via the user interface, of a third selectable option indicating a second option to associate the information document with the trade secret. In these examples, the information document may indicate information associated with the value of the business secret. Process 1600 may also include receiving a third input identifying the information document using a third selectable portion of the user interface. Process 1600 may also include causing a value determined by the remote system based at least in part on the information document to be displayed via the user interface. In these examples, the record may indicate a second encrypted document obfuscation value associated with a second tile of the tile chain to which the information document has been registered.

Additionally or alternatively, process 1600 may include determining a characteristic of the document based at least in part on a document obfuscation value corresponding to the document and determining a type of business secret associated with the document based at least in part on the characteristic. Process 1600 may also include causing display of text indicating the type of trade secret via the user interface.

Additionally or alternatively, process 1600 may include causing display, via a user interface, of a commercial secret repository screen including a first identifier of a first document associated with an entity identifier, a second identifier of a second document associated with the entity identifier, and/or a search field configured to receive input to search for a record in a commercial secret registry associated with the entity identifier. The process 1600 may also include receiving third input data indicative of text entered into the search field and causing one or more of the records to be displayed via the user interface based at least in part on the text entered into the search field.

Additionally or alternatively, process 1600 may include causing display, via the user interface, a third selectable portion indicating a second option to verify that the second document corresponds to the first document. Process 1600 may also include receiving third input data indicating a selection of a third selected portion and causing a display request to identify a fourth selectable portion of the second document. The process 1600 may also include receiving fourth input data identifying a second document and causing display, via the user interface, of an indication that a first document confusion value associated with the first document has at least a threshold degree of similarity to a second document confusion value associated with the second document.

Additionally or alternatively, the process 1600 may include determining that a first document confusion value associated with a first document has at least a threshold degree of similarity to a second document confusion value associated with a second document, and associating the first document with the second document based at least in part on determining that the first document confusion value has at least the threshold degree of similarity to the second document confusion value. Process 1600 may also include causing display, via a user interface, of an indication that the first document has been associated with the second document.

Additionally or alternatively, the process 1600 may include determining that a similarity of a first document confusion value associated with the document to a document confusion value registered in association with the commercial secret registry is less than a threshold similarity, and determining that the document is unique relative to the commercial secret registry based at least in part on the similarity of the first document confusion value to the document confusion value being less than the threshold similarity. Process 1600 may also include causing an indication to be displayed via the user interface that the document is unique with respect to the trade secret registry.

Additionally or alternatively, the process 1600 may include causing display, via a user interface, of insurance policy information associated with an insurance policy issued for a trade secret. In these examples, the insurance policy information may include a payment value associated with an amount to be paid to an entity associated with the business secret at the time of the event. The process 1600 may also include receiving compliance data indicating that the entity is not in compliance with the conditions of the insurance policy and causing display, via the user interface, of updated insurance policy information including an updated payment value, the updated payment value being less than the payment value.

Additionally or alternatively, process 1600 may include causing display, via the user interface, of a second selectable portion indicating an option to verify that the second document is similar to the first document. Process 1600 may also include receiving second input data indicating a selection of a second selectable portion and causing a display request to identify a third selectable portion of a second document. The process 1600 may also include receiving third input data identifying a second document and causing display, via the user interface, of an indication that a first document confusion value associated with the first document has at least a threshold degree of similarity to a second document confusion value associated with the second document.

FIG. 17 sets forth a flow chart illustrating an exemplary process for digital property management including document version control. The order in which operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement process 1700.

At block 1702, the process 1700 may include storing, in association with a trade secret registry, a first record indicating: a first document obfuscation value corresponding to a first document representing a business secret; and an encrypted document obfuscation value generated based at least in part on the first document obfuscation value, the encrypted document obfuscation value representing a tile in a blockchain of the remote system. For example, a system associated with a trade secret registry may store records corresponding to trade secrets registered with the trade secret registry. These records may include information such as a document obfuscation value generated based at least in part on the document representing the business secret. The document obfuscation value may be generated by the user's electronic device and/or by a system associated with a trade secret registry. Additionally, the electronic device and/or system may request registration of the business secret and/or the document obfuscation value in association with the blockchain of the remote system. The remote system may register such business secrets and may generate encrypted document obfuscation values representing tiles of the tile chain.

At block 1704, the process 1700 may include receiving an indication that the first document represents a first version of the first document. For example, an indication may be received from an electronic device. In other examples, the system may determine that the first document represents the first version.

At block 1706, the process 1700 may include receiving input data from the electronic device requesting that the second document be registered in association with the trade secret registry. For example, a communication component of the electronic device may transmit data indicative of a request to register the second document in association with the trade secret registry.

At block 1708, the process 1700 may include receiving, from the electronic device, a second document obfuscation value corresponding to a second document. For example, the communication component can also send a document obfuscation value generated based at least in part on the second document. The obfuscation component may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic apparatus and/or a remote storage device accessible to the electronic apparatus. The obfuscation component may then generate a document obfuscation value corresponding to the document. In general, the obfuscation component may receive as input text data, image data, formatting data, and/or other data corresponding to a document, and may generate as output a document obfuscation value corresponding to the input. In an example, an electronic device may include a plurality of obfuscating components, each employing a different hashing algorithm. In these examples, each obfuscation component may output a different document obfuscation value for the same document.

At block 1710, the process 1700 may include determining that the second document corresponds to a second version of the first document based at least in part on a comparison of the first document confusion value and the second document confusion value. For example, the version control component may be configured to determine that two or more documents and/or business secrets are versions of the same document and/or business secret. For example, as described more fully above with respect to FIG. 1, the results from the comparison component may be used to determine that two documents are similar, but not identical, in one or more respects. The version control component may also receive, identify, determine, and/or generate information indicating that the two documents are associated with the same and/or related entity identifiers. The version control component may also receive, identify, determine, and/or generate information indicating that the two documents are associated with the same or similar type of business secret. With some or all of this information, the version control component can determine that the two documents are versions of the same document. An indication of this version control may be stored relative to the record associated with the document and/or a visual indication may be displayed via a user interface.

At block 1712, the process 1700 may include generating a second record that: an identifier indicating that the second document has been registered in association with the trade secret registry; indicating that the second document is a second version of the first document; and includes a selectable link that, when selected, causes the first record to be displayed. The record may include a record identifier, trade secret details, and/or transaction details. The record identifier may include a number and/or letter that identifies the record relative to the trade secret registry. For example, the details of the business secret may include a naming designator for the business secret, a description of the business secret, a naming designator for a document representing the business secret, and/or a tag generated as described elsewhere herein. The transaction details may include a status registered with the trade secret registry, a document obfuscation value, a block number associated with a block in which the trade secret is registered to the blockchain, an encrypted document obfuscation value (also described as a blockdocument obfuscation value), and/or a block timestamp. Other information that may be included in the record and displayed relative to the user interface may include insurance policy details, valuation details, and/or other information associated with the trade secret, as described more fully elsewhere herein.

Additionally or alternatively, the process 1700 may include storing first access control data indicating a first identifier of a first person allowed to access the first record. The process 1700 may also include storing second access control data indicating a second identifier of a second person allowed to access the second record. In these examples, the second access control data may indicate that access to the first record by the second person is not allowed. The process 1700 may also include receiving second input data requesting access to the second record, wherein the second input data indicates that the second person is requesting access to the second record. The process 1700 may also include causing display of a second record including the selectable link based at least in part on the second input data. The process 1700 may also include receiving third input data corresponding to a selection of the selectable link and refraining from causing display of the first record based at least in part on the second access control data indicating that access to the first record is not allowed.

Additionally or alternatively, process 1700 may include associating the business secret with the insurance policy using an intelligent contract associated with the blockchain, wherein the intelligent contract indicates a condition for validating the insurance policy. The process 1700 may also include receiving validation data from the electronic device indicating that the condition has been met and transmitting the validation data to a remote system associated with the insurer, wherein the validation data causes the intelligent contract to validate the insurance policy. Process 1700 may also include receiving confirmation data from the remote system indicating that the insurance policy has been validated with the smart contract.

Additionally or alternatively, the process 1700 may include receiving valuation data from the electronic device that is indicated as relating to the value of the trade secret. The process 1700 may also include receiving, from the electronic device, a third document obfuscation value corresponding to the evaluation data, and receiving, from at least one of the electronic device or a remote system, a second encrypted document obfuscation value generated based at least in part on the third document obfuscation value. In these examples, the second encrypted document obfuscation value may represent a second tile in the tile chain. Additionally, the first record may include a third document obfuscation value and a second encrypted document obfuscation value.

Additionally or alternatively, the process 1700 may include associating the first feature vector with the first document based at least in part on first text data associated with the first document. The process 1700 may also include associating a second feature vector with the second document based at least in part on second text data associated with the second document. The process 1700 may also include determining that a distance between the first feature vector and the second feature vector is less than a threshold distance. In these examples, determining that the second document corresponds to the second version of the first document may be based, at least in part, on a distance that is less than a threshold distance. In other examples, the process 1700 may include determining a number of other feature vectors within a threshold distance from the first feature vector and determining a popularity score associated with the first document based at least in part on the number of other feature vectors.

Additionally or alternatively, the process 1700 may include receiving an indication of a type of commercial secret associated with the commercial secret and identifying a frequency with which a version of the commercial secret associated with the type of commercial secret is registered with a commercial secret registry. The process 1700 may also include generating a version registration alert based at least in part on the frequency and transmitting alert data representative of the version registration alert to the electronic device.

Additionally or alternatively, the process 1700 can include determining a frequency of registering a version of the business secret at the business secret registry with at least one of the electronic device or an entity identifier corresponding to an entity associated with the electronic device. The process 1700 may also include generating a version registration alert based at least in part on the frequency and transmitting alert data representative of the version registration alert to the electronic device.

FIG. 18 shows a flowchart of an exemplary process for digital property management including trade secret valuation. The order in which operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement process 1800.

At block 1802, process 1800 may include storing a record in association with the trade secret registry, the record indicating: a first document obfuscation value corresponding to a document representing a business secret; and a first encrypted document obfuscation value generated based at least in part on the first document obfuscation value, the first encrypted document obfuscation value representing a first tile in a blockchain of the remote system. For example, a system associated with a trade secret registry may store records corresponding to trade secrets registered with the trade secret registry. These records may include information such as a document obfuscation value generated based at least in part on the document representing the business secret. The document obfuscation value may be generated by the user's electronic device and/or by a system associated with a trade secret registry. Additionally, the electronic device and/or system may request registration of the business secret and/or the document obfuscation value in association with the blockchain of the remote system. The remote system may register such business secrets and may generate encrypted document obfuscation values representing tiles of the tile chain.

At block 1804, the process 1800 may include receiving, from the electronic device, valuation data that is indicated as relating to the value of the business secret. For example, a user interface of the electronic device may include a selectable portion that indicates an option for determining a value of the trade secret. Based at least in part on the selection of the selectable portion, the user interface may display a series of dialog boxes and/or input fields requesting information associated with determining the value of the trade secret. For example, the valuation component can be configured to identify and/or determine a value associated with a given business secret. The information requested by the input field may include, for example, the type of the trade secret, the importance of the trade secret to the entity, the entity revenue, the entity value, the trade secret creation date, and the like.

In other examples, tag data generated as described herein may be used to determine some or all of the data described herein for determining the value of a business secret. For example, the tag data may be used to determine a type of commercial secret. Business secrets of the same or similar type may be analyzed to determine the value of the business secret in question.

At block 1806, the process 1800 may include receiving a second document obfuscation value corresponding to the evaluation data from the electronic device. A document obfuscation value may be generated based at least in part on the evaluation data and may be generated using an obfuscation component as described elsewhere herein.

At block 1808, the process 1800 may include receiving, from at least one of the electronic device or the remote system, a second encrypted document obfuscation value generated based at least in part on a second document obfuscation value, the second encrypted document obfuscation value representing a second tile in the tile chain. In these examples, the record may include the second document obfuscation value and the second encrypted document obfuscation value. By doing so, estimation data can be registered with the block chain, which can provide support for estimation determinations at a given time.

Additionally or alternatively, process 1800 may include receiving an indication that the first document represents a first version of the first document and receiving input data from the electronic device requesting that the second document be registered in association with the trade secret registry. The process 1800 may also include receiving, from the electronic device, a third document confusion value corresponding to the second document and determining that the second document corresponds to the second version of the first document based at least in part on a comparison of the first document confusion value and the third document confusion value. Process 1800 may also include generating a second record indicating that an identifier of the second document has been registered in association with the trade secret registry and indicating that the second document corresponds to a second version of the first document.

Additionally or alternatively, the process 1800 may include storing first access control data indicating a first identifier of a first person allowed to access the first portion of the record. Process 1800 may also include storing second access control data indicating a second identifier of a second person allowed to access a second portion of the record. In these examples, the second access control data may indicate that access to the first portion by the second person is not allowed. The process 1800 may also include receiving second input data requesting access to the second portion, where the second input data indicates that the second person is requesting access to the second record. Process 1800 may also include causing display of the second portion based at least in part on the second input data. Process 1800 may also include receiving third input data requesting access to the first portion of the record by the second person and refraining from causing the first portion to be displayed based at least in part on the second access control data indicating that access to the first portion is not allowed.

Additionally or alternatively, process 1800 may include associating the business secret with the insurance policy using an intelligent contract associated with the blockchain, where the intelligent contract indicates a condition for validating the insurance policy. Process 1800 may also include receiving validation data from the electronic device indicating that the condition has been met and sending the validation data to a remote system associated with the insurer, wherein the validation data causes the intelligent contract to validate the insurance policy. Process 1800 may also include receiving confirmation data from the remote system indicating that the insurance policy has been validated with the intelligent contract.

FIG. 19 shows a flowchart of an exemplary process for digital property management including access control. The order in which the operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the process 1900.

At block 1902, the process 1900 may include storing first access control data indicating: a first identifier of a first person allowed to access a record associated with a trade secret registry, the record indicating a trade secret registered in association with the trade secret registry; and a function of a trade secret registry authorizing use of the first person. For example, the first access control data may be stored in association with a remote system. The access control data may indicate who is authorized to view a given record and/or given information associated with the record. In these examples, for example, a user accessing the record may need to authenticate the user's identity, such as by entering a username and/or password. For example, the functionality may include the ability to view information, manipulate information, alter access controls, and the like.

At block 1904, the process 1900 may include storing second access control data indicating: a second identifier of a second person allowed to access the record; and the second person is not authorized to use the function. The second access control data may be stored in the same or similar manner as the first access control data.

At block 1906, the process 1900 may include receiving first input data requesting access to the record, the first input data indicating that a second person is requesting access to the record. The first input data may be received from an electronic device displaying a user interface that allows a user to input authentication information to gain access to information associated with a trade secret registry.

At block 1908, the process 1900 may include causing display of the record based at least in part on the first input data. For example, assuming that the second access control data indicates that the second person is authorized to view the record, the record may be allowed to be displayed.

At block 1910, process 1900 may include receiving second input data requesting use of the function. For example, the second person may provide input to a user interface of the electronic device to manipulate information associated with the record, such as one or more tags associated with the record.

At block 1912, the process 1900 may include refraining from causing the function to be performed based at least in part on the second access control data indicating that the second person is not authorized to use the function. For example, assuming that the second access control data indicates that the second person is not authorized to utilize the functions, upon receiving input data requesting use of the functions, the system may determine that such request cannot be performed based at least in part on the second access control data.

Additionally or alternatively, the process 1900 can include receiving an indication that the first trade secret represents a first version of the first trade secret and receiving input data from the electronic device requesting registration of a second trade secret in association with the trade secret registry. Process 1900 may also include receiving a document obfuscation value corresponding to a second business secret from the electronic device and determining that the second business secret corresponds to a second version of the first business secret based at least in part on a comparison of the document obfuscation values. Process 1900 may also include generating a second record indicating that an identifier of the second commercial secret has been registered in association with the commercial secret registry and indicating that the second commercial secret corresponds to the second version of the first commercial secret.

Additionally or alternatively, process 1900 can include receiving valuation data from the electronic device that is indicated as relating to the value of the trade secret. The process 1900 can also include receiving a document obfuscation value corresponding to the evaluation data from the electronic device and receiving an encrypted document obfuscation value generated based at least in part on the document obfuscation value from at least one of the electronic device or the remote system. In these examples, the encrypted document obfuscation value may represent a tile in a tile chain. Additionally, the record may include a document obfuscation value and an encrypted document obfuscation value.

Additionally or alternatively, process 1900 can include associating the business secret with the insurance policy using an intelligent contract associated with the blockchain, wherein the intelligent contract indicates a condition for validating the insurance policy. The process 1900 can also include receiving attestation data from the electronic device indicating that the condition has been met and transmitting the attestation data to the remote system. The validation data may cause the smart contract to validate the insurance policy. Process 1900 may also include receiving confirmation data from the remote system indicating that the insurance policy has been validated with the smart contract.

Additionally or alternatively, the process 1900 can include generating a log of accesses to records by one or more electronic devices. The log may indicate identifiers of individual ones of the persons accessing the record and/or time values at which individual ones of the persons accessed the record. The process 1900 can also include receiving an indication that the first access control data associated with the first person has been removed and generating alert data. The alert data may indicate that the first person has accessed the record and one or more time values at which the first person accessed the record. The alert data may also request confirmation that the first person has experienced an out-of-title interview associated with the trade secret.

Additionally or alternatively, the process 1900 can include generating a log of accesses to records by one or more electronic devices. The log may indicate identifiers of individual ones of the persons accessing the record and/or time values at which individual ones of the persons accessed the record. The process 1900 can also include generating a compliance schedule associated with the insurance policy relating to the trade secret based at least in part on the log. The compliance schedule may indicate a period of time during which the first person may perform compliance with the policy conditions. The process 1900 may also include determining that the condition is not satisfied before the expiration of the time period and adjusting the payment value associated with the insurance policy based at least in part on determining that the condition is not satisfied.

Additionally or alternatively, process 1900 can include generating an interface to the trade secret registry configured to allow access to at least a portion of the trade secret registry via a remote archiving system associated with the intellectual property asset. Process 1900 may also include sending access information for the interface to a remote archival system and receiving a request from the remote archival system to perform a search of the trade secret registry. The request may include text data for searching a trade secret registry. Process 1900 may also include identifying search results and transmitting result data representing the results to a remote archiving system.

Additionally or alternatively, the process 1900 can include generating a log of accesses of the record by the one or more electronic devices and determining, based at least in part on the log, that the number of times the record has been accessed during the period of time exceeds a threshold number of times. Process 1900 may further include generating an alert indicative of abnormal activity with respect to the record based at least in part on determining that the number of times the record has been accessed during the time period exceeds a threshold number of times. The process 1900 can also include sending alert data representing an alert to an electronic device associated with the record.

FIG. 20 shows a flowchart of an exemplary process for valuing an asset in accordance with a digital asset authentication and management system. The order in which the operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the process 2000.

At block 2002, the process 2000 may include storing a record in association with the trade secret registry, the record indicating: a document obfuscation value corresponding to a document representing a business secret; and an encrypted document obfuscation value generated based at least in part on the document obfuscation value, the encrypted document obfuscation value representing a tile in a tile chain of the remote system. For example, a system associated with a trade secret registry may store records corresponding to trade secrets registered with the trade secret registry. These records may include information such as a document obfuscation value generated based at least in part on the document representing the business secret. The document obfuscation value may be generated by the user's electronic device and/or by a system associated with a trade secret registry. Additionally, the electronic device and/or system may request registration of the business secret and/or the document obfuscation value in association with the blockchain of the remote system. The remote system may register such business secrets and may generate encrypted document obfuscation values representing tiles of the tile chain.

At block 2004, process 2000 may include identifying tag data indicative of a characteristic associated with the document. For example, the tag data generator may be configured to generate tag data associated with a document. For example, one or more input fields may be caused to be displayed via a user interface. The input field may include a request to "tag" or otherwise provide a keyword for the document. For example, a document corresponding to source code for operating a sewing machine may be associated with a keyword such as "source code", "sewing machine", "version 1.1.20", and the like. A user of the electronic device can input text corresponding to the tags, and the tag data generator can utilize such input to generate the tag data. Additionally or alternatively, the tag data generator may automatically generate the tag data. For example, the tag data generator may analyze a document to be registered in association with a trade secret registry to identify keywords associated with the document. For example, the tag data generator may identify one or more fields of the document and/or values associated with the fields. By way of illustration, the tag data generator can identify a title field, a document type field, one or more sections of a document, and/or the like. The values associated with these fields (such as text data) may be used to generate the tags. Additionally or alternatively, the text data of the document may be analyzed to determine which words are common in the document. These words may be recognized as keywords and may be used to generate tag data.

At block 2006, the process 2000 may include receiving, from the electronic device, valuation data that is indicated as being related to the value of the trade secret. For example, a user interface of the electronic device may include a selectable portion that indicates an option for determining a value of the trade secret. Based at least in part on the selection of the selectable portion, the user interface may display a series of dialog boxes and/or input fields requesting information associated with determining the value of the trade secret. For example, the valuation component can be configured to identify and/or determine a value associated with a given business secret. The information requested by the input field may include, for example, the type of the trade secret, the importance of the trade secret to the entity, the entity revenue, the entity value, the trade secret creation date, and the like.

At block 2008, the process 2000 may include determining a value of the business secret based at least in part on the tag data and the evaluation data. For example, the valuation component can utilize some or all of the information described with respect to block 2006 to determine the value of the business secret.

At block 2010, the process 2000 may include causing an indication of the value to be displayed via a user interface accessible to the electronic device. For example, valuation details can be generated and stored in association with a record corresponding to a business secret. Valuation details can include the determined value, the type of business secret, the creation date, the entity value, and/or the revenue value. Additionally, if supporting documents are provided to assist in valuation determination, selectable links to those documents may also be displayed with the record.

Additionally or alternatively, the process 2000 may include receiving entity value data from at least one of the electronic device or another device, the entity value data indicating at least one of an entity value of an entity associated with the document or a revenue and/or revenue value of the entity. In these examples, determining the value of the business secret may be based at least in part on the entity value data.

Additionally or alternatively, process 2000 may include utilizing a time value associated with registration of a tile in the chain of tiles in determining the value of the trade secret. In these examples, the value may increase as the period of time between the time value and the current time increases (continuously, periodically, on a scheduled basis, or randomly).

Additionally or alternatively, process 2000 may include receiving, from the remote system, a second encrypted document obfuscation value generated based at least in part on a second document obfuscation value corresponding to financial data associated with the business secret. The second encrypted document obfuscation value may represent a second tile in the tile chain of the remote system. In these examples, determining the value of the trade secret may be based at least in part on receiving the second encrypted document obfuscation value.

FIG. 21 shows a flowchart of an exemplary process for providing an insurance policy in accordance with the digital property authentication and management system. The order in which operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement process 2100.

At block 2102, process 2100 can include storing a record in association with the trade secret registry, the record indicating: a document obfuscation value corresponding to a document representing a business secret; and an encrypted document obfuscation value generated based at least in part on the document obfuscation value, the encrypted document obfuscation value representing a tile in a blockchain of the enrollment system. These records may include information such as a document obfuscation value generated based at least in part on the document representing the business secret. The document obfuscation value may be generated by the user's electronic device and/or by a system associated with a trade secret registry. Additionally, the electronic device and/or system may request registration of the business secret and/or the document obfuscation value in association with the blockchain of the remote system. The remote system may register such business secrets and may generate encrypted document obfuscation values representing tiles of the tile chain.

At block 2104, process 2100 can include identifying tag data indicative of a characteristic associated with the document. For example, the tag data generator may be configured to generate tag data associated with a document. For example, one or more input fields may be caused to be displayed via a user interface. The input field may include a request to "tag" or otherwise provide a keyword for the document. For example, a document corresponding to source code for operating a sewing machine may be associated with a keyword such as "source code", "sewing machine", "version 1.1.20", and the like. A user of the electronic device can input text corresponding to the tags, and the tag data generator can utilize such input to generate the tag data. Additionally or alternatively, the tag data generator may automatically generate the tag data. For example, the tag data generator may analyze a document to be registered in association with a trade secret registry to identify keywords associated with the document. For example, the tag data generator may identify one or more fields of the document and/or values associated with the fields. By way of illustration, the tag data generator can identify a title field, a document type field, one or more sections of a document, and/or the like. The values associated with these fields (such as text data) may be used to generate the tags. Additionally or alternatively, the text data of the document may be analyzed to determine which words are common in the document. These words may be recognized as keywords and may be used to generate tag data.

At block 2106, process 2100 may include receiving input data from the electronic device requesting issuance of an insurance policy associated with the business secret. For example, the electronic device may display a user interface that may include a selectable portion indicating options for applying for or otherwise obtaining an insurance policy. Upon selection of the selectable portion, input data may be generated indicating that the user has selected an option to apply for the insurance policy.

At block 2108, process 2100 may include generating a policy request indicating: the trade secret has been registered with a trade secret registry; encrypting the document obfuscation value; and at least a portion of the tag data. For example, the policy component may be configured to assist in providing one or more policies for a given trade secret. The user interface may display one or more dialog boxes and/or input fields configured to receive user input regarding providing an insurance policy. This information may include, for example, the type or category of the trade secret, the value of the trade secret (determined from above or identified by the user), the warranty period, the value of the entity, the date the trade secret was created, and/or the portion of the document requested and/or the supporting document that was made available for upload. In an example of providing a support document, the support document may be registered with the blockchain in the same or similar manner as described above with respect to the support document for business secret valuation.

At block 2110, the process 2100 may include sending an insurance policy request to a distributed ledger system associated with the insurer. For example, the policy component and/or the communication component can be configured to receive input data corresponding to user input and can transmit the input data to a distributed ledger system associated with an insurer. The distributed ledger system can process the input data and, in an example, issue a policy, for example, to ensure that trade secrets are not compromised.

At block 2112, the process 2100 may include receiving an indication from the distributed ledger system that an insurance policy has been issued. In these examples, confirmation data indicating that a policy has been issued and information associated with the policy may be received from the distributed ledger system. This information may be incorporated into a record associated with the business secret and may be displayed via a user interface in an example. Some non-limiting examples of information associated with a policy may include a policy type, an obligation limit, a reserve value, a policy premium, a policy form, a policy number, a policy life, an obligation share limit, and/or an estimate of a trade secret. Additionally or alternatively, the information may include a payment value associated with an amount to be paid to an entity associated with the business secret at the time of the event. In these examples, the policy component may receive compliance data indicating that the entity is not in compliance with the conditions of the insurance policy and may cause display of updated insurance policy information, including the updated payment value. In these examples, the updated payment value may be less than the original payment value. When the condition is satisfied, the payment value may be updated to reflect compliance with the policy condition.

At block 2114, the process 2100 can include causing display of an indication that the insurance policy has been issued via a user interface accessible to the electronic device. For example, information associated with the policy may be incorporated into a record associated with the trade secret and may be displayed via a user interface in an example.

Additionally or alternatively, process 2100 can include generating a log of accesses to records by one or more electronic devices. The log may indicate identifiers of individual ones of the persons accessing the record and/or time values at which individual ones of the persons accessed the record. The process 2100 can also include generating a compliance schedule associated with the insurance policy based at least in part on the log. The compliance schedule may indicate a period of time during which at least one of the persons may perform compliance with the policy conditions. The process 2100 may also include determining that the condition is not satisfied prior to expiration of the time period and adjusting a payment value associated with the insurance policy based at least in part on determining that the condition is not satisfied. The process 2100 can also include generating alert data indicative of the condition not being met based at least in part on determining that the condition is not met and transmitting the alert data to one or more electronic devices. In these examples, the alert data may cause the processor of the one or more electronic devices to launch an application and display an alert corresponding to the alert data.

Additionally or alternatively, process 2100 may include receiving, from the remote system, a second encrypted document obfuscation value generated based at least in part on a second document obfuscation value corresponding to financial data associated with the business secret. The second encrypted document obfuscation value may represent a second tile in the tile chain of the remote system. In these examples, the policy request may include the second encrypted document obfuscation value and/or an indication thereof.

Additionally or alternatively, process 2100 can include determining a value of the trade secret based at least in part on the record. In these examples, the insurance policy request includes the value of the trade secret.

FIG. 22 shows a flowchart of an exemplary process for asset verification in accordance with a digital asset authentication and management system. The order in which operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement process 2200.

At block 2202, process 2200 may include storing a record in association with the trade secret registry, the record indicating: a first document obfuscation value corresponding to a first document representing a business secret; and an encrypted document obfuscation value generated based at least in part on the first document obfuscation value, the encrypted document obfuscation value representing a tile in a blockchain of the remote system. These records may include information such as a document obfuscation value generated based at least in part on the document representing the business secret. The document obfuscation value may be generated by the user's electronic device and/or by a system associated with a trade secret registry. Additionally, the electronic device and/or system may request registration of the business secret and/or the document obfuscation value in association with the blockchain of the remote system. The remote system may register such business secrets and may generate encrypted document obfuscation values representing tiles of the tile chain.

At block 2204, process 2200 may include receiving a second document from the electronic device that is indicated to have been compromised. For example, the commanded document may be identified, such as via a user interface of the electronic device.

At block 2206, process 2200 may include receiving input data from the electronic device requesting verification that the second document corresponds to a registered document registered with respect to the trade secret registry. Input data may be received from an electronic device displaying a user interface.

At block 2208, process 2200 may include generating, based at least in part on the second document, a second document obfuscation value corresponding to the second document. For example, a document obfuscation value may be generated for the directed document in the same or similar manner as described above with respect to the obfuscation component. The verification component may be operative to analyze the document confusion value of the commanded document relative to other document confusion values of the registered documents.

At block 2210, process 2200 may include determining a similarity between the first document confusion value and the second document confusion value. For example, the comparison component may be configured to analyze the document confusion value and determine a similarity and/or a difference between the document confusion value and/or the documents corresponding to the document confusion value. In other examples, the feature vectors may be associated with some or all of the document obfuscation values. The feature vector may correspond to a document obfuscation value and/or a characteristic of the document. For example, the presence or absence of text data and/or image data from a document may affect the feature vectors. In other examples, the text data and/or the image data itself may affect the feature vectors. Other factors such as document length, entity associated with the document, creation date, modification date, and/or other metadata may affect the feature vector. For example, a feature may be described as an individual measurable property or characteristic of a document. The given feature may be a number and/or may be considered a string and/or a graphic. A set of such features may be described as a feature vector. Thus, similar feature vectors indicate similar characteristics and/or properties of the documents they represent.

At block 2212, the process 2200 may include determining that the similarity is greater than a threshold similarity. For example, a threshold similarity may be identified and/or determined and the similarity between document confusion values may be compared to the threshold similarity. Document confusion values with a similarity that meets or exceeds a threshold similarity may be determined to be similar, while hash value pairs below the threshold similarity may be determined to be dissimilar. Additionally, the document obfuscation value may be segmented and the segments may be compared to determine similar and dissimilar portions of the document obfuscation value. The number of similar and dissimilar document confusion values may be used to determine an overall similarity between the document confusion values. For another example, process 2200 may include determining that a levenson distance between a first characteristic of the first document and a second characteristic of the second document is less than a threshold levenson distance.

At block 2214, the process 2200 may include determining that the second document corresponds to the first document based at least in part on the similarity being greater than the threshold similarity. The verification component may determine that the directed document is the same as or similar to the registered document if the verification component determines that at least one of the registered document confusion values matches the document confusion value of the directed document. In other examples, the verification component may determine a similarity between the commanded document and one or more registered documents. In these examples, the directed document may be determined to be similar to the registered document when the similarity meets or exceeds a threshold similarity. In other examples, the verification component may be configured to determine which portions of the commanded document match or are similar to the at least one registered document. An indication of the matching or similar portion may be displayed, such as via a user interface. Additionally, where multiple versions of a document have been registered, the validation component may be configured to determine which of the multiple versions is most similar to the commanded document, and may provide an indication of the most similar version.

Additionally or alternatively, process 2200 may include sending a request to a remote system associated with the blockchain to identify a second encrypted document obfuscation value corresponding to a second document and/or a second hash corresponding to the second document. Process 2200 may also include receiving a second encrypted document obfuscation value and determining that the first encrypted document obfuscation value corresponds to the second encrypted document obfuscation value. In these examples, determining that the second document corresponds to the first document may be based at least in part on the first encrypted document obfuscation value corresponding to a second encrypted document obfuscation value.

FIG. 23 depicts a flowchart of another exemplary process for asset verification in accordance with a digital asset authentication and management system. The order in which operations or steps are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement process 2300.

At block 2302, process 2300 can include storing a record indicating: a first document obfuscation value corresponding to a first document representing a business secret; and an encrypted document obfuscation value generated based at least in part on the first document obfuscation value, the encrypted document obfuscation value representing a tile in a blockchain of the remote system. These records may include information such as a document obfuscation value generated based at least in part on the document representing the business secret. The document obfuscation value may be generated by the user's electronic device and/or by a system associated with a trade secret registry. Additionally, the electronic device and/or system may request registration of the business secret and/or the document obfuscation value in association with the blockchain of the remote system. The remote system may register such business secrets and may generate encrypted document obfuscation values representing tiles of the tile chain.

At block 2304, process 2300 can include receiving a second document from the electronic device that is indicated as having been compromised. For example, the commanded document may be identified, such as via a user interface of the electronic device.

At block 2306, the process 2300 may include generating a second document obfuscation value corresponding to the second document based at least in part on the second document. For example, a document obfuscation value may be generated for the directed document in the same or similar manner as described above with respect to the obfuscation component. The verification component may be operative to analyze the document confusion value of the commanded document relative to other document confusion values of the registered documents.

At block 2308, the process 2300 may include determining a similarity between the first document confusion value and the second document confusion value. For example, the comparison component may be configured to analyze the document confusion value and determine a similarity and/or a difference between the document confusion value and/or the documents corresponding to the document confusion value. In other examples, the feature vectors may be associated with some or all of the document obfuscation values. The feature vector may correspond to a document obfuscation value and/or a characteristic of the document. For example, the presence or absence of text data and/or image data from a document may affect the feature vectors. In other examples, the text data and/or the image data itself may affect the feature vectors. Other factors such as document length, entity associated with the document, creation date, modification date, and/or other metadata may affect the feature vector. For example, a feature may be described as an individual measurable property or characteristic of a document. The given feature may be a number and/or may be considered a string and/or a graphic. A set of such features may be described as a feature vector. Thus, similar feature vectors indicate similar characteristics and/or properties of the documents they represent.

At block 2310, process 2300 can include determining that the second document corresponds to the first document based at least in part on the similarity. The verification component may determine that the directed document is the same as or similar to the registered document if the verification component determines that at least one of the registered document confusion values matches the document confusion value of the directed document. In other examples, the verification component may determine a similarity between the commanded document and one or more registered documents. In these examples, the directed document may be determined to be similar to the registered document when the similarity meets or exceeds a threshold similarity. In other examples, the verification component may be configured to determine which portions of the commanded document match or are similar to the at least one registered document. An indication of the matching or similar portion may be displayed, such as via a user interface. Additionally, where multiple versions of a document have been registered, the validation component may be configured to determine which of the multiple versions is most similar to the commanded document, and may provide an indication of the most similar version.

Additionally or alternatively, process 2300 can include sending a request to a remote system associated with the blockchain to identify a second encrypted document obfuscation value corresponding to a second document and/or a second hash corresponding to the second document. The process 2300 may also include receiving a second encrypted document obfuscation value and determining that the first encrypted document obfuscation value corresponds to the second encrypted document obfuscation value. In these examples, determining that the second document corresponds to the first document may be based at least in part on the first encrypted document obfuscation value corresponding to a second encrypted document obfuscation value.

Additionally or alternatively, process 2300 can include storing a second record associated with the second version of the first document, wherein the second record can be associated with the first record based at least in part on the second record associated with the second version of the first document. Process 2300 can also include determining a second similarity between a third document obfuscation value corresponding to a second version of the first document and the second document obfuscation value. In these examples, determining that the second document corresponds to the first document may include determining that the second document corresponds to a second version of the first document based at least in part on the second similarity.

Additionally or alternatively, the process 2300 can include causing a series of dialog boxes to be displayed via a user interface of the electronic device. Causing display of the series of dialog boxes may be based at least in part on determining that the second document corresponds to the first document. In these examples, the series of dialog boxes may include text associated with submitting an insurance coverage claim in association with an insurance policy for the trade secret. The process 2300 can also include receiving input data including a response to the text and sending at least one of the input data and/or a claim notice to a distributed ledger system associated with the insurer. The process 2300 can also include receiving status data from the distributed ledger system indicating that information is requested to process a claim. The process 2300 can also include sending an alert to the electronic device indicating that information is requested, wherein the alert includes the selectable portion. The process 2300 can also include causing a request for information to be displayed via the user interface and based at least in part on receiving an indication that the selectable portion has been selected.

Additionally or alternatively, process 2300 may include determining a first portion of the first document obfuscation value corresponding to a second portion of the second document obfuscation value and identifying a third portion of the first document corresponding to the first portion of the first document obfuscation value. Process 2300 can also include causing display, via the user interface and based at least in part on identifying the third portion, of an indication that the third portion of the first document is similar to at least a portion of the second document.

Although the foregoing invention has been described with respect to specific examples, it should be understood that the scope of the invention is not limited to these specific examples. Since other modifications and changes varied to fit particular operating requirements and environments will be apparent to those skilled in the art, the invention is not considered limited to the examples selected for purposes of disclosure, but rather covers all changes and modifications which do not constitute departures from the true spirit and scope of the invention.

Although the present application describes embodiments with particular structural features and/or methodological acts, it is to be understood that the claims are not necessarily limited to the particular features or acts described. Rather, the specific features and acts are merely illustrative of some embodiments that fall within the scope of the claims.

Embodiments of the present disclosure may be described in view of the following clauses.

1. A method, comprising: receiving, at an electronic device, a document representing a business secret; receiving an input at the electronic device indicating that the document is to be registered at a trade secret registry associated with a registration system remote from the electronic device; generating a document obfuscation value representative of the document based at least in part on receiving the input; sending, from the electronic device, the document obfuscation value and a first request to generate a tile in a blockchain associated with a distributed ledger system that is at least remote from the electronic device; receiving, at the electronic device, a tile value representing the tile in the chain of tiles from the distributed ledger system; sending, from the electronic device and to the enrollment system, a second request to enroll the document with respect to the trade secret registry; generating, by the enrollment system, a record in the trade secret enrollment, the record: indicating that the trade secret has been registered in the trade secret registry; including the block value; and indicating a time value associated with at least one of the generation of the chunk value or the generation of the record; generating confirmation data indicating that the record has been generated; and transmitting the confirmation data from the registration system to the electronic device.

2. The method of clause 1, wherein the document obfuscation value comprises a first document obfuscation value, and the method further comprises: identifying a first portion of the document and a second portion of the document; generating a second document obfuscation value representing the first portion of the document; generating a third document obfuscation value representing the second portion of the document; and wherein generating the first document obfuscation value comprises generating the first document obfuscation value based at least in part on the second document obfuscation value and the third document obfuscation value.

3. The method of

clause

1 or 2, wherein the block comprises a first block, the blockchain comprises a first blockchain, the blockvalue comprises a first blockvalue, the time value comprises a first time value, and the method further comprises: sending, from the electronic device and to an insurer system, the document obfuscation value and a third request to generate a second tile in a second chain of tiles associated with the insurer system; receiving, at the electronic device and from the insurer system, a second block value representing the second block in the second block chain; sending the second block value from the electronic device and to the registration system; and wherein the recording of the trade secret registry is: associating the second chunk value with the commercial secret; and indicating a second time value associated with the generation of the second tile value.

4. The method of

clause

1, 2 or 3, further comprising: generating tag data indicative of properties associated with the document, the properties including at least one of: an identifier of at least one of a title, a type of business secret, or a person or entity associated with the document; storing the tag data in a database associated with the enrollment system, the tag data associated with the business secret; receiving, at the electronic device, input data requesting a search for a trade secret associated with the trade secret registry, the input data including a search term; and causing searching of the tag data for the search term based at least in part on receiving the input data.

5. The method of

clause

1, 2, 3, or 4, wherein generating the document obfuscation value comprises generating the document obfuscation value based at least in part on a cryptographic hash.

6. A system, comprising: one or more processors; and a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving a document representing digital property; receiving input indicating that the document is to be registered at a digital property registry associated with a registration system; generating a document obfuscation value representative of the document based at least in part on receiving the input; sending the document obfuscation value and a request to the registration system to register the digital property in association with the digital property registry; and receiving acknowledgement data from the registration system, the acknowledgement data indicating: the digital property has been registered in association with the digital property registry; and the digital property has been associated with a blockvalue that represents a block in a blockchain associated with the distributed ledger system.

7. The system of clause 6, wherein the document obfuscation value comprises a first document obfuscation value, and the operations further comprise: identifying a first portion of the document and a second portion of the document; generating a second document obfuscation value representing the first portion of the document; generating a third document obfuscation value representing the second portion of the document; and wherein generating the first document obfuscation value comprises generating the first document obfuscation value based at least in part on the second document obfuscation value and the third document obfuscation value.

8. The system of clause 6 or 7, wherein the block comprises a first block, the blockchain comprises a first blockchain, the blockvalue comprises a first blockvalue, the distributed ledger system comprises a first distributed ledger system, and the validation data indicates that the digital property has been associated with a second blockvalue, the second blockvalue representing a second block in a second blockchain associated with a second distributed ledger system.

9. The system of clause 6, 7 or 8, wherein the document obfuscation value comprises a first document obfuscation value, the tile comprises a first tile, the tile chain comprises a first tile chain, the tile value comprises a first tile value, the distributed ledger system comprises a first distributed ledger system, generating the first document obfuscation value comprises generating the first document obfuscation value using a first hash value generator, and the operations further comprise: generating a second document obfuscation value representing the document based at least in part on receiving the input, the second document obfuscation value being generated using a second hash value generator that is different from the first hash value generator; sending the second document obfuscation value to the registration system; and wherein the validation data indicates that the digital property has been associated with a second tile value associated with the second document obfuscation value, the second tile value representing a second tile in a second chain of tiles associated with a second distributed ledger system.

10. The system of clause 6, 7, 8, or 9, wherein the input comprises a first input, and the operations further comprise: receiving a second input indicative of at least one of: identification information of at least one of a title associated with the document, a type of business secret associated with the document, or a person or entity associated with the document; generating label data based at least in part on the second input; storing the tag data; receiving a third input requesting a search of the digital property registry, the third input comprising a search term; causing the tag data to be searched based at least in part on the search term; and generating response data indicative of results of the search of at least the tag data.

11. The system of clause 6, 7, 8, 9, or 10, the operations further comprising: identifying fields of the document, each of the fields being associated with a field type; identifying field values associated with the respective ones of the fields; and generating tag data associated with the document, the tag data generated based at least in part on the field type and the field value for the respective ones of the fields.

12. The system of clause 6, 7, 8, 9, 10, or 11, the operations further comprising: storing security rules associated with a firewall; and wherein: sending the document obfuscation value and the request comprises sending the document obfuscation value and the request via the firewall and based at least in part on the security rule allowing transmission of the document obfuscation value and the request to the registration system; and receiving the confirmation data comprises receiving the confirmation data via the firewall and based at least in part on the security rules that allow the confirmation data to be received from the check-in system.

13. The system of clause 6, 7, 8, 9, 10, 11, or 12, wherein the document comprises a first document, the document obfuscation value comprises a first document obfuscation value, and the operations further comprise: receiving input data requesting verification that a second document corresponds to the first document; generating a second document obfuscation value corresponding to the second document based at least in part on the second document; determining that the first document confusion value corresponds to the second document confusion value; and determining that the second document corresponds to the first document based at least in part on the first document obfuscation value corresponding to the second document obfuscation value.

14. A method, comprising: receiving, from an electronic device, a document obfuscation value representing a document corresponding to digital property; receiving input data indicating that the digital property is to be registered in a digital property registry; sending the document obfuscation value to a distributed ledger system and a request to generate a block in a block chain associated with the distributed ledger system; receiving, from the distributed ledger system, a block value representing the block in the block chain; and generating a record in the digital property registry, the record: indicating that the digital property has been registered in the digital property registry; and including the block value.

15. The method of clause 14, wherein the document obfuscation value comprises a first document obfuscation value, the block comprises a first block, the blockchain comprises a first blockchain, the blockvalue comprises a first blockvalue, the distributed ledger system comprises a first distributed ledger system, the request comprises a first request, and the method further comprises: receiving, from the electronic device, a second document obfuscation value representing the document; sending the second document obfuscation value to a second distributed ledger system and a second request to generate a second block in a second blockchain associated with the second distributed ledger system; receiving, from the second distributed ledger system, a second block value representing the second block in the second block chain; and wherein the record associates the second chunk value with the digital property.

16. The method of clause 14 or 15, wherein the record comprises a first record, and the method further comprises: receiving an identifier corresponding to at least one of: the electronic device; or an entity associated with the electronic device; associating the identifier with the first record; determining that a second record associated with the digital property registry is associated with the identifier; and associating the first record with the second record based at least in part on determining that the first record and the second record are associated with the identifier.

17. The method of clause 14, 15 or 16, wherein the block comprises a first block, the blockchain comprises a first blockchain, the blockvalue comprises a first blockvalue, the distributed ledger system comprises a first distributed ledger system, the request comprises a first request, and the method further comprises: sending the document obfuscation value to a second distributed ledger system and a second request to generate a second block in a second block chain associated with the second distributed ledger system; receiving, from the second distributed ledger system, a second block value representing the second block in the second block chain; and wherein the record associates the second chunk value with the digital property.

18. The method of clause 14, 15, 16 or 17, wherein the input data comprises first input data, and the method further comprises: receiving second input data, the second input data indicating at least one of: an identifier of at least one of a title associated with the document, a type of business secret associated with the document, or a person or entity associated with the document; generating tag data based at least in part on the second input data; receiving third input data requesting a search of the digital property associated with the digital property registry, the third input data including search terms; and causing searching of the tag data for the search term based at least in part on receiving the third input data.

19. The method of clause 14, 15, 16, 17 or 18, further comprising: identifying fields of the document based at least in part on the document obfuscation value, individual ones of the fields being associated with a field type; identifying field values associated with the respective ones of the fields; and generating tag data associated with the document, the tag data generated based at least in part on the field type and the field value for the respective ones of the fields.

20. A system, comprising: one or more processors; and a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving, from an electronic device, data representing a document corresponding to digital property; receiving input data indicating that the document is to be registered in a digital property registry; generating a document obfuscation value representative of the document based at least in part on receiving the input data; removing the document from the system; sending the document obfuscation value to a distributed ledger system and a request to generate a block in a block chain associated with the distributed ledger system; receiving, from the distributed ledger system, a block value representing the block in the block chain; and generating a record in the digital property registry, the record: indicating that the digital property has been registered in the digital property registry; including the block value; and indicating a time value associated with at least one of the generation of the chunk value or the generation of the record.

21. The system of clause 20, wherein the document obfuscation value comprises a first document obfuscation value, the block comprises a first block, the block chain comprises a first block chain, the block value comprises a first block value, the distributed ledger system comprises a first distributed ledger system, the request comprises a first request, generating the first document obfuscation value comprises generating the first document obfuscation value using a first hash value generator, and the operations further comprise: generating a second document obfuscation value representing the document based at least in part on receiving the input data, the second document obfuscation value generated using a second hash value generator that is different from the first hash value generator; sending the second document obfuscation value to a second distributed ledger system and a second request to generate a second block in a second blockchain associated with the second distributed ledger system; receiving, from the second distributed ledger system, a second block value representing the second block in the second block chain; and wherein the record associates the second chunk value with the digital property.

22. The system of clause 20 or 21, wherein the record comprises a first record, and the operations further comprise: receiving an identifier corresponding to at least one of: the electronic device; or an entity associated with the electronic device; associating the identifier with the first record; determining that a second record associated with the digital property registry is associated with the identifier; and associating the first record with the second record based at least in part on determining that the first record and the second record are associated with the identifier.

23. The system of clause 20, 21 or 22, wherein the document obfuscation value comprises a first document obfuscation value, and the operations further comprise: identifying a first portion of the document and a second portion of the document; generating a second document obfuscation value representing the first portion of the document; generating a third document obfuscation value representing the second portion of the document; and wherein generating the first document obfuscation value comprises generating the first document obfuscation value based at least in part on the second document obfuscation value and the third document obfuscation value.

24. The system of clause 20, 21, 22 or 23, wherein the block comprises a first block, the blockchain comprises a first blockchain, the blockvalue comprises a first blockvalue, the time value comprises a first time value, the distributed ledger system comprises a first distributed ledger system, the request comprises a first request, and the operations further comprise: sending the document obfuscation value to a second distributed ledger system and a second request to generate a second block in a second block chain associated with the second distributed ledger system; receiving, from the second distributed ledger system, a second block value representing the second block in the second block chain; and wherein the record associates the second chunk value with the digital property.

25. The system of clause 20, 21, 22, 23, or 24, wherein the input data comprises first input data, and the operations further comprise: receiving second input data, the second input data indicating at least one of: an identifier of at least one of a title associated with the document, a type of business secret associated with the document, or a person or entity associated with the document; generating tag data based at least in part on the second input data; receiving third input data requesting a search of the digital property associated with the digital property registry, the third input data including search terms; and causing searching of the tag data for the search term based at least in part on receiving the third input data.

26. The system of clause 20, 21, 22, 23, 24, or 25, the operations further comprising: identifying fields of the document, each of the fields being associated with a field type; identifying field values associated with the respective ones of the fields; and generating tag data associated with the document, the tag data generated based at least in part on the field type and the field value for the respective ones of the fields.

27. The system of clause 20, 21, 22, 23, 24, 25, or 26, the operations further comprising: storing security rules associated with a firewall; and wherein: receiving the document from the electronic device comprises receiving the document via the firewall and based at least in part on the security rules that allow the document to be received from the electronic device; sending the document obfuscation value and the request to the distributed ledger system comprises sending the document obfuscation value and the request via the firewall and based at least in part on the security rules that allow the document obfuscation value and the request to be transmitted to the distributed ledger system; receiving the blocking value from the distributed ledger system comprises receiving the blocking value via the firewall and based at least in part on the security rule that allows the blocking value to be received from the distributed ledger system; and sending the confirmation data to the electronic device comprises sending the confirmation data via the firewall and based at least in part on the security rules that allow the confirmation data to be transmitted to the electronic device.

28. A system, comprising: one or more processors; and a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving, from an electronic device, a document obfuscation value representing a document corresponding to digital property; receiving a request to register a digital property in association with a digital property registry; analyzing the document confusion value against a stored document confusion value stored in association with the digital property registry; determining that the document obfuscation value is different from the stored document obfuscation value based, at least in part, on analyzing the document obfuscation value relative to the stored document obfuscation value; receiving a tile value associated with the document obfuscation value from a distributed ledger system, the tile value representing a tile in the chain of tiles; and based at least in part on determining that the document obfuscation value is different from the stored document obfuscation value, generating a record in the digital property registry, the record: indicating that the digital property has been registered in the digital property registry; and associating the block value with the digital property.

29. The system of clause 28, wherein determining that the document obfuscation value is different from the stored document obfuscation value comprises determining that the document obfuscation value is different from the stored document obfuscation value based, at least in part, on: determining a degree of difference between the document obfuscation value and the stored document obfuscation value; and determining that the degree of difference is greater than a threshold degree of difference.

30. The system of clause 28 or 29, the operations further comprising: determining a similarity between the document confusion value and at least one of the stored document confusion values; determining that the similarity is greater than a threshold similarity; determining that the entity identifier associated with the document obfuscation value is associated with the at least one of the stored document obfuscation values; and associating the digital property with at least one digital property associated with the at least one of the stored document obfuscation values based, at least in part, on the similarity being greater than the threshold similarity and the entity identifier being associated with the at least one of the document obfuscation values and the stored document obfuscation values.

31. The system of clause 28, 29, or 30, the operations further comprising: generating acknowledgement data indicating: the record has been associated with the digital property registry; and the document has been determined to be unique relative to other documents registered in association with the digital property registry; and transmitting the confirmation data to the electronic device.

32. A system, comprising: one or more processors; and a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving a document representing digital property; receiving input indicating that the document is to be registered in a digital property registry associated with a registration system; generating a document obfuscation value representative of the document based at least in part on receiving the input; sending the document obfuscation value to a distributed ledger system and a first request to register the document obfuscation value with the distributed ledger system; receiving a blockiness value from the distributed ledger system indicating that the document obfuscation value has been registered in a blockiness of a blockchain associated with the distributed ledger system; sending the document obfuscation value, the block value, and a second request to register the digital property in association with the digital property registry to the registration system; and receiving acknowledgement data from the registration system, the acknowledgement data indicating: registering the digital property in association with the digital property registry; and the digital property has been associated with the block value.

33. The system of clause 32, wherein the document obfuscation value comprises a first document obfuscation value, and the operations further comprise: identifying a first portion of the document and a second portion of the document; generating a second document obfuscation value representing the first portion of the document; generating a third document obfuscation value representing the second portion of the document; and wherein generating the first document obfuscation value comprises generating the first document obfuscation value based at least in part on the second document obfuscation value and the third document obfuscation value.

34. The system of clause 32 or 33, wherein the document obfuscation value comprises a first document obfuscation value, the tile comprises a first tile, the tile chain comprises a first tile chain, the tile value comprises a first tile value, the distributed ledger system comprises a first distributed ledger system, generating the first document obfuscation value comprises generating the first document obfuscation value using a first hash value generator, and the operations further comprise: generating a second document obfuscation value representing the document based at least in part on receiving the input, the second document obfuscation value being generated using a second hash value generator that is different from the first hash value generator; sending the second document obfuscation value to the registration system; and wherein the validation data indicates that the digital property has been associated with a second tile value associated with the second document obfuscation value, the second tile value representing a second tile in a second chain of tiles associated with a second distributed ledger system.

35. The system of clause 32, 33 or 34, wherein the input comprises a first input, and the operations further comprise: receiving a second input indicative of at least one of: identification information of at least one of a title associated with the document, a type of business secret associated with the document, or a person or entity associated with the document; generating label data based at least in part on the second input; storing the tag data; receiving a third input requesting a search of the digital property registry, the third input comprising a search term; causing the tag data to be searched based at least in part on the search term; and generating response data indicative of results of the search of at least the tag data.

36. The system of clause 32, 33, 34 or 35, the operations further comprising: identifying fields of the document, each of the fields being associated with a field type; identifying field values associated with the respective ones of the fields; and generating tag data associated with the document, the tag data generated based at least in part on the field type and the field value for the respective ones of the fields.

37. A system, comprising: one or more processors; and a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: causing display of a user interface indicating an option to enroll a trade secret in a trade secret enrolment authority associated with an enrolment system; receiving, via the user interface, a first input indicating a first request to register the trade secret in the trade secret registry; cause display of a second request identifying a document to be registered as the business secret based at least in part on receiving the first input; receiving, via the user interface, a second input identifying the document; and cause display of a record associated with the trade secret registry based at least in part on the second input, the record indicating: a document obfuscation value generated based at least in part on the document has been registered in association with the trade secret registry; having registered with the commercial secret registry a block value associated with a block of a block chain; and a time value associated with at least one of the generation of the chunk value or the generation of the record.

38. The system of clause 37, wherein the option comprises a first option, and the operations further comprise: causing display of a second option to obtain an insurance policy associated with the trade secret; receiving, via the user interface, a third input indicating a third request to obtain the insurance policy; and causing, based at least in part on receiving the third input, display: one or more requests for information associated with at least one of the insurance policy or the trade secret; and one or more input fields configured to receive text input in response to the one or more requests for information; receiving, via the user interface, text input for each of the one or more input fields; receiving an indication from an insurer system associated with an insurer that the policy has been issued; and causing display of insurance policy information associated with the insurance policy via the user interface.

39. The system of clause 37 or 38, the operations further comprising: receiving an indication from an insurer system associated with an insurer that the policy has been issued; and causing display of insurance policy information associated with the insurance policy via the user interface.

40. The system of clause 37, 38 or 39, wherein the option comprises a first option, and the operations further comprise: causing display, via the user interface, of an input field associated with the document, the input field including at least one of: a document name field, a document description field, or a tag field; cause display, via the user interface, a second option to automatically populate at least one of the input fields; receiving, via the user interface, a third input indicating a third request to automatically populate the at least one of the input fields; and causing display of text in the at least one of the input fields based at least in part on the third input.

41. The system of clause 37, 38, 39, or 40, wherein the option comprises a first option, the tile value comprises a first tile value, the tile comprises a first tile, and the operations further comprise: causing display, via the user interface, a second option to associate an information document with the trade secret, the information document indicating information associated with a value of the trade secret; receiving, with the user interface, a third input identifying the information document; causing display, via the user interface, of the value determined by the check-in system based at least in part on the information document; and wherein the record indicates a second tile value associated with a second tile of the chain of tiles in which the information document has been registered.

42. A method, comprising: causing display of a user interface including an option to register the digital property in a digital property registry; receiving first input data requesting registration of the digital property in the digital property registry; causing display of a request identifying a document to be registered as the digital property; receiving second input data identifying the document; and causing display of a tile value associated with a tile of a tile chain in which an identifier of the document has been registered.

43. The method of clause 42, wherein the option comprises a first option, and the method further comprises: causing display of a second option to obtain an insurance policy associated with the digital property; receiving a third input data requesting to acquire the insurance policy; causing display of an input field configured to receive text input in response to an information request based at least in part on the third input data; receiving fourth input data representing the text input to the input field; receiving an indication from an insurer system associated with an insurer that the policy has been issued; and causing display of insurance policy information associated with the insurance policy.

44. The method of clause 42 or 43, wherein the option comprises a first option, and the method further comprises: causing display of a second option to determine a value of an input field associated with the document; receiving, via the user interface, third input data requesting a determination of the value; and causing display of text in the input field based at least in part on the third input data.

45. The method of clause 42, 43 or 44, further comprising: receiving fourth input data representing user input to manipulate the text; causing display of the manipulated text relative to the input field based at least in part on the fourth input data; causing a request to be displayed via the user interface to confirm the manipulated text displayed in the input field; receiving, via the user interface, fifth input data indicating a confirmation of the manipulated text; and associating the manipulated text with the identifier of the document based at least in part on the fifth input data.

46. The method of clause 42, 43, 44 or 45, wherein the option comprises a first option, the document comprises a first document, and the method further comprises: causing display of a second option that associates a second document with the digital property, the second document indicating information associated with a value of the digital property; receiving third input data identifying the second document; and causing display of text indicating the value based at least in part on the second document.

47. The method of clause 42, 43, 44, 45, or 46, further comprising: determining a characteristic of the document based at least in part on a document confusion value corresponding to the document; determining a type of business secret associated with the document based at least in part on the characteristic; and cause display of text via the user interface indicating the type of trade secret.

48. The method of clause 42, 43, 44, 45, 46, or 47, wherein the identifier comprises a first identifier, the document comprises a first document, the first document associated with an entity identifier, the entity identifier corresponding to an entity having access to the digital property registry, and the method further comprises: causing display, via the user interface, of a commercial secret repository screen, the screen comprising: the first identifier of the first document; a second identifier of a second document associated with the entity identifier; and a search field configured to receive input to search records in the digital property registry associated with the entity identifier; receiving third input data indicative of text entered into the search field; and cause display of one or more of the records via the user interface based at least in part on the text entered into the search field.

49. The method of clause 42, 43, 44, 45, 46, 47 or 48, wherein the options comprise a first option, the document comprises a first document, and the method further comprises: causing display, via the user interface, a second option to verify that a second document corresponds to the first document; receiving third input data requesting verification that the second document corresponds to the first document; causing display of a request identifying the second document; receiving fourth input data identifying the second document; and causing display, via the user interface, of an indication that a first document obfuscation value associated with the first document has at least a threshold degree of similarity to a second document obfuscation value associated with the second document.

50. A method, comprising: causing display of a user interface requesting identification of a document to be registered as digital property in a digital property registry; receiving input data identifying the document; and causing display of a record associated with the digital property registry based at least in part on the input data, the record indicating: a document obfuscation value generated based at least in part on the document has been registered in association with the digital property registry; and block values associated with blocks of the block chain have been registered in association with the digital property registry.

51. The method of clause 50, wherein the input data comprises first input data, and the method further comprises: causing display of an option to obtain an insurance policy associated with the digital property; receiving second input data requesting to acquire the insurance policy; causing display of an input field configured to receive text input in response to an information request based at least in part on the second input data; receiving third input data representing the text input to the input field; receiving an indication from an insurer system associated with an insurer that the policy has been issued; and causing display of insurance policy information associated with the insurance policy.

52. The method of clause 50 or 51, wherein the input data comprises first input data, the document comprises a first document, and the method further comprises: causing display of an option to associate a second document with the trade secret, the second document indicating information associated with a value of the trade secret; receiving second input data identifying the second document; and causing display of text indicating the value based at least in part on the second document.

53. The method of clause 50, 51 or 52, further comprising: determining a characteristic of the document based at least in part on a document confusion value corresponding to the document; determining a type of business secret associated with the document based at least in part on the characteristic; and cause display of text via the user interface indicating the type of trade secret.

54. The method of clause 50, 51, 52, or 53, wherein the document comprises a first document, and the method further comprises: determining that a first document confusion value associated with the first document has at least a threshold degree of similarity to a second document confusion value associated with the second document; associating the first document with the second document based at least in part on determining that the first document confusion value has at least a threshold degree of similarity to the second document confusion value; and causing display, via the user interface, an indication that the first document has been associated with the second document.

55. The method of clause 50, 51, 52, 53, or 54, further comprising: determining that a similarity of a first document obfuscation value associated with the document to a document obfuscation value registered in association with the business secret registry is less than a threshold similarity; determining that the document is unique relative to the business secret registry based at least in part on a similarity of the first document confusion value and the document confusion value being less than the threshold phase velocity; and causing display, via the user interface, an indication that the document is unique with respect to the trade secret registry.

56. The method of clauses 50, 51, 52, 53, 54, or 55, further comprising: causing display, via the user interface, of insurance policy information associated with an insurance policy issued for the trade secret, the insurance policy information including a payment value associated with an amount paid to an entity associated with the trade secret at the occurrence of an event; receiving compliance data indicating that the entity is not in compliance with the conditions of the insurance policy; and causing display, via the user interface, of updated insurance policy information including the updated payment value, the updated payment value being less than the payment value.

57. The method of clause 50, 51, 52, 53, 54, 55, or 56, wherein the input data comprises first input data, the document comprises a first document, and the method further comprises: causing an option to be displayed via the user interface to verify that a second document is similar to the first document; receiving second input data requesting verification that the second document is similar to the first document; causing display of a request identifying the second document; receiving third input data identifying the second document; and causing display, via the user interface, of an indication that a first document obfuscation value associated with the first document has at least a threshold degree of similarity to a second document obfuscation value associated with the second document.

58. A system, comprising: one or more processors; and a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: storing, in association with a trade secret registry, a first record indicating: a first document obfuscation value corresponding to a first document representing a business secret; and a blocking value generated based at least in part on the first document obfuscation value, the blocking value representing a block in a blockchain of a distributed ledger system; receiving an indication that the first document represents a first version of the first document; receiving, from an electronic device, input data requesting registration of a second document in association with the trade secret registry; receiving, from the electronic device, a second document obfuscation value corresponding to the second document; determining that the second document corresponds to a second version of the first document based at least in part on a comparison of the first document obfuscation value and the second document obfuscation value; and generating a second record: indicating that an identifier of the second document has been registered in association with the trade secret registry; indicating that the second document is the second version of the first document; and including a selectable link that, when selected, causes the first record to be displayed.

59. The system of clause 58, wherein the input data comprises first input data, and the operations further comprise: storing first access control data indicating a first identifier of a first person allowed to access the first record; storing second access control data indicating a second identifier of a second person allowed to access the second record, the second access control data indicating that access to the first record by the second person is not allowed; receiving second input data requesting access to the second record, the second input data indicating that the second person is requesting access to the second record; causing display of the second record including the selectable link based at least in part on the second input data; receiving third input data corresponding to selection of the selectable link; and refrain from causing display of the first record based at least in part on the second access control data indicating that access to the first record is not allowed.

60. The system of clause 58 or 59, the operations further comprising: associating the business secret with an insurance policy using an intelligent contract associated with the blockchain, the intelligent contract indicating conditions for validating the insurance policy; receiving, from the electronic device, attestation data indicating that the condition has been satisfied; sending the validation data to the distributed ledger system, the validation data causing the smart contract to validate the insurance policy; and receiving confirmation data from the distributed ledger system indicating that the insurance policy has been validated with the intelligent contract.

61. The system of clause 58, 59 or 60, wherein the tile value comprises a first tile value, the tile comprises a first tile, and the operations further comprise: receiving valuation data from the electronic device that is indicated as relating to a value of the business secret; receiving a third document obfuscation value corresponding to the valuation data from the electronic device; receiving, from at least one of the electronic device or the distributed ledger system, a second block value generated based at least in part on the third document obfuscation value, the second block value representing a second block in the block chain; and wherein the first record comprises the third document obfuscation value and the second tile value.

62. The system of clause 58, 59, 60, or 61, the operations further comprising: associating a first feature vector with the first document based at least in part on first text data associated with the first document; associating a second feature vector with the second document based at least in part on second text data associated with the second document; determining that a distance between the first feature vector and the second feature vector is less than a threshold distance; and wherein determining that the second document corresponds to the second version of the first document comprises determining that the second document corresponds to the second version of the first document based, at least in part, on the distance being less than the threshold distance.

63. The system of clause 58, 59, 60, 61, or 62, the operations further comprising: associating a feature vector with the first document based at least in part on first text data associated with the first document; determining a number of other feature vectors within a threshold distance from the first feature vector; and determining a popularity score associated with the first document based at least in part on the number of the other feature vectors.

64. The system of clause 58, 59, 60, 61, 62, or 63, the operations further comprising: receiving an indication of a type of commercial secret associated with the commercial secret; identifying a frequency of registration of a version of a trade secret associated with the trade secret type with the trade secret registry; generating a version check-in alert based at least in part on the frequency; and sending alert data representative of the version registration alert to the electronic device.

65. The system of clause 58, 59, 60, 61, 62, 63, or 64, the operations further comprising: determining, using at least one of the electronic device or an entity identifier corresponding to an entity associated with the electronic device, a frequency of registering a version of a commercial secret with the commercial secret registry; generating a version check-in alert based at least in part on the frequency; and sending alert data representative of the version registration alert to the electronic device.

66. A method, comprising: storing a record in association with a trade secret registry, the record indicating: a first document obfuscation value corresponding to a document representing a business secret; and a first tile value generated based at least in part on the first document obfuscation value, the first tile value representing a first tile in a chain of tiles of a distributed ledger system; receiving valuation data from an electronic device that is indicated to be related to a value of the business secret; receiving a second document obfuscation value corresponding to the valuation data from the electronic device; receiving, from at least one of the electronic device or the distributed ledger system, a second block value generated based at least in part on the second document obfuscation value, the second block value representing a second block in the block chain; and wherein the record comprises the second document obfuscation value and the second tile value.

67. The method of clause 66, wherein the document comprises a first document, the record comprises a first record, and the method further comprises: receiving an indication that the first document represents a first version of the first document; receiving, from the electronic device, input data requesting registration of a second document in association with the trade secret registry; receiving, from the electronic device, a third document obfuscation value corresponding to the second document; determining that the second document corresponds to a second version of the first document based at least in part on a comparison of the first document confusion value and the third document confusion value; and generating a second record: an identifier indicating that the second document has been registered in association with the trade secret registry; and indicating that the second document corresponds to the second version of the first document.

68. The method of clause 66 or 67, further comprising: storing first access control data indicating a first identifier of a first person allowed to access a first portion of the record; storing second access control data indicating a second identifier of a second person allowed to access a second portion of the record, the second access control data indicating that the second person is not allowed to access the first portion of the record; receiving first input data requesting access to the record, the first input data indicating that the second person is requesting access to the record; causing display of the second portion of the record based at least in part on the first input data; receiving second input data that the second person requests access to the first portion of the record; and refrain from causing display of the first portion of the record based at least in part on the second access control data indicating that access to the first portion of the record is not allowed.

69. The method of clause 66, 67 or 68, further comprising: associating the business secret with an insurance policy using an intelligent contract associated with the blockchain, the intelligent contract indicating conditions for validating the insurance policy; receiving, from the electronic device, attestation data indicating that the condition has been satisfied; sending the validation data to the distributed ledger system, the validation data causing the smart contract to validate the insurance policy; and receiving confirmation data from the distributed ledger system indicating that the insurance policy has been validated with the intelligent contract.

70. A system, comprising: one or more processors; and a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: storing first access control data indicating: a first identifier of a first person allowed to access a record associated with a trade secret registry, the record indicating a trade secret registered in association with the trade secret registry; and a function of the trade secret registry authorizing use of the first person; storing second access control data, the second access control data indicating: a second identifier of a second person allowed to access the record; and the second person is not authorized to use the function; receiving first input data requesting access to the record, the first input data indicating that the second person is requesting access to the record; causing display of the record based at least in part on the first input data; receiving second input data requesting use of the function; and refrain from causing the function to be performed based at least in part on the second access control data indicating that the second person is not authorized to use the function.

71. The system of clause 70, wherein the trade secret comprises a first trade secret, the record comprises a first document obfuscation value corresponding to the first trade secret, and the operations further comprise: receiving an indication that the first commercial secret represents a first version of the first commercial secret; receiving, from an electronic device, third input data requesting registration of a second trade secret in association with the trade secret registry; receiving, from the electronic device, a second document obfuscation value corresponding to the second business secret; determining that the second merchant secret corresponds to a second version of the first merchant secret based at least in part on a comparison of the first document obfuscation value and the second document obfuscation value; and generating a second record: indicating that the second trade secret has been enrolled in association with the trade secret enrollee; and indicating that the second commercial secret is the second version of the first commercial secret.

72. The system of clause 70 or 71, wherein a first document obfuscation value corresponds to the document, a first chunk value is associated with the business secret, and the operations further comprise: receiving valuation data from an electronic device that is indicated as relating to a value of the business secret; receiving a second document obfuscation value corresponding to the valuation data from the electronic device; receiving, from at least one of the electronic device or a distributed ledger system, a second block value generated based at least in part on the second document obfuscation value, the second block value representing a block in a block chain of the distributed ledger system; and wherein the record comprises the second document obfuscation value and the second tile value.

73. The system of clause 70, 71 or 72, wherein the record indicates a document obfuscation value corresponding to the business secret and a blocking value generated based at least in part on the document obfuscation value, the blocking value representing a block in a blockchain of the distributed ledger system, and the operations further comprise: associating the business secret with an insurance policy using an intelligent contract associated with the blockchain, the intelligent contract indicating conditions for validating the insurance policy; receiving, from an electronic device, attestation data indicating that the condition has been satisfied; sending the validation data to the distributed ledger system, the validation data causing the smart contract to validate the insurance policy; and receiving confirmation data from the distributed ledger system indicating that the insurance policy has been validated with the intelligent contract.

74. The system of clause 70, 71, 72, or 73, the operations further comprising: generating a log of one or more electronic devices accessing the record, the log indicating: accessing identifiers of individual ones of the recorded people, the people including the first person; and the time value at which said individual of said persons accessed said record; receiving an indication that the first access control data associated with the first person has been removed; and generating alert data: indicating that the first person has accessed the record; one or more time values indicating that the first person accessed the record; and requesting confirmation that the first person has experienced an out-of-title interview associated with the trade secret.

75. The system of clause 70, 71, 72, 73, or 74, the operations further comprising: generating a log of one or more electronic devices accessing the record, the log indicating: accessing identifiers of individual ones of the recorded people, the people including the first person; and the time value at which said individual of said persons accessed said record; generating, based at least in part on the log, a compliance schedule associated with an insurance policy relating to the trade secret, the compliance schedule indicating a period of time during which the first person may perform compliance with a condition of the insurance policy; determining that the condition is not satisfied before the time period expires; and adjusting a payment value associated with the insurance policy based at least in part on determining that the condition is not satisfied.

76. The system of clause 70, 71, 72, 73, 74, or 75, the operations further comprising: generating an interface to the trade secret registry configured to allow access to at least a portion of the trade secret registry via a remote archiving system associated with intellectual property assets; sending access information for the interface to the remote archiving system; receiving a request from the remote archiving system to perform a search of the trade secret registry, the request including text data for searching the trade secret registry; identifying results of the search; and sending result data representative of the result to the remote archiving system.

77. The system of clause 70, 71, 72, 73, 74, 75, or 76, the operations further comprising: generating a log of accesses of the record by one or more electronic devices; determining, based at least in part on the log, that the number of times the record has been accessed during a period of time exceeds a threshold number of times; generating an alert indicative of abnormal activity with respect to the record based at least in part on determining that the number of times the record has been accessed during the time period exceeds the threshold number of times; and transmitting alarm data representative of the alarm to an electronic device associated with the record.

78. A system, comprising: one or more processors; and a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: storing a record in association with a trade secret registry, the record indicating: a document obfuscation value corresponding to a document representing a business secret; and a block value generated based at least in part on the document obfuscation value, the block value representing a block in a block chain of a distributed ledger system; receiving valuation data from an electronic device that is indicated to be related to a value of the business secret; determining the value of the business secret based at least in part on the valuation data; and causing display of an indication of the value via a user interface accessible to the electronic device.

79. The system of clause 78, the operations further comprising: determining a series of dialog boxes to be displayed via the user interface based at least in part on tag data indicative of a characteristic associated with the document, the series of dialog boxes including text associated with determining the value of the trade secret; transmitting data representing the series of dialog boxes to the electronic device; and wherein the valuation data includes inputs to the series of dialog boxes.

80. The system of clause 78 or 79, wherein the trade secret comprises a first trade secret, the value comprises a first value, and the operations further comprise: determining a type of trade secret associated with the first trade secret based at least in part on tag data indicative of a characteristic associated with the document; identifying a second trade secret associated with the trade secret type; identifying a second value associated with the second business secret; and wherein determining the first value of the first commercial secret comprises determining the first value of the first commercial secret based at least in part on the second value.

81. The system of clause 78, 79 or 80, the operations further comprising: receiving entity value data from at least one of the electronic device or another device, the entity value data indicating at least one of an entity value of an entity associated with the document or a revenue value of the entity; and wherein determining the value of the business secret comprises determining the value of the business secret based at least in part on the entity value data.

82. The system of clause 78, 79, 80, or 81, wherein determining the value of the trade secret comprises determining the value of the trade secret based at least in part on a time value associated with registration of the tile in the blockchain, such that the value increases as a time period between the time value and a current time increases.

83. The system of clause 78, 79, 80, 81 or 82, wherein the tile value comprises a first tile value, the document obfuscation value comprises a first document obfuscation value, the tile comprises a first tile, and the operations further comprise: receiving, from the distributed ledger system, a second block value generated based at least in part on a second document obfuscation value corresponding to financial data associated with the business secret, the second block value representing a second block in the block chain of the distributed ledger system; and wherein determining the value of the trade secret comprises determining the value of the trade secret based at least in part on receiving the second chunk value.

84. A method, comprising: storing a record in association with a trade secret registry, the record indicating: a document obfuscation value corresponding to a document representing a business secret; and a block value generated based at least in part on the document obfuscation value, the block value representing a block in a block chain of a distributed ledger system; receiving, from an electronic device, input data requesting issuance of an insurance policy associated with the trade secret; generating a policy request, the request indicating: the trade secret has been registered with the trade secret registry; and the block value; sending the policy request to an insurer system associated with an insurer; receiving an indication from the insurer system that the policy has been issued; and causing display of an indication that the policy has been issued via a user interface accessible to the electronic device.

85. The method of clause 84, wherein the input data comprises first input data, and the method further comprises: determining a series of dialog boxes to be displayed via the user interface based at least in part on tag data indicative of a characteristic of the document, the series of dialog boxes including text associated with applying for the insurance policy; transmitting data representing the series of dialog boxes to the electronic device; receiving second input data from the electronic device indicating responses to the series of dialog boxes; and wherein the policy request includes the second input data.

86. The method of clause 84 or 85, further comprising: generating a log of one or more electronic devices accessing the record, the log indicating: accessing identifiers of individual ones of the recorded persons; and the time value at which said individual of said persons accessed said record; generating a compliance schedule associated with the insurance policy based at least in part on the log, the compliance schedule indicating a period of time during which at least one of the persons may perform compliance with a condition of the insurance policy; determining that the condition is not satisfied before the time period expires; and adjusting a payment value associated with the insurance policy based at least in part on determining that the condition is not satisfied.

87. The method of clause 84, 85 or 86, further comprising: based at least in part on determining that the condition is not met prior to expiration of the time period, generating alert data indicating that the condition is not met; and transmitting the alert data to the one or more electronic devices, the alert data causing processors of the one or more electronic devices to launch an application and display an alert corresponding to the alert data.

88. The method of clause 84, 85, 86 or 87, wherein the tile value comprises a first tile value, the document obfuscation value comprises a first document obfuscation value, the tile comprises a first tile, and the method further comprises: receiving, from the distributed ledger system, a second block value generated based at least in part on a second document obfuscation value corresponding to financial data associated with the business secret, the second block value representing a second block in the block chain of the distributed ledger system; and wherein the policy request includes the second block value.

89. The method of clause 84, 85, 86, 87, or 88, further comprising: determining a value of the trade secret based at least in part on the record; and wherein the insurance policy request includes the value of the trade secret.

90. The method of paragraphs 84, 85, 86, 87, 88 or 89, further comprising causing display of information associated with the insurance policy via the user interface, the information including at least one of: a policy type; a limit of responsibility; the value is reserved; or a premium value of the policy.

91. A system, comprising: one or more processors; and a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: storing a record in association with a trade secret registry, the record indicating: a document obfuscation value corresponding to a document representing a business secret; and a block value generated based at least in part on the document obfuscation value, the block value representing a block in a block chain of a distributed ledger system; receiving, from an electronic device, input data requesting issuance of an insurance policy associated with the trade secret; generating, based at least in part on receiving the input data, an insurance policy request indicating that the trade secret has been registered with the trade secret registry; sending the policy request to an insurer system associated with an insurer; and receiving an indication from the insurer system that the policy has been issued.

92. The system of clause 91, wherein the input data comprises first input data, and the operations further comprise: determining a series of dialog boxes to be displayed via a user interface, the series of dialog boxes including text associated with applying for the insurance policy; transmitting data representing the series of dialog boxes to the electronic device; receiving second input data from the electronic device indicating responses to the series of dialog boxes; and wherein the policy request includes the second input data.

93. The system of clause 91 or 92, the operations further comprising: generating a log of accesses of the record by one or more electronic devices, the log indicating identifiers of respective ones of the persons accessing the record; generating a compliance schedule associated with the insurance policy based at least in part on the log, the compliance schedule indicating a period of time during which at least one of the persons may perform compliance with a condition of the insurance policy; determining that the condition is not satisfied before the time period expires; and adjusting a payment value associated with the insurance policy based at least in part on determining that the condition is not satisfied.

94. The system of clause 91, 92 or 93, the operations further comprising: based at least in part on determining that the condition is not met prior to expiration of the time period, generating alert data indicating that the condition is not met; and transmitting the alert data to the one or more electronic devices, the alert data causing processors of the one or more electronic devices to launch an application and display an alert corresponding to the alert data.

95. The system of clause 91, 92, 93 or 94, wherein the tile value comprises a first tile value, the document obfuscation value comprises a first document obfuscation value, the tile comprises a first tile, and the operations further comprise: receiving, from the distributed ledger system, a second block value generated based at least in part on a second document obfuscation value corresponding to financial data associated with the business secret, the second block value representing a second block in the block chain of the distributed ledger system; and wherein the policy request includes an indication that the financial data has been registered with the blockchain.

96. The system of clause 91, 92, 93, 94, or 95, the operations further comprising: determining a value of the trade secret based at least in part on the record; and wherein the insurance policy request includes the value of the trade secret.

97. The system of clause 91, 92, 93, 94, 95 or 96, the operations further comprising causing display, via a user interface, of information associated with the insurance policy, the information comprising at least one of: a policy type; a limit of responsibility; the value is reserved; or a premium value of the policy.

98. A system, comprising: one or more processors; and a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: storing a record in association with a trade secret registry, the record indicating: a first document obfuscation value corresponding to a first document representing a business secret; and a blocking value generated based at least in part on the first document obfuscation value, the blocking value representing a block in a blockchain of a distributed ledger system; receiving a second document from the electronic device that is indicated as having been compromised; receiving input data from the electronic device requesting verification that the second document corresponds to a registered document registered with respect to the trade secret registry; generating a second document obfuscation value corresponding to the second document based at least in part on the second document; determining a similarity between the first document confusion value and the second document confusion value; determining that the similarity is greater than a threshold similarity; and determining that the second document corresponds to the first document based at least in part on the similarity being greater than the threshold similarity.

99. The system of clause 98, the operations further comprising: causing the first document obfuscation value to be segmented into first segments, each of the first segments corresponding to a portion of the first document; causing the second document obfuscation value to be segmented into second segments, each of the second segments corresponding to a portion of the second document; wherein determining the similarity comprises determining the similarity based at least in part on analyzing the first segment relative to the second segment; and wherein determining that the similarity is greater than the threshold similarity comprises determining that the similarity is greater than the threshold similarity based at least in part on a number of the first segments corresponding to the second segments being greater than a threshold number of segments.

100. The system of clause 98 or 99, the operations further comprising: determining a Levensian distance between a first characteristic of the first document and a second characteristic of the second document; wherein determining the similarity comprises determining the similarity based at least in part on the Levens distance; and wherein determining that the similarity is greater than the threshold similarity comprises determining that the similarity is greater than the threshold similarity based at least in part on the levenshtein distance being less than a threshold levenshtein distance.

101. The system of clause 98, 99 or 100, wherein the tile value comprises a first tile value, the tile comprises a first tile, and the operations further comprise: sending the second document obfuscation value to the distributed ledger system; sending a request to the distributed ledger system identifying a second block value corresponding to the second document obfuscation value, the second block value representing a second block in the block chain; receiving the second blocking value from the distributed ledger system; determining that the first block value corresponds to the second block value; and wherein determining that the second document corresponds to the first document comprises determining that the second document corresponds to the first document based at least in part on the first tile value corresponding to the second tile value.

102. A method, comprising: storing a record indicating: a first document obfuscation value corresponding to a first document representing a business secret; and a blocking value generated based at least in part on the first document obfuscation value, the blocking value representing a block in a blockchain of a distributed ledger system; receiving a second document from the electronic device that is indicated as having been compromised; generating a second document obfuscation value corresponding to the second document based at least in part on the second document; determining a similarity between the first document confusion value and the second document confusion value; and determining that the second document corresponds to the first document based at least in part on the similarity.

103. The method of clause 102, further comprising: causing the first document obfuscation value to be segmented into first segments; causing the second document obfuscation value to be segmented into a second segment; and wherein determining the similarity comprises determining the similarity based at least in part on determining a number of the first segments corresponding to the second segments.

104. The method of clause 102 or 103, further comprising: determining a Levensian distance between a first characteristic of the first document and a second characteristic of the second document; and wherein determining the similarity comprises determining the similarity based at least in part on the levenstein distance.

105. The method of

clause

102, 103 or 104, wherein the tile value comprises a first tile value, and the method further comprises: receiving a second block value corresponding to the second document obfuscation value from the distributed ledger system; determining that the first block value corresponds to the second block value; and wherein determining that the second document corresponds to the first document comprises determining that the second document corresponds to the first document based at least in part on the first tile value corresponding to the second tile value.

106. The method of

clause

102, 103, 104 or 105, wherein the record comprises a first record associated with a first version of the first document, the similarity comprises a first similarity, and the method further comprises: storing a second record associated with a second version of the first document, the second record associated with the first record based at least in part on the second record being associated with the second version of the first document; determining a second similarity between a third document obfuscation value corresponding to the second version of the first document and the second document obfuscation value; and wherein determining that the second document corresponds to the first document comprises determining that the second document corresponds to the second version of the first document based at least in part on the second similarity.

107. The method of

clause

102, 103, 104, 105, or 106, further comprising: based at least in part on determining that the second document corresponds to the first document, causing display, via a user interface of the electronic device, of a series of dialog boxes that include text associated with submitting a passage for an insurance scope in association with an insurance policy for the trade secret; receiving input data comprising a response to the text; and sending at least one of the input data or a notification of the passage to an insurer system associated with an insurer.

108. The method of

clause

102, 103, 104, 105, 106 or 107, further comprising: receiving status data from the insurer system, the status data indicating that information is requested to process the passage; sending an alert to the electronic device indicating that the information is requested; and causing a request for the information to be displayed via a user interface.

109. The method of

clause

102, 103, 104, 105, 106, 107 or 108, further comprising: determining a first portion of the first document obfuscation value corresponding to a second portion of the second document obfuscation value; identifying a third portion of the first document corresponding to the first portion of the first document obfuscation value; and causing display, via a user interface and based at least in part on identifying the third portion, of an indication that the third portion of the first document is similar to at least a portion of the second document.

110. A system, comprising: one or more processors; and a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: storing a record indicating: a first document obfuscation value corresponding to a first document corresponding to a business secret; and a blocking value generated based at least in part on the first document obfuscation value, the blocking value representing a block in a blockchain of a distributed ledger system; receiving a second document from the electronic device that is indicated as having been compromised; generating a second document obfuscation value corresponding to the second document based at least in part on the second document; determining a similarity between the first document confusion value and the second document confusion value; and determining that the second document corresponds to the first document based at least in part on the similarity.

111. The system of clause 110, the operations further comprising: causing the first document obfuscation value to be segmented into first segments; causing the second document obfuscation value to be segmented into a second segment; and wherein determining the similarity comprises determining the similarity based at least in part on determining a number of the first segments corresponding to the second segments.

112. The system of clause 110 or 111, the operations further comprising: determining a Levensian distance between a first characteristic of the first document and a second characteristic of the second document; and wherein determining the similarity comprises determining the similarity based at least in part on the levenstein distance.

113. The system of clause 110, 111 or 112, wherein the tile value comprises a first tile value, and the operations further comprise: receiving a second block value corresponding to the second document obfuscation value from the distributed ledger system; determining that the first block value corresponds to the second block value; and wherein determining that the second document corresponds to the first document comprises determining that the second document corresponds to the first document based at least in part on the first tile value corresponding to the second tile value.

114. The system of clause 110, 111, 112 or 113, wherein the record comprises a first record associated with a first version of the first document, the similarity comprises a first similarity, and the operations further comprise: storing a second record associated with a second version of the first document, the second record associated with the first record based at least in part on the second record being associated with the second version of the first document; determining a second similarity between a third document obfuscation value corresponding to the second version of the first document and the second document obfuscation value; and wherein determining that the second document corresponds to the first document comprises determining that the second document corresponds to the second version of the first document based at least in part on the second similarity.

115. The system of clause 110, 111, 112, 113, or 114, the operations further comprising: based at least in part on determining that the second document corresponds to the first document, causing display, via a user interface of the electronic device, of a series of dialog boxes that include text associated with submitting a passage for an insurance scope in association with an insurance policy for the trade secret; receiving input data comprising a response to the text; and sending at least one of the input data or a notification of the passage to an insurer system associated with the insurer who issued the policy.

116. The system of clause 110, 111, 112, 113, 114, or 115, the operations further comprising: receiving status data from the insurer system, the status data indicating that information is requested to process the passage; sending an alert to the electronic device indicating that the information is requested; and causing a request for the information to be displayed via a user interface.

117. The system of clause 110, 111, 112, 113, 114, 115, or 116, the operations further comprising: determining a first portion of the first document obfuscation value corresponding to a second portion of the second document obfuscation value; identifying a third portion of the first document corresponding to the first portion of the first document obfuscation value; and causing display, via a user interface and based at least in part on identifying the third portion, of an indication that the third portion of the first document is similar to at least a portion of the second document.

Claims

1. A method, comprising:

receiving, at an electronic device, a document representing a business secret;

receiving an input at the electronic device indicating that the document is to be registered at a trade secret registry associated with a registration system remote from the electronic device;

Generating a document obfuscation value representative of the document based at least in part on receiving the input;

sending, from the electronic device, the document obfuscation value and a first request to generate a tile in a blockchain associated with a distributed ledger system that is at least remote from the electronic device;

receiving, at the electronic device, a tile value representing the tile in the chain of tiles from the distributed ledger system;

sending, from the electronic device and to the enrollment system, a second request to enroll the document with respect to the trade secret registry;

generating, by the enrollment system, a record in the trade secret enrollment, the record:

indicating that the trade secret has been registered at the trade secret registry;

including the block value; and

indicating a time value associated with at least one of generation of the chunk value or generation of the record;

generating confirmation data indicating that the record has been generated; and

transmitting the confirmation data from the registration system to the electronic device.

2. The method of claim 1, wherein the document obfuscation value comprises a first document obfuscation value, and the method further comprises:

Identifying a first portion of the document and a second portion of the document;

generating a second document obfuscation value representing the first portion of the document;

generating a third document obfuscation value representing the second portion of the document; and is

Wherein generating the first document obfuscation value comprises generating the first document obfuscation value based at least in part on the second document obfuscation value and the third document obfuscation value.

3. The method of claim 1, wherein the tile comprises a first tile, the chain of tiles comprises a first chain of tiles, the tile value comprises a first tile value, the time value comprises a first time value, and the method further comprises:

sending, from the electronic device and to an insurer system, the document obfuscation value and a third request to generate a second tile in a second chain of tiles associated with the insurer system;

receiving, at the electronic device and from the insurer system, a second block value representing the second block in the second block chain;

sending the second block value from the electronic device and to the registration system; and is

Wherein the recording of the trade secret registry is:

Associating the second chunk value with the commercial secret; and

indicating a second time value associated with the generation of the second chunk value.

4. The method of claim 1, further comprising:

generating tag data indicative of properties associated with the document, the properties including at least one of: a title, a type of business secret, or an identifier of at least one of a person or entity associated with the document;

storing the tag data in a database associated with the enrollment system, the tag data associated with the business secret;

receiving, at the electronic device, input data requesting a search for a trade secret associated with the trade secret registry, the input data including a search term; and

causing the tag data to be searched for the search term based at least in part on receiving the input data.

5. The system of claim 1, wherein generating the document obfuscation value comprises generating the document obfuscation value based at least in part on a cryptographic hash.

6. A system, comprising:

one or more processors; and

a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:

Receiving a document representing digital property;

receiving input indicating that the document is to be registered at a digital property registry associated with a registration system;

sending the document obfuscation value and a request to the registration system to register the digital property in association with the digital property registry; and

receiving confirmation data from the registration system, the confirmation data indicating:

the digital property has been registered in association with the digital property registry; and

the digital property has been associated with a blockvalue that represents a block in a blockchain associated with the distributed ledger system.

7. The system of claim 6, wherein the document obfuscation value comprises a first document obfuscation value, and the operations further comprise:

8. The system of claim 6, wherein the block comprises a first block, the blockchain comprises a first blockchain, the blockvalue comprises a first blockvalue, the distributed ledger system comprises a first distributed ledger system, and the validation data indicates that the digital property has been associated with a second blockvalue, the second blockvalue representing a second block in a second blockchain associated with a second distributed ledger system.

9. The system of claim 6, wherein the document obfuscation value comprises a first document obfuscation value, the tile comprises a first tile, the blockchain comprises a first blockchain, the blockvalue comprises a first tile value, the distributed ledger system comprises a first distributed ledger system, generating the first document obfuscation value comprises generating the first document obfuscation value using a first hash value generator, and the operations further comprise:

generating a second document obfuscation value representative of the document based at least in part on receiving the input, the second document obfuscation value being generated with a second hash value generator different from the first hash value generator;

Sending the second document obfuscation value to the registration system; and is

Wherein the validation data indicates that the digital property has been associated with a second tile value associated with the second document obfuscation value, the second tile value representing a second tile in a second chain of tiles associated with a second distributed ledger system.

10. The system of claim 6, wherein the input comprises a first input, and the operations further comprise:

receiving a second input indicative of at least one of: identification information of at least one of a title associated with the document, a type of business secret associated with the document, or a person or entity associated with the document;

generating label data based at least in part on the second input;

storing the tag data;

receiving a third input requesting a search of the digital property registry, the third input comprising a search term;

causing the tag data to be searched based at least in part on the search term; and

generating response data indicative of results of the search of at least the tag data.

11. The system of claim 6, the operations further comprising:

Identifying fields of the document, each of the fields being associated with a field type;

identifying field values associated with the respective ones of the fields; and

generating tag data associated with the document, the tag data generated based at least in part on the field types and the field values of the respective ones of the fields.

12. The system of claim 6, the operations further comprising:

storing security rules associated with a firewall; and is

Wherein:

sending the document obfuscation value and the request comprises sending the document obfuscation value and the request via the firewall and based at least in part on the security rule allowing transmission of the document obfuscation value and the request to the registration system; and

receiving the confirmation data comprises receiving the confirmation data via the firewall and based at least in part on the security rule allowing receipt of the confirmation data from the check-in system.

13. The system of claim 6, wherein the document comprises a first document, the document obfuscation value comprises a first document obfuscation value, and the operations further comprise:

Receiving input data requesting verification that a second document corresponds to the first document;

generating a second document obfuscation value corresponding to the second document based at least in part on the second document;

determining that the first document confusion value corresponds to the second document confusion value; and

determining that the second document corresponds to the first document based at least in part on the first document obfuscation value corresponding to the second document obfuscation value.

14. A method, comprising:

receiving, from an electronic device, a document obfuscation value representing a document corresponding to digital property;

receiving input data indicating that the digital property is to be registered in a digital property registry;

sending the document obfuscation value and a request to a distributed ledger system to generate a block in a block chain associated with the distributed ledger system;

receiving, from the distributed ledger system, a block value representing the block in the block chain; and

generating a record in the digital property registry, the record:

indicating that the digital property has been registered at the digital property registry; and

including the block value.

15. The method of claim 14, wherein the document obfuscation value comprises a first document obfuscation value, the tile comprises a first tile, the blockchain comprises a first blockchain, the blockvalue comprises a first blockchain, the distributed ledger system comprises a first distributed ledger system, the request comprises a first request, and the method further comprises:

Receiving, from the electronic device, a second document obfuscation value representing the document;

sending the second document obfuscation value and a second request to a second distributed ledger system to generate a second tile in a second blockchain associated with the second distributed ledger system;

receiving, from the second distributed ledger system, a second block value representing the second block in the second block chain; and is

Wherein the record associates the second chunk value with the digital property.