Smart Contracts
The system addresses the limitations of smart contracts by making them human-readable and integrating them into a collaborative platform, enhancing usability and transferability through Mithra tokens, thus improving efficiency and security in contract management.
Patent Information
- Application Number
- JP2021517210
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-09-30
- Filing Date
- 2019-09-30
- Publication Date
- 2026-02-06
- Estimated Expiration
- 2039-09-30
AI Technical Summary
Existing smart contracts lack human readability, limiting their usability and transferability, and traditional contracts are inefficient and difficult to track, verify, and apply advanced technologies like AI and analytics.
A system and method for creating, negotiating, and approving smart contracts that are both human-readable and machine-readable, using Mithra tokens to represent contract terms and integrate them into a collaborative and secure platform for distribution across networks, enabling efficient negotiation and management.
Enables human-readable smart contracts that are easily usable, consumable, and transferable, improving efficiency and usability while allowing integration with blockchain technology for secure and efficient contract management.
Smart Images

Figure 0007811846000015 
Figure 0007811846000016 
Figure 0007811846000017
Abstract
Description
[Technical Field]
[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims priority to Provisional Application No. 62 / 738,848, filed September 28, 2018, the entire disclosure of which is incorporated by reference at a minimum. FIELD OF THE INVENTION
[0002] The present invention relates to technology for processes for negotiating and implementing compliance regulations, contracts, and transactions, and more particularly to a new type of smart contract and system for integrating the parties involved in such contract types and their associated transactions into a collaborative and secure system and distributing this new type of contract across business and consumer networks. [Background technology]
[0003] Legal contracts have evolved slowly over the past millennia, and the technology to create, manage, and enforce them continues to be outdated.
[0004] Traditional contract systems for creating, reviewing, negotiating, signing, executing, publishing, and storing governing rules and contracts are time-consuming and wasteful. Contracts are presented in structured data formats, which is the vast majority of how so-called "digital" contracts are handled, making them difficult to track, verify, discover the terms therein, audit, or transfer. Additionally, this hinders progress in the world of contracts by making it impossible to properly apply technologies such as artificial intelligence and analytics.
[0005] In the 1990s, a new type of contract called a smart contract emerged. A smart contract is a computer protocol intended to digitally facilitate, verify, or enforce the negotiation or execution of a contract. Smart contracts enable trusted transactions to be conducted without a third party. Many provisions of a smart contract can be self-executing. For example, a smart contract may stipulate that a certain amount of digital currency should be transferred upon the occurrence of a specific condition. The smart contract may detect the occurrence of the condition and, upon detection, transfer the digital currency. These transactions are traceable and irreversible. Additionally, the encryption used by smart contracts ensures security, a key requirement for contract management in a digital world.
[0006] Smart contracts use a scripting language to define the rights and obligations of the parties. One exemplary scripting language for smart contracts is Solidity. Solidity is an object-oriented, high-level language that can control the behavior of accounts within the Ethereum blockchain. Solidity has been used to create smart contracts that are used to implement voting, crowdfunding, blind auctions, and multi-signature wallets.
[0007] While smart contracts in the art undoubtedly offer several distinct advantages over traditional contract technology, they fall short by not being presented in a manner that is human-readable. Because contracts are legally binding agreements that govern the rights and obligations of the parties to those agreements, human readability is the most important attribute of any contract technology. Without human readability, the uses of smart contracts are severely limited.
[0008] There was an attempt to combine cryptography and contracts when renowned financial cryptographer Ian Grigg invented Ricardian contracts in 1996. Ricardian contracts are a way to record documents as legal contracts and securely link them to other systems, such as accounting for contracts, as an issuance of value.
[0009] According to Grigg, "A Ricardian contract can be defined as a single document that: a) is a contract offered by an issuer to a holder; b) is for valuable rights held by the holder and controlled by the issuer; c) is easily readable by people (like a paper contract); d) is readable by computer programs (is parsable like a database); e) is digitally signed; f) contains key and server information; and g) is bound to a unique and secure identifier."
[0010] An important distinction exists between smart contracts and Ricardian contracts: while it is possible to implement a Ricardian contract as a smart contract, this does not mean that all Ricardian contracts are smart contracts. Therefore, not all smart contracts are Ricardian contracts. A smart contract refers to a type of digital compliant agreement that has already been agreed upon and can be automatically executed. On the other hand, a Ricardian contract follows a contract model that records the so-called "intent" of a particular contract and its "actions," regardless of whether they have been executed. Using hashes to reference external documents, Ricardian contracts can similarly reference code.
[0011] The advantages offered by Ricardian contracts include security, transparency, efficiency, and reliability, which are lacking in traditional written contracts, and human readability, which is lacking in smart contracts.
[0012] However, Ricardian contracts are not well known by the general public and only a few projects have attempted to implement them. One of the main challenges of Ricardian contracts is their lack of usability, consumability, and transferability. Like many great inventions, if no use or profitable activity is built around them, they will very quickly become forgotten or abandoned. Therefore, the following is clearly needed:
[0013] A new type of contract that uses smart contract techniques and is human-readable and consumable.
[0014] A high performance and robust revenue collaboration that allows this new type of contract to be easily usable, consumable, and transferable by users within the revenue collaboration. Summary of the Invention [Means for solving the problem]
[0015] In one embodiment of the present invention, there is provided a system for creating, negotiating, and approving smart contracts, the system comprising: an internet-connected server running software (SW) on a processor, the SW providing a web presence with an interactive interface; a data repository coupled to the server storing user information, contract templates, and completed contracts; a port to a blockchain service; a registration interface for registering users, each user in the registration being issued a digital blockchain wallet for either a personal account or a business account; and a communication service by which registered users communicate. A registered user initiates a smart contract either by manually writing it using an online editor or by accessing a smart contract template from a data repository; the new contract is submitted to the blockchain and associated with a Mithra token that defines all of the contract terms; with the issued token in effect, the contract issuer engages one or more counterparties to join the smart contract; the counterparties, upon active engagement, create counter tokens that define the rights and obligations under the contract for the counterparties; through a communication service, the initiator and counterparties negotiate the contract terms to reach an agreement; the contract is signed and published to either a public or private store.
[0016] In one embodiment, the contract is both human-readable and machine-readable. Also, in one embodiment, counterparties are invited to join the contract via a direct email or text invitation from the initiator. Also, in one embodiment, the issuer assigns user permissions to each invited counterparty, including, but not limited to, administrative privileges, view-only, edit and / or comment, or sign-only. In one embodiment, upon receiving the invitation via email or SMS, the invitee signs in to the system or registers if they are a first-time user.
[0017] In one embodiment, the initiator and counterparty negotiate the contract terms via a chat communication system, and the terms are codified in their respective Mithra tokens. Also, in one embodiment, the initiator and counterparty are each provided with a human-readable version of the smart contract, presented side-by-side so that each party can propose changes to the terms, which can be reviewed and accepted or challenged by the other party until agreement is reached. In one embodiment, the system further comprises a search function by which a user can search for templates in a data repository and select a template for initiating a contract. In one embodiment, the system further comprises a search function by which a user can search for published contracts and join the selected contract by submitting an offer or proposal. In one embodiment, when a user selects a contract within the search results, the user is presented with a submission form by which the user can enter the terms to be entered into the smart contract, and negotiation begins between the issuer and the submitting user. In one embodiment, a submitting user is issued a counter Mithra token that defines the rights and obligations for that user, where they are allowed to participate in the negotiation process.
[0018] In another aspect of the invention, a method for creating, negotiating, and approving smart contracts includes the steps of initiating a smart contract either by manually writing it in an online editor operated by software running on a processor of an internet-connected server providing a system of interactive interfaces or by accessing a smart contract template from a data repository coupled to the server; associating the new smart contract with Mithra tokens that define all of the contract terms by submitting the contract to a blockchain service; engaging counterparties to join the smart contract, who have issued counter Mithra tokens that define the rights and obligations for the counterparties; negotiating the smart contract terms towards agreement by the initiator and the counterparties using an online communication service; and signing the smart contract and publishing it to a public or private store.
[0019] In one embodiment, the method includes providing the contract in a human-readable and machine-readable manner. Also, in one embodiment, the method includes inviting counterparties to join the contract via direct email or text invitation from the initiator. In one embodiment, the method includes assigning user permissions to each invited counterparty, including, but not limited to, administrative privileges, view-only, edit and / or comment, or sign-only.
[0020] In one embodiment, the method includes the invitee signing in or registering with the system upon receiving the invitation via email or SMS. Also, in one embodiment, the method includes negotiating contract terms between the initiator and the counterparty via a chat communication system, where the terms are codified in their respective Mithra tokens. In one embodiment, the method includes providing human-readable versions of the smart contract presented side-by-side for the initiator and counterparty in a two-way interface so that each party may propose changes to the terms, which can be reviewed and accepted or challenged by the other party until agreement is reached.
[0021] In one embodiment, the method further includes a step in which a user searches for templates in a data repository using a search function and selects a template for initiating a contract. In one embodiment, the method further includes a step in which a user searches for published contracts using a search function and joins the selected contract by submitting an offer or proposal. In one embodiment, the method includes a step of presenting a submission form to the user, whereby the user may enter terms to be entered into the smart contract, wherein negotiation is initiated between the issuer and the submitting user. Also, in one embodiment, the method includes a step of issuing a counter Mithra token defining rights and obligations for the submitting user, wherein the submitting user is now admitted to the negotiation process. The present invention provides, for example, the following items. (Item 1) 1. A system for creating, negotiating, and approving smart contracts, the system comprising: an internet connected server running software (SW) on a processor, said SW providing a web presence with an interactive interface; a data repository coupled to the server that stores user information, contract templates, and completed contracts; Ports to blockchain services and a registration interface for registering users, each user being issued a digital blockchain wallet upon registration; Communication services and Equipped with The communication service allows registered users to communicate, A registered user initiates a smart contract by manually writing the smart contract using an online editor or by accessing a smart contract template from the data repository, and the new contract is submitted to a blockchain and associated with a token that defines the contract terms of the smart contract; Once an issued token is issued, the contract issuer engages one or more counterparties to join the smart contract, the counterparties, through their active participation, create counter tokens that define the rights and obligations under the smart contract for the counterparties, and through the communication service, the initiator and the counterparties negotiate contract terms for an agreement, and the smart contract is signed. (Item 2) Item 10. The system of item 1, wherein the smart contract is linked to a human-readable representation of the contract terms of the smart contract. (Item 3) Item 10. The system of item 1, wherein the counterparties are invited to join the smart contract by direct email or text invitation from the initiator. (Item 4) Item 4. The system of item 3, wherein the publisher assigns user permissions to each invited contract partner, including, but not limited to, administrative privileges, view only, edit and / or comment, or sign only. (Item 5) Upon receiving the invitation via email or SMS, the invitee may Item 4. The system of item 3, wherein the user signs in or, if a first-time user, registers. (Item 6) Item 6. The system of item 5, wherein the initiator and counterparty negotiate contract terms via a chat communication system, and the terms are codified in respective tokens. (Item 7) Item 5. The system of item 5, wherein the initiator and the counterparty are each provided with a human-readable version of the smart contract presented side-by-side, whereby each party may propose changes to terms that can be scrutinized and accepted or challenged by the other party until agreement is reached. (Item 8) 2. The system of claim 1, further comprising a search function whereby a user can search for templates within the data repository and select a template to initiate a contract. (Item 9) 2. The system of claim 1, further comprising a search function whereby a user can search published contracts and join a selected contract by submitting an offer or proposal. (Item 10) 10. The system of claim 9, wherein when a user selects a contract within the search results, a submission form is presented to the user, whereby the user may enter terms, which are entered into the smart contract, and negotiation begins between the issuer and the submitting user. (Item 11) Item 11. The system of item 10, wherein the submitting user is issued a counter token that defines rights and obligations for that user, whereby participation in the negotiation process is permitted. (Item 12) 1. A method for creating, negotiating, and approving smart contracts, the method comprising: Initiating a smart contract by manually authoring it using an online editor operated by software running on a processor of an internet-connected server providing a system of interactive interfaces, or by accessing a smart contract template from a data repository coupled to said server; Associating the new smart contract with a Mithra token that defines all of the contract terms by submitting the contract to a blockchain service; Involving counterparties in joining the smart contract, the counterparties issuing counter tokens that define rights and obligations for the counterparties; negotiating smart contract terms for agreement by the initiator and the counterparty using an online communication service; signing the smart contract and publishing it to a public or private store; A method comprising: (Item 13) Item 13. The method of item 12, comprising providing the contract to be both human-readable and machine-readable. (Item 14) Participating in a contract via a direct email or text invitation from the initiator Item 13. The method of item 12, including inviting the counterparty to participate. (Item 15) Item 15. The method of item 14, including assigning user permissions to each invited contract partner, including, but not limited to, administrative privileges, view only, edit and / or comment, or sign only. (Item 16) Item 15. The method of item 14, comprising signing in or registering with the system by the invitee upon receiving the invitation via email or SMS. (Item 17) Item 17. The method of item 16, comprising negotiating contract terms between the initiator and the counterparty via a chat communication system, the terms being codified in respective Mithra tokens. (Item 18) 17. The method of claim 16, further comprising providing a human-readable version of the smart contract presented side-by-side for the initiator and the counterparty in a two-way interface so that each party may propose changes to terms, which can be scrutinized and accepted or challenged by the other party until agreement is reached. (Item 19) Item 12. The method of item 11, further comprising a user searching for templates in the data repository via a search function and selecting a template to initiate a contract. (Item 20) Item 12. The method of item 11, further comprising a user searching for published contracts through a search function and joining a selected contract by submitting an offer or proposal. (Item 21) 21. The method of claim 20, comprising presenting a submission form to a user, whereby the user may enter terms, the terms being entered into the smart contract, and negotiation being initiated between the issuer and the submitting user. (Item 22) 22. The method of claim 21, further comprising issuing a counter Mithra token that defines rights and obligations for the submitting user, wherein the submitting user is now authorized to participate in the negotiation process. (Item 23) 1. A method of creating a human-readable smart contract, the method comprising: generating a smart contract including code in a scripting language, said code specifying terms that define rights and obligations of at least two parties; generating human readable text describing the terms of the smart contract; linking a first address defining the location of the smart contract with a second address defining the location of the human-readable text on the World Wide Web, whereby said linking enables readability of the smart contract; A method comprising: (Item 24) receiving, from a user, a selection of a template describing at least one clause, the template including a fixed portion and a variable portion; receiving a value for the variable portion from the user; further comprising Item 24. The method of item 23, wherein generating the human-readable text includes generating the code such that the code specifies the at least one clause according to the value, and generating the smart contract includes generating the human-readable text to explain the at least one clause according to the value. (Item 25) receiving an edit to the human readable text from one of the at least two parties, the edit modifying the value for the variable portion; amending the smart contract to specify the at least one clause with the modified value; and 25. The method of claim 24, further comprising: [Brief explanation of the drawings]
[0022] [Figure 1] FIG. 1 is a diagrammatic representation of a Mithra contract 101.
[0023] [Figure 2]FIG. 2 is an architecture diagram illustrating, at a high level, the system for the Mithra platform in one embodiment of the present invention.
[0024] [Figure 3] FIG. 3 illustrates one of many bidirectional interfaces that may be provided within a system domain in one embodiment of the present invention.
[0025] [Figure 4] FIG. 4 is a simplified example of an interactive interface within the system for creating, selecting, and editing templates in one embodiment of the present invention.
[0026] [Figure 5] FIG. 5 illustrates an interactive interface that allows a user to search for contracts, templates, and outstanding contracts stored in various collections within the system in one embodiment of the present invention.
[0027] [Figure 6] FIG. 6 illustrates an exemplary project overview dashboard for a user in one embodiment of the present invention.
[0028] [Figure 7] FIG. 7 is an example of a project details dashboard in one embodiment of the present invention.
[0029] [Figure 8] FIG. 8 illustrates a window that a user may invoke to invite others to join a contract in one embodiment of the present invention.
[0030] [Figure 9] FIG. 9 illustrates the results of a search for a contract in one embodiment of the present invention.
[0031] [Figure 10] FIG. 10 illustrates an interface that allows users to submit offers and enter into contracts in one embodiment of the present invention.
[0032] [Figure 11] FIG. 11 illustrates the side-by-side presentation of the same contract to two participants in one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION
[0033] The present invention consists of two main components: 1. A new type of smart contract, referred to herein as a Mithra contract.
[0034] 2. To integrate the parties involved in Mithra contracts and their associated transactions into a collaborative and secure system, and to smart A system for distributing contracts across business and consumer networks. (Mithra Contract)
[0035] Figure 1 is a schematic diagram of a Mithra contract 101. A Mithra contract (MC) is a contract that users can create that is both human-readable and machine-readable, legally binding, machine-executable and shareable by humans, and tokenized to enable transferability, traceability, tradeability, and portability. smart It is a new type of smart contract that allows contracts to be created, negotiated, and approved.
[0036] Unlike Ricardo contracts, human readability of Mithra contracts is achieved by creating a human-readable representation on the World Wide Web (WWW) of the smart contract underlying the MC. The smart contract underlying the MC is accessible through a link. A link is shown in Figure 1 on the left side of the diagram. A link is a unique, shareable address, which may be human-readable. A human-readable address can be resolved into a smart contract address, which identifies a location on a distributed ledger or blockchain. In contrast to a human-readable address, smart The contract address may be a long alphanumeric or hexadecimal number. In one embodiment, the human-readable address may identify the location on the World Wide Web of a human-readable version of the MC, for example, by including a uniform resource locator.
[0037] Human-readable addresses can be resolved into smart contract addresses using the Ethereum blockchain standard EIP / ERC181.8. Similarly, a reverse solution that allows for the lookup of human-readable addresses into smart contract addresses may be possible using the EIP / ERC181.8 standard. Thus, with Mithra contracts, authorized users can read the representation of a smart contract that is already presented on the blockchain in human-readable form by opening it in a compatible editor. Mithra contracts further allow for the determinism between the parties to the contract. smart By representing each clause or set of clauses defined within the contract as a special form of token called Mithra Token (MT), smart Tokenizing the contract: MT may specify both sections of code that define the terms of a smart contract and human-readable text that explains the terms. smartEach party involved in a contract—not only the parties to the contract, but also legal representatives, attorneys, agents, and other authorized parties—will hold Mithra tokens with their respective obligations, permissions, and rights. In FIG. 1, registered member 102a owns MT103a, which defines certain terms associated with that person. Another member 102b owns MT103b, which defines certain permissions and rights. The arrow joining the two illustrates the associated permissions and rights. As a simple example, MT103a may define the right for member 102a to collect monthly rent from member 102b, and thus MT103b would define the terms of the obligation to pay monthly rent imposed on member 102a by MT103a.
[0038] The complete set of terms represented by Mithra tokens are grouped together to form a Mithra group (MG). Thus, a Mithra contract can consist of a finite number of Mithra groups, each of which can consist of a finite number of Mithra tokens until it reaches a final state, which is triggered either by signatures from all required parties or when the contract terms are met between a single pair of tokens in the group. Each MT represents an asset that can have value because it is a set of rights and obligations; therefore, the owner of the MT can demand or pay money to change ownership of the MT. In Figure 1, several Mithra groups 104 are illustrated. Note that the members and tokens represented by 102x and 103x are not necessarily separate from the group, but are grouped together.
[0039] To further define, smart The contract governs the rights and obligations of the parties to the governing provisions. smartRights on one side of a contract equate to corresponding obligations on the other side, and vice versa. Thus, the terms represented by Mithra tokens can sometimes be further categorized as rights, obligations, or other. This is particularly useful when Mithra tokens possess intrinsic value for which rights can be transferred or monetized. A Mithra contract consists of the entire set of negotiated rights and obligations represented by tokens and associated with persons.
[0040] As a result, the Mithra token becomes a fully tradable token that can be transferred to another party in its own right, along with all of its rights and obligations with respect to the Mithra family within the Mithra contract.
[0041] Mithra contracts offer various technical features that can improve the distributed computing platforms on which they operate. For example, the way the human-readable version is linked to the smart contract on the Ethereum blockchain allows for more efficient lookups between the two. Instead of having to cross-reference various different databases, a resolver is employed, requiring secure computing resources. In another example, by grouping contract clauses into tokens, memory can be used more efficiently. Instead of having to repeat common clauses over and over across many different contracts, tokenization allows for the centralization and reuse of common clauses. Thus, Mithra contracts offer various technical and technological improvements. (Mithra Platform - Revenue Activity Collaboration for Mithra Contracts)
[0042] The Mithra Platform consists of a range of novel technological components that can be integrated and highly consumable by individuals and businesses alike, generating revenue-generating collaboration for Mithra contracts. The Mithra Platform constitutes a concrete application that enables the generation of smart contracts and their corresponding human-readable forms.
[0043] Figure 2 is an architectural diagram illustrating the system for the Mithra platform at a high level. Line 209 represents the well-known Internet network, including all of the interconnected networks and sub-networks. Mithra domain 200 comprises server 201 running software 203 on a processor. Software 203 provides a website and a user dashboard with multiple interactive interfaces for users to interact with the system. Data repository 202 provides storage for user data and contacts, as well as other data storage as required by server 201. Those skilled in the art will recognize that there may be multiple servers and data repositories, and that system intelligence may be distributed in many ways. The simplified architecture shown is deemed sufficient to explain the functionality of the inventive system.
[0044] Third party server 204 is meant to represent virtually any number of servers and domains within the Internet network with which Mithra domain 200 may interact that are implementations of services for registered members. One such service is, for example, Ethereum. TM It can be a connection to a blockchain service such as
[0045] Users 205(1-n) are users who connect to Mithra domain 200 through computers, such as pad devices, laptop computers, tower systems, and integrated systems, having an internal LAN. The connection is typically through one or another type of Internet Service Provider (ISP) 207. Users 206(1-n) represent users who connect through mobile devices, such as smartphones and the like, via a wireless network through network hub 208, for example.
[0046] In one embodiment, Mithra domain 200 is configured to allow users to interact with Mithra domain 200 through computerized devices running a web browser. In an alternative embodiment, each user platform may download and run an application that communicates with a compatible application running Mithra domain 200.
[0047] Exemplary bidirectional interfaces are described below for various purposes. (User wallet and account management) (User wallet management)
[0048] To join the system, users must first register or sign in by either importing a seed phrase assigned to their existing wallet or by having a new blockchain wallet created by the system. The system assigns a highly secure private key (seed phrase) to the new wallet address, enabling them to join and access the new wallet. The system also provides helpful tips on how to securely derive the private key. The user wallet will be used for two main purposes:
[0049] · Manage system access as described above.
[0050] Manage utility tokens required to use the system, such as purchasing more tokens, transferring tokens to another wallet, or making payments. (User, Account, and Wallet Management)
[0051] Due to the corporate nature of the System and its business and consumer target market, the System is subject to compliance regulations, smart It must overcome existing distributed ledger models that lack meaningful structure and permission management for executing contracts and transaction processes. smart Contracts and transactions belong to their respective organizations, not to the person personally.
[0052] Thus, in one embodiment of the present system, two user account types are provided: one business account and one personal account. (Business Account vs. Personal Account)
[0053] FIG. 3 illustrates one of many interactive interfaces that may be provided by SW 203 executing on server 201 within Mithra domain 200. The services provided by the interactive interface illustrated by FIG. 3 are for registering new members and, in some cases, for editing registration information. While the registration interface is selected in this example, various interfaces for different purposes may be selected in menu column 302 found at the bottom left of the registration interface. This menu column remains for substantially all interfaces that may be accessed by a user, allowing the user to easily navigate from one interface to another. Command line 301, as seen in FIG. 2, provides links to various other functions enabled by SW 203. Those skilled in the art will appreciate that SW 203 may be a wide variety of programs and executable code providing many different functions and running on many different platforms.
[0054] The illustrated interface is operable for a new user to register and provide the necessary information to the system to instantiate the person or business as a registered user. As is common in interfaces of this type, input fields for name, address, email, etc. are provided in area 303 of the interface. Other functionality related to registration, including, for example, personal information, email, and connected accounts, security, notifications, etc., is provided by a menu list in the left vicinity in area 303. These are links that redirect the user to other interfaces.
[0055] At the time of registration with the Mithra revenue collaboration, users are asked to create a business account or a personal account. If a new user selects a business account, the system will issue a new wallet for the user instead of allowing the user to use an existing wallet, even if it may be compatible. The intent is that the wallet associated with the business account will remain within the business and be used only for the business. An individual can maintain two system accounts, with two separate wallets: one for the business and one for their personal use. The business and personal account types share some common features, both of which include: User Information Email and connected accounts like LinkedIn or Facebook Security Settings Proof of identity or KYC (Know Your Customer) Notification settings Preferences such as Project View, Project Sorter By, etc. Wallet information such as wallet address The following settings distinguish between business and personal accounts: (Account Type - Business vs. Personal)
[0056] For business accounts, some additional fields will be required, such as user role, which can be administrator, user, or other required role. Also, for organizational unit identifier (which can be retrieved from the registered organizations list), users from the same organization should have the same value in this field.
[0057] A first person creating a business account for a specific organization fills in details of the organization, such as its name, address, contact details, and industry. This person is automatically granted the administrator role. In addition, the system will automatically generate an organizational unit identifier. (Business Manager User Dashboard)
[0058] An administrator user is provided with a purposeful administrator dashboard for performing a set of actions. The dashboard is a set of interactive interfaces, each providing input fields and links to other interfaces as needed, the functionality of which is described herein without explicitly illustrating the individual fields and links within the interfaces.
[0059] Invite a new user: Invite a new user from the same organizational unit into the system via email and / or SMS invitation. The new user must create a new wallet on the platform instead of reusing an existing compatible wallet. The default role for a new user is set to "User", but an admin user can select a different role at the time of invitation.
[0060] · Change User Role: Upgrade or downgrade user role.
[0061] Revoke a User: When a user leaves an organization or is no longer required to hold a system license, an Admin User can revoke the user's access to the user's account and any wallets associated with the revoked account.
[0062] Restore Users: If user access is accidentally revoked or if a user is required to regain use of the system, an admin user can restore user access to accounts and wallets.
[0063] The system will not allow wallet access associated with a revoked account. However, there is a possibility that a revoked user will attempt to port and use their wallet on another compatible blockchain network. A global system switch will be put in place to ensure that revoked business wallets do not regain access to data associated with any Mithra system. (Template Management)
[0064] The templates in Mithra Contracts are as follows: smart A template implies a structured digital document that defines the nature of a contract or project. A template may have fixed narrative portions that can be adjusted, and variable portions that allow the template to be adapted to specific situations and may provide flexibility for the parties to negotiate terms.
[0065] One example is a commercial building for sale. smart To create a contract, smart The nature of a contract is that there will be some fixed language and some variables. What is fixed is the fact that the transaction represented by the sale of the building is a sale with rights being transferred from one party or organization to another. Who the parties to the transaction are, the sale price, the means and terms of payment, etc. are all variables. smart These are variables that must be negotiated and finalized as the contract evolves. smart When a contract is signed, a template may be created that defines the location of fixed and variable elements. smart When developing a contract, you may have your own rights within the template, and the variables to be negotiated by different people for the sale of different buildings may be the same. smart The use of templates may be required, such as to create a contract.
[0066] Mithra revenue collaboration is heavily dependent on the use of templates. There are three hierarchical levels of templates available: clause templates, contract templates, and project templates.
[0067] By providing templates, embodiments may provide technical advantages in terms of memory and processing power usage. Allowing frequently used contract clauses to be reused in templates may use memory more efficiently than having to repeat or re-generate the same wording each time. FIG. 4 is a simplified example of an interactive interface within the Mithra system for creating, selecting, and editing templates. The dashboard link shown as element 302 in FIG. 3 is, of course, present in virtually all interactive interfaces presented to users within the system. Command line 401 provides an active link for navigating to alternative collections of templates. The "Create New Link 402" navigates to an interactive interface that allows users to create new templates. A collection 403 of existing templates of various types and for various uses is displayed.
[0068] Each project template consists of one or more contract templates, which are made up of one or more clause templates. Templates can be defined in the following hierarchy: General templates Industry-specific templates, e.g., healthcare, oil and gas, real estate Geography-specific templates, e.g., California, Singapore, London Organization-specific templates, e.g., government departments, associations, private companies Personalized templates
[0069] All templates are reusable, searchable, and analyzable. Breaking down templates to the clause level means that digital clauses can be easily integrated into multiple smart It allows clauses to be reused within contracts and contract templates, and makes templates searchable via keywords and / or other search criteria. More importantly, clauses can be analyzed and become valuable to contract users. For example, the system now has a way to analyze how many times a particular clause is used across a revenue collaboration. This allows contract users to gain insight into whether a clause is a standard clause used by many users, or a customized clause that requires special attention. The system provides a green light for standard clauses and a red light for clauses that require careful scrutiny.
[0070] Templates can be created via the user's library by simply adding a new template. Alternatively, this can be done via the project, smart When a contract or clause is created or updated, it can be generated via the template save feature.
[0071] All templates will appear in the user's library dashboard, which allows the user to organize them into various categories such as recent files, favorites, downloads, archives, and published.
[0072] Templates are stored in the user's library on the dashboard and can be organized into various categories such as recent files, favorites, downloads, archives, and published.
[0073] Template owners can choose to publish their templates to either a private environment or a public store. Once made publicly available, templates become searchable, downloadable, and usable by other users within the template marketplace on the Mithra platform. Template owners can decide whether payment is required for the public to download their templates. The system facilitates the payment process for template purchases.
[0074] Users can choose any suitable payment method. On the Mithra platform, the ShelterZoom Mithra Coin (SMC) utility token is typically used for template transactions. Thus, SMC will be paid from the buyer's wallet to the template seller's wallet.
[0075] In scenarios where templates are published to a private store, all users with access to the private store can also download and use the template. For example, it is common for companies or associations to publish templates for their respective employees or members to use as their organization's default templates. This would significantly reduce template duplication across the organization. Once a digital template is created once, all authorized users can download it from the same source, without having to create it again by each individual.
[0076] These privately published templates are often free for members to use, but may also require payment from the template users.
[0077] Template users can also subscribe to template notifications. For example, users will receive system notifications when new templates are made available for their subscribed industries or categories, or when new versions for templates they have downloaded are published. In addition, contract templates can be smart It is one of the main starting points for starting contract creation.
[0078] FIG. 5 illustrates how users are stored in various collections within the system. smart Contracts, Templates, and Pending smart Figure 1 illustrates an interface that allows users to search for contracts. The normal command line for the Mithra dashboard is always clear, and this interface allows users to smart A query field 501 is provided for entering a query to find contract, project, and legal clause templates. In addition, a second query field 502 allows the user to enter a query, either out of the box or custom. smart Existing contracts for almost anything that can be edited to produce a contract and then saved as a template smart Allows contracts to be searched and discovered. (Project (Transaction) Management)
[0079] Project management, sometimes referred to as transaction management in the system, is the starting point for creating a Mithra contract. A project can be any type of project or transaction, such as a procurement project, a real estate transaction, a financial transaction, or a supply chain project. (Project Overview Dashboard) From the Project Overview Dashboard, users can:
[0080] · Get at-a-glance insight into recent projects, new messages, and a consolidated status overview.
[0081] View important information about each project, such as the project name, start date, status, and profile pictures of project participants.
[0082] · Create a new project (transaction).
[0083] Select an existing project.
[0084] · Sort the project list by date, status, user, or any other available sort order.
[0085] · Search for projects by defined search criteria.
[0086] Projects are presented in either a card view or a line view to accommodate user preference.
[0087] 6 illustrates an exemplary project overview dashboard for a user, formatted in a card view. Recently accessed files may be selected in area 601. Recent messages may be visited and replied to in area 602. Status is presented in area 603. Those skilled in the art will appreciate that the interface of FIG. 6 is exemplary and much functionality may be compromised as the diagram requires certain standards regarding font size, etc.
[0088] All projects in the user's wallet are presented in this dashboard in a card view, with each project in a small, card-sized icon, in area 604. In this example, only the subject line is shown, but in some embodiments, significantly more information, status, such as whether it has been signed, date, and the like, may be shown as well.
[0089] Each icon is a link to the project shown, and selecting one project redirects the user to another interface where the project can be further managed as shown below.
[0090] In an alternative embodiment, the project overview dashboard is presented in a line view where each project is represented in a line rather than as a card. The functionality is the same. (Project Details Dashboard)
[0091] Once the user selects an existing project, the user is redirected to the project details dashboard. Figure 7 is an example of a project details dashboard in one embodiment of the present invention. The dashboard is divided into five main sections:
[0092] Documents - All documents associated with the project smart Contracts and documents are displayed in either a card view or a line view in area 702, which is sortable and searchable. Selected smart Contract - Selected smart A simple overview of contracts 701
[0093] Workflow smart A selected set of contracts containing all past versions of the contract and the actions and participants associated with each version. smart A detailed workflow 703 for a contract. The user can click on any version in the workflow and smart You can follow the steps to the contract details page. Selected users in user area 704 smart A list of participants in the contract
[0094] Chat - A chat section 705 to facilitate communication between participants with permission to chat and to view chat history. The contract issuer defines permissions regarding user chat privileges, e.g., a seller and a buyer can chat directly if there is no proxy between them, but cannot chat directly if there is an appointed proxy. For more advanced features, see the Chat section later in this document.
[0095] The dashboard also allows you to create new projects or create new ones for existing projects. smart It is also used to initiate the creation of a contract. ( smart Contract Management)
[0096] smart Contract management is, in many embodiments, a very important feature of the present invention. ( smart Creating a Contract (Issuing Mithra Tokens)
[0097] smart Contract processes can be created using predefined templates or completely new smart A new contract based on one of smart In the latter scenario, the contract writer begins by creating a contract. In the latter scenario, the contract writer finds suitable clauses by manually adding them one by one using an inline editor or by searching a clause template library, and then writes them into the contract. smart The clause template can be inserted into the contract. Either way, once the user selects a predefined template or finds an appropriate clause using the clause template library, the selected template is retrieved and compiled into the MC. The user can then define any variables within the template or clause template.
[0098] Upon completion, the contract writer: smartContracts can be submitted to the blockchain, which in turn generates a smart contract with an issued token (Mithra token) that carries all the defined terms. ( smart Publishing Contracts - Public vs. Private Stores
[0099] The contract issuer: smart You can choose to publish your contract to either a public store or a private store. smart The contract is that everyone smart Browse the contract, smart Available in the global search area so that you may have the opportunity to join the contract. Held in a private store smart Contracts are not publicly discoverable; users can only access them by invitation. smart You can join the contract. ( smart Join the contract (counter Mithra token creation) When the issued token is in the issued state, the contract issuer then issues it to the counterparty or counterparties according to the publishing method. smart You can get involved to join the contract. 1. Invite your counterparty via private invitation
[0100] The issuer smart One or many parties can be invited to join the contract and each invitee can be assigned different user permissions, for example, manage, view, edit and / or comment, or sign only.
[0101] Upon receiving the invitation via email or SMS, the Invitee may sign in to the System or register if the Invitee is a first-time user.
[0102] Invitees are officially smart Join the contract, smart Sign a contract or submit an offer, or smart Counter Mithra tokens can be created either by directly countering the terms of the contract.
[0103] Figure 8 shows the user smart 8 illustrates a window 801 that may be invoked to invite others to join a contract. If it is a "other person" to be invited, that person will have a profile with a username and contact information. The inviting user may select user permissions as shown in window 801, and the invited user will receive a communication, such as an email, with the invitation, according to the configuration. New users may be invited as well, and will become registered users upon registration in the process. 2. Join via the Contract Marketplace
[0104] Mithra's public store is smart Creating a Marketplace for Contracts. Referring back to FIG. 5 and the description of FIG. 5 above, the contract marketplace can be searched. The marketplace model of the present invention allows suppliers to smart Listing the contract and the parties involved in the contract smart Allows users to subscribe to or search for contracts. For example, government smart An IT services company interested in contracting can explore any government RFPs for IT services, or a landlord who prefers short-term leases in a particular area can subscribe to alerts whenever such leases come on the market. smart 1 shows example results of searching for contracts or listing by contract owner. smart The contracts are shown, each depicted as an annotated icon in FIG.
[0105] Within the contract marketplace smart In response to finding a contract, participants may: smart Should redirect to a human-readable version of the contract, 1001 smart A participant may select a contract by submitting an offer or proposal, for example, an estate offer or an RFC proposal. smart The submission form allows users to enter into a contract, so that each value entered into a field automatically appears on the digital contract. smart Once all fields on the submission form are filled in, participants can view the smart The entire contract can be previewed and then submitted by selecting the "Submit" link 1002 at the bottom.
[0106] Counter Mithra tokens are then generated for recipients who are currently in the contract workflow and can start the negotiation process. ( smart Contract Negotiation)
[0107] Mithra contracts, fully digitized and tokenized contracts, create unprecedented capabilities in contract negotiation. By storing their respective contract terms on the Mithra token, each party can fully participate in real-time contract negotiations and view counter-terms as they are presented. Using distributed ledger technology, parties can be assured that all changes are verifiable and immutable. This procedure creates trust among all contract participants. Additionally, the system provides an effective side-by-side review dashboard, illustrated as Figure 11, whereby participants can collaborate to amend contract terms so that each party is visible to the trajectory changes and has the opportunity to accept them. In Figure 11, Victoria smart In two places in the contract, he proposes to change the deposit from $10,000 to $15,000 by striking out the $10,000 value and typing in the new $15,000 value. In Aaron's version, Aaron has accepted the first of the two changes, but has not yet accepted the second.
[0108] These changes may involve removing clauses, adding clauses, or modifying variables present in the template relating to clauses. When such changes are made, the changes may be made to both the human-readable version shown in Figure 11 and the underlying smart contract code. (Creating candidate lists - handling multiple offers)
[0109] In situations where multiple offers are received from participants, e.g., in an RFC or estate sale, the system allows the contract issuer to shortlist several offers so that the issuer can focus its negotiations on those selected offers. The issuer will also select the contract winner by signing the smart contract. ( smartContract Signing - Mithra Token Matching)
[0110] Once all terms are met between the issued tokens and their counter tokens held by their respective holders, the smart contract can be signed and executed. (Transfer of Ownership - Transfer of Mithra Tokens)
[0111] Mithra tokens can carry the rights and obligations of assets. Under certain circumstances, tokens can be transferred from one party to another such that all of the rights and obligations inherent in the tokens will be transferred along with them. For example, before finalizing a property sale, the buyer's economic situation suddenly changes due to unemployment. The buyer can no longer purchase the property. However, the buyer can find a new buyer who wishes to take over all of the rights and obligations represented by the Mithra tokens held by the buyer. Perhaps by requesting the seller's permission, the buyer could simply transfer the tokens to the new buyer, thus transferring ownership of the tokens. (Share)
[0112] Due to the Mithra contacts being presented in a human-readable format via www representation, this new type of smart contract becomes shareable via a unique and verifiable link. The smart contract link of the present invention, where the smart contract is represented by a link, is: smart Based on the visibility settings of the contract, it can be shared privately within a group of people or shared publicly across social media or wider networks. (Search and Match)
[0113] The Mithra contract architecture opens the door for contract search and matching in a way that has never been done before.
[0114] Due to the searchable nature of Mithra contracts, combined with information discoverability controlled by the contract issuer, users can now conduct searches via searching open information in the Mithra contract web representation. Mithra contract issuers will have full control over that information and will be able to control whether such information should be open, partially open, or completely hidden. (Permissions and Rights Management)
[0115] Each participant has different levels of permissions and rights to enable certain actions such as editing the contract, reviewing, signing, attaching documents, or transferring tokens. The rights are divided into two groups:
[0116] 1. Rights for existing objects - a set of permissions that users have to enforce with created objects. This applies to Mithra contracts, Mithra swarms, Mithra tokens, and terms.
[0117] 2. Default Rights - A set of permissions that allows a user to act on objects that have not yet been created. Each group is divided into: Rights for specific users (accounts) Rights for everyone
[0118] Rights for a specific user (account) to a created object are configured by the user during object creation, or set by another user with rights to this action.
[0119] Permissions for everyone (everyone) on a created object are configured when the object is created (to all false) and can be changed by users who have the rights to do so. They can be adjusted by user actions with this object.
[0120] Default rights are granted by the user with rights to this action on objects that have not yet been created.
[0121] Thus, it is possible to grant rights for users that will create groups (MG) in the Mithra contract, or that will create tokens (MT) in the Mithra group, or that will add conditions to the tokens. (default rights for specific users (accounts))
[0122] Once a user with default rights to create any object creates this object, the rights from the default are copied into the rights to this object for this user.
[0123] In the event that the address of the user to whom default rights are desired to be granted is not known, default rights for everyone are granted.
[0124] Each field in each structure is a specific right for a specific object. The following example illustrates the permissions associated with the Mithra contract rights structure. Permission [0] grant / revoke - the right to grant / revoke rights to actions using this MC Permission [1] viewing - the right to view the data in this MC Permission [2] editMetadata - Right to edit metadata within this MC Permission [3] createMG - the right to create an MG within this MC Permission [4] editMGDefaultRigfts - Right to edit the default rights for MG created within this MC Permission [5] deactiveReactive - Right to remove / restore this MC Permission [6] attachDocument - Right to add a document to this MC
[0125] (Grant of Rights)
[0126] A user can acquire rights either by creating an object or by being granted rights by another user who has been given the right to grant rights. In order to grant a right to an object, the initiator of the transaction must himself possess the right.
[0127] grantRevoke on this object
[0128] A transaction's (!) Msg.sender can only grant those rights to concrete objects it owns, i.e., if the initiator of a transaction does not own any rights, it cannot grant rights to other users. chat
[0129] In one embodiment, the dashboard provides enabled participants with communication channels, record management, and / or smart It provides a simplified way to create contracts. Participants can chat via three different types of chat methods: General chat
[0130] -This is the default chat setting. Participants use this as a communication channel for communicating, discussing, or collaborating on any subject they wish to discuss. · smartRegarding recorded chat within a contract or transaction
[0131] -Participants can view chat history in specific smart Mutually agree to chat at a location that will become a document or evidence supporting the contract or a legally binding governing provision in itself within the transaction process. smart Participants involved in a contract or transaction can collaborate via chat to support the process in a more complete way. After the chat, participants will be given two additional options: a. Based on a specific token or where the chat is initiated smart Attach chat transcripts as documentation to a contract or transaction.
[0132] b. Tokenize the chat history as Mithra tokens. In this option, the requesting party receives the tokenized smart The requesting party will be prompted to enter the metadata and required information to support the creation of the contract. smart The party issuing the contract will be the one who issues the contract. All other participants will be issued their respective counter tokens, requiring their final digital signature before the smart contract can be executed.
[0133] -Details regarding legally binding compliance chat are illustrated in the following sections. Legally binding compliance chat as the start of a new process or transaction
[0134] -Participants agree that chat history is legally binding. smart A mutual agreement to chat in a chat room will become a contract. In this way, the chat will become a legally binding smartIt is the first step for creating a contract, giving participants an easy interface for a traditionally cumbersome process.
[0135] At each step of the chat, participants will be given the option to import clause templates via keyboard search and / or other criteria search such as country, region, industry, or compliance provision type. This will ensure that participants are guided by the appropriate legal clauses as far as the system allows.
[0136] At the end of the chat, and upon request of any participant in the chat, the recorded chat will be smart The requesting party will be tokenized. smart The requesting party will be prompted to enter metadata and required information to support the creation of the contract and its integration into the Mithra platform as a Mithra contract. smart The issuing party of the contract will be the one who issues the contract. All other participants will be issued their respective counter tokens. -All participants may edit the terms and conditions, smart You will be given the right to negotiate the contract.
[0137] -All participants will be required to electronically sign the final smart contract before it can be executed.
[0138] The chat functionality described above is supported by messaging chat, voice chat, and video chat. However, as part of the legally binding compliance regulations for chat, all media must be converted to text. (Other features)
[0139] This system is smartIt provides several other important functions to support the contract process. Manage user roles and responsibilities · smart Add an attachment to a contract Download one of the available document types ·digital smart Create a PDF from a contract Save as a template (Common System Capabilities) Template Management and smart There are some common foundational competencies shared with contract management or project management: Master Data Management
[0140] Master data sets are common data sets that can be used across various areas of the system. Master data sets are templates, or smart It is not constrained by contracts or projects (transactions).
[0141] For example, industry, region, user role, estate, and agent master data for real estate; institution and medical practitioner master data for healthcare; university and course master data for education Metadata Management
[0142] ○Metadata is specific template, project (transaction), smart A set of common data used for a contract or set of terms (Mithra tokens). Metadata can be either common or industry / subject specific. It is retained across entities in the hierarchy.
[0143] For example, project name, project creation date, project template used, status, visibility flag (public or private) are a common set of metadata about projects, while property data such as real estate agent ID and property photos may be project metadata specific to the real estate industry.
[0144] All project-level metadata is stored in the project smart All contract-level metadata is shared across contracts and Mithra tokens. smart It is shared across Mithra tokens within a contract. Metadata in lower levels of the hierarchy takes precedence over those in higher levels. For example, a procurement project has its visibility flag (metadata) set to "yes" at the project level. A project may have 10 visibility flags, two of which have their visibility flags set to "no". smart This is the contract between those two smart While the contract is not publicly visible, the other eight smart This means that the contract is available for public viewing or searching. Template creation
[0145] o As described in the previous section, templates can be created either through the library or through the project area when a user saves a project template, contract template, or clause template for the first time. Template update
[0146] Similar to the template creation feature, templates can be added via the user's library dashboard or updated in projects, smart Contracts, or clauses, can be saved and updated within the project flow. ·editor
[0147] Editors are used extensively across the system. Mithra contracts have an inline editor built in. This allows you to edit templates, projects, and smart Used to create, edit, and manage contracts and clauses. Both the input and output editors are in place.
[0148] ■An example of an input editor is one in which the user can load clauses for Mithra tokens from binary files such as Microsoft Office (.doc, .xls), Office Open XML (.docx, .xlsx), or OpenDocument (.odt, .ods). One implementation is for the document to be parsed through numbered lists and headers. Each header or element in the numbered list becomes a clause. If it is a header, the header text becomes the clause's name, and the text following the header becomes the clause's value. If there is no text following the header, the clause's value is left empty. If the header has a numeral, this is saved as the clause's numeral; otherwise, it is calculated automatically. If it is a numbered list element and not a header, the clause's name is left empty and only the numeral and value are assigned. The header type (Header 1, Header 2, etc.) or the indentation of the numeral indicates the clause's indentation. A clause ends where the next header or numbered element appears. Depending on the indentation, the numeral of the next clause is calculated. There is the ability to exclude some headers and numerals from being extracted as clauses.
[0149] ■The user smart It is possible to manage the printable version of the contract or template output either through predefined output, where the user uploads their own PDF form to be used as a template for the output, or through system-generated output, where the user can define headers, footers, styles, fonts, colors, etc. ·notification
[0150] Notifications - Email, SMS, and / or push notifications for status changes, new invitations, new offers, revised smart Used for warnings about contracts, etc. ·Clause Search Global Search PDF generation Publish Workflow (Share)
[0151] Due to the fact that Mithra contracts are presented in a human-readable format via www representation, this new type of smart contract becomes shareable via a unique and verifiable link. A smart contract link of the present invention, where a smart contract is represented by a link, is defined as: smart Based on the visibility settings of the contract, it can be shared privately within a group of people or shared publicly across social media or wider networks. (Example smart contract)
[0152] An example of a Mithra contract implementation definition is provided below. [Table 1-1] [Table 1-2] [Table 1-3] [Table 1-4] [Table 1-5] [Table 1-6] [Table 1-7] [Table 1-8] [Table 1-9] [Table 1-10] [Table 1-11] [Table 1-12] [Table 1-13] [Table 1-14]
[0153] Those skilled in the art will also understand, upon reading and understanding the many different descriptions herein, that all descriptions of specific embodiments are exemplary and merely indicative of the many other descriptions not provided that may be within the scope of the inventions enabled herein, the scope of which is limited only by the claims.
Claims
1. 1. A system for creating, enabling negotiation for, and approving smart contracts, the system comprising: a data storage storing user information, smart contract templates, and smart contracts, the smart contract templates comprising project templates, each of which is comprised of one or more contract templates, each of which is comprised of one or more clause templates, the one or more clause templates being structured digital documents that define the nature of clauses of a smart contract, each of which has a fixed descriptive portion and an adjustable variable portion, whereby one smart contract template can be used to create smart contracts for different sales that have the same adjustable variable portion; a communication service by which registered users communicate; a processor coupled to said data storage and said communication service; wherein the processor: receiving a request from one or more users to create a smart contract based on the one or more users accessing a smart contract template from the data storage, wherein the one or more users are registered using a registration interface, wherein upon registration the one or more users are issued a digital wallet for use in a blockchain service, the one or more users are issuers of the smart contract, and the smart contract may be associated with multiple counterparties to the smart contract; Submitting the smart contract to the blockchain service to issue an issued token that has all the terms defined in the smart contract; publishing the smart contract to a public or private store; issuing a plurality of counter tokens to each of the plurality of counterparties, whereby the plurality of counterparties are engaged to join the smart contract, the plurality of counter tokens including a first token having a first set of terms defined in the smart contract and associated with a first counterparty of the plurality of counterparties, and a second token having a second set of terms defined in the smart contract and associated with a second counterparty of the plurality of counterparties, the communication service enabling the one or more users and the plurality of counterparties to negotiate for the terms defined in the smart contract to reach an agreement; After the agreement is reached, allowing each participant in the smart contract to electronically sign the smart contract; A system that is configured to:
2. 10. The system of claim 1, wherein the processor is further configured to provide a search function, the search function enabling the one or more users to search for smart contract templates in the data storage and select a smart contract template to create the smart contract.
3. The system of claim 2 , wherein the processor is further configured to enable the one or more users to subscribe to template notifications for an industry or category.
4. The processor: determining whether a new smart contract template or a new version of a previously downloaded smart contract template has been published based on the one or more users' subscriptions to the template notifications; and notifying the one or more users when the new smart contract template or the new version of the previously downloaded smart contract template is published; and The system of claim 3 , further configured to:
5. 5. The system of claim 1, wherein the processor is further configured to invite the plurality of counterparties to join the smart contract via direct email or text invitation from the one or more users.
6. 6. The system of claim 5, wherein the processor is further configured to assign user permissions to each of the plurality of invited contract partners, including, but not limited to, administrative privileges, view only, edit and / or comment, or sign only.
7. 6. The system of claim 5, wherein the processor is further configured to enable the invited partners to sign in to the system or, if first-time users, to register.
8. 8. The system of claim 7, wherein the processor is further configured to enable the one or more users and the plurality of counterparties to negotiate for terms defined in the smart contract via a chat communication system.
9. 8. The system of claim 7, wherein the processor is further configured to provide the smart contract presented side-by-side to the one or more users and each of the plurality of counterparties, whereby each party may propose changes to terms that may be scrutinized and accepted or challenged by the other party until agreement is reached.
10. 5. The system of claim 1, wherein the processor is further configured to provide a search function whereby counterparties can search published smart contracts and join selected smart contracts by submitting offers or proposals.
11. 11. The system of claim 10, wherein the processor is further configured to present a submission form to the counterparty when the counterparty selects a smart contract within the search results, the submission form including fields to be filled in by the counterparty, and when the counterparty enters terms in the fields, the entered terms appear in the smart contract and negotiation begins between the one or more users and the counterparty.
12. 1. A method of operating a system for creating, enabling negotiation for, and approving smart contracts, the system comprising a processor and data storage coupled to the processor, the method comprising: the processor creates a smart contract based on one or more users accessing a smart contract template from the data storage, the one or more users being issuers of the smart contract, the smart contract being associated with multiple counterparties to the smart contract, the smart contract template comprising a project template, each of the project templates being comprised of one or more contract templates, each of the one or more contract templates being comprised of one or more clause templates, the one or more clause templates being structured digital documents that define the nature of clauses of a smart contract, each of the smart contract template, the project template, the contract template, and the clause template having a fixed descriptive portion and an adjustable variable portion, whereby one smart contract template can be used to create smart contracts for different sales having the same adjustable variable portion; The processor submits the smart contract to a blockchain service, thereby associating the smart contract with an issued token that has all the terms defined in the smart contract; the processor publishing the smart contract to a public store or a private store; the processor issuing a plurality of counter tokens for each of the plurality of counterparties whereby the plurality of counterparties are engaged in joining the smart contract, the plurality of counter tokens including a first token having a first set of clauses defined in the smart contract and associated with a first counterparty of the plurality of counterparties, and a second token having a second set of clauses defined in the smart contract and associated with a second counterparty of the plurality of counterparties; providing an online communication service to the one or more users and the plurality of counterparties to negotiate for the terms defined in the smart contract to reach an agreement; After the agreement is reached, the processor enables each participant in the smart contract to electronically sign the smart contract. A method comprising:
13. 13. The method of claim 12, further comprising the processor providing a search function, the search function enabling the one or more users to search for smart contract templates in the data storage and select a smart contract template to create the smart contract.
14. The method of claim 13 , further comprising the processor enabling the one or more users to subscribe to template notifications for an industry or category.
15. the processor determining, based on the one or more users' subscriptions to the template notifications, whether a new smart contract template or a new version of a previously downloaded smart contract template has been published; the processor notifying the one or more users when the new smart contract template or the new version of the previously downloaded smart contract template is published; and 15. The method of claim 14, further comprising:
16. 16. The method of any one of claims 12 to 15, comprising the processor providing the smart contract in a machine-readable manner.
17. 16. The method of any one of claims 12 to 15, further comprising inviting the plurality of counterparties to join the smart contract via a direct email or text invitation from the one or more users.
18. 20. The method of claim 17, further comprising the processor assigning user permissions to each of the plurality of invited contract partners, including, but not limited to, administrative privileges, view only, edit and / or comment, or sign only.
19. 18. The method of claim 17, further comprising the processor enabling the invited partners to sign in or register with the system.
20. 20. The method of claim 19, further comprising: enabling the one or more users and the plurality of counterparties to negotiate for terms defined in the smart contract via a chat communication system.
21. 20. The method of claim 19, further comprising: the processor providing the smart contract presented side-by-side to the one or more users and each of the plurality of counterparties, whereby each party may propose changes to terms that may be scrutinized and accepted or challenged by the other party until agreement is reached.
22. 16. The method of any one of claims 12 to 15, further comprising the processor providing a search function for published smart contracts, whereby counterparties can search the published smart contracts and join selected smart contracts by submitting offers or proposals.
23. 23. The method of claim 22, further comprising: the processor presenting a submission form to the counterparty, the submission form including fields to be filled in by the counterparty, wherein when the counterparty enters terms in the fields, the entered terms appear in the smart contract and negotiation begins between the one or more users and the counterparty.
Citation Information
Patent Citations
Signature verification system, signature verification method and program
JP2018014622A
Computationally Efficient Transfer Processing, Audit and Search Apparatus, Methods and Systems
JP2018525729A
A method for secure peer-to-peer communication on the blockchain
JP2019519014A
Network-leveraged real estate transaction assistance system and method
US20180060981A1