Block chain-based activity commemoration method
By establishing untampered records of event information on the blockchain and transfer rules of commemorative medals, the reliability and accessibility of event participation proof is solved, and the permanent credibility of event participants' information on the blockchain is realized. and immutability.
Patent Information
- Application Number
- CN202310743887.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-06-24
- Publication Date
- 2024-12-27
AI Technical Summary
In the prior art, electronic information records participating in activities are easily forged or tampered with, physical information carriers are inefficient in accessibility, and it is difficult to provide a permanently reliable way of proof.
Using the blockchain contract-based activity information penetration method, the on-chain data association relationship, the event participation relationship penetration process and commemorative medal transfer rules are established to ensure that the commemorative medals of event participants are tampered with and permanently on the blockchain. Trusted.
The information records of event participants cannot be changed and always be credible on the blockchain. The relevance of their participation in activities is proved through commemorative medals, and the requirements for event participation proof in different scenarios are met.
Smart Images

Figure CN119205455A_ABST
Abstract
Description
Technical Field
[0001] The invention belongs to the field of blockchain and relates to an activity commemoration method. Background Art
[0002] Blockchain is a distributed database technology that stores data on multiple computer nodes in a decentralized manner and ensures data consistency and security through a consensus algorithm. Its core is a chain structure composed of interconnected blocks, which makes data tamper-proof and transparent. It can be applied in various fields to provide a safe, efficient and reliable way of data exchange and verification.
[0003] Blockchain contract is an automated technology defined and executed in the form of programming code based on blockchain technology. It utilizes the decentralization and security characteristics of blockchain to achieve reliable, transparent and tamper-proof execution.
[0004] People often participate in various purposeful and meaningful activities at specific times and places, such as meetings, seminars, exhibitions, concerts, sports competitions, etc. However, it is currently difficult for participants to prove that they have participated in certain activities in a way that is never lost, always reliable, and efficient. Physical evidence such as paper tickets is easy to lose, and centralized storage data such as electronic tickets is prone to tampering, forgery, or inaccessibility. Summary of the invention
[0005] In order to solve the problems in the prior art that electronic information records of participating activities are easily forged, tampered with and lost, while the accessibility efficiency of physical information carriers is very low, the present invention provides a method for uploading activity information to the chain based on blockchain contract technology.
[0006] The technical solution adopted by the present invention to solve its technical problems is: a method for commemorating an activity based on blockchain, including establishing an on-chain data association relationship, establishing a set of on-chain processes for activity participation relationships, and providing a method for setting rules for transferring commemorative medals between accounts.
[0007] On the first aspect, the establishment of an on-chain data association relationship means that the platform system has a separate contract on the blockchain, and the platform system will generate an activity unique identifier, a commemorative medal unique identifier, and activity description data in the contract.
[0008] The activity unique identifier represents an activity, and each real activity has one and only one activity identifier in the contract. The activity identifier and the activity description data are in a one-to-one correspondence.
[0009] The unique badge identifier represents each badge, and different badges have completely different identifiers. A blockchain account can own a badge, and the essence of a blockchain account owning a badge is that the blockchain account has the unique badge identifier.
[0010] The activity description data preferably includes activity title, activity time, activity location and other related content describing the activity. There is a one-to-one correspondence between the activity description data and the activity identifier.
[0011] In the platform contract, each badge unique identifier must be associated with and can only be associated with one activity unique identifier at most. Conversely, an activity unique identifier can be associated with multiple badge unique identifiers. This technical model reflects that each badge must represent and can only represent one activity, while one activity can issue multiple badges.
[0012] On the second aspect, the establishment of a set of activity participation relationship chain process includes the generation of collection codes, the issuance of collection codes, and the initiation of chaining by participants.
[0013] The collection code is generated. The event organizer generates a set of non-repeating random numbers associated with the event based on the platform system. The random numbers are called collection codes. Each collection code must be associated with and can only be associated with one event at most. This situation where a collection code is associated with a unique event is called collection code-to-event mapping. Through collection code mapping, if a participant has a collection code, it means that the participant has the voucher associated with the event.
[0014] The event organizer issues the collection code to the participants of the event mapped by the collection code, which represents the event organizer's recognition of the event participants' participation in the event.
[0015] The participant initiates the on-chain. The participant provides the platform with the collection code and the blockchain account address he / she owns at the same time, triggering the platform to cast a commemorative medal associated with the activity mapped by the collection code on the blockchain, and the commemorative medal is cast in the blockchain account submitted by the participant.
[0016] Based on the fact that the medallion is minted in a blockchain account and the blockchain account is owned by the participant, the medallion proves that its owner participated in the activity associated with the medallion.
[0017] On the third aspect, the rules for transferring commemorative medals between accounts refer to the mandatory rules set in the platform contract that must be followed when transferring commemorative medals between different blockchain accounts.
[0018] Preferably, the transfer rules of commemorative medals between different blockchain accounts include setting an upper limit on the number of transfers allowed, setting a deadline for transfers allowed, and setting a frequency for transfers allowed.
[0019] Preferably, the upper limit of the number of transfers allowed includes prohibiting transfer, transferring once, transferring twice, and transferring multiple times.
[0020] Preferably, the transfer-permitted cut-off time setting includes within 30 days from the generation of the commemorative medal, and within 180 days from the generation of the commemorative medal.
[0021] Preferably, the setting of the allowed transfer frequency includes allowing the next transfer only when more than 7 days have passed since the last transfer of the commemorative medal, and allowing the next transfer only when more than 30 days have passed since the last transfer of the commemorative medal.
[0022] The beneficial effect of implementing the present invention is that the relevant information of users participating in activities can be recorded on the blockchain, making the relevant information unchangeable, always credible and traceable. By participating in the activities, participants can obtain commemorative medals associated with the activities to prove their relevance to the activities, thereby achieving the purpose of commemorating the activities. By setting commemorative medal transfer rules in the contract, the needs of different levels of activity participation proof scenarios can be effectively met. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] The present invention is further described below in conjunction with the accompanying drawings and embodiments.
[0024] Figure 1 It is an interactive schematic diagram of the present invention;
[0025] Figure 2 This is a schematic diagram of the core data association relationship on the blockchain of the present invention;
[0026] Figure 3 A schematic diagram showing the relationship between the activities, the collection code, and the commemorative medal of the present invention;
[0027] Figure 4 This is a schematic diagram of determining the rules for transferring commemorative medals between accounts according to the present invention. DETAILED DESCRIPTION
[0028] [Example 1]
[0029] The present invention provides an activity commemoration method based on blockchain.
[0030] First, as Figure 2 As shown, the present invention establishes an on-chain data association relationship based on the blockchain contract, the association relationship can never be changed, and reflects that each commemorative medal must represent and can only represent one activity. The association relationship includes the activity unique identifier, the commemorative medal unique identifier, and the activity description data.
[0031] The unique activity identifier represents an activity, and each activity has only one activity identifier in the contract. The activity identifier and the activity description data are in a one-to-one correspondence.
[0032] The unique badge identifier represents each badge, and different badges have completely different identifiers. A blockchain account can own a badge, and the essence of a blockchain account owning a badge is that the blockchain account owns the unique badge identifier.
[0033] Preferably, the unique identifier of the activity and the unique identifier of the commemorative medal can be generated by various public algorithms that ensure uniqueness, such as a self-incrementing number, a universally unique identifier (UUID), a random number hash, etc.
[0034] Furthermore, in the contract, each badge unique identifier must be associated with and can only be associated with one activity unique identifier at most. Conversely, an activity unique identifier can be associated with multiple badge unique identifiers. This technical model reflects that each badge must represent and can only represent one activity, while an activity can issue multiple badges.
[0035] Second, as Figure 1 As shown, the present invention establishes a set of activity participation relationship chain process, involving three roles: platform party, activity organizer, and activity participant.
[0036] First, the event organizer submits the event information to the platform system and applies for the event code.
[0037] Secondly, the platform system generates a set of non-duplicate collection codes associated with the event and returns them to the event organizer, such as Figure 3 As shown, each collection code must be associated with and can only be associated with one activity at most.
[0038] Then, the event organizer will distribute the collection code to the participants of the activity associated with the collection code according to the needs of the activity, which represents the event organizer's recognition of the event participants' participation in the event. The distributed collection code becomes proof of the participants' participation in the event.
[0039] Then, the event participants submit the collection code and their blockchain account address to the platform at the same time.
[0040] Finally, the platform verifies the code submitted by the participant, and after verifying that it is indeed issued by the platform, the platform will mint a commemorative medal associated with the activity mapped by the code on the blockchain, and Figure 2 The medallion is minted in the blockchain account submitted by the participant, as shown Figure 3 As shown, the commemorative medallions minted for each collection code are different and unique.
[0041] In a third aspect, the present invention provides a method for setting rules for transferring commemorative medals between accounts. The transfer rules refer to the mandatory rules that must be followed when transferring commemorative medals between different blockchain accounts set in the platform contract.
[0042] Preferably, if Figure 4 The transfer rules of commemorative medals between different blockchain accounts include setting the upper limit of the number of transfers allowed, setting the transfer deadline, and setting the transfer frequency allowed.
[0043] Preferably, in this embodiment, the upper limit of the number of times allowed for transfer is set to 0, that is, the transfer of commemorative medals between accounts is prohibited.
[0044] Preferably, since the upper limit of the number of transfers has been set to 0, that is, the transfer of commemorative medals between accounts has been prohibited in the blockchain contract, the settings of the allowed transfer deadline and the allowed transfer frequency in this embodiment are meaningless and do not need to be set again.
[0045] Through this embodiment, the on-chain commemorative medal is soul-bound with the blockchain account of the event participant when it is minted, and the account that first receives the commemorative medal becomes the permanent ownership account of the commemorative medal. Event participants can strictly prove that they have participated in the relevant activities by issuing commemorative medals, and the participants' ability to prove this is permanent and credible. This embodiment is suitable for scenarios where the transfer of commemorative medals is strictly prohibited, such as exam certificate commemorative medals, official competition medals, membership certification commemorative medals, etc.
[0046] [Example 2]
[0047] like Figure 4 As shown, the transfer rules between commemorative medal accounts can also be, preferably, set as follows: the upper limit of the number of transfers allowed is 2 times, the transfer deadline allowed is within 180 days, and the transfer frequency allowed is 30 days before another transfer. Compared with Example 1, the transfer rules of this embodiment are conducive to users collecting commemorative medals, and can solve the problem that the commemorative medals of event participants are scattered among different accounts and can never be collected. Because the number of transfers allowed is only 2 times and the transfer deadline is limited to 180 days, the phenomenon of free and unlimited transfers destroying the significance of event commemoration is effectively blocked. This embodiment is suitable for commemorative scenes that tend to be entertainment activities. Commemorative medals can be used to replace event tickets, for self-organized outdoor activities, for reading clubs, for car clubs, etc.
Claims
1. A method for commemorating an activity based on blockchain, including blockchain, contract data association, and activity data on-chain process, characterized in that: A data association relationship on the chain was established, a set of activity participation relationship on-chain processes was established, and a method for setting rules for transferring commemorative medals between accounts was provided.
2. The method for commemorating an activity based on blockchain according to claim 1, characterized in that: The platform system has a separate contract on the blockchain, in which it will generate a unique activity ID, a unique medal ID, and activity description data.
3. A blockchain-based activity commemoration method according to claim 1 or 2, characterized in that: Each activity has one and only one unique activity identifier in the contract. The activity unique identifier and the activity description data are in a one-to-one correspondence. The commemorative medal unique identifiers are completely different from each other. Each commemorative medal unique identifier must be associated with and can only be associated with one activity unique identifier at most.
4. The method for commemorating an activity based on blockchain according to claim 1, characterized in that: The process of uploading the activity participation relationship to the chain includes the generation of the collection code, the issuance of the collection code, and the initiation of the chain loading by the participants.
5. A blockchain-based activity commemoration method according to claim 1 or 4, characterized in that: The event organizer generates a set of collection codes associated with the event based on the platform system. The event organizer distributes the collection codes to participants of the event associated with the collection codes. Participants provide the collection codes and their blockchain account addresses to the platform at the same time, triggering the platform to mint a commemorative medal for the event associated with the collection code on the blockchain, and the commemorative medal is minted in the blockchain account submitted by the participant.
6. The method for commemorating an activity based on blockchain according to claim 1, characterized in that: Mandatory rules that must be followed when transferring commemorative medals between different blockchain accounts are set in the platform contract, including setting an upper limit on the number of transfers allowed, setting a transfer deadline, and setting a transfer frequency allowed.
7. A blockchain-based activity commemoration method according to claim 1 or 6, characterized in that: The upper limit of the number of transfers allowed should be set to 0 transfers, 1 transfer, 2 transfers, or a clear number of such times. The deadline for transfers allowed should be set to within 30 days from the generation of the commemorative badge, within 180 days from the generation of the commemorative badge, or a clear time length such as the above. The frequency of transfers allowed should be set to allow the next transfer to be made after 7 days from the last commemorative badge transfer, after 30 days from the last commemorative badge transfer, or a clear time length such as the above.
