CN113498592B - Method and system for digital property authentication and management - Google Patents

Abstract

Systems and methods for digital property authentication and management are disclosed. A request can be made to register documents representing trade secrets with the Trade Secrets Registry. A document obfuscation value corresponding to the document may be generated and registered with the blockchain. A record of the registration may be generated for the trade secret registry. The registry may be searchable and/or provide functionality such as valuations, provision of insurance and/or verification, among other benefits and functionality.

Description

Methods and systems for digital property authentication and management

Cross-references to related applications

This application claims U.S. Patent Application No. 16/280,557, filed on February 20, 2019, titled "Digital Property Authentication and Management System", filed on February 20, 2019, titled " U.S. Patent Application No. 16/280,622 titled "Digital Property Authentication and Management System" filed on February 20, 2019 U.S. Patent Application No. 16/280,670, U.S. Patent Application No. 16/280,703 titled "Digital Property Authentication and Management System" filed on February 20, 2019, and U.S. Patent Application No. 16/280,703 filed on February 20, 2019 Priority is granted to U.S. Patent Application No. 16/280,766 titled "Digital Property Authentication and Management System" filed on the 20th, the entire content of which is incorporated herein by reference.

Background technique

Trade secrets can be valuable assets for companies and individuals. However, unlike other forms of intellectual property, no government registration and/or grant of trade secret rights is provided. This article describes technology improvements and solutions to technical problems that can be used to assist in protecting trade secrets and more.

Description of the drawings

Detailed description is given below with reference to the accompanying drawings. In the figures, the leftmost digit of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different drawings indicates similar or identical items. The systems depicted in the figures are not to scale, and components within the figures may be depicted not to scale with each other.

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

FIG. 2 shows an exemplary user interface displaying a trade secret registration function according to the digital property authentication and management system.

Figure 3 shows an exemplary user interface displaying trade secret maintenance functions according to the digital property authentication and management system.

Figure 4 illustrates an exemplary user interface displaying trade secret verification functionality according to a digital property authentication and management system.

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

Figure 6 illustrates an exemplary user interface displaying valuation functionality in accordance with a digital property authentication and management system.

Figure 7 illustrates an exemplary user interface displaying access control functionality according to a digital property authentication and management system.

8 shows a flowchart of an exemplary process for trade secret registration according to the digital property authentication and management system.

Figure 9 shows a flowchart of an exemplary process for trade secret verification according to the digital property authentication and management system.

Figure 10 shows a flow diagram of an exemplary process for digital property authentication.

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

Figure 12 shows a flow diagram of another exemplary process for digital property authentication.

Figure 13 shows a flow diagram of another exemplary process for digital property authentication.

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

15 illustrates a flow diagram of an exemplary process associated with a user interface in accordance with a digital property authentication and management system.

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

Figure 17 shows a flowchart of an exemplary process for digital asset management including document versioning.

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

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

Figure 20 illustrates a flowchart of an exemplary process for valuing property in accordance with a digital property authentication and management system.

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

22 illustrates a flowchart of an exemplary process for registration verification according to the digital property authentication and management system.

23 illustrates a flowchart of another exemplary process for registration verification according to the digital property authentication and management system.

Detailed ways

Systems and methods for digital property authentication and management are disclosed. Take, for example, a company or individual that owns one or more intellectual property assets, described as an entity in this article. While some of these intellectual property assets may be registrable by government entities, such as patents and trademarks filed for and issued by the U.S. Patent and Trademark Office or copyrights registered by the U.S. Copyright Office, other types of intellectual property, such as trade secrets, may not be registrable by government entities. Register. Additionally, information (sometimes referred to as confidential information or know-how) that may not meet a specific (e.g., legal) definition of a trade secret and/or may not meet multiple different definitions of a trade secret may still be of value to the entity. In these and other examples, registration of such property (collectively referred to herein as "Trade Secrets") is permitted in a manner that establishes a mark of ownership, credibility of possession, or other information useful in evaluating the protection, insurance, or enforcement of such property. ) would be beneficial to such entities.

The innovation described herein provides a digital property authentication and management system that is, among other things, capable of registering information, documents and/or other properties, providing a user interface for registering and managing such property, capable of verifying that information, documents and/or other properties may be registered, Registration and/or analysis of misappropriated property, assisting with asset valuation, assisting in the provision of insurance, and utilizing data generated by the system and/or available to the system to increase functionality associated with registered property.

For example, client-side devices and/or systems described herein as electronic devices may include applications that enable 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 describes a trade secret, and/or has been designated as a trade secret, and/or has been designated as significant to the entity. The client-side device and/or system may include an obfuscation component that may receive data representing a document and may generate a document obfuscation value corresponding to the document. For example, a document obfuscation value may include a sequence 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 are 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 can allow output data to be produced reproducibly.

The client-side device and/or system may send the document obfuscation value and request data, in an example indicating a request to register the document obfuscation value in association with a trade secret registry, to the registration system. The registration system may receive the document obfuscation value and/or the request data and may initiate the process of registering the document obfuscation value in association with the trade secret registry. For example, a registry system may send document obfuscation values and/or request data to a blockchain system that manages one or more blockchains. In other examples, the client-side device may send document obfuscation values 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 the document obfuscation value and/or identifying information associated with the document obfuscation value and/or the document on the blockchain. The blockchain system may register document obfuscation values and/or other information described herein in connection with blocks of the blockchain. Crypto-document obfuscation values can be generated by a registry that can represent blocks in a blockchain. Additionally or alternatively, a time value may be determined that indicates the time and/or date at which the document obfuscation value and/or other information described herein was registered to the blockchain. The blockchain system can then send the encrypted document obfuscation value to a registration system associated with the Trade Secrets Registry. The blockchain system may additionally or alternatively send the encrypted document obfuscation value to the client-side device, particularly upon receipt of request data from the client-side device to register the document obfuscation value.

The registration system can generate records in a trade secrets registry. Records may include information associated with trade secrets. For example, a record may include data indicating an identifier of the record, a naming indicator associated with the trade secret, a description of the trade secret, a naming indicator associated with the document, one or more tag, a status indicator for a trade secret, a document obfuscation value, a block number associated with a block of the blockchain in which the document obfuscation value is registered, an encrypted document obfuscation value, a time value and/or a trade secret and/or trade secret One or more other types of data associated with the registration, such as valuations, insurance policy information, version control information, etc. In an example, the registration system may generate confirmation data indicating that the record has been generated, and may send the confirmation data to the client-side device and/or system for display via the user interface.

Additionally or alternatively, the registration system may be configured to identify, determine, and/or generate one or more indicia of undisclosed trade secrets. For example, users of the registration system may provide information and/or documents indicating that trade secrets have 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 trade secrets 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 non-disclosure markings. In examples, these marks may be used for insurance applications and/or offers and/or for legal proceedings.

Additionally or alternatively, the registration system may be configured to determine whether a document to be registered with the trade secret registry is unique relative to other documents registered 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 a document obfuscation value and a registered document obfuscation value may be determined, and if the similarity is greater than a threshold similarity, it may be determined that the document is not unique.

Additionally or alternatively, a comparison of the obfuscation value of the document to be registered with the obfuscation value of the registered document may be used to determine whether the documents associated with the trade secret registry are different versions of the same document, such as, for example, different versions of source code. For example, the registration system may determine that the similarity between two document confusion values is greater than a threshold similarity. Additionally, in an example, the registration system may determine that entity identifiers indicating entities associated with the document 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 this determination to the client-side device and/or system. Additionally or alternatively, the registration system may generate a record of documents to be registered and may associate the record with records of registered documents. A selectable link can be associated with a record such that when the link is selected via the user interface, the associated record can be displayed.

In examples, 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 one or more processors to perform the operations described herein. For example, the user interface may include a selectable portion indicating an option to register a trade secret in association with a trade secret registry, enabling the user to select and/or identify documents corresponding to the trade secret, enabling the user to view the trade secret registry. Records that enable users to obtain and/or view information associated with insurance policies on trade secrets, enable the valuation of trade secrets, enable the entry of text to generate label data, enable searches of information associated with trade secret registries Records and/or records associated with entities, enable verification of documents registered with respect to the Trade Secrets Registry, and/or display links and/or associations between records.

Additionally or alternatively, the registration system may be configured to determine the value of the trade secret and/or record information related to such valuation. For example, during and/or after registration of a trade secret with a trade secret registry, methods for determining the value of the trade secret and/or recording information related to such valuation may be displayed, such as via a user interface of a client-side device and/or system. options. 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 valuing the trade secret. Such information may include, for example, the type of trade secret, the importance of the trade secret to the entity, the entity's revenues and profits (including, inter alia, those arising from the entity's use of the trade secret), the cost of developing the trade secret, the entity's value, The date of creation of the trade secret, the expected life of the trade secret, etc. Additionally, in an example, the input field may include a request for supporting documentation that includes information that may be relevant to the valuation of the trade secret. In these examples, users can identify supporting documentation. A document obfuscation value may be generated for a given supporting document and/or the supporting document and/or the document obfuscation value may be registered in association with the blockchain. The record of the trade secret may include information associated with the supporting document, such as a corresponding document obfuscation value and/or a cryptographic document obfuscation value corresponding to the block in the blockchain in which the supporting document is registered. The registration system may utilize some or all of this information to generate a value associated with the trade secret.

Additionally or alternatively, the registration system may be configured to utilize access controls to limit access to certain records and/or portions of records. For example, access control data may be stored in association with a registration system. 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 a record may be required 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's obligations associated with the access. Accordingly, the registration system may generate access logs that may indicate the user identifier of the user who accessed a given record, the time value associated with the access to the record, and/or what information was displayed and/or manipulated by the user. Access logs may be used by registration systems to assist in maintaining the confidentiality and/or confidentiality of trade secrets. For example, alerts may be generated and/or sent when records are accessed and/or when unusual activity is detected. In other examples, when a user leaves a company, access records can be used to determine what sensitive information the user viewed and what confidentiality obligations the departing user should be reminded of. In other examples, such as when a trade secret is associated with an insurance policy, the access logs may be used to satisfy one or more conditions of the insurance policy, such as, for example, periodic reminders of confidentiality to users who have accessed the records.

This disclosure provides an overall understanding of the principles of structure, function, manufacture, and use of the systems and methods disclosed herein. One or more examples of the 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 shown or described in connection with one embodiment may be combined with features of other embodiments, including between systems and methods. Such modifications and changes are intended to be included within the scope of the appended claims.

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

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

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 . Memory 116 may include components such as, for example, one or more obfuscation components 118 , tag data generator 120 , communications component 122 , firewall 124 , and/or one or more user interfaces 126 . As shown in FIG. 1, 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 the only examples of components of electronic device 102 .

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

Obfuscation component 118 may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with electronic device 102 and/or remote storage devices accessible to electronic device 102 . Obfuscation component 118 may then generate a document obfuscation value corresponding to the document. Obfuscation component 118 may also be described herein as a hash function and may be configured to map arbitrary size data to fixed size data. Document obfuscation values may also be described herein as hash codes, digests, and/or hashes. A hash function can utilize one or more algorithms to generate document obfuscation values. Algorithms may include, for example, trivial hashing functions, perfect hashing, minimal perfect hashing, hashing uniformly distributed data, hashing data with other distributions, hashing variable-length data, specialized hashing functions, rolling hashing, universal hashing column, hashing with a checksum function, multiplicative hashing, non-linear lookup table hashing, efficient hashing of strings, and/or one or more other hashing algorithms. Generally, obfuscation component 118 may receive text data, image data, formatted data, and/or other data corresponding to a document as input, and may generate document obfuscation values corresponding to the input as output. In an example, electronic device 102 may include multiple obfuscation components, each obfuscation component employing a different hashing algorithm. In these examples, each obfuscation component can output different document obfuscation values for the same document.

Tag data generator 120 may be configured to generate tag data associated with the document. For example, one or more input fields may be caused to be displayed via user interface 126 . Input fields can include requests to "tag" documents or otherwise provide keywords. For example, a document corresponding to source code for operating a sewing machine may be associated with keywords such as "source code," "sewing," "sewing machine," "version 1.1.20," and so on. A user of electronic device 102 may input text corresponding to these tags, and tag data generator 120 may utilize such input to generate tag data. Additionally or alternatively, tag data generator 120 may automatically generate tag data. For example, 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, tag data generator 120 may identify one or more fields of the document and/or values associated with these fields. By way of illustration, tag data generator 120 may identify a title field, a document type field, one or more sections of a document, and the like. Values associated with these fields, such as text data, can be used to generate labels. Additionally or alternatively, the document's text data may be analyzed to determine which words are commonly used in the document, with the user being able to review, edit and/or delete the identified words, for example to ensure that particularly sensitive terms (e.g. , an important element of the trade secret compound). These words can be identified as keywords and used to generate label data.

Communication component 122 may be configured to enable communication between electronic device 102 and other components of architecture 100 such as registration system registration system 104, distributed ledger system 106, and/or underwriter system 108. Communications component 122 may also generate data to be transmitted and/or may format generated data for transmission to one or more of the remote systems. Communications component 122 may also be configured to receive data from one or more of the remote systems.

Firewall 124 may be configured to receive data from communication component 122 and/or from one or more other components of electronic device 102 . 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 instruct the electronic device 102 to be configured to send certain data to the registration system registration system 104 and/or the distributed ledger system 106 and/or the underwriter system 108 . The security rules may also direct the electronic device 102 to be configured to receive certain data from the registration system 104 and/or the distributed ledger system 106 and/or the underwriter system 108 . For example, the security rules may indicate that electronic device 102 is allowed to send document obfuscation values to registration system 104 but is not allowed to send documents to registration system 104 . Firewall 124 may be used to control the distribution of sensitive information, particularly when 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. Memory 132 may include, for example, one or more obfuscation components 134, tag data generator 136, communications component 138, record generator 140, trade secret registry 142, comparison component 144, grouping component 146, valuation 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 and the like. The description of the components of the registration system 104 continues below by way of example. 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 a system and/or device is described herein as a "remote system" and/or "remote device," the system and/or device may be located at a different location than, for example, electronic device 102 .

For example, obfuscation component 134 may perform the same or similar operations as obfuscation component 118 of electronic device 102 . For example, instead of or in addition to electronic device 102 using obfuscation component 118 , registration system 104 may utilize obfuscation component 134 to generate one or more document obfuscation values. In these examples, the electronic device 102 may send data corresponding to the document representing the trade secret to the registration system 104 . Registration system 104 may receive the data and may utilize the data to generate document obfuscation values via obfuscation component 134 . The document obfuscation value may be generated in the same or similar manner as the document obfuscation value generated by obfuscation component 118 . In an example, the registration system 104 may include multiple obfuscation components 134, each obfuscation component 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 can be sent to a different blockchain system for registration, as described elsewhere in this article.

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

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

Communication component 138 may be configured to enable communication between registration system 104 and other components of architecture 100 such as electronic device 102, distributed ledger system 106, and/or underwriter system 108. Communications component 138 may also generate data to be transmitted and/or may format data that has been generated for transmission to other components of architecture 100 . Communications component 138 may also be configured to receive data from one or more of the other remote systems and/or electronic device 102 .

For example, communications component 138 may be configured to generate request data indicating a request to register a trade secret in association with a blockchain, such as the blockchain associated with distributed ledger system 106 . The request data may be sent to the distributed ledger system 106 along with, for example, a document obfuscation value, and/or an identifier of the document and/or trade secret, and/or other information associated with the document and/or trade secret. The distributed ledger system 106 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 block of the blockchain. The distributed ledger system 106 may generate a cryptographic document obfuscation value that represents a block in the blockchain and/or the distributed ledger system 106 may generate an indication of the time and/or time the document obfuscation value (or other data) was registered with the blockchain. Or a time value of a date. Distributed ledger system 106 may send encrypted document obfuscation values, time values, and/or other information (such as, for example, block numbers) to registration system 104 and/or electronic device 102 .

As used in this article, a blockchain is a list and/or ledger of records linked using cryptography, also described as blocks. A block in the blockchain contains the cryptographic hash of the previous block, a time value or timestamp, and in the example, transaction data. Blockchain can 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 registration system 104 to register a trade secret in a trade secret registry. As described in more detail elsewhere in this article, blockchain may also be used to register valuation documents, insurance policy documents, and/or other information associated with a trade secrets registry. Blockchains may be managed by a peer-to-peer network that collectively adheres to protocols for inter-node communication and validation of new blocks. Once recorded in a block, the data cannot be changed without changing all subsequent blocks, which would require a majority of the network to agree.

In an example, multiple blockchain systems may be utilized to register transactions between registration system 104 and electronic device 102 . For example, a document obfuscation value can be sent to multiple blockchain systems, and each blockchain system can return an encrypted document obfuscation value corresponding to a block in its corresponding blockchain. As described more fully below, records indicating registration of a trade secret with trade secret registry 142 may include multiple cryptographic document obfuscation values and/or other information associated with the registration of a block in multiple blockchains.

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

In an example, 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 filing system associated with other intellectual property assets. As described more fully herein with respect to access control component 162, access information may be sent for the access interface. Registration system 104 may receive a request to perform a search of trade secret registry 142, such as from a remote filing 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 the results of the search, and result data representing the results may be sent to the remote filing system and/or electronic device 102 .

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

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

In other examples, comparison component 144 may utilize Levenshtein distance to determine similarity between trade secrets. The confusion value of two documents and/or the Levenstein distance between the documents can be determined. A shorter Levenstein distance can indicate more similarities than a longer Levenstein distance. As used herein, Levenstein distance (also known as edit distance) can be described as a string metric used to measure the difference between two sequences. For example, the Levenstein distance between two words can be thought of as the minimum number of single-character edits required to change one word into the other. Therefore, the Levenstein distance between two very similar words will be shorter than the Levenstein distance between two very different words. In these examples, a Levenstein distance can be determined between two documents and/or two document confusion values representing those documents, with a shorter Levenstein distance indicating more similarity between the documents.

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

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

Valuation component 148 may be configured to identify and/or determine the value associated with a given trade secret. For example, during and/or after registering 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 valuing the trade secret. Such information may include, for example, the type of trade secret, the importance of the trade secret to the entity, the entity's revenues and profits (including, inter alia, those arising from the entity's use of the trade secret), the costs of developing the trade secret information, the entity's value , date of creation of the trade secret, expected life span of the trade secret, etc.

Additionally, in an example, the input field may include a request for supporting documentation that includes information that may be relevant to the valuation of the trade secret. In these examples, users can identify supporting documentation. A document obfuscation value may be generated for a given supporting document and/or the supporting document and/or the document obfuscation value may be registered in association with the blockchain. The record of the trade secret may include information associated with the supporting document, such as a corresponding document obfuscation value and/or a cryptographic document obfuscation value corresponding to the block in the blockchain in which the supporting 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 trade secret. For example, tag data can be used to determine the type of trade secret. Trade secrets of the same or similar type may be analyzed to determine the value of the trade secret in question. Remote system 104 may utilize some or all of this information to generate value associated with the trade secret.

For example, a trade secret may be identified and/or determined as source code and may be indicated as being of significant value to the entity associated with the source code. Input data received from electronic device 102 may indicate that the entity's value is $5,000,000 and that the entity's annual revenue is $1,500,000. Annual profits from use of trade secrets are $400,000. The development cost of the trade secret is $1,000,000. The life expectancy of a trade secret is 10 years. Additionally, the entity may have uploaded documentation confirming some or all of this information. Based at least in part on this information, valuation component 148 may determine the value of the trade secret. In the example, a discounted cash flow analysis can determine the attributable profit stream over the expected life. Comparisons can be made with valuations of other registered trade secrets, such as other source code identified as important, and with company statistics similar to those identified for the entity. Development costs may be considered. These alternative measures may be combined to produce current and projected valuation ranges. In an example, valuation component 148 may place one or more guardrails and/or limits on the value of the trade secret. For example, if the total value of the entity is $5,000,000, you can set a limit that the value of the trade secret cannot exceed $5,000,000. Additionally or alternatively, data may be used to influence the valuation of the trade secret indicating that the trade secret has been registered with the trade secret registry 142, licensed to a third party, insured by an underwriter, and/or as first established by the registry. Since then, users' updates to information associated with trade secrets have become more valuable.

In other examples, quantitative analysis of one or more factors may be used for valuation. For example, factors such as related industry, type of information, scope of intellectual property, duration of intellectual property, specificity and/or uniqueness of intellectual property, degree of confidentiality and/or confidentiality measures implemented, replicability of intellectual property, possibility of misappropriation nature, detectability of trade secrets and/or their misappropriation, and/or overlap with other intellectual property and/or known assets. Other information may also be used, such as the geographical scope of the intellectual property. Values corresponding to these factors may be identified, determined and/or generated and used to determine the value of the trade secret, such as, for example, via a machine learning algorithm.

Policy component 150 may be configured to assist in applying for, underwriting, and providing one or more insurance policies for a given trade secret. For example, upon registration with the trade secret registry 142, an option may be presented to obtain insurance coverage for the trade secret. For example, a selectable portion of user interface 126 may provide the option to apply for an insurance policy. When selected, 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, trade secret type or category, trade secret value (determined from above or identified by the user), desired policy term, desired policy limitations and retentions, entity value, trade secret The date of creation, and/or the part that implements the upload of supporting documentation and/or the requested documentation. In the example of providing supporting documentation, the supporting documentation may be registered with the blockchain in the same or similar manner as described above with respect to supporting documentation for trade secret valuations.

Policy component 150 and/or communication component 138 may be configured to receive input data corresponding to user input and may send the input data to the underwriter system 108 associated with the underwriter. The underwriter system 108 may process the input data and, in one example, underwrite and/or issue a policy that insures against misappropriation of trade secrets, for example. In these examples, confirmation data indicating that the policy has been issued and information associated with the policy may be received from the underwriter system 108 . This information may be incorporated into the record associated with the trade secret and may be displayed via user interface 126 in the example. Some non-limiting examples of information associated with an insurance policy may include policy type, liability limits, retained value, policy premium, policy form, policy number, policy term, liability sublimits, and/or a valuation of trade secrets. Additionally or alternatively, the information may include one or more payment values that correspond to payments to be made to the entity associated with the trade secret upon the occurrence of different categories of events, including different levels of unauthorized access or use. Amount associated. In these examples, policy component 150 may receive noncompliance data indicating that the entity has not complied with a condition of the insurance policy and may cause updated insurance policy information to be displayed, including an indication that treatment action is required and/or updated payment values. In these examples, the updated payout value may be less than the original payout value. When conditions are met, the payout value can be updated to reflect compliance with the policy conditions.

In an example, one or more smart contracts may be used in association with policy component 150 . For example, smart contracts linked to the blockchain can be used to associate an insurance policy with a given trade secret. As described herein, a smart contract may be a computer protocol that digitally facilitates, verifies, and/or enforces the negotiation and/or performance of a contract. Transactions involving smart contracts may be traceable and irreversible. Smart contracts can utilize, for example, Byzantine fault-tolerant algorithms, which can achieve digital security through decentralization of contracts. Smart contracts may be initiated, hosted, and/or implemented, at least in part, by a distributed ledger system 106 associated with a blockchain. In these examples, the smart contract may indicate conditions that substantiate the insurance policy, such as the sponsor's continued investment in digital threshold levels and/or physical security, and may receive substantiation data indicating that the conditions have been met. In these examples, the substantiation data can be sent to the distributed ledger system 106, which can enable the smart contract to substantiate 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 trade secret valuation determination or support. Additionally or alternatively, wizard 152 may be used to receive user input for insurance policy application, underwriting and offering. In examples where an insurance policy is provided using wizard 152, wizard 152 and/or information associated with wizard 152 may be provided by a given underwriter and/or may be specific to a given underwriter. Additionally or alternatively, wizard 152 may be utilized to submit notifications of potential misappropriation events and/or insurance claims, as described more fully herein.

Verification component 154 may be configured to verify that information contained in a particular document has been registered with trade secret registry 142 . For example, once enrolled, the verification component 154 may be used to determine whether other information, such as information that has been allegedly stolen, matches or is similar to information contained in the enrolled document and/or to verify other information, such as information that has been allegedly stolen. ) matches or is similar to information contained in a registered document. In these examples, the compromised information (eg, in the form of an alleged document) may be identified as part of the user verification request, such as via user interface 126 of electronic device 102 . Document obfuscation values may be generated for accused documents in the same or similar manner as described above with respect to obfuscation components 118, 134. The verification component 154 may be used to analyze the document obfuscation value of the accused document relative to other document obfuscation 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 accused document or document segment, the verification component 154 may determine that the accused document is the same as or similar to the registered document or document segment. In other examples, verification component 154 may determine the similarity between the accused document and one or more registered documents. Determining the similarity may be performed as described above with respect to comparison component 144 . In these examples, when the similarity reaches or exceeds the threshold similarity, it can be determined that the accused document is similar to the registered document. In other examples, verification component 154 may be configured to determine which portions of the accused document match or are similar to at least one registered document. An indication of matching or similar portions may be displayed, such as via user interface 126 . Additionally, where multiple versions of a document have been registered, verification component 154 may be configured to determine which of the multiple versions is most similar to the accused document and may provide an indication of the most similar version.

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

Linking component 158 may be configured to associate one record with one or more other records of trade secret registry 142 . For example, 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, linking component 158 may be utilized to generate an association between the records. Generating the association may include storing data indicating that the records are associated. Generating associations may also or alternatively include generating links or other similar functionality that may be displayed with the record via user interface 126 . For example, a link may correspond to a selectable portion of user interface 126 that, when selected, may cause the linked record and/or a portion thereof to be displayed.

Access database component 160 may be configured to store data indicative of access details of one or more records associated with trade secret registry 142 . For example, access control data may be stored in association with registration system 104 . Access control data may indicate who is authorized to view a given record and/or given information associated with the record. In these examples, access control component 162 may be configured to require the user to authenticate the user's identity in order to access the record, such as by entering a username and/or password, for example. Accordingly, the registration system 104 may generate access logs that may indicate the user identifier of the user who accessed a given record, the time value associated with the recorded access, and/or what information was displayed and/or manipulated by the user. Access logs may be used by the registration system 104 to assist in maintaining the confidentiality and/or confidentiality of trade secrets. For example, alerts may be generated and/or sent when records are accessed and/or when unusual activity is detected. In other examples, when a user leaves a company, access records can be used to determine what sensitive information the user viewed and what confidentiality obligations the departing user should be reminded of. In other examples, such as when a trade secret is associated with an insurance policy, the access logs may be used to satisfy one or more conditions of the insurance policy, such as, for example, periodic reminders of confidentiality to users who have accessed the records. It will be appreciated that the systems and/or user interfaces described herein may be used to assist audits in maintaining the confidentiality of trade secrets and/or in complying with policies and/or rules associated with trade secret maintenance, such as for insurance policy purposes. Scheduled, periodic and/or random reminders may be sent to devices associated with the entity registering a given trade secret. Alerts may request that certain tasks be performed and/or certain information should 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 a device to display the user interface to identify one or more priority tiers, which may otherwise be described as priority levels, to be consistent with a given Trade secrets are associated. For example, if a user specifies a trade secret with a high priority tier, certain operations may be prohibited, access controls may be stricter, security measures may be stronger, and/or when a trade secret is disclosed, a given non-disclosure Agreements (which may be informal and/or non-boilerplate non-disclosure agreements) are identified, finalized and/or generated. As another example, if a user specifies a trade secret with a low priority tier, some actions may be enabled that would not be enabled for higher tiers, access controls may be less stringent than those for higher tiers, and/or when the trade secret is disclosed , forms and/or standard non-disclosure agreements may be identified, determined and/or generated.

In the example of linking two records, as described more fully with respect to linking component 158, access control data may be utilized to allow or disable access to the linked record and/or portions of the linked record. For example, a given user may have been provided access to a first record but not a linked second record. In these examples, the first record may be displayed to the user, but when the user attempts to select a portion of the user interface 126 that corresponds to a link to the second record, the access control data may be utilized to prevent the second record from being displayed. In other examples, the user may have been authorized to access some information associated with the first record, but not other information associated with the first record. Thus, only a portion of the first record may be displayed to the user, while other portions of the record 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 trade secrets are versions of the same document and/or trade secret. For example, as described more fully above, results from comparison component 144 may 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 trade secret type. Using some or all of this information, version control component 164 can determine that the two documents are versions of the same document. This versioning indication may be stored relative to the record associated with the document and/or a visual indication may be displayed via user interface 126 .

Versioning component 164 may also be configured to generate alerts and/or reminders for document versioning. For example, version control component 164 may determine that a version of a particular trade secret was registered for a given entity at a given time historically and/or within a given time frame. If the version is not registered in a manner consistent with historical trends, an alert and/or reminder for the registered 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 the trade secret has been registered in a manner consistent with that trend. The version is registered in this way. If a version is not registered as such, alerts and/or reminders may be generated and sent.

As shown in FIG. 1 , several components of the registration system 104 , the distributed ledger system 106 , and/or the underwriter system 108 and the associated functionality of those components as described herein may be operated by one or more of the other remote systems and /or executed by the electronic device 102 . Additionally or alternatively, some or all of the components and/or functions associated with electronic device 102 may be performed by registration system 104 , distributed ledger system 106 , and/or underwriter system 108 .

It should be noted that the exchange of such information can only be carried out if the User agrees to the exchange of data and/or information described herein. For example, users may be provided with the opportunity to opt-in and/or opt-out of the exchange of data between devices and/or with remote systems 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, it may be obtained before performing some, any, or all of the operations and/or processes described herein. User agrees.

It should be understood that wherever the term "trade secret" is used in this disclosure, care is taken to include not only trade secrets, but also any documents and/or data and/or information that includes confidential information, know-how and other information, and not Must be documents, data and/or information that meet 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 a processor with multiple cores. Additionally, 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 the like. In one implementation, the processor may include a microcontroller and/or microprocessor. Processors 112 and/or 128 may include a graphics processing unit (GPU), a microprocessor, a digital signal processor, or other processing unit or component 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. For example, and without 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), systems on a chip (SOCs), complex programmable Logic devices (CPLD), etc. 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, programs parts 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 disk (DVD) or other optical storage device, tape cassette, magnetic tape, magnetic disk storage device or other magnetic storage device, RAID storage system or any other medium that can be used to store the required information and can be accessed by the 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 can be accessed by processor 112 and/or 128 to execute instructions stored on memory 116 and/or 132 medium. In a 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 device that can be used to store required information and that can be accessed by the processor. Tangible medium.

Furthermore, functional components may be stored in corresponding memories, or the same functionality may alternatively be implemented in hardware, firmware, an application specific integrated circuit, a field programmable gate array, or as a system-on-a-chip (SoC). Additionally, 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 I/O of the respective device, such as a network interface, A hardware resource device such as a device, etc., and provides various services to applications or components executing on the processor. Such OS parts may implement: Variants of the FreeBSD operating system released by the FreeBSD Project; other UNIX or UNIX-like variants; variants of the Linux operating system released by Linus Torvalds; Amazon.com from Seattle, Washington, USA The company's FireOS operating system; Windows operating system from Microsoft Corporation of Redmond, Washington, USA; such as LynxOS released by LynxSoftware Technologies of San Jose, California; such as the embedded operating system (Enea OSE) released by ENEA AB of Sweden )etc.

Network interfaces 114 and/or 130 may enable messages between components and/or devices illustrated 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 network 110 .

For example, each of network interfaces 114 and/or 130 may include a personal area network (PAN) component to enable messaging over one or more short-range wireless message channels. For example, the PAN component may enable messages conforming 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 message protocol. Additionally, each of network interfaces 114 and/or 130 may include wide area network (WAN) components to enable messaging over the wide area network.

In some cases, registration system 104 may be local to the environment associated with electronic device 102 . For example, remote system 104 may be located within electronic device 102. In some cases, some or all of the functions of remote system 104 may be performed by electronic device 102 . Furthermore, while the 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 the processor to perform certain operations, it should be understood that the operations described may be performed by some or All parts and/or other parts not specified are performed.

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

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

Selection of the first selectable portion 204 may cause the user interface 202 to display a fourth selectable portion 210 at step 2 indicating options for identifying documents representing trade secrets to be registered with the trade secret registry. For example, identification of a document may include input such as a naming indicator for the document and/or selecting the document from a database of the electronic device displaying user interface 202 . The document can be identified and the electronic device can cause a document obfuscation value corresponding to the document to be generated. 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 device and/or remote storage devices accessible to the electronic device. The obfuscation component can then generate a document obfuscation value corresponding to the document. Generally, an obfuscation component may receive text data, image data, formatted data, and/or other data corresponding to a document as input, and may generate a document obfuscation value corresponding to the input as output. In an example, the electronic device may include multiple obfuscation components, each obfuscation component employing a different hashing algorithm. In these examples, each obfuscation component can output different document obfuscation values for the same document.

At step 3, user interface 202 may include a naming indicator 212 for the document. User interface 202 may also include document obfuscation values 214 generated based at least in part on the document. As shown in Figure 2, for example, the document's naming indicator 212 is "Document 1" and the document obfuscation value 214 is "0xaafdee662b084f7378f1ad91bfe08bdb34de1e801efb61103043fc62bd8963f."

At step 4, user interface 202 may include one or more dialog boxes and/or input fields 216 associated with the trade secret. Input field 216 may include text requesting information from the user regarding the trade secret. As shown in Figure 2, for example, input field 216 may request information such as a trade secret name, a description of the trade secret, and/or one or more labels for the trade secret. For example, a document corresponding to source code for operating a sewing machine may be associated with keywords such as "source code," "sewing," "sewing machine," "version 1.1.20," and so on. A user of the electronic device may input text corresponding to these tags, and a tag data generator may utilize such input to generate tag data. Additionally or alternatively, the label data generator may automatically generate label 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, a tag data generator may identify one or more fields of a document and/or values associated with those fields. As an illustration, the tag data generator can identify a title field, a document type field, one or more sections of a document, etc. Values associated with these fields, such as text data, can be used to generate labels. Additionally or alternatively, the document's text data can be analyzed to determine which words are commonly used in the document. These words can be identified as keywords and used to generate label data.

At step 5, the user interface 202 may display text indicating the status of the registration process and/or operations performed by a remote system such as a remote system associated with a trade secret registry and/or a remote system associated with a blockchain. describe. For example, the text might state that a transaction is pending, and it might state that trade secrets and/or document obfuscation values are being submitted to the blockchain. Upon displaying the text, the communication component may generate request data indicating a request to register the trade secret in association with the blockchain. The request data may be sent to a remote system associated with the blockchain along with, for example, a document obfuscation value, and/or an identifier of the document and/or trade secret, and/or other information associated with the document and/or 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 block of the blockchain. The remote system may generate a cryptographic document obfuscation value representing a block in the blockchain and/or the remote system may generate a time value indicating the time and/or date when 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, a block number) to the remote system associated with the trade secret registry.

In an example, multiple blockchain systems may be utilized to register transactions between trade secret registration systems and electronic devices. For example, a document obfuscation value can be sent to multiple blockchain systems, and each blockchain system can return an encrypted document obfuscation value corresponding to a block in its corresponding blockchain. As described more fully below, a record indicating registration of a trade secret with a trade secret registry may include multiple cryptographic document obfuscation values and/or other information associated with registering a block in multiple blockchains.

At step 6, user interface 202 may display a record indicating that the trade secret has been registered with the trade secret registry. Records may include record identifiers 218, trade secret details 220, and/or transaction details 222. Record identifier 218 may include numbers and/or letters that identify the record relative to the trade secret registry. For example, trade secret details 220 may include a naming indicator of the trade secret, a description of the trade secret, a naming indicator of a document representing the trade secret, and/or a tag generated as described elsewhere herein. Transaction details 222 may include the status of registration with the trade secret registry, a document obfuscation value, a block number associated with the block in which the trade secret was registered to the blockchain, a cryptographic document obfuscation value (also described as a block document obfuscation value ) and/or block timestamp. Other information that may be included in the record and displayed with respect to user interface 202 may include insurance policy details, valuation details, and/or other information associated with trade secrets, as described more fully elsewhere herein.

Records may be generated by a record generator of a remote system associated with the trade secret registry. Records may be stored in the Trade Secrets Registry along 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 send the confirmation data to the electronic device for display via user interface 202 .

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

For example, at step 1, the user interface 302 may include a first selectable portion 304 indicating an option to register the trade secret with a trade secret registry. The user interface 302 may also include a second selectable portion 306 indicating options for managing registered trade secrets, and/or a third selectable portion indicating options for verifying that documents have been registered in association with the trade secret registry. 308. To illustrate the use and functionality of user interface 302, a user may provide input indicating selection of second selectable portion 306. It should be understood that, in examples, the first, second, and third selectable portions 304, 306, 308 of the user interface 302 may be the same as the first, second, and third selectable portions of the user interface 202 described with respect to FIG. 2 204, 206, 208 are the same or similar (and can be functionally similar).

Selection of the second selectable portion 306 may cause the user interface 302 to display, at step 2, information associated with the trade secret that has been registered in association with the trade secret registry. In an example, a trade secret indicator 310 may be displayed. Trade secret indicator 310 may include information that describes and/or summarizes a given trade secret. As shown in Figure 3, for example, the information may include a name of the trade secret, a date the trade secret was registered in association with a trade secret registry, and/or a label associated with the trade secret. In this manner, trade secret indicator 310 provides an indication of the trade secret associated with the trade secret registry without, in the example, providing all information for each record of the trade secret. In an example, trade secret indicator 310 may be limited to those trade secrets associated with a given entity and/or entity identifier. Additionally or alternatively, the trade secret indicator 310 may be limited to those trade secrets that a user logged in using certain access credentials is authorized to view.

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

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

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

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

Selection of the third selectable portion 306 may cause the user interface 302 to display a fourth selectable portion 410 at step 2 indicating options for identifying, for example, documents alleged to have been misappropriated. In these examples, documents may be obtained from third parties who may be accused of misappropriating or otherwise obtaining trade secrets without permission. For example, identification of the accused document may include input, such as a naming indicator of the document and/or selection of the document from a database of, for example, the electronic device displaying user interface 402. The document can be identified and the electronic device can cause a document obfuscation value corresponding to the document to be generated. 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 device and/or remote storage devices accessible to the electronic device. The obfuscation component can then generate a document obfuscation value corresponding to the document. Generally, the obfuscation component may receive as input text data, image data, video data, formatted data, and/or any other data corresponding to documents and/or files representing trade secrets, and may generate a document obfuscation value corresponding to the input as output. In an example, the electronic device may include multiple obfuscation components, each obfuscation component employing a different hashing algorithm. In these examples, each obfuscation component can output different document obfuscation values for the same document.

At step 3, user interface 402 may display verification status 412, similarity indicator 414, and/or identifier 416 of registered trade secrets determined to match and/or be similar to the accused document. For example, the verification component may be configured to verify that a particular document has been registered with a trade secret registry. For example, once registered, the verification component may be used to determine whether another document (such as a document that is alleged to have been compromised) matches or is similar to the registered document and/or to verify that another document (such as a document that is alleged to have been compromised) is consistent with the registered document. Registration documents match or are similar. The verification component may be used to analyze the document obfuscation value of the accused document relative to other document obfuscation values of the registered document. If the verification component determines that at least one of the registered document obfuscation values matches the document obfuscation value of the accused document, the verification component may determine that the accused document is the same as or similar to the registered document. In other examples, the verification component may determine the similarity between the accused document and one or more registered documents.

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

As shown in the example in Figure 4, verification status 412 is "Document Verified," indicating that the accused document matches or is similar to at least one registered trade secret. The similarity indicator 414 is "97% match with registered documents" indicating that the accused document is 97% similar to at least one of the registered documents. It should be understood that the specific writing of verification status 412 and/or similarity indicator 414 is provided as an example and not as a limitation. Other forms of verification status and/or similarity indicators may be provided. Additionally, while similarity is expressed as a percentage in Figure 4, other forms of describing similarity are included in this disclosure. Additionally, the identifier 416 of the registered trade secret is "Name: Trade Secret 1". This can provide users with an indication of registered trade secrets similar to the accused document.

In an example, user interface 402 may display a dialog box and/or input field that includes text associated with submitting an insurance coverage claim in connection with an insurance policy for trade secrets. In these examples, one or more wizards may be launched to assist in filing an insurance coverage claim, given the potential for an assertion of trade secret misappropriation or other legal claim given the similarity between the alleged document and a registered trade secret. Input data representing a response to the dialog box may be received, and based at least in part on receiving the input data, the input data may be formatted and/or sent to a remote system associated with the insurer indicating that a claim is to be filed and/or that the Notify insurer of potential misappropriation and/or other legal action.

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

At step 1, user interface 502 may display records indicating trade secrets that have been registered with the trade secret registry. Records may include record identifiers 504 , trade secret details 506 , and/or transaction details 508 . Record identifier 504 may include numbers and/or letters that identify the record relative to the trade secret registry. For example, trade secret details 506 may include a naming indicator of the trade secret, a description of the trade secret, a naming indicator of a document representing the trade secret, and/or a tag generated as described elsewhere herein. Transaction details 508 may include the status of registration with the trade secret registry, a document obfuscation value, a block number associated with the block in which the trade secret was registered to the blockchain, a cryptographic document obfuscation value (also described as a block document obfuscation value ) and/or block timestamp. Additionally, user interface 502 may include 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 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 insurance policies for a given trade secret. Information requested via input field 512 may include, for example, the trade secret type or category, the value of the trade secret (determined from above or identified by the user), the policy term, the entity value, the date the trade secret was created, and/or enabling upload supporting documentation. and/or the portion of the requested document. In the example of providing supporting documentation, the supporting documentation may be registered with the blockchain in the same or similar manner as described above with respect to supporting documentation for trade secret valuations.

The electronic device and/or the policy component and/or another component of the trade secret registration system may be configured to receive input data corresponding to user input and may send the input data to a remote system associated with the insurer. The remote system can process the input data and, in one example, issue an insurance policy ensuring that trade secrets are not misappropriated. In these examples, confirmation data indicating that a policy has been issued and information associated with the policy may be received from the remote system. This information, described as policy details 514, may be incorporated into records associated with the trade secret and may be displayed via user interface 502 at step 3 in the example. Some non-limiting examples of policy details 514 may include policy type, liability limit, retained value, policy premium, policy form, policy number, policy term, liability sublimits, and/or valuation of trade secrets. Additionally or alternatively, the policy details 514 may include a payment value associated with an amount to be paid to the entity associated with the trade secret upon the occurrence of the event. In these examples, the policy component may receive compliance data indicating that the entity has not complied with a condition of the insurance policy and may cause updated insurance policy information, including updated payment values, to be displayed. In these examples, the updated payout value may be less than the original payout value. When conditions are met, the payout value can be updated to reflect compliance with the policy conditions.

In an example, one or more smart contracts may be utilized in association with policy components. For example, smart contracts linked to the blockchain can be used to associate an insurance policy with a given trade secret. As described herein, a smart contract may be a computer protocol that digitally facilitates, verifies, and/or enforces the negotiation and/or performance of a contract. Transactions involving smart contracts may be traceable and irreversible. Smart contracts can utilize, for example, Byzantine fault-tolerant algorithms, which can achieve digital security through decentralization of contracts. Smart contracts may be initiated, hosted, and/or implemented, at least in part, by a remote system associated with a blockchain. In these examples, the smart contract may indicate the conditions for substantiating the insurance policy and may receive substantiation data indicating that the conditions have been met. In these examples, the substantiation data can be sent to the distributed ledger system 106, which can enable the smart contract to substantiate the insurance policy.

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

At step 1, user interface 602 may display records indicating trade secrets that have been registered with the trade secret registry. Records may include record identifiers 604, trade secret details 606, and/or transaction details 608. Record identifier 604 may include numbers and/or letters that identify the record relative to the trade secret registry. For example, trade secret details 606 may include a naming indicator of the trade secret, a description of the trade secret, a naming indicator of a document representing the trade secret, and/or a tag generated as described elsewhere herein. Transaction details 608 may include the status of registration with the trade secret registry, a document obfuscation value, a block number associated with the block in which the trade secret was registered to the blockchain, a cryptographic document obfuscation value (also described as a block document obfuscation value ) and/or block timestamp. Additionally, user interface 602 may include selectable portion 610 indicating options for determining the value of the trade secret.

At step 2, based at least in part on 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 may be configured to identify and/or determine the value associated with a given trade secret. Information requested by input field 612 may include, for example, the type of trade secret, importance of the trade secret to the entity, entity revenue, entity value, date the trade secret was created, etc.

Additionally, in an example, input field 612 may include a request for supporting documentation that includes information that may be relevant to the valuation of the trade secret. In these examples, users can identify supporting documentation. A document obfuscation value may be generated for a given supporting document and/or the supporting document and/or the document obfuscation value may be registered in association with the blockchain. The record of the trade secret may include information associated with the supporting document, such as a corresponding document obfuscation value and/or a cryptographic document obfuscation value corresponding to the block in the blockchain in which the supporting 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 trade secret. For example, tag data can be used to determine the type of trade secret. Trade secrets of the same or similar type may be analyzed to determine the value of the trade secret in question. Remote system 104 may utilize some or all of this information to generate value associated with the trade secret.

For example, a trade secret may be identified and/or determined as source code and may be indicated as being of significant value to the entity associated with the source code. Input data received from the electronic device may indicate that the entity's value is $5,000,000 and that the entity's annual revenue is $350,000. Additionally, the entity may have uploaded documentation confirming some or all of this information. Based at least in part on this information, the valuation component can determine the value of the trade secret. In an example, comparisons may be made between other registered trade secrets, such as other source code identified as important, and comparisons to company statistics similar to those identified for the entity. In an example, the valuation component may place one or more guardrails and/or limits on the value of the trade secret. For example, if the total value of the entity is $5,000,000, you can set a limit that 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 the amount of time since the trade secret was registered may be used to affect the valuation 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, described as valuation details 614, may be incorporated into the record associated with the trade secret and may be displayed via user interface 602 in step 3 in the example. Some non-limiting examples of valuation details 614 may include value, trade secret type, trade secret creation date, entity value, entity revenue value, and/or one or more selectable links that, when selected, may cause the display Supporting documentation (if any) provided for valuation purposes.

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

At step 1, user interface 702 may include an authentication screen requesting user input to authenticate access to records associated with the trade secret registry. For example, 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 by a remote system associated with the trade secret registry.

Upon authenticating the user input, at step 2, the user interface 702 may include a first selectable portion 708 indicating an option to register the trade secret with a trade secret registry. User interface 702 may also include a second selectable portion 710 indicating options for managing registered trade secrets, and/or a third selectable portion indicating options for verifying that documents have been registered in association with the trade secret registry. 712. To illustrate the use and functionality of user interface 702, a user may provide input indicating selection of second selectable portion 710. It should be understood that, in examples, the first, second, and third selectable portions 708, 710, 712 of the user interface 702 may be the same as the first, second, and third selectable portions of the user interface 202 described with respect to FIG. 204, 206, 208 are the same or similar (and can be functionally similar).

Selection of the second selectable portion 710 may cause the user interface 702 to display, at step 3, information associated with the trade secret that has been registered in association with the trade secret registry. In an example, a trade secret indicator 714 may be displayed. Trade secret indicator 714 may include information that describes and/or summarizes a given trade secret. As shown in Figure 7, for example, the information may include a name of the trade secret, a date the trade secret was registered in association with a trade secret registry, and/or a label 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 without, in the example, providing all information for each record of the trade secret. In an example, trade secret indicator 714 may be limited to those trade secrets associated with a given entity and/or entity identifier. Additionally or alternatively, the trade secret indicator 714 may be limited to those trade secrets that a user logged in using certain access credentials is authorized to view.

In an example, the trade secret indicator 714 may be selectable and, when selected, may cause the records associated with the trade secret indicator 714 to be displayed at step 4. As shown in Figure 7, the user can provide input corresponding to the selection of "Trade Secret 1". Selection of the trade secret indicator may cause records associated with "Trade Secret 1" to be displayed at step 4. As shown in Figure 7, the record may include the same or similar information as the record described with respect to Figure 2, including record identifiers, 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 a portion of the record based at least in part on access control data associated with authentication information provided by the user for access to the system. For example, as shown in Figure 7, the access control data associated with a user viewing the record indicates that the user has permission to view the record identifier, trade secret details, and transaction details, but does not have permission to access certain valuation details. For example, access control data indicates that access is granted for trade secret type and creation date, but access is prohibited for value, entity value, and/or revenue value. Thus, entities associated with the system can set access authorizations and determine what information will be available to a given individual. Additionally or alternatively, the access control data may indicate that a given individual is authorized to utilize certain features of the trade secret registry but is prohibited from utilizing other features. 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 records, such as adding, removing, and/or changing tags.

At step 5, the user interface may display the trade secret indicator 714 again. 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. Accordingly, upon selection of the trade secret indicator 714 corresponding to "Trade Secret 2," at step 6, the user interface 702 may display information indicating that access is prohibited or otherwise denied. 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 the linked record when a link is selected.

Figures 8-23 illustrate the process of digital property authentication and management. The processes described herein are shown as a collection of blocks in a logic flow diagram that represent a sequence of operations, some or all of which may be implemented in hardware, software, or a combination thereof. In the context of software, a block may represent computer-executable instructions stored on one or more computer-readable media that, when executed by one or more processors, program the processor to perform the enumerated operate. Generally speaking, computer-executable instructions include routines, programs, objects, components, data structures, etc. that perform specific functions or implement specific data types. Unless otherwise noted, the order of the description boxes should not be construed as a limitation. Any number of the described blocks may be combined in any order and/or in parallel to implement a process or alternative process, and not all blocks need to be executed. For purposes of this discussion, processes are described with reference to the environments, architectures, and systems described in the examples herein, such as, for example, those described with respect to FIGS. 1-7 , but the processes may be in a wide variety of other environments, architectures, and systems. accomplish.

8 illustrates a flow diagram of an exemplary process 800 for trade secret registration 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 limiting, and any number of the described operations may 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 registration system associated with a trade secret registry, 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 the 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 representing a trade secret. For example, the selectable portion and/or another portion of the user interface may include text requesting a user of the user interface to select the selectable portion to identify documents to be registered as trade secrets 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. Input can include selecting a naming indicator for the document.

At block 804, 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 device and/or remote storage devices accessible to the electronic device. The obfuscation component can then generate a document obfuscation value corresponding to the document. Generally, an obfuscation component may receive text data, image data, formatted data, and/or other data corresponding to a document as input, and may generate a document obfuscation value corresponding to the input as output. In an example, the electronic device may include multiple obfuscation components, each obfuscation component employing a different hashing algorithm. In these examples, each obfuscation component can output different document obfuscation values 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 the trade secret registry. For example, the document obfuscation value may be received from an electronic device, such as via a firewall. Additionally, the electronic device may have generated and sent 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, the communications component of the registration system may be configured to generate an instruction to register the business in association with a blockchain, such as a blockchain associated with a distributed ledger system. Secret request data. The request data may be sent to the distributed ledger system along with, for example, a document obfuscation value, and/or an identifier of the document and/or trade secret, and/or other information associated with the document and/or trade secret.

At block 808, process 800 may include the distributed ledger system generating a cryptographic document obfuscation value corresponding to the block in the blockchain. For example, the distributed ledger 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 block of the blockchain. The distributed ledger system may generate a cryptographic document obfuscation value that represents a block in the blockchain and/or the distributed ledger system may generate a time and/or date indicating the registration of the document obfuscation value (or other data) with the blockchain. time value. The distributed ledger system may send encrypted document obfuscation values, time values, and/or other information (such as, for example, block numbers) to registration systems and/or electronic devices. At block 810, process 800 may include the registration system receiving the encrypted document obfuscation value from the distributed ledger system.

At block 812, process 800 may include the registration system generating a record corresponding to the trade secret in the trade secret registry. For example, the registration system's record generator can then generate records in a trade secrets registry. For example, a record may include an identifier for the record, a naming indicator for the trade secret, a description of the trade secret, a naming indicator for the document, one or more tags, a status identifier for the record, a document obfuscation value, an encrypted document obfuscation value, a zone Block number, time value (also described as block timestamp), insurance policy details, valuation details, and/or other information associated with trade secrets. Records may be stored in the Trade Secrets Registry along with one or more other records.

At block 814, process 800 may include the registration system generating tag data associated with the document. For example, a 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 the electronic device. Input fields can include requests to "tag" documents or otherwise provide keywords. For example, a document corresponding to source code for operating a sewing machine may be associated with keywords such as "source code," "sewing," "sewing machine," "version 1.1.20," and so on. A user of the electronic device may input text corresponding to these tags, and a tag data generator may utilize such input to generate tag data. Additionally or alternatively, the label data generator may automatically generate label 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, a tag data generator may identify one or more fields of a document and/or values associated with those fields. As an illustration, the tag data generator can identify a title field, a document type field, one or more sections of a document, etc. Values associated with these fields, such as text data, can be used to generate labels. Additionally or alternatively, the document's text data can be analyzed to determine which words are commonly used in the document. These words can be identified as keywords and used to generate label data.

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

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

At block 820, process 800 may include the electronic device causing display of information associated with the record. Displaying information associated with a record may include information such as that described herein, for example with respect to FIGS. 1-7.

9 illustrates a flow diagram of an exemplary process 900 for trade 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 limiting, and any number of the described operations may 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 registration system associated with a trade secret registry, 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 an accused document and/or an identifier of the accused document. For example, a selectable portion of the user interface may be displayed on the electronic device indicating options for identifying documents that have been alleged to have been misappropriated, for example. In these examples, documents may be obtained from third parties who may be accused of misappropriating or otherwise obtaining trade secrets without permission. For example, identification of the accused 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.

At block 904, process 900 may include the electronic device generating a document obfuscation value corresponding to the accused document. For example, a document may be identified and the electronic device may cause a document obfuscation value to be generated 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 device and/or remote storage devices accessible to the electronic device. The obfuscation component can then generate a document obfuscation value corresponding to the document. Generally, an obfuscation component may receive text data, image data, formatted data, and/or other data corresponding to a document as input, and may generate a document obfuscation value corresponding to the input as output. In an example, the electronic device may include multiple obfuscation components, each obfuscation component employing a different hashing algorithm. In these examples, each obfuscation component can output different document obfuscation values for the same document.

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

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

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

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

At block 912, process 900 may include the distributed ledger system verifying that similar document obfuscation values have been registered to the blockchain. For example, it may be determined that the accused document obfuscation value matches the registered document obfuscation value. In these examples, it may be advantageous to verify that the registered document obfuscation value corresponds to the trade secret registered to the blockchain. Accordingly, the alleged document obfuscation value can be submitted to a distributed ledger system, which can search the blockchain for matching registered document obfuscation values and/or areas in the blockchain representing registered trade secrets. The block's corresponding encrypted document obfuscation value.

At block 914, process 900 may include the registration system generating verification data identifying similar trade secrets and, in an example, validating the registration to the blockchain. The registration system may receive data from the distributed ledger system indicating that the alleged 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, process 900 may include the electronic device receiving verification data. For example, the verification status of the verification data may indicate that the accused document matches or is similar to at least one registered trade secret. The similarity indicator may indicate that the accused document is similar to at least one of the registered documents, such as by a percentage. Additionally, an identifier of the registered trade secret may be provided. This can provide users with an indication of registered trade secrets similar to the accused document.

At block 918, process 900 may include the electronic device launching a claim submission wizard to initiate a process of filing an insurance claim associated with the trade secret. In an example, the user interface may display a dialog box and/or input field that includes text associated with submitting an insurance coverage claim in connection with an insurance policy for the trade secret. In these examples, one or more wizards may be launched to assist in filing an insurance coverage claim, given the potential for an assertion of trade secret misappropriation or other legal claim given the similarity between the alleged document and a registered trade secret. Input data representing a response to the dialog box may be received, and based at least in part on receiving the input data, the input data may be formatted and/or sent to a remote system associated with the insurer indicating that a claim is to be filed and/or that the Notify insurer of potential misappropriation and/or other legal action.

Figure 10 shows a flow diagram of an exemplary process for digital property authentication. The order in which operations or steps are described is not intended to be construed as limiting, and any number of the described operations may 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 that represents a trade secret. For example, the user interface may include a selectable portion that, when selected, may identify a document representing a trade secret. For example, the selectable portion and/or another portion of the user interface may include text requesting a user of the user interface to select the selectable portion to identify documents to be registered as trade secrets 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. Input can include selecting a naming indicator for the document.

At block 1004, process 1000 may include receiving input at the electronic device indicating that the document is to be registered with a trade secret registry associated with a registration 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 selected by the user to indicate that the document is to be registered with the Trade Secrets Registry.

At block 1006, process 1000 may include generating a document obfuscation value representative of 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 device and/or remote storage devices accessible to the electronic device. The obfuscation component can then generate a document obfuscation value corresponding to the document. Generally, an obfuscation component may receive text data, image data, formatted data, and/or other data corresponding to a document as input, and may generate a document obfuscation value corresponding to the input as output. In an example, the electronic device may include multiple obfuscation components, each obfuscation component employing a different hashing algorithm. In these examples, each obfuscation component can output different document obfuscation values for the same document.

At block 1008, 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, the distribution The ledger system can also be described in this article as a second remote system. For example, the communication component of the electronic device may format and/or transmit the document obfuscation value to the registration system and may generate request data for transmission to the registration system and/or the distributed ledger system.

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

The distributed ledger 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 block of the blockchain. The distributed ledger system may generate a cryptographic document obfuscation value that represents a block in the blockchain and/or the distributed ledger system may generate a time and/or date indicating the registration of the document obfuscation value (or other data) with the blockchain. time value. The distributed ledger system may send encrypted document obfuscation values, time values, and/or other information (such as, for example, block numbers) to registration systems and/or electronic devices. The registration system and/or electronic device may receive the encrypted document obfuscation value from the distributed ledger system.

At block 1012, process 1000 may include sending second request data from the electronic device to the first remote system, the second request data representing a second request to register the document with the trade secret registry. This request data can 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 a trade secret registry that: indicates that the trade secret has been registered in the trade secret registry; includes an encrypted document obfuscation value; and indicates an encrypted document obfuscation value A time value associated with at least one of the generation of the record or the generation of the record. For example, the registration system's record generator can then generate records in a trade secrets registry. For example, a record may include an identifier for the record, a naming indicator for the trade secret, a description of the trade secret, a naming indicator for the document, one or more tags, a status identifier for the record, a document obfuscation value, an encrypted document obfuscation value, a zone Block number, time value (also described as block timestamp), insurance policy details, valuation details, and/or other information associated with trade secrets. Records may be stored in the Trade Secrets Registry along with one or more other records.

At block 1016, 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 the record has been generated.

At block 1018, process 1000 may include sending confirmation data from the first remote system to the electronic device. Receipt of the confirmation data may cause information to be displayed 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 representative of the first portion of the document and a third document obfuscation value representative of 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 document obfuscation values for 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 1000 may include sending the document obfuscation value and third request data indicating a third request to generate a second block in a second blockchain associated with the underwriter system. Process 1000 may also include receiving a second encrypted document obfuscation value representing a second block in a second blockchain from the underwriter system. In an example in which 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 trade 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 properties associated with the document. Properties may include at least one of the following: a title, a trade secret type, and/or an identifier of at least one of a person or entity associated with the document. Process 1000 may also include storing tag data in a database associated with the registration system. Tag data can be associated with document obfuscation values and/or trade secrets. Process 1000 may also include receiving input data at the registration system requesting a search for trade secrets associated with the trade secret registry. In these examples, the input data may include search terms. Process 1000 may also include causing tag data to be searched for a search term based at least in part on receiving the input data.

Figure 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 limiting, and any number of the described operations may 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 trade secret. For example, the user interface may include a selectable portion that, when selected, may identify a document representing a trade secret. For example, the selectable portion and/or another portion of the user interface may include text requesting a user of the user interface to select the selectable portion to identify documents to be registered as trade secrets 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. Input can include selecting a naming indicator for the document.

At block 1104, process 1100 may include receiving input indicating that the document is to be registered in a trade secret registry associated with the 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 selected by the user to indicate that the document is to be registered with the Trade Secrets Registry.

At block 1106, process 1100 may include generating a document obfuscation value representative of 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 device and/or remote storage devices accessible to the electronic device. The obfuscation component can then generate a document obfuscation value corresponding to the document. Generally, an obfuscation component may receive text data, image data, formatted data, and/or other data corresponding to a document as input, and may generate a document obfuscation value corresponding to the input as output. In an example, the electronic device may include multiple obfuscation components, each obfuscation component employing a different hashing algorithm. In these examples, each obfuscation component can output different document obfuscation values for the same document.

At block 1108 , process 1100 may include sending the document obfuscation value and request data indicating a request to register the trade secret in association with a trade secret registry to the registration system. For example, the communication component of the electronic device may format and/or send the document obfuscation value to the registration system. Additionally, the communications 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 the trade secret registry; and the trade secret has been associated with an encrypted document obfuscation value, the encrypted document Obfuscated values represent blocks in the 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 the communication component of the electronic device may be configured to generate an indication of a block associated with a blockchain, such as a distributed ledger system. Chain) Request data associated with a request to register a trade secret. The request data may be sent to the distributed ledger system along with, for example, a document obfuscation value, and/or an identifier of the document and/or trade secret, and/or other information associated with the document and/or trade secret.

The distributed ledger 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 block of the blockchain. The distributed ledger system may generate a cryptographic document obfuscation value that represents a block in the blockchain and/or the distributed ledger system may generate a time and/or date indicating the registration of the document obfuscation value (or other data) with the blockchain. time value. The distributed ledger system may send encrypted document obfuscation values, time values, and/or other information (such as, for example, block numbers) to registration systems and/or electronic devices. The registration system and/or electronic device may receive the encrypted document obfuscation value from the distributed ledger system.

The registration system can then generate records in the Trade Secrets Registry. For example, the registration system's record generator can then generate records in a trade secrets registry. For example, a record may include an identifier for the record, a naming indicator for the trade secret, a description of the trade secret, a naming indicator for the document, one or more tags, a status identifier for the record, a document obfuscation value, an encrypted document obfuscation value, a zone Block number, time value (also described as block timestamp), insurance policy details, valuation details, and/or other information associated with trade secrets. Records may be stored in the Trade Secrets Registry along with one or more other records.

Additionally or alternatively, process 1100 may include identifying first and second portions of the document and generating a second document obfuscation value representative of the first portion of the document and a third document obfuscation value representative of 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 document obfuscation values for 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 may include receiving confirmation data indicating that the trade secret has been associated with a second encrypted document obfuscation value representing a second blockchain associated with the underwriter's system. of the second block.

Additionally or alternatively, process 1100 may include generating a second document obfuscation value representative of 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 that is different from the first hash value generator. Process 1100 may also include sending the second document obfuscation value to the registration system. In these examples, the confirmation data may indicate that the trade secret has been associated with a second encrypted document obfuscation value associated with the second document obfuscation value, and that the second encrypted document obfuscation value represents a second block associated with the third system The second block in the chain.

Additionally or alternatively, process 1100 may include receiving a second input indicating at least one of: a title associated with the document, a trade secret type associated with the document, and/or a trade secret type associated with the document. Identification information of at least one of the individuals or entities. Process 1100 may also include generating tag data based at least in part on the second input and sending 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 registration 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 the document, wherein each of the fields may be associated with a field type. 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 field types and/or field values of respective ones of the fields.

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

Figure 12 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 limiting, and any number of the described operations may be combined in any order and/or in parallel to implement process 1200.

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

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

At block 1206 , process 1200 may include sending to the remote system the document obfuscation value and request data indicating a request to generate a block in a blockchain associated with the remote system. For example, the 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, process 1200 may include receiving from a remote system a cryptographic document obfuscation value representing a block in the blockchain. For example, based at least in part on receiving the document obfuscation value and/or the request data, the system and/or the communication component of the electronic device may be configured to generate an indication associated with a blockchain, such as a blockchain associated with a remote system Request data for requests to register trade secrets. The request data may be sent to the remote system along with, for example, a document obfuscation value, and/or an identifier of the document and/or trade secret, and/or other information associated with the document and/or 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 block of the blockchain. The remote system may generate a cryptographic document obfuscation value representing a block in the blockchain and/or the remote system may generate a time value indicating the time and/or date when 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 (eg, block number) to the system and/or electronic device. The system and/or electronic device may receive the encrypted document obfuscation value from the remote system.

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

Additionally or alternatively, process 1200 may include receiving a second document obfuscation value representing the document from the electronic device, and sending the second document obfuscation value and second request data to the distributed ledger system, the second request data indicating that the A second request to generate a second block in a second blockchain associated with the distributed ledger system. Process 1200 may also include receiving a second cryptographic document obfuscation value representing a second block in a second blockchain from the distributed ledger system. In these examples, the record may associate the second encrypted document obfuscation value with the trade secret.

Additionally or alternatively, 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. Process 1200 may also include associating the identifier with the first record and determining that a second record associated with the trade secret registry is associated with the identifier. 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, process 1200 may include sending the document obfuscation value and second request data to the distributed ledger system, the second request data indicating generation in a second blockchain associated with the distributed ledger system Second request for second block. Process 1200 may also include receiving a second cryptographic document obfuscation value representing a second block in a second blockchain from the distributed ledger system. In these examples, the record may associate the second encrypted document obfuscation value with the trade secret.

Additionally or alternatively, process 1200 may include receiving second input data indicating at least one of: a title associated with the document, a trade secret type associated with the document, or a trade secret type associated with the document. An identifier for at least one of the person or entity. Process 1200 may also include generating tag data based at least in part on the second input data. Process 1200 may also include receiving third input data requesting a search for trade secrets associated with the trade secret registry, wherein the third input data may include search terms. Process 1200 may also include causing the tag data to be searched 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 the document, wherein each of the fields may be associated with a field type. 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 field types and/or field values of respective ones of the fields.

Figure 13 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 limiting, and any number of the described operations may 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 the trade secret from the electronic device. For example, the user interface may include a selectable portion that, when selected, may identify a document representing a trade secret. For example, the selectable portion and/or another portion of the user interface may include text requesting a user of the user interface to select the selectable portion to identify documents to be registered as trade secrets 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. Input can include selecting a naming indicator for the document.

At block 1304, process 1300 may include receiving input data indicating that the document is to be registered in the 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 selected by the user to indicate that the document is to be registered with the Trade Secrets Registry.

At block 1306, process 1300 may include generating a document obfuscation value representative of the document based at least in part on receiving the input data. For example, obfuscation components of the electronic device and/or system associated with the trade secret registry may, such as from one or more databases, and/or other storage locations associated with the electronic device and/or system, and/or the electronic device and/or a remote storage device accessible to the system receives data corresponding to the document. The obfuscation component can then generate a document obfuscation value corresponding to the document. Generally, an obfuscation component may receive text data, image data, formatted data, and/or other data corresponding to a document as input, and may generate a document obfuscation value corresponding to the input as output. In an example, the electronic device may include multiple obfuscation components, each obfuscation component employing a different hashing algorithm. In these examples, each obfuscation component can output different document obfuscation values 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 for security or other reasons so that it is not stored or otherwise available to anyone accessing the system other than the electronic device from which it was received. .

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

At block 1312, process 1300 may include receiving from a remote system a cryptographic document obfuscation value representing a block in the blockchain. For example, based at least in part on receiving the document obfuscation value and/or the request data, the system and/or the communication component of the electronic device may be configured to generate an indication associated with a blockchain, such as a blockchain associated with a remote system Request data for requests to register trade secrets. The request data may be sent to the remote system along with, for example, a document obfuscation value, and/or an identifier of the document and/or trade secret, and/or other information associated with the document and/or 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 block of the blockchain. The remote system may generate a cryptographic document obfuscation value representing a block in the blockchain and/or the remote system may generate a time value indicating the time and/or date when 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 (eg, block number) to the system and/or electronic device. The system and/or electronic device may receive the encrypted document obfuscation value from the remote system.

At block 1314, process 1300 may include generating a record in the trade secret registry that: indicates that the trade secret has been registered in the trade secret registry; includes the encrypted document obfuscation value; and indicates the generation or recording of the encrypted document obfuscation value. generates at least one associated time value. For example, the system's record generator can then generate records in a trade secret registry. For example, a record may include an identifier for the record, a naming indicator for the trade secret, a description of the trade secret, a naming indicator for the document, one or more tags, a status identifier for the record, a document obfuscation value, an encrypted document obfuscation value, a zone Block number, time value (also described as block timestamp), insurance policy details, valuation details, and/or other information associated with trade secrets. Records may be stored in the Trade Secrets Registry along 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, using a second hash value generator that is different from the first hash value generator. Document obfuscation values. 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 generating a second zone in a second blockchain associated with the distributed ledger system. The second request of the block. Process 1300 may also include receiving a second cryptographic document obfuscation value representing a second block in a second blockchain from the distributed ledger system. In these examples, the record may associate the second encrypted document obfuscation value with the trade secret.

Additionally or alternatively, 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 the identifier with the first record and determining that a second record associated with the trade secret registry is associated with the identifier. 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 first and second portions of the document and generating a second document obfuscation value representative of the first portion of the document and a third document obfuscation value representative of 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 document obfuscation values for 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 1300 may include sending the document obfuscation value and second request data to the distributed ledger system, the second request data indicating generation in a second blockchain associated with the distributed ledger system Second request for second block. Process 1300 may also include receiving a second cryptographic document obfuscation value representing a second block in a second blockchain from the distributed ledger system. In these examples, the record may associate the second encrypted document obfuscation value with the trade secret.

Additionally or alternatively, process 1300 may include receiving second input data indicating at least one of: a title associated with the document, a trade secret type associated with the document, or a trade secret type associated with the document. An identifier for at least one of the person or entity. 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 trade secrets associated with the trade secret registry, wherein the third input data may include search terms. Process 1300 may also include causing the tag data to be searched 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 the document, wherein each of the fields may be associated with a field type. 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 field types and/or field values of respective ones of the fields.

Additionally or alternatively, process 1300 may include storing security rules associated with the firewall. In these examples, receiving data representing the document may be based, at least in part, on security rules that allow 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 security rules that permit transmission of the document obfuscation value and the request data to the remote system. Additionally, sending the confirmation data may be based at least in part on security rules that allow transmission of the confirmation data to the electronic device.

14 illustrates 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 limiting, and any number of the described operations may 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 from an electronic device representing a document corresponding to the trade secret. For example, an obfuscation component of the electronic device may receive data corresponding to the document, such as from one or more databases and/or other storage locations associated with the electronic device and/or remote storage devices accessible to the electronic device. The obfuscation component can then generate a document obfuscation value corresponding to the document. Generally, an obfuscation component may receive text data, image data, formatted data, and/or other data corresponding to a document as input, and may generate a document obfuscation value corresponding to the input as output. In an example, the electronic device may include multiple obfuscation components, each obfuscation component employing a different hashing algorithm. In these examples, each obfuscation component can output different document obfuscation values 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, the communication component of the electronic device may format and/or send input data to the system.

At block 1406, process 1400 may include analyzing the document obfuscation value relative to a stored document obfuscation value that is stored in association with the trade secret registry. For example, the comparison component may be configured to analyze the document confusion value and determine the degree of similarity and/or 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 trade secret. Similar documents may have similar document obfuscation values. Therefore, the comparison component can analyze the document obfuscation values to determine the similarity between them. A threshold similarity can be identified and/or determined and the similarity between document obfuscation values can be compared to the threshold similarity. Document obfuscation values whose similarity reaches or exceeds a threshold similarity can be determined to be similar, while pairs of hash values below the threshold similarity can be determined to be dissimilar. Additionally, the document obfuscation values can be segmented and the segments can be compared to determine portions of the document obfuscation values that are similar and portions that are dissimilar. The number of similar and dissimilar document confusion values can be used to determine the overall similarity between document confusion values.

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

In other examples, Levenstein distance can be used to determine the similarity between trade secrets. The confusion value of two documents and/or the Levenstein distance between the documents can be determined. A shorter Levenstein distance can indicate more similarities than a longer Levenstein distance. As used herein, Levenstein distance (also known as edit distance) can be described as a string metric used to measure the difference between two sequences. For example, the Levenstein distance between two words can be thought of as the minimum number of single-character edits required to change one word into the other. Therefore, the Levenstein distance between two very similar words will be shorter than the Levenstein distance between two very different words. In these examples, a Levenstein distance can be determined between two documents and/or two document confusion values representing those documents, with a shorter Levenstein distance indicating more similarity between the documents.

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

At block 1408 , 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 the comparison component as described with respect to block 1406 .

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

At block 1412 , process 1400 may include generating a record in the trade 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 the trade secret has been registered in the trade secret registry; and associating encrypted document obfuscation values with trade secrets. For example, the system's record generator can then generate records in a trade secret registry. For example, a record may include an identifier for the record, a naming indicator for the trade secret, a description of the trade secret, a naming indicator for the document, one or more tags, a status identifier for the record, a document obfuscation value, an encrypted document obfuscation value, a zone Block number, time value (also described as block timestamp), insurance policy details, valuation details, and/or other information associated with trade secrets. Records may be stored in the Trade Secrets Registry along with one or more other records.

Additionally or alternatively, process 1400 may include determining, at least in part, that the similarity between the document obfuscation value and the stored document obfuscation value is greater than a threshold similarity and/or determining that the entity identifier associated with the document obfuscation value is identical to the stored document obfuscation value. The stored document obfuscation values are associated to associate the trade secret with at least one trade secret associated with at least one of the stored document obfuscation values.

Additionally or alternatively, process 1400 may include generating confirmation data indicating 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 of. Process 1400 may also include sending the confirmation data to the electronic device, such as for display via a user interface.

15 illustrates a flow diagram of an exemplary process associated with a user interface 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 limiting, and any number of the described operations may be combined in any order and/or in parallel to implement process 1500.

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

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

At block 1506 , process 1500 may include causing a display request to identify a second selectable portion of the document to be registered as a trade secret based at least in part on receiving the first input. 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, process 1500 may include receiving a second input identifying the document using a second selectable portion of the user interface. For example, identification of a document may include input such as a naming indicator of the document and/or selecting the document from a database of the electronic device displaying the user interface. The document can be identified and the electronic device can cause a document obfuscation value corresponding to the document to be generated. 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 device and/or remote storage devices accessible to the electronic device. The obfuscation component can then generate a document obfuscation value corresponding to the document. Generally, an obfuscation component may receive text data, image data, formatted data, and/or other data corresponding to a document as input, and may generate a document obfuscation value corresponding to the input as output. In an example, the electronic device may include multiple obfuscation components, each obfuscation component employing a different hashing algorithm. In these examples, each obfuscation component can output different document obfuscation values for the same document.

At block 1510 , process 1500 may include causing, based at least in part on the second input, to display a record associated with the trade secret registry, the record indicating that the document obfuscation value generated based at least in part on the document has been associated with the trade secret registry. the encrypted document obfuscation value associated with the block of the blockchain has been registered in association with the trade 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 . Records may include record identifiers, trade secret details, and/or transaction details. The record identifier may include numbers and/or letters that identify the record relative to the trade secret registry. For example, trade secret details may include a naming indicator of the trade secret, a description of the trade secret, a naming indicator of a document representing the trade secret, and/or a tag generated as described elsewhere herein. Transaction details may include status of registration with the trade secret registry, document obfuscation value, block number associated with the block in which the trade secret was registered to the blockchain, cryptographic document obfuscation value (also described as block document obfuscation value) and/or block timestamp. Other information that may be included in the record and displayed with respect to the user interface may include insurance policy details, valuation details, and/or other information associated with trade secrets, as described more fully elsewhere herein.

Records may be generated by a record generator of a remote system associated with the trade secret registry. Records may be stored in the Trade Secrets Registry along 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 send the confirmation data to the electronic device for display via the user interface.

Additionally or alternatively, process 1500 may include causing display of a third selectable portion indicating a second option to obtain an insurance policy associated with the trade secret and receiving a third input via the user interface indicating selection of the third selectable portion. . Process 1500 may also include causing one or more requests to be displayed for information associated with at least one of an insurance policy or a trade secret based at least in part on receiving a third input. Additionally, 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. Process 1500 may also include receiving text input to each of the one or more input fields via the user interface and receiving an indication from a distributed ledger system associated with the insurer that the insurance policy has been issued. 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 input fields associated with the document to be displayed via a user interface. In these examples, the input fields may include at least one of a document name field, a document description field, and/or a label field. Process 1500 may further include causing a third selectable portion to be displayed via the user interface, the third selectable portion indicating a second option to automatically populate at least one of the input fields. Process 1500 may also include receiving, via the user interface, a third input indicating selection of a third selectable portion and causing text to be displayed 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 a third selectable option to be displayed via the user interface, the 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 trade 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 display, via the user interface, of the value determined by the remote system based at least in part on the information document. In these examples, the record may indicate a second encrypted document obfuscation value associated with a second block of the blockchain to which the informational document has been enrolled.

16 illustrates a flowchart of another exemplary process associated with a user interface 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 limiting, and any number of the described operations may be combined in any order and/or in parallel to implement process 1600.

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

At block 1604, process 1600 may include receiving first input data indicating selection of a first selectable portion. Input may be received via touch input on the screen of the electronic device and/or through tactile and/or auditory 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 a trade 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, process 1600 may include receiving second input data identifying the document. For example, identification of a document may include input such as a naming indicator of the document and/or selecting the document from a database of the electronic device displaying the user interface. The document can be identified and the electronic device can cause a document obfuscation value corresponding to the document to be generated. 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 device and/or remote storage devices accessible to the electronic device. The obfuscation component can then generate a document obfuscation value corresponding to the document. Generally, an obfuscation component may receive text data, image data, formatted data, and/or other data corresponding to a document as input, and may generate a document obfuscation value corresponding to the input as output. In an example, the electronic device may include multiple obfuscation components, each obfuscation component employing a different hashing algorithm. In these examples, each obfuscation component can output different document obfuscation values for the same document.

At block 1610, process 1600 may include causing display of the encrypted document obfuscation value associated with the block of the blockchain in which the identifier of the document has been registered. The encrypted document obfuscation value may be part of the record, which may also include record identifiers, trade secret details, and/or transaction details. The record identifier may include numbers and/or letters that identify the record relative to the trade secret registry. For example, trade secret details may include a naming indicator of the trade secret, a description of the trade secret, a naming indicator of a document representing the trade secret, and/or a tag generated as described elsewhere herein. Transaction details may include status of registration with the trade secret registry, document obfuscation value, block number associated with the block in which the trade secret was registered to the blockchain, cryptographic document obfuscation value (also described as block document obfuscation value) and/or block timestamp. Other information that may be included in the record and displayed with respect to the user interface may include insurance policy details, valuation details, and/or other information associated with trade secrets, as described more fully elsewhere herein.

Additionally or alternatively, process 1600 may include causing display of a third selectable portion indicating a second option to obtain an insurance policy associated with the trade secret and receiving a third input via the user interface indicating selection of the third selectable portion. . Process 1600 may also include causing one or more requests to display information associated with at least one of an insurance policy or a trade secret based at least in part on receiving a third input. Additionally, 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. Process 1600 may also include receiving text input to each of the one or more input fields via the user interface and receiving an indication from a distributed ledger system associated with the insurer that the insurance policy has been issued. Process 1600 may also include causing display of insurance policy information associated with the insurance policy via the user interface.

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

Additionally or alternatively, process 1600 may include receiving input data representing user input to manipulate text from the input field. Process 1600 may also include causing the manipulated text to be displayed relative to the input field based at least in part on the fourth input data. 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. Process 1600 may also include receiving input data via a user interface indicating selection of a 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 a third selectable option to be displayed via the user interface, the 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 trade 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 display, via the user interface, of a value determined by the remote system based at least in part on the information document. In these examples, the record may indicate a second encrypted document obfuscation value associated with a second block of the blockchain to which the informational document has been enrolled.

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 trade secret type associated with the document based at least in part on the characteristic. Process 1600 may also include causing text indicating the type of trade secret to be displayed via the user interface.

Additionally or alternatively, process 1600 may include causing display, via the user interface, of a trade secret repository screen that includes a first identifier of the first document associated with the entity identifier, the a second identifier of the associated second document, and/or a search field configured to receive input to search for records in the trade secret registry associated with the entity identifier. 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 a third selectable portion to be displayed via the user interface, the 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 selection of a third selectable portion and causing the display request to identify a fourth selectable portion of the second document. Process 1600 may also include receiving fourth input data identifying a second document and causing display, via the user interface, that a first document obfuscation value associated with the first document is at least threshold similar to a second document obfuscation value associated with the second document. degree indication.

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

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

Additionally or alternatively, process 1600 may include causing display, via the user interface, of insurance policy information associated with an insurance policy issued for the trade secret. In these examples, the insurance policy information may include a payment value associated with an amount to be paid to the entity associated with the trade secret upon the occurrence of the event. Process 1600 may also include receiving compliance data indicating that the entity has failed to comply with a condition of the insurance policy and causing updated insurance policy information including an updated payment value to be displayed via the user interface, the updated payment value being less than the payment value.

Additionally or alternatively, process 1600 may include causing a second selectable portion to be displayed via the user interface, the 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 selection of a second selectable portion and causing the display request to identify a third selectable portion of the second document. Process 1600 may also include receiving third input data identifying a second document and causing display, via the user interface, that a first document obfuscation value associated with the first document is at least threshold similar to a second document obfuscation value associated with the second document. degree indication.

Figure 17 shows a flowchart of an exemplary process for digital asset management including document versioning. The order in which operations or steps are described is not intended to be construed as limiting, and any number of the described operations may be combined in any order and/or in parallel to implement process 1700.

At block 1702 , process 1700 may include storing a first record in association with a trade secret registry, the first record indicating: a first document obfuscation value corresponding to a first document representing the trade secret; and based at least in part on An encrypted document obfuscation value generated by the first document obfuscation value that represents a block in the remote system's blockchain. 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 document obfuscation values generated based at least in part on documents representing trade secrets. The document obfuscation value may be generated by the user's electronic device and/or by a system associated with the trade secret registry. Additionally, the electronic device and/or system may request that the trade secret and/or document obfuscation value be registered in association with the remote system's blockchain. A remote system can register such trade secrets and can generate cryptographic document obfuscations representing blocks of the blockchain.

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

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

At block 1708, process 1700 may include receiving a second document obfuscation value corresponding to the second document from the electronic device. For example, the communication component may 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 device and/or remote storage devices accessible to the electronic device. The obfuscation component can then generate a document obfuscation value corresponding to the document. Generally, an obfuscation component may receive text data, image data, formatted data, and/or other data corresponding to a document as input, and may generate a document obfuscation value corresponding to the input as output. In an example, the electronic device may include multiple obfuscation components, each obfuscation component employing a different hashing algorithm. In these examples, each obfuscation component can output different document obfuscation values for the same document.

At block 1710 , 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 obfuscation value and the second document obfuscation value. For example, the version control component may be configured to determine that two or more documents and/or trade secrets are versions of the same document and/or trade secret. For example, as described more fully above with respect to FIG. 1, 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 trade secret type. Using some or all of this information, the version control component can determine that the two documents are versions of the same document. This versioning indication may be stored relative to the record associated with the document and/or a visual indication may be displayed via the user interface.

At block 1712, process 1700 may include generating a second record that: indicates that an identifier of the second document has been registered in association with the trade secret registry; indicates 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. Records may include record identifiers, trade secret details, and/or transaction details. The record identifier may include numbers and/or letters that identify the record relative to the trade secret registry. For example, trade secret details may include a naming indicator of the trade secret, a description of the trade secret, a naming indicator of a document representing the trade secret, and/or a tag generated as described elsewhere herein. Transaction details may include status of registration with the trade secret registry, document obfuscation value, block number associated with the block in which the trade secret was registered to the blockchain, cryptographic document obfuscation value (also described as block document obfuscation value) and/or block timestamp. Other information that may be included in the record and displayed with respect to the user interface may include insurance policy details, valuation details, and/or other information associated with trade secrets, as described more fully elsewhere herein.

Additionally or alternatively, process 1700 may include storing first access control data indicating a first identifier of a first person permitted to access the first record. Process 1700 may also include storing second access control data indicating a second identifier of a second person who is permitted to access the second record. In these examples, the second access control data may indicate that the second person is not allowed to access the first record. 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. Process 1700 may also include causing display of a second record including a selectable link based at least in part on the second input data. Process 1700 may also include receiving third input data corresponding to selection of the selectable link and avoiding causing the first record to be displayed based at least in part on second access control data indicating that access to the first record is not permitted.

Additionally or alternatively, process 1700 may include associating the trade secret with the insurance policy using a smart contract associated with the blockchain, where the smart contract indicates conditions for substantiating the insurance policy. Process 1700 may also include receiving verification data from the electronic device indicating that the condition has been met and sending the verification data to a remote system associated with the insurer, wherein the verification data causes the smart contract to certify the insurance policy. Process 1700 may also include receiving confirmation data from the remote system indicating that the insurance policy has been certified using the smart contract.

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

Additionally or alternatively, process 1700 may include associating a first feature vector with the first document based at least in part on first text data associated with the first document. 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. 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, 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, process 1700 may include receiving an indication of a trade secret type associated with the trade secret and identifying a frequency with which versions of the trade secret associated with the trade secret type are registered with a trade secret registry. Process 1700 may also include generating a version registration alert based at least in part on the frequency and sending alert data representative of the version registration alert to the electronic device.

Additionally or alternatively, process 1700 may include utilizing at least one of the electronic device or an entity identifier corresponding to an entity associated with the electronic device to determine how frequently a version of the trade secret is registered in a trade secret registry. Process 1700 may also include generating a version registration alert based at least in part on the frequency and sending alert data representative of the version registration alert to the electronic device.

Figure 18 illustrates 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 limiting, and any number of the described operations may 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 a trade secret registry indicating: a first document obfuscation value corresponding to a document representing the trade secret; and generating a document based at least in part on the first document obfuscation value. A first encrypted document obfuscation value representing the first block in the remote system's blockchain. 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 document obfuscation values generated based at least in part on documents representing trade secrets. The document obfuscation value may be generated by the user's electronic device and/or by a system associated with the trade secret registry. Additionally, the electronic device and/or system may request that the trade secret and/or document obfuscation value be registered in association with the remote system's blockchain. A remote system can register such trade secrets and can generate cryptographic document obfuscations representing blocks of the blockchain.

At block 1804, process 1800 may include receiving valuation data from the electronic device indicated as related to the value of the trade secret. For example, the user interface of the electronic device may include a selectable portion indicating options for determining the value of the trade secret. Based at least in part on 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 may be configured to identify and/or determine the value associated with a given trade secret. Information requested by the input fields may include, for example, the type of trade secret, the importance of the trade secret to the entity, the entity's revenue, the entity's value, the date the trade secret was created, etc.

Additionally, in an example, the input field may include a request for supporting documentation that includes information that may be relevant to the valuation of the trade secret. In these examples, users can identify supporting documentation. A document obfuscation value may be generated for a given supporting document and/or the supporting document and/or the document obfuscation value may be registered in association with the blockchain. The record of the trade secret may include information associated with the supporting document, such as a corresponding document obfuscation value and/or a cryptographic document obfuscation value corresponding to the block in the blockchain in which the supporting 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 trade secret. For example, tag data can be used to determine the type of trade secret. Trade secrets of the same or similar type may be analyzed to determine the value of the trade secret in question.

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

At block 1808, 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 the second document obfuscation value, the second encrypted document obfuscation value representing the blockchain second block in . In these examples, the record may include a second document obfuscation value and a second encrypted document obfuscation value. By doing so, valuation data can be registered to the blockchain, which can provide support for the determination of valuation 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 registration of the second document in association with the trade secret registry. Process 1800 may also include receiving a third document obfuscation value corresponding to the second document from the electronic device and determining, based at least in part on a comparison of the first document obfuscation value and the third document obfuscation value, that the second document corresponds to a third document obfuscation value of the first document. Second version. Process 1800 may also include generating a second record indicating that the 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, process 1800 may include storing first access control data indicating a first identifier of a first person permitted 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 who is permitted to access the second portion of the record. In these examples, the second access control data may indicate that the second person is not allowed to access the first portion. Process 1800 may also include receiving second input data requesting access to the second portion, wherein the second input data indicates that the second person is requesting access to the second record. Process 1800 may also include causing the second portion to be displayed based at least in part on the second input data. Process 1800 may also include receiving third input data from a second person requesting access to the first portion of the record and avoiding causing the first portion to be displayed based at least in part on second access control data indicating that access to the first portion is not permitted.

Additionally or alternatively, process 1800 may include associating the trade secret with the insurance policy using a smart contract associated with the blockchain, where the smart contract indicates conditions for substantiating the insurance policy. Process 1800 may also include receiving verification data from the electronic device indicating that the condition has been met and sending the verification data to a remote system associated with the insurer, wherein the verification data causes the smart contract to certify the insurance policy. Process 1800 may also include receiving confirmation data from the remote system indicating that the insurance policy has been certified using the smart contract.

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

At block 1902, process 1900 may include storing first access control data indicating a first identifier of a first person permitted to access a record associated with the trade secret registry, the record indicating Trade secrets registered in association with the Trade Secrets Registry; and functions of the Trade Secrets Registry authorized to the first person. For example, first access control data may be stored in association with the remote system. 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 a record may be required to authenticate the user's identity, such as by entering a username and/or password. For example, functionality may include the ability to view information, manipulate information, change access controls, etc.

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

At block 1906, process 1900 may include receiving first input data requesting access to the record, the first input data indicating that the 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 enter authentication information to gain access to information associated with the trade secret registry.

At block 1908, process 1900 may include causing the record to be displayed based at least in part on the first input data. For example, assuming 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 functionality. For example, the second person may provide input to the 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, process 1900 may include avoiding causing performance of the function based at least in part on second access control data indicating that the second person is not authorized to use the function. For example, assuming the second access control data indicates that the second person is not authorized to utilize the functionality, upon receipt of input data requesting use of the functionality, the system may determine, based at least in part on the second access control data, that such request cannot be performed .

Additionally or alternatively, process 1900 may 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 the second trade secret in association with a trade secret registry. Process 1900 may also include receiving a document obfuscation value corresponding to a second trade secret from the electronic device and determining, based at least in part on a comparison of the document obfuscation values, that the second trade secret corresponds to a second version of the first trade secret. Process 1900 may also include generating a second record indicating that the identifier of the second trade secret has been registered in association with the trade secret registry and indicating that the second trade secret corresponds to a second version of the first trade secret.

Additionally or alternatively, process 1900 may include receiving valuation data from the electronic device indicated as related to the value of the trade secret. Process 1900 may also include receiving a document obfuscation value corresponding to the valuation data from an 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 a remote system. In these examples, cryptographic document obfuscation values can represent blocks in the blockchain. Additionally, records may include document obfuscation values and encrypted document obfuscation values.

Additionally or alternatively, process 1900 may include associating the trade secret with the insurance policy using a smart contract associated with the blockchain, where the smart contract indicates conditions for substantiating the insurance policy. Process 1900 may also include receiving confirmation data from the electronic device indicating that the condition has been met and sending the confirmation data to the remote system. Verification data enables smart contracts to certify insurance policies. Process 1900 may also include receiving confirmation data from the remote system indicating that the insurance policy has been certified using the smart contract.

Additionally or alternatively, process 1900 may include generating a log of recorded accesses by one or more electronic devices. The log may indicate an identifier of each of the persons who accessed the record and/or a time value at which each of the persons accessed the record. Process 1900 may also include receiving an indication that 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 times when the first person accessed the record. Alert data can also request confirmation that the first person has undergone an exit interview associated with the trade secret.

Additionally or alternatively, process 1900 may include generating a log of recorded accesses by one or more electronic devices. The log may indicate an identifier of each of the persons who accessed the record and/or a time value at which each of the persons accessed the record. Process 1900 may also include generating a compliance schedule associated with an insurance policy involving the trade secret based at least in part on the logs. The compliance schedule may indicate the time period during which the first person can enforce compliance with the conditions of the insurance policy. Process 1900 may also include determining that a condition has not been 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 has not been satisfied.

Additionally or alternatively, process 1900 may 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 filing system associated with the intellectual property asset. Process 1900 may also include sending access information for the interface to a remote filing system and receiving a request from the remote filing system to perform a search of the trade secret registry. The request may include text data for searching the trade secret registry. Process 1900 may also include identifying search results and sending result data representative of the results to a remote archiving system.

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

Figure 20 illustrates a flowchart of an exemplary process for valuing property 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 limiting, and any number of the described operations may be combined in any order and/or in parallel to implement process 2000.

At block 2002, process 2000 may include storing a record in association with a trade secret registry indicating: a document obfuscation value corresponding to a document representing the trade secret; and an encrypted document obfuscation generated based at least in part on the document obfuscation value The cryptographic document obfuscation value represents a block in the remote system's blockchain. 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 document obfuscation values generated based at least in part on documents representing trade secrets. The document obfuscation value may be generated by the user's electronic device and/or by a system associated with the trade secret registry. Additionally, the electronic device and/or system may request that the trade secret and/or document obfuscation value be registered in association with the remote system's blockchain. A remote system can register such trade secrets and can generate cryptographic document obfuscations representing blocks of the blockchain.

At block 2004, process 2000 may include identifying tag data indicative of properties associated with the document. For example, a 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 the user interface. Input fields can include requests to "tag" documents or otherwise provide keywords. For example, a document corresponding to source code for operating a sewing machine may be associated with keywords such as "source code," "sewing," "sewing machine," "version 1.1.20," and so on. A user of the electronic device may input text corresponding to these tags, and a tag data generator may utilize such input to generate tag data. Additionally or alternatively, the label data generator may automatically generate label 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, a tag data generator may identify one or more fields of a document and/or values associated with those fields. As an illustration, the tag data generator can identify a title field, a document type field, one or more sections of a document, etc. Values associated with these fields, such as text data, can be used to generate labels. Additionally or alternatively, the document's text data can be analyzed to determine which words are commonly used in the document. These words can be identified as keywords and used to generate label data.

At block 2006, process 2000 may include receiving valuation data from the electronic device indicated as related to the value of the trade secret. For example, the user interface of the electronic device may include a selectable portion indicating options for determining the value of the trade secret. Based at least in part on 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 may be configured to identify and/or determine the value associated with a given trade secret. Information requested by the input fields may include, for example, the type of trade secret, the importance of the trade secret to the entity, the entity's revenue, the entity's value, the date the trade secret was created, etc.

Additionally, in an example, the input field may include a request for supporting documentation that includes information that may be relevant to the valuation of the trade secret. In these examples, users can identify supporting documentation. A document obfuscation value may be generated for a given supporting document and/or the supporting document and/or the document obfuscation value may be registered in association with the blockchain. The record of the trade secret may include information associated with the supporting document, such as a corresponding document obfuscation value and/or a cryptographic document obfuscation value corresponding to the block in the blockchain in which the supporting 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 trade secret. For example, tag data can be used to determine the type of trade secret. Trade secrets of the same or similar type may be analyzed to determine the value of the trade secret in question.

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

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

Additionally or alternatively, process 2000 may include receiving entity value data from at least one of an electronic device or another device, the entity value data indicating an entity value of the entity associated with the document or earnings and/or income of the entity At least one of the values. In these examples, determining the value of the trade 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 the registration of a block in the blockchain when determining the value of the trade secret. In these examples, the value may increase (continuously, periodically, on a predetermined schedule, or randomly) as the period of time between the time value and the current time increases.

Additionally or alternatively, process 2000 may include receiving from a 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 trade secret. The second encrypted document obfuscation value may represent a second block in the remote system's blockchain. 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.

21 illustrates a flowchart of an exemplary process for providing an insurance policy 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 limiting, and any number of the described operations may be combined in any order and/or in parallel to implement process 2100.

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

At block 2104, process 2100 may include identifying tag data indicative of properties associated with the document. For example, a 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 the user interface. Input fields can include requests to "tag" documents or otherwise provide keywords. For example, a document corresponding to source code for operating a sewing machine may be associated with keywords such as "source code," "sewing," "sewing machine," "version 1.1.20," and so on. A user of the electronic device may input text corresponding to these tags, and a tag data generator may utilize such input to generate tag data. Additionally or alternatively, the label data generator may automatically generate label 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, a tag data generator may identify one or more fields of a document and/or values associated with those fields. As an illustration, the tag data generator can identify a title field, a document type field, one or more sections of a document, etc. Values associated with these fields, such as text data, can be used to generate labels. Additionally or alternatively, the document's text data can be analyzed to determine which words are commonly used in the document. These words can be identified as keywords and used to generate label data.

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

At block 2108, process 2100 may include generating an insurance policy request indicating that: the trade secret has been registered with the Trade Secret Registry; the encrypted 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 insurance 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 the provision of the insurance policy. This information may include, for example, the trade secret type or category, the value of the trade secret (determined from above or identified by the user), policy term, entity value, date the trade secret was created, and/or enable upload of supporting documentation and/or requested section of the document. In the example of providing supporting documentation, the supporting documentation may be registered with the blockchain in the same or similar manner as described above with respect to supporting documentation for trade secret valuations.

At block 2110, process 2100 may include sending the insurance policy request to a distributed ledger system associated with the insurer. For example, the policy component and/or the communications component may be configured to receive input data corresponding to user input and may send the input data to a distributed ledger system associated with the insurer. Distributed ledger systems can process input data and, in one example, issue insurance policies that ensure trade secrets are not misappropriated.

At block 2112, process 2100 may include receiving an indication from the distributed ledger system that the 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 records associated with the trade secret and may be displayed via a user interface in an example. Some non-limiting examples of information associated with an insurance policy may include policy type, liability limits, retained value, policy premium, policy form, policy number, policy term, liability sublimits, and/or a valuation of trade secrets. Additionally or alternatively, the information may include a payment value associated with an amount to be paid to the entity associated with the trade secret upon the occurrence of the event. In these examples, the policy component may receive compliance data indicating that the entity has not complied with a condition of the insurance policy and may cause updated insurance policy information, including updated payment values, to be displayed. In these examples, the updated payout value may be less than the original payout value. When conditions are met, the payout value can be updated to reflect compliance with the policy conditions.

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

Additionally or alternatively, process 2100 may include generating a log of recorded accesses by one or more electronic devices. The log may indicate an identifier of each of the persons who accessed the record and/or a time value at which each of the persons accessed the record. Process 2100 may also include generating a compliance schedule associated with the insurance policy based at least in part on the logs. The compliance schedule may indicate a time period during which at least one of the persons described may enforce compliance with the conditions of the insurance policy. Process 2100 may also include determining that a condition has not been 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 has not been satisfied. Process 2100 may also include generating alert data indicating that the condition is not met and sending the alert data to one or more electronic devices based at least in part on determining that the condition is not met. In these examples, the alert data may cause a processor of 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 a 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 trade secret. The second encrypted document obfuscation value may represent a second block in the remote system's blockchain. In these examples, the insurance policy request may include the second encrypted document obfuscation value and/or an indication thereof.

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

22 illustrates a flowchart of an exemplary process for property verification according to a digital property authentication and management system. The order in which operations or steps are described is not intended to be construed as limiting, and any number of the described operations may 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 a trade secret registry indicating: a first document obfuscation value corresponding to a first document representing the trade secret; and based at least in part on the first document obfuscation Value generates a cryptographic document obfuscation value that represents a block in the remote system's blockchain. These records may include information such as document obfuscation values generated based at least in part on documents representing trade secrets. The document obfuscation value may be generated by the user's electronic device and/or by a system associated with the trade secret registry. Additionally, the electronic device and/or system may request that the trade secret and/or document obfuscation value be registered in association with the remote system's blockchain. A remote system can register such trade secrets and can generate cryptographic document obfuscations representing blocks of the blockchain.

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 accused 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 the trade secret registry. Input data can be received from an electronic device displaying a user interface.

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

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

In other examples, Levenstein distance can be used to determine the similarity between trade secrets. The confusion value of two documents and/or the Levenstein distance between the documents can be determined. A shorter Levenstein distance can indicate more similarities than a longer Levenstein distance. As used herein, Levenstein distance (also known as edit distance) can be described as a string metric used to measure the difference between two sequences. For example, the Levenstein distance between two words can be thought of as the minimum number of single-character edits required to change one word into the other. Therefore, the Levenstein distance between two very similar words will be shorter than the Levenstein distance between two very different words. In these examples, a Levenstein distance can be determined between two documents and/or two document confusion values representing those documents, with a shorter Levenstein distance indicating more similarity between the documents.

At block 2212, 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 obfuscation values whose similarity reaches or exceeds a threshold similarity can be determined to be similar, while pairs of hash values below the threshold similarity can be determined to be dissimilar. Additionally, the document obfuscation values can be segmented and the segments can be compared to determine portions of the document obfuscation values that are similar and portions that are dissimilar. The number of similar and dissimilar document confusion values can be used to determine the overall similarity between document confusion values. As another example, process 2200 may include determining that a Levenstein distance between a first characteristic of a first document and a second characteristic of a second document is less than a threshold Levenstein distance.

At block 2214, process 2200 may include determining that the second document corresponds to the first document based at least in part on a similarity greater than a threshold similarity. If the verification component determines that at least one of the registered document obfuscation values matches the document obfuscation value of the accused document, the verification component may determine that the accused document is the same as or similar to the registered document. In other examples, the verification component may determine the similarity between the accused document and one or more registered documents. In these examples, when the similarity reaches or exceeds the threshold similarity, it can be determined that the accused document is similar to the registered document. In other examples, the verification component may be configured to determine which portions of the accused document match or are similar to at least one registered document. An indication of matching or similar portions may be displayed, such as via a user interface. Additionally, where multiple versions of a document have been registered, the verification component may be configured to determine which of the multiple versions is most similar to the accused 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 the 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 the second encrypted document obfuscation value.

23 illustrates a flowchart of another exemplary process for property verification according to a digital property authentication and management system. The order in which operations or steps are described is not intended to be construed as limiting, and any number of the described operations may be combined in any order and/or in parallel to implement process 2300.

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

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

At block 2306, 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, the document obfuscation value may be generated for the accused document in the same or similar manner as described above with respect to the obfuscation component. The verification component may be used to analyze the document obfuscation value of the accused document relative to other document obfuscation values of the registered document.

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

In other examples, Levenstein distance can be used to determine the similarity between trade secrets. The confusion value of two documents and/or the Levenstein distance between the documents can be determined. A shorter Levenstein distance can indicate more similarities than a longer Levenstein distance. As used herein, Levenstein distance (also known as edit distance) can be described as a string metric used to measure the difference between two sequences. For example, the Levenstein distance between two words can be thought of as the minimum number of single-character edits required to change one word into the other. Therefore, the Levenstein distance between two very similar words will be shorter than the Levenstein distance between two very different words. In these examples, a Levenstein distance can be determined between two documents and/or two document confusion values representing those documents, with a shorter Levenstein distance indicating more similarity between the documents.

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

Additionally or alternatively, process 2300 may include sending a request to a remote system associated with the blockchain identifying a second encrypted document obfuscation value corresponding to the second document and/or a second hash corresponding to the second document. 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 the second encrypted document obfuscation value.

Additionally or alternatively, process 2300 may include storing a second record associated with the second version of the first document, wherein the second record may be based at least in part on the combination of the second record associated with the second version of the first document with The first record is associated. Process 2300 may also include determining a second degree of similarity between a third document obfuscation value and a second document obfuscation value corresponding to the second version of the first document. 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, process 2300 may include causing a series of dialog boxes to be displayed via a user interface of the electronic device. Causing the series of dialog boxes to be displayed 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 connection with an insurance policy for trade secrets. Process 2300 may also include receiving input data including a response to the text and sending at least one of the input data and/or the claim notification to a distributed ledger system associated with the insurer. Process 2300 may also include receiving status data from the distributed ledger system indicating that information is requested to process the claim. Process 2300 may also include sending an alert to the electronic device indicating that information is requested, wherein the alert includes a selectable portion. Process 2300 may also include causing the 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 first portion of the first document corresponding to the first portion of the first document obfuscation value. the third part. Process 2300 may also include causing display, via the user interface and based at least in part on identifying the third portion, 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 variations as to adapt particular operating requirements and circumstances will be apparent to those skilled in the art, this invention is not to be considered limited to the examples selected for the purpose of disclosure but is to cover all such modifications and variations that do not constitute a departure from this invention. all changes and modifications in spirit and scope.

Although this application describes embodiments having specific structural features and/or methodological acts, it is to be understood that the claims are not necessarily limited to the specific features or acts. Rather, the specific features and acts are indicative of some implementations falling within the scope of the claims.

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

1. A method comprising: receiving at an electronic device a document representing a trade secret; receiving at said electronic device an input instructing registration of a trade secret associated with a registration system remote from said electronic device registering the document; generating a document obfuscation value representing the document based at least in part on receiving the input; sending the document obfuscation value and a first request to generate a block in a blockchain from the electronic device , the blockchain being associated with a distributed ledger system at least remote from the electronic device; receiving at the electronic device from the distributed ledger system a block representing the block in the blockchain block value; sending from the electronic device and to the registration system a second request to register the document with respect to the trade secret registry; generating a record in the trade secret registry by the registration system, the record: indicating that the trade secret has been registered in the trade secret registry; including the block value; and indicating at least one of the generation of the block value or the generation of the record. a time value; generating confirmation data indicating that the record has been generated; and sending the confirmation data from the registration system to the electronic device.

2. The method of clause 1, wherein the document obfuscation value includes a first document obfuscation value, and the method further includes: identifying the first portion of the document and the second portion of the document; generating a representation of the a second document obfuscation value for the first portion of the document; generating a third document obfuscation value representative of the second portion of the document; and wherein generating the first document obfuscation value includes based at least in part on the second The document obfuscation value and the third document obfuscation value are used to generate the first document obfuscation value.

3. The method of clause 1 or 2, wherein the block includes a first block, the blockchain includes a first block chain, the block value includes a first block value, and the time The value includes a first time value, and the method further includes transmitting the document obfuscation value from the electronic device and to an underwriter system and generating a second time value in a second blockchain associated with the underwriter system. a third request for a block; receiving at the electronic device and from the underwriter system a second block value representing the second block in the second blockchain; from the electronic device and sending the second block value to the registration system; and wherein the record in the trade secret registry: associates the second block value with the trade secret; and indicates the association with the second block value. A second time value associated with the generation of the block value.

4. The method of clause 1, 2 or 3, further comprising: generating tag data indicative of a property associated with the document, the property comprising at least one of the following: title, trade secret type or association with the document. an identifier of at least one of the persons or entities associated with the document; storing the tag data in a database associated with the registration system, the tag data being associated with the trade secret; in the electronic receiving, at an apparatus, input data requesting a search for trade secrets associated with the trade secret registry, the input data including a search term; and causing the tag to be searched for the search term based at least in part on receiving the input data data.

5. The method of clause 1, 2, 3, or 4, wherein generating the document obfuscation value includes generating the document obfuscation value based at least in part on a cryptographic hash.

6. A system comprising: one or more processors; and non-transitory computer-readable media storing computer-executable instructions that, when executed by the one or more processors Causes the one or more processors to perform operations including: receiving a document representing a digital property; receiving input indicating that the document is to be registered in a digital property registry associated with a registration system; based at least in part on receiving the inputs to generate a document obfuscation value representing the document; sending the document obfuscation value and a request to register the digital property in association with the digital property registry to the registration system; and from the registration system Receive confirmation data indicating that: the digital property has been registered in association with the digital property registry; and the digital property has been associated with a block value, the block value representing a distributed classification Blocks in the blockchain associated with the ledger system.

7. The system of clause 6, wherein the document obfuscation value includes a first document obfuscation value, and the operations further include: identifying the first portion of the document and the second portion of the document; generating a representation of the a second document obfuscation value for the first portion of the document; generating a third document obfuscation value representative of the second portion of the document; and wherein generating the first document obfuscation value includes based at least in part on the second The document obfuscation value and the third document obfuscation value are used to generate the first document obfuscation value.

8. The system of clause 6 or 7, wherein the block includes a first block, the blockchain includes a first block chain, the block value includes a first block value, and the distribution The distributed ledger system includes a first distributed ledger system, and the confirmation data indicates that the digital property has been associated with a second block value, the second block value representing association with a second distributed ledger system The second block in the linked second blockchain.

9. The system of clause 6, 7 or 8, wherein the document obfuscation value includes a first document obfuscation value, the block includes a first block, and the blockchain includes a first blockchain, so The block value includes a first block value, the distributed ledger system includes a first distributed ledger system, and generating the first document obfuscation value includes generating the first document using a first hash value generator. obfuscated value, and the operations further include generating, based at least in part on receiving the input, a second document obfuscated value representative of the document, the second document obfuscated value generated using the first hash value generated by a second hash value generator that is different from the second hash value generator; sending the second document obfuscation value to the registration system; and wherein the confirmation data indicates that the digital property has been associated with the second document obfuscation value associated with a second block value representing a second block in a second blockchain associated with the second distributed ledger system.

10. The system of clause 6, 7, 8, or 9, wherein the input includes a first input, and the operations further include receiving a second input indicative of at least one of: a at least one of a title, a type of trade secret associated with the document, or identification of a person or entity associated with the document; generating tag 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 including a search term; causing the tag data to be searched based at least in part on the search term; and generating the data indicative of at least the tag data. Response data for the search results described above.

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

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 includes via the firewall and transmitting the document obfuscation value and the request based at least in part on the security rules that permit transmission of the document obfuscation value and the request to the registration system; and receiving the confirmation data includes via The firewall receives the confirmation data based at least in part on the security rules that permit receipt of the confirmation data from the registration system.

13. The system of clause 6, 7, 8, 9, 10, 11, or 12, wherein the document includes a first document, the document obfuscation value includes a first document obfuscation value, and the operations further include: 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 the first document obfuscation value Corresponding to the second document obfuscation 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 a document obfuscation value representing a document corresponding to a digital property from an electronic device; receiving input data indicating that the digital property is to be registered in a digital property registry; sending to a distributed ledger system the document obfuscation value and a request to generate a block in a blockchain associated with the distributed ledger system; receiving from the distributed ledger system a request representing the block in the blockchain a block value; and generating a record in the digital property registry that: indicates that the digital property has been registered in the digital property registry; and includes the block value.

15. The method of clause 14, wherein the document obfuscation value includes a first document obfuscation value, the block includes a first block, the blockchain includes a first block chain, and the block value including a first block value, the distributed ledger system including a first distributed ledger system, the request including a first request, and the method further comprising: receiving a third block value representing the document from the electronic device. two document obfuscation values; sending the second document obfuscation value to a second distributed ledger system and generating a second block of a second block in a second blockchain associated with the second distributed ledger system. Requesting; receiving a second block value representing the second block in the second blockchain from the second distributed ledger system; and wherein the record compares the second block value with The digital property is associated with it.

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

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

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

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, each of the fields being associated with a field type identifying a field value associated with the respective one of the fields; and generating tag data associated with the document, the tag data being based at least in part on all of the respective ones of the fields. generated based on the field type and the field value.

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

21. The system of clause 20, wherein the document obfuscation value includes a first document obfuscation value, the block includes a first block, the blockchain includes a first block chain, and the block value includes a first block value, the distributed ledger system includes a first distributed ledger system, the request includes a first request, and generating the first document obfuscation value includes generating the first hash value generator using a first hash value generator. the first document obfuscation value, and the operations further include generating, based at least in part on receiving the input data, a second document obfuscation value representative of the document, the second document obfuscation value being generated using a combination with the first document obfuscation value. a hash value generator generated by a second hash value generator different from each other; sending the second document obfuscation value and the second document obfuscation value associated with the second distributed ledger system to a second distributed ledger system. generating a second request for a second block in a second blockchain; receiving a second block value from the second distributed ledger system representing the second block in the second blockchain; and wherein said record associates said second block value with said digital property.

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

23. The system of clause 20, 21, or 22, wherein the document obfuscation value includes a first document obfuscation value, and the operations further include: identifying the first portion of the document and the second portion of the document; generating a second document obfuscation value representative of the first portion of the document; generating a third document obfuscation value representative of the second portion of the document; and wherein generating the first document obfuscation value includes based at least in part on The second document confusion value and the third document confusion value are used to generate the first document confusion value.

24. A system as claimed in clause 20, 21, 22 or 23, wherein said block comprises a first block, said blockchain comprises a first blockchain and said block value comprises a first block value , the time value includes a first time value, the distributed ledger system includes a first distributed ledger system, the request includes a first request, and the operation further includes: sending a request to a second distributed ledger system sending the document obfuscation value 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 representation representing the a second block value of the second block in the second blockchain; and wherein the record associates the second block value with the digital property.

25. The system of clause 20, 21, 22, 23 or 24, wherein the input data includes first input data, and the operations further include receiving second input data, the second input data indicating At least one of: a title associated with the document, a type of trade secret associated with the document, or an identifier of a person or entity associated with the document; based at least in part on the first two input data to generate tag data; receiving a third input data requesting a search for digital property associated with the digital property registry, the third input data including a search term; and causing the data to be generated based at least in part on receiving the third input data. Three input data are used to search the tag data for the search terms.

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

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 includes receiving the document via the firewall and based at least in part on the security rules permitting receipt of the document from the electronic device; sending the document obfuscation value and the request to the distributed ledger system includes via the firewall and transmitting the document obfuscation value and the request based at least in part on the security rules that permit transmission of the document obfuscation value and the request to the distributed ledger system; from the distributed ledger system receiving the block value by the ledger system includes receiving the block value via the firewall and based at least in part on the security rules permitting receipt of the block value from the distributed ledger system; and transferring the block value to the ledger system. Sending the confirmation data to the electronic device includes sending the confirmation data via the firewall and based at least in part on the security rules that permit transmission of the confirmation data to the electronic device.

28. A system comprising: one or more processors; and non-transitory computer-readable media storing computer-executable instructions that when executed by the one or more processors causing the one or more processors to perform operations including: receiving a document obfuscation value from an electronic device representing a document corresponding to a digital property; receiving a request to register the digital property in association with a digital property registry; analyzing the document obfuscation value against a stored document obfuscation value stored in association with the digital property registry; determining the document obfuscation based at least in part on analyzing the document obfuscation value relative to the stored document obfuscation value a value that is different from the stored document obfuscation value; receiving a block value associated with the document obfuscation value from a distributed ledger system, the block value representing a block in the blockchain; and, at least in part, Based on determining that the document obfuscation value is different from the stored document obfuscation value, a record is generated in the digital property registry, the record: indicating that the digital property has been registered in the digital property registry; and registering the digital property in the digital property registry. The block value is associated 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 includes determining that the document obfuscation value is different from the stored document obfuscation value based at least in part on determining that the document obfuscation value is different from the stored document obfuscation value. a difference between the document confusion value and the stored document confusion value; and determining that the difference is greater than a threshold difference.

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

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

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

33. The system of clause 32, wherein the document obfuscation value includes a first document obfuscation value, and the operations further include: identifying the first portion of the document and the second portion of the document; generating a representation of the a second document obfuscation value for the first portion of the document; generating a third document obfuscation value representative of the second portion of the document; and wherein generating the first document obfuscation value includes based at least in part on the second The document obfuscation value and the third document obfuscation value are used to generate the first document obfuscation value.

34. The system of clause 32 or 33, wherein the document obfuscation value includes a first document obfuscation value, the block includes a first block, the block chain includes a first block chain, and the block chain includes a first block chain. The block value includes a first block value, the distributed ledger system includes a first distributed ledger system, and generating the first document obfuscation value includes generating the first document obfuscation value using a first hash value generator. , and the operations further include generating, based at least in part on receiving the input, a second document obfuscation value representing the document, the second document obfuscation value being generated using a different hash value generator than the first hash value generator. generated by a second hash value generator; sending the second document obfuscation value to the registration system; and wherein the confirmation data indicates that the digital property has been associated with the second document obfuscation value A second block value is associated, the second block value representing a second block in a second blockchain associated with the second distributed ledger system.

35. The system of clause 32, 33, or 34, wherein the input includes a first input, and the operations further include receiving a second input indicative of at least one of: a title associated with the document, A type of trade secret associated with the document or identification of at least one of a person or entity associated with the document; generating tag data based at least in part on the second input; storing the tag data; receiving Requesting a third input to search the digital property registry, the third input including a search term; causing the tag data to be searched based at least in part on the search term; and generating the search indicative of at least the tag data The resulting response 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 fields associated with all of the fields. a field value associated with each 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 of the respective one of the fields. .

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

38. The system of clause 37, wherein the options comprise 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 display, based at least in part on receiving the third input, of information associated with at least one of the insurance policy or the trade secret one or more requests for information; and one or more input fields configured to receive text input in response to the one or more requests for information; receiving input to the one or more input fields via the user interface. text input into various input fields; receiving an indication from an underwriter system associated with the underwriter that the policy has been issued; and causing policy information associated with the policy to be displayed via the user interface.

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

40. The system of clause 37, 38 or 39, wherein the options comprise a first option, and the operations further comprise causing an input field associated with the document to be displayed via the user interface, the input The fields include at least one of: a document name field, a document description field, or a label field; causing a second option to automatically populate at least one of the input fields to be displayed via the user interface; receiving an indication via the user interface to automatically populating a third requested third input of the at least one of the input fields; and causing text to be displayed 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 options include a first option, the block value includes a first block value, the block includes a first block, and the Operations further include causing display, via the user interface, of 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 an identification using the user interface a third input of the information document; causing display, via the user interface, of the value determined by the registration system based at least in part on the information document; and wherein the record indicates a connection with all records for which the information document has been registered. The second block value associated with the second block of the blockchain.

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

43. The method of clause 42, wherein the options comprise a first option, and the method further comprising: causing display of a second option to obtain an insurance policy associated with the digital property; receiving a request to obtain the insurance Single third input data; causing display of an input field configured to receive text input in response to a request for information based at least in part on said third input data; receiving fourth input data representative of said text input to said input field ; receiving an indication from an insurer's system associated with the insurer that the policy has been issued; and causing policy information associated with the policy to be displayed.

44. The method of clause 42 or 43, wherein the options comprise a first option, and the method further comprising: causing to display a second option that determines a value of an input field associated with the document; via the A user interface receives third input data requesting determination of the value; and causes text to be displayed 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; such that the text is relative to the input field based at least in part on the fourth input data Display the manipulated text; cause a request to confirm the manipulated text displayed in the input field to be displayed via the user interface; receive fifth input data via the user interface indicating confirmation of the manipulated text; and The manipulated text is associated 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 options include a first option, the document includes a first document, and the method further includes causing display to associate a second document with the number. a second option associated with a property, the second document indicating information associated with a value of the digital property; receiving third input data identifying the second document; and causing based at least in part on the second document to display text indicating the value.

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 obfuscation value corresponding to the document; based at least in part on the characteristic to determine a type of trade secret associated with the document; and causing text indicating the type of trade secret to be displayed via the user interface.

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

49. The method of clause 42, 43, 44, 45, 46, 47, or 48, wherein the option includes a first option, the document includes a first document, and the method further includes causing, via the The user interface displays a second option to verify that a second document corresponds to the first document; receives third input data requesting to verify that the second document corresponds to the first document; causes a request to identify the second document to be displayed ; receiving fourth input data identifying the second document; and causing display, via the user interface, of a first document obfuscation value associated with the first document and a second document obfuscation associated with the second document. An indication that the values are at least threshold similar.

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

51. The method of clause 50, wherein the input data includes first input data, and the method further includes: causing an option to obtain an insurance policy associated with the digital property to be displayed; receiving a request to obtain the insurance a single second input data; causing display of an input field configured to receive text input in response to a request for information based at least in part on said second input data; receiving third input data representative of said text input to said input field ; receiving an indication from an insurer's system associated with the insurer that the policy has been issued; and causing policy information associated with the policy to be displayed.

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

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 obfuscation value corresponding to the document; determining, based at least in part on the characteristic, that the document is consistent with the document. a trade secret type associated with the document; and causing text indicating the trade secret type to be displayed via the user interface.

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

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

56. The method of clause 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, said The insurance policy information includes a payment value associated with an amount paid to the entity associated with the trade secret upon the occurrence of the event; receiving compliance data indicating that the entity has not complied with a condition of the insurance policy; and enabling access via the The user interface displays updated insurance policy information including an 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 includes first input data, the document includes a first document, and the method further includes: causing via The user interface displays an option to verify that the second document is similar to the first document; receives second input data requesting to verify that the second document is similar to the first document; causing a request to identify the second document to be displayed ; receiving third input data identifying the second document; and causing display, via the user interface, of a first document obfuscation value associated with the first document and a second document obfuscation associated with the second document. An indication that the values are at least threshold similar.

58. A system comprising: one or more processors; and non-transitory computer-readable media storing computer-executable instructions that when executed by the one or more processors Causes the one or more processors to perform operations including: storing a first record in association with a trade secret registry, the first record indicating: a first document obfuscation corresponding to a first document representing a trade secret value; and a block value generated based at least in part on the obfuscated value of the first document, the block value representing a block in the blockchain of the distributed ledger system; receiving the first document representing the an indication of a first version of a document; receiving input data from an electronic device requesting registration of a second document in association with the trade secret registry; receiving a second document obfuscation corresponding to the second document from the electronic device value; 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 the an identifier of the second document that 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, The selectable link causes the first record to be displayed.

59. The system of clause 58, wherein the input data includes first input data, and the operations further include storing a first identifier indicative of a first person permitted to access the first record. Access control data; storing second access control data indicating a second identifier of a second person who is permitted to access the second record, the second access control data indicating that the second person is not permitted to access the first record. Access to the record; 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; based at least in part on the second input data displaying the second record including the selectable link; receiving third input data corresponding to selection of the selectable link; and based at least in part on the second access indicating that access to the first record is not allowed Control data to avoid causing the first record to be displayed.

60. The system of clause 58 or 59, said operations further comprising: associating said trade secret with an insurance policy using a smart contract associated with said blockchain, said smart contract instructing for verification a condition of the insurance policy; receiving verification data from the electronic device indicating that the condition has been met; sending the verification data to the distributed ledger system, the verification data causing the smart contract to verify the an insurance policy; and receiving confirmation data from the distributed ledger system indicating that the insurance policy has been certified using the smart contract.

61. The system of clause 58, 59, or 60, wherein the block value includes a first block value, the block includes a first block, and the operations further include: receiving from the electronic device Valuation data indicated as being related to the value of the trade secret; receiving from the electronic device a third document obfuscation value corresponding to the valuation data; from the electronic device or the distributed ledger system At least one of receives 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 blockchain; and wherein the first The record includes the third document obfuscation value and the second block 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; associating a second feature vector with the second document based at least in part on second text data associated with the second document; determining a relationship 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 includes determining that the second document corresponds to the second version based at least in part on the distance being less than the threshold distance. the second version of the first document.

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 associated; determining a number of other feature vectors within a threshold distance from the first feature vector; and determining a popularity associated with the first document based at least in part on the number of other feature vectors Fraction.

64. The system of clause 58, 59, 60, 61, 62 or 63, the operations further comprising: receiving an indication of the type of trade secret associated with the trade secret; identifying registration with the trade secret registry a frequency of trade secret versions associated with the trade secret type; generating a version registration 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: using the electronic device or an entity identifier corresponding to an entity associated with the electronic device At least one of determining a frequency with which trade secret versions are registered with the trade secret registry; generating a version registration 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 trade secret; and based at least in part on the first document obfuscating a first block value generated by the value, said first block value representing a first block in a blockchain of the distributed ledger system; receiving from an electronic device an estimate associated with a value of said trade secret. value data; receiving from the electronic device a second document obfuscation value corresponding to the valuation data; receiving from at least one of the electronic device or the distributed ledger system based at least in part on the second a second block value generated by the document obfuscation value, the second block value representing a second block in the blockchain; and wherein the record includes the second document obfuscation value and the second zone block value.

67. The method of clause 66, wherein the document includes a first document, the record includes a first record, and the method further includes receiving the first document representing a first version of the first document an instruction; receiving input data from the electronic device requesting registration of a second document in association with the trade secret registry; receiving a third document obfuscation value corresponding to the second document from the electronic device; at least in part determining that the second document corresponds to a second version of the first document based on a comparison of the first document obfuscation value and the third document obfuscation value; and generating a second record indicating that the business has Registering an identifier of the second document in association with a 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 who is permitted to access the first portion of the record; storing first access control data indicating that the first person is permitted to access the first portion of the record; second access control data for a second identifier of a second person for a second portion of the record, the second access control data indicating that access by the second person to the first portion of the record is not permitted; receiving a request first input data to access the record, the first input data indicating that the second person is requesting access to the record; causing the second portion of the record to be displayed based at least in part on the first input data ; receiving second input data from the second person requesting access to the first portion of the record; and avoiding based at least in part on the second access control data indicating that access to the first portion of the record is not permitted. Causes the first portion of the record to be displayed.

69. The method of clause 66, 67 or 68, further comprising: associating the trade secret with an insurance policy using a smart contract associated with the blockchain, the smart contract instructing for verification a condition of the insurance policy; receiving verification data from the electronic device indicating that the condition has been met; sending the verification data to the distributed ledger system, the verification data causing the smart contract to verify the an insurance policy; and receiving confirmation data from the distributed ledger system indicating that the insurance policy has been certified using the smart contract.

70. A system comprising: one or more processors; and non-transitory computer-readable media storing computer-executable instructions that when executed by the one or more processors Causes the one or more processors to perform operations including storing first access control data indicating a first person permitted to access records associated with the trade secret registry. an identifier, the record indicating a trade secret registered in association with the trade secret registry; and a function of the trade secret registry authorized for use by the first person; storing second access control data, the The second access control data indicates: a second identifier of a second person who is allowed to access the record; and the second person is not authorized to use the function; first input data requesting access to the record is received, so the first input data indicating that the second person is requesting access to the record; causing the record to be displayed based at least in part on the first input data; receiving second input data requesting use of the function; and Preventing execution of the function based 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 includes a first trade secret, the record includes a first document obfuscation value corresponding to the first trade secret, and the operations further comprise: receiving the an indication that a first trade secret represents a first version of the first trade secret; receiving third input data from an electronic device 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 trade secret; determining, based at least in part on a comparison of the first document obfuscation value and the second document obfuscation value, that the second trade secret corresponds to the first a second version of a trade secret; and generating a second record indicating that the second trade secret has been registered in association with the trade secret registry; and indicating that the second trade secret is all of the first trade secret. Describe the second version.

72. The system of clause 70 or 71, wherein a first document obfuscation value corresponds to the document, a first block value is associated with the trade secret, and the operations further comprise: receiving an instruction from an electronic device Valuation data related to the value of the trade 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 receiving 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 blockchain of the distributed ledger system; and wherein the record includes The second document obfuscation value and the second block value.

73. The system of clause 70, 71, or 72, wherein the record indicates a document obfuscation value corresponding to the trade secret and a block value generated based at least in part on the document obfuscation value, the block value representing a distribution a block in a blockchain of a ledger system, and the operations further include associating the trade secret with an insurance policy using a smart contract associated with the blockchain, the smart contract instructing to use to substantiate a condition of the insurance policy; receiving confirmation data from an electronic device indicating that the condition has been met; sending the confirmation data to the distributed ledger system, the confirmation data causing the smart contract to confirm said an insurance policy; and receiving confirmation data from the distributed ledger system indicating that the insurance policy has been certified using the smart 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: each of the persons who accessed the record. an identifier of a person, including the first person; and a time value at which each of the persons accessed the record; receiving the first access control data associated with the first person an indication that has been removed; and generating alert data indicating that the first person has accessed the record; indicating one or more time values when the first person accessed the record; and requesting confirmation that the first person Have undergone an exit interview related to said 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: of the persons who accessed the record an identifier of each person, including the first person; and a value of the time at which each of the persons accessed the record; generating, based at least in part on the log, information related to the trade secret a compliance schedule associated with the insurance policy that indicates a time period during which the first person may enforce compliance with a condition of the insurance policy; a determination that the condition has not expired before the expiration of the time period is satisfied; 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, the interface being configured to allow accessing at least a portion of the trade secret registry through an associated remote archiving system; sending access information for the interface to the remote archiving system; receiving from the remote archiving system to perform a search of the trade secret registry a request that includes text data for searching the trade secret registry; identifying results of the search; and sending result data representative of the results to the remote filing system.

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

78. A system comprising: one or more processors; and non-transitory computer-readable media storing computer-executable instructions that when executed by the one or more processors Causes the one or more processors to perform operations including: storing a record in association with a trade secret registry indicating: a document obfuscation value corresponding to a document representing a trade secret; and based at least in part on a block value generated by the document obfuscation value, the block value representing a block in a blockchain of a distributed ledger system; receiving valuation data from an electronic device indicated to be related to the value of the trade secret; determining the value of the trade secret based at least in part on the valuation data; and causing display of an indication of the value via a user interface accessible via 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 characteristics associated with the document, the The series of dialog boxes includes text associated with determining the value of the trade secret; sending data representative of the series of dialog boxes to the electronic device; and wherein the valuation data includes an estimate of the series of dialog boxes. input of.

80. The system of clause 78 or 79, wherein the trade secret includes a first trade secret, the value includes a first value, and the operations further include: based, at least in part, on instructing a user associated with the document. Characteristic tag data that determines a trade secret type associated with the first trade secret; identifies a second trade secret associated with the trade secret type; identifies a second value associated with the second trade secret; and wherein determining the first value of the first trade secret includes determining the first value of the first trade 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 being associated with the document and wherein determining the value of the trade secret includes determining the value of the trade 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 includes based at least in part on a time value associated with the registration of the block in the blockchain The value of the trade secret is determined such that the value increases as the time period between the time value and the current time increases.

83. The system of clause 78, 79, 80, 81 or 82, wherein the block value includes a first block value, the document obfuscation value includes a first document obfuscation value, and the block includes a first block, and the operations further include receiving from the distributed ledger system a second block value generated based at least in part on a second document obfuscation value corresponding to the financial data associated with the trade secret, the second block value represents a second block in the blockchain of the distributed ledger system; and wherein determining the value of the trade secret includes based at least in part on receiving the second block block value to determine the value of the trade secret.

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 trade secret; and generating a document based at least in part on the document obfuscation value a block value representing a block in a blockchain of a distributed ledger system; receiving input data from an electronic device requesting the issuance of an insurance policy associated with the trade secret; generating an insurance policy request, The request indicates that: the trade secret has been registered with the trade secret registry; and the block value; sending the insurance policy request to an underwriter system associated with the underwriter; receiving from the underwriter system an indication that the insurance policy has been issued; and causing a user interface accessible via the electronic device to display the indication that the insurance policy has been issued.

85. The method of clause 84, wherein the input data includes first input data, and the method further includes determining to display via the user interface based at least in part on tag data indicative of characteristics of the document a series of dialog boxes, the series of dialog boxes including text associated with applying for the insurance policy; sending data representing the series of dialog boxes to the electronic device; receiving an instruction from the electronic device to the Second input data in response to a series of dialog boxes; and wherein the insurance 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: an identifier of each of the persons who accessed the record; and a time value at which each of the persons accessed the record; and generating a compliance schedule associated with the insurance policy based at least in part on the log, the compliance schedule indicating which of the persons A time period during which at least one person may enforce compliance with a condition of the insurance policy; a determination that the condition is not satisfied prior to expiration of the time period; and an adjustment to the policy based at least in part on a determination that the condition has not been satisfied Single associated payment value.

87. The method of clause 84, 85, or 86, further comprising: based at least in part on determining that the condition is not met before expiration of the time period, generating alert data indicating that the condition is not met; and The alert data is sent to the one or more electronic devices, the alert data causing a processor 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 block value includes a first block value, the document obfuscation value includes a first document obfuscation value, and the block includes a first block , and the method further includes receiving from the distributed ledger system a second block value generated based at least in part on a second document obfuscation value corresponding to the financial data associated with the trade secret, the The second block value represents a second block in the blockchain of the distributed ledger system; and wherein the insurance 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 records; and wherein the insurance policy request includes a value of the trade secret Said value.

90. The method of paragraph 84, 85, 86, 87, 88, or 89, further comprising causing information associated with the insurance policy to be displayed via the user interface, the information comprising at least one of the following: policy Type; limit of liability; retained value; or policy premium value.

91. A system comprising: one or more processors; and non-transitory computer-readable media storing computer-executable instructions that when executed by the one or more processors Causes the one or more processors to perform operations including: storing a record in association with a trade secret registry indicating: a document obfuscation value corresponding to a document representing a trade secret; and based at least in part on a block value generated by the document obfuscation value, the block value representing a block in a blockchain of a distributed ledger system; receiving input data from an electronic device requesting the 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 insurance policy request to an underwriter system associated with the insurer; and receiving an indication from said insurer's system that said insurance policy has been issued.

92. The system of clause 91, wherein the input data includes first input data, and the operations further include determining a series of dialog boxes to be displayed via the user interface, the series of dialog boxes including information related to the application. text associated with the insurance policy; sending data representing the series of dialog boxes to the electronic device; receiving second input data from the electronic device indicative of a response to the series of dialog boxes; and wherein the The insurance policy request includes the second input data.

93. The system of clause 91 or 92, the operations further comprising: generating a log of one or more electronic devices accessing the record, the log indicating an identifier of each of the persons who accessed the record; Generating a compliance schedule associated with the insurance policy based at least in part on the logs, the compliance schedule indicating a time period during which at least one of the persons may enforce compliance with a condition of the insurance policy ; determining that the condition is not satisfied before expiration of the time period; and adjusting a payment value associated with the 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 satisfied prior to expiration of the time period, generating alert data indicating that the condition is not satisfied; and sending the alert data to the one or more electronic devices, the alert data causing a processor 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 block value includes a first block value, the document obfuscation value includes a first document obfuscation value, and the block includes a first block , and the operations further include receiving from the distributed ledger system a second block value generated based at least in part on a second document obfuscation value corresponding to the financial data associated with the trade secret, the The two-block value represents a second block in the blockchain of the distributed ledger system; and wherein the insurance 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 records; and wherein the insurance policy request includes the trade secret The stated value of the 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 the following: policy Type; limit of liability; retained value; or policy premium value.

98. A system comprising: one or more processors; and non-transitory computer-readable media storing computer-executable instructions that when executed by the one or more processors Causes the one or more processors to perform operations including: storing a record in association with a trade secret registry, the record indicating: a first document obfuscation value corresponding to a first document representing the trade secret; and at least generating a block value based in part on the first document obfuscation value, the block value representing a block in a blockchain of a distributed ledger system; receiving a second document from an electronic device that is indicated to have been compromised; Receive input data from the electronic device that requests verification that the second document corresponds to a registered document registered with the trade secret registry; and generate a document corresponding to the second document based at least in part on the second document. a second document confusion value for a 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 based at least in part on the similarity degree is greater than the threshold similarity to determine that the second document corresponds to the first document.

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 portion; causing the second document confusion value to be segmented into second segments, each of the second segments corresponding to a portion of the second document; wherein determining the similarity includes based at least in part on a relative analyzing the first segment with respect to the second segment to determine the similarity; and wherein determining that the similarity is greater than the threshold similarity includes based at least in part on the first segment corresponding to the second segment The number is greater than the threshold number of segments to determine that the similarity is greater than the threshold similarity.

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

101. The system of clause 98, 99, or 100, wherein the block value includes a first block value, the block includes a first block, and the operations further include: classifying to the distributed The ledger system sends the second document obfuscation value; and sends a request to the distributed ledger system to identify a second block value corresponding to the second document obfuscation value, the second block value representing the a second block in a blockchain; receiving the second block value from the distributed ledger system; determining that the first block value corresponds to the second block value; and wherein determining that the Corresponding the second document to the first document includes determining that the second document corresponds to the first document based at least in part on the first block value corresponding to the second block value.

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

103. The method of clause 102, further comprising: causing the first document confusion value to be segmented into a first segment; causing the second document confusion value to be segmented into a second segment; and wherein determining the similarity The degree includes determining the degree of 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 Levenstein distance between a first characteristic of the first document and a second characteristic of the second document; and wherein determining the similarity The degree includes determining the degree of similarity based at least in part on the Levenstein distance.

105. The method of clause 102, 103, or 104, wherein the block value includes a first block value, and the method further comprises: receiving from the distributed ledger system corresponding to the second document a second block value of obfuscated values; determining that the first block value corresponds to the second block value; and wherein determining that the second document corresponds to the first document includes based at least in part on the A block value corresponding to the second block value determines that the second document corresponds to the first document.

106. The method of clause 102, 103, 104, or 105, wherein the record includes a first record associated with a first version of the first document, and the similarity includes a first similarity, and the method further includes storing a second record associated with the second version of the first document, the second record being associated with the first record based at least in part on the second record associated with the second version of the first document; determining a second degree of 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 includes 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 a series of dialog boxes including text associated with submitting a paragraph for coverage in connection with an insurance policy for the trade secret; receiving input data including a response to the text; and The underwriter's associated underwriter system sends at least one of the input data or a notification of the paragraph.

108. The method of clause 102, 103, 104, 105, 106, or 107, further comprising: receiving status data from the underwriter system indicating that information was requested to process the paragraph; The electronic device sends an alert indicating that the information is requested; and causes the 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 value of the first document obfuscation value corresponding to a second portion of the second document obfuscation value. a first portion; identifying a third portion of the first document corresponding to the first portion of the first document obfuscation value; and causing display of the third portion via a user interface and based at least in part on identifying the third portion. 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 non-transitory computer-readable media storing computer-executable instructions that when executed by the one or more processors Causes the one or more processors to perform operations including: storing a record indicating: a first document obfuscation value corresponding to a first document corresponding to a trade secret; and based at least in part on the first document a block value generated by a document obfuscation value, the block value representing a block in a blockchain of a distributed ledger system; receiving a second document from an electronic device that is indicated to have been compromised; based at least in part on the a second document generates a second document confusion value corresponding to the second document; determines a similarity between the first document confusion value and the second document confusion value; and based at least in part on the similarity It is determined that the second document corresponds to the first document.

111. The system of clause 110, the operations further comprising: causing the first document obfuscation value to be segmented into a first segment; causing the second document obfuscation value to be segmented into a second segment; and wherein it is determined that the The similarity includes 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 Levenstein distance between a first characteristic of the first document and a second characteristic of the second document; and wherein determining the The similarity includes determining the similarity based at least in part on the Levenstein distance.

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

114. The system of clause 110, 111, 112, or 113, wherein the record includes a first record associated with a first version of the first document, and the similarity includes a first similarity, and the operations further include storing a second record associated with a second version of the first document, the second record being associated with the first record based at least in part on the second record associated with the second version of the first document; determining a second degree of 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 includes 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, such that, via a user of the electronic device The interface displays a series of dialog boxes including text associated with submitting a paragraph for insurance coverage in association with an insurance policy for the trade secret; receiving input data including a response to the text; and At least one of the input data or a notification of the paragraph is sent to an underwriter system associated with an underwriter that issued the insurance policy.

116. The system of clause 110, 111, 112, 113, 114, or 115, the operations further comprising: receiving status data from the underwriter system, the status data indicating that information is requested to process the paragraph; sending an alert to the electronic device indicating that the information is requested; and causing the 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 the first document obfuscation corresponding to a second portion of the second document obfuscation value a first portion of a 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 An indication that the third portion of the first document is similar to at least a portion of the second document.

Claims (35)

1. A method for digital property authentication or management, the method comprising:

receiving, at the electronic device, a document representative of a trade secret;

receiving, at the electronic device, an input 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 confusion value representing the document based at least in part on receiving the input;

storing security rules associated with a firewall of the electronic device;

transmitting the document confusion value and a first request from the electronic device for generating a block in a blockchain, the blockchain being associated with a distributed ledger system that is at least remote from the electronic device, wherein transmitting the document confusion value and the first request is performed via the firewall and based at least in part on the security rules that allow the document confusion value and the request to be transmitted to the registration system;

receiving, at the electronic device, a blockvalue from the distributed ledger system that represents the block in the blockchain;

sending, from the electronic device and to the registration system, a second request for registering the document with respect to the trade secret registry, the second request including the block value and a time value associated with generation of the block value;

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 registration;

Including the block value; and

indicating the time value;

generating acknowledgement data indicating that the record has been generated;

transmitting the validation data from the registration system to the electronic device, wherein transmitting the validation data is performed via the firewall and based at least in part on the security rules that allow transmission of the validation data to the registration system; and

on the electronic device and based at least in part on the confirmation data, causing a user interface to be displayed, the user interface including the record and displaying (1) an indication that the trade secret has been registered at the trade secret registry, (2) the tile value, and (3) the time value.

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

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

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

generating a third document confusion value representing the second portion of the document; and is also provided with

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

3. The method of claim 1, wherein the block comprises a first block, the blockchain comprises a first blockchain, the block value comprises a first block value, the time value comprises a first time value, and the method further comprises:

sending the document confusion value and a third request for generating a second block in a second blockchain associated with the insurer system from the electronic device and to the insurer system;

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

sending the second block value and a second time value associated with generation of the second block value from the electronic device and to the registration system; and is also provided with

The record in the trade secret registry is associated with the second block value and the second time 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: an identifier of at least one of a title, a trade secret type, 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 trade secret;

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

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

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

6. A system for digital property authentication or management, the 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 confusion value representing the document based at least in part on receiving the input;

Storing security rules associated with a firewall of the system;

transmitting the document confusion value and a request to the registration system for registering the digital property in association with the digital property registry, wherein transmitting the document confusion value and the request is performed via the firewall and based at least in part on security rules that allow the document confusion value and the request to be transmitted to the registration system;

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 having associated with it a blockvalue representing a block in a blockchain associated with a distributed ledger system, wherein receiving the validation data is performed via the firewall and based at least in part on the security rules allowing the validation data to be received from the registration system; and

based at least in part on the confirmation data, causing a user interface to be displayed, the user interface displaying an indication: (1) The digital property has been registered in association with the digital property registry, and (2) the digital property has been associated with the block value.

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

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

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

generating a third document confusion value representing the second portion of the document; and is also provided with

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

8. The system of claim 6, wherein the chunk comprises a first chunk, the blockchain comprises a first blockchain, the chunk value comprises a first chunk value, the distributed ledger system comprises a first distributed ledger system, and the operations further comprise:

requesting that the digital property be registered in association with a second distributed ledger system prior to receiving the validation data; and

wherein the validation data indicates that the digital property has been associated with a second blockvalue that represents a second blockin a second blockchain associated with the second distributed ledger system.

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

generating a second document confusion value representing the document based at least in part on receiving the input, the second document confusion value generated using a second hash value generator that is different from the first hash value generator;

transmitting the second document confusion value to the registration system; and is also provided with

Wherein the validation data indicates that the digital property has been associated with a second blockvalue associated with the second document confusion value, the second blockvalue representing a second blockin a second blockchain 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 trade 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;

storing the tag data;

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

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

response data is generated indicating the 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

tag data associated with the document is generated, the tag data generated based at least in part on the field type and the field value of the respective one of the fields.

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

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

generating a second document confusion 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

the second document is determined to correspond to the first document based at least in part on the first document confusion value corresponding to the second document confusion value.

13. A method for digital property authentication or management, the method comprising:

receiving, from the electronic device, a document confusion value representing a document corresponding to the digital property;

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

sending the document confusion value and a request for generating a block in a blockchain associated with the distributed ledger system to a distributed ledger system;

receiving a blockvalue from the distributed ledger system representing the blockin the blockchain; 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.

14. The method of claim 13, wherein the document confusion value comprises a first document confusion value, the chunk comprises a first chunk, 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 a second document confusion value representing the document from the electronic device;

sending the second document confusion value and a second request for generating a second chunk in a second blockchain associated with a second distributed ledger system to the second distributed ledger system;

receiving a second block value from the second distributed ledger system representing the second block in the second blockchain; and is also provided with

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

15. The method of claim 13, wherein the record comprises a first record, and the method further comprises:

receiving an identifier corresponding to at least one of:

an electronic device; or (b)

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

the first record is associated with the second record based at least in part on determining that the first record and the second record are associated with the identifier.

16. The method of claim 13, wherein the chunk comprises a first chunk, 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 confusion value and a second request for generating a second chunk in a second blockchain associated with a second distributed ledger system to the second distributed ledger system;

receiving a second block value from the second distributed ledger system representing the second block in the second blockchain; and

wherein the record associates the second block value with the digital property.

17. The method of claim 13, wherein the input data comprises first input data, and the method further comprises:

Receiving second input data indicative of at least one of: an identifier of at least one of a title associated with the document, a type of trade 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 for digital property associated with the digital property registry, the third input data comprising search terms; and

based at least in part on receiving the third input data, the tag data is caused to be searched for the search term.

18. The method of claim 13, further comprising:

identifying fields of the document based at least in part on the document confusion value, each of the fields being associated with a field type;

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

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

19. A system for digital property authentication or management, 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 data from the electronic device representative of a document corresponding to the digital property;

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

generating a document confusion value representing the document based at least in part on receiving the input data;

removing the document from the system;

sending the document confusion value and a request for generating a block in a blockchain associated with the distributed ledger system to a distributed ledger system;

receiving a blockvalue from the distributed ledger system representing the blockin the blockchain; 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 block value or the generation of the record.

20. The system of claim 19, wherein the document confusion value comprises a first document confusion value, the chunk comprises a first chunk, 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, generating the first document confusion value comprises generating the first document confusion value using a first hash value generator, and the operations further comprise:

generating a second document confusion value representing the document based at least in part on receiving the input data, the second document confusion value generated using a second hash value generator that is different from the first hash value generator;

sending the second document confusion value and a second request for generating a second chunk in a second blockchain associated with a second distributed ledger system to the second distributed ledger system;

receiving, from the second distributed ledger system, a second block value representative of the second block in the second blockchain; and is also provided with

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

21. The system of claim 19, 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 (b)

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

the first record is associated with the second record based at least in part on determining that the first record and the second record are associated with the identifier.

22. The system of claim 19, wherein the document confusion value comprises a first document confusion value, and the operations further comprise:

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

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

generating a third document confusion value representing the second portion of the document; and is also provided with

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

23. The system of claim 19, 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 confusion value and a second request for generating a second chunk in a second blockchain associated with a second distributed ledger system to the second distributed ledger system;

receiving a second block value from the second distributed ledger system representing the second block in the second blockchain; and is also provided with

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

24. The system of claim 19, wherein the input data comprises first input data, and the operations further comprise:

receiving second input data, the second input data being indicative of at least one of: an identifier of at least one of a title associated with the document, a type of trade 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 for digital property associated with the digital property registry, the third input data comprising search terms; and

such that the tag data is searched for the search term based at least in part on receiving the third input data.

25. The system of claim 19, 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

tag data associated with the document is generated, the tag data generated based at least in part on the field type and the field value of the respective one of the fields.

26. The system of claim 19, the operations further comprising:

storing security rules associated with the firewall; and is also provided with

Wherein:

receiving the document from the electronic device includes receiving the document via the firewall and based at least in part on the security rules allowing the document to be received from the electronic device;

Sending the document confusion value and the request to the distributed ledger system includes: transmitting the document confusion value and the request via the firewall and based at least in part on the security rules that allow transmission of the document confusion value and the request to the distributed ledger system; and

receiving the block value from the distributed ledger system includes: the block value is received via the firewall and based at least in part on the security rules allowing the block value to be received from the distributed ledger system.

27. A system for digital property authentication or management, the 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 the electronic device, a document confusion value representing a document corresponding to the digital property;

receiving a request to register a digital property in association with the digital property registration department;

analyzing the document confusion value relative to stored document confusion values stored in association with the digital property registry;

Determining that the document confusion value is different from the stored document confusion value based at least in part on analyzing the document confusion value relative to the stored document confusion value;

receiving a chunk value associated with the document confusion value from a distributed ledger system, the chunk value representing a chunk in the blockchain; and

generating a record in the digital property registry based at least in part on determining that the document confusion value is different from the stored document confusion value, the record:

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

the block value is associated with the digital property.

28. The system of claim 27, wherein determining that the document confusion value is different from the stored document confusion value comprises determining that the document confusion value is different from the stored document confusion value based at least in part on:

determining a degree of difference between the document confusion value and the stored document confusion value; and

and determining that the difference degree is greater than a threshold difference degree.

29. The system of claim 27, 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 an entity identifier associated with the document confusion value is associated with the at least one of the stored document confusion values; and

the digital property and at least one digital property associated with the at least one of the stored document confusion values are associated 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 confusion values and the stored document confusion values.

30. The system of claim 27, the operations further comprising:

generating acknowledgement data, the acknowledgement data indicating:

the record has been associated with the digital property registry; and

the document having been determined to be unique relative to other documents registered in association with the digital property registry; and

the confirmation data is sent to the electronic device.

31. A system for digital property authentication or management, the 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 confusion value representing the document based at least in part on receiving the input;

storing security rules associated with a firewall of the system;

transmitting the document confusion value and a first request for registering the document confusion value with the distributed ledger system to the distributed ledger system;

receiving, from the distributed ledger system, a blockvalue indicating that the document confusion value has been registered in a blockof a blockchain associated with the distributed ledger system;

transmitting the document confusion value, the block value, and a second request to the registration system for registering the digital property in association with the digital property registry, wherein transmitting the document confusion value, the block value, and the second request is performed via the firewall and based at least in part on security rules that allow transmission of the document confusion value, the block value, and the second request to the registration system;

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 having associated with a block value, wherein receiving the validation data is performed via the firewall and based at least in part on the security rules allowing receipt of the validation data from the registration system; and

based at least in part on the confirmation data, causing a user interface to be displayed, the user interface displaying an indication: (1) The digital property has been registered in association with the digital property registry, and (2) the digital property has been associated with the block value.

32. The system of claim 31, wherein the document confusion value comprises a first document confusion value, and the operations further comprise:

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

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

generating a third document confusion value representing the second portion of the document; and is also provided with

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

33. The system of claim 31, wherein the document confusion value comprises a first document confusion value, the chunk comprises a first chunk, the blockchain comprises a first blockchain, the blockvalue comprises a first blockvalue, the distributed ledger system comprises a first distributed ledger system, generating the first document confusion value comprises generating the first document confusion value using a first hash value generator, and the operations further comprise:

generating a second document confusion value representing the document based at least in part on receiving the input, the second document confusion value generated using a second hash value generator that is different from the first hash value generator;

transmitting the second document confusion value to the registration system; and is also provided with

Wherein the validation data indicates that the digital property has been associated with a second blockvalue associated with the second document confusion value, the second blockvalue representing a second blockin a second blockchain associated with a second distributed ledger system.

34. The system of claim 31, 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 trade 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;

storing the tag data;

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

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

response data is generated indicating results of the search for at least the tag data.

35. The system of claim 31, 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

tag data associated with the document is generated, the tag data generated based at least in part on the field type and the field value of the respective one of the fields.