CN110910140A - Implementation method, front-end server, client, device and medium of smart contract - Google Patents
Implementation method, front-end server, client, device and medium of smart contract Download PDFInfo
- Publication number
- CN110910140A CN110910140A CN201910964145.6A CN201910964145A CN110910140A CN 110910140 A CN110910140 A CN 110910140A CN 201910964145 A CN201910964145 A CN 201910964145A CN 110910140 A CN110910140 A CN 110910140A
- Authority
- CN
- China
- Prior art keywords
- event
- verification
- ethereum
- client
- address
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/405—Establishing or using transaction specific rules
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
- G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Theoretical Computer Science (AREA)
- Finance (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Software Systems (AREA)
- Strategic Management (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- General Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Medical Informatics (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
本发明公开了一种智能合约的实现方法，包括：以太坊前置服务器获取验证方案可升级钱包的合约地址，根据所述合约地址生成智能合约部署请求，并发送至以太坊客户端；以太坊客户端接收所述智能合约部署请求，将智能合约变量设置为验证方案可升级钱包的合约地址；以太坊前置服务器获取验证逻辑地址，根据所述验证逻辑地址生成验证逻辑更新请求，并发送至以太坊客户端；所述以太坊客户端接收所述验证逻辑更新请求，将验证方案可升级钱包中的验证逻辑变量更新为验证逻辑地址，并向以太坊网络广播验证逻辑变量的更新结果。本发明解决了解决现有多签钱包的验证逻辑固定、更新不灵活的的问题。
The invention discloses a method for realizing a smart contract, comprising: an Ethereum front-end server obtains a contract address of an upgradeable wallet of a verification scheme, generates a smart contract deployment request according to the contract address, and sends it to the Ethereum client; The client receives the smart contract deployment request, and sets the smart contract variable to the contract address of the wallet that can be upgraded by the verification scheme; the Ethereum front-end server obtains the verification logic address, generates a verification logic update request according to the verification logic address, and sends it to The Ethereum client; the Ethereum client receives the verification logic update request, updates the verification logic variable in the verification scheme upgradeable wallet to the verification logic address, and broadcasts the update result of the verification logic variable to the Ethereum network. The invention solves the problems that the verification logic of the existing multi-signature wallet is fixed and the update is inflexible.
Description
Technical Field
The invention relates to the technical field of information, in particular to an intelligent contract implementation method, a front-end server, a client, equipment and a storage medium.
Background
In a standardized enterprise, an important transaction, especially an operation involving a large amount of funds, often needs to be executed after being approved and confirmed by a plurality of responsible persons, so as to reduce the possibility of misoperation and improve the accuracy of the operation.
Since the block chain industry enters the enterprise, due to the limitation of the block chain industry, one transaction can only be initiated by a single account, which is easy to cause transfer errors and cannot return. On the other hand, if the private key of the single account is leaked, the assets are completely in an unsafe state. This is the most serious thing for enterprise-level applications, and a investment loss may have a huge impact on the enterprise. Existing multi-sign wallets further improve security by requiring multiple parties to agree upon prior to the execution of a transaction. This can easily reach through intelligent contract on the ether mill platform, holds the asset (for example ethernet coin or other token) through intelligent contract, and a transaction can only carry out after the verification logic contract of setting up through wallet in advance to solved the single point that the private key held the account and fallen down the problem, avoided the private key to lose effectively or leak the condition that probably leads to losing of all assets in the account. However, the existing multi-signature wallets have different verification logic contracts, and different multi-signature wallets cannot be commonly used. Once the verification logic contract needs to be changed, the wallet cannot be used, and a developer needs to re-deploy a new multi-sign wallet to the ethernet network, so that the process is complicated and inflexible.
Therefore, finding a method for solving the problems of fixed verification logic and inflexible update of the existing multi-signature wallet becomes a technical problem to be solved by those skilled in the art.
Disclosure of Invention
The embodiment of the invention provides an intelligent contract implementation method, a front-end server, a client, equipment and a storage medium, and aims to solve the problems that the verification logic of the existing multi-signature wallet is fixed and the updating is not flexible.
An implementation method of an intelligent contract comprises the following steps:
the method comprises the steps that an Ethernet front-end server obtains contract addresses of upgradable wallets of a verification scheme, and an intelligent contract deployment request is generated according to the contract addresses;
the Ethernet workshop front server sends the intelligent contract deployment request to an Ethernet workshop client on an Ethernet workshop network;
the Ethernet workshop client receives the intelligent contract deployment request, obtains a contract address of the verification scheme upgradable wallet, sets an intelligent contract variable as the contract address, and broadcasts a setting result to the Ethernet workshop network;
the Ethernet workshop front-end server acquires a verification logic address and generates a verification logic updating request according to the verification logic address;
the Ethernet workshop front server sends the verification logic updating request to an Ethernet workshop client on an Ethernet workshop network;
and the Ethernet workshop client receives the verification logic updating request to obtain a verification logic address, updates the verification logic variable in the verification scheme upgradable wallet into the verification logic address, and broadcasts the updating result of the verification logic variable to the Ethernet workshop network.
Further, the method further comprises:
the Ethernet workshop front-end server acquires event information of an event to be executed and generates an event request according to the event information;
the Ethernet workshop front server sends the event request to the Ethernet workshop client;
and the Ethernet workshop client receives the event request, generates an event structure, and calls a verification scheme according to the verification logic address to verify the event structure.
Further, the method further comprises:
if the event structure is verified successfully, the Etherhouse client executes the event to be executed, and then deletes the event information of the event to be executed from the Etherhouse network;
and sending the execution result of the event to be executed to the Ethernet workshop front-end server and broadcasting the execution result to the Ethernet workshop network.
Further, the method further comprises:
if the event structure is failed to be verified, the Ethernet workshop client deletes the event information of the event to be executed from the Ethernet workshop network;
and sending the execution result of the event to be executed to the Ethernet workshop front-end server and broadcasting the execution result to the Ethernet workshop network.
Further, the event structure refers to an information body created by the ether house client according to the event information of the event to be executed;
the event structure body comprises data to be requested, an event name, the number of praise persons and the number of disrespect persons; the data to be requested refers to operation direction information of the authentication scheme upgradeable wallet.
An Etherhouse front-end server comprising:
the contract address acquisition module is used for acquiring a contract address of the verification scheme upgradable wallet and generating an intelligent contract deployment request according to the contract address;
the deployment request module is used for sending the intelligent contract deployment request to an Ethernet workshop client on an Ethernet workshop network;
the verification address acquisition module is used for acquiring a verification logic address and generating a verification logic updating request according to the verification logic address;
the updating request module is used for sending the verifying logic updating request to an Ethernet workshop client on the Ethernet workshop network;
the event acquisition module is used for acquiring event information of an event to be executed and generating an event request according to the event information;
and the event request module is used for sending the event request to the Etherhouse client.
An Etherhouse client comprising:
the system comprises a deployment request receiving module, a contract address generation module and a contract address generation module, wherein the deployment request receiving module is used for receiving an intelligent contract deployment request sent by an Ethernet front-end server to obtain a contract address of an upgradable wallet of a verification scheme;
the deployment module is used for setting the intelligent contract variable as the contract address and broadcasting the setting result to the Ethernet network;
the updating request receiving module is used for receiving a verification logic updating request sent by the Etherhouse front-end server to obtain a verification logic address;
and the updating module is used for updating the verification logic variable in the verification scheme upgradable wallet into the verification logic address and broadcasting the updating result of the verification logic variable to the Ethernet workshop network.
Further, the ethernet house client includes:
and the verification module is used for receiving an event request of an event to be executed sent by the Ethernet front-end server, generating an event structure, and calling a verification scheme according to the verification logic address to verify the event structure.
The first execution module is used for executing the event to be executed if the event structure is verified successfully, and then deleting the event information of the event to be executed from the Ethernet workshop;
the second execution module is used for deleting the event information of the event to be executed from the Ethernet workshop network if the event structure fails to be verified;
the event request comprises event information of an event to be executed.
A computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the ethernet front-end server or the ethernet client in the implementation method of the intelligent contract.
A computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the steps of the ethernet house front-end server or the ethernet house client in the implementation method of the intelligent contract.
The method comprises the steps that when a verification scheme upgradable wallet and a verification logic variable are created, a contract address of the verification scheme upgradable wallet is obtained through an Ethernet workshop front-end server, an intelligent contract deployment request is generated according to the contract address, and the intelligent contract deployment request is sent to an Ethernet workshop client on an Ethernet workshop network; the Ethernet client receives the intelligent contract deployment request, obtains a contract address of the verification scheme scalable wallet, and sets an intelligent contract variable as the contract address so as to complete the deployment of the verification scheme scalable wallet; when the verification logic is upgraded, the Ethenhouse front-end server acquires a verification logic address, generates a verification logic updating request according to the verification logic address and sends the verification logic updating request to the Ethenhouse client on the Ethenhouse network; the Ethernet workshop client receives the verification logic updating request to obtain a verification logic address, updates the verification logic variable in the verification scheme upgradable wallet into the verification logic address, and broadcasts the updating result of the verification logic variable to the Ethernet workshop network, thereby realizing the updating of the verification logic in the intelligent contract, without changing the wallet, greatly improving the universality and the practicability of the intelligent contract, and even if the verification scheme needs to be updated, the verification scheme does not need to be switched to a new intelligent contract.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
FIG. 1 is a flow chart of a method for implementing intelligent contracts in one embodiment of the present invention;
FIG. 2 is another flow diagram of a method for implementing intelligent contracts in an embodiment of the invention;
FIG. 3 is another flow diagram of a method for implementing intelligent contracts in an embodiment of the invention;
FIG. 4 is another flow diagram of a method for implementing intelligent contracts in an embodiment of the invention;
FIG. 5 is another flow diagram of a method for implementing intelligent contracts in an embodiment of the invention;
FIG. 6 is a schematic block diagram of an Etherhouse front Server in an embodiment of the present invention;
FIG. 7 is a schematic block diagram of an Etherhouse client in an embodiment of the present invention;
FIG. 8 is a schematic diagram of a computer device according to an embodiment of the invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The following describes in detail the implementation method of the intelligent contract provided in this embodiment. In this embodiment, the method for implementing the intelligent contract is applied to a system composed of an ethernet front-end server and an ethernet client. And the Ethernet workshop front-mounted server is in communication with the Ethernet workshop client through network connection. The authentication logic in the existing smart contract is fixed, that is, a smart contract, or a wallet, corresponds to an authentication logic. The verification logic in the verification scheme upgradable wallet can be replaced, and specifically, the verification logic is replaced by adding the set verification logic variable in the verification scheme upgradable wallet and assigning the verification logic variable, so that the wallet does not need to be replaced, and the universality and the practicability of the intelligent contract are greatly improved. In this embodiment, the method for implementing the intelligent contract includes: the method comprises the steps of deploying a verification scheme upgradable wallet, updating a verification logic contract in the verification scheme upgradable wallet and performing verification by using the updated verification logic contract.
As shown in fig. 1, the method for implementing the intelligent contract includes:
in step S101, the ethernet premises server obtains a contract address of the verification-scheme upgradable wallet, and generates an intelligent contract deployment request according to the contract address.
In this embodiment, the verification scheme upgradeable wallet is an intelligent contract on the blockchain. A Smart contract (Smart contract) is a computer protocol intended to propagate, verify or execute contracts in an informational manner. Smart contracts allow for trusted transactions to be conducted without third parties, which may be tracked and irreversible to optimize the security of traditional contracts and reduce the transaction costs associated with the contracts. In this embodiment, the verification scheme upgradeable wallet has modifiable verification logic variables set therein. In the verification scheme upgradeable wallet, the verification scheme acts as a plug-in module in the wallet, and the deployer can update the verification scheme by assigning values to verification logic variables.
Upon deployment of the authentication scheme upgradeable wallet, the implementational logic of the authentication scheme upgradeable wallet is written by a deployer on the Etherhouse front-end server and the contract address of the authentication scheme upgradeable wallet is set. The contract address refers to a call interface of the authentication scheme upgradeable wallet. At the same time, a designated responsibility is given by the deployer on the etherhouse front server to the owner of the authentication scheme upgradeable wallet. Alternatively, the deployer may complete the setup of the wallet owner by invoking the setOwner method in the authentication scheme upgradeable wallet, setting the parameters therein to the etherhouse address of the responsible person.
And the Ethernet workshop front-end server acquires the contract address and generates an intelligent contract deployment request according to the contract address.
In step S102, the ethernet premises server sends the intelligent contract deployment request to the ethernet premises client on the ethernet premises network.
After the intelligent contract deployment request is generated, the Ethernet workshop front-end server sends the deployment request to the Ethernet workshop so as to tell the Ethernet workshop client side on the Ethernet workshop to update the implementation contract.
In step S103, the ethernet shop client receives the intelligent contract deployment request, obtains a contract address of the verification scheme upgradable wallet, sets an intelligent contract variable as the contract address, and broadcasts a setting result to the ethernet shop network.
Here, each ethernet client is provided with an intelligent contract variable, and the intelligent contract variable is used for storing a contract address of an intelligent contract by the ethernet client so as to update the intelligent contract. The intelligent contract variables are therefore variable. In this embodiment, the ethernet client receives and parses the intelligent contract deployment request, obtains a contract address of the verification scheme scalable wallet, and sets an intelligent contract variable of itself as the contract address to complete updating of an intelligent contract. And when the subsequent Etherhouse client uses the verification scheme scalable wallet for transaction operation, the verification scheme scalable wallet is accessed through the contract address.
After the Ethernet mill client end sets the contract address, the setting result is broadcasted to the Ethernet mill network to inform other Ethernet mill client ends on the block chain to synchronously update the intelligent contract variable to the same contract address, and the intelligent contract deployment operation is recorded.
The above-described steps S101 to S103 implement deployment of the authentication scheme scalable wallet on the ethernet bay. The verification scheme upgradable wallet comprises verification logic variables, and a deployer can realize upgrading of the verification scheme in the intelligent contract by assigning values to the verification logic variables. Optionally, the following presents an implementation flow for updating the authentication scheme upgradeable authentication logic contract in the wallet.
In step S104, when the verification logic is upgraded, the ethernet front-end server obtains a verification logic address, and generates a verification logic update request according to the verification logic address.
As previously mentioned, in the verification scheme upgradeable wallet, the verification scheme acts as a plug-in module in the wallet, and the deployer can update the verification scheme by assigning values to the verification logic variables. When the verification scheme upgradable wallet is deployed, a deployer writes the verification logic on the Etherhouse front-end server and sets a verification logic address corresponding to the verification logic. The authentication logical address refers to an entry when the authentication scheme upgradeable wallet executes the authentication scheme.
And the Ethernet workshop front-end server acquires the verification logic address and generates a verification logic updating request according to the verification logic address.
In step S105, the ethernet premises server sends the request for updating the verification logic to the ethernet premises client on the ethernet premises network.
After the verification logic update request is generated, the Ethernet workshop front-end server sends the update request to the Ethernet workshop so as to tell the Ethernet workshop client to update the verification scheme in the scalable wallet.
In step S106, the ethernet workshop client receives the verification logic update request, obtains a verification logic address, updates the verification logic variable in the verification scheme upgradable wallet to the verification logic address, and broadcasts the update result of the verification logic variable to the ethernet workshop network.
The verification logic variable is used for storing a verification logic address by the Etherhouse client so as to update the verification logic. The verification logic variable is therefore variable. In this embodiment, the etherhouse client receives and analyzes the verification logic update request, obtains the verification logic address, and sets the verification logic variable of the etherhouse client as the verification logic address to complete updating of the verification scheme.
After the Ethernet workshop client end sets the verification logic address, the set result is broadcast to the Ethernet workshop network to inform other Ethernet workshop client ends on the block chain to synchronously update the verification logic variable to the same verification logic address, and the current verification logic updating operation is recorded so as to facilitate subsequent tracking.
In summary, in the embodiments of the present invention, a verification scheme upgradable wallet is deployed, where the verification scheme upgradable wallet includes a verification logic variable, and the verification logic in the verification scheme upgradable wallet is updated by assigning values to the verification logic variable, so that the verification logic is flexibly updated without replacing the wallet, and the generality and the practicability of the intelligent contract are greatly improved, and even if the verification scheme needs to be updated, the verification scheme does not need to be switched to a new intelligent contract.
Optionally, another preferred example of the present invention is provided on the basis of the embodiment in fig. 1, as shown in fig. 2, after the etherhouse client updates the verification logic variable in the verification scheme upgradable wallet to the verification logic address, the method further includes:
in step S107, the ethernet house client sends the update result to the ethernet house front server.
Here, the ethernet workshop client notifies the ethernet workshop front-end server of the update result, that is, the assignment of the current verification logic variable in the verification scheme upgradable wallet, so that the ethernet workshop front-end server knows that the deployment of the verification logic address is completed, and the ethernet workshop front-end server can initiate an operation event according to the responsible person.
Alternatively, another preferred example of the present invention is presented based on the completion of the authentication scheme of the embodiment of fig. 1 or fig. 2 to upgrade the deployment and updating of wallets, using an updated authentication logic contract to perform the verification. As shown in fig. 3, the method for implementing the intelligent contract further includes:
in step S108, the ethernet premises server obtains event information of an event to be executed, and generates an event request according to the event information.
After deployment of the authentication scheme upgradeable wallet and authentication logic is complete, a to-be-executed event is initiated on the Etherhouse front-end server by the responsible person. Here, the event to be performed includes, but is not limited to, a transfer, a digital money transaction. And the Ethernet workshop front-end server acquires the event information and generates an event request according to the event information. Optionally, the event information includes, but is not limited to, an ethernet house address of the responsible person, and an event name. The Etherhouse address of the responsible person is the account of the responsible person in the Etherhouse network, and is the unique identification of the responsible person. Typically, one responsible person corresponds to one Etherhouse address. When the verification scheme upgradeable wallet has multiple responsible persons, then all responsible persons are required to initiate the pending event through the etherhouse front-end server.
For example, assuming that the verification scheme is scalable to 3 responsible persons of the wallet, after any one person initiates the event to be executed, other persons are required to initiate the event to be executed in turn until the verification is completed. The Ethernet workshop front-end server acquires the event information of each responsible person, including but not limited to the Ethernet workshop address and the event name of the responsible person, and generates an event request. Here, the event request corresponds to each responsible person, and one responsible person corresponds to one event request.
In step S109, the ethernet premises server sends the event request to the ethernet premises client.
And each time an event request corresponding to one responsible person is generated, the Ethernet workshop front-end server sends the event request to the Ethernet workshop so as to request the Ethernet workshop client to execute the intelligent contract.
Here, each time the ethernet premises server receives event information of one responsible person, a corresponding event request is generated and sent to the ethernet premises client to request verification.
In step S110, the ethernet workshop client receives the event request, generates an event structure, and invokes a verification scheme according to the verification logic address to verify the event structure.
After receiving the event request, any ethernet mill client on the ethernet mill network assembles an event structure according to the event information in the event request, transmits the event structure into a verification scheme, and performs a preset verification operation on the current operation event through the verification scheme. The event structure body refers to a corresponding information body created when the ether house client receives an event request, and the event structure body includes, but is not limited to, data to be requested, an event name, the number of approved persons and the number of disapproved persons. The data to be requested refers to operation guide information of the verification scheme upgradable wallet, such as transaction mode, transaction amount, and accounts of two or more parties of the transaction.
As a preferred example of the present invention, the verification scheme may be used to determine whether the event request can be executed, where returning true indicates execution, and returning false indicates that execution cannot be performed. Alternatively, the verification scheme may be 2/3 with the person in charge agreeing to return true, otherwise false; or, the verification scheme may preset the weight information of each responsible person, and return true if the sum of the weight information of the responsible persons who agree to execute reaches a certain threshold, otherwise return false. It should be understood that the above verification scheme is only a specific example of the present invention, and is not intended to limit the present invention, and in practical applications, other verification schemes may be available.
Exemplarily, assuming that there is an authentication scheme upgradable wallet Z, there are three responsible persons, namely responsible person a, responsible person B, and responsible person C; the verification scheme is 2/3 the responsible person agrees to return true, otherwise false is returned. Then:
after the responsible person A initiates the event to be executed, the Etherhouse front-end server obtains the event information according to the event to be executed initiated by the responsible person A, for example, 1 ten thousand RMB money is transferred to the client XXX network to pay the money. And generating an event request according to the event information, and sending the event request to the Etherhouse client. The Etherhouse client generates an event structure according to the event information, and the method comprises the following steps: the data to be requested are network transfer, 1 ten thousand RMB, financial accounts and accounts of clients XXX; the event name is a payment to customer XXX; the number of praise persons is 1, and the number of disrespect persons is 0. And then, calling a verification scheme according to the verification logic address to verify the event structure.
After the responsible person A initiates the pending event, the responsible person C also initiates the pending event, such as a different intended customer XXX network transfer of 1 ten thousand RMB to pay. The Ethernet workshop front-end server acquires event information according to a to-be-executed event initiated by the responsible person C, generates an event request according to the event information, and sends the event request to the Ethernet workshop client. The Etherhouse client generates an event structure according to the event information, and the method comprises the following steps: the data to be requested are network transfer, 1 ten thousand RMB, financial accounts and accounts of clients XXX; the event name is a payment to customer XXX; the number of praise persons is 1, and the number of disrespect persons is 1. And then, calling a verification scheme according to the verification logic address to verify the event structure.
Responsible person B also initiates an event to be performed, such as an agreement to transfer 1 million RMB to the customer XXX network for payment of the good. The Ethernet workshop front-end server acquires event information according to a to-be-executed event initiated by the responsible person B, generates an event request according to the event information, and sends the event request to the Ethernet workshop client. The Etherhouse client generates an event structure according to the event information, and the method comprises the following steps: the data to be requested are network transfer, 1 ten thousand RMB, financial accounts and accounts of clients XXX; the event name is a payment to customer XXX; the number of praise adults is 2 and the number of disfavor adults is 1. And then, calling a verification scheme according to the verification logic address to verify the event structure.
It should be noted that the order of initiating the events to be executed by the responsible person a, the responsible person B and the responsible person C and whether to approve or disapprove the execution are only a specific example of the present invention and are not intended to limit the present invention.
Optionally, another preferred example of the present invention is provided on the basis of the embodiment of fig. 3, and as shown in fig. 4, performing the check using the updated verification logic contract further includes:
in step S111, if the event structure is successfully verified, the ethernet workshop client executes the event to be executed, and then deletes the event information of the event to be executed from the ethernet workshop network.
Optionally, since the verification scheme is used to determine whether the event request can be executed, returning true indicates execution, and returning false indicates that execution cannot be performed. And if the event structure is verified through the verification scheme and the true is output, executing the event, such as transfer.
Illustratively, as described in the foregoing example, the verification scheme may be an upgradable wallet Z, after the responsible person B initiates the to-be-executed event, the number of agreeable persons in the event structure generated by the ethernet client is 2, the number of disapproved persons is 1, after verification by the verification scheme, 2/3 responsible persons agree and return true, then the ethernet client executes the to-be-executed event, and transfers 1 ten thousand RMB to the client XXX network for payment.
After the event is executed, the Ethernet workshop client deletes the event, and broadcasts the deletion result to the Ethernet workshop network to inform the Ethernet workshop client on the block chain that the event is executed, and deletes the event synchronously to indicate that the event is finished, thereby avoiding the same event being repeatedly executed for many times.
Optionally, another preferred example of the present invention is provided on the basis of the embodiment of fig. 3, and as shown in fig. 5, performing the check using the updated verification logic contract further includes:
in step S112, if the event structure fails to be verified, the ethernet workshop client deletes the event information of the event to be executed from the ethernet workshop network.
Optionally, if false is output after the verification of the verification scheme on the event structure, the event is not executed.
Illustratively, the verification scheme as described in the previous example may upgrade wallet Z, if the responsible person B initiated the event to be performed network transfers 1 million RMB for payment of a different intended customer XXX. The Ethernet workshop front-end server acquires event information according to a to-be-executed event initiated by the responsible person B, generates an event request according to the event information, and sends the event request to the Ethernet workshop client. The Etherhouse client generates an event structure according to the event information, and the method comprises the following steps: the data to be requested are network transfer, 1 ten thousand RMB, financial accounts and accounts of clients XXX; the event name is a payment to customer XXX; the number of praise persons is 1, and the number of disrespect persons is 2. And then, calling a verification scheme according to the verification logic address to verify the event structure. And after verification of the verification scheme, if no 2/3 responsible person agrees, false is returned, the Etherhouse client does not execute the event to be executed, namely 1 ten thousand RMB coins are not transferred to the client XXX to pay the goods, the event is deleted, the deletion result is broadcasted to the Etherhouse network to inform the Etherhouse client on the blockchain that the event cannot be executed, and the event is deleted synchronously, so that the event is prevented from being executed.
Optionally, another preferred example of the present invention is provided on the basis of the embodiment in fig. 4 or fig. 5, and the implementation method of the intelligent contract further includes:
and sending the execution result of the event to be executed to an Ethernet workshop front-end server and broadcasting the execution result to an Ethernet workshop network.
Here, the ethernet workshop client notifies the ethernet workshop front-end server of the execution result, i.e. the message that the operation initiated by the responsible person is executed or can not be executed, so that the ethernet workshop front-end server outputs the execution result of the operation event to inform the responsible person.
The embodiment realizes that the wallet can be upgraded based on the verification scheme to complete the event to be executed, and the intelligent contract can be realized by calling the verification scheme through the verification logic address to verify the event structure; because the verification scheme can be modified, even if the number of persons responsible is changed or the number of persons determining whether the event request can be executed is updated, the wallet does not need to be changed, the verification logic in the wallet can be upgraded by assigning the verification logic variable, so that the verification logic can be flexibly updated under the condition that the wallet does not need to be changed, the universality and the practicability of the intelligent contract are greatly improved, and even if the verification scheme needs to be updated, the verification scheme does not need to be switched to a new intelligent contract.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
In an embodiment, an ethernet bay front server is provided, and the ethernet bay front server corresponds to the ethernet bay front server in the implementation method of the intelligent contract in the embodiment one to one. As shown in fig. 6, the ethernet premises server includes a contract address acquisition module 61, a deployment request module 62, a verification address acquisition module 63, an update request module 64, an event acquisition module 65, and an event request module 66. The functional modules are explained in detail as follows:
the contract address acquisition module 61 is used for acquiring a contract address of the verification scheme upgradable wallet and generating an intelligent contract deployment request according to the contract address;
a deployment request module 62, configured to send the intelligent contract deployment request to an ethernet workshop client on an ethernet workshop network;
a verification address obtaining module 63, configured to obtain a verification logic address, and generate a verification logic update request according to the verification logic address;
an update request module 64, configured to send the verification logic update request to an ethernet workshop client on the ethernet workshop network;
an event obtaining module 65, configured to obtain event information of an event to be executed, and generate an event request according to the event information;
an event request module 66, configured to send the event request to the ethernet house client.
For specific definition of the ethernet front-end server, reference may be made to the above definition of the implementation method of the intelligent contract, and details are not described here. The modules in the ethernet premises server described above may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In an embodiment, a taifang client is provided, and the taifang client corresponds to the taifang clients in the implementation method of the intelligent contract in the above embodiment one to one. As shown in fig. 7, the gateway client includes a deployment request receiving module 71, a deployment module 72, an update request receiving module 73, and an update module 74. The functional modules are explained in detail as follows:
a deployment request receiving module 71, configured to receive an intelligent contract deployment request sent by the ethernet front-end server, and obtain a contract address of an upgradable wallet in the verification scheme;
the deployment module 72 is configured to set the intelligent contract variable as the contract address, and broadcast the setting result to the ethernet network;
an update request receiving module 73, configured to receive a verification logic update request sent by the ethernet front end server, to obtain a verification logic address;
an updating module 74, configured to update the verification logic variable in the verification scheme upgradable wallet to the verification logic address, and broadcast the update result of the verification logic variable to the ethernet network.
Optionally, the ethernet house client includes:
the verification module 75 is configured to receive an event request of an event to be executed, which is sent by the ethernet front-end server, generate an event structure, and invoke a verification scheme according to the verification logic address to verify the event structure.
A first executing module 76, configured to execute the event to be executed if the event structure is successfully verified, and then delete the event information of the event to be executed from the ethernet network;
a second executing module 77, configured to delete the event information of the event to be executed from the ethernet network if the event structure fails to be verified.
The event request comprises event information of an event to be executed. The verification module 75 generates an event structure from the event information in the event request. The event structure body is an information body created by the Ethengfang client according to the event information of the event to be executed; the event structure body comprises data to be requested, an event name, the number of praise persons and the number of disrespect persons; the data to be requested refers to operation guide information of the authentication scheme upgradeable wallet. And then, calling a verification scheme according to the verification logic address, and verifying the event structure so as to realize the verification of the event to be executed.
Optionally, the ethernet house client includes:
and an execution result sending module 78, configured to send the execution result of the event to be executed to the ethernet premises server, and broadcast the execution result to the ethernet premises network.
For specific definition of the ethernet client, reference may be made to the above definition of the implementation method of the smart contract, and details are not described here. The various modules in the etherhouse client described above may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 8. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to realize the functions of the Ethernet workshop front-end server and the Ethernet workshop client in the implementation method of the intelligent contract.
In one embodiment, a computer device is provided, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor executes the computer program to implement the steps performed by the ethernet front-end server or the ethernet client in the method for implementing the intelligent contract.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, performs the steps performed by an ethernet premises server or an ethernet premises client in a method for implementing smart contracts.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, databases, or other media used in embodiments provided herein may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.
Claims (10)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910964145.6A CN110910140A (en) | 2019-10-11 | 2019-10-11 | Implementation method, front-end server, client, device and medium of smart contract |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910964145.6A CN110910140A (en) | 2019-10-11 | 2019-10-11 | Implementation method, front-end server, client, device and medium of smart contract |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110910140A true CN110910140A (en) | 2020-03-24 |
Family
ID=69815385
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910964145.6A Pending CN110910140A (en) | 2019-10-11 | 2019-10-11 | Implementation method, front-end server, client, device and medium of smart contract |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110910140A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112529709A (en) * | 2020-12-30 | 2021-03-19 | 四川新华万云科技有限公司 | Ether house intelligent contract implementation method based on multi-sign technology |
| EP4517629A1 (en) * | 2023-08-29 | 2025-03-05 | Giesecke+Devrient advance52 GmbH | Secure token wallet and electronic transaction system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10121141B1 (en) * | 2014-06-25 | 2018-11-06 | Urban Airship, Inc. | Updating digital wallet assets |
| CN109684189A (en) * | 2017-10-18 | 2019-04-26 | 富士通株式会社 | The logic verification method and device and computer storage medium of block chain intelligence contract |
| CN109977638A (en) * | 2019-02-22 | 2019-07-05 | 亦非云互联网技术（上海）有限公司 | Intelligent contract update method and system, storage medium and terminal based on ether mill |
| CN110018840A (en) * | 2019-04-11 | 2019-07-16 | 深圳市网心科技有限公司 | A kind of intelligence contract upgrade method, device, block chain node device and medium |
-
2019
- 2019-10-11 CN CN201910964145.6A patent/CN110910140A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10121141B1 (en) * | 2014-06-25 | 2018-11-06 | Urban Airship, Inc. | Updating digital wallet assets |
| CN109684189A (en) * | 2017-10-18 | 2019-04-26 | 富士通株式会社 | The logic verification method and device and computer storage medium of block chain intelligence contract |
| CN109977638A (en) * | 2019-02-22 | 2019-07-05 | 亦非云互联网技术（上海）有限公司 | Intelligent contract update method and system, storage medium and terminal based on ether mill |
| CN110018840A (en) * | 2019-04-11 | 2019-07-16 | 深圳市网心科技有限公司 | A kind of intelligence contract upgrade method, device, block chain node device and medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112529709A (en) * | 2020-12-30 | 2021-03-19 | 四川新华万云科技有限公司 | Ether house intelligent contract implementation method based on multi-sign technology |
| EP4517629A1 (en) * | 2023-08-29 | 2025-03-05 | Giesecke+Devrient advance52 GmbH | Secure token wallet and electronic transaction system |
| WO2025045501A1 (en) * | 2023-08-29 | 2025-03-06 | Giesecke+Devrient Advance52 Gmbh | Secure token wallet and electronic transaction system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110633963B (en) | Electronic bill processing method, electronic bill processing device, computer readable storage medium and computer readable storage device | |
| CN109040029B (en) | Method and apparatus for executing transactions in a blockchain | |
| CN109981679B (en) | Method and apparatus for performing transactions in a blockchain network | |
| CN112700246B (en) | Block chain-based data processing method, device, equipment and readable storage medium | |
| CN112003858B (en) | Block chain-based platform docking method, electronic device and storage medium | |
| CN111080455A (en) | Cross-border transaction method, device and hardware device based on blockchain | |
| CN110599349B (en) | Data processing method based on block chain network, related equipment and storage medium | |
| CN110634065B (en) | Loan information processing method, device, equipment and storage medium based on blockchain | |
| CN111666565A (en) | Sandbox simulation test method and device, computer equipment and storage medium | |
| CN110955448A (en) | Intelligent contract separation method, contract processing method, apparatus, device and medium | |
| CN110597916B (en) | Data processing method and device based on block chain, storage medium and terminal | |
| CN111524009A (en) | Transaction verification method and device for blockchain system and hardware equipment | |
| CN111325586B (en) | Bill generation method, device, server and medium based on block chain network | |
| CN110933022A (en) | Block processing method and device, computer equipment and storage medium | |
| CN111681053A (en) | Receiving and paying chain construction method and device, computer equipment and readable storage medium | |
| CN110910140A (en) | Implementation method, front-end server, client, device and medium of smart contract | |
| CN111047323A (en) | Credit transaction method and device based on block chain and hardware equipment | |
| CN111027992B (en) | Asset transaction method, device and hardware equipment based on blockchain system | |
| WO2022206433A1 (en) | Method and apparatus for pre-executing chaincode in fabric blockchain | |
| CN110599267A (en) | Electronic invoice billing method and device, computer readable storage medium and computer equipment | |
| CN113781230A (en) | Blockchain-based transaction processing method and device | |
| CN110443076B (en) | Evidence storage method and system based on real-name block chain | |
| CN110598479B (en) | A data processing method, device and computer readable storage medium | |
| CN111047322A (en) | Intelligent contract deployment method and device based on block chain and hardware equipment | |
| CN113282671A (en) | Claims settlement method and device based on block chain and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |