CN109727040B - Data publishing method, data calling method, device and storage medium - Google Patents
Data publishing method, data calling method, device and storage medium Download PDFInfo
- Publication number
- CN109727040B CN109727040B CN201910077671.0A CN201910077671A CN109727040B CN 109727040 B CN109727040 B CN 109727040B CN 201910077671 A CN201910077671 A CN 201910077671A CN 109727040 B CN109727040 B CN 109727040B
- Authority
- CN
- China
- Prior art keywords
- transaction
- event
- result
- contract
- data
- 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.)
- Active
Links
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a data publishing method, a data calling method, equipment and a storage medium, wherein the method comprises the following steps: receiving and executing a first transaction of a first event which is sent by a first data issuing terminal and issues a result which is not generated, and recording the first event to a block chain; receiving and executing a plurality of second transactions for issuing the to-be-audited result of the first event, which are sent by a plurality of data issuing terminals, recording the plurality of to-be-audited results to a block chain for the auditing terminals to acquire and audit, and generating a third transaction for issuing the result of the first event when the audit is passed; receiving and executing a third transaction, and recording the result of the first event to the block chain; the data outside the chain can be truly and accurately input into the chain.
Description
Technical Field
The present application relates to the field of block chain technology, and in particular, to a data publishing method, a data calling method, a device, and a storage medium.
Background
A gap exists between the block chain and data in the real world in the butt joint, and the prediction machine is used for truly and accurately inputting data outside the chain into the chain, so that the authenticity of the data on the chain is guaranteed, and the credible interaction between an intelligent contract and the external world is realized. The design idea of the prediction machine comprises a centralization realization mode and a decentralized realization mode completely based on a block chain, wherein the centralization mode is stable and efficient, but the trust of a block chain user is difficult to obtain; the decentralization implementation mode needs to consider not only the convenience of use but also the perfect reward and punishment mechanism of a data provider so as to ensure that the data is accurate and the system runs stably, and is very complex to implement. Many contracts on the block chain depend on data outside the chain, and the existing block chain technology cannot meet the requirement that the data outside the chain is truly and accurately input into the chain.
Disclosure of Invention
In view of the above-mentioned drawbacks and deficiencies of the prior art, it is desirable to provide a data publishing method, a data invoking method, an apparatus, and a storage medium for truly and accurately inputting data outside a chain into the chain.
In a first aspect, the present invention provides a data publishing method, including:
receiving and executing a first transaction of a first event which is sent by a first data issuing terminal and issues a result which is not generated, and recording the first event to a block chain;
receiving and executing a plurality of second transactions for issuing the to-be-audited result of the first event, which are sent by a plurality of data issuing terminals, recording the plurality of to-be-audited results to a block chain for the auditing terminals to acquire and audit, and generating a third transaction for issuing the result of the first event when the audit is passed;
and receiving and executing a third transaction, and recording the result of the first event to the blockchain.
In a second aspect, the present invention provides a data publishing method, including:
sending a second transaction for issuing a to-be-audited result of a first event to a first contract to trigger the first contract to execute the second transaction, recording the to-be-audited result to a block chain, so that an auditing terminal can acquire and audit the to-be-audited result recorded on the block chain, generating a third transaction for issuing the result of the first event when the auditing terminal passes, triggering the first contract to execute the third transaction, and recording the result of the first event to the block chain;
the first event is sent to the first contract by the first data issuing terminal to issue a first transaction of the first event which does not produce a result, and the first contract is triggered to execute the first transaction and then recorded on the block chain.
In a third aspect, the present invention provides a data publishing method, including:
obtaining a to-be-audited result of a first event recorded on a block chain to generate or obtain an audit result:
if the audit is passed, sending a third transaction for issuing the result of the first event to the first contract to trigger the first contract to execute the third transaction, and recording the result of the first event to the block chain;
the first event is sent to the first contract by the first data issuing terminal to issue a first transaction of the first event without a result, the first contract is triggered to execute the first transaction and then recorded on the block chain, the to-be-audited result is sent to the first contract by the plurality of data issuing terminals to issue a plurality of second transactions of the to-be-audited result of the first event, and the first contract is triggered to execute the plurality of second transactions and then recorded on the block chain.
In a fourth aspect, the present invention provides a data calling method, including:
receiving a sixth transaction which is sent by the first data calling terminal and used for issuing the first contract event, executing the sixth transaction, and recording the first contract event to the block chain; wherein the result of the first contract event is generated based on the result of the first event issued by the data issuing method; performing a sixth transaction includes: verifying whether the result of the first event is to be issued: if not, the sixth transaction fails to be executed;
and receiving a seventh transaction which is generated and sent by the first data calling terminal after monitoring the result of the first event issued on the block chain, generating a first result according to the result of the first event called from the first contract and the rule of the first contract event, and recording the first result on the block chain.
In a fifth aspect, the present invention provides a data calling method, including:
sending a sixth transaction issued based on the first contract event to the second contract to trigger the second contract to execute the sixth transaction, and recording the first contract event to the blockchain; wherein the result of the first contract event is generated based on the result of the first event issued by the data issuing method; performing a sixth transaction includes: verifying whether the result of the first event is to be issued: if not, the sixth transaction fails to be executed;
after monitoring the result of issuing the first event on the blockchain, generating a seventh transaction for issuing the result of the first contract event and sending the seventh transaction to the second contract so as to trigger the second contract to generate a first result according to the result of calling the first event from the first contract and the rule of the first contract event, and recording the first result on the blockchain.
In a sixth aspect, the present invention also provides an apparatus comprising one or more processors and a memory, wherein the memory contains instructions executable by the one or more processors to cause the one or more processors to perform the data issuing method and the data calling method provided according to embodiments of the present invention.
In a seventh aspect, the present invention further provides a storage medium storing a computer program, where the computer program makes a computer execute the data publishing method and the data calling method provided in accordance with the embodiments of the present invention.
According to the data release method, the data call method, the device and the storage medium provided by the embodiments of the invention, a first transaction for releasing a first event which does not generate a result and is sent by a first data release terminal is received and executed, and the first event is recorded on a block chain; receiving and executing a plurality of second transactions for issuing the to-be-audited result of the first event, which are sent by a plurality of data issuing terminals, recording the plurality of to-be-audited results to a block chain for the auditing terminals to acquire and audit, and generating a third transaction for issuing the result of the first event when the audit is passed; and receiving and executing a third transaction, recording the result of the first event to the block chain, and really and accurately inputting data outside the chain into the chain.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
fig. 1 is a flowchart of a data publishing method according to an embodiment of the present invention.
Fig. 2 is a flowchart of step S12 in a preferred embodiment of the method shown in fig. 1.
FIG. 3 is a flow diagram of a preferred embodiment of the method shown in FIG. 1.
FIG. 4 is a flow diagram of a preferred embodiment of the method shown in FIG. 1.
FIG. 5 is a flow chart of a preferred embodiment of the method shown in FIG. 4.
FIG. 6 is a flow chart of a preferred embodiment of the method shown in FIG. 5.
Fig. 7 is a flowchart of step S12 in a preferred embodiment of the method shown in fig. 1.
Fig. 8 is a flowchart of step S15 in a preferred embodiment of the method of fig. 1.
Fig. 9 is a flowchart of step S18 in a preferred embodiment of the method shown in fig. 1.
Fig. 10 is a flowchart of a data distribution method according to an embodiment of the present invention.
Fig. 11 is a flowchart of a data distribution method according to an embodiment of the present invention.
Fig. 12 is a flowchart of a data calling method according to an embodiment of the present invention.
Fig. 13 is a flowchart of a data calling method according to an embodiment of the present invention.
Fig. 14 is a schematic structural diagram of an apparatus according to an embodiment of the present invention.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Fig. 1 is a flowchart of a data publishing method according to an embodiment of the present invention. As shown in fig. 1, in this embodiment, the present invention provides a data publishing method, including:
s12: receiving and executing a first transaction of a first event which is sent by a first data issuing terminal and issues a result which is not generated, and recording the first event to a block chain;
s15: receiving and executing a plurality of second transactions for issuing the to-be-audited result of the first event, which are sent by a plurality of data issuing terminals, recording the plurality of to-be-audited results to a block chain for the auditing terminals to acquire and audit, and generating a third transaction for issuing the result of the first event when the audit is passed;
s18: and receiving and executing a third transaction, and recording the result of the first event to the blockchain.
Specifically, the block height of the current block chain is taken as 100, only one data issuing terminal in the block chain is taken as a data issuing party A, and one auditing terminal is taken as an auditing party M; the first event without a result is that a hash value hash (200) of a block with a height of 200 needs to be obtained, the hash value of the block with the height of 200 is a hash (200) ' as a result to be audited of the first event, and the result of the first event is that the audit is passed (that is, the audit hash (200) is consistent with the hash (200) '), for example, where the hash values of all blocks with the height of 200 described in the specification are hash values of blocks with the height of 200 on the second block chain, and include the hash (200) and the hash (200) ', and the second block chain and the current block chain are two different block chains;
in step S12, the predicting machine contract receives and executes a first transaction sent by the data publisher a for publishing the hash (200) of the chunk with the height of 200, and records the hash (200) of the chunk with the height of 200 onto the chunk chain;
in step S15, the predicting machine contract receives and executes a second transaction that the block hash value of the block with the publication height of 200 sent by the data publisher a is hash (200) ', records the block hash value of the block with the height of 200 as hash (200)' on the block chain for the auditor M to obtain and audit, and generates a third transaction that the publication audit is passed when the audit is passed;
in step S18, the predictive engine contract receives and executes a third transaction, recording an audit pass to the blockchain.
The foregoing embodiment describes the data issuing method in detail by taking the block height of the current block chain as 100, only one data issuing terminal in the block chain as a data issuing party a, one auditing terminal as an auditing party M, the first event that does not produce a result is to acquire the hash value of the block with the height of 200 (hash value of 200) for the block with the height of 200 as the result to be audited of the first event, and the result of the first event is that the audit is passed (i.e., the audit hash (200) is consistent with the hash (200)'), in further embodiments, the data issuing method provided by the present invention is not limited to the above examples, and the number of the data issuing terminals may be configured as any positive integer according to actual requirements, and the number of the auditing terminals may be configured as any positive integer, which will be described in further detail with reference to the drawings and embodiments. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Configuring the result of the first event as a specific value of the result, for example as a hash (200) in the above embodiment, may achieve the same technical effect. The above embodiment truly and accurately inputs data outside the chain into the chain.
Fig. 2 is a flowchart of step S12 in a preferred embodiment of the method shown in fig. 1. As shown in fig. 2, in a preferred embodiment, step S12 includes:
s122: receiving a first transaction;
s124: and allocating a first event ID for the first event, and recording the first event and the first event ID to the blockchain.
Specifically, in step S122, the prediction engine contract receives a first transaction sent by the data publisher a, where the first transaction is issued to require obtaining a block hash value hash (200) of a block with a height of 200; in step S124, the prediction engine contract assigns a first event ID to the first event, where the ID is 0123, and records hash values hash (200) and 0123 of the blocks with height of 200 to be obtained on the block chain.
In further embodiments, since the first event ID is used to identify the first event, other forms of first event IDs, such as 0x0123, may be allocated to the first event according to actual requirements, and the same technical effect may be achieved.
The above embodiment assigns the first event ID to the first event, and a user needing to acquire data of the first event can query all states of the first event on the blockchain through the first event ID, so as to provide a good user experience for the user.
FIG. 3 is a flow diagram of a preferred embodiment of the method shown in FIG. 1. As shown in fig. 3, in a preferred embodiment, the method further includes:
s14: receiving and executing a fourth transaction, marking the first event as revoked on the blockchain; and generating and sending the fourth transaction by the first data issuing terminal when the first event needs to be cancelled.
Specifically, a first event which does not generate a result is taken as a block hash value hash (200) for acquiring a block with the height of 200; when the data publisher a knows that the second blockchain is obsolete and the block with the height of 200 is not generated, the data publisher a generates a fourth transaction which marks the first event as cancelled and sends the fourth transaction to the president contract.
When the data publisher A knows that the second block chain is disused and a block with the height of 200 cannot be generated, generating a fourth transaction which marks the first event as cancelled and sending the fourth transaction to a president contract;
in step S14, the predictive engine contract receives and executes a fourth transaction, marking the first event as revoked on the blockchain.
In further embodiments, the first data distribution terminal may further generate and send a fourth transaction when the first event needs to be cancelled according to actual needs.
FIG. 4 is a flow diagram of a preferred embodiment of the method shown in FIG. 1. As shown in fig. 4, in a preferred embodiment, the method further includes:
s17: receiving and executing a fifth transaction, marking the first event as revoked on the blockchain; and generating and sending the fifth transaction by the auditing terminal when the auditing is not passed.
Specifically, a first event without a result is taken as a block hash value hash (200) of a block with a height of 200, a result to be audited of the first event is taken as a block hash value hash (200) 'of the block with the height of 200, and a result of the first event is that the audit does not pass (that is, the audit hash (200) is inconsistent with the hash (200)'); and the auditor M does not generate a fifth transaction which marks the first event as cancelled according to the audit result, and sends the fifth transaction to the prompter contract as an example.
In step S17, the predictive engine contract receives and executes a fifth transaction, marking the first event as cancelled on the blockchain.
FIG. 5 is a flow chart of a preferred embodiment of the method shown in FIG. 4. In a preferred embodiment, as shown in fig. 5, a fifth transaction is received and executed, and after the first event is marked as cancelled on the blockchain, the method further comprises:
s172: deducting the deposit which is deposited by the account which issues the result to be verified that the verification fails.
Specifically, in step S172, the book machine contract deducts the deposit against the account of the data publisher a.
In more embodiments, a penalty policy of a deposit against an account from which an audit result to be audited is deducted may be configured as another penalty policy to restrict a data issuer from issuing a correct audit result, so that the same technical effect may be achieved.
FIG. 6 is a flow chart of a preferred embodiment of the method shown in FIG. 5. As shown in fig. 6, in a preferred embodiment, after deducting a deposit against an account issuing a result to be audited that has failed the audit, the method further includes:
s1722: adding one to the first amount of dishonest behaviour of the account to update the first amount;
s1724: determining whether the first total amount is not less than a pre-configured threshold of dishonest behavior:
if yes, canceling the authority of the account to issue the result to be checked;
wherein performing the second transaction further comprises: judging whether the sending address of the second transaction has the authority of issuing the result to be checked or not: otherwise, the second transaction execution fails.
Specifically, for example, the first total amount of the dishonest behavior of the account of the data publisher a is 2, the threshold value of the preconfigured dishonest behavior is 3, and the sending address of the second transaction (i.e., the address of the data publisher a) has a right to publish the result to be audited.
In step S1722, the predicting machine contract adds one to the first total amount of the dishonest behavior of the account to update the first total amount, where the first total amount of the dishonest behavior of the account of the data publisher a is 2 and adds one to update the first total amount, and the updated first total amount is 3;
in step S1724, the prolog contract determines whether the first total amount is not less than the threshold value of the preconfigured dishonest behavior, since the first total amount is 3, the threshold value of the preconfigured dishonest behavior is 3, and the first total amount is not less than the threshold value of the preconfigured dishonest behavior: canceling the authority of the account of the data publisher A to publish the result to be audited;
wherein performing the second transaction further comprises: judging whether the sending address of the second transaction has the authority of issuing the result to be checked or not: otherwise, the second transaction execution fails.
In further embodiments, the method of counting the first total amount of dishonest behavior may be configured as another strategy, for example, multiplying the first total amount of dishonest behavior by two to update the first total amount; the pre-configured threshold for dishonest behavior may be configured to any value greater than 0; the authorization for issuing the result to be audited may be cancelled by the account of the data issuer a, and then other policies may be added, for example, an overtime duration is added, and after the overtime duration, the authorization for issuing the result to be audited is allocated to the account of the data issuer a again, or after a plurality of mortgages of the data issuer a are received, the authorization for issuing the result to be audited is allocated to the account of the data issuer a again, so that the same technical effect may be achieved.
Fig. 7 is a flowchart of step S12 in a preferred embodiment of the method shown in fig. 1. As shown in fig. 7, in a preferred embodiment, receiving and executing a first transaction for issuing a first event that does not produce a result, where the first transaction is sent by a first data issuing terminal, and the recording the first event onto the blockchain includes:
s122: receiving a first transaction;
s123: judging whether the sending address of the first transaction has the authority of issuing the first event without the result: otherwise, the first transaction execution fails.
Specifically, take an example that the prediction engine contract receives a first transaction generated and sent by the data publisher B, and the data publisher B does not have the right to publish the first event;
in step S122, the predictive engine contract receives a first transaction;
in step S123, the prediction engine contract determines that the data issuer B does not have the authority to issue the first transaction, and the first transaction execution fails.
The embodiment further performs authority judgment on the sending address of the first transaction, so that only the first transaction sent by the address with the authority of issuing the first event can be executed, and the authenticity of data is further ensured.
Fig. 8 is a flowchart of step S15 in a preferred embodiment of the method of fig. 1. As shown in fig. 8, in a preferred embodiment, receiving and executing a plurality of second transactions which are sent by a plurality of data distribution terminals and distribute to-be-audited results of a first event, and recording the to-be-audited results to a block chain includes:
s152: receiving a second transaction;
s153: judging whether the sending address of the second transaction has the authority of issuing the result to be checked or not:
otherwise, the second transaction execution fails.
Specifically, for example, the prediction engine contract receives a second transaction generated and sent by the data publisher C, and the data publisher C does not have the right to publish the result to be audited;
in step S152, the predictive engine contract receives a second transaction;
in step S153, the prediction engine contract determines that the data issuer C does not have the right to issue the result to be checked, and the second transaction execution fails.
The embodiment further performs permission judgment on the sending address of the second transaction, so that only the second transaction sent by the address with the permission of issuing the result to be audited can be executed, and authenticity of data is further ensured.
Fig. 9 is a flowchart of step S18 in a preferred embodiment of the method shown in fig. 1. As shown in fig. 9, in a preferred embodiment, receiving and executing the third transaction, recording the result of the first event onto the blockchain comprises:
s182: receiving a third transaction;
s183: judging whether the sending address of the third transaction has the authority of issuing the result:
otherwise, the third transaction execution fails.
Specifically, take an example that the forecast contract receives the third transaction generated and sent by the data publisher D, and the data publisher D does not have the right to publish the result;
in step S182, the predictive engine contract receives a third transaction;
in step S183, the predictive engine contract determines that the data distributor D does not have the authority to distribute the above result, and the third transaction execution fails.
The embodiment further performs authority judgment on the sending address of the third transaction, so that only the third transaction sent by the address with the authority of issuing the result can be executed, and the authenticity of data is further ensured.
Fig. 10 is a flowchart of a data distribution method according to an embodiment of the present invention. As shown in fig. 10, in this embodiment, the present invention provides a data publishing method, including:
s22: sending a second transaction for issuing a to-be-audited result of a first event to a first contract to trigger the first contract to execute the second transaction, recording the to-be-audited result to a block chain, so that an auditing terminal can acquire and audit the to-be-audited result recorded on the block chain, generating a third transaction for issuing the result of the first event when the auditing terminal passes, triggering the first contract to execute the third transaction, and recording the result of the first event to the block chain;
the first event is sent to the first contract by the first data issuing terminal to issue a first transaction of the first event which does not produce a result, and the first contract is triggered to execute the first transaction and then recorded on the block chain.
Specifically, the block height of a current block chain is 100, a first contract is a prediction machine contract, only one data issuing terminal in the block chain is a data issuing party A, and one auditing terminal is an auditing party M; the first event is sent to the language predictive machine contract by the data issuing party A to issue a first transaction of the first event which does not produce a result, and the language predictive machine contract is triggered to execute the first transaction and then recorded on the block chain; the first event without the result is the block hash value hash (200) of the block with the height of 200, the block hash value of the block with the height of 200 is the hash (200) 'of the first event to be audited, and the result of the first event is audit pass (i.e. the audit hash (200) is consistent with the hash (200)');
in step S22, the data publisher a sends, to the preplanning machine contract, a second transaction in which the block hash value of the block with the publication height of 200 is hash (200) 'to trigger the preplanning machine contract to execute the second transaction, records, to the block chain, the block hash value of the block with the height of 200 is hash (200)' to allow the auditor M to obtain and audit the to-be-audited result recorded on the block chain, and generates, when the audit is passed, a third transaction in which the audit is passed to issue, to trigger the first contract to execute the third transaction, and records the audit pass to the block chain;
in the embodiment, the block height of the current block chain is 100, the first contract is a prediction machine contract, only one data issuing terminal in the block chain is a data issuing party a, and one auditing terminal is an auditing party M; the first event is sent to the pre-language engine contract by the data issuing party A to issue a first transaction of the first event which does not produce a result, and the first transaction is triggered to be executed by the first contract and then recorded on the block chain; the data issuing method provided by the present invention is described in detail in the following embodiment, where the first event that does not generate a result is a block hash value hash (200) of a block with a height of 200 that needs to be obtained, the result to be audited of the first event is that the block hash value of the block with the height of 200 is hash (200) ', and the result of the first event is that the audit passes (that is, the audit hash (200) is consistent with the hash (200)'), in further embodiments, the data issuing method provided by the present invention is not limited to the above example, the number of the audit terminals may be configured as any positive integer according to the actual requirement, and the result of the first event is configured as a specific numerical value of the result, for example, the result is configured as the hash (200) in the above embodiment, and the same technical effect can be achieved. The above embodiment truly and accurately inputs data outside the chain into the chain.
In a preferred embodiment, sending a second transaction issuing a result to be audited of the first event to the first contract to trigger the first contract to execute the second transaction, and before recording the result to be audited on the blockchain, the method further includes:
and sending a first transaction issuing a first event which does not produce a result to the first contract to trigger the first contract to execute the first transaction, and recording the first event to the blockchain.
Specifically, for example, a data publisher a and a data publisher E are provided in the block chain, the data publisher a has a right to publish the result to be audited, but does not have a right to publish the first event, and the data publisher E has a right to publish the first event.
The data issuing method includes the following steps that a data issuing party A sends a second transaction for issuing a block hash value of a block with the height of 200 as a hash (200) 'to a prediction machine contract to trigger the prediction machine contract to execute the second transaction, and before recording the block hash value of the block with the height of 200 as the hash (200)' on a block chain, the data issuing method further includes:
and the data issuing party E sends and issues a first transaction for acquiring the block hash value hash (200) of the block with the height of 200 to the prediction machine contract so as to trigger the prediction machine contract to execute the first transaction, and records the block hash value hash (200) of the block with the height of 200 to the block chain.
In a preferred embodiment, the method further comprises:
sending a fourth transaction to the first contract to trigger the first contract to execute the fourth transaction, marking the first event as revoked on the blockchain; wherein the fourth transaction is generated when the first event needs to be undone.
Specifically, a first event which does not generate a result is taken as a block hash value hash (200) for acquiring a block with the height of 200; when the data publisher a knows that the second blockchain is obsolete and the block with the height of 200 is not generated, the data publisher a generates a fourth transaction which marks the first event as cancelled and sends the fourth transaction to the president contract.
And the data publisher A sends the fourth transaction to the language predictive contract to trigger the language predictive contract to execute the fourth transaction, and marks the first event as revoked on the block chain.
In further embodiments, the first data distribution terminal may further generate and send a fourth transaction when the first event needs to be cancelled according to actual needs.
Fig. 11 is a flowchart of a data distribution method according to an embodiment of the present invention. As shown in fig. 11, in this embodiment, the present invention provides a data distribution method, including:
s32: obtaining a to-be-audited result of a first event recorded on a block chain to generate or obtain an audit result:
if the audit is passed, sending a third transaction for issuing the result of the first event to the first contract to trigger the first contract to execute the third transaction, and recording the result of the first event to the block chain;
the first event is sent to the first contract by the first data issuing terminal to issue a first transaction of the first event without a result, the first contract is triggered to execute the first transaction and then recorded on the block chain, the to-be-audited result is sent to the first contract by the plurality of data issuing terminals to issue a plurality of second transactions of the to-be-audited result of the first event, and the first contract is triggered to execute the plurality of second transactions and then recorded on the block chain.
Specifically, the block height of a current block chain is 100, a first contract is a prediction machine contract, only one data issuing terminal in the block chain is a data issuing party A, and one auditing terminal is an auditing party M; the first event is sent to the language predictive machine contract by the data issuing party A to issue a first transaction of the first event which does not produce a result, and the language predictive machine contract is triggered to execute the first transaction and then recorded on the block chain; sending a second transaction of the to-be-audited result of the first event to the pre-talker contract by the data publisher A, triggering the pre-talker contract to execute the second transaction, and recording the second transaction to the block chain; the first event without the result is the block hash value hash (200) of the block with the height of 200, the block hash value of the block with the height of 200 is the hash (200) 'of the first event to be audited, and the result of the first event is audit pass (i.e. the audit hash (200) is consistent with the hash (200)');
in step S32, the auditor M obtains the hash value of the block with height 200 recorded on the block chain as hash (200)' to generate or obtain the audit result:
and if the audit is passed, sending a third transaction for issuing the audit to the language predictive contract to trigger the language predictive contract to execute the third transaction, and recording the audit passed to the block chain.
In the embodiment, the block height of the current block chain is 100, the first contract is a prediction machine contract, only one data issuing terminal in the block chain is a data issuing party a, and one auditing terminal is an auditing party M; the first event is sent to the language predictive machine contract by the data issuing party A to issue a first transaction of the first event which does not produce a result, and the language predictive machine contract is triggered to execute the first transaction and then recorded on the block chain; sending a second transaction of the to-be-audited result of the first event to the pre-talker contract by the data publisher A, triggering the pre-talker contract to execute the second transaction, and recording the second transaction to the block chain; the data issuing method provided by the invention is explained in detail by taking as an example that the hash value of the block with the height of 200 needs to be obtained as the first event without generating a result, the hash value of the block with the height of 200 is hash (200) 'as the result to be audited of the first event, and the result of the first event is that the audit passes (that is, the audit hash (200) is consistent with the hash (200)'), in further embodiments, the data issuing method provided by the invention is not limited to the above example, the number of the data issuing terminals can be configured as any positive integer according to the actual requirement, and the result of the first event is configured as a specific numerical value of the result, for example, the hash (200) is configured in the above embodiment, and the same technical effect can be achieved. The above embodiment truly and accurately inputs data outside the chain into the chain.
In a preferred embodiment, the method further comprises: sending a fifth transaction to the first contract to trigger the first contract to execute the fifth transaction, marking the first event as revoked on the blockchain; wherein the fifth transaction is generated when the audit is not passed.
Specifically, a first event without a result is taken as a block hash value hash (200) of a block with a height of 200, a result to be audited of the first event is taken as a block hash value hash (200) 'of the block with the height of 200, and a result of the first event is that the audit does not pass (that is, the audit hash (200) is inconsistent with the hash (200)'); and the auditor M does not generate a fifth transaction which marks the first event as cancelled according to the audit result, and sends the fifth transaction to the prompter contract as an example.
And the auditor M sends a fifth transaction to the language predictive contract to trigger the language predictive contract to execute the fifth transaction, and the first event is marked as being cancelled on the block chain.
Fig. 12 is a flowchart of a data calling method according to an embodiment of the present invention. As shown in fig. 12, in this embodiment, the present invention provides a data calling method, including:
s42: receiving a sixth transaction which is sent by the first data calling terminal and used for issuing the first contract event, executing the sixth transaction, and recording the first contract event to the block chain; wherein the result of the first contract event is generated based on the result of the first event issued by the data issuing method; performing a sixth transaction includes: verifying whether the result of the first event is to be issued: if not, the sixth transaction fails to be executed;
s45: and receiving a seventh transaction which is generated and sent by the first data calling terminal after monitoring the result of the first event issued on the block chain, generating a first result according to the result of the first event called from the first contract and the rule of the first contract event, and recording the first result on the block chain.
Specifically, a data calling terminal in a block chain is taken as a data calling party O, and the result of the first contract event is generated based on the result of the first event issued by the data issuing method; the first contract event is a random number for dealing the current round of games, wherein the result of the first event (the block hash value of a block with the height of 200 is hash (200)) is called, and the first result is a dealing sequence generated according to the random number and the rule of the first contract event; performing a sixth transaction includes: verifying whether the result of the first event is to be issued: is to be issued as an example;
in step S42, the game contract receives a sixth transaction sent by the data caller O, in which the result of calling the first event is the random number of the current round of game dealing, executes the sixth transaction, and records the random number of the current round of game dealing, in which the result of calling the first event is the random number of the current round of game dealing, onto the blockchain;
in step S45: and the game contract receives a seventh transaction generated and sent by the data caller O after monitoring that the result of the first event issued on the block chain (the result is passed, namely the hash (200) 'is consistent with the hash (200) and is the correct block hash value of the block with the height of 200), generates a dealing sequence according to the hash (200)' called from the language predictive machine contract and the rule of the first contract event, and records the dealing sequence on the block chain.
In the embodiment, the data calling terminal in the block chain is used as the data calling party O, and the result of the first contract event is generated based on the result of the first event issued by the data issuing method; the first contract event is a random number for dealing the current round of games, and the result of calling the first event (the block hash value of the block with the height of 200 hash (200)) is a dealing sequence generated according to the random number and the rule of the first contract event. The embodiment calls the data outside the chain truly and accurately, and realizes the perception and the requirement of different contracts on the data outside the chain.
In a preferred embodiment, the method further comprises:
receiving and executing an eighth transaction, marking the first contract event as revoked on the blockchain; wherein the eighth transaction is generated and sent by the first invoking terminal when the first contract event needs to be revoked.
Specifically, a first contract event is used as a result of calling the first event (a block hash value hash (200) of a block with the height of 200) as a random number of the card dealing of the current round of game, and when a data caller O acquires that the first event is marked as cancelled on a block chain, an eighth transaction for marking the first contract event as cancelled is generated and sent to a game contract example;
the game contract receives and executes an eighth transaction, marking the first contract event as revoked on the blockchain.
The above-described embodiments illustrate the revocation of a first contract event by way of example of the generation of an eighth transaction that marks the first contract event as revoked, the circumstances of which include, but are not limited to: when the data publisher A knows that the block chain is about to stop running and a block with the height of 200 cannot be generated, a fourth transaction marking a first event as cancelled is generated and sent to a language-predictive contract, the language-predictive contract receives and executes the fourth transaction, the first event is marked as cancelled on the block chain, when the data caller O acquires the first event as cancelled on the block chain, an eighth transaction marking the first contract event as cancelled is generated and sent to a game contract, and when the auditing result is that the fifth transaction marking the first event as cancelled is not generated and sent to the language-predictive contract, the language-predictive contract receives and executes the fifth transaction, the first event is marked as cancelled on the block chain, and when the data caller O acquires the first event as cancelled on the block chain, the eighth transaction marking the first event as cancelled is generated by the data caller, and sent to the game contract.
In a preferred embodiment, receiving a sixth transaction issued a first contract event sent by a first data call terminal, executing the sixth transaction, and recording the first contract event onto the blockchain includes:
receiving a sixth transaction;
determining whether the sending address of the sixth transaction has the right to issue the first contract event:
otherwise, the sixth transaction execution fails.
Specifically, take as an example that the game contract receives the sixth transaction generated and sent by the data caller P, and the data caller P does not have the right to issue the first contract event;
the game contract receiving a sixth transaction;
the game contract judgment data caller P does not have the authority to issue the first contract event, and the sixth transaction execution fails.
The above embodiment further performs authority determination on the sending address of the sixth transaction, so that only the sixth transaction sent by the address having the authority to issue the first contract event can be executed, and the correctness of data calling is further ensured.
In a preferred embodiment, receiving a seventh transaction generated and sent by the first data invoking terminal after monitoring that the result of the first event is issued on the blockchain, generating a first result according to the result of invoking the first event from the first contract and the rule of the first contract event, and recording the first result on the blockchain includes:
receiving a seventh transaction;
judging that the data caller Q does not have the authority of issuing the first contract event:
otherwise, the seventh transaction execution fails.
Specifically, take as an example that the game contract receives the seventh transaction generated and sent by the data caller Q, and the data caller Q does not have the right to issue the first contract event;
the game contract receiving a seventh transaction;
the game contract judges that the sending address of the seventh transaction does not have the authority of issuing the first contract event, and the execution of the seventh transaction fails.
Fig. 13 is a flowchart of a data calling method according to an embodiment of the present invention. As shown in fig. 13, in this embodiment, the present invention provides a data calling method, including:
s52: sending a sixth transaction issued based on the first contract event to the second contract to trigger the second contract to execute the sixth transaction, and recording the first contract event to the blockchain; wherein the result of the first contract event is generated based on the result of the first event issued by the data issuing method; performing a sixth transaction includes: verifying whether the result of the first event is to be issued: if not, the sixth transaction fails to be executed;
s55: after monitoring the result of issuing the first event on the blockchain, generating a seventh transaction for issuing the result of the first contract event and sending the seventh transaction to the second contract so as to trigger the second contract to generate a first result according to the result of calling the first event from the first contract and the rule of the first contract event, and recording the first result on the blockchain.
Specifically, a data calling terminal in the block chain is taken as a data calling party O, the second contract is a game contract, and the result of the first contract event is generated based on the result of the first event issued by the data issuing method; the first contract event is a random number for dealing the current round of games, wherein the result of the first event (the block hash value of a block with the height of 200 is hash (200)) is called, and the first result is a dealing sequence generated according to the random number and the rule of the first contract event; performing a sixth transaction includes: verifying whether the result of the first event is to be issued: is to be issued as an example;
in step S52, the data invoker O sends a sixth transaction calling the result of the first event as the random number of the current round of game dealing to the game contract to trigger the game contract to execute the sixth transaction, and records the random number calling the result of the first event as the random number of the current round of game dealing onto the blockchain;
in step S55, after monitoring the result of the first event issued on the blockchain, the data caller O generates a seventh deal issuing the result of the first contract event and sends the seventh deal to the game contract, so as to trigger the game contract to generate a dealing sequence according to the hash (200)' invoked from the game player contract and the rule of the first contract event, and record the dealing sequence on the blockchain.
In the embodiment, the data calling terminal in the block chain is used as the data calling party O, the second contract is a game contract, and the result of the first contract event is generated based on the result of the first event issued by the data issuing method; the first contract event is a random number for dealing the current round of games, and the result of calling the first event (the block hash value of the block with the height of 200 hash (200)) is a dealing sequence generated according to the random number and the rule of the first contract event. The embodiment calls the data outside the chain truly and accurately, and realizes the perception and the requirement of different contracts on the data outside the chain.
In a preferred embodiment, the method further comprises:
sending an eighth transaction to the second contract to trigger the second contract to execute the eighth transaction, marking the first contract event as revoked on the blockchain; wherein the eighth transaction is generated when the first contract event needs to be undone.
Specifically, a first contract event is used as a result of calling the first event (a block hash value hash (200) of a block with the height of 200) as a random number of the card dealing of the current round of game, and when a data caller O acquires that the first event is marked as cancelled on a block chain, an eighth transaction for marking the first contract event as cancelled is generated and sent to a game contract example;
the data invoker O sends an eighth transaction to the game contract to trigger the game contract to execute the eighth transaction, marking the first contract event as revoked on the blockchain.
Cases of revoking a first contract event include, but are not limited to: when the data publisher A knows that the block chain is about to stop running and a block with the height of 200 cannot be generated, a fourth transaction marking a first event as cancelled is generated and sent to a language-predictive contract, the language-predictive contract receives and executes the fourth transaction, the first event is marked as cancelled on the block chain, when the data caller O acquires the first event as cancelled on the block chain, an eighth transaction marking the first contract event as cancelled is generated and sent to a game contract, and when the auditing result is that the fifth transaction marking the first event as cancelled is not generated and sent to the language-predictive contract, the language-predictive contract receives and executes the fifth transaction, the first event is marked as cancelled on the block chain, and when the data caller O acquires the first event as cancelled on the block chain, the eighth transaction marking the first event as cancelled is generated by the data caller, and sent to the game contract.
Fig. 14 is a schematic structural diagram of an apparatus according to an embodiment of the present invention.
As shown in fig. 14, as another aspect, the present application also provides a device 1400 including one or more Central Processing Units (CPUs) 1401 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1402 or a program loaded from a storage portion 1408 into a Random Access Memory (RAM) 1403. In the RAM1403, various programs and data necessary for the operation of the device 1400 are also stored. The CPU1401, ROM1402, and RAM1403 are connected to each other via a bus 1404. An input/output (I/O) interface 1405 is also connected to bus 1404.
The following components are connected to the I/O interface 1405: an input portion 1406 including a keyboard, a mouse, and the like; an output portion 1407 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker and the like; a storage portion 1408 including a hard disk and the like; and a communication portion 1409 including a network interface card such as a LAN card, a modem, or the like. The communication section 1409 performs communication processing via a network such as the internet. The driver 1410 is also connected to the I/O interface 1405 as necessary. A removable medium 1411 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1410 as necessary, so that a computer program read out therefrom is installed into the storage section 1408 as necessary.
In particular, according to an embodiment of the present disclosure, the data publishing method and the data calling method described in any of the above embodiments may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for performing a data publishing method and a data calling method. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 1409 and/or installed from the removable medium 1411.
As yet another aspect, the present application also provides a computer-readable storage medium, which may be the computer-readable storage medium included in the apparatus of the above-described embodiment; or it may be a separate computer readable storage medium not incorporated into the device. The computer-readable storage medium stores one or more programs, which are used by one or more processors to execute the data distribution method and the data calling method described in the present application.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules described in the embodiments of the present application may be implemented by software or hardware. The described units or modules may also be provided in a processor, for example, each of the described units may be a software program provided in a computer or a mobile intelligent device, or may be a separately configured hardware device. Wherein the designation of a unit or module does not in some way constitute a limitation of the unit or module itself.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the present application. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (22)
1. A method for data distribution, comprising:
receiving and executing a first transaction sent by a first data issuing terminal; the first transaction comprises a first event which is issued by the first data issuing terminal and does not generate a result, wherein the first event which does not generate a result is the acquisition of block data of a block after the current block height;
recording the first event onto a blockchain;
receiving and executing second transactions sent by a plurality of data issuing terminals; the second transaction comprises a to-be-audited result of the first event issued by a plurality of data issuing terminals;
recording a plurality of results to be audited on the block chain for the auditing terminal to obtain and audit, and generating a third transaction when the audit is passed; wherein the third transaction comprises a result of the first event issued by the audit terminal;
and receiving and executing the third transaction, and recording the result of the first event to the block chain.
2. The method of claim 1, wherein the recording the first event onto a blockchain comprises:
and allocating a first event ID to the first event, and recording the first event and the first event ID to a block chain.
3. The method of claim 1, further comprising:
receiving and executing a fourth transaction, marking the first event as revoked on the blockchain; wherein the fourth transaction is generated and sent by the first data distribution terminal when the first event needs to be cancelled.
4. The method of claim 1, further comprising:
receiving and executing a fifth transaction, marking the first event as revoked on the blockchain; and the fifth transaction is generated and sent by the auditing terminal when the auditing is not passed.
5. The method of claim 4, wherein receiving and executing a fifth transaction, after marking the first event as cancelled on the blockchain, further comprises:
deducting the deposit which is deposited by the account which issues the result to be verified that the verification fails.
6. The method of claim 5, wherein deducting a deposit against an account issuing a result to be audited that has failed the audit further comprises:
adding one to the first amount of dishonest behavior of the account to update the first total amount;
determining whether the first total amount is not less than a pre-configured threshold of dishonest behavior:
if yes, canceling the authority of the account to issue the result to be checked;
wherein performing the second transaction further comprises: judging whether the sending address of the second transaction has the authority of issuing the result to be checked or not: otherwise, the second transaction execution fails.
7. The method according to any one of claims 1-6, wherein receiving and executing the first transaction sent by the first data distribution terminal comprises:
receiving the first transaction;
judging whether the sending address of the first transaction has the authority of issuing a first event without a result:
otherwise, the first transaction fails to execute.
8. The method according to any one of claims 1-5, wherein receiving and executing the second transaction sent by the plurality of data distribution terminals comprises:
receiving the second transaction;
judging whether the sending address of the second transaction has the authority of issuing the result to be checked or not:
otherwise, the second transaction execution fails.
9. The method of any of claims 1-6, wherein receiving and executing the third transaction, logging the result of the first event onto the blockchain comprises:
receiving the third transaction;
judging whether the sending address of the third transaction has the authority of issuing the result:
otherwise, the third transaction execution fails.
10. A method for data distribution, comprising:
issuing a to-be-audited result of a first event, generating a second transaction according to the to-be-audited result, sending the second transaction to a first contract to trigger the first contract to execute the second transaction, recording the to-be-audited result to a block chain, allowing an auditing terminal to acquire and audit the to-be-audited result recorded on the block chain, issuing a result of the first event when auditing is passed, generating a third transaction according to the result of the first event, sending the third transaction to the first contract to trigger the first contract to execute the third transaction, and recording the result of the first event to the block chain;
the first event is that a first data issuing terminal sends a first transaction to the first contract, the first contract is triggered to execute the first transaction and then is recorded on the block chain, the first transaction comprises a first event which is issued by the first data issuing terminal and does not generate a result, and the first event which does not generate a result is block data of a block after the current block height is acquired.
11. The method according to claim 10, wherein before issuing the to-be-audited result of the first event, the method further comprises:
issuing a first event which does not produce a result, and generating a first transaction according to the first event;
and sending the first transaction to a first contract to trigger the first contract to execute the first transaction, and recording the first event onto a block chain.
12. The method of claim 10, further comprising:
sending a fourth transaction to the first contract to trigger the first contract to execute the fourth transaction, the first event being marked as revoked on the blockchain; wherein the fourth transaction is generated when the first event needs to be undone.
13. A method for data distribution, comprising:
obtaining a to-be-audited result of a first event recorded on a block chain to generate or obtain an audit result:
if the audit is passed, sending a third transaction for issuing the result of the first event to the first contract to trigger the first contract to execute the third transaction, and recording the result of the first event to the block chain;
the first event is a first transaction for issuing a first event without a result to the first contract, the first transaction is triggered to execute the first transaction and then recorded on the block chain, the first event without the result is block data of a block after the current block height is obtained, the result to be audited is sent to the first contract by a plurality of data issuing terminals, a plurality of second transactions for issuing the result to be audited of the first event are triggered, and the first contract is triggered to execute the second transactions and then recorded on the block chain.
14. The method of claim 13, further comprising:
sending a fifth transaction to a first contract to trigger the first contract to execute the fifth transaction, the first event being marked as revoked on the blockchain; wherein the fifth transaction is generated when the audit is not passed.
15. A data calling method, comprising:
receiving a sixth transaction which is sent by a first data calling terminal and used for issuing a first contract event, executing the sixth transaction, and recording the first contract event to a block chain; wherein the result of the first contract event is generated based on the result of the first event published by the data publication method according to any one of claims 1-14; the executing the sixth transaction comprises: verifying whether the result of the first event is to be issued: if not, the sixth transaction fails to be executed;
and receiving a seventh transaction which is generated and sent by a first data calling terminal after monitoring the result of the first event issued on the block chain, and issuing a first contract event result, generating a first result according to the result of the first event called from the first contract and the rule of the first contract event, and recording the first result on the block chain.
16. The method of claim 15, further comprising:
receiving and executing an eighth transaction, marking the first contract event as revoked on the blockchain; wherein the eighth transaction is generated and sent by the first data call terminal when the first contract event needs to be revoked.
17. The method of claim 15 or 16, wherein receiving a sixth transaction issued a first contract event sent by a first data call terminal, executing the sixth transaction, and recording the first contract event onto a blockchain comprises:
receiving the sixth transaction;
determining whether a sending address of the sixth transaction has permission to issue the first contract event:
otherwise, the sixth transaction execution fails.
18. The method according to claim 15 or 16, wherein the receiving a seventh transaction that the first data call terminal generates and sends after monitoring that the result of the first event is issued on the blockchain, and the generating a first result according to the result of the first event called from the first contract and the rule of the first contract event, and the recording the first result on the blockchain comprises:
receiving the seventh transaction;
determining whether the sending address of the seventh transaction has the right to issue the first contract event result:
otherwise, the seventh transaction execution fails.
19. A data calling method, comprising:
sending a sixth transaction issued based on a first contract event to a second contract to trigger the second contract to execute the sixth transaction, recording the first contract event onto a blockchain; wherein the result of the first contract event is generated based on the result of the first event published by the data publication method according to any one of claims 1-14; the executing the sixth transaction comprises: verifying whether the result of the first event is to be issued: if not, the sixth transaction fails to be executed;
after monitoring the result of the first event issued on the block chain, generating a seventh transaction for issuing the result of the first contract event and sending the seventh transaction to a second contract so as to trigger the second contract to generate a first result according to the result of the first event called from the first contract and the rule of the first contract event, and recording the first result on the block chain.
20. The method of claim 19, further comprising:
sending an eighth transaction to a second contract to trigger the second contract to execute the eighth transaction, the first contract event being marked as revoked on the blockchain; wherein the eighth transaction is generated when the first contract event needs to be reversed.
21. A computer device, the device comprising:
one or more processors;
a memory for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method recited in any of claims 1-20.
22. A storage medium storing a computer program, characterized in that the program, when executed by a processor, implements the method according to any one of claims 1-20.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910077671.0A CN109727040B (en) | 2019-01-28 | 2019-01-28 | Data publishing method, data calling method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910077671.0A CN109727040B (en) | 2019-01-28 | 2019-01-28 | Data publishing method, data calling method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109727040A CN109727040A (en) | 2019-05-07 |
| CN109727040B true CN109727040B (en) | 2020-09-15 |
Family
ID=66300928
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910077671.0A Active CN109727040B (en) | 2019-01-28 | 2019-01-28 | Data publishing method, data calling method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109727040B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110555319B (en) * | 2019-07-22 | 2022-12-27 | 平安科技（深圳）有限公司 | Resource expected result auditing method and device based on block chain and computer equipment |
| CN112711777A (en) * | 2020-12-29 | 2021-04-27 | 杭州趣链科技有限公司 | Chain linking method, chain linking device and node equipment |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10176481B2 (en) * | 2015-12-21 | 2019-01-08 | Beston Technologies Pty Ltd | Method and apparatus for managing and providing provenance of product using blockchain |
| US10521775B2 (en) * | 2016-04-18 | 2019-12-31 | R3 Ltd. | Secure processing of electronic transactions by a decentralized, distributed ledger system |
| CN107222482A (en) * | 2017-06-01 | 2017-09-29 | 黑龙江卓亚科技有限公司 | A kind of data management system and method based on compound block chain network |
| CN107742210A (en) * | 2017-10-13 | 2018-02-27 | 布比（北京）网络技术有限公司 | Across the chain fund transfer system and method for a kind of different blocks interchain |
| CN108492108B (en) * | 2018-03-29 | 2021-04-23 | 深圳前海微众银行股份有限公司 | Block chain cross-chain communication method, system and computer readable storage medium |
| CN110400142B (en) * | 2018-06-01 | 2021-06-25 | 腾讯科技（深圳）有限公司 | Data processing method, device and storage medium |
| CN109146448B (en) * | 2018-07-13 | 2021-02-09 | 杭州复杂美科技有限公司 | Cross-chain asset transfer method, device and storage medium |
| CN109117994B (en) * | 2018-07-27 | 2020-04-14 | 阿里巴巴集团控股有限公司 | Event prediction method and device and electronic equipment |
-
2019
- 2019-01-28 CN CN201910077671.0A patent/CN109727040B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN109727040A (en) | 2019-05-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7384965B2 (en) | Agent-based Turing-complete transactions with integrated feedback within blockchain systems | |
| CN109981679B (en) | Method and apparatus for performing transactions in a blockchain network | |
| US20220261461A1 (en) | Secure resource management to prevent fraudulent resource access | |
| CN111309745B (en) | Virtual resource processing method and device, electronic equipment and storage medium | |
| CN110275891A (en) | Artificial intelligence software market | |
| CN110138767B (en) | Transaction request processing method, device, equipment and storage medium | |
| CN109727040B (en) | Data publishing method, data calling method, device and storage medium | |
| EP4147416B1 (en) | Blockchain-based accountable distributed computing system | |
| CN110009497B (en) | Block chain-based decision method and device and electronic equipment | |
| US20060179009A1 (en) | Management of terms and conditions for an agreement | |
| CN111222885B (en) | Data processing request endorsement method and device, computer equipment and storage medium | |
| US20230368185A1 (en) | Public trust ledger smart contract token transfer in a database system | |
| CN110347657A (en) | Data creation method, device, electronic equipment and storage medium | |
| KR102304953B1 (en) | Peer node and method for processing information thereof, and blockchain platform systems | |
| CN110858211A (en) | Data storage method, device and system and storage medium | |
| Keller | ‘Design and implementation of a blockchain-based trusted VNF package repository | |
| CN110751483A (en) | Financial accounting and sales rushing method and device based on block chain and electronic equipment | |
| US20230396445A1 (en) | Multi-signature wallets in public trust ledger actions via a database system | |
| US11995202B2 (en) | Computer system and data access control method | |
| US20230367766A1 (en) | Environmental impact tracking in public trust ledger actions via a database system | |
| US20240177143A1 (en) | Intermediary roles in public trust ledger actions via a database system | |
| Nielsen | Quality and IT security assessment of open source software projects | |
| CN114297675A (en) | Processing method, device, equipment and medium for auditing request of target object | |
| Sharudin | Implementation of Open Vote Network in Blockchain Signaling System Using Decentralized Autonomous Organization Smart Contract in Ethereum Blockchain | |
| CN117474682A (en) | Data processing method, device, medium and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |