JP2021518028A - Decentralized marketplaces and ecosystems enabled by blockchain-based document distribution, collaboration, and distribution - Google Patents

Abstract

Disclosed herein are systems, methods, and computer program product embodiments for managing documents using the blockchain. A token server system can facilitate the creation of documents. The token server system can encrypt and store an encrypted version of a document and create a link to the encrypted version of the document. The token server system may also create a document token for depositing within a digital wallet to specify the cryptographic hash of the document and ownership of the document. The token server system may expose links and hashes to the blockchain using one or more smart contract features. In some embodiments, the document can be a contract. The token server system can facilitate the modification of documents from other parties. The modification may represent a counter-offer or negotiation process.

Description

(Cross-reference of related applications)
The present application is referred to as "Blockchain-Powered Industry-Agnotic, One-Stop Deal and Service Market, and New Demand-Driven and Integrated, Applied on the 20th month of the year, 20th month of the year, 12th year of the application, and the 10th year of the application. Claims the interests of US Provisional Patent Application No. 62 / 777,520 incorporated herein as.

This area generally provides more sophisticated and immediate negotiation of document tokenization and modification using blockchain technology, their applications, marketplaces and e-commerce websites for creating, delivering, distributing and working with sensitive documents. And those applications for extending into transaction decision-making, those applications for migrating supply-driven marketplace models to demand-driven marketplace models, and, for example, real estate, automobiles, digital assets, tangible assets, Or related to those applications for generating ubiquitous marketplaces, e-commerce, or commercial trading platforms for other goods and services.

When individuals, businesses, and governments interact, the parties often exchange many documents for interaction. These documents may contain written requests or may be contractual obligations. For example, the exchange of offers or invitations to negotiate may initiate the process of executing a transaction, such as the purchase of a property, goods, or service. The parties may also exchange documents during the negotiation process. For example, the parties may exchange amendments to the agreement or contract. These fixes may be emailed along with the tracked changes.

However, during negotiations, the parties may exchange many versions of the document with complex amendments. Tracking changes can be difficult to manage. In addition, the negotiation process is further complicated in situations where a particular transaction involves multiple parties. Encrypting and preserving the true record of modifications that may be relied upon by a party to represent the party's true desires and contractual position can also be difficult using insecure techniques such as email. ..

Lack of auditable real-time bargaining and immediate contracting capabilities can constrain many marketplaces and e-commerce websites within the realm of buying and selling relatively low-value products, or marketplaces can offer. Constrain products / services. Immediate trading of goods and services through complex contract structures is difficult to achieve in traditional marketplaces.

Moreover, buying and selling goods and services online is generally confined to the marketplace or electronic trading platform, largely due to trust issues and technical limitations. This method not only requires marketplace participants, such as suppliers or consumers, to go through several setup steps, but also buys their own products or participates in the marketplace with the services they need. Does not provide marketplace participants with the flexibility to target audiences that marketplace participants consider likely to offer to others. In countries and regions where online marketplaces are limited, traders from those developing markets can be significantly disadvantaged.

In addition, general marketplace transactions limit inventory to those listed by the seller. For example, a typical online transaction begins with an online retailer listing items for purchase. Similarly, an individual listing a real estate property may list the availability of the property for purchase or rent. Initiating a transaction on a list from a seller limits the inventory of goods, services, and / or real estate to those listed for sale. In addition, traditional online retailers typically connect businesses to consumers, allowing them to buy from businesses. This inflexible model prevents transactions from different parties with different roles. For example, these approaches do not facilitate business-to-business or consumer store transactions.

The list model used in the real estate industry also prevents buyers from submitting offers and opening transactions on their own. The list model accounts for only about 2% of the real estate market, excluding most of the market. In addition, these real estate transactions typically require face-to-face interaction between the parties and a large amount of paperwork. The lack of technical ability to carry out legally binding property purchases, leases and rentals in a fast and reliable manner further complicates the process. Users also face data security issues and concerns that sensitive personal data can be hacked, mined and collected. The lack of security books can discourage buyers and lessees from making online offers and discourage sellers from disclosing relevant information. Thus, buyers and sellers may lack the ability and willingness to offer online offers.

Moreover, since real estate transactions may be infrequent for buyers and sellers, buyers and sellers may rely heavily on real estate agents and professionals and be forced to use them. In some cases, agents may negotiate with offers and counter-offers without transparency and auditing capabilities for buyers and sellers. Buyers and sellers do not have an overview of the trading system. For example, without talking to an agent, potential buyers may not be able to easily track the status of offers, while sellers may not be able to easily track the offers they receive. be. Similar problems can arise during the rental property application process.

Disclosed herein are systems, devices, devices, methods, and / or computer program product embodiments for managing documents using blockchain technology, and / or combinations and secondary thereof. It is a combination.

In certain embodiments, the token server system may use document tokens, digital wallets, and blockchain to facilitate and manage documents and document modifications. The token server system may generate document tokens that represent digital document ownership and / or document modification permission. The token server system may distribute the document token to the digital wallet specified by the document owner. The token server system may also encrypt the document, store the encrypted version of the document, generate a hash of the document, and create a link to the encrypted version of the document. The token server system may then store hashes and links on the blockchain using one or more smart contract features. The token server system may also consume processing tokens and / or cryptocurrencies to perform blockchain operations.

The token server system may also perform similar actions to manage document modifications. For example, a party who has permission to modify the original document may, for example, insert, erase, and / or modify the text as facilitated by the graphical user interface generated by the token server system. Modifications may be made. The token server system may then generate a separate document token corresponding to this modified document. The token server system may perform actions similar to the modified document, such as encrypting, hashing, and generating a link to the modified document. The token server system may also expose the hash of this modified document and a link to its encrypted version to the blockchain to preserve the modification. The token server system may also modify the document token and distribute it to the owner of the original document. In this way, publishing to the blockchain can provide confidence that the fix is preserved, the fix is intended, and there is no interference. The token server system provides each party with a graphical user interface to view and / or modify these documents in a human-readable format, even while using the blockchain integrity system. May be good.

In some embodiments, a computer implementation method for managing documents using the blockchain may be used by the token server system. The token server system may receive a document creation request from a user account corresponding to the digital wallet. The token server system may facilitate the creation of the document, encrypt the document, and store the encrypted version of the document. The token server system may create a link to an encrypted version of the document and generate a cryptographic hash of the document. The token server system may also generate a document token corresponding to the document and transmit the document token to the digital wallet. The token server system may expose links and cryptographic hashes to the blockchain using one or more smart contract features.

In some embodiments, a computer implementation method for providing graphical user interface icons for generating documents may be used by the token server system. The token server system may generate a graphical user interface (GUI) that includes a first icon used to initiate the link generation process. The first icon may be a document action button, such as the "offer immediately" button, as described further below. In response to receiving an interaction with the first icon, the token server system may generate an interface for attaching one or more documents to a link. This linking can be referred to as a "1-Link" process as further described below. The token server system may receive an indication to attach one or more documents to a link via a GUI and generate a document token for each of the one or more documents. Document tokens may be deposited in a digital wallet that indicates the ownership of each of the one or more documents. The token server system may expose a blockchain link to one or more documents to the blockchain and generate a message corresponding to the link. The message may include a blockchain link and a second icon used to initiate the document generation process.

In some embodiments, a computer implementation method for managing documents generated from different account types may be used by the token server system. For example, different account types may represent a demand-driven value chain for transactions. The token server system may receive a document creation request from a first account corresponding to the first digital wallet, the first account corresponding to the first account type. The token server system may facilitate the creation of a first document and create a document token corresponding to the first document. The token server system transmits the document token to the first digital wallet and uses one or more smart contract functions to blockchain the hash of the first document and the link to the encrypted version of the first document. You may publish it to. The token server system may then transmit the notification to a second account corresponding to the second digital wallet, the second account corresponding to a second account type different from the first account type. The token server system may then facilitate the creation of a second document by the second account.

Various embodiments can use these technical features, for example, to achieve improvements in the real estate industry. The token server system may generate GUI elements such as an "offer immediately" button, which may be used to generate a protected real estate offer on the blockchain. Other document action buttons, such as the words "Lease Now", "Rent Now", "Apply Now", and / or "Buy Now", are also used to generate real estate offers. May be done. Sellers also have document action buttons such as the "List Now" and / or "Manage Now" buttons to create a list and / or offer document for offering properties for sale or rent. May be used. The token server system may facilitate a streamlined document generation process, also preserve the hash of the document generated using the blockchain, and maintain confidentiality while taking advantage of the immutability of the blockchain. You may.

The token server system may be used to manage real estate documents in this way using the blockchain as well. For example, the token server system may manage offers, counter-offers, and / or other negotiated modifications of the contract document. The token server system may use the blockchain to preserve these document modifications. In addition, the token server system may preserve other documents related to real estate transactions, such as loan approvals, inspection reports, real estate titles, contracts, agreements, and / or other real estate documents. This management may track the progress and / or execution of real estate transactions and the documents used in the transaction.

Along with document management, the token server system also provides a "1-Link" process, either independently of its graphical user interface (GUI) or as part of another workflow, link management and /. Alternatively, a document distribution may be provided. The link may represent a document that is preserved by the blockchain and may further provide access to other documents preserved by the blockchain. For example, a user may generate a link to an offer document to provide an offer to purchase real estate. The link may be a document that includes a link to another document, such as a loan approval document. The user may then transmit the link as an offer to the property owner. In some embodiments, the link may correspond to an embedded e-mail message such that the e-mail message contains a link to another message. Thus, the 1-Link process may provide a streamlined document transmission process facilitated by the token server system.

The token server system may also use the technical features described in this disclosure to provide a demand-driven value chain. Demand-driven value chains can allow parties with a certain demand to generate documents in industries that traditionally utilize supply-driven trading marketplaces. For example, the buyer may generate an offer and / or an offer document, the seller may generate a sales document, and / or the buyer's agent may generate an offer document on behalf of its client. good. For example, a traditional online retailer may list items and receive purchase orders from buyers. In a demand-driven value chain, a buyer may submit an offer for goods, services, and / or real estate, even if the seller does not provide the list. In this way, the token server system may facilitate offers, counter-offers, and / or negotiations between the parties, regardless of role or account type. Buyers and / or sellers may initiate transactions. In addition, different parties and / or account types such as businesses, stores, entities, and / or consumers may use demand-driven value chains to initiate and / or facilitate transactions using blockchain integrity. good. In this way, the token server system may use the blockchain to support a decentralized marketplace for transactions.

The accompanying drawings are incorporated herein and form part of this specification.

FIG. 1 depicts a block diagram of a document management environment according to some embodiments.

FIG. 2 depicts a flow chart illustrating a method for publishing a document to the blockchain, according to some embodiments.

FIG. 3A depicts a flow chart illustrating a method for dividing a document permit, according to some embodiments.

FIG. 3B depicts a flow chart illustrating a method for specifying confidentiality settings for a document, according to some embodiments.

FIG. 4 depicts a flow chart illustrating a method for modifying a document, according to some embodiments.

FIG. 5 depicts a flow chart illustrating a method for document negotiation according to some embodiments.

FIG. 6 depicts a flow chart illustrating a method for generating a graphical user interface for document negotiation, according to some embodiments.

FIG. 7 depicts a block diagram of a graphical user interface, including segmented document portions, according to some embodiments.

FIG. 8A shows, according to some embodiments, the words "offer immediately", "lease immediately", "borrow immediately", "apply immediately", "buy immediately", "list immediately". , And / or draw a block diagram of the graphical user interface, including a document action button that can display "Manage Now".

FIG. 8B depicts a block diagram of a graphical user interface for link management and generation of 1-Link processes, according to some embodiments.

FIG. 8C depicts a block diagram of a graphical user interface of a message including a document action button and a document link, according to some embodiments.

FIG. 9 illustrates a flow chart illustrating a method for generating a message including a document action button and a document link, according to some embodiments.

FIG. 10 depicts a block diagram of a document chain environment that provides a demand-driven value chain, according to some embodiments.

FIG. 11A depicts a flow chart illustrating a method for role-based document generation, according to some embodiments.

FIG. 11B illustrates a flow chart illustrating a method for demand matching according to some embodiments.

FIG. 12 illustrates an exemplary computer system useful for implementing various embodiments.

In the drawings, similar reference numbers generally indicate the same or similar elements. In addition, in general, the leftmost digit of the reference number identifies the drawing in which the reference number first appears.

What is provided herein is a system, device, device, method, and / or computer program product embodiment for managing documents using blockchain technology, and / or combinations and secondary thereof. It is a combination. An embodiment disclosed herein provides a front-end user interface while managing documents using a connected, associated, or related back-end system that is interfaced with the blockchain. May facilitate document generation. The front end allows users to view documents that are linked onto the blockchain in a human-readable manner, managing document creation, managing permissions for documents, managing document modifications from different parties, and / or human-readable. It may be a user interface such as a graphical user interface (GUI) that enables this.

The backend may manage documents using the document token process and blockchain interface. Document tokens may be used to represent ownership and / or permission corresponding to a document, as described further below. Document tokens may also be used to track document modifications and / or segment permissions for different parts of a document. In addition, document tokens may be generated for each modified document version. These document tokens may represent ownership of the modification or may be used in conjunction with the blockchain to provide evidence of the document modification. For example, on either the public or private blockchain, modifications may be tracked as updated blocks and / or code running on the blockchain using smart contract features.

Publishing to the blockchain can provide confidence that security and modifications are immutable. In addition, distributed ledger technology may provide a streamlined format for tracking corrections and presenting these corrections to the parties communicating and / or editing the document. As will be further described below, the embodiments described herein further provide faster and more efficient backend processing for blockchain operation. In particular, the use of asynchronous calls to the blockchain can provide increased speed and avoid delays associated with blockchain transaction time.

The embodiments described herein may also be used in contract negotiations to provide a streamlined contract platform for tracking and viewing offers and counter-offers. For example, a user may generate an offer to purchase goods, services, properties, insurance, and / or other contractual obligations. These offers may be documented. The system described below may facilitate the generation of these offers and publish these offers to the blockchain. Blockchain immutability can preserve these offers. In addition, the use of encryption can maintain the confidentiality of sensitive information when making these offers. By managing these offer documents using the blockchain, the parties to the contract may present offers that can be relied upon by other parties in a more trusted manner.

In addition, counter-offers may be managed in a similar fashion. For example, the counter-offer may be a modified offer that can be represented as a document with a corresponding document token. These counter-offers may also be managed using the blockchain in a similar fashion. By managing offers and counter-offers, the document platform may streamline the negotiating process of maintaining confidentiality while maintaining a high degree of trust. Parties using the document platform may provide a digital signature to negotiate the terms of the contract and / or to represent acceptance of the offer. In this way, the document platform may facilitate the execution of the contract. In some embodiments, the negotiations and executions may be conducted in a decentralized manner and / or provide a decentralized marketplace for peer-to-peer transactions.

The document action button and / or 1-Link process may also be implemented using the system described below to streamline the document generation, document delivery, and document distribution processes. In some embodiments, this rationalization may be particularly useful in documents preserved using the blockchain. "Offer Immediately", "Lease Immediately", "Rent Immediately", "Apply Immediately", "Buy Immediately", "List Immediately", and / or "Manage Immediately" Buttons Document action buttons such as, etc. may allow the user to quickly generate a document with less GUI interaction. Reducing interactions can help reduce wasted computer resources or unnecessary web navigation. In addition, document action buttons may help reduce network traffic due to the reduced number of interactions. Similarly, the 1-Link process may deliver blockchain maintenance documents in a similar compact format. The user accessing the link may access various blockchain maintenance documents and / or generate another document using the document action button. Thus, the 1-Link process can also reduce network traffic while reducing the number of user interactions and computer transactions.

Various embodiments of these features will be discussed here with respect to the corresponding figures.

FIG. 1 depicts a block diagram of a document management environment 100 according to some embodiments. The document management environment 100 may include a token server system 110, a blockchain 120, a user interface 130, and / or a user device 140. The token server system 110 may include one or more servers and / or databases capable of instantiating user interfaces 130A-130B for user devices 140A-140B. The token server system 110 may include object storage, a web service interface, storage for internet applications, and / or cloud computing and / or storage. In some embodiments, the token server system 110 may use peer-to-peer networks and / or protocols for storing and / or sharing data in a distributed file system. For example, the token server system 110 may use content addressing to uniquely identify files in the global namespace to network user devices 140. In some embodiments, the token server system 110 may use the InterPlanetary File System (IPFS) protocol and / or server, such as Amazon S3 (R).

