Receipt storage methods and nodes combining code annotation and multi-type dimensions
A multi-type, receipt technology, applied in the blockchain field, can solve the problems of poor versatility, little regard for privacy performance, and high complexity
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
example 1
[0049]
[0050]In the code based on the intelligent contract written in the Solidity language, one or more fields can be labeled by exposure identifiers such that the receipt content corresponding to this part of the field is allowed to store in a clear text (need to further combine the user type, " The dimension of the transaction type and the event function is determined whether or not the original storage is used), and the rest of the receipt should be stored in ciphertext. Similarly, in the code of the intelligent contract written based on the Serpent, LLL language, one or more fields can also be labeled by exposure identifiers to implement the clear text storage of the relevant receipt content.
[0051]The exposed identifier can be dedicated to indicate the receipt fields that allow plain text storage, such as using keyword plain to characterize the exposed identifier. Then, for the receipt content that is desirable in express form, it can be added to the corresponding field (or othe...
example 2
[0053]
[0054]In the above-described code example 2, an exposed identifier PLAIN is added at the time of the code of the intelligent contract, so that the code of the smart contract is executed, and when the transaction initiator belongs to the preset user type, the receipt data is generated by the special event function. The log allows the receipt content that allows the exposed fields corresponding to the transaction type of the intelligent contract to be stored in a clear text. For example, when the FROM field in the log belongs to the exposure field, the TO field does not belong to the exposure field, the receipt data can be recorded. The FROM field in all logs is stored in a clear text, and the To field is stored in ciphertext, then the retrieval operation can be implemented for the receipt content in the FROM field, such as the amount of transactions initiated by a certain account.
[0055]In an embodiment, the intelligent contract corresponding to the transaction received by the f...
example 3
[0103]
[0104]
[0105]In the above-described code example 3, similarly to the code example 2, the exposed identifier "Plain" is located in front of the code of the intelligent contract, so that all fields in the receipt data are labeled as the contract-level field; at the same time, intelligent contracts Contains events CURRENTPRICE1 and events CURRENTPRICE2: Assuming event currentprice1 corresponds to a special event function defined in the Special Event Function list, the event currentprice2 corresponds to the normal event function, then the transaction initiator belongs to the preset user type and the FROM field is the exposed field. Next, in the log log1, log2 generated by the event currentprice1 and event currentprice2, the FROM field contained in the log log1 is stored in a clear text, and the FROM field contained in the log log2 is stored in ciphertext; Similarly, log log1 belongs to the exposed field. Other fields are also stored in a clear text, and non-exposed fields are store...
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More 


