Receipt storage method combining code labeling, transaction and event type, and node
A receipt and transaction 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
[0049]
[0050] In the code of the smart contract written based on the Solidity language, one or more fields can be marked by exposing the identifier, so that the receipt content corresponding to this part of the field in the receipt data is allowed to be stored in plain text (need to further combine the transaction 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 fields can also be marked by exposing identifiers to realize the plain text storage of relevant receipt content.
[0051] 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 desired to be stored in plain text, plain can be added bef...
example 2
[0053]
[0054] In the above code example 2, the exposed identifier plain is added at the front of the code of the smart contract. From the dimension of programming language, the exposed identifier plain indicates: After the code of the smart contract is executed, the generated receipt data All fields in are allowed to be stored in plain text, then subsequent retrieval operations can be performed on the receipt content in these fields, for example, for the From field, it can be used to count the transaction volume initiated by an account, etc. By further combining dimensions such as transaction type and event function, there may be different storage schemes for receipt data, see below.
[0055] 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 in a high...
example 3
[0098] plain Contract Example{
[0099] int price;
[0100] int price1;
[0101] event currentPrice1(int price);
[0102] event currentPrice2(int price1);
[0103] …
[0104] In the above code example 3, similar to code example 2, the exposed identifier "plain" is placed at the forefront of the code of the smart contract, so that all fields in the receipt data are marked as contract-level fields; at the same time, in the smart contract Contains the event currentPrice1 and event currentPrice2: Assuming that the From field is the exposed field corresponding to the transaction type, and the event currentPrice1 corresponds to the special event function defined in the special event function list, and the event currentPrice2 corresponds to the normal event function, then in the event currentPrice1 and event currentPrice2 In the logs Log1 and Log2 generated respectively, the From field contained in the log Log1 is stored in plain text, and the From field contained in the log Log2 ...
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More - R&D
- Intellectual Property
- Life Sciences
- Materials
- Tech Scout
- Unparalleled Data Quality
- Higher Quality Content
- 60% Fewer Hallucinations
Browse by: Latest US Patents, China's latest patents, Technical Efficacy Thesaurus, Application Domain, Technology Topic, Popular Technical Reports.
© 2025 PatSnap. All rights reserved.Legal|Privacy policy|Modern Slavery Act Transparency Statement|Sitemap|About US| Contact US: help@patsnap.com