The token server system 110 may include an interface with the blockchain 120. The blockchain 120 may be a private or public blockchain. The token server system 110 may use one or more smart contract functions to interface and / or expose data to the blockchain 120. Smart contract features may include protocols for digitally facilitating, validating, and / or enforcing transactions. The transaction may be traceable and irreversible. As will be further described below, the token server system 110 may interface with the blockchain 120 to store documents and / or data representing modifications of the documents. The data may include cryptographic hashes of the document and / or links to human-readable representations of the document.

In some embodiments, the token server system 110 may also manage the processing tokens used to interact with the blockchain 120. For example, the token server system 110 may manage digital wallet information related to cryptocurrencies. The token server system 110 may use and / or consume digital currency to execute transactions on the blockchain 120. For example, the token server system 110 is also used to execute transactions, execute blockchain contracts, and / or publish data on the blockchain 120 in blocks, gas, transactions, and / or mining charges. May be managed. As described further below, the token server system 110 may also manage document tokens that may represent ownership and / or permission for documents and / or document modifications. The token server system 110 may facilitate the disclosure of document data to the blockchain 120 and / or may remove the processing token from the account corresponding to the digital wallet to perform the disclosure.

The token server system 110 may provide a front-end user interface 130 to allow users to create, manage, edit, and / or modify documents. The user interface 130 may be a graphical user interface (GUI) that can be accessed and / or displayed on the user device 140. The user device 140 may be a computer, laptop, tablet, telephone, and / or other device capable of accessing the Internet and / or displaying the user interface 130. The user interface 130 may include an application programming interface (API) to provide communication between the user device 140 and the token server system 110.

As described further below, the token server system 110 allows the user to create a document, modify the document, manage document permissions, generate links and / or messages corresponding to the document. A front-end GUI that contains GUI elements that manage document modifications from other parties, manage digital wallets, manage user account information and / or account roles, and / or enable other document interactions. May be provided. In some embodiments, the token server system 110 facilitates the incorporation of GUI elements into a web page that is not managed by the token server system 110, allowing the user to access the actions provided by the token server system 110. May be possible. For example, the token server system 110 may provide web widgets that can be integrated, integrated, or overlaid on other web pages to provide similar document functionality.

For example, the token server system 110 may generate icons and / or buttons that allow the user to create a document. The user may interact with the icon or button via selection, pressing, or clicking on the GUI. In response to this interaction, the token server system 110 may generate a document creation GUI element to be displayed on the GUI. The document creation GUI element may be a fillable form and / or may include an editable text box. In some embodiments, the document creation GUI element may include an option to attach a locally stored data file on the user device 140. The token server system 110 may allow the generation of documents that can be encrypted and / or stored on the blockchain 120.

In certain embodiments, the token server system 110 may provide a GUI element that allows the user to create an offer document and initiate a contract negotiation process. For example, the GUI element may be a button that displays the text "offer immediately" on a web page. Users may browse web pages displaying different products, services, properties, insurance, and / or other contractual obligations, and may interact with buttons to generate and submit offer documents. .. The offer document may be a fillable form that may allow the user to enter personal information and / or information such as an offer to purchase the property. The user may also specify terms and / or obligations and generate a contract document for the property owner. The token server system 110 may distribute the offer document to the property owner and notify the owner of the pending offer. For example, the token server system 110 may provide notifications via email or via push notifications to the user device 140 corresponding to the user account associated with the owner.

The token server system 110 may use the blockchain 120 to manage and / or store offer documents. As will be further explained below, the token server system 110 may store the encrypted version of the offer document and / or create a link to the encrypted version of the document. The token server system 110 may also generate a cryptographic hash of the document. Using this information along with other information such as owner identification and / or other metadata, the token server system 110 may create a document token corresponding to the offer document. Document tokens may represent ownership of the offer document and / or may be transmitted to the digital wallet corresponding to the offering party. The token server system 110 may use the document token in future operations to determine access and / or modification permissions. In some embodiments, the token server system 110 transmits a document token to the seller's party's digital wallet to allow the seller's party to access and / or modify the document. May be good. For example, a document token may indicate that the seller's party may modify the document using a digital signature to accept the contract offer.

The token server system 110 may use the blockchain 120 to manage offer documents. For example, the token server system 110 may use the smart contract function to expose a cryptographic hash of the document and / or a link to an encrypted version of the document. The document may be encrypted using the key corresponding to the seller's party. Publishing document data on the blockchain 120 may preserve the credibility of the document and the legitimacy of the offer and / or content. For example, the immutable quality of blockchain 120 can be protected from unauthorized document modification or tampering. In addition, cryptographic hashes can protect privacy and prevent other users of the blockchain 120 from viewing sensitive information. For example, the user device 140C may use a separate user interface 130C to access the blockchain 120, separate from the token server system 110. Encryption can prevent the user device 140C from viewing sensitive information stored on the blockchain 120.

In response to delivering a notification of the offer document to the seller's party, the seller's party may use the user device 140 and the corresponding user interface 130 to access the offer document and access the token server system 110. good. In particular, the token server system 110 may ensure that the digital wallet corresponding to the seller's party includes the document token corresponding to the offer document. The token server system 110 may also identify permissions corresponding to this document token, such as permissions to view, access, and / or modify the offer document. The token server system 110 may further verify that the offer document has not been modified by verifying the cryptographic hash stored on the blockchain 120. The token server system 110 may also provide the seller's party with a link to an encrypted version of the offer document. The seller's party or token server system 110 may then use the digital signature key corresponding to the seller's party to decrypt the encrypted document. If the seller's party accepts the offer presented in the offer document, the seller's party may provide a digital signature to confirm acceptance. The Digital Signature may also be keyed to the seller's parties to provide verification and additional credibility that the signature is legitimate and protected from interference or tampering. In some embodiments, the digital signature may also be reflected in the human readable portion of the offer document.

In certain embodiments, the digital signature may be a modification of the offer document. The token server system 110 may manage the modification in a manner similar to generating the document so that the modified document can be preserved using the blockchain 120. For example, the signed document may be encrypted and stored as a modified version of the offer document. The token server system 110 may generate a corresponding link to this encrypted version of the signed document and / or generate a cryptographic hash of the signed document. The token server system 110 may create a document token corresponding to the signed document and may transmit the document token to a digital wallet corresponding to the seller's party and / or the offering party. The token server system 110 may expose a hash of the signed document and / or a link to an encrypted version thereof to the blockchain 120. Similarly, encryption may be performed using the key corresponding to the offering party to maintain confidentiality. In this way, the token server system 110 may use a document management process that uses the blockchain 120 to facilitate the offer and acceptance of contracts.

Similar to the offer and acceptance process, the token server system 110 may manage the negotiation process through document modification. The negotiation process may include one or more rounds of offers and counter-offers. The parties may use the token server system 110 to negotiate digitally and modify different parts of the document. For example, the parties may negotiate different contractual terms and / or obligations. The token server system 110 may use a tokenization process to manage different parts of the document and / or manage counter offers.

For example, the seller's party may receive an offer document from the offering party. The seller's parties may not agree to one or more contractual terms provided in the offer document, such as the offer price for purchasing the property. In this case, the seller's party may make modifications to the offer document via user interface 130. The seller's parties may modify the text of the offer document. In some embodiments, the seller's party may modify the fillable form elements to modify the offer document.

The token server system 110 may manage the modification in a manner similar to generating the document so that the modified document can be preserved using the blockchain 120. The modified document may be encrypted and stored as a modified version of the offer document. The token server system 110 may generate a corresponding link to this encrypted version of the modified document and / or generate a cryptographic hash of the modified document. The token server system 110 may create a document token corresponding to the modified document and may transmit the document token to a digital wallet corresponding to the seller's party and / or the offering party. The token server system 110 may expose a hash of the modified document and / or a link to an encrypted version thereof to the blockchain 120. Similarly, encryption may be performed using the key corresponding to the offering party to maintain confidentiality. In this way, the token server system 110 may use a document management process that uses the blockchain 120 to facilitate contract negotiations. The token server system 110 may further continue to manage additional modifications and / or counter offers from either party in this way.

In some embodiments, the token server system 110 may preserve negotiations and / or counter-offers locally prior to publishing the document to the blockchain 120. For example, if publishing a document on the blockchain 120 can consume digital currency or gas, the parties negotiate and / or make counter offers using local or accessible memory to the token server system 110. You may choose that. The token server system 110 may publish the agreed document to the blockchain 120 once the negotiations and document modifications have been completed. For example, the token server system 110 may identify a digital signature indicating a matching clause and / or acceptance prior to publishing the document to the blockchain 120.

Although the token server system 110 has been described as managing offer documents from the offering party to the seller's party, the token server system 110 may also manage document transmission from different contractual roles. For example, the seller's party may generate an offer document to the buyer's party. The buyer's party may in this case accept the offer and / or offer the opposite offer. Similarly, the parties may use the token server system 110 and the blockchain 120 to negotiate services and / or other contract exchanges. The document management provided by the token server system 110 may provide confidentiality in the document exchange and credibility in the immutability of the blockchain 120 to represent the position of the parties. Similarly, the token server system 110 may be used to manage documents such as rental contracts, lease contracts, real estate documents, auctions, and / or other documents.

The document management process used by the token server system 110 may also facilitate multi-party document exchange, negotiation, and / or transactions, as described further below. For example, in a real estate transaction, in addition to the buyer and seller, other parties such as the buyer's agent, seller's agent, lawyer, mortgage lender, and / or other parties may be involved in the transaction. The token server system 110 may manage these different account roles and / or may provide permissions to different users depending on their role in the transaction. For example, a mortgage lender may be required to provide evidence that the buyer is eligible to borrow a certain amount and / or is approved for it. The mortgage lender may provide this document to the token server system 110. In some embodiments, the token server system 110 may provide the mortgage lender with a form that may be a modifiable document, which may include information such as a qualifying amount. .. Using the digital signature of the mortgage lender, this document may be validated and / or stored on the blockchain 120. In addition, the buyer may be able to use this document in more than one transaction if the buyer has submitted multiple offers to different sellers.

In some embodiments, the master document may be compiled and different parts may be assigned to different roles in the transaction. For example, a mortgage lender may be assigned to modify a portion of the master document, while a seller's agent may be assigned to modify a different portion. The token server system 110 may manage and / or control these modifications to ensure that the corresponding role implements those specified modifications without tampering with other individuals. good. In addition, these modifications may be preserved on the blockchain 120. In this way, the parties may be responsible for modifications that may correlate with a particular account and / or account role that is trusted and supplies document modifications.

The token server system 110 may manage various levels of confidentiality associated with the document. For example, the user who generates the document may specify the document as open, semi-secret, or secret. This designation may be stored as metadata corresponding to the document. For example, the confidentiality designation may be a visibility flag. In some embodiments, the confidentiality designation may correspond to a list of real estate for goods, services, and / or for sale. For example, the confidentiality designation may correspond to a list of real estate properties for sale or lease. Confidentiality may facilitate the decision of the real estate owner to list the property using documents that can be preserved by the blockchain 120, taking into account the offer in secret. For example, a celebrity may not want to openly list properties and / or list property identification information, but may still want to consider potential offers. Based on the confidentiality designation by the user, the token server system 110 may expose the list document to the desired agent, buyer, and / or borrower. For example, the token server system 110 may transmit a document token to the user with the corresponding permission to interact with the list document, as described further below.

In some embodiments, the token server system 110 may manage these lists to help match the parties to the lists. For example, the "open" designation may indicate that the list document may be openly available for matching by the token server system 110. The "open" designation may allow public access and / or browsing of the list. The buyer or borrower may transmit the offer request and / or the offer document to the token server system 110, which may attempt to match the request with the list document. For example, the buyer may indicate a particular price, geographical area, residential specifications such as bedrooms and bathrooms, and / or other requirements for the property. The token server system 110 may provide the buyer with an "open" list document if the identified conditions for the list are met and / or matched by the price and / or requirements offered by the buyer.

The "semi-secret" designation may indicate that the list document may be exposed when the buyer and / or borrower submits the offer and the token server system 110 identifies that the list document corresponds to the offer. Unlike "open" documents, "semi-secret" documents may not be searchable. In some embodiments, the "semi-secret" document may only be searchable by certain fields, for example, the exact address is kept confidential, but the postcode is searchable. A "semi-secret" document may contain additional conditions prior to being exposed to the user. For example, a "semi-secret" list document may include price terms. The token server system 110 may expose the list document if the buyer offers a sufficient offer price. Similarly, the user may designate the list document as "semi-secret" and only available to certain individuals, such as certain agents. For buyers offering requests and / or offers with different terms, the token server system 110 may facilitate a demand-driven value chain, as further described below.

The "secret" designation may indicate that the token server system 110 may expose the list document after the real estate property owner evaluates the request or offer and provides affirmative confirmation to expose the list document. This "Confidential" designation may indicate a confidentiality request that may include input from the listed parties prior to providing the identifying information to the offering party. Using these designations, the token server system 110 may manage the confidentiality associated with the list documents posted on the blockchain 120, while still facilitating the integrity of the list documents. The added confidentiality may also allow additional participation in the listed property.

In addition to the list document, the token server system 110 may facilitate the creation of a contract document. To illustrate an exemplary embodiment, a user, Ted, may wish to use the token server system 110 to sell a home. Ted may use the token server system 110 to create a contract document. Ted may also have a real estate agent to help sell a home. Ted may provide user information to the token server system 110 for the real estate agent and provide the agent with the right to manage part of the contract document. The agent may then provide a link to the potential buyer to search for the buyer and / or provide the buyer with access to the contract document. The buyer accessing the link may have the token server system 110 make a copy of the contract document containing the buyer's rights and obligations.

In some cases, the buyer may not agree to the terms in the contract document and may initiate the negotiation process. For example, the buyer may edit the text of the contract document, such as rights and obligations and / or final price. The buyer may leave a comment on certain terms of the contract document. The negotiation process may be managed and / or carried out by the agent, depending on the permissions granted to the agent. In some embodiments, the seller and / or agent may negotiate with multiple buyers at the same time. The negotiation process may continue until the terms and / or contents of the contract document match the seller and buyer. Ted may choose the buyer to carry out the contract document by viewing the counter-offer and / or providing a digital signature for the agreementable contract document amendment. Ted may store a copy of the contract document from the token server system 110 locally on the user device 140. For example, this copy may be a PDF document. Ted may also use the blockchain explorer to access the blockchain 120 and view transaction information as preserved by the token server system 110.

A company or entity may use the token server system 110 to manage documents. For example, John may create a workflow that can be the owner of a company and can specify departments and / or account roles that correspond to company employees. Employees may use the token server system 110 to generate documents, edit documents, transmit documents to external parties, and / or negotiate with these external parties. External parties can be external individuals, suppliers, contractors, and / or other parties outside John's company. Using the token server system 110 and the blockchain 120, John may verify the authenticity of documents created by employees and / or received from outside parties.

The token server system 110 may manage multi-party contracts. For example, the token server system 110 may manage one-to-many, many-to-one, and / or many-to-many multi-party contracts. In an exemplary embodiment, the user Sam may wish to enter into a contract as the owner. Sam may use the token server system 110 to create a set of contract documents intended for negotiation. Sam may specify a portion of each contract document whose terms may change. These parts may represent fields in the contract document.

Sam may be an employee working for a company with a Treasury Department or a Treasurer. Sam may transmit the set of contract documents to a sub-accountant who can scrutinize, sign, and / or edit the contract documents. The sub-accountant may return the contract document to Sam for further editing. If the sub-accountant signs the contract document, the token server system 110 may generate a notification, such as an email, to Sam. Sam may then use the token server system 110 to transmit one or more links to the contract document to one or more other parties. These parties can be outside the company.

The other party may create a counteroffering offer that may include a set of variable fields. For example, the other party may choose to edit the terms of the contract document and / or not. If the values of the fields are separated, the negotiation process may be initiated to be managed by the token server system 110. The owner and / or the other party of the contract document may continue to modify the value of the field. At each modification, the other party may receive a notification from the token server system 110 and / or accept or reject the offer. The contract document may be agreed through acceptance from the parties and / or that each field contains the same value from each party. The parties may apply the digital signature to the contract document to terminate their contractual obligations.

In some embodiments, Sam may utilize different versions of the contract document for different parties. The token server system 110 may provide a GUI for Sam to manage these different contract documents and / or links corresponding to the contract documents. If the other party agrees to those corresponding provisions as provided by Sam, Sam may sign and / or complete the negotiation process with that other party.

