Receipt storage method and node in combination with code annotations and user and event typescombining code labeling with user and event types
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
[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 the user type and dimension of the event function to determine whether it is actually stored in plaintext), and 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 be added before ...
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. Specifically, when the transaction initiator belongs to the preset user type, for the log generated by the special event function in the receipt data, all receipt contents corresponding to the log 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, when the transaction initiator belongs to the preset user type, the From field is allowed to correspond to the log generated by the special event function in the receipt data. The receipt content of the account is stored in plain text, then subsequent ret...
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 , when the transaction initiator belongs to the default user type, for the logs generated by the special event function in the receipt data, the receipt content related to the state variable "price" is allowed to be stored in plain text (provided that the transaction initiator belongs to the default user type), then subsequent retrieval operations 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 smart contract is a smart contract written...
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