Public welfare application management method and device based on blockchain

Abstract

The present disclosure discloses a blockchain-based public welfare application management method and device. The blockchain includes multiple nodes, each of which corresponds to a plurality of public welfare applications. The plurality of public welfare applications each have an uplink interface, and the plurality of public welfare applications upload public welfare tasks and user public welfare behavior data to the blockchain through their respective uplink interfaces. The method comprises: obtaining a first public welfare task published by a target public welfare application from the blockchain, where the target public welfare application is any one of the plurality of public welfare applications; displaying the first public welfare task in a task pool; after the user completes the first public welfare task, obtaining the user's public welfare behavior data from the blockchain; and determining the user's credit data based on the user's public welfare behavior data.

Description

Technical Field

[0001] The present disclosure relates to the field of blockchain technology, and in particular to a blockchain-based public welfare application management method and device. Background Art

[0002] Existing volunteer-based public welfare apps can only provide users with public welfare tasks and manage their public welfare activities based on their own platform data. This approach leads to the following problems: First, users can only perform public welfare tasks within the public welfare app they own. To perform public welfare tasks in other public welfare apps, they need to register separately, resulting in a low promotion rate for public welfare tasks; second, the public welfare activities of the same user can only be managed and evaluated separately within each public welfare app, and the management and evaluation methods of each public welfare app are prone to tampering or fraud, making it impossible to conduct a unified and effective evaluation of the public welfare activities of the same user. Summary of the Invention

[0003] In view of this, the present disclosure provides a blockchain-based public welfare application management method to achieve unified management of public welfare tasks in public welfare applications and public welfare behavior data generated by users performing public welfare tasks.

[0004] In a first aspect, a method for managing public welfare applications based on a blockchain is provided, wherein the blockchain includes multiple nodes, each of the multiple nodes corresponds to a multiple public welfare applications, each of the multiple public welfare applications has an uplink interface, and the multiple public welfare applications upload public welfare tasks and user public welfare behavior data to the blockchain through their respective corresponding uplink interfaces. The method includes: obtaining a first public welfare task issued by a target public welfare application from the blockchain, where the target public welfare application is any one of the multiple public welfare applications; displaying the first public welfare task in a task pool; after the first public welfare task is completed by the user, obtaining the user's public welfare behavior data from the blockchain; and determining the user's credit data based on the user's public welfare behavior data.

[0005] Optionally, the first public welfare task is selected by the user from the task pool or the target public welfare application.

[0006] Optionally, the user's public welfare behavior data includes confirmation data for the first public welfare task, the confirmation data is generated by the person being served by the first public welfare task or the initiator of the first public welfare task, and the confirmation data is used to confirm the validity of the first public welfare task.

[0007] Optionally, the confirmation data of the first public welfare task includes at least one of the following information: the content of the first public welfare task, the date on which the user starts the first public welfare task, the date on which the user ends the first public welfare task, the time it takes the user to complete the first public welfare task, the score of the user's completion of the first public welfare task, and the effectiveness result of the user's completion of the first public welfare task.

[0008] Optionally, the user's public welfare behavior data further includes at least one of the following information: the ID of the target public welfare application, the name of the target public welfare application, the type of the target public welfare application, the user's ID, and the user's name.

[0009] Optionally, determining the credit data of the user based on the public welfare behavior data of the user includes: inputting the time it takes for the user to complete the first public welfare task, the score for the user's completion of the first public welfare task, and the content of the first public welfare task in the public welfare behavior data of the user into a credit data conversion model, so that the credit data conversion model determines the credit data of the user according to different weights.

[0010] Optionally, the user's public welfare behavior data is encrypted and / or has an electronic signature and a timestamp.

[0011] Optionally, the credit data is a credit score.

[0012] Optionally, the public welfare application is a mini program or an APP.

[0013] In a second aspect, a public welfare application management device based on a blockchain is provided, wherein the blockchain includes multiple nodes, each of which corresponds to a plurality of public welfare applications. The plurality of public welfare applications all have an uplink interface, and the plurality of public welfare applications upload public welfare tasks and user public welfare behavior data to the blockchain through their respective corresponding uplink interfaces. The device includes: a first acquisition module, for acquiring a first public welfare task issued by a target public welfare application from the blockchain, where the target public welfare application is any one of the plurality of public welfare applications; a display module, for displaying the first public welfare task in a task pool; a second acquisition module, for acquiring the user's public welfare behavior data from the blockchain after the user completes the first public welfare task; and a determination module, for determining the user's credit data based on the user's public welfare behavior data.

[0014] Optionally, the first public welfare task is selected by the user from the task pool or the target public welfare application.

[0015] Optionally, the user's public welfare behavior data includes confirmation data for the first public welfare task, the confirmation data is generated by the person being served by the first public welfare task or the initiator of the first public welfare task, and the confirmation data is used to confirm the validity of the first public welfare task.

[0016] Optionally, the confirmation data of the first public welfare task includes at least one of the following information: the content of the first public welfare task, the date on which the user starts the first public welfare task, the date on which the user ends the first public welfare task, the time it takes the user to complete the first public welfare task, the score of the user's completion of the first public welfare task, and the effectiveness result of the user's completion of the first public welfare task.