The token server system 110 may also manage documents and / or contract document templates. Law firms may create these templates. The token server system 110 may provide these templates for purchase and use by the user. These templates may include rental and / or lease documents. For example, Sara may want to rent her own apartment. She may use the token server system 110 to identify a standard rental agreement document template. Sara may purchase the template using digital currency and / or using processing tokens, which will be further described below. Sara may edit some of the conditions listed in the template. The token server system 110 may generate links that provide access to rental agreement documents and / or other information provided by Sara about the apartment. Three potential tenants may access the link to respond to the document created by Sara. Sara may communicate with each of them and may terminate and execute a contract with one of them using the digital signature provided to the token server system 110.

The token server system 110 may provide a template contract or document, but the token server system 110 may also collect statistics related to template modifications. For example, the token server system 110 may identify modification trends. Law firms may analyze these statistics to identify frequently used contracts and / or amendments. For example, many users may modify certain paragraphs in a rental agreement. The law firm may modify the template to improve the usability of the template.

The token server system 110 may manage documents other than contract documents. For example, James may wish to use a single electronic medical card that may contain medical records and / or insurance information. James may create a medical card from the template provided by the token server system 110. When James visits a doctor, James may give the doctor access to a portion of the card. For example, James may provide the physician with permission to modify the medical record portion of the medical card document. Using the link provided by the token server system 110, the physician may enter new data into the medical history and / or provide the prescription via modification of the document. Physicians may also provide a uniquely identifiable digital signature for modification that can be preserved using the blockchain 120. At the pharmacy, James may present a signed prescription, which the pharmacist may verify using the token server system 110 and / or the blockchain 120. In this way, James can avoid the problem of losing or damaging the physical medical card. The token server system 110 may provide a reliable document management service in which modifications can be recorded on the blockchain 120.

The token server system 110 may manage and / or preserve copyright information and / or other date-sensitive documents. For example, Alice may have written a scientific treatise. To preserve its copyright, Alice uses the token server system 110 and the blockchain 120 to preserve the documents. Based on the invariant nature of blockchain 120, Alice may rely on blockchain 120 to confirm the date and time of copyright and / or as evidence.

In some embodiments, the token server system 110 may manage documents associated with records and / or certificates. For example, the user may use the token server system 110 and use the blockchain 120 to manage and / or preserve documents. These documents may include certificates such as birth certificates, marriage certificates, driver's licenses, college degrees, and / or other documents that the user may consider official. Conservation on the blockchain 120 can indicate that the document is genuine. For example, a university, government agency, and / or other body may use the blockchain 120 associated with a user to verify the authenticity of a document and / or that a particular certificate was actually issued by that group. Documents may be preserved on top. The token server system 110 may manage the document tokens associated with these certificates and / or transmit the document tokens to the digital wallet corresponding to the user. A user may be able to use the token server system 110 to track, view, and / or manage documents throughout his or her life. The token server system 110 may provide a repository for these documents while maintaining confidentiality and providing verifiable evidence of authenticity.

Other functions and / or operations of the token server system 110 will be described herein further with reference to the other figures of the present disclosure.

FIG. 2 illustrates a flow chart illustrating a method 200 for publishing a document to the blockchain 120, according to some embodiments. The method 200 will be described with reference to FIG. 1, however, the method 200 is not limited to its exemplary embodiments.

In certain embodiments, the token server system 110 may facilitate document generation and document integrity on the blockchain 120. Method 200 is described with reference to the token server system 110, where method 200 is described, for example, in a computer system and / or hardware (eg, circuit, dedicated logic, programmable logic, etc.) described with reference to FIG. It may be executed on any computing device, such as microcode), software (eg, instructions executed on a processing device), or processing logic that may include a combination thereof.

It should be understood that not all steps may be required to implement the disclosure provided herein. In addition, some of the steps may be performed simultaneously or in a different order than those shown in FIG. 2, as will be appreciated by those skilled in the art.

At 205, the token server system 110 may receive a document creation request from a user account corresponding to the digital wallet. The token server system 110 may interface with the user device 140 via the user interface 130 to receive the document creation request. For example, the token server system 110 may provide a graphical user interface (GUI) that should be displayed on the user device 140. The user device 140 may interact with the GUI via API interactions. In some embodiments, the token server system 110 may manage user accounts and / or user profiles. The user may log in to the token server system 110 to generate a document creation request. The token server system 110 may manage the digital wallet information corresponding to the user account. The digital wallet may represent a crypto wallet and / or may include a corresponding cryptocurrency balance.

In some embodiments, the document creation request may begin with an interaction with a web widget on a web page. For example, a website may include widgets that can trigger the token server system 110 to facilitate the creation of documents. In some embodiments, a website listing real estate information may include the widget, allowing the user to generate an offer document to purchase the property. If the widget is implemented within a web page, document creation may require digital wallet information to provide electronic transactions. The widget may be a document action button, as described further below. Widgets and / or action buttons may be located on web pages that are not managed by the token server system 110. For example, a website may be managed by a third party system and / or an administrator, while the token server system 110 may facilitate document creation in response to the user interacting with the widget. The widget may be a plugin for a website.

At 210, the token server system 110 may facilitate the creation of documents. The token server system 110 may generate GUI elements that should be displayed on the user device 140 to allow the user to generate the document. For example, the GUI element may be a fillable form that allows the user to enter text input. In some embodiments, the fillable form may include a field indicating the requested text data. The user may enter text data to specify the content of the document. The GUI element may be a pop-up template or form on a web page currently being viewed on user device 140. The GUI element may prompt the user to provide information such as, for example, digital wallet information and / or information for providing an offer to another party. The user may provide it with the identification of other parties with whom the document should be communicated.

In some embodiments, the user may be browsing the property list and / or may be considering purchasing an item or item on a web page. The seller of the property may provide some initial identification information to list the property for sale. Depending on how it interacts with the GUI element, the token server system 110 may generate a template form that allows the user to enter contract terms and generate an offer to purchase a property. .. The token server system 110 may identify the recipient of the created document based on the list and previously provided seller identification information.

The user may generate the document via typed text and / or fillable forms, but document creation may also allow the user to attach additional documents. For example, the user may include a link to a document stored in the cloud storage system so that it is contained within the generated document.

The token server system 110 may also facilitate the creation of documents by providing a library of templates of choice for the user. For example, the template may be a different contract. Templates may include non-disclosure agreements, non-disclosure agreements, lease agreements, real estate agreements, and / or other agreements. The token server system 110 may facilitate document creation by providing access to a library of templates. The user may select a template, provide additional information, and / or modify the default terms to match the intended contractual offer. In some embodiments, these templates may be provided for sale for user access. For example, a law firm may create a standardized contract document template, which may be incorporated into the library for sale and purchase by users of the system.

At 215, the token server system 110 may encrypt and / or store an encrypted version of the document. For example, the token server system 110 may encrypt a document using a digital key that corresponds to the user who produces the document and / or the user who is intended to receive the document. The token server system 110 may facilitate the distribution of keys to recipients of the document. In some embodiments, the recipient of the document may be the seller of the property listing the property for sale on a web page. Thus, the seller may have previously provided the token server system 110 with an encryption key to generate the list. The token server system 110 may use this key to encrypt a document generated by the offering party. In some embodiments, the offering party may provide an encryption key, and the token server system 110 may use the offering party's key to encrypt the document. The token server system 110 may then provide the recipient with this key to decrypt the document.

In some embodiments, the token server system 110 may store an encrypted version of the document in the database. The database may be web accessible or may be accessed using the link generated at 220. At 220, the token server system 110 may create a link to an encrypted version of the document. The link may be a uniform resource locator (URL) or another web address that identifies the storage location of the encrypted document. Since the stored document is encrypted, the discovery of the link can still remain confidential due to the encryption nature of the document.

At 225, the token server system 110 may generate a hash of the document. The hash may be a cryptographic hash of the document. The cryptographic hash may be a one-way hash function and / or may be used on the blockchain 120 to provide block verification. It may provide a decentralized configuration for the blockchain 120 using a working proof algorithm or other type of blockchain proof algorithm or methodology. The hash may also provide evidence that the document has not been tampered with and is a true representation of the document.

At 230, the token server system 110 may create a document token corresponding to the document. The document token may represent ownership of the document. In some embodiments, the token server system 110 may use the document token to segment different permissions associated with the document. The document token may be a type of digital token, cryptographic token, or virtual currency that can be used in conjunction with a digital wallet to specify ownership. However, document tokens can differ from cryptocurrencies because document tokens can be non-substitutable and instead can be unique to each created document. In some embodiments, the grant may correspond to a document-related confidentiality designation as described above. The confidentiality specification may be the metadata corresponding to the document token.

At 235, the token server system 110 may transmit or transfer the document token to the digital wallet. For example, the token server system 110 may transmit the document token to the digital wallet of the party that created and offered the document. In some embodiments, the document token may be transmitted to the party receiving the document. As will be further described below, one or more document tokens may be generated and / or distributed to segment different parts of a document with different permissions.

At 240, the token server system 110 may use one or more smart contract functions to expose a hash of the document and / or a link to an encrypted version of the document to the blockchain 120. Publishing a hash of a document and / or a link to an encrypted version of the document may indicate a version of the document that preserves the document and can be trusted as tamper-proof. Disclosure of these elements may further preserve the contractual position of the parties. In an embodiment in which method 200 is used to generate an initial offer, the token server system 110 may preserve the offer at 240 and provide credibility to the party receiving the offer. In an embodiment in which method 200 is used to preserve an agreed contract that has been negotiated offline, the token server system 110 may expose hashes and links to preserve the agreed contract.

In certain embodiments, the token server system 110 may consume processing tokens to publish the document to the blockchain 120. The processing token may be an alternative token asset that can be used as a processing fee to perform the blockchain operation. The processing token may be cryptocurrency or digital currency. In some embodiments, the processing token may be a utility token. The digital wallet may include a balance of processing tokens used to carry out blockchain 120 transactions. The token server system 110 may use processing tokens to expose the data to the blockchain 120.

To expose the data to the blockchain 120, the token server system 110 may use one or more smart contract functions. The smart contract function may include a set of computer code that runs on the blockchain 120 or on top of the blockchain 120. The smart contract function may include a set of rules agreed by the parties involved. Depending on the execution, if these predetermined sets of rules are met, the smart contract itself will be executed and produce an agreed output. Smart contract code may enable decentralized automation by facilitating, validating, and enforcing the terms of the basic agreement. The smart contract function may be an automatically executable line of code stored on the blockchain 120, including certain rules. Once the rules are met, the code may be executed by itself and provide the corresponding output. In certain embodiments, the terms of the contract document may be programmed using one or more smart contract features. In this way, the blockchain 120 may execute the contractual terms of the document.

FIG. 3A depicts a flow chart illustrating a method 300A for dividing a document permit, according to some embodiments. The method 300A shall be described with reference to FIG. 1, however, the method 300A is not limited to its exemplary embodiments.

In certain embodiments, the token server system 110 may facilitate the division of permissions on documents. The method 300A is described with reference to the token server system 110, where the method 300A is described, for example, with reference to FIG. 12 for computer systems and / or hardware (eg, circuits, dedicated logic, programmable logic, etc.). It may be executed on any computing device, such as microcode), software (eg, instructions executed on a processing device), or processing logic that may include a combination thereof.

It should be understood that not all steps may be required to implement the disclosure provided herein. In addition, some of the steps may be performed simultaneously or in a different order than those shown in FIG. 3A, as will be appreciated by those skilled in the art.

At 305, the token server system 110 may receive a request to access the encrypted document. The user may have already created the document using method 200 as described with reference to FIG. The token server system 110 may have previously provided a document token corresponding to a document to the creator of the document and / or to the recipient of the document. The token server system 110 may receive the request based on the access of the previously generated link to the encrypted version of the document.

At 310, the token server system 110 may decrypt the encrypted document in response to identifying the corresponding first document token in the first digital wallet associated with the request. For example, the first digital wallet may correspond to the owner of the document. In some embodiments, the owner of the document may grant the recipient of the document permission to modify the permission. In this case, the first digital wallet may correspond to the recipient of the document.

At 315, the token server system 110 may generate a graphical user interface (GUI) that displays the decrypted document. The token server system 110 may decrypt the document using the key provided by the owner of the first digital wallet. The GUI may display the document in a human-readable form.

At 320, the token server system 110 may identify the first portion of the document and associate the first authorization with the first portion. The first part of the document may be, for example, text parts such as the body, header information, signature blocks, and / or other parts of the document. The first permission may include read and / or write permission. These permissions may be specified based on user identity, user account type, user role, and / or other identifying information. In this way, the user may indicate that a particular part can be modified by a particular user. Similarly, the user may indicate that a particular portion may be read-only. The user may implement this designation using the GUI and / or the user interface 130. In some embodiments, the grant may correspond to a document-related confidentiality designation as described above. For example, the confidentiality designation may be an "open", "semi-secret", or "secret" designation. The confidentiality specification may be the metadata corresponding to the document token. This confidentiality designation will be further explained with reference to FIG. 3B.

At 325, the token server system 110 may identify a second part of the document and associate the second permission with the second part. The second part of the document may be different from the first part and the second permission may be different from the first permission. Thus, the owner of a document or another owner who is granted permission to specify a permit may parse the document into different categories and specify different users to interact with the different categories. In some embodiments, the second permission may correspond to a confidentiality designation.

At 330, the token server system 110 may transmit or transfer the document token to a second digital wallet and provide interaction with the first portion in accordance with the first permission. At 335, the token server system 110 may transmit or transfer the document token to a third digital wallet and provide interaction with the second portion in accordance with the second permission. In this way, different users may interact with different parts of the document based on the distributed document tokens. The tokenization may provide permissions and help divide a document into parts with different permissions. Permission can be managed by the token server system 110, while document tokens can be distributed to individuals who are granted permission to interact with the document. Tokenization may also help provide specific modification permission, such as signing authority to a particular individual. Document tokens can represent ownership and / or permission to interact with specific parts of a document, so parties trust that the modifications provided in those corresponding parts are from the appropriate parties. Can be done. In addition, the owner of the document may segment the document for use by multiple parties. For example, when multiple parties are involved in a transaction, the document owner may segment each section of the document for each party. In some embodiments, the parties may be able to view the documents, but may only modify the parts specified by their corresponding permissions.

In some embodiments, the main division of a document may correspond to a plurality of documents. For example, a document can be a large number of documents with multiple parts or divisions for different parties. Documents larger than a book may be divided into individual document parts. Document tokens corresponding to a larger number of documents may be distributed to the relevant parties.

FIG. 3B illustrates a flow chart illustrating method 300B for specifying confidentiality settings for a document, according to some embodiments. Method 300B shall be described with reference to FIG. 1, however, Method 300B is not limited to its exemplary embodiments.

In certain embodiments, the token server system 110 may facilitate the setting of confidentiality designations associated with the document. For example, the confidentiality designation may be "open," "semi-secret," or "secret." The method 300B is described with reference to the token server system 110, where the method 300B is described, for example, with reference to a computer system and / or hardware (eg, a circuit, dedicated logic, programmable logic, etc.) described with reference to FIG. It may be executed on any computing device, such as microcode), software (eg, instructions executed on a processing device), or processing logic that may include a combination thereof.

It should be understood that not all steps may be required to implement the disclosure provided herein. In addition, some of the steps may be performed simultaneously or in a different order than those shown in FIG. 3B, as will be appreciated by those skilled in the art.

At 340, the token server system 110 may receive a document creation request from a user account corresponding to the digital wallet. Receiving a document creation request may be similar to the request described in 205 with reference to FIG. At 345, the token server system 110 may facilitate the creation of the first document. The preparation of the first document may be carried out in a manner similar to 210 as described with reference to FIG. At 350, the token server system 110 may create a document token corresponding to the first document. The document token may be created in a manner similar to 230 as described with reference to FIG. At 355, the token server system 110 may transmit or transfer the document token to the digital wallet. The token server system 110 may transmit document tokens in a format similar to 235 as described with reference to FIG. At 360, the token server system 110 may use one or more smart contract functions to expose a hash of the first document and a link to an encrypted version of the first document to the blockchain. The token server system 110 may perform 215, 220, 225, and / or 240 as described with reference to FIG. 2 to implement 360.

At 365, the token server system 110 receives a confidentiality designation for the first document that indicates the conditions for exposing the first document to the requesting party or the party attempting to access the first document. May be good. As described above, the user may provide a confidentiality designation to designate a document as open, semi-secret, or secret. The token server system 110 may also allow the user to view and / or interact with the document by receiving the designation through user interaction with a graphical user interface (GUI). For example, to supply a specification, the user may use a drop-down menu and / or select a GUI element. As described above, the "open" designation may indicate that the list document may be openly available for matching by the token server system 110. The "open" designation may allow public access and / or browsing of the list. The "semi-secret" designation may indicate that the list document may be exposed when the buyer and / or borrower submits the offer and the token server system 110 identifies that the list document corresponds to the offer. Unlike "open" documents, "semi-secret" documents may not be searchable. In some embodiments, the "semi-secret" document may only be searchable by certain fields, for example, the exact address is kept confidential, but the postcode is searchable. A "semi-secret" document may contain additional conditions prior to being exposed to the user. The "secret" designation may indicate that the token server system 110 may expose the list document after the real estate property owner evaluates the request or offer and provides affirmative confirmation to expose the list document. This "Confidential" designation may indicate a confidentiality request that may include input from the listed parties prior to providing the identifying information to the offering party.

At 370, the token server system 110 may associate the confidentiality designation with the first document via document metadata. This designation may be stored as metadata corresponding to the document. For example, the confidentiality designation may be a visibility flag.

At 375, the token server system 110 may receive a second document from the requesting party satisfying the conditions. The second document may be an offer document. For example, the second document may indicate an offer to purchase goods, services, real estate properties, and / or other offers. The second document may indicate a particular price, geographical area, residential specifications such as bedrooms and bathrooms, and / or other requirements for the property. The token server system 110 receives this second document in response to the requesting party interacting with a document action button as further described below, and / or the second document. May help promote the production of.

At 380, the token server system 110 may receive the second document and expose it to the party requesting the first document in response to determining that the conditions are met. Depending on the confidentiality designation, the token server system 110 may perform a process for exposing the party requesting the first document. For example, the token server system 110 may display a first document on the GUI for viewing by the requesting party. If the confidentiality designation is "open," the token server system 110 may allow browsing of the first document and / or public access to the first document. In some embodiments, the token server system 110 may provide an "open" document to the requesting party if the conditions identified in the second document match the content from the first document. ..

A "semi-secret" designation is when the requesting party submits a second document and the token server system 110 identifies that the content of the second document meets the conditions corresponding to the first document, the first document. May be shown that can be exposed. A "semi-secret" document may contain additional conditions prior to being exposed to the user. For example, a "semi-secret" document may be a list of real estate properties that may include price terms. The token server system 110 may expose the list document if the buyer offers a sufficient offer price in the second document. Similarly, the user may designate the list document as "semi-secret" and only available to certain individuals, such as certain agents. The token server system 110 receives a requesting party status indication as a second document to provide access to the first document.

The "secret" designation allows the token server system 110 to expose the first document after the party generating the first document evaluates the second document and provides affirmative confirmation to expose the first document. It may be shown that. This "confidential" designation may indicate a confidentiality request that may include input from the party generating the first document prior to providing the identifying information to the requesting party. Using these designations, the token server system 110 may manage the confidentiality associated with the document posted on the blockchain 120 while still facilitating document integrity.

FIG. 4 depicts a flowchart illustrating method 400 for modifying a document, according to some embodiments. Method 400 shall be described with reference to FIG. 1, however, method 400 is not limited to its exemplary embodiments.

In certain embodiments, the token server system 110 may facilitate modification of previously generated documents. Method 400 is described with reference to the token server system 110, where method 400 is described, for example, with reference to computer systems and / or hardware (eg, circuits, dedicated logic, programmable logic, etc.) described with reference to FIG. It may be executed on any computing device, such as microcode), software (eg, instructions executed on a processing device), or processing logic that may include a combination thereof.

It should be understood that not all steps may be required to implement the disclosure provided herein. In addition, some of the steps may be performed simultaneously or in a different order than those shown in FIG. 4, as will be appreciated by those skilled in the art.

At 405, the token server system 110 may receive a request to access the encrypted document. Similar to 305, the request may be received from a user account accessing the encrypted document from link access and / or through a user account profile managed by the token server system 110.

At 410, the token server system 110 decrypts the encrypted document in response to identifying the corresponding first document token in the digital wallet associated with the request, where the first document token is the document. Indicates permission to modify part of. Like 310, the token server system 110 may identify the presence of a document token in the digital wallet. For example, the user may have previously received this document token. The document token may provide the user with permission to modify part of the document. For example, in embodiments where the user can sign a contract document, a portion of the document may allow the user to apply a digital signature to the signature block as a modification of the document.

At 415, the token server system 110 may generate a graphical user interface (GUI) that displays the decrypted document. The token server system 110 may decrypt the document using the key provided by the owner of the digital wallet. The GUI may display the document in a human-readable form.

At 420, the token server system 110 may receive a modification of the portion of the document corresponding to the first document token in order to generate the modified document. In some embodiments, the user may be able to view the document, but may be limited to modifying the portion corresponding to the document token. For example, that part may be the signature block of the contract. In some embodiments, that part may be a particular clause of the contract. For example, one or more parts such as rights, obligations, guarantees, terms and / or other documentary provisions may be negotiated. The modifications may be edits of these provisions or may be received via a GUI displaying the decrypted document. Depending on the modification of the document, the user may choose to preserve and / or save this modification. The token server system 110 may implement the modification locally, or may use the blockchain 120 to preserve the modification. To preserve modifications using the blockchain 120, the token server system 110 may perform operations similar to document generation.

In particular, the token server system 110 may encrypt and store the encrypted version of the document modified at 425, or may create a link to the encrypted version of the document modified at 430, at 435. You may create a hash of the modified document. Similar to the elements described with reference to FIG. 2, the token server system 110 may perform these actions to generate a modified version of the document while adhering to the immutability of the blockchain 120. In some embodiments, the modified document generation may be a separate document from the original document. The modified document may be preserved on the blockchain in subsequent blocks that may represent the updated version of the document or counter-offer. In this way, changes in the document may be tracked while reserving the benefits provided by publishing the updates to the blockchain.

At 440, the token server system 110 may create a second document token corresponding to the modified document. At 445, the token server system 110 may transmit or transfer a second document token to the digital wallet. At 450, the token server system 110 may use one or more smart contract functions to expose a hash of the modified document and a link to an encrypted version of the modified document to the blockchain. The creation of a second document token, the transmission of a second document token, and the disclosure of hashes and / or links may be similar to the corresponding elements described with reference to FIG.

Using similar behavior for document creation and document modification, the token server system 110 may simplify and / or streamline the document modification process. Utilizing similar behavior rather than maintaining different protocols for document creation and modification may support more compact processing with less computational overhead. The token server system 110 may manage and preserve these modifications in a streamlined manner, even if multiple parties are implementing many complex modifications and / or negotiations. Further, the token server system 110 may perform this management asynchronously in order to avoid a long transaction time when writing to the blockchain 120.

FIG. 5 illustrates a flow chart illustrating method 500 for document negotiation, according to some embodiments. Method 500 will be described with reference to FIG. 1, however, method 500 is not limited to its exemplary embodiments.

In certain embodiments, the token server system 110 may facilitate negotiation of document clauses between different parties. Method 500 may use the elements of methods 200, 300A, 300B, and 400, but may further provide details exemplifying the interaction between multiple digital wallets. Method 500 will be described with reference to the token server system 110, where method 500 will be described, for example, with reference to computer systems and / or hardware (eg, circuits, dedicated logic, programmable logic, etc.) described with reference to FIG. It may be executed on any computing device, such as microcode), software (eg, instructions executed on a processing device), or processing logic that may include a combination thereof.

It should be understood that not all steps may be required to implement the disclosure provided herein. In addition, some of the steps may be performed simultaneously or in a different order than those shown in FIG. 5, as will be appreciated by those skilled in the art.

At 505, the token server system 110 may receive an interaction with the GUI element corresponding to the first account in order to generate a document to be sent to the second account. The GUI element may be, for example, a button or widget on a web page. For example, a user in the second account may list properties for sale, and a GUI element allows the user in the first account to provide the offer document to the second account. It may be a "offer immediately" button. The user of the first account may provide information and / or text in the format described above to generate the document.

At 510, the token server system 110 may generate a first document token corresponding to the document. This document token may represent ownership of the document by the first account. At 515, the token server system 110 may use one or more smart contract functions to expose a hash of a document and a link to an encrypted version of the document to the blockchain. The process may be performed in a manner similar to that described with reference to FIG.

At 520, the token server system 110 may transmit or transfer the first document token to the first digital wallet corresponding to the first account and the second digital wallet corresponding to the second account. Transmission of the first document token to each account may indicate that each party can access and / or modify the document. The configuration may allow a second account to modify the document during the negotiation process.

At 525, the token server system 110 may receive a request to access the document from a second account. For example, a second account may have access to a link to an encrypted version of the document and / or to a website and / or cloud platform managed by the token server system 110 to access the document. May provide login credentials for. The token server system 110 may utilize the user interface 130 to generate a GUI that should be displayed on the user device 140 for the user of the second account.

At 530, the token server system 110 may receive document modifications from a second account to generate modified documents. For example, the user corresponding to the second account may modify the document using the GUI displayed on the user device 140. This amendment may represent a discrepancy with the provisions of the document. In some embodiments, the modifications may include additions, inserts, erases, replacements, and / or other document modifications made by the user of the second account. In some embodiments, the GUI may display the document in a web browser and the user may provide modifications to the token server system 110 via the web browser.

At 535, the token server system 110 may create a second document token corresponding to the modified document. Similar to the second document token described with reference to FIG. 4, the second document token may indicate a modified document while still preserving the original document corresponding to the first document token. good. The second document token may be used to specify ownership and / or modification permission and to maintain a record of modification.

At 540, the token server system 110 may transmit or transfer the second document token to the first digital wallet and the second digital wallet. In this way, both the original offering party and the counter-offering party may access and / or modify the modified document. At 545, the token server system 110 may use one or more smart contract functions to expose a hash of the modified document and / or a link to an encrypted version of the modified document to the blockchain 120. good. Like the original document, the token server system 110 may preserve the modified document in a similar fashion in terms of the immutable properties of the blockchain 120. Similar to the other processes described above, the token server system 110 may consume processing tokens to expose the data to the blockchain 120.

In some embodiments, method 500 may be used for further counter-offers. For example, the parties may continue to negotiate or amend the provisions until the parties agree. In this case, the parties may specify that the token server system 110 does not publish the document or modified document on the blockchain 120 until an agreement is reached. In some embodiments, publication of the modified document may occur each time a counter-offer and / or modification is returned.

FIG. 6 illustrates a flow chart illustrating method 600 for generating a graphical user interface (GUI) for document negotiation, according to some embodiments. Method 600 will be described with reference to FIG. 1, however, method 600 is not limited to its exemplary embodiments.

In certain embodiments, the token server system 110 may generate a GUI for displaying contract negotiations regarding the parties to a transaction. An exemplary embodiment of the GUI is depicted in FIG. Method 600 is described with reference to the token server system 110, where method 600 is described, for example, in a computer system and / or hardware (eg, circuit, dedicated logic, programmable logic, etc.) described with reference to FIG. It may be executed on any computing device, such as microcode), software (eg, instructions executed on a processing device), or processing logic that may include a combination thereof.

It should be understood that not all steps may be required to implement the disclosure provided herein. In addition, some of the steps may be performed simultaneously or in a different order than those shown in FIG. 6, as will be appreciated by those skilled in the art.

At 605, the token server system 110 may generate a first GUI displaying a first set of segmented parts of the document and a second set of segmented parts of the document, where the document is the blockchain 120. Corresponds to the document link stored above. An exemplary embodiment of the first GUI display is depicted in FIG. For example, the first set and the second set of segmented portions may correspond to the same document. The first set may display the edits and / or modifications made by the first user account, while the second set may display the edits and / or modifications made by the second user account. .. These edits and / or modifications may be preserved on the blockchain 120.

At 610, the token server system 110 may generate a second GUI displaying a first set of segmented parts of the document and a second set of segmented parts of the document. The second GUI may be displayed on the user device 140, which may be different from the user device 140 displaying the first GUI. For example, the offering party may view the first GUI, while the receiving party of the offer may view the second GUI. The segmented portion of the document may represent modifications and / or edits provided by either party.

At 615, the token server system 110 may receive modifications of the segmented portion of the first set of segmented portions via the second GUI. For example, the party receiving the offer document may view the offer document via a second GUI. The offer document may be segmented into different parts. The parties may then modify one of these parts. For example, the amendment may be an amendment to the terms of the contract and / or other text or object in the contract document. Modifications may include additions, insertions, deletions, replacements, and / or other document modifications made by the user of the second account. If the first set of segmented parts appears to the left of the second set of segmented parts, the user may enter these modifications into these left segments.

At 620, the token server system 110 may update a second set of segmented portions of the document of the first GUI to display the modifications. This updated view may depict the counter-offer presented by the second party to the first party. For example, the first party may view the first GUI or may view the modifications presented by the second party in the second set of segmented parts. Thus, the first party may view its own modifications in the first set of segmented portions while viewing the modifications of the second party in the second set of segmented portions. The GUI display may further provide side-by-side scrolling to allow the user to browse the segmented parts and compare the modified parts. The first GUI also uses techniques such as highlighting, color, font size, and / or other GUI elements to show different modified clauses between the two sets of segmented parts, using techniques such as highlighting, color, font size, and / or other GUI elements. The correction may be emphasized. In this way, the GUI may provide a view of human-readable text and preserved blockchain modifications. The GUI amendments may allow users to easily compare offers and / or counter-offers and amend documents during the negotiation process to achieve consensual terms.

FIG. 7 depicts a block diagram of a graphical user interface (GUI) 700, including segmented document portions 712A-718A, 712B-718B, according to some embodiments. The token server system 110 may use the user interface 130 to generate a GUI 700 to be displayed on the user device 140. As described with reference to FIG. 6, the GUI 700 may display documents 710A, 710B with corresponding segmented portions. Document 710A may contain the same content as Document 710B, but may differ in the representation of modifications proposed by each party. For example, the segmented portion 712A of document 710A may include the same content as the segmented portion 712B of document 710B. In some embodiments, documents 710A, 710B may be contracts and may include different compartments corresponding to segmented portions 712A-718A, 712B-718B. For example, the segmented portions 716A and 716B may correspond to the guarantees granted by the seller. The segmented portions 714A and 716B may include an offer price. In this way, the GUI 700 may depict two versions of the contract for the user to make modifications and / or view.

A first party viewing the GUI 700 may provide a modification of Document 710A. For example, the user may edit the segmented portion 714A to modify the offer price. The segmented portion may include an editable text and / or a fillable form for providing information. With respect to the first party viewing the GUI 700, Document 710B may include modifications generated by the second party. For example, Document 710B may include an offer against the terms of the contract. The GUI 700 may display both modifications generated by the first party and the second party, allowing comparison of modifications.

In some embodiments, the token server system 110 may generate a version of GUI 700 for a second party. The token server system 110 may invert the positions of documents 710A and 710B. For example, the second party may edit the document 710A as displayed on the user device 140 corresponding to the second user. This modification may appear as a modification of document 710B to the first user viewing the GUI 700 on the user device 140 corresponding to the first user. Thus, regardless of the user role in the transaction, the user may make document modifications in document 710A while viewing the edits of other parties in document 710B.

Two documents 710A, 710B may be depicted in FIG. 7, but other versions of document 710 may be displayed in multi-party transactions and / or negotiations. For example, the GUI 700 may depict multiple versions of a document with different modifications from different parties.

The GUI 700 may provide a human-readable interface for interacting with document tokens and documents managed via the blockchain. As described above, the document and / or the modified document may correspond to a document token with the corresponding permission. For example, the parties may be restricted to modifying only certain segmented parts. In addition, the modifications may be stored and / or published on the blockchain to maintain a record of the modifications. In this way, the GUI 700 may provide a mode for viewing and / or interacting with documents managed using the blockchain 120.

In addition to displaying the segmented portion, the GUI 700 may include one or more navigation interfaces 720A, 720B. The navigation interface 720 may provide a document management GUI element provided by the token server system 110. For example, the navigation interface 720 may include GUI icons or buttons for identifying, viewing, and / or selecting contracts. For example, the user may be negotiating multiple contracts, and the navigation interface 720 may allow the user to select and view different contracts.

The navigation interface 720 may include a library link to allow the user to create a new document or contract. In some embodiments, the user may generate a document and provide customized segmentation to a portion of the document. Similar to the segmentation described above with reference to FIG. 3A, the user may specify the permissions corresponding to the parts. In some embodiments, the token server system 110 may provide selectable documents and / or contract templates with preformed content and / or segmentation. The user may select and / or modify these templates.

Navigation interfaces 720A, 720B also provide a messaging interface, a list of tasks for users, a management screen for managing digital wallets, and / or other GUI elements that can be used during the document modification and / or negotiation process. It may be included.

FIG. 8A depicts a block diagram of a graphical user interface (GUI) 800A, including a document action button 850A, according to some embodiments. The document action button 850A has the words "offer immediately", "lease immediately", "borrow immediately", "apply immediately", "buy immediately", "list immediately", "immediately" You may display "manage" and / or other words that indicate the generation of the document.

The GUI 800A may be a web browser and / or may include a web page that allows widgets and / or GUI buttons or icons to be included. The GUI 800A may include an address input portion 810A for defining a website. The user may browse the GUI 800A using a web browser on the user device 140. The GUI 800A may be accessed by a user browsing a web page, for example, a web page listing real estate for sale and / or rent. The user may be searching for a home to buy and / or rent and may use the GUI 800A to browse information related to the real estate property. In addition, the GUI 800A may initiate a document generation process and may include a document action button 850A, which will be further described below. In some embodiments, the website listing the real estate property may implement a document action button 850A on the GUI 800A to facilitate user access to the document generation process provided by the token server system 110. In some embodiments, the token server system 110 may generate a GUI 800A and / or manage a website associated with a real estate transaction.

The GUI 800A may display an image 820A, text data 830A, and / or additional detail 840A. Additional details 840 may include description and / or additional text information that may be formatted differently from the text data 830A. In some embodiments, the user may enter and / or navigate to a web page listing properties for sale. In this case, image 820A may depict an image of the property, text data 830A may include high level details related to the property, and additional detail 840A may include paragraph descriptions and / or related to the property. Other bullet points may be included. The user may browse this information to know about the property.

The GUI 800A may include a document action button 850A. The document action button 850A may be a GUI element that can provide an interface with the token server system 110. For example, the document action button 850A may be a widget embedded in a web page displaying a property list. In some embodiments, the document action button 850A is the word "offer immediately", "lease immediately", "borrow immediately", "apply immediately", "buy immediately", and / or document. Other terms may be displayed to indicate to the user that a can be generated. In some embodiments, the document action button 850A is used for other documents, such as for listing properties, using the "List Now" and / or "Manage Now" options. May be done.

In response to interacting with the document action button 850A via selection, pressing, and / or clicking, the widget may generate a call to the token server system 110 to provide the document generation process. .. For example, the token server system 110 may provide a fillable form and / or template that can be displayed on the GUI 800A for the user to draft a document and / or provide information in a template. The token server system 110 may provide an overlay on the GUI 800A for the user to enter this information. Depending on entering the requested information, the token server system 110 may transmit the offer to the intended recipient. The token server system 110 may also generate the corresponding document token and / or preserve the document on the blockchain 120.

As described above, the GUI 800A provides various technical improvements. The GUI 800A may provide a streamlined format for document generation that preserves the documents generated using the blockchain 120. "Offer Immediately", "Lease Immediately", "Rent Immediately", "Apply Immediately", "Buy Immediately", "List Immediately", and / or "Manage Immediately" Buttons The possible document action button 850A may allow the user to quickly generate a document with less GUI interaction. Reducing interactions can help reduce wasted computer resources or unnecessary web navigation. In addition, the document action button 850A may help reduce network traffic due to the reduced number of interactions.

As described above, the document action button 850A may be a widget and / or plug-in embedded within a third party website or web page. The document action button 850A may be located on a web page that is not managed by the token server system 110. For example, a website may be managed by a third party system and / or an administrator, while the token server system 110 may facilitate document creation in response to the user interacting with the document action button 850A. Document action button 850A may be used to generate documents related to transactions for goods, services, and / or real estate. In addition, the document action button 850A may initiate a document tokenization and blockchain integrity process facilitated by the token server system 110. In some embodiments, the document action button 850A may be used to facilitate a trading process that may include offers and counter-offers. The trading process may include offers, negotiations, acceptances, and / or conclusions. Through interaction with the document action button 850A, the user may generate documents and / or transactions via the decentralized marketplace.

FIG. 8B depicts a block diagram of a graphical user interface (GUI) 800B for link management and generation of 1-Link processes, according to some embodiments. The user may use the GUI 800B to manage links and / or documents transmitted to other parties. For example, the buyer may use the link to offer an offer to buy real estate. The GUI 800B may allow buyers to manage different offers. Similarly, the seller may use the GUI 800B to manage offers for sale. These offer documents may also be managed via links. The parties may use GUI800B to generate the document and / or the link corresponding to the document and manage the document and / or the recipient of the link.

The user may also use GUI800B to manage links such as links to property lists and / or other documents and / or links to offer documents created by the user using the token server system 110. good. The link may represent a document that can be preserved by the blockchain 120, which may further include access to other documents preserved by the blockchain 120. Thus, the link may be a distribution system for other blockchain-based documents, and the link itself may be a blockchain-based document.

These links may be included in a message that may also represent another type of document that can be managed via the blockchain 120. Method 900, as described with reference to FIG. 9, illustrates an exemplary embodiment of generating a message containing a link to a blockchain management document. In some embodiments, the step of generating a link may include the step of generating a link to a document managed by the token server system 110 using the blockchain 120. For example, the link may provide access to one or more documents that are preserved using the blockchain 120.

The user may access the token server system 110 and / or use the GUI 800B when generating multiple offer messages and / or transmitting multiple documents. The GUI 800B may arrange one or more links in rows and columns to manage the links. The link may be a link to a web page and / or electronic message with the corresponding document. For example, FIG. 8C may depict a message interface accessible from a link.

Turning to GUI800B again, the user may use GUI800B to create a link to a document and / or create a document with a corresponding link. For example, the user may interact with the link creation button 870B displayed on the GUI 800B. This document may allow the user to enter text and / or may be a fillable form. The link creation button 870B may be an icon and / or a button that allows the user to create a new link. Creating a new link may include a fillable form, a wizard, and / or other prompts that allow the user to provide information about different fields associated with the link. The GUI 800B may also include management for received links.

The GUI 800B may include several fields for organizing the generated links. For example, the GUI 800B may include a selection field 810B, an address field 820B, a recipient field 830B, a role field 840B, a transmission detail field 850B, and / or an interaction button 860B. The selection field 810B may allow the user to select one or more links. This selection may allow management of multiple links. The address field 820B may include details related to the physical address of the property. Address field 820B may be used when the link and corresponding document relate to real estate. The recipient field 830B may include one or more identifiers for delivering the link. For example, the recipient field may contain one or more email addresses. The role field 840B may list the roles corresponding to the recipient and / or the user generating the link. For example, in a real estate transaction, role field 840B may include roles such as "buyer", "seller", "agent", "lender", and / or other roles. The transmission detail field 850B may display one or more items related to the transmission of the link. For example, the transmission detail field 850B may indicate whether the link has been transmitted or whether the link is a draft. In some embodiments, the transmission detail field 850B may also indicate the sender of the link. The interaction button 860B may include a GUI element that allows the user to interact with the link. For example, the interaction button 860B has the ability to edit the link and / or the document corresponding to the link, copy the link, view the link, view the message associated with the link, and / or other links. The operation may be included. In some embodiments, the token server system 110 may facilitate a message associated with the document, and the "view message" interaction button 860B allows the user to view the corresponding message. May be good. Although these fields have been described, the GUI 800B may also use other fields for organizing links and / or corresponding documents.

As such, the GUI 800B may provide a streamlined form of link creation and / or link management for delivering blockchain maintenance documents. A user who creates a link via the link creation button 870B may access the 1-Link process and quickly generate a blockchain maintenance document associated with a link that may contain a link to another blockchain maintenance document. .. Thus, the use of the GUI 800B and / or 1-Link process provides the generation of linked blockchain maintenance documents while also reducing the number of user interactions and computer transactions, as well as network traffic. It may be reduced.

The 1-Link process may provide a decentralized process for buying, selling, and / or trading goods and / or services online. In some embodiments, the user may avoid using a virtual marketplace or an existing e-commerce website. Users may use the 1-Link process to conduct peer-to-peer transactions, including offers and counter-offers. Links generated from the 1-Link process are used, transmitted, and transmitted in electronic communications, including, but not limited to, text messages, emails, websites, social media, chat rooms, instant messages, and / or voice transmissions. / Or may be dispersed. In some embodiments, the links may be communicated via an analog process such as a handwritten message.

Links are integrated into other processes, including calendar and scheduling applications, language translation processes, payment platforms, messaging and negotiation processes, chat room applications, video and / or audio chat, and / or advertising or display elements, and / Or other processes may be integrated. In some embodiments, the user may choose a form of communication that can be a trace of legally binding electronic communication. Links may also provide users with the ability to provide payments using nominal currency, digital currencies, and / or other forms of currency.

Existing e-commerce websites allow users to use the online marketplace to sell, buy, lease and trade goods and services in exchange for financial indemnification or in-kind goods and services. Request. Buyers and sellers use these existing platforms to advertise, buy, trade, bid, initiate exchanges, and / or terminate them. The host marketplace may also charge the user additional costs regarding fees for using the marketplace. The Host Marketplace may also limit users to comply with Marketplace specifications when promoting the terms and conditions of goods and / or transactions for sale. The host marketplace may limit users from selling to audiences they believe are likely to buy their products or offer them the services they need.

The 1-Link process may provide a method for facilitating transactions in a decentralized fashion. The 1-Link process may democratize transactions between users, which may allow users to conduct transactions while avoiding online marketplaces. For example, sellers, buyers, and / or traders may use the 1-Link process to exchange goods and services directly. You may also provide potential buyers with a link to a list of documents that may offer goods and / or services for sale so that the parties can execute transactions directly while avoiding the use of the online marketplace. good.

As described above, the seller may use the 1-Link process to generate a link for transmission to the buyer. In this way, the seller may avoid using the virtual marketplace as a host for the promotion of goods or services for sale. In addition, sellers may avoid multiple steps involved in virtual marketplace transactions. Using the 1-Link process, the seller may generate links, customized emails, and / or other communication methods that embed links to send to the buyer. Messages and / or links are goods and / or services for sale, details related to offers for sale, and / or, for example, pricing, contact information, payment options, and / or other details, etc. You may display web pages, mini-websites, and / or social media pages that may display other transaction information. Buyers may use links to purchase products or services and / or enter into negotiations with sellers to amend the terms of sale. As will be further explained below, the buyer may use a document action button accessible via a message or link to generate a document for negotiation.

In some embodiments, the buyer may use the 1-Link process to generate links and / or messages for purchasing goods and / or services. The buyer may use the 1-Link process even if the seller has not previously created the link prior to the transaction. The buyer may use the 1-Link process when the buyer searches for and / or identifies the product or service and creates a link that describes the desired purchase. In some embodiments, the link may describe the goods or services the buyer is searching for. The Buyer may transmit the Link to the Seller, which may allow the Seller to offer goods and / or services that may meet the Buyer's requirements. The parties may then carry out the transaction via the 1-Link process, which may generate the corresponding document token. Examples of this embodiment will be further described below with reference to FIGS. 10, 11A, and 11B, which illustrate the demand-driven value chain.

Users may also use the 1-Link process to trade goods and / or services. When trading, the parties may rely on the negotiation and / or counter-offer elements of the 1-Link process. For example, the parties may modify the terms of the document, including the content of the goods and / or services being traded.

As such, the 1-Link process may provide a personalized marketplace that can democratize and / or decentralize the trading process. The 1-Link process may assist in lead generation, marketing, sale, purchase, transaction decision and / or transaction of goods and / or services without relying on a third party sales platform. For developing countries where online marketplaces may be limited, the 1-Link process may provide a mode for conducting transactions that may not have previously existed. In addition, the 1-Link process may provide users with convenience, efficiency, cost savings, and / or reliability through blockchain-based document maintenance. The 1-Link process may also be used in other contexts, such as political campaigns. The 1-Link process may provide a form for donors to donate to political campaigns.

FIG. 8C depicts a block diagram of a graphical user interface (GUI) 800C of message 810C including a document action button 850C and a document link 840C, according to some embodiments. The GUI 800C may include an email message that can be generated using the link management elements of the GUI 800B. Message 810C may represent a blockchain-based document that may include links to other blockchain-based documents via document link 840C.

The user may browse the GUI 800C in preparation for sending the offer document to the parties. For example, a real estate agent or seller may prepare message 810C for transmission to a potential or interested buyer of real estate. Including the document action button 850C within message 810C may allow a potential buyer to generate an offer document in response to message 810C and offer the offer to the seller. In addition, potential buyers may also access document link 840C to access documents preserved on the blockchain 120 that may assist the buyer's decision-making process and / or offer document generation process. Although the seller / buyer embodiment is described, the GUI 800C also includes the context of the buyer / seller in the reverse context of the buyer transmitting message 810C, in the context of the borrower / landlord, and / or in the context of the buyer / seller with respect to the goods and / or services. May be used in.

To generate message 810C, the user may be directed by the prompt provided by the token server system 110 to enter one or more links. For example, a user may list properties on a web page with a corresponding address. This address may be requested and compiled into the GUI 800C via the address display 830C. The user may interact with the address display 830C, select it, press it, and / or click on it to navigate to a web page listing properties. Message 810C may also include text element 820C, which may include text entered by the user. For example, the text may be a personalized message that provides an introduction to the document linked within message 810C.

Message 810C may include document link 840C. Document link 840C may include a link to a stored document that allows the user to download the document. In some embodiments, the document link 840C may represent other documents preserved by the blockchain 120. These documents may be tokenized in the manner described above. In this way, access may be restricted based on encryption, but a user accessing document link 840C may access the document based on the permissions provided by the document token. In certain embodiments, the bank may send the new client a link that may contain some confidential documents for scrutiny and signature. The bank may specifically grant the client permission as the only party to be able to view and / or modify the document. The client may securely access the document by using an encryption key to scrutinize and sign the document. Using the token server system 110, banks may avoid security concerns during document exchanges and ensure that documents are securely delivered to the right people. In some embodiments, law enforcement agencies may also use links for collaboration to share documents with both internal and external stakeholders for case studies or prosecution.

Message 810C may further include a document action button 850C. The document action button 850C may be similar to the document action button 850A as described with reference to FIG. 8A. The document action button 850C may be embedded within the message 810C, allowing the user to generate a document via a call to the token server system 110. Depending on the interaction with the document action button 850C, a web browser may be opened and the user may generate a document to be stored on the blockchain 120. For example, this document may be an offer to purchase a property.

Message 810C may be accessed via a link generated by the token server system 110 and / or via an electronic message delivered by the token server system 110. Message 810C may represent a document that can be similarly stored on the blockchain 120. This document may include links to other documents managed by the token server system 110 and maintained using the blockchain 120. Message 810C may further include a document action button 850C that allows the user to generate a new document. As described above, the message 810C may illustrate the document protected by the blockchain 120 within another document maintained by the blockchain 120. In addition, message 810C may illustrate the ability of a document preserved by the blockchain 120 to provide the user with the ability to generate another blockchain preserved document. As described above, the inclusion of the document action button 850C may streamline the document generation process, allowing users to quickly generate blockchain-preserved documents with fewer navigation interactions. May be good. Reducing interactions can help reduce wasted computer resources or unnecessary web navigation. In addition, the document action button 850C may help reduce network traffic due to the reduced number of interactions.

In some embodiments, message 810C may be used for secure document and / or message delivery. For example, message 810C may not include the document action button 850C. The user may create an e-mail document and store the document token delivered through the 1-Link process. The recipient may open the email and generate a second document token to sign the email. The signature may be an acknowledgment of receiving the email and / or an agreement on the content of the email that may require the signature. Generation of a second document token may indicate that the recipient has viewed the document, which may provide auditability and / or traceability. As described above, the message 810C may be used as a secure document distribution mechanism.

FIG. 9 illustrates a flow chart illustrating method 900 for generating a message including a document action button and a document link, according to some embodiments. Method 900 shall be described with reference to FIG. 1, however, method 900 is not limited to its exemplary embodiments. Method 900 may be an embodiment of the 1-Link process.

In certain embodiments, the token server system 110 may generate links and / or messages that allow users to access blockchain-preserved documents and document generation processes. Method 900 is described with reference to the token server system 110, where method 900 is described, for example, in a computer system and / or hardware (eg, circuit, dedicated logic, programmable logic, etc.) described with reference to FIG. It may be executed on any computing device, such as microcode), software (eg, instructions executed on a processing device), or processing logic that may include a combination thereof.

It should be understood that not all steps may be required to implement the disclosure provided herein. In addition, some of the steps may be performed simultaneously or in a different order than those shown in FIG. 9, as will be appreciated by those skilled in the art.

At 905, the token server system 110 may generate a GUI that includes a first icon for initiating the link generation process. The GUI may be, for example, GUI 800B. The link generation process is one or more display screens that request information from the user, and / or link information that can be compiled into a message, and / or other data that may allow the user to access the blockchain maintenance document. It may include a structure.

At 910, the token server system 110 may receive an interaction with the first icon. The first icon interaction may initiate a document creation process similar to that described above. The document may be secured on the blockchain 120 using the techniques described above, which may include encryption, hashing, and / or document tokenization.

At 915, the token server system 110 may generate an interface for attaching one or more documents to a link. For example, the interface may be one or more display screens that request information and / or require the user to upload a document. In some embodiments, the interface may be a fillable form. In some embodiments, the one or more documents may be personal documents containing confidential information. For example, in a real estate transaction, the document may relate to the user's credit history or loan approval amount.

At 920, the token server system 110 may receive an indication to attach one or more documents to a link via a GUI. In some embodiments, the user may specify the document location by providing a link to the document. Based on the information provided, the token server system 110 may identify the document. As described above, the user may upload one or more documents.

At 925, the token server system 110 may generate document tokens for each of one or more documents. The token server system 110 may generate document tokens as described above. For example, the token server system 110 may apply encryption, hashing, document tokenization, and / or a digital wallet deposit. The token server system 110 encrypts and stores each encrypted version of one or more documents, creates a blockchain link to each encrypted version of one or more documents, and creates a blockchain link to each encrypted version of one or more documents. Each cryptographic hash may be generated.

At 930, the token server system 110 may expose a blockchain link to one or more documents to the blockchain 120. Publishing a blockchain link may preserve the attached document. Similar to the process described above, the blockchain link may be linked to an encrypted version of the document for confidentiality purposes.

At 935, the token server system 110 may generate a message corresponding to the link, which initiates a document generation process for generating the blockchain link and the response document to be published on the blockchain 120. Includes a second icon for The message may be, for example, an e-mail message as depicted in the GUI 800C. The blockchain link may be the document link 840C and the second icon may be the document action button 850C.

As described above, the message may be a delivery system that transmits a blockchain-preserved document to an individual, or may provide an individual with the ability to generate a response document. For example, the message may be an offer document that may include other support documents. The offer document may indicate a request to purchase the property. The support document may include, for example, a document indicating the user's pre-approval of the loan amount. The lender may publish the pre-approval to the blockchain 120, which may show its credibility. The message may include this information and may provide the ability to generate a response document. The response document may be, for example, a counter-offer, acceptance of the offer, and / or other document with a digital signature corresponding to the seller. The token server system 110 may manage the response document or publish the response document on the blockchain 120 in the manner described above.

FIG. 10 depicts a block diagram of a document chain environment 1000 that provides a demand-driven value chain according to some embodiments. The document chain environment 1000 may include a token server system 1010 that can operate in a manner similar to the token server system 110. The document chain environment 1000 may also include a blockchain 1020 that can operate in a manner similar to the blockchain 120. The token server system 1010 may interact with several account profiles and different types of account profiles such as store account 1030, corporate account 1040, and / or user account 1050.

These different accounts may represent different account types. For example, user account 1050 may represent a user account profile for consumers. The store account 1030 may represent a retailer that may be wholesale or retail. The retailer may have a physical location and / or may be an online retailer. The corporate account 1040 may represent a company and / or government that cannot sell consumer goods.

As can be seen from the document chain environment 1000, each account may interact with other accounts of the same type and / or different types via the token server system 1010. Accounts may exchange documents, including offer documents, between account types. User account 1050 may submit offers, offers, and / or suggestions to store account 1030 and / or corporate account 1040. In some embodiments, the user account 1050 is when the store account 1030, the enterprise account 1040, and / or another user account 1050 does not list real estate properties for sale, services, and / or for sale. However, you may submit these offers. As such, the token server system 1010 may provide a decentralized marketplace for the exchange of goods, services, and / or contractual obligations that can be initiated regardless of account type. The token server system 1010 may provide self-sufficiency and autonomy between the parties to negotiate a transaction.

In addition, offers, acceptances, and / or negotiations may not be limited by the role of a particular account. For example, the store account 1030, the enterprise account 1040, and / or the user account 1050 may be the offering party and / or the receiving party, respectively. Similarly, each party may offer a counter-offer to the transaction. In this way, the token server system 1010 may facilitate a decentralized marketplace between different accounts and / or account types. In addition, the token server system 1010 may facilitate multi-party transactions between these accounts and account types.

In some embodiments, the token server system 1010 may also submit a demand-driven value chain. Demand-driven value chains may also allow buyers to generate offers and / or offer documents in industries that traditionally used supply-driven trading marketplaces. For example, a traditional online retailer may list items and receive purchase orders from buyers. In a demand-driven value chain, a buyer may submit an offer for goods, services, and / or real estate, even if the seller does not provide the list. Similarly, the borrower may offer an offer to rent a property from the landlord. Using a demand-driven value chain, parties such as buyers, sellers, borrowers, landlords, agents, consumers requesting services, and / or service providers initiate offers and / or generate offer documents. You may.

Thus, the token server system 1010 may facilitate offers, counter-offers, and / or negotiations between the parties, regardless of role or account type. Buyers and / or sellers may initiate transactions. In addition, different parties and / or account types such as businesses, stores, entities, and / or consumers may use demand-driven value chains to initiate and / or facilitate transactions using blockchain integrity. good. In this way, the token server system may use the blockchain to support a decentralized marketplace for transactions. In addition, the token server system 1010 may provide the flexibility to facilitate transactions from different parties with different roles. Thus, the token server system 1010 provides a one-stop shop where parties can introduce, initiate, negotiate, complete, and / or inquire about transactions in a decentralized manner and / or obtain services. You may.

In this demand-driven model, parties requesting goods and services visit specific marketplaces, listing websites, and / or aggregated websites to search for specific goods and services. Can be avoided. For convenience, the parties may initiate and / or generate document tokens, referred to as demand tokens, which may define their demand demands. For example, the parties want to buy a new car and generate a document defining their requirements for the new car, the manufacturer is Toyota, the color is red, and the price is $ 25,000- $ 28, Up to 000 and / or delivery options can be up to Brooklyn.

Using demand tokens, the token server system 1010 may also search and / or identify other document tokens, referred to as supply tokens, with supply specifications for goods and services that exactly match the specified demand. good. Those requirements or supply specifications may be stored in the metadata layer of the demand token as searchable fields. The token server system 1010 may notify the possible supply accounts that they are receiving demand for goods and services that they may be able to provide. In some embodiments, a busy mother may attempt to find a two-day babysitter service while she is traveling. The mother may generate a demand document and the token server system may generate a demand token. The token server system 1010 may search and / or identify the babysitter who generated the supply document and the corresponding supply token with content that closely matches the requirements of the busy mother. Demand-based matching to supply eliminates some steps required by parties on both the supply and demand sides, eliminating marketing costs for suppliers and search time and effort for parties requesting goods and services. Can be reduced.

FIG. 11A illustrates a flow chart illustrating method 1100A for role-based document generation, according to some embodiments. Method 1100A shall be described with reference to FIG. 10, however, method 1100A is not limited to its exemplary embodiments.

In certain embodiments, the token server system 1010 may facilitate negotiations and / or counter-offers between parties of different account types. The method 1100A is described with reference to the token server system 1010, where the method 1100A is described, for example, in reference to FIG. 12 for computer systems and / or hardware (eg, circuits, dedicated logic, programmable logic, etc.). It may be executed on any computing device, such as microcode), software (eg, instructions executed on a processing device), or processing logic that may include a combination thereof.

It should be understood that not all steps may be required to implement the disclosure provided herein. In addition, some of the steps may be performed simultaneously or in a different order than those shown in FIG. 11A, as will be appreciated by those skilled in the art.

At 1105, the token server system 1010 may receive a document creation request from the first account corresponding to the first digital wallet, the first account corresponding to the first account type. The first account type may be, for example, a store account 1030, a corporate account 1040, or a user account 1050. The document creation request may be received from an interaction with a GUI element such as a document action button.

At 1110, the token server system 1010 may facilitate the creation of a first document. This document creation process may be similar to the other document creation processes described above. At 1115, the token server system 1010 may create a document token corresponding to the first document. At 1120, the token server system 1010 may transmit the document token to the first digital wallet. The creation of the document token and the transmission of the document token to the first digital wallet may also occur in the manner described above. At 1125, the token server system 1010 may use one or more smart contract functions to expose a hash of the first document and a link to an encrypted version of the first document to the blockchain. This may also be performed in the manner described above.

In 1130, the token server system 1010 may transmit the notification to a second account corresponding to the second digital wallet, the second account corresponding to a second account type different from the first account type. do. The notification may be, for example, a push notification or an email message. In some embodiments, the document token may be transmitted to a second digital wallet similar to the first digital wallet, depending on the permissions specified.

The second account type may be different from the first account type. This difference may demonstrate different positions and roles of the offering party and the receiving party. For example, the store account 1030 may transmit an offer document indicating an offer to sell the product to the user account 1050. Similarly, the user account 1050 may transmit an offer document for purchasing the product to the store account 1030. The user account 1050 may interact with the corporate account 1040 in the same manner, for example, by purchasing services such as insurance. FIG. 11A illustrates exemplary embodiments with different account types, but in some embodiments the account types may be the same account type.

At 1135, the token server system 1010 may facilitate the creation of a second document by the second account. For example, the second account may generate a modified version of the first document. The second document may be a signed version and / or may include a digital signature. In some embodiments, the second document may be a counter-offer with amended provisions. Depending on creating the second document, the token server system 1010 may perform the encryption, hashing, and / or tokenization described above. The token server system 1010 may further deliver the second document to the first account. In this way, the parties may negotiate and / or carry out transactions in a peer-to-peer manner that preserves the terms of the contract through the immutability of the blockchain 1020.

FIG. 11B illustrates a flow chart illustrating method 1100B for demand matching according to some embodiments. Method 1100B shall be described with reference to FIG. 10, however, Method 1100B is not limited to its exemplary embodiments.

In certain embodiments, the token server system 1010 may perform demand-driven matching and / or identification of documents. Method 1100B is described with reference to the token server system 1010, where method 1100B is described, for example, with reference to computer systems and / or hardware (eg, circuits, dedicated logic, programmable logic, etc.) described with reference to FIG. It may be executed on any computing device, such as microcode), software (eg, instructions executed on a processing device), or processing logic that may include a combination thereof.

It should be understood that not all steps may be required to implement the disclosure provided herein. In addition, some of the steps may be performed simultaneously or in a different order than those shown in FIG. 11B, as will be appreciated by those skilled in the art.

At 1140, the token server system 1010 may receive a plurality of supply documents. The supply document may indicate the availability of goods, services, real estate properties, and / or other offers for sale. The plurality of supply documents may be supplied by different users who interface with the token server system 1010. The token server system 1010 may use the blockchain 1020 to preserve these supply documents. The supply document may have been generated using the document action button as described above. The content of the plurality of supply documents may vary. For example, the supply document may explain a list of sales of real estate properties. In some embodiments, the supply document may list automotive and / or babysitter services. The user may indicate the confidentiality designation corresponding to the supply document in the format described above.

At 1145, the token server system 1010 may create supply document tokens corresponding to each of the plurality of supply documents. These supply document tokens may be similar to the document tokens described above. The token server system 1010 may transmit the supply document token to the digital wallet corresponding to the owner of each supply document.

At 1150, the token server system 1010 may receive a demand document containing specifications for the desired transaction. For example, the demand document may list specifications for goods, services, or real estate. The user may be searching for a new car and may enter prices and / or other details related to the desired car. In some embodiments, the user may be searching for a babysitter service and may provide specifications such as the desired years of experience. These users may generate a demand document via the token server system 1010 to provide this information.

At 1155, the token server system 1010 may create a demand document token corresponding to the demand document. The token server system 1010 may create a document token of this type similar to the other document tokens described above. At 1160, the token server system 1010 may transmit or transfer the demand document token to the digital wallet. This transmission may occur like any other transfer of a document token to a digital wallet as described above. In some embodiments, the digital wallet may accommodate the user generating the demand document.

At 1165, the token server system 1010 may analyze the contents of the demand document to identify the specification. For example, the token server system 1010 may identify the field values corresponding to the contents of the demand document. For example, the demand document may be a fillable form and the values may be extracted. In some embodiments, the token server system 1010 may use an optical character recognition application and / or a machine learning algorithm to identify semantic information corresponding to the specification.

At 1170, the token server system 1010 may identify a supply document among a plurality of supply documents, including content corresponding to the specifications of the demand document. Based on the analysis of the specification, the token server system 1010 may identify one or more matching and / or nearly matching supply documents containing content that meets the criteria of the specification. For example, the supply document may include the price or years of experience of the property that meets the criteria of the demand document. The token server system 1010 may perform the matching based on the extracted fields of the demand document and comparable fields from the supply document. In some embodiments, the token server system 1010 may identify searchable fields within the metadata layer corresponding to the supply document and / or the supply document token. In some embodiments, the token server system 1010 may utilize machine learning techniques to analyze the feed document and identify matching or near matching based on the configuration and / or training of the machine learning algorithm. The token server system 1010 may notify the owners of the identified supply documents that those particular supply documents have been selected.

At 1175, the token server system 1010 may transmit or transfer the supply document token corresponding to the identified supply document to the digital wallet. As described above, the digital wallet may accommodate the user providing the demand document. The token server system 1010 may transmit the supply document token in a manner similar to that described above. By transmitting the supply document token, the user corresponding to the digital wallet may view the supply document. This permission may be identified due to the inclusion of the Supply Document Token in the digital wallet. In some embodiments, the token server system 1010 may ensure that the confidentiality designation provides permission to share the supply document with the user providing the demand document. As described above, this configuration of receiving offer documents may help facilitate a demand-driven trading system.

Various embodiments may be implemented using one or more well-known computer systems, such as the computer system 1200 shown in FIG. One or more computer systems 1200 may be used, for example, to implement any of the embodiments discussed herein and their combinations and secondary combinations.

The computer system 1200 may include one or more processors (also referred to as a central processing unit or CPU) such as processor 1204. Processor 1204 may be connected to the communications infrastructure or bus 1206.

The computer system 1200 may also include user input / output devices 1203 such as monitors, keyboards, pointing devices, etc., which may communicate with the communication infrastructure 1206 through the user input / output interface 1202.

One or more of the processors 1204 may be a graphics processing unit (GPU). In certain embodiments, the GPU may be a processor, which is a dedicated electronic circuit designed to handle mathematically intensive applications. The GPU may have a parallel structure that is efficient for parallel processing of large amounts of data such as mathematically intensive data common to computer graphics applications, images, videos and the like.

The computer system 1200 may also include primary or primary memory 1208 such as random access memory (RAM). The primary memory 1208 may include one or more levels of cache. The primary memory 1208 may store control logic (ie, computer software) and / or data therein.

The computer system 1200 may also include one or more secondary storage devices or memory 1210. The secondary memory 1210 may include, for example, a hard disk drive 1212 and / or a removable storage device or drive 1214. The removable storage drive 1214 may be a floppy disk drive, a magnetic tape drive, a compact disk drive, an optical storage device, a tape backup device, and / or any other storage device / drive.

The removable storage drive 1214 may interact with the removable storage unit 1218. The removable storage unit 1218 may include computer software (control logic) and / or a computer-enabled or readable storage device that stores data on it. The removable storage unit 1218 may be a floppy disk, magnetic tape, compact disk, DVD, optical storage disk, and / or any other computer data storage device. The removable storage drive 1214 may read from and / or write to the removable storage unit 1218.

Secondary memory 1210 may include other means, devices, components, appliances, or other approaches to allow computer programs and / or other instructions and / or data to be accessed by the computer system 1200. good. Such means, devices, components, instruments, or other approaches may include, for example, removable storage units 1222 and interfaces 1220. Examples of removable storage units 1222 and interfaces 1220 include program cartridges and cartridge interfaces (such as those found in video game devices), removable memory chips (such as EPROM or PROM) and associated sockets, memory sticks and USB ports, memory cards. And an associated memory card slot, and / or any other removable storage unit and associated interface.

The computer system 1200 may further include a communication or network interface 1224. The communication interface 1224 allows the computer system 1200 to communicate and interact with any combination of external devices, external networks, external entities, etc. (referred to individually and collectively by reference number 1228). You may. For example, the communication interface 1224 may be external or via a communication path 1226 where the computer system 1200 may be wired and / or wireless (or a combination thereof) and may include any combination such as LAN, WAN, Internet and the like. It may be possible to communicate with the remote device 1228. Control logic and / or data may be transmitted to and from computer system 1200 via communication path 1226.

The computer system 1200 also includes personal digital assistants (PDAs), desktop workstations, laptop or notebook computers, netbooks, tablets, smartphones, smartwatches or other wearables, to name a few non-limiting examples. It may be any of household appliances, Internet of Things parts, and / or buried systems, or any combination thereof.

The computer system 1200 includes, but is not limited to, remote or distributed cloud computing solutions, local or on-premises software (“on-premises” cloud-based solutions), “as a service” models (eg, software as a service (CaaS), services). Digital Content as a Service (DCaaS), Software as a Service (Software as a Service), Management Software as a Service (MSAAS), Platform as a Service (PaaS), Desktop as a Service (DaaS), Framework as a Service (FaaS), Includes backend as a service (Software as a Service), mobile backend as a service (MBaaS), infrastructure as a service (Software as a Service), etc.), and / or any combination of the aforementioned embodiments or other services or delivery paradigms. It may be a client or server that accesses or hosts any application and / or data through any delivery paradigm, including a hybrid model.

Any applicable data structure, file format, and schema within computer system 400 is, but is not limited to, JavaScript object notation (JSON), extensible markup language (XML), and another markup language (XML). YAML), extensible hypertext markup language (XHTML), wireless markup language (WML), MessagePack, XML user interface language (XUL), or any other functionally similar representation, alone or in combination. It may be derived from the included standard. Alternatively, dedicated data structures, formats, or schemas may be used either exclusively or in combination with publicly known or open standards.

In some embodiments, a tangible non-transient device or product comprising a tangible non-transient computer usable or readable medium having control logic (software) stored on it is also described herein. , Can be referred to as a computer program product or program storage device. This includes, but is not limited to, computer systems 1200, primary memory 1208, secondary memory 1210, and removable storage units 1218 and 1222, and tangible artifacts that embody any combination described above. When such control logic is executed by one or more data processing devices (computer system 1200, etc.), such data processing devices may be operated as described herein.

Based on the teachings contained in this disclosure, one of ordinary skill in the art will appreciate how to make and use embodiments of the present disclosure using data processing devices, computer systems, and / or computer architectures other than those shown in FIG. It will be obvious. In particular, embodiments may operate with software, hardware, and / or operating system implementations other than those described herein.

It should be understood that the detailed description section, rather than any other section, is intended to be used to interpret the claims. Other sections may describe one or more exemplary embodiments, but not all, as considered by the inventor, thus limiting the claims disclosed or attached in any way. Intended not to.

It should be understood that the present disclosure describes exemplary embodiments for exemplary fields and uses, but the present disclosure is not limited thereto. Other embodiments and modifications thereof are considered possible and are within the scope and spirit of the present disclosure. For example, without limiting the generality of this paragraph, embodiments are not limited to the software, hardware, firmware, and / or entities illustrated and / or described herein. Moreover, embodiments (whether or not expressly described herein) have significant utility in fields and uses other than those described herein.

Embodiments have been described herein with functional structural blocks illustrating implementation of the defined functions and their relationships. The boundaries of these functional structural blocks have been arbitrarily defined herein for convenience of explanation. Alternative boundaries can be defined as long as the defined functions and relationships (or their equivalents) are properly implemented. Also, alternative embodiments can implement functional blocks, steps, actions, methods, etc. using a different order than that described herein.

References to "one embodiment," "an embodiment," "an exemplary embodiment," or similar terms herein may include specific features, structures, or properties in the embodiments described. However, it is shown that not all embodiments may necessarily include specific features, structures, or properties. Moreover, such terms do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or property is described in connection with an embodiment, such feature, structure, or, whether expressly referred to or described herein. It will be within the knowledge of one of ordinary skill in the art to incorporate the property into other embodiments. In addition, some embodiments can be described using the expressions "combined" and "connected", along with their derivatives. These terms are not necessarily intended as synonyms for each other. For example, in some embodiments, the terms "connected" and / or "combined" are used to indicate that two or more elements are in direct physical or electrical contact with each other. Can be explained using. However, the term "combined" can also mean that two or more elements are not in direct contact with each other, but still work or interact with each other.

The scope and scope of this disclosure should not be limited by any of the exemplary embodiments described above, but should be defined only in accordance with the following claims and their equivalents.

The token server system may also use the technical features described in this disclosure to provide a demand-driven value chain. Demand-driven value chains can allow parties with a certain demand to generate documents in industries that traditionally utilize supply-driven trading marketplaces. For example, the buyer may generate an offer and / or an offer document, the seller may generate a sales document, and / or the buyer's agent may generate an offer document on behalf of its client. good. For example, a traditional online retailer may list items and receive purchase orders from buyers. In a demand-driven value chain, a buyer may submit an offer for goods, services, and / or real estate, even if the seller does not provide the list. In this way, the token server system may facilitate offers, counter-offers, and / or negotiations between the parties, regardless of role or account type. Buyers and / or sellers may initiate transactions. In addition, different parties and / or account types such as businesses, stores, entities, and / or consumers may use demand-driven value chains to initiate and / or facilitate transactions using blockchain integrity. good. In this way, the token server system may use the blockchain to support a decentralized marketplace for transactions.
The present invention provides, for example,:
(Item 1)
It ’s a computer implementation method.
Receiving document creation requests from user accounts that support digital wallets
To facilitate the creation of documents and
Encrypting and storing an encrypted version of the document
Creating a link to the encrypted version of the document
Generating a cryptographic hash of the document
Creating a document token corresponding to the document
To transmit the document token to the digital wallet and
To expose the link and the cryptographic hash to the blockchain using one or more smart contract functions.
Computer implementation methods, including.
(Item 2)
Receiving a confidentiality designation for the document that indicates the conditions under which the party attempting to access the document is exposed to the document.
To associate the confidentiality designation with the document via the metadata corresponding to the document.
The computer mounting method according to item 1, further comprising.
(Item 3)
Receiving some modifications to the document and generating the modifications,
To encrypt and store the encrypted version of the modified document,
Creating a second link that corresponds to the encrypted version of the modified document,
To generate a second cryptographic hash corresponding to the modified document,
To expose the second link and the second cryptographic hash to the blockchain using one or more smart contract functions.
The computer mounting method according to item 1, further comprising.
(Item 4)
Creating a second document token corresponding to the modified document,
To transmit the second document token to the digital wallet
The computer mounting method according to item 3, further comprising.
(Item 5)
The digital wallet corresponds to a first user account, the modifications are received from a second user account, and the method further addresses the document token to a second digital wallet corresponding to the second user account. The computer mounting method according to item 3, which comprises transmitting to.
(Item 6)
To generate a graphical user interface (GUI) that displays a first set of segmented portions of the document and a second set of segmented portions of the document, the first set and the second set. The set corresponds to the same segmented portion of the document.
The computer mounting method according to item 1, further comprising.
(Item 7)
To facilitate modification of the document from a first user through a first set of segmented portions.
Displaying modifications from a second user in the second set of segmented parts
The computer mounting method according to item 6, further comprising.
(Item 8)
It ’s a system,
Memory and
At least one processor coupled to the memory, said at least one processor.
Receiving document creation requests from user accounts that support digital wallets
To facilitate the creation of documents and
Encrypting and storing an encrypted version of the document
Creating a link to the encrypted version of the document
Generating a cryptographic hash of the document
Creating a document token corresponding to the document
To transmit the document token to the digital wallet and
To expose the link and the cryptographic hash to the blockchain using one or more smart contract functions.
With at least one processor configured to do
The system.
(Item 9)
The at least one processor further
Receiving a confidentiality designation for the document that indicates the conditions under which the party attempting to access the document is exposed to the document.
To associate the confidentiality designation with the document via the metadata corresponding to the document.
8. The system according to item 8, wherein the system is configured to perform the above.
(Item 10)
The at least one processor further
Receiving some modifications to the document and generating the modifications,
To encrypt and store the encrypted version of the modified document,
Creating a second link that corresponds to the encrypted version of the modified document,
To generate a second cryptographic hash corresponding to the modified document,
To expose the second link and the second cryptographic hash to the blockchain using one or more smart contract functions.
8. The system according to item 8, wherein the system is configured to perform the above.
(Item 11)
At least one process is further
Creating a second document token corresponding to the modified document,
To transmit the second document token to the digital wallet
10. The system according to item 10, wherein the system is configured to perform the above.
(Item 12)
The digital wallet corresponds to a first user account, the modifications are received from a second user account, and at least one process further associates the document token with a second user account corresponding to the second user account. Transmit to digital wallet
Item 10. The system according to item 10.
(Item 13)
The at least one processor is further configured to generate a graphical user interface (GUI) that displays a first set of segmented portions of the document and a second set of segmented portions of the document. The system of item 8, wherein one set and the second set correspond to the same segmented portion of the document.
(Item 14)
The at least one processor further
To facilitate modification of the document from a first user through a first set of segmented portions.
Displaying modifications from a second user in the second set of segmented parts
13. The system according to item 13, wherein the system is configured to perform the above.
(Item 15)
A non-transient computer readable device, said non-transient computer readable device, having instructions stored on it, said at least when the instructions are executed by at least one computing device. In one computing device
Receiving document creation requests from user accounts that support digital wallets
To facilitate the creation of documents and
Encrypting and storing an encrypted version of the document
Creating a link to the encrypted version of the document
Generating a cryptographic hash of the document
Creating a document token corresponding to the document
To transmit the document token to the digital wallet and
To expose the link and the cryptographic hash to the blockchain using one or more smart contract functions.
A non-transient computer-readable device that performs actions including.
(Item 16)
The above operation further
Receiving a confidentiality designation for the document that indicates the conditions under which the party attempting to access the document is exposed to the document.
To associate the confidentiality designation with the document via the metadata corresponding to the document.
15. The non-transient computer readable device according to item 15.
(Item 17)
The above operation further
Receiving some modifications to the document and generating the modifications,
To encrypt and store the encrypted version of the modified document,
Creating a second link that corresponds to the encrypted version of the modified document,
To generate a second cryptographic hash corresponding to the modified document,
To expose the second link and the second cryptographic hash to the blockchain using one or more smart contract functions.
15. The non-transient computer readable device according to item 15.
(Item 18)
The above operation further
Creating a second document token corresponding to the modified document,
To transmit the second document token to the digital wallet
17. A non-transient computer-readable device according to item 17.
(Item 19)
The digital wallet corresponds to a first user account, the modifications are received from a second user account, and the action further corresponds to the document token to a second digital wallet corresponding to the second user account. The non-transient computer readable device according to item 17, wherein the non-transient computer readable device comprises transmitting to.
(Item 20)
The above operation further
To generate a graphical user interface (GUI) that displays a first set of segmented portions of the document and a second set of segmented portions of the document, the first set and the second set. The set corresponds to the same segmented portion of the document.
To facilitate modification of the document from a first user through a first set of segmented portions.
Displaying modifications from a second user in the second set of segmented parts
15. The non-transient computer readable device according to item 15.
(Item 21)
It ’s a computer implementation method.
Generating a graphical user interface (GUI) that contains the icons used to initiate the link generation process, and
Receiving the interaction with the icon and
Generating an interface for attaching one or more documents to a link,
Receiving an indication to attach one or more documents to the link via the GUI.
Generating a document token for each of the one or more documents, the document token being deposited in a digital wallet indicating ownership of each of the one or more documents.
Publishing blockchain links to one or more of the above documents on the blockchain,
To generate a message corresponding to the link, the message includes the blockchain link and a document action button used to initiate the document generation process.
Computer implementation methods, including.
(Item 22)
21. The computer implementation method of item 21, further comprising generating a second GUI for managing one or more links.
(Item 23)
21. The computer implementation method of item 21, wherein the link generation process includes a prompt displayed on the GUI.
(Item 24)
To encrypt and store each encrypted version of one or more of the documents.
Creating a blockchain link to each encrypted version of one or more of the documents mentioned above,
To generate a cryptographic hash for each of the above one or more documents
21. The computer mounting method according to item 21.
(Item 25)
Identifying the interaction with the document action button
To facilitate the document generation process, generate response documents,
To transmit the response document and display it on the GUI.
21. The computer mounting method according to item 21.
(Item 26)
25. The computer implementation method of item 25, wherein the response document comprises a digital signature.
(Item 27)
25. The computer implementation method of item 25, further comprising publishing the response document on the blockchain.
(Item 28)
It ’s a system,
Memory and
At least one processor coupled to the memory, said at least one processor.
Generating a graphical user interface (GUI) that contains the icons used to initiate the link generation process, and
Receiving the interaction with the icon and
Generating an interface for attaching one or more documents to a link,
Receiving an indication to attach one or more documents to the link via the GUI.
Generating a document token for each of the one or more documents, the document token being deposited in a digital wallet indicating ownership of each of the one or more documents.
Publishing blockchain links to one or more of the above documents on the blockchain,
To generate a message corresponding to the link, the message includes the blockchain link and a document action button used to initiate the document generation process.
With at least one processor configured to do
The system.
(Item 29)
28. The system of item 28, wherein the at least one processor is further configured to generate a second GUI for managing one or more links.
(Item 30)
28. The system of item 28, wherein the link generation process includes a prompt displayed on the GUI.
(Item 31)
The at least one processor further
To encrypt and store each encrypted version of one or more of the documents.
Creating a blockchain link to each encrypted version of one or more of the documents mentioned above,
To generate a cryptographic hash for each of the above one or more documents
28. The system of item 28, which is configured to do so.
(Item 32)
The at least one processor further
Identifying the interaction with the document action button
To facilitate the document generation process, generate response documents,
To transmit the response document and display it on the GUI.
28. The system of item 28, which is configured to do so.
(Item 33)
32. The system of item 32, wherein the response document comprises a digital signature.
(Item 34)
32. The system of item 32, wherein the at least one processor is further configured to publish the response document on the blockchain.
(Item 35)
A non-transient computer readable device, said non-transient computer readable device, having instructions stored on it, said at least when the instructions are executed by at least one computing device. In one computing device
Generating a graphical user interface (GUI) that contains the icons used to initiate the link generation process, and
Receiving the interaction with the icon and
Generating an interface for attaching one or more documents to a link,
Receiving an indication to attach one or more documents to the link via the GUI.
Generating a document token for each of the one or more documents, the document token being deposited in a digital wallet indicating ownership of each of the one or more documents.
Publishing blockchain links to one or more of the above documents on the blockchain,
To generate a message corresponding to the link, the message includes the blockchain link and a document action button used to initiate the document generation process.
A non-transient computer-readable device that performs actions including.
(Item 36)
35. The non-transient computer readable device of item 35, wherein the operation further comprises generating a second GUI for managing one or more links.
(Item 37)
35. The non-transient computer readable device of item 35, wherein the link generation process includes a prompt displayed on the GUI.
(Item 38)
The above operation further
To encrypt and store each encrypted version of one or more of the documents.
Creating a blockchain link to each encrypted version of one or more of the documents mentioned above,
To generate a cryptographic hash for each of the above one or more documents
35. The non-transient computer readable device according to item 35.
(Item 39)
The above operation further
Identifying the interaction with the document action button
To facilitate the document generation process, generate response documents,
To transmit the response document and display it on the GUI,
To publish the response document on the blockchain
35. The non-transient computer readable device according to item 35.
(Item 40)
The non-transient computer-readable device of item 39, wherein the response document comprises a digital signature.
(Item 41)
It ’s a computer implementation method.
Receiving a document creation request from a first account corresponding to a first digital wallet, the first account corresponding to a first account type.
To facilitate the creation of the first document and
Creating a document token corresponding to the first document and
Transmission of the document token to the first digital wallet and
Using one or more smart contract functions to expose a hash of the first document and a link to an encrypted version of the first document to the blockchain.
By transmitting the notification to the second account corresponding to the second digital wallet, the second account corresponds to a second account type different from the first account type.
To facilitate the creation of a second document by the second account
Computer implementation methods, including.
(Item 42)
The computer implementation method according to item 41, wherein the first account type corresponds to a user account and the second account type corresponds to a store count.
(Item 43)
The computer implementation method according to item 41, wherein the first account type corresponds to a store count and the second account type corresponds to a user account.
(Item 44)
The computer implementation method according to item 41, wherein the second document is a modified version of the first document.
(Item 45)
The computer implementation method according to item 41, wherein the second document is a counter-offer document.
(Item 46)
The computer implementation method of item 41, wherein the second document comprises a digital signature.
(Item 47)
41. The computer implementation method of item 41, further comprising transmitting the document token to the second digital wallet.
(Item 48)
It ’s a system,
Memory and
At least one processor coupled to the memory, said at least one processor.
Receiving a document creation request from a first account corresponding to a first digital wallet, the first account corresponding to a first account type.
To facilitate the creation of the first document and
Creating a document token corresponding to the first document and
Transmission of the document token to the first digital wallet and
Using one or more smart contract functions to expose a hash of the first document and a link to an encrypted version of the first document to the blockchain.
By transmitting the notification to the second account corresponding to the second digital wallet, the second account corresponds to a second account type different from the first account type.
To facilitate the creation of a second document by the second account
With at least one processor configured to do
The system.
(Item 49)
The system according to item 48, wherein the first account type corresponds to a user account and the second account type corresponds to a store count.
(Item 50)
The system according to item 48, wherein the first account type corresponds to a store count and the second account type corresponds to a user account.
(Item 51)
28. The system of item 48, wherein the second document is a modified version of the first document.
(Item 52)
The system according to item 48, wherein the second document is a counter-offer document.
(Item 53)
The system of item 48, wherein the second document comprises a digital signature.
(Item 54)
28. The system of item 48, wherein the at least one processor is further configured to transmit the document token to the second digital wallet.
(Item 55)
A non-transient computer readable device, said non-transient computer readable device, having instructions stored on it, said at least when the instructions are executed by at least one computing device. In one computing device
Receiving a document creation request from a first account corresponding to a first digital wallet, the first account corresponding to a first account type.
To facilitate the creation of the first document and
Creating a document token corresponding to the first document and
Transmission of the document token to the first digital wallet and
Using one or more smart contract functions to expose a hash of the first document and a link to an encrypted version of the first document to the blockchain.
By transmitting the notification to the second account corresponding to the second digital wallet, the second account corresponds to a second account type different from the first account type.
To facilitate the creation of a second document by the second account
A non-transient computer-readable device that performs actions including.
(Item 56)
The non-transient computer readable device of item 55, wherein the first account type corresponds to a user account and the second account type corresponds to a store count.
(Item 57)
The non-transient computer readable device of item 55, wherein the first account type corresponds to a store count and the second account type corresponds to a user account.
(Item 58)
The non-transient computer-readable device according to item 55, wherein the second document is a modified version of the first document.
(Item 59)
The non-transient computer-readable device according to item 55, wherein the second document is a counter-offer document.
(Item 60)
The second document is the non-transient computer readable device of item 55, which comprises a digital signature.
(Item 61)
It ’s a computer implementation method.
To generate a message corresponding to a document action button, which, when pressed, initiates a document generation process.
When the document generation process is started,
Generating a document token for a document corresponding to the message, the document token being deposited in a digital wallet indicating ownership of the document.
To publish the above document on the blockchain
Computer implementation methods, including.
(Item 62)
It ’s a computer implementation method.
Generating an interface for attaching documents to links,
To generate a document token for the document, the document token is deposited in a digital wallet indicating ownership of the document.
Publishing the blockchain link to the document on the blockchain and
To generate a message corresponding to the link, that the message includes the blockchain link.
Computer implementation methods, including.

Claims (62)

It ’s a computer implementation method.
Receiving document creation requests from user accounts that support digital wallets
To facilitate the creation of documents and
Encrypting and storing an encrypted version of the document
Creating a link to the encrypted version of the document
Generating a cryptographic hash of the document
Creating a document token corresponding to the document
To transmit the document token to the digital wallet and
A computer implementation method comprising exposing the link and the cryptographic hash to the blockchain using one or more smart contract functions. Receiving a confidentiality designation for the document that indicates the conditions under which the party attempting to access the document is exposed to the document.
The computer implementation method of claim 1, further comprising associating the confidentiality designation with the document via metadata corresponding to the document. Receiving some modifications to the document and generating the modifications,
To encrypt and store the encrypted version of the modified document,
Creating a second link that corresponds to the encrypted version of the modified document,
To generate a second cryptographic hash corresponding to the modified document,
The computer implementation method according to claim 1, further comprising exposing the second link and the second cryptographic hash to the blockchain using one or more smart contract functions. Creating a second document token corresponding to the modified document,
The computer implementation method according to claim 3, further comprising transmitting the second document token to the digital wallet. The digital wallet corresponds to a first user account, the modifications are received from a second user account, and the method further addresses the document token to a second digital wallet corresponding to the second user account. The computer mounting method according to claim 3, which comprises transmitting to. To generate a graphical user interface (GUI) that displays a first set of segmented portions of the document and a second set of segmented portions of the document, the first set and the second set. The computer implementation method of claim 1, wherein the set corresponds to the same segmented portion of the document. To facilitate modification of the document from a first user through a first set of segmented portions.
The computer implementation method of claim 6, further comprising displaying modifications from a second user in a second set of segmented portions. It ’s a system,
Memory and
At least one processor coupled to the memory, said at least one processor.
Receiving document creation requests from user accounts that support digital wallets
To facilitate the creation of documents and
Encrypting and storing an encrypted version of the document
Creating a link to the encrypted version of the document
Generating a cryptographic hash of the document
Creating a document token corresponding to the document
To transmit the document token to the digital wallet and
A system comprising at least one processor configured to expose the link and the cryptographic hash to the blockchain using one or more smart contract functions. The at least one processor further
Receiving a confidentiality designation for the document that indicates the conditions under which the party attempting to access the document is exposed to the document.
The system of claim 8, wherein the confidentiality designation is associated with the document via metadata corresponding to the document. The at least one processor further
Receiving some modifications to the document and generating the modifications,
To encrypt and store the encrypted version of the modified document,
Creating a second link that corresponds to the encrypted version of the modified document,
To generate a second cryptographic hash corresponding to the modified document,
The system according to claim 8, wherein one or more smart contract functions are used to expose the second link and the second cryptographic hash to the blockchain. At least one process is further
Creating a second document token corresponding to the modified document,
10. The system of claim 10, configured to transmit the second document token to the digital wallet. The digital wallet corresponds to a first user account, the modifications are received from a second user account, and at least one process further associates the document token with a second user account corresponding to the second user account. The system of claim 10, configured to transmit to a digital wallet. The at least one processor is further configured to generate a graphical user interface (GUI) that displays a first set of segmented portions of the document and a second set of segmented portions of the document. The system of claim 8, wherein one set and the second set correspond to the same segmented portion of the document. The at least one processor further
To facilitate modification of the document from a first user through a first set of segmented portions.
13. The system of claim 13, configured to display modifications from a second user in a second set of segmented portions. A non-transient computer readable device, said non-transient computer readable device, having instructions stored on it, said at least when the instructions are executed by at least one computing device. In one computing device
Receiving document creation requests from user accounts that support digital wallets
To facilitate the creation of documents and
Encrypting and storing an encrypted version of the document
Creating a link to the encrypted version of the document
Generating a cryptographic hash of the document
Creating a document token corresponding to the document
To transmit the document token to the digital wallet and
A non-transient computer-readable device that uses one or more smart contract functions to perform operations, including exposing the link and the cryptographic hash to the blockchain. The above operation further
Receiving a confidentiality designation for the document that indicates the conditions under which the party attempting to access the document is exposed to the document.
The non-transient computer-readable device of claim 15, comprising associating the confidentiality designation with the document via metadata corresponding to the document. The above operation further
Receiving some modifications to the document and generating the modifications,
To encrypt and store the encrypted version of the modified document,
Creating a second link that corresponds to the encrypted version of the modified document,
To generate a second cryptographic hash corresponding to the modified document,
The non-transient computer-readable device of claim 15, comprising using one or more smart contract functions to expose the second link and the second cryptographic hash to the blockchain. The above operation further
Creating a second document token corresponding to the modified document,
The non-transient computer-readable device of claim 17, comprising transmitting the second document token to the digital wallet. The digital wallet corresponds to a first user account, the modifications are received from a second user account, and the action further corresponds to the document token to a second digital wallet corresponding to the second user account. The non-transient computer readable device according to claim 17, wherein the non-transient computer readable device comprises transmitting to. The above operation further
To generate a graphical user interface (GUI) that displays a first set of segmented portions of the document and a second set of segmented portions of the document, the first set and the second set. The set corresponds to the same segmented portion of the document.
To facilitate modification of the document from a first user through a first set of segmented portions.
The non-transient computer-readable device of claim 15, comprising displaying modifications from a second user in a second set of segmented portions. It ’s a computer implementation method.
Generating a graphical user interface (GUI) that contains the icons used to initiate the link generation process, and
Receiving the interaction with the icon and
Generating an interface for attaching one or more documents to a link,
Receiving an indication to attach one or more documents to the link via the GUI.
Generating a document token for each of the one or more documents, the document token being deposited in a digital wallet indicating ownership of each of the one or more documents.
Publishing blockchain links to one or more of the above documents on the blockchain,
A computer implementation method of generating a message corresponding to the link, the message comprising the blockchain link and a document action button used to initiate the document generation process. .. 21. The computer implementation method of claim 21, further comprising generating a second GUI for managing one or more links. 21. The computer implementation method of claim 21, wherein the link generation process includes a prompt displayed on the GUI. To encrypt and store each encrypted version of one or more of the documents.
Creating a blockchain link to each encrypted version of one or more of the documents mentioned above,
21. The computer implementation method of claim 21, further comprising generating a cryptographic hash of each of the one or more documents. Identifying the interaction with the document action button
To facilitate the document generation process, generate response documents,
The computer implementation method according to claim 21, further comprising transmitting the response document and displaying it on the GUI. 25. The computer implementation method of claim 25, wherein the response document comprises a digital signature. 25. The computer implementation method of claim 25, further comprising publishing the response document on the blockchain. It ’s a system,
Memory and
At least one processor coupled to the memory, said at least one processor.
Generating a graphical user interface (GUI) that contains the icons used to initiate the link generation process, and
Receiving the interaction with the icon and
Generating an interface for attaching one or more documents to a link,
Receiving an indication to attach one or more documents to the link via the GUI.
Generating a document token for each of the one or more documents, the document token being deposited in a digital wallet indicating ownership of each of the one or more documents.
Publishing blockchain links to one or more of the above documents on the blockchain,
To generate a message corresponding to the link, the message is configured to include the blockchain link and a document action button used to initiate the document generation process. A system with at least one processor. 28. The system of claim 28, wherein the at least one processor is further configured to generate a second GUI for managing one or more links. 28. The system of claim 28, wherein the link generation process includes a prompt displayed on the GUI. The at least one processor further
To encrypt and store each encrypted version of one or more of the documents.
Creating a blockchain link to each encrypted version of one or more of the documents mentioned above,
28. The system of claim 28, configured to generate a cryptographic hash of each of the one or more documents. The at least one processor further
Identifying the interaction with the document action button
To facilitate the document generation process, generate response documents,
28. The system of claim 28, configured to transmit the response document and display it on the GUI. 32. The system of claim 32, wherein the response document comprises a digital signature. 32. The system of claim 32, wherein the at least one processor is further configured to publish the response document on the blockchain. A non-transient computer readable device, said non-transient computer readable device, having instructions stored on it, said at least when the instructions are executed by at least one computing device. In one computing device
Generating a graphical user interface (GUI) that contains the icons used to initiate the link generation process, and
Receiving the interaction with the icon and
Generating an interface for attaching one or more documents to a link,
Receiving an indication to attach one or more documents to the link via the GUI.
Generating a document token for each of the one or more documents, the document token being deposited in a digital wallet indicating ownership of each of the one or more documents.
Publishing blockchain links to one or more of the above documents on the blockchain,
Generating a message corresponding to the link, the message causing an action including including the blockchain link and a document action button used to initiate the document generation process. , Non-transient computer readable device. The non-transient computer-readable device of claim 35, wherein the operation further comprises generating a second GUI for managing one or more links. The non-transient computer-readable device of claim 35, wherein the link generation process includes a prompt displayed on the GUI. The above operation further
To encrypt and store each encrypted version of one or more of the documents.
Creating a blockchain link to each encrypted version of one or more of the documents mentioned above,
The non-transient computer-readable device of claim 35, comprising generating a cryptographic hash of each of the one or more documents. The above operation further
Identifying the interaction with the document action button
To facilitate the document generation process, generate response documents,
To transmit the response document and display it on the GUI,
The non-transient computer-readable device of claim 35, comprising publishing the response document on the blockchain. The non-transient computer-readable device of claim 39, wherein the response document comprises a digital signature. It ’s a computer implementation method.
Receiving a document creation request from a first account corresponding to a first digital wallet, the first account corresponding to a first account type.
To facilitate the creation of the first document and
Creating a document token corresponding to the first document and
Transmission of the document token to the first digital wallet and
Using one or more smart contract functions to expose a hash of the first document and a link to an encrypted version of the first document to the blockchain.
By transmitting the notification to the second account corresponding to the second digital wallet, the second account corresponds to a second account type different from the first account type.
A computer implementation method comprising facilitating the creation of a second document by the second account. The computer implementation method according to claim 41, wherein the first account type corresponds to a user account and the second account type corresponds to a store count. The computer implementation method according to claim 41, wherein the first account type corresponds to a store count and the second account type corresponds to a user account. The computer implementation method according to claim 41, wherein the second document is a modified version of the first document. The computer implementation method according to claim 41, wherein the second document is a counter-offer document. The computer implementation method of claim 41, wherein the second document comprises a digital signature. 41. The computer implementation method of claim 41, further comprising transmitting the document token to the second digital wallet. It ’s a system,
Memory and
At least one processor coupled to the memory, said at least one processor.
Receiving a document creation request from a first account corresponding to a first digital wallet, the first account corresponding to a first account type.
To facilitate the creation of the first document and
Creating a document token corresponding to the first document and
Transmission of the document token to the first digital wallet and
Using one or more smart contract functions to expose a hash of the first document and a link to an encrypted version of the first document to the blockchain.
By transmitting the notification to the second account corresponding to the second digital wallet, the second account corresponds to a second account type different from the first account type.
A system comprising at least one processor configured to facilitate the creation of a second document by the second account. The system of claim 48, wherein the first account type corresponds to a user account and the second account type corresponds to a store count. The system of claim 48, wherein the first account type corresponds to a store count and the second account type corresponds to a user account. The system of claim 48, wherein the second document is a modified version of the first document. The system of claim 48, wherein the second document is a counter-offer document. The system of claim 48, wherein the second document comprises a digital signature. 48. The system of claim 48, wherein the at least one processor is further configured to transmit the document token to the second digital wallet. A non-transient computer readable device, said non-transient computer readable device, having instructions stored on it, said at least when the instructions are executed by at least one computing device. In one computing device
Receiving a document creation request from a first account corresponding to a first digital wallet, the first account corresponding to a first account type.
To facilitate the creation of the first document and
Creating a document token corresponding to the first document and
Transmission of the document token to the first digital wallet and
Using one or more smart contract functions to expose a hash of the first document and a link to an encrypted version of the first document to the blockchain.
By transmitting the notification to the second account corresponding to the second digital wallet, the second account corresponds to a second account type different from the first account type.
A non-transient computer-readable device that performs actions, including facilitating the creation of a second document by the second account. The non-transient computer-readable device of claim 55, wherein the first account type corresponds to a user account and the second account type corresponds to a store count. The non-transient computer-readable device of claim 55, wherein the first account type corresponds to a store count and the second account type corresponds to a user account. The non-transient computer-readable device of claim 55, wherein the second document is a modified version of the first document. The non-transient computer-readable device of claim 55, wherein the second document is a counter-offer document. The non-transient computer-readable device of claim 55, wherein the second document comprises a digital signature. It ’s a computer implementation method.
To generate a message corresponding to a document action button, which, when pressed, initiates a document generation process.
When the document generation process is started,
Generating a document token for a document corresponding to the message, the document token being deposited in a digital wallet indicating ownership of the document.
A computer implementation method, including publishing the document to the blockchain. It ’s a computer implementation method.
Generating an interface for attaching documents to links,
By generating a document token for the document, the document token is deposited in a digital wallet indicating ownership of the document.
Publishing the blockchain link to the document on the blockchain and
A computer implementation method comprising generating a message corresponding to the link, wherein the message includes the blockchain link.

Images