EP3516615A1 - Systems and methods for interception of smart contracts - Google Patents
Systems and methods for interception of smart contractsInfo
- Publication number
- EP3516615A1 EP3516615A1 EP17787256.1A EP17787256A EP3516615A1 EP 3516615 A1 EP3516615 A1 EP 3516615A1 EP 17787256 A EP17787256 A EP 17787256A EP 3516615 A1 EP3516615 A1 EP 3516615A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- judgment
- smart contract
- database
- execution
- distributed ledger
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
- 238000000034 method Methods 0.000 title claims description 56
- 230000004044 response Effects 0.000 claims abstract description 45
- 230000001960 triggered effect Effects 0.000 claims description 2
- 230000006870 function Effects 0.000 description 93
- 238000004891 communication Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 7
- 230000008520 organization Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 206010010144 Completed suicide Diseases 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000004888 barrier function Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000010348 incorporation Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000005065 mining Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/18—Legal services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
Definitions
- Smart contracts typically include program instructions that may be executed in response to a transaction in the distributed ledger system addressed to the contract. Smart contracts may also represent legal contracts between users, with program functions of the smart contracts implementing terms, conditions, etc. of the legal contract.
- a legal contract represented by the smart contract may represent an illegal transaction in some jurisdictions.
- the smart contract may include logical errors that cause it to execute a transaction different from that agreed to by parties to the legal contract.
- the immutability of the transactions, contracts, etc. provided by the distributed ledger system may be a barrier to actions to stop execution of such a contract.
- FIG. 1 is a schematic diagram depicting an embodiment of a system for providing intervention in the operation of a smart contract in a distributed ledger system.
- FIG. 2 is a schematic diagram depicting an embodiment of a virtual court server system.
- FIG. 3 is a schematic diagram depicting an embodiment of the distributed ledger system.
- FIG. 4 is a schematic diagram depicting an embodiment of a distributed node of the distributed ledger system.
- FIG. 5 is a flowchart depicting an embodiment of a method of determining a judgment for the smart contract.
- FIG. 6 is a schematic diagram depicting an embodiment a court smart contract.
- FIG. 7 is a flowchart depicting an embodiment of a method of intervening in the operation of the smart contract based on the judgment.
- FIG. 8 is a schematic diagram depicting an embodiment of the smart contract.
- FIG. 9 is a schematic diagram depicting an embodiment of a virtual machine of the distributed node.
- Intervening in the operation of a smart contract in a distributed ledger system may include launching execution of the smart contract; upon launching execution of the smart contract, executing a judgment checking function to determine whether a judgment against the smart contract exists in a judgment database; in response to a judgment against the smart contract existing in the judgment database, intervening in the operation of the smart contract to prevent the execution of the smart contract; and, in response to no judgment against the smart contract existing in the judgment database, continuing execution of the smart contract.
- Intervening in the operation of a smart contract in a distributed ledger system also may include determining a judgment of a validity of a complaint against the smart contract based on input received from one or more judges; in response to the judgment upholding the validity of the complaint against the smart contract, recording the judgment in a judgment database; receiving a request, from a judgment checking function, to determine whether the judgment against the smart contract exists in the judgment database in response to launching execution of the smart contract; and responding to the request indicating whether the judgment exists in the judgment database.
- FIG. 1 depicts an embodiment of a system 20 for providing improved intervention in the operation of smart contracts in a distributed ledger system.
- the system 20 includes a distributed ledger system 24, a virtual court server system 28, one or more judge systems 32, one or more complainant system(s) 36, and one or more other systems 38.
- the distributed ledger system 24 provides a platform for the operation of smart contracts, including a first smart contract 40 for which a judgment may be evaluated, and a second smart contract 42, also referred to herein as a court contract 42, which may be utilized to implement a judgment against the smart contract 40.
- the virtual court server system 28 receives complaints regarding the operation of the smart contract 40 from the complainant system 36, receives one or more inputs regarding the complaint from the judge systems 32, and provides mechanisms for intervention in the operation of the smart contract 40 in the distributed ledger system 24, such as maintaining a judgment database and/or communicating with the court contract 42.
- the other system 38 may also interact with the distributed ledger system 24, such as, e.g., interacting with smart contracts of the distributed ledger system 24.
- FIG. 2 depicts an embodiment of the virtual court server system 28, including a judge system interface module 44, a complainant system interface module 48, a distributed ledger system interface module 52, a virtual court server system control module 56, and a judgment database module 60.
- the complainant system interface module 48 provides a communication interface between the virtual court server system 28 and the complainant system 36 to receive complaint information from the complainant system 36.
- the judge system interface module 44 provides a communication interface between the virtual court server system 28 and the judge systems 32 to communicate complaint information to the judge systems 32 and receive judgment information from the judge systems 32.
- the distributed ledger system interface module 52 provides a communication interface between the distributed ledger system 24 and the virtual court server system 28 to provide enforcement mechanisms for intervention in the operation of the smart contract 40, such as maintaining the judgment database and/or communicating with the court contract 42.
- the virtual court server system control module 56 provides control logic to implement functions of the virtual court server system 28 discussed herein.
- the judgment database module 60 provides a judgment database for storage for and access to the judgments against the smart contract 40.
- the judgment database may instead or additionally be stored in the distributed ledger system 24, such as in the form of a data structure of the court contract 42.
- the virtual court server system may include only any subset of, or an alternative connection of, the features depicted in or discussed herein in regard to FIG. 2.
- FIG. 3 depicts an exemplary embodiment of the distributed ledger system 24.
- the distributed ledger system 24 includes a plurality of distributed nodes 66.
- the distributed nodes 66 are organized as a peer-to-peer network, in which each of the nodes 66 may connect to one or more of the other nodes 66 using a peer-to-peer communication protocol. At least one of the distributed nodes 66 may also connect to the virtual court server system 28. At least one of the distributed nodes 66 also may connect to the other system 38.
- the configuration of connections between individual distributed nodes 66 may change over time according to operation of the peer-to-peer protocol.
- the ledger structure storage module 70 stores data structures into which the ledger of the distributed ledger system 24 is organized in a non-transitory machine-readable storage medium.
- the communication module 74 performs communications between the distributed node 66 and other distributed nodes 66 and other systems or components connected to the distributed node 66, such as the virtual court server system 28.
- the virtual machine module 78 executes smart contracts stored on the distributed ledger of the distributed ledger system 24.
- the ledger structure creation module 82 performs an algorithm to incorporate new transactions and other data into ledger structures of the distributed ledger system 24, such as a data encryption algorithm of a selected complexity.
- the distributed node may include only any subset of, or an alternative connection of, the features depicted in or discussed herein in regard to FIG. 4.
- the distributed ledger system 24 may be a blockchain system in which the ledger implemented by the distributed ledger system 24 is in the form of a sequence of structured data blocks, also referred to as a blockchain.
- the ledger structure storage module 70 is a block storage module that stores the blocks of the blockchain system
- the ledger structure creation module 82 is a block creation module performing an algorithm to incorporate new transactions and other data into blocks of the blockchain of the blockchain system, also referred to as mining blocks of the blockchain system.
- the distributed ledger system 24 may be another type of distributed ledger system instead of a blockchain system, in which the ledger may be organized into a structure other than blocks of a blockchain.
- Components of embodiments of the system 20 for providing an improved intervention in the operation of the smart contract 40 in the distributed ledger system 24, such as the virtual court server system 28, the judge system(s) 32, the complainant system(s) 36, the other system(s) 38, nodes 66 of the distributed ledger system 24, etc., and/or any individual one, subset, or all of the components thereof, may be implemented as hardware, software, or a mixture of hardware and software.
- each of the virtual court server system 28, the judge system(s) 32, the complainant system(s) 36, the other system(s) 38, nodes 66 of the distributed ledger system 24, etc., and/or any individual one, subset, or all of the components thereof, may be implemented using a processor and a non-transitory storage medium, where the non-transitory machine-readable storage medium includes program instructions that when executed by the processor perform embodiments of the functions of such components discussed herein.
- each of the virtual court server system 28, the judge system(s) 32, the complainant system(s) 36, the other system(s) 38, nodes 66 of the distributed ledger system 24, etc., and/or any individual one, subset, or all of the components thereof, may be implemented using a computer system, such as, e.g., a desktop computer, laptop computer, mobile computing device, network device, server, Internet server, cloud server, etc.
- Components of embodiments of the system 20 for providing an improved intervention in the operation of the smart contract 40 in the distributed ledger system 24, such as the virtual court server system 28, the judge system(s) 32, the complainant system(s) 36, the other system(s) 38, nodes 66 of the distributed ledger system 24, etc., and/or any individual one, subset, or all of the components thereof, may each be connected to, and communicate with, other components of embodiments of the system 20, e.g., as indicated by the connections exemplarily depicted in FIG. 1, over one or more communication networks represented by such connections.
- FIG. 5 depicts an embodiment of a method 500 of intervening in the operation of the smart contract 40 in the distributed ledger system 24.
- the method 500 begins at step 502.
- a complaint is received regarding the smart contract 40 from a complainant.
- the complaint contains information alleging an illegality or other problem with the operation of the smart contract 40.
- the complaint includes an identifier identifying the smart contract 40, such as an address of the smart contract 40 in the distributed ledger system 24, and one or more assertions that the smart contract 40 has violated a legal rule.
- the complaint may identify a legal jurisdiction, such as a state or country, etc., identify a law or rule of the identified legal jurisdiction, such as a rule related to the conducting of financial transactions, etc., and assert that the smart contract 40 violates the identified law.
- the complaint may identify a portion of a legal contract between a person or system originating the complaint and the owner or operator of the smart contract 40, which legal contract the smart contract 40 is intended to implement, and assert that the smart contract 40 implements something other than the identified portion of the legal contract.
- the complaint is received at the virtual court server system 28 from a complainant operating the complainant system 36.
- the complainant may transmit a file containing the complaint to the virtual court server system via the complainant system interface module 48.
- the complainant is a person or other legal entity, such as a corporation, etc., that asserts the illegality or other problem against the smart contract 40.
- the complainant typically has interacted with the smart contract 40 and observed the asserted illegality or other problem, and is turning to the system 20 for intervention in the operation of smart contracts for relief, much in a similar way to how a complainant turns to a court of a jurisdiction for relief for a legal complaint.
- the virtual court server system 28 is typically operated by an organization or other entity with a mandate to conduct intervention in the operation of smart contracts in the distributed ledger system 24.
- the virtual court server system 28 may be operated by an organization that created or operates the distributed ledger system 24.
- step 506 input regarding the complaint is received from one or more judges.
- the input contains information regarding a judgment of the complaint.
- the received input may include a vote from each of the one or more judges as to whether the complaint is agreed with and/or valid, and the judgment being that the smart contract 40 is illegal or has the indicated problem, or whether the complaint is disagreed with and/or invalid, and the judgment being that the smart contract 40 is not illegal or does not include the identified problem.
- the input regarding the complaint is received at the virtual court server system 28 from the one or more judges operating the one or more judge systems 32.
- a judge may transmit a file or other data containing the input regarding the complaint to the virtual court server system 28 via the judge system interface module 44.
- the one or more judges are people or other legal entities, such as corporations, etc., elected or otherwise designated within the operation of the distributed ledger system 24 to pass judgment on complaints.
- the judges may be elected via an election by users or other stakeholders in the distributed ledger system 24.
- the judges are typically required to satisfy one or more criteria to run for election, such as being authenticated users of the distributed ledger system 24, submitting an application to be a judge, etc.
- the judges are appointed by the organization or other entity with the mandate to conduct intervention in the operation of smart contracts, such as the organization that created or operates the distributed ledger system 24.
- the one or more judges providing input may include a predetermined number of judges organized according to one or more of a geographic region, a legal jurisdiction, a smart contract type, a legal rule type, etc.
- a judgment of the complaint is determined based on the received input.
- the determined judgment includes whether the complaint is upheld, in whole or part, and the smart contract 40 judged illegal or having the indicated problem, or whether the complaint is dismissed, and the smart contract 40 judged to not be illegal or have the indicated problem.
- the determination is performed by combining the inputs received from the one or more judges. For example, the determination may be performed by adding together votes received from the one or more judges, and then determining whether a threshold has been reached regarding a judgment for the contract.
- the threshold may selected according to various different voting systems. In one example, the threshold is whether one of the options for the judgment, i.e., it being upheld or dismissed, reaches a plurality of the votes of the one or more judges. In another example, the threshold is whether one of the options for the judgment reaches a majority of the votes of the one or more judges.
- the determination is conducted by the virtual court server system based on the received input from the one or more judges, such as by the control module acting on the inputs received via the judge system interface module.
- step 508 it is determined that the judgment is that the smart contract 40 has the illegality or other problem indicated in the complaint, the method proceeds to step 510.
- the determined judgment is recorded in a judgment database.
- the judgment database may be stored in the virtual court server system 28 and/or in the distributed ledger system 24.
- the determined judgment is recorded in the judgment database module 60.
- the judgment is recorded by the virtual court server system 28, such as by the control module 56 storing the judgment in the judgment database module 60.
- the judgment database module 60 provides a database to store and provide access to the judgments of smart contracts.
- the control module 56 provides as inputs to a write function of the judgment database module 60 an identifier of the smart contract 40, such as an address of the smart contract 40, and the judgment.
- the judgment may be recorded in a data structure of the distributed ledger system 24 representing the judgment database using a smart contract of the distributed ledger system 24, such as the court contract 42.
- FIG. 6 depicts an embodiment of the court contract 42, including one or more judgment database updating functions 83, one or more judgment database checking functions 84, and one or more judgment database data structures 85.
- the judgment database updating function 83 includes program instructions to execute a write to the judgment database data structure 85, which contains the judgment database.
- the write can include as an input an identification of the smart contract 40, such as an address of the smart contract 40, and the judgment, such as, e.g., a Boolean or integer value indicating that a judgment against the smart contract 40 exists, and as a result of its execution record the identifiers of the contract 40 and judgment as a corresponding pair of data values in the data structure 85.
- an identification of the smart contract 40 such as an address of the smart contract 40
- the judgment such as, e.g., a Boolean or integer value indicating that a judgment against the smart contract 40 exists
- the virtual court server system 28 To record the judgment, the virtual court server system 28 generates and transmits, such as via the distributed ledger system interface module 52, to at least one distributed node 66 of the distributed ledger system 24 a transaction addressed to the court contract 42 invoking the judgment database updating function 83.
- the court contract is executed to execute the judgment database updating function 83 to record the judgment in the judgment database data structure 85 of the court contract 42.
- the exemplary contract Court ⁇ ⁇ includes an isLegal[] data structure, an updateStatus() function, and a checkStatus() function.
- the judgment database is implemented using the isLegal[] data structure
- the judgment database updating function is implemented using the update Status() function.
- the updateStatus() function updates the isLegal[] data structure with a judgment b for an indicated address when the function is triggered by a transaction from the court contract owner.
- the court contract 42 may include only any subset of, or an alternative connection of, the features depicted in or discussed herein in regard to FIG. 6.
- step 508 it is determined that the judgment is that the smart contract 40 does not have the illegality or other problem indicated in the complaint, the method proceeds to step 512.
- an inquiry is received regarding whether a judgment against the smart contract 40 exists.
- the inquiry includes an identifier identifying the smart contract 40, such as an address of the smart contract 40 in the distributed ledger system 24, and a request for identification of any judgments against the smart contract 40.
- the inquiry may be received by a component of the virtual court server system 28 or the distributed ledger system 24.
- the inquiry is received by the virtual court server system 28.
- the inquiry may be received via the distributed ledger system interface module 52.
- the inquiry may be received by a smart contract such as the court contract 42. For example, returning to FIG.
- the inquiry may be received by the court contract 42 as part of it being executed to perform the judgment database checking function 84.
- the judgment database checking function 84 includes program instructions to execute a read of the judgment database data structure 85, which contains the judgment database. In the exemplary contract Court ⁇ ⁇ discussed above, this may take the form of a call to or invocation of the checkStatus() function.
- the inquiry is received from and/or initiated by a component of the distributed ledger system 24 in response to launching or requesting to launch execution of the smart contract 40.
- the inquiry may be received from and/or initiated by the smart contract 40 itself, such as as a result of execution of at least one program instruction of the smart contract 40, or received from and/or initiated by the virtual machine 78 of a distributed node 66 of the distributed ledger system 24 that is launching execution of the smart contract 24.
- the judgment database is read to determine whether any judgment against the smart contract 40 has been recorded in the judgment database.
- the judgment database may be read by a component of the virtual court server system 28 or the distributed ledger system 24.
- the control module 56 provides as inputs to a read function of the judgment database module 60 an identifier of the smart contract 40, such as an address of the smart contract 40.
- the court contract 42 may be executed to perform the judgment database checking function 84 to perform a read of the data structure 85 for any judgments associated with the contract 40.
- the read can include as an input an identification of the smart contract 40, such as an address of the smart contract 40, and as a result of its execution return any judgment, such as, e.g., a Boolean or integer value indicating that a judgment against the smart contract 40 exists, stored in the data structure 85 in association with the identifier of the smart contract 40.
- this make take the form of executing the checkstatus() function to perform a read of the isLegal[] data structure for a judgment value corresponding to the address a.
- a response to the inquiry is provided to the requesting component.
- the response indicates whether any judgment against the indicated smart contract 40 exists in the judgment database.
- the response is transmitted by the virtual court server system 28.
- the response may be transmitted by the virtual court server system control module 56 via the distributed ledger system interface module 52.
- the response is transmitted to the requesting component of the distributed ledger system 24.
- the response may be transmitted to the smart contract 40 or virtual machine 78 of the distributed ledger system 24 that initiated the inquiry.
- the virtual court server system 56 may generate a transaction containing the response and transmit the transaction to at least one node 66 of the distributed ledger system 24.
- the transaction may be addressed to the smart contract 40, or to another smart contract acting as an intermediary, such as as an oracle, for the smart contract 40. In the case of using an intermediary or oracle contract, the
- the intermediary or oracle contract may transmit a second transaction to or execute a call to the requesting smart contract 40 to deliver the response, or alternatively the requesting smart contract 40 may transmit a transaction to or execute a call to the intermediary or oracle contract to retrieve the response.
- the virtual court server system 28 may provide a communication to the virtual machine module 78 of a distributed node 66 of the distributed ledger system 24 containing the response, such as via the distributed ledger system interface module 52.
- the court contract 42 performs the read of the judgment database stored in the judgment database data structure 85 of the court contract 42
- the court contract outputs the response.
- the court contract 42 may be invoked by the smart contract 40 to perform the judgment database checking function 84, and output the result of the read of the judgment database data structure 85 to the smart contract 40.
- this may take the form of the checkstatus() function outputting the result of this function to the invoking smart contract.
- a method of determining a judgment for a smart contract in a distributed ledger system may include only any subset of, or an alternative ordering of, the features depicted in or discussed above in regard to FIG. 5.
- FIG. 7 depicts an embodiment of another method 700 of intervening in the operation of the smart contract 40 based on the judgment for the smart contract 40.
- the method 700 of intervening in the operation of the smart contract 40 may be complimentary to the method 500 of intervening in the operation of the smart contract 40.
- the method 500, or portions thereof may be performed by a first set of components, such as one or more components of the virtual court server system 28 and/or distributed ledger system 24, as discussed herein, and the method 700, or portions thereof, may be performed by a second set of components, such as one or more components of the virtual court server system 28 and/or distributed ledger system 24, as discussed herein, in concert with the performance of the method 500.
- the method 600 begins at step 702.
- execution of the smart contract 40 is launched or requested to be launched.
- Execution of the smart contract 40 is launched in response to events in the distributed ledger system 24.
- execution of the smart contract 24 is launched in response to a transaction addressed to the smart contract 40 being transmitted to a node 66 of the distributed ledger system 24, such as by a component of a distributed application of which the smart contract 40 is a part, or in response to a call to the smart contract 40 that does not require a transaction, such as by another smart contract or other component.
- Execution of the smart contract 40 is performed by the virtual machine module 78 of at least one distributed node 66 of the distributed ledger system 24.
- a judgment checking function is executed.
- the judgment checking function checks whether a judgment against the smart contract exists in the judgment database, such as in the judgment database module 60 or the judgment database data structure 85 of the court contract 42.
- the judgment checking function is executed prior to other, non- judgment-checking functions of the smart contract 40, so that if a judgment against the smart contract 40 exists, intervention in the operation of the smart contract 40 can be performed before such other functions of the smart contract 40 are executed.
- the judgment checking function may be or include a function of a contract of the distributed ledger system 24, such as the court contract 42 or the smart contract 40; a function of another component of the distributed ledger system 24, such as the virtual machine 78 of a distributed node 66 of the distributed ledger system 24; a function of a component of the virtual court server system 28; or combinations thereof.
- the judgment checking function is or includes a function of a contract of the distributed ledger system 24, such as the court contract 42, invoked by the smart contract 40, which checks a judgment database stored as a data structure of such a contract, such as the judgment database data structure 85.
- FIG. 8 depicts an embodiment of the smart contract 40 including one or more judgment checking functions 86 and one or more other functions 90.
- the one or more other functions 90 include program instructions to perform other functionality of the smart contract 40, such as in a role as part of a distributed application.
- the judgment checking function 86 includes program instructions to invoke another contract of the distributed ledger system, such as the court contract 42, to check whether a judgment for the smart contract 40 exits in a data structure of such a contract, such as the judgment database data structure 85.
- the smart contract 40 may execute the judgment checking function 86, which may invoke the court contract 42 to perform the judgment database checking function 84, which determines whether a judgment exists for the smart contract 40 in the data structure 85 of the court contract 42.
- the invocation of the court contract 42 by the smart contract 40 may communicate as an input to the judgment database checking function 84 an identification of the smart contract 40, such as an address of the smart contract 40, and output as a result of the execution of the judgment database checking function 84 an indication of whether a judgment exists against the smart contract 40.
- the exemplary contract someContract ⁇ ⁇ includes functions someConract() and someFunction().
- the function someConract() may be executed upon launching, and invokes an instance of the Court ⁇ ⁇ contract, providing it with an input of the address a of the contract someContract ⁇ ⁇ .
- the function someFunction() which performs other functionality of the smart contract (the details of which are omitted for simplicity of illustration and replaced by a comment to "do stuff), and which may be invoked by a transaction addressed to the contract, performs this functionality conditional upon the output of an invocation of the checkStatus() function of the instantiated Court ⁇ ⁇ contract, which returns an indication of whether there is a judgment against the contract, such as, e.g., a "1" or “true” for there being a judgment against the contract, and a "0" or “false” for there being no judgment against the contract.
- the judgment checking function is or includes a function of the smart contract 40 itself.
- the judgment checking function 86 includes program instructions to check whether a judgment for the smart contract exits in the judgment database module 60.
- the judgment checking function 86 includes one or more predetermined instructions of a programming language in which the smart contract 40 is written that executes a read of the judgment database, such as the judgment database module 60, to determine if it includes a judgment for the smart contract 40.
- the read can include as input the address of the smart contract 40.
- the predetermined instruction may be configured in the programming language to execute the read to the judgment database.
- the predetermined instruction may communicate with the judgment database module 60 via the distributed ledger system interface module 52 of the virtual court server system 28.
- the judgment checking function is or includes a function of the virtual machine 78 of the distributed node 66 executing the smart contract 40.
- FIG. 9 depicts an embodiment of the virtual machine 78 including one or more judgment checking functions 94 and one or more other functions 98.
- the one or more other functions 98 perform functionality of the virtual machine 78, such as to execute the smart contract 40.
- the judgment checking function 94 performs functionality to check whether a judgment for the smart contract 40 exits in the judgment database, such as in the judgment database module 60.
- the judgment checking function 94 may execute a read of the judgment database, such as the judgment database module 60, to determine if it includes a judgment for the smart contract 40.
- the read can include as input the address of the smart contract 40.
- the virtual machine may communicate with the judgment database module 60 via the distributed ledger system interface module 52 of the virtual court server system 28.
- the smart contract 40 may include program instructions that invoke the judgment checking function and output the result.
- the statement "if(court.checkStatus(. . .)) ⁇ . . . ⁇ else ⁇ . . . ⁇ ” determines whether a judgment against the smart contract exists as a function of the output of the checkStatus() function of the Court ⁇ ⁇ contract.
- the smart contract 40 may include a program instruction "if (legalToken()) (suicide(recipient); ⁇ " which invokes a judgment checking function
- the virtual machine may similarly invoke the judgment checking function and taken an action as a function of the output, as discussed further below.
- step 708 If at step 708, it is determined that a judgment does not exist for the smart contract 40, the method proceeds to step 712. At step 712, execution of the smart contract 40 continues without any intervention. For embodiments in which the judgment checking function is or includes a function of the smart contract 40, the smart contract 40 proceeds to executing the other function(s) 90 of the smart contract 40. For embodiments in which the judgment checking function is or includes a function of the virtual machine 78, the virtual machine proceeds to execute the smart contract 40.
- continuing execution of the smart contract includes at least one of: conducting a financial transaction between at least two parties by the smart contract, transferring ownership of a digital or physical asset between at least two parties by the smart contract, performing an identification of an individual to authorize access to restricted systems by the smart contract, or triggering by the smart contract an electronic device to generate an electrical signal to control operation of an electrical, mechanical or electromechanical apparatus.
- step 708 If at step 708, it is determined that a judgment does exist for the smart contract 40, the method proceeds to step 710.
- intervention in the operation of the smart contract 40 is performed to prevent the contract 40 from executing.
- the smart contract 40 may abort operation of the smart contract before other functionality is performed.
- someContract ⁇ ⁇ the statement "if(court.checkStatus(. . .)) ⁇ . . . ⁇ else ⁇ . . . ⁇ ” performs the "else ⁇ . . . ⁇ content, which may include nothing, or notification of the legal status, etc.
- the smart contract may execute a self destruct function to prevent current and future operation of the smart contract 40.
- the program instruction calls a self destruct function "suicide()" to prevent current and future operation of the smart contract 40.
- the self destruct function may delete data of the smart contract 40 from the distributed ledger system 24.
- the judgment checking function is a function of the virtual machine 78
- the virtual machine 78 does not execute and/or stops execution of the smart contract 40. The method ends at step 714.
- a method of intervening in the operation of a smart contract based on a judgment for the smart contract may include only any subset of, or an alternative ordering of, the features depicted in or discussed above in regard to FIG. 7.
- a method of determining a judgment against a smart contract and/or intervening in the operation of a smart contract based on the judgment may include any combination of the methods of FIGS. 5 and 7, or any combination of any subset and/or alternative ordering of the features of such methods.
- Additional embodiments of the virtual court server system 28, judge system(s) 32, complainant system 36, distributed ledger system 24, other system(s) 38 and associated methods 500, 700 of determining a judgment of a smart contract in a distributed ledger system and intervening in the operation of a smart contract based on a judgment, as discussed herein, are possible.
- any feature of any of the embodiments of these systems and methods described herein may be used in any other embodiment of these systems and methods.
- embodiments of these systems and methods may include only any subset of the components or features of these systems and methods discussed herein.
Landscapes
- Business, Economics & Management (AREA)
- Tourism & Hospitality (AREA)
- Engineering & Computer Science (AREA)
- Marketing (AREA)
- Health & Medical Sciences (AREA)
- Economics (AREA)
- General Health & Medical Sciences (AREA)
- Human Resources & Organizations (AREA)
- Technology Law (AREA)
- Primary Health Care (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201662396293P | 2016-09-19 | 2016-09-19 | |
PCT/IB2017/055639 WO2018051305A1 (en) | 2016-09-19 | 2017-09-18 | Systems and methods for interception of smart contracts |
Publications (1)
Publication Number | Publication Date |
---|---|
EP3516615A1 true EP3516615A1 (en) | 2019-07-31 |
Family
ID=66998812
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP17787256.1A Ceased EP3516615A1 (en) | 2016-09-19 | 2017-09-18 | Systems and methods for interception of smart contracts |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP3516615A1 (en) |
CN (1) | CN109997166B (en) |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5895450A (en) * | 1995-02-22 | 1999-04-20 | Sloo; Marshall A. | Method and apparatus for handling complaints |
CN1965313A (en) * | 2003-12-31 | 2007-05-16 | 汤姆森环球资源股份公司 | Systems, methods, software and interfaces for integration of case law with legal briefs, litigation documents, and/or other litigation-support documents |
US20150379510A1 (en) * | 2012-07-10 | 2015-12-31 | Stanley Benjamin Smith | Method and system to use a block chain infrastructure and Smart Contracts to monetize data transactions involving changes to data included into a data supply chain. |
CN102945264B (en) * | 2012-10-24 | 2017-02-15 | 浪潮通用软件有限公司 | Method for intelligently starting distributed transaction |
US20140244521A1 (en) * | 2013-02-27 | 2014-08-28 | Datanalytics, Inc. d/b/a Juristat | Systems and methods for legal data processing |
CN104793988B (en) * | 2014-01-20 | 2019-01-22 | 阿里巴巴集团控股有限公司 | The implementation method and device of integration across database distributed transaction |
CN104090863A (en) * | 2014-07-24 | 2014-10-08 | 高德良 | Intelligent legal instrument generating method and system |
WO2016053760A1 (en) * | 2014-09-30 | 2016-04-07 | Raistone, Inc. | Systems and methods for transferring digital assets using a de-centralized exchange |
-
2017
- 2017-09-18 CN CN201780057248.3A patent/CN109997166B/en active Active
- 2017-09-18 EP EP17787256.1A patent/EP3516615A1/en not_active Ceased
Also Published As
Publication number | Publication date |
---|---|
CN109997166B (en) | 2024-02-06 |
CN109997166A (en) | 2019-07-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10984494B2 (en) | Systems and methods for interception of smart contracts | |
US11250439B2 (en) | Systems and methods for smart contract intervention | |
CN108881187B (en) | Cross-link data transmission method and device suitable for permission link scene | |
US11693840B2 (en) | Database storing authenticated skill-based attributes | |
US20220138212A1 (en) | Blockchain implementing reliability database | |
US20220066997A1 (en) | Blockchain implementing reliability database | |
US11308073B2 (en) | Database node functional testing | |
US20190251075A1 (en) | Asset management method and apparatus, and electronic device | |
US11502828B2 (en) | Authenticating chaincode to chaincode invocations of a blockchain | |
JP2021504833A (en) | Asset management methods and equipment, and electronic devices | |
US9742808B2 (en) | Data access policies | |
US11669532B2 (en) | Blockchain implementing reliability database | |
WO2020074358A1 (en) | Blockchain notification board storing blockchain resources | |
CN103516718A (en) | Identity risk score generation and implementation | |
WO2021148904A1 (en) | Index structure for blockchain ledger | |
JP2022525551A (en) | Preventing erroneous transmission of copies of data records to distributed ledger systems | |
US11792022B2 (en) | Resolution of conflicting data | |
CN113472781B (en) | Service acquisition method, server and computer readable storage medium | |
EP3516615A1 (en) | Systems and methods for interception of smart contracts | |
AU2018332539B2 (en) | Systems and methods for smart contract intervention | |
US11586760B2 (en) | System and method for associating multiple logins to a single record in a database | |
US20220027260A1 (en) | Automatically capturing weather data during engineering tests | |
EP3685333A1 (en) | Systems and methods for smart contract intervention | |
US20240249013A1 (en) | Data protection through collaborative association | |
US20220385677A1 (en) | Cloud-based security for identity imposter |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20190409 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40007711 Country of ref document: HK |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20200928 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R003 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED |
|
18R | Application refused |
Effective date: 20220203 |