Object-level receipt storage method and node based on code annotationsCode annotation-based object-level receipt storage method and node
A receipt and node technology, applied in the blockchain field, can solve problems such as little consideration of privacy performance, high complexity, and poor versatility
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
example 1
[0045]
[0046] In the code of the smart contract based on the Solidity language, one or more objects can be identified by exposing the identifier, so that the receipt content corresponding to this part of the object in the receipt data can be stored in plain text, while the rest of the receipt content can be stored in encrypted form. stored in text form. 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.
[0047] The exposure identifier may be a receipt field dedicated to indicate that plaintext storage is required, 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 be added before the corresponding object (or it can be associated with the corresponding object in other ways).
example 2
[0049]
[0050] 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 the fields in the generated receipt data are stored in plain text.
[0051] 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, the receipt content corresponding to the From field in the generated receipt data can be stored in plain text after the code of the smart contract is executed. Retrieval operations are performed on the receipt content, for example, the transaction volume initiated by a certain account can be counted.
[0052] It should be pointed out that: in the above code example 2 and its related embodiments, the object (all fields or From field) marked by the exposed identifier "plain" is a contract-level object, so that the first blockchain node stores When...
example 3
[0054]
[0055] 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 stored in plain text, then the follow-up can be used for the state variable "price" Retrieve the contents of the receipt. Since the state variable "price" belongs to the contract-level object in Code Example 3, when the code of the smart contract contains multiple events, the contract-level object can be applied to all events in the smart contract, then when multiple events generate their own For the corresponding Logs field, each Logs field (such as the Topic field in the Logs field) will store the receipt content related to the state variable "price" in pl...
PUM
Abstract
Description
Claims
Application Information
- R&D Engineer
- R&D Manager
- IP Professional
- Industry Leading Data Capabilities
- Powerful AI technology
- Patent DNA Extraction
Browse by: Latest US Patents, China's latest patents, Technical Efficacy Thesaurus, Application Domain, Technology Topic, Popular Technical Reports.
© 2024 PatSnap. All rights reserved.Legal|Privacy policy|Modern Slavery Act Transparency Statement|Sitemap|About US| Contact US: help@patsnap.com