Conditional receipt storage method and node combining code labeling and event types
A technology of event type and receipt, applied in the field of blockchain, can solve the problems of little consideration of privacy performance, high complexity, poor versatility, etc.
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
example 1
[0047]
[0048] In the code of the smart contract based on the Solidity language, one or more objects can be marked by exposing the identifier, so that the receipt content corresponding to this part of the object in the receipt data is allowed to be stored in plain text (need to further combine event functions and The dimensions of the preset conditions are used to determine whether to actually store in plaintext), while the rest of the receipt content should be stored in ciphertext. Similarly, in the code of smart contracts written based on Serpent, LLL language, etc., one or more objects can also be marked by exposing identifiers, so as to realize the plain text storage of relevant receipt content.
[0049] The exposure identifier may be a receipt field dedicated to indicate that plaintext storage is allowed, for example, the keyword plain may be used to represent the exposure identifier. Then, for the receipt content that is expected to be stored in plain text, plain can...
example 2
[0051]
[0052] In the above code example 2, by adding the exposure identifier plain at the front of the code of the smart contract, after the code of the smart contract is executed, all fields in the generated receipt data are allowed to be stored in plain text.
[0053] Of course, in other embodiments, the fields that need to be stored in plain text may also be specified. For example, when the From field is marked by an exposed identifier, after the code of the smart contract is executed, the receipt content corresponding to the From field in the generated receipt data can be stored in plain text (need to further combine event functions and preset The dimension of the condition is used to determine whether to use plaintext storage), then subsequent retrieval operations can be performed on the receipt content in the From field, for example, the transaction volume initiated by a certain account can be counted.
example 3
[0055]
[0056]
[0057] In the above code example 3, by adding the exposure identifier "plain" before the type int of the state variable "price" (or, the exposure identifier plain can be placed after the type int), so that after the code of the smart contract is executed , in each field of the generated receipt data (usually including Topic field, Output field, etc.), the receipt content related to the state variable "price" is allowed to be stored in plain text (need to further combine the event function and the dimension of the preset condition to It is determined whether the plaintext storage is actually used), then the subsequent retrieval operation can be performed on the receipt content related to the state variable "price".
[0058] In an embodiment, the smart contract corresponding to the transaction received by the first blockchain node may be a smart contract written in a high-level language, or may be a smart contract in bytecode form. Among them, when the sm...
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More 