[0017] Optionally, the user's public welfare behavior data further includes at least one of the following information: the ID of the target public welfare application, the name of the target public welfare application, the type of the target public welfare application, the user's ID, and the user's name.

[0018] Optionally, the determination module is also used to input the time it takes for the user to complete the first public welfare task, the score for the user's completion of the first public welfare task, and the content of the first public welfare task in the user's public welfare behavior data into a credit data conversion model, so that the credit data conversion model determines the user's credit data according to different weights.

[0019] Optionally, the user's public welfare behavior data is encrypted and / or has an electronic signature and a timestamp.

[0020] Optionally, the credit data is a credit score.

[0021] Optionally, the public welfare application is a mini program or an APP.

[0022] In a third aspect, a blockchain-based public welfare application management device is provided, comprising a memory and a processor, wherein the memory stores executable code, and the processor is configured to execute the executable code to implement the method described in the first aspect.

[0023] In a fourth aspect, a computer-readable storage medium is provided, on which executable code is stored. When the executable code is executed, the method described in the first aspect can be implemented.

[0024] In a fifth aspect, a computer program product is provided, comprising an executable code, which, when executed, can implement the method described in the first aspect.

[0025] The disclosed embodiment provides a blockchain-based public welfare application management solution, wherein multiple nodes of the blockchain correspond one-to-one to multiple public welfare applications, so that the multiple public welfare applications can save the public welfare tasks within them and the public welfare behavior data of users on the blockchain through their respective link interfaces. The solution can obtain the first public welfare task issued by the target public welfare application from the blockchain and display it in the task pool, and can generate credit data for the user based on the public welfare behavior data generated after the user completes the first public welfare task. In this way, on the one hand, the public welfare tasks issued by multiple public welfare applications can be managed in a unified manner, so that users can find and complete the public welfare tasks issued by multiple public welfare applications through a unified entrance, effectively promoting public welfare tasks; on the other hand, the public welfare behavior data of the same user can be uniformly and effectively evaluated, avoiding the possibility of tampering with and falsification of the user's public welfare behavior data. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 A schematic diagram of the blockchain architecture provided for the implementation of this disclosure.

[0027] Figure 2 This is a system architecture diagram of a unified management platform for public welfare applications provided in an embodiment of the present disclosure.

[0028] Figure 3 A schematic diagram of the structure of a blockchain composed of public welfare applications provided in an embodiment of the present disclosure.

[0029] Figure 4 This is a flowchart of a blockchain-based public welfare application management method provided by an embodiment of the present disclosure.

[0030] Figure 5 This is a schematic diagram of a solution for managing public welfare applications using a unified management platform for public welfare applications provided by an embodiment of the present disclosure.

[0031] Figure 6 yes Figure 5 Schematic diagram of the method flow in the scheme shown.

[0032] Figure 7 It is a structural diagram of a blockchain-based public welfare application management device provided by an embodiment of the present disclosure.

[0033] Figure 8 This is a structural diagram of a blockchain-based public welfare application management device provided in another embodiment of the present disclosure. DETAILED DESCRIPTION

[0034] The technical solutions in the embodiments of the present disclosure are clearly and completely described below. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all the embodiments.

[0035] A volunteer service-type public welfare application is a public welfare application that helps volunteers (or users) use their offline time to provide services to people or organizations in need. The application mentioned in the embodiments of the present disclosure may also be referred to as an application program. In some embodiments, the application may refer to an APP, such as be my eyes, Xiao Ai Bang Bang, Yun Tong and other APPs. In other embodiments, the application may refer to a mini-program (a mini-program can be understood as an application that can be used without downloading or uninstalling, and is a lightweight solution for applications, such as an Alipay mini-program or a WeChat mini-program). Alternatively, in some embodiments, the application may also be a website that provides services, for example, a website where a large organization issues public welfare tasks.

[0036] Existing public welfare applications can only provide users with public welfare tasks posted on their own platforms. After users register for a public welfare application, they can only perform public welfare tasks within the application. After users perform public welfare tasks, they generally generate public welfare behavior data, and existing public welfare applications can only manage users' public welfare behavior data within their own platforms. Public welfare behavior data can be data that represents the user's efforts when performing the public welfare task, such as the time spent. This approach will cause the following problems: the promotion rate of public welfare tasks is not high, and because public welfare applications generally use centralized databases, users' public welfare behavior data is likely to be tampered with and falsified. Therefore, it is impossible to conduct a unified, authoritative and effective assessment of the public welfare behavior of the same user, resulting in low credibility.

[0037] In light of this, the disclosed embodiments provide a blockchain-based public welfare application management solution. Because blockchain technology can organize and maintain large amounts of data in a decentralized or multi-centralized manner, and features characteristics such as distribution, immutability, traceability, and security and reliability, managing public welfare applications with the help of blockchain can unify the management of public welfare tasks and user public welfare behavior data, effectively solving the aforementioned problems.

[0038] To facilitate understanding, a brief introduction to the blockchain and some of its concepts involved in the embodiments of the present disclosure is first given.

[0039] Blockchain

[0040] See also Figure 1Blockchain 100 is a typical distributed collaborative system, and can also be referred to as a blockchain network. The system includes multiple blockchain nodes 110. These multiple blockchain nodes 110 can collectively maintain a continuously growing distributed data record. The content and time sequence of these recorded data can be protected using cryptographic techniques, making it difficult for any party to tamper with, deny, or falsify information. Blockchain nodes 110 can be devices with computing capabilities, such as servers, server groups, or blockchain chips. The server groups can be centralized or distributed. In other implementations, the aforementioned servers can also be servers providing services for a cloud platform.

[0041] In a blockchain, data (e.g., transaction information, transaction results, etc.) can be encapsulated in blocks. Blocks can be linked to each other through forward references to form a "chain," or blockchain. Typically, the first block in a blockchain is called the "genesis block" or "initial block," the block preceding the current block is called the "previous block," and the block following the current block is called the "successor block."

[0042] Typically, a block consists of a block header and a block body. The block header contains basic information about the current block, ensuring that it is correctly included in the blockchain. For example, the block header may record the block hash value of the previous block. Another example is the block height of the current block. This height, also known as "block height," identifies the block's position in the blockchain. Typically, the genesis block has a block height of 0. The block body can be used to record transaction information. This transaction information may include, for example, the transaction amount and transaction data.

[0043] Blockchains are generally divided into three types: public blockchain, private blockchain, and consortium blockchain. Furthermore, there can be combinations of these types, such as private blockchain + consortium blockchain, or consortium blockchain + public blockchain.

[0044] Public blockchains are the most decentralized. Participants in a public blockchain (also known as nodes in the blockchain) can access data records, participate in transactions, and compete for the right to record new blocks. Furthermore, each node can freely join or leave the network and perform related operations.

[0045] In contrast, a private blockchain has write permissions controlled by a specific organization or institution, while data read permissions are regulated by that organization. Simply put, a private blockchain can be a weakly centralized system with strict node restrictions and a small number of nodes. This type of blockchain is more suitable for internal use within a specific organization.

[0046] A consortium blockchain is a blockchain that sits somewhere between public and private blockchains, enabling partial decentralization. Each node in a consortium blockchain typically has a corresponding entity or organization; nodes join the network through authorization and form a stakeholder alliance to jointly maintain the blockchain's operations. The embodiments provided in this disclosure can be implemented on any suitable type of blockchain mentioned above, preferably on a consortium blockchain to ensure the credibility and authority of the data on the blockchain.

[0047] In some implementations, blockchain node 110 may have a corresponding blockchain client (referred to as client), and blockchain node 110 may connect to the client to enable the client to access blockchain services. A client may be a terminal device or an application on a terminal device. A terminal device may be any device with computing capabilities, such as a mobile phone, computer, wearable computing device, or server. A client may obtain blockchain services by initiating a blockchain transaction (referred to as a transaction, also referred to as a request). That is, the client may generate a transaction and send the generated transaction to the blockchain via blockchain node 110. For example, a client may initiate a request to upload its data to its corresponding blockchain node 110. In response to the request, blockchain node 110 may store the data on the blockchain.

[0048] However, when the user end is an application on an external terminal device, the user end cannot directly interact with the corresponding blockchain node 110. To effectively solve this problem, in some implementations, an externally accessible application program interface (API) can be deployed in the application to enable the application to interact with the blockchain node 110 through the API.

[0049] Consensus Mechanism

[0050] The consensus mechanism can be understood as how the nodes responsible for keeping records (or accounting nodes) on the blockchain reach a consensus to determine the validity of a record. The consensus mechanism disseminates data obtained by one blockchain node to other nodes on the blockchain. This process can also be understood as storing data on the blockchain.

[0051] The blockchain consensus mechanism embodies the characteristics of "majority rule" and "equality for all." "Majority rule" doesn't necessarily refer solely to the number of nodes; it can also refer to computing power, equity stakes, or other computer-comparable characteristics. "Equality for all" means that when nodes meet certain conditions, all nodes have the right to propose consensus results first, which, upon direct approval by other nodes, may ultimately become the final consensus result.

[0052] The self-trust of blockchains is primarily reflected in the fact that users distributed across the blockchain do not need to trust the other party or a centralized institution; they only need to trust the software system underlying the blockchain protocol to conduct transactions. This self-trust is premised on the blockchain's consensus mechanism. Specifically, in a market without mutual trust, the necessary and sufficient condition for consensus among nodes is that each node, motivated by its own self-interest, will voluntarily and honestly adhere to the pre-defined rules of the protocol, verify the authenticity of each record, and ultimately record those deemed authentic in the blockchain. In other words, if each node has independent and competing interests, collusion to defraud is virtually impossible. This is especially true when nodes have a shared reputation within the network. Blockchain technology utilizes a consensus-based mathematical algorithm to establish a network of trust between machines, thereby creating a new kind of trust through technological endorsement rather than centralized credit institutions.

[0053] The consensus mechanism of the blockchain can be, for example, one of the following consensus mechanisms: Proof of Work (POW), Proof of Stake (POS), Proof of Share Authorization, Validation Pool, and Practical Byzantine Fault Tolerance (PBFT).

[0054] In view of the above characteristics of blockchain, such as Figure 2 FIG2 is a diagram showing the system architecture of a unified management platform for public welfare applications based on blockchain according to an embodiment of the present disclosure. The system architecture 20 of the unified management platform for public welfare applications may include a public welfare application terminal 21, a data transmission terminal 22, a blockchain terminal 23, and a public welfare management application terminal 24.

[0055] The public welfare application terminal 21 can be a public welfare application. The public welfare application can be any type of public welfare application as described above. The user of the public welfare application can be the user as described above (i.e., volunteer), or the initiator of a public welfare task or the person being served by the public welfare task in the public welfare application. The public welfare application can be used to allow the initiator or the person being served to publish public welfare tasks on their own, or to allow users to select public welfare tasks within the application. The public welfare application can also generate public welfare behavior data for the user after the user executes the public welfare task within the public welfare application.

[0056] The public welfare tasks mentioned in this disclosure may be any form of volunteer service, for example, helping the blind to read instructions, helping astronomical research institutes to identify scientific stargazing, helping left-behind children in mountainous areas to remotely install software, helping to explain in museums, helping environmental enthusiasts or those hiking in remote scenic spots to clean up garbage, helping to accompany children in welfare institutions, etc. Users of public welfare applications can register accounts, claim public welfare tasks, publish public welfare tasks, and perform other related operations (for example, operations when users start and end public welfare tasks, confirmation operations by the initiator of public welfare tasks or the service personnel of the public welfare tasks on the completion of the public welfare tasks performed by users, etc.) through the public welfare application interface.

[0057] This disclosure does not specifically limit the form of data generated by public welfare applications regarding public welfare activities. As an implementation method, users can be offline users of the public welfare application's platform. After a user performs a public welfare task offline, the public welfare application's administrator, the initiator of the public welfare task, or the person being served can upload data on the user's performance and completion of the task. The public welfare application then automatically generates public welfare activity data based on this data.

[0058] As another implementation method, the user can be an online user of the public welfare application platform. After the user starts a public welfare task in the public welfare application and completes the task, the user can click on "Completed" in the interface of the public welfare task, so that the public welfare application automatically generates the user's public welfare behavior data for the public welfare task completed by the user, and the public welfare behavior data includes information indicating that the user has completed the public welfare task; or after the user starts a public welfare task in the public welfare application, but interrupts or abandons the task for various reasons, the user can click on "Unfinished" or "Abandoned" in the interface of the public welfare task, and the public welfare application can also automatically generate the user's public welfare behavior data for the public welfare task performed by the user, and the public welfare behavior data includes information indicating that the user has not completed the task.

[0059] The data transmission terminal 22 can be understood as the portion of the public welfare application terminal 21 that enables the public welfare application to communicate with the blockchain terminal 23. For example, the data transmission terminal 22 can be an API embedded in the public welfare application. The public welfare application can send a transaction request to the blockchain through the embedded API to store the data in the public welfare application on the blockchain. This disclosure does not specifically limit the data in the public welfare application. For example, it can be request data for the public welfare application to use blockchain services, data of public welfare tasks issued by the public welfare application, or the public welfare behavior data of the above-mentioned users.

[0060] In some implementations, the API can also assist users in public welfare applications in identity verification or assist in encryption when uploading data.

[0061] The blockchain terminal 23 includes a blockchain composed of multiple public welfare applications. Each of the multiple public welfare applications can have the same function as the above public welfare application. Multiple public welfare applications together constitute a blockchain. The blockchain includes multiple nodes. The multiple nodes are trusted nodes of the blockchain and correspond one-to-one with the multiple public welfare applications. Figure 3 FIGURE 1 is a schematic diagram of the architecture of a blockchain 30 composed of multiple public welfare applications provided in an embodiment of the present disclosure. Figure 3 Public welfare applications A, B, C, and D, among others, collectively constitute a blockchain 30. These applications can be public welfare applications on terminal devices outside the blockchain. Nodes A', B', C', and D' are trusted nodes for these applications on the blockchain. Each node corresponds to a public welfare application (e.g., node A' corresponds to public welfare application A), enabling public welfare applications to interact with the blockchain through the corresponding node. Specifically, each public welfare application can send a transaction request through its own API to upload public welfare tasks and user public welfare behavior data to the blockchain node corresponding to each public welfare application. After the corresponding blockchain node receives the data uploaded by the public welfare application, it initiates a consensus request, and other nodes on the blockchain respond to the request based on the consensus mechanism. If consensus is reached, the blockchain node can broadcast the data to other nodes on the blockchain to complete the data on-chain and storage.

[0062] In some implementations, such as Figure 2 As shown, the blockchain of the blockchain end 23 can also perform on-chain encryption on the data requested by the public welfare application and / or add digital signatures and timestamps to the data on the blockchain. The specific implementation method can be found in the following text and will not be explained in detail here.

[0063] Continue to see Figure 2The public welfare management application 24 may be an application layer that provides functionality for the unified management platform 20. In some embodiments, the public welfare management application 24 may also be referred to as a public welfare points system. The public welfare management application 24 may provide functions including, but not limited to, displaying public welfare tasks, managing user-performed public welfare tasks, and managing user credit data.

[0064] Public welfare tasks can be displayed by displaying the public welfare tasks published by various public welfare applications on the public welfare management application 24. For example, public welfare tasks A1, A2, and A3 published by public welfare application A, public welfare tasks B1 and B2 published by public welfare application B, and public welfare task C1 published by public welfare application C can be displayed simultaneously in the task pool. It should be understood that the above examples are for illustrative purposes only, and this disclosure does not impose specific restrictions on the number of public welfare applications and public welfare tasks, and can be set accordingly based on actual needs.

[0065] In some implementations, the public welfare management application 24 may also include a query function, allowing third-party organizations to query and use the user's credit data. For example, the third-party organization may be a corporate credit product model (such as a credit product like Sesame Credit or a bank's user risk assessment model), which may use the user's credit data as an evaluation factor in its model. Another example is a government agency, which may use the user's credit data as part of its citizen evaluation and assessment (e.g., resident credit, talent programs, household registration points, etc.).

[0066] The public welfare management application terminal 24 can be executed by a management device. The present disclosure does not make any specific limitations on the management device. For example, the management device can be a device with computing capabilities or an application on the device. For example, the management device can be a server, or a mobile terminal, or it can also be an application on a mobile terminal, such as an APP, a mini-program, or a website. When the management device is an application on a mobile terminal, the registered user of the application can be a user (the volunteer mentioned above) or the public welfare application mentioned above. In other embodiments, the registered user can also be the third-party organization mentioned above.

[0067] The public welfare management application end 24 can interact with the blockchain end 23 to obtain the data it needs from the blockchain within the blockchain end 23 (for example, the public welfare tasks uploaded by the public welfare application and the user's public welfare behavior data), so as to realize the above functions based on the data obtained from the blockchain, that is, to realize the management of the public welfare application.

[0068] The following combination Figure 4The blockchain-based public welfare application management method provided by the embodiments of the present disclosure is described in detail. It is understood that this method can be implemented by the public welfare management application terminal 24, or it can be understood that the method is executed by the aforementioned management device. It should be noted that some of the features involved in this method have been described in detail in the above content. Please refer to the above content for relevant features and will not be repeated here.

[0069] In step S410, a first public welfare task published by a target public welfare application is obtained from the blockchain.

[0070] The target public welfare application may be any one of the plurality of public welfare applications described above. The first public welfare task may be one of the plurality of public welfare tasks issued by the target public welfare application, and the first public welfare task may be, but is not limited to, any type of public welfare task described above.

[0071] The first public welfare task may include multiple data about the first public welfare task, such as the specific content of the first public welfare task (including time requirements, location requirements, task type, task name, etc.), information of the publisher of the first public welfare task, information of the target public welfare application corresponding to the first public welfare task, and a link entry for executing the first public welfare task.

[0072] This disclosure does not specifically limit the implementation method for obtaining the first public welfare task published by the target public welfare application from the blockchain. For example, the target public welfare application may send a display request for the first public welfare task through an API and request that the first public welfare task be stored on the blockchain. The blockchain, in response to the request, stores the first public welfare task on the blockchain and uploads the display request to the management device. The management device, in response to the display request, retrieves the first public welfare task from the blockchain.

[0073] In step S420, the first public welfare task is displayed in the task pool.

[0074] The task pool can be a program module with display capabilities on the front end, and multiple public welfare tasks can be displayed in the task pool. Figure 5 As shown, the public welfare tasks displayed in the public welfare pool are displayed after the public welfare application sends a display request for the public welfare tasks.

[0075] As mentioned above, the first public welfare task includes multiple data. The present disclosure does not specifically limit the data and form in which the first public welfare task is displayed in the task pool. For example, all data of the first public welfare task can be displayed in the task pool, or part of the multiple data of the first public welfare task can be displayed in the task pool. The display can be in the form of text or in the form of pictures.

[0076] As an implementation method, the public welfare pool can display the specific content of the first public welfare task and the link entrance for executing the first public welfare task, so that users can directly select tasks through the task pool and enter the target public welfare application through the link entrance to execute the first public welfare task.

[0077] In step S430, after the first public welfare task is completed by the user, the public welfare behavior data of the user is obtained from the blockchain.

[0078] Since the task pool and the target public welfare application in the embodiment of the present disclosure can both display public welfare tasks within the public welfare application, the user can select the first public welfare task through the target public welfare application or by selecting the first public welfare task in the task pool. It is understandable that the task pool can only serve as a display environment for the first public welfare task. Even if the user selects the first public welfare task in the task pool, the user will enter the target public welfare application through the link entrance after clicking to execute. That is to say, after the user executes the first public welfare task, it can trigger an authentication request for task completion. In response to the request, the target public welfare application will generate the public welfare behavior data of the user for the first public welfare task. After that, the target public welfare application can upload the user's public welfare behavior data to the blockchain through the API and save it.

[0079] The user's public welfare behavior data may include, but is not limited to, the public welfare behavior data described above. For example, it may also include the user's location and the location where the first public welfare task is performed. In some implementations, as shown in Table 1, the user's public welfare behavior data may also include at least one of the following information: the content of the first public welfare task, the date the user starts the first public welfare task, the date the user ends the first public welfare task, the length of time the user completes the first public welfare task, etc. Setting the content included in the user's public welfare behavior data to be as detailed as in the embodiment of the present disclosure is more conducive to subsequent data management from multiple aspects and dimensions.

[0080] Of course, in addition to this, a user's public welfare behavior data can also include information about the attributes of the user or the target public welfare application. As shown in Table 1, public welfare behavior data can also include at least one of the following information: the ID of the target public welfare application, the name of the target public welfare application, the type of the target public welfare application, and the user's ID and name. Because the user's public welfare behavior data includes user attribute information, the user's public welfare behavior data on the blockchain can be labeled, thereby forming the user's public welfare passport on the blockchain. For example, the public welfare passport can be the user's unique identity ID.

[0081] Table 1

[0082]

[0083] In step S440, the user's credit data is determined based on the user's public welfare behavior data.

[0084] The user's credit data is data that indicates the user's creditworthiness, and may be, for example, a credit score.

[0085] This disclosure does not specifically limit the specific method for determining a user's credit data based on their public welfare behavior data. As an implementation method, a calculation function can be set based on the user's public welfare behavior data, including the duration of time the user completed the first public welfare task, the distance from the execution location, and the substantive requirements of the first public welfare task for the user, to calculate the user's public welfare behavior data.

[0086] As another implementation, a user's public welfare behavior data can be determined using a pre-set credit data conversion model. This credit data conversion model can be a neural network model, a function, or a pre-calibrated grading table. By inputting the user's public welfare behavior data (for example, the time it takes for the user to complete a first public welfare task, the score for the user's completion of the first public welfare task, and the content of the first public welfare task in the user's public welfare behavior data) into the credit data conversion model, the credit data conversion model determines the user's credit data based on different weights. For example, the weight corresponding to the content of the public welfare task is 0.5, the weight corresponding to the duration is 0.3, and the weight corresponding to the evaluation is 0.2. The public welfare tasks are divided into a difficulty level of 1-10 based on the difficulty of the task content. If the first public welfare task is for the user to translate for an international conference, the difficulty level is 8. If the first public welfare task is for the user to organize personnel for a public welfare organization, the difficulty level is 2. The evaluation is divided into a level of 0-5. If a user completes a public welfare task with a difficulty level of 8 for 1 hour and the evaluation is 4.5 points, the user's credit data is 5.2. If a user completes a public welfare task with a difficulty level of 2 for 1 hour and receives a rating of 4.5 points, the user's credit data will be 2.2.

[0087] It can be understood that since the user's public welfare behavior data in the present disclosure includes a variety of data, evaluating the user's credit data based on the user's public welfare behavior data in the present disclosure will obtain a more objective and authoritative evaluation.

[0088] In the management method of public welfare applications based on blockchain provided by the embodiment of the present disclosure, its blockchain can connect multiple public welfare applications, so that the public welfare tasks and user public welfare behavior data issued by multiple public welfare applications can be uniformly stored. This method can obtain public welfare tasks from the blockchain and display them uniformly, and after obtaining the user's public welfare behavior data through the blockchain, the data is converted into the user's credit data, so that users (i.e. volunteers) can find and complete public welfare tasks through a unified entrance, and the public welfare behavior data of the same user generated in multiple public welfare applications can also be converted into the user's credit data according to a unified standard. This not only avoids multiple registrations and effectively promotes public welfare tasks, but also constructs a public welfare service resume for users, so that the credit data on the resume can be used by third-party institutions, thereby making users have a very high enthusiasm for service and effectively promoting the national popularity of public welfare services.

[0089] This disclosure does not specifically limit the method by which the target public welfare application stores the user's public welfare behavior data on the blockchain, and it can be any of the methods described above. As an implementation method, Figure 5 and Figure 6 As shown, the target public welfare application can first initiate a user identity verification request to the blockchain through the API. In response to this request, the API can use facial recognition, fingerprint authentication, or key authentication to verify whether the user is the holder of the public welfare passport corresponding to their ID. By verifying the user's identity, the authenticity of the data can be guaranteed to the greatest extent.

[0090] In other implementations, such as Figure 5 As shown, after identity verification is passed, the API can further encrypt the public welfare behavior data and upload it to the corresponding blockchain node. When the node stores the user's public welfare behavior data on the blockchain (that is, before transmitting the node's data to other nodes), it can further encrypt and / or add an electronic signature and timestamp to maximize the immutability of the user's public welfare behavior data.

[0091] This disclosure does not specifically limit the encryption method for public welfare behavior data. As an implementation method, the API and blockchain nodes can encrypt public welfare behavior data based on a hash algorithm or symmetric encryption technology.

[0092] As another implementation, Figure 6As shown, blockchain nodes can encrypt public welfare activity data using asymmetric encryption. It's understood that electronic signatures also typically utilize asymmetric encryption. Specifically, the target public welfare application, as a trusted node on the blockchain, receives a private and public key pair when applying to join the blockchain. This private key is accessible only to the target public welfare application; other nodes have completely different private keys. Signing the same data with different private keys results in completely different results, similar to the handwriting of a physical signature (i.e., each person's pen signature is completely different). Using the private key to encrypt a user's public welfare activity data is called adding an electronic signature, and the encrypted data is the digital signature. The public key is shared by all nodes on the same blockchain as the target public welfare application. Upon receiving the broadcasted public welfare activity data and digital signature, other nodes can use the public key to verify the data's integrity and the sender's identity. Successful verification triggers subsequent processes, such as each node saving the data on the blockchain.

[0093] As mentioned above, the target public welfare application can generate public welfare behavior data of the user for the first public welfare task after the user triggers the authentication request for task completion. In order to avoid the possibility of falsification by the user's own confirmation of the completion of the task. In some embodiments, Figure 6 As shown, after the user completes the first public welfare task within the target public welfare application, the service validity can be confirmed by the person being served or the task initiator. Specifically, the target public welfare application can receive an authentication request for the first public welfare task initiated by the user, and obtain confirmation data for the target public welfare task from the initiator of the target public welfare task or the person being served in response to the request. The confirmation data is used to confirm the validity of the first public welfare task, that is, whether the user has completed the first public welfare task, whether the various data of the user's execution of the first public welfare task are consistent with the actual situation, and the quality of the user's completion of the public welfare task. As shown in Table 1, the confirmation data may include confirmation of at least one of the following information: the content of the first public welfare task, the date on which the user starts the first public welfare task, the date on which the user ends the first public welfare task, the time it takes for the user to complete the first public welfare task, the score for the user's completion of the first public welfare task, and the effectiveness result of the user's completion of the first public welfare task. In order to further ensure that the person being served or the task initiator is also valid, as Figure 6 As shown, before uploading the user's public welfare behavior data to the blockchain, the confirmation data of the service recipient or task initiator regarding the target public welfare task in the user's public welfare behavior data can also be sent to the user to obtain the user's confirmation. After the user confirms the confirmation data, the generated user's public welfare behavior data is uploaded to the corresponding blockchain node via the API.

[0094] As mentioned above and Figure 5 、 Figure 6 From the content, we can know that the public welfare points system can also manage the public welfare tasks performed by users based on the public welfare behavior data of users. From the above content, we can know that the public welfare behavior data generated by multiple public welfare tasks performed by users will be stored on the blockchain. After the public welfare points system obtains this data from the blockchain, it can display all the public welfare tasks performed by the user based on this data, and display their completion status. If the user's public welfare behavior data for the first public welfare task indicates that the user has completed the first public welfare task, the completion status of the first public welfare task claimed by the user will be registered as completed. If the user's public welfare behavior data for the second public welfare task indicates that the user has abandoned the second public welfare task, the completion status of the second public welfare task claimed by the user will be registered as abandoned and unfinished.

[0095] Combined with the above Figures 1 to 6 , describes the method embodiment of the present disclosure in detail, and the following is combined with Figures 7 and 8 , the device embodiment of the present disclosure is described in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so that the parts not described in detail can be referred to the previous method embodiment.

[0096] Figure 7 This is a schematic diagram of the structure of a blockchain-based public welfare application management device provided in one embodiment of the present disclosure. The blockchain includes multiple nodes, each corresponding to multiple public welfare applications. Each of the multiple public welfare applications has an uplink interface, and the multiple public welfare applications upload public welfare tasks and user public welfare behavior data to the blockchain through their corresponding uplink interfaces. The device 700 may include a first acquisition module 710, a display module 720, a second acquisition module 730, and a determination module 740. These modules are described in detail below.

[0097] The first acquisition module 710 is used to acquire a first public welfare task issued by a target public welfare application from the blockchain, where the target public welfare application is any one of multiple public welfare applications.

[0098] The display module 720 is used to display the first public welfare task in the task pool.

[0099] The second acquisition module 730 is used to obtain the user's public welfare behavior data from the blockchain after the first public welfare task is completed by the user.

[0100] The determination module 740 is used to determine the user's credit data based on the user's public welfare behavior data.

[0101] Optionally, the first public welfare task is selected by the user from a task pool or a target public welfare application.

[0102] Optionally, the user's public welfare behavior data includes confirmation data for the first public welfare task, the confirmation data is generated by the person being served by the first public welfare task or the initiator of the first public welfare task, and the confirmation data is used to confirm the validity of the first public welfare task.

[0103] Optionally, the confirmation data of the first public welfare task includes at least one of the following information: the content of the first public welfare task, the date on which the user starts the first public welfare task, the date on which the user ends the first public welfare task, the time it takes the user to complete the first public welfare task, the score of the user's completion of the first public welfare task, and the effectiveness result of the user's completion of the first public welfare task.

[0104] Optionally, the user's public welfare behavior data further includes at least one of the following information: the ID of the target public welfare application, the name of the target public welfare application, the type of the target public welfare application, the user's ID, and the user's name.

[0105] Optionally, the determination module is also used to input the time it takes for the user to complete the first public welfare task, the score for the user's completion of the first public welfare task, and the content of the first public welfare task in the user's public welfare behavior data into the credit data conversion model, so that the credit data conversion model determines the user's credit data according to different weights.

[0106] Optionally, the user's public welfare behavior data is encrypted and / or has an electronic signature and a time stamp.

[0107] Optionally, the credit data is a credit score.

[0108] Optionally, the public welfare application is a mini program or an APP.

[0109] Figure 8 This is a schematic diagram of the structure of a blockchain-based public welfare application management device, provided in accordance with another embodiment of the present disclosure. The device 800 may be, for example, a computing device with computing capabilities. For example, the device 800 may be a mobile terminal or a server. The device 800 may include a memory 810 and a processor 820. The memory 810 may be used to store executable code. The processor 820 may be used to execute the executable code stored in the memory 810 to implement the steps of the various methods described above. In some embodiments, the device 800 may also include a network interface 830, through which data exchange between the processor 820 and external devices may be implemented.

[0110] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present disclosure is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0111] Those skilled in the art will appreciate that the units and algorithm steps of the various examples described in conjunction with the embodiments of the present disclosure can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0112] In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0113] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0114] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0115] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A blockchain-based public welfare application management method, wherein the blockchain comprises a plurality of nodes, each of which corresponds to a plurality of public welfare applications. Each of the plurality of public welfare applications has an uplink interface, and each of the plurality of public welfare applications uploads public welfare tasks and user public welfare behavior data to the blockchain through its corresponding uplink interface. The method comprises: Obtaining a first public welfare task issued by a target public welfare application from the blockchain, wherein the target public welfare application is any one of the multiple public welfare applications; Displaying the first public welfare task in the task pool; After the first public welfare task is completed by the user, obtaining the public welfare behavior data of the user from the blockchain; Determining the user's credit data based on the user's public welfare behavior data; The first public welfare task is selected by the user from the task pool or the target public welfare application, and the first public welfare task is one of multiple public welfare tasks released by the target public welfare application.

2. According to the method according to claim 1, the user's public welfare behavior data includes confirmation data for the first public welfare task, the confirmation data is generated by the person being served by the first public welfare task or the initiator of the first public welfare task, and the confirmation data is used to confirm the validity of the first public welfare task.

3. According to the method according to claim 2, the confirmation data of the first public welfare task includes at least one of the following information: the content of the first public welfare task, the date on which the user starts the first public welfare task, the date on which the user ends the first public welfare task, the time it takes for the user to complete the first public welfare task, the score of the user's completion of the first public welfare task, and the effectiveness result of the user's completion of the first public welfare task.

4. The method according to claim 2, wherein the user's public welfare behavior data further includes at least one of the following information: the ID of the target public welfare application, the name of the target public welfare application, the type of the target public welfare application, the user's ID, and the user's name.

5. The method according to claim 3, Determining the user's credit data based on the user's public welfare behavior data includes: The time it takes for the user to complete the first public welfare task, the score for the user's completion of the first public welfare task, and the content of the first public welfare task in the user's public welfare behavior data are input into the credit data conversion model, so that the credit data conversion model determines the user's credit data according to different weights.

6. According to the method according to any one of claims 1-5, the user's public welfare behavior data is encrypted and / or has an electronic signature and time stamp.

7. The method according to any one of claims 1-5, wherein the credit data is a credit score.

8. The method according to any one of claims 1 to 5, wherein the public welfare application is a mini program or an APP.

9. A blockchain-based public welfare application management device, wherein the blockchain includes multiple nodes, each of which corresponds to a plurality of public welfare applications. Each of the plurality of public welfare applications has an uplink interface, and the plurality of public welfare applications upload public welfare tasks and user public welfare behavior data to the blockchain through their respective corresponding uplink interfaces. The device comprises: A first acquisition module is configured to acquire, from the blockchain, a first public welfare task issued by a target public welfare application, where the target public welfare application is any one of the multiple public welfare applications; A display module, configured to display the first public welfare task in a task pool; A second acquisition module is configured to acquire the user's public welfare behavior data from the blockchain after the user completes the first public welfare task; A determination module, configured to determine the user's credit data based on the user's public welfare behavior data; The first public welfare task is selected by the user from the task pool or the target public welfare application, and the first public welfare task is one of multiple public welfare tasks released by the target public welfare application.

10. A blockchain-based public welfare application management device, comprising a memory and a processor, wherein the memory stores executable code, and the processor is configured to execute the executable code to implement the method according to any one of claims 1 to 8.

Images