# US 2020/0394085 A1 · Smart contract information redirect to updated version of smart contract

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0394085 A1
- Document ID: US20200394085A1
- Status: Published application
- Kind: A1
- Application number: 16/442,836
- Filed: 2019-06-17
- Published: 2020-12-17
- Earliest claimed: 2019-06-17
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Marc Edward MERCURI
- Web page: https://patentgrep.com/patent/US20200394085A1

## CPC

- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The disclosed technology is generally directed to blockchain technology. In one example of the technology, a call to a first smart contract function of a first smart contract is received from a requestor. A redirection policy status of the first smart contract function is evaluated. Responsive to an evaluation that a redirection policy status of the first smart contract function is a status indicating “redirect,” a first event is communicated to the requestor, such that the first event includes an indication that an updated version of the first smart contract exists, such that the first event includes metadata, and such that the metadata includes information associated with requesting a function call to the updated version of the first smart contract.

## Claims

### Claim 1

An apparatus, comprising:
a device including at least one memory adapted to store run-time data for the device, and at least one processor that is adapted to execute processor-executable code that, in response to execution, enables the device to perform actions, including:
receiving, from a requestor, a call to a first smart contract function of a first smart contract;
evaluating a redirection policy status of the first smart contract function; and
responsive to an evaluation that a redirection policy status of the first smart contract function is a status indicating “redirect,” communicating a first event to the requestor, such that the first event includes an indication that an updated version of the first smart contract exists, such that the first event includes metadata, and such that the metadata includes information associated with requesting a function call to the updated version of the first smart contract.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the metadata includes a ledger contract identifier.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the metadata includes a ledger endpoint of a distributed ledger associated with the updated version of the first smart contract.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the metadata includes a ledger type of a distributed ledger associated with the updated version of the first smart contract.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the metadata includes a common name of a distributed ledger associated with the updated version of the first smart contract.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the metadata includes a function signature.

### Claim 7 (depends on 6)

The apparatus of claim 6, wherein the function signature includes at least a name of a function on the updated version of the first smart contract, and parameters of the function on the updated version of the first smart contract.

### Claim 8 (depends on 1)

The apparatus of claim 1, the actions further including:
enabling a user to set a redirection policy status of each function of a plurality of functions of the first smart contract, wherein the plurality of functions of the first smart contract includes the first smart contract function, and wherein, for each function of the plurality of functions of the first smart contract, the possible redirection policy statuses of the function include: a status indicating “allowed,” and the status indicating “redirect.”

### Claim 9 (depends on 8)

The apparatus of claim 8, wherein, for each function of the plurality of functions of the first smart contract, the possible redirection policy statuses of the function also include: a status indicating “disallowed.”

### Claim 10

A method, comprising:
receiving a communication, wherein the communication includes a call from a requestor to a first smart contract function of a first smart contract;
determining a redirection policy status associated with the first smart contract function; and
via at least one processor, responsive to an evaluation that a redirection policy status of the first smart contract function is a status indicating “redirect,” causing a first event to be communicated to the requestor, such that the first event includes an indication that an updated version of the first smart contract exists, such that the first event includes metadata, and such that the metadata includes information associated with requesting a function call to the updated version of the first smart contract.

### Claim 11 (depends on 10)

The method of claim 10, wherein the metadata includes a ledger contract identifier.

### Claim 12 (depends on 10)

The method of claim 10, wherein the metadata includes a ledger endpoint of a distributed ledger associated with the updated version of the first smart contract.

### Claim 13 (depends on 10)

The method of claim 10, wherein the metadata includes a ledger type of a distributed ledger associated with the updated version of the first smart contract.

### Claim 14 (depends on 10)

The method of claim 10, wherein the metadata includes a function signature.

### Claim 15 (depends on 10)

The method of claim 10, further comprising:
enabling a user to set a redirection policy status of each function of a plurality of functions of the first smart contract, wherein the plurality of functions of the first smart contract includes the first smart contract function, and wherein, for each function of the plurality of functions of the first smart contract, the possible redirection policy statuses of the function include: a status indicating “allowed,” and the status indicating “redirect.”

### Claim 16

A processor-readable storage medium, having stored thereon process-executable code that, upon execution by at least one processor, enables actions, comprising:
responsive to a call to a first smart contract function of a first smart contract from a requestor, evaluating a status of the first smart contract function; and
responsive to an evaluation that a status of the first smart contract function is a status indicating “redirect,” communicating an indication that an updated version of the first smart contract exists, and further communicating metadata, such that the metadata includes information associated with requesting a function call to the updated version of the first smart contract.

### Claim 17 (depends on 16)

The processor-readable storage medium of claim 16, wherein the metadata includes a ledger contract identifier.

### Claim 18 (depends on 16)

The processor-readable storage medium of claim 16, wherein the metadata includes a ledger endpoint of a distributed ledger associated with the updated version of the first smart contract.

### Claim 19 (depends on 16)

The processor-readable storage medium of claim 16, wherein the metadata includes a ledger type of a distributed ledger associated with the updated version of the first smart contract.

### Claim 20 (depends on 16)

The processor-readable storage medium of claim 16, the actions further comprising:
enabling a user to set a redirection policy status of each function of a plurality of functions of the first smart contract, wherein the plurality of functions of the first smart contract includes the first smart contract function, and wherein, for each function of the plurality of functions of the first smart contract, the possible redirection policy statuses of the function include: a status indicating “allowed,” and the status indicating “redirect.”
