Method and system for block chain transaction fee payment-for-another management

Abstract

The invention provides a method and a system for block chain transaction fee payment-for-another management. The method comprises the following steps: based on an intelligent contract, creating an account management contract and a fee payment party management contract; a fee payment party management contract is called, a fee payment party contract corresponding to the fee payment party is created, information of the fee payment party is maintained, and the fee payment party contract is used for managing token types and token amounts supported by the fee payment party; an account management contract is called, an intelligent account contract corresponding to the user is created, identity authentication data of the user is maintained, and the intelligent account contract is used for selecting a credit fee pay-for-another party of the user from the fee pay-for-another parties with the created fee pay-for-another party contract and managing access and authority of the fee pay-for-another party. According to the invention, unified management and operation of different compliant fee payment parties can be realized, respective management and operation of each fee payment party operation main body are avoided, and the management and operation efficiency and safety are improved.

Description

Technical Field

[0001] The present invention relates to the field of blockchain technology, and in particular to a technology for managing blockchain transaction fee payment. Background Art

[0002] Transactions in blockchain usually require the use of tokens to pay transaction fees. For example, transactions in Ethereum are usually paid with Ether. Generally, the user who initiates the transaction pays the fee himself, but it can also be paid by a fee payer (Paymaster) with authorized credit at the time of the transaction.

[0003] At present, the typical implementation method of transaction fee payment on the blockchain is to use a transaction fee payment contract created based on the account abstraction standard (such as ERC-4337). However, in the existing typical implementation method, the transaction fee payment contracts corresponding to different users may be maintained and managed by different third-party operators, which has low maintenance efficiency and high costs, and cannot achieve efficient integration and coordination. Moreover, different third-party operators and third-party operators and users may support different types of tokens, and different types of tokens need to be exchanged before transaction fees can be paid. There may even be a failure in transaction fee payment due to the inability to support the exchange of different types of tokens, resulting in a poor user experience. In addition, there is no unified management of different third-party operators, which poses a security risk. Summary of the invention

[0004] The purpose of the present invention is to provide a method and system for blockchain transaction fee payment management, which is applied to blockchains that support account abstraction standards, so as to at least partially solve the defects of existing blockchain transaction fee payment management mechanisms, such as low efficiency, poor user experience and security risks.

[0005] According to one aspect of the present invention, a method for managing blockchain transaction fee payment is provided, wherein the method comprises:

[0006] Based on smart contracts, create account management contracts and fee payer management contracts on the blockchain;

[0007] Calling the fee payer management contract, creating a fee payer contract corresponding to the fee payer, and maintaining the fee payer information, wherein the fee payer contract is used to manage the types of tokens supported by the fee payer and the amount of tokens;

[0008] The account management contract is called to create a smart account contract corresponding to the user, and to maintain the identity authentication data of the user, wherein the smart account contract is used to select a credit fee payer of the user from the fee payers of the created fee payer contract, and to manage access and permissions to the fee payer.

[0009] Optionally, the step of creating a fee payer contract corresponding to the fee payer includes:

[0010] Create a fee payer contract that complies with the ERC-4337 standard corresponding to the fee payer.

[0011] Optionally, the maintaining the information of the fee payer includes:

[0012] The fee payer is marked, enabled, disabled and / or the information of the fee payer is updated.

[0013] Optionally, the management of the token types supported by the fee payment agent includes:

[0014] Add, delete, enable and / or disable the types of tokens supported by the fee payer, and determine the exchange rules for different types of tokens.

[0015] Optionally, the management of the token amount includes:

[0016] Deposit and / or withdraw token amounts;

[0017] A token amount is allocated to a user to determine the user's available token amount.

[0018] Optionally, the step of creating a smart account contract corresponding to the user includes:

[0019] Create a smart account contract that complies with the ERC-4337 standard corresponding to the user.

[0020] Optionally, the method for managing blockchain transaction fee payment further includes:

[0021] Call the smart account contract corresponding to the user to initiate a transaction fee payment request, wherein the transaction fee payment request at least includes: the fee payer, the type of token to be paid, the estimated fee, and the signature;

[0022] According to the transaction fee payment request, call the fee payer contract corresponding to the fee payer and verify the payment conditions, wherein the payment conditions at least include: whether the signature verification is passed, whether the fee payer contract is enabled, and whether the required estimated fee is exceeded;

[0023] If the verification is successful, the fee payment is executed according to the type of token paid on behalf of the user and the estimated fee, and the user's smart account contract is updated and synchronized to the blockchain.

[0024] Optionally, the performing fee payment according to the type of the token for payment and the estimated fee includes:

[0025] If the token type of the token injected into the fee payer's contract is different from the token type of the payment, the fee payment will be executed after the token exchange is carried out according to the exchange rules of different token types and the estimated fee.

[0026] Optionally, the performing fee payment after exchanging tokens according to the exchange rules of different token types and the estimated fee includes:

[0027] Token exchange is carried out according to the exchange rules of different token types and the estimated fees;

[0028] Determine whether the amount of tokens after the exchange exceeds the available amount of tokens of the user. If not, execute fee payment.

[0029] According to another aspect of the present invention, a system for blockchain transaction fee payment management is provided, wherein the system comprises:

[0030] An account management contract created based on a smart contract on the blockchain, used to create a smart account contract corresponding to a user and maintain the identity authentication data of the user, wherein the smart account contract is used to add a credit fee payer of the user and manage access and permissions to the fee payer;

[0031] A fee payer management contract is created on the blockchain based on a smart contract, and is used to create a fee payer contract corresponding to the fee payer and maintain the information of the fee payer, wherein the fee payer contract is used to manage the types of tokens supported by the fee payer and the amount of tokens.

[0032] Compared with the prior art, the present invention provides a method and system for blockchain transaction fee payment management. The method includes: based on smart contracts, creating an account management contract and a fee payer management contract on the blockchain; calling the fee payer management contract, creating a fee payer contract corresponding to the fee payer, and maintaining the fee payer information, wherein the fee payer contract is used to manage the types of tokens supported by the fee payer and the amount of tokens; calling the account management contract, creating a smart account contract corresponding to the user, and maintaining the user's identity authentication data, wherein the smart account contract is used to select the user's credit fee payer from the fee payers for which the fee payer contract has been created, and manage the access and permissions of the fee payer. Through the constructed blockchain transaction fee payment management system, unified management and operation of different compliant fee payers can be achieved, avoiding the separate management and operation of each fee payer operating entity, and improving management and operation efficiency and security. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:

[0034] Figure 1 A schematic diagram of a method for managing blockchain transaction fee payment according to one aspect of the present invention is shown;

[0035] Figure 2 A schematic diagram of a system for managing blockchain transaction fee payment according to another aspect of the present invention is shown;

[0036] The same or similar reference numerals in the drawings represent the same or similar components. DETAILED DESCRIPTION

[0037] The present invention is further described in detail below in conjunction with the accompanying drawings.

[0038] In a typical configuration of each embodiment of the present invention, the execution subject of the method, each trusted party of the system and / or each module of the device includes one or more processors (CPU), input / output interface, network interface and memory.

[0039] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0040] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory media such as modulated data signals and carrier waves.

[0041] Blockchain is a decentralized distributed ledger that is tamper-proof, secure and reliable. It combines distributed storage, peer-to-peer transmission, consensus mechanism, cryptography and other technologies to record transactions and information through a growing data block chain to ensure data security and transparency. In order to motivate users to execute transactions, users who initiate transactions need to pay transaction fees (since the transaction price is determined by the supply and demand relationship in the blockchain, similar to the "oil price", it is usually called gas fee). Transaction fees are usually paid directly by users, but due to various reasons (for example, insufficient token balance of users, token types supported by users are not supported by the other party, etc.), there may be situations where users cannot pay transaction fees directly when initiating transactions, resulting in transaction failure. In order to improve the success rate of transactions and improve user experience, many existing blockchains support transaction fee payment. When users initiate transactions and need to pay transaction fees, a compliant third-party fee payer with authorized credit pays the transaction fees on their behalf. At present, the typical implementation method of transaction fee payment on blockchains that support account abstraction standards is to directly adopt a transaction fee payment contract created based on standards such as ERC-4337. However, in the existing typical implementation methods, the transaction fee payment contracts corresponding to different users may be maintained and managed by different third-party operators, which have low maintenance efficiency and high costs, and cannot achieve efficient integration and coordination. Moreover, different third-party operators and third-party operators and users may support different types of tokens, and different types of tokens need to be exchanged before transaction fees can be paid. There may even be a failure in transaction fee payment due to the inability to support the exchange of different types of tokens, resulting in a poor user experience. In addition, there is no unified management of different third-party operators, which poses a security risk.

[0042] The present invention provides a method and system for blockchain transaction fee payment management. By constructing a blockchain transaction fee payment management system based on smart contracts, users with transaction fee payment needs and compliant fee payers are included in the system to implement the transaction fee payment function, which can at least partially solve the defects or deficiencies in the above-mentioned prior art.

[0043] In order to further illustrate the technical means adopted by the present invention and the effects achieved, the technical scheme of the present invention is clearly and completely described below in conjunction with the accompanying drawings and various embodiments.

[0044] Figure 1 A schematic diagram of a method for managing blockchain transaction fee payment according to one aspect of the present invention is shown, wherein the method of one embodiment includes:

[0045] S101 creates account management contracts and fee payer management contracts on the blockchain based on smart contracts;

[0046] S102 calls the fee payer management contract, creates a fee payer contract corresponding to the fee payer, and maintains the information of the fee payer, wherein the fee payer contract is used to manage the types of tokens supported by the fee payer and the amount of tokens;

[0047] S103 calls the account management contract, creates a smart account contract corresponding to the user, and maintains the identity authentication data of the user, wherein the smart account contract is used to select the user's trusted fee payer from the fee payers of the fee payer contract that has been created, and to manage access and permissions to the fee payer.

[0048] The method of this embodiment may be implemented by a node of a blockchain supporting the account abstraction standard and / or a client interacting with the node. The node or client may be a computer device. The computer device includes, but is not limited to, a personal computer, a laptop, an industrial computer, a server, a network host, a single network server, etc. Here, the computer device is only an example, and other existing or future devices and / or resources that may appear should also be included in the scope of protection of the present application if they are applicable to the present application, and are hereby included by reference.

[0049] In this embodiment, in step S101, an account management contract of a smart contract based on the account abstraction standard is created on the blockchain to manage users who have transaction fee payment needs, and a fee payer management contract of a smart contract based on the account abstraction standard is created on the blockchain to manage compliant third-party fee payers that provide transaction fee payment services, thereby building a blockchain transaction fee payment management system including an account management contract and a fee payer management contract.

[0050] Continuing in this embodiment, after completing the construction of the blockchain transaction fee payment management system, in step S102, the fee payer management contract created in step S101 can be called, and for each compliant third-party fee payer that provides transaction fee payment services, a fee payer contract corresponding to the fee payer is created, and the fee payer information is maintained, wherein the fee payer contract is used to manage the types of tokens supported by the fee payer and the amount of tokens. The fee payer information may include: the name of the fee payer, tag information (such as unauthenticated status or authenticated status), status information (such as enabled status or disabled status), the contract subject and contract version of the fee payer contract corresponding to the fee payer, and other information.

[0051] Continuing with this embodiment, after completing the construction of the blockchain transaction fee payment management system, in step S103, the account management contract created in step S101 can be called to create a smart account contract corresponding to each user who has a transaction fee payment requirement, and maintain the user's identity authentication data (for example, the identity authentication data of the user authenticated by a third party), wherein the smart account contract is used to select the corresponding user's credit fee payer from the fee payers for which the fee payer contract has been created, as well as to manage access and permissions to the fee payer.

[0052] Through steps S101 to S103 of the above embodiment, a system for blockchain transaction fee payment management can be constructed, and different compliant third-party fee payers can be included in the system to achieve unified management, which can not only reduce management costs and improve management efficiency, but also improve security.

[0053] Optionally, in step S102, the creating a fee payer contract corresponding to the fee payer includes:

[0054] Create a fee payer contract that complies with the ERC-4337 standard corresponding to the fee payer.

[0055] ERC-4337 is an "Account Abstraction (AA)" standard that can unlock the functionality of smart contract wallets in the Ethereum blockchain or EVM (Ethereum Virtual Machine)-compatible blockchains. In this optional embodiment, a compliant third-party fee payer who wants to provide transaction fee payment services on the blockchain can create a fee payer contract that complies with the ERC-4337 standard for the fee payer, providing the fee payer with standard payment-related functions.

[0056] Optionally, in step S102, maintaining the information of the fee payer includes:

[0057] The fee payer is marked, enabled, disabled and / or the information of the fee payer is updated.

[0058] Among them, the fee payer's information can be maintained by calling the fee payer management contract, and the fee payer can be marked. If the fee payer contract corresponding to the fee payer has not been authenticated, the fee payer can be marked as unauthenticated; if the fee payer contract corresponding to the fee payer has been authenticated, the fee payer can be marked as authenticated; the fee payer contract corresponding to the fee payer can be enabled or disabled; if the fee payer's information has changed, the fee payer's information can also be updated.

[0059] Optionally, in step S102, the management of the token types supported by the fee payment agent includes:

[0060] Add, delete, enable and / or disable the types of tokens supported by the fee payer, and determine the exchange rules for different types of tokens.

[0061] Among them, for the transaction fee payment service provided by the corresponding fee payer, if the fee payer has added a new type of supported token, the newly added token type can be added to the fee payer contract corresponding to the fee payer; if the fee payer no longer supports one or some token types, the newly added token type can be deleted in the fee payer contract corresponding to the fee payer; further, for the supported token types, they need to be enabled before they can be used for the user's transaction fee payment; for the enabled token types, they can also be disabled. In addition, the exchange rules of different token types can also be determined in the fee payer contract corresponding to the fee payer, supporting the exchange of different types of tokens. When the token types of the two parties to the transaction (for example, the user and the fee payer, or two different fee payers) are different, the exchange between different tokens can be carried out according to the exchange rules of the corresponding token types to ensure the normal completion of the transaction fee payment and avoid the failure of the transaction fee payment. The convenience and success rate of transactions are improved, and the user experience is better.

[0062] Optionally, in step S102, the management of the token amount includes:

[0063] Deposit and / or withdraw token amounts;

[0064] A token amount is allocated to a user to determine the user's available token amount.

[0065] Among them, the fee payer contract corresponding to the fee payer can be used to inject tokens into the fee payer's transaction fee payment token pool and / or withdraw tokens from the fee payer's transaction fee payment token pool. The token amount in the fee payer's transaction fee payment token pool can also be allocated to each user it serves to determine the user's available token amount.

[0066] An exemplary solidity code (fee payer management contract and fee payer contract) of the above embodiment and / or optional embodiment applicable to an EVM-compatible blockchain is as follows:

[0067] contract PaymasterManager{

[0068] struct PaymasterInfo{

[0069] address paymasterAddress;

[0070] bool isActive;

[0071] string description;

[0072] }

[0073] mapping(address => PaymasterInfo) public paymasters;

[0074] address[] public paymasterList;

[0075] / / Add a new Paymaster (fee payer)

[0076] function addPaymaster(address _paymasterAddress, string calldata _description) external {

[0077] require(paymasters[_paymasterAddress].paymasterAddress == address(0), "Paymaster already exists.");

[0078] paymasters[_paymasterAddress] =

[0079] PaymasterInfo(_paymasterAddress, true, _description);

[0080] paymasterList.push(_paymasterAddress);

[0081] emit PaymasterAdded(_paymasterAddress, _description);

[0082] }

[0083] / / Update the status of the Paymaster (fee payer)

[0084] function updatePaymasterStatus(address _paymasterAddress, bool _isActive) external {

[0085] require(paymasters[_paymasterAddress].paymasterAddress != address(0), "Paymaster does not exist.");

[0086] paymasters[_paymasterAddress].isActive = _isActive;

[0087] emit PaymasterStatusUpdated(_paymasterAddress, _isActive);

[0088] }

[0089] }

[0090] contract TokenPaymaster {

[0091] mapping(address => bool) public supportedTokens;

[0092] / / Add supported tokens

[0093] function addToken(address _token) external {

[0094] require(!supportedTokens[_token], "Token already

[0095] supported.");

[0096] supportedTokens[_token] = true;

[0097] }

[0098] / / Remove supported tokens

[0099] function removeToken(address _token) external {

[0100] require(supportedTokens[_token],"Token is not supported.");

[0101] supportedTokens[_token]=false;

[0102] }

[0103] / / Token exchange

[0104] function swapToken(address_fromToken,address_toToken,uint256_amount)external{

[0105]

[0106] Optionally, in step S103, creating a smart account contract corresponding to the user includes:

[0107] Create a smart account contract that complies with the ERC-4337 standard corresponding to the user.

[0108] In this optional embodiment, to meet the user's transaction fee payment needs, a smart account contract that complies with the ERC-4337 standard can be created for the user to provide the user with smart account functions, and related functions can be expanded in the ERC-4337 standard, for example, adding compliant fee payers that can provide transaction fee payment services for the user, or deleting added fee payers, as well as access management to the fee payers (for example, managing the whitelist and / or blacklist of fee payers accessible to the user).

[0109] An exemplary solidity code (related to smart account contracts) of the above embodiment and / or optional embodiment applicable to an EVM-compatible blockchain is as follows:

[0110]

[0111] function revokePaymaster(address_paymaster)external{

[0112] require(msg.sender==owner,"Only owner can manage Paymasters.");

[0113] trustedPaymasters[_paymaster]=false;

[0114] }

[0115] }

[0116] Optionally, the method for managing blockchain transaction fee payment further includes:

[0117] S104 calls the smart account contract corresponding to the user to initiate a transaction fee payment request, wherein the transaction fee payment request at least includes: the fee payer, the type of token to be paid, the estimated fee, and the signature;

[0118] S105: calling the fee payer contract corresponding to the fee payer according to the transaction fee payment request, and verifying the payment conditions, wherein the payment conditions at least include: whether the signature verification is passed, whether the fee payer contract is enabled, and whether the required estimated fee is exceeded;

[0119] If the verification is passed in S106, the fee payment is executed according to the type of token for payment and the estimated fee, and the user's smart account contract is updated and synchronized to the blockchain.

[0120] The blockchain transaction fee payment management system constructed based on the above embodiment and / or optional embodiment can execute the transaction fee payment of the user. In an optional embodiment, when the system obtains information that the user has initiated a blockchain transaction using transaction fee payment, in step S104, the smart account contract corresponding to the user can be called to initiate a transaction fee payment request, wherein the transaction fee payment request at least includes: the fee payer, the type of token to be paid, the estimated fee and the signature, wherein the fee payer can be an identifier corresponding to the operating entity of the fee payer, and the signature includes the user's identity authentication data.

[0121] Continuing in this optional embodiment, in step S105, the system may call the fee payer contract corresponding to the fee payer according to the fee payer in the transaction fee payment request submitted by the user, and verify the payment conditions according to the signature, estimated fee and the fee payer contract in the transaction fee payment request submitted by the user, wherein the payment conditions at least include: whether the signature verification is passed, whether the fee payer contract is enabled, and whether the required estimated fee is exceeded. If the signature verification fails, or the fee payer contract is not enabled, or the estimated fee exceeds the available token amount of the user, the verification fails.

[0122] Continuing in this optional embodiment, in step S106, if the verification is passed, the system can execute fee payment according to the type of token to be paid and the estimated fee in the transaction fee payment request submitted by the user, update the relevant information in the user's smart account contract, and synchronize the updated smart account contract of the user to the blockchain.

[0123] Optionally, in step S106, executing fee payment according to the type of the token for payment and the estimated fee includes:

[0124] If the token type of the token injected into the fee payer's contract is different from the token type of the payment, the fee payment will be executed after the token exchange is carried out according to the exchange rules of different token types and the estimated fee.

[0125] Among them, if the type of token paid in the transaction fee payment request submitted by the user is different from the type of token injected in the fee payer's contract, it is necessary to first exchange different types of tokens based on the type of token paid, the type of token corresponding to the available amount of the user's token injected, the exchange rules of the corresponding token type and the estimated fee, and then execute the fee payment.

[0126] Optionally, the performing fee payment after exchanging tokens according to the exchange rules of different token types and the estimated fee includes:

[0127] Token exchange is carried out according to the exchange rules of different token types and the estimated fees;

[0128] Determine whether the amount of tokens after the exchange exceeds the available amount of tokens of the user. If not, execute fee payment.

[0129] Among them, different types of tokens are exchanged first according to the type of tokens paid on behalf of others, the type of tokens corresponding to the available amount of tokens injected into the user, the exchange rules of the corresponding token types and the estimated fees, and then it is determined whether the amount of tokens after exchange has exceeded the available amount of tokens of the user in the contract of the fee payer. If not, the fee payment is executed.

[0130] Figure 2 A system for managing blockchain transaction fee payment according to another aspect of the present invention is shown, wherein the system of one embodiment includes:

[0131] An account management contract created based on a smart contract on the blockchain, used to create a smart account contract corresponding to a user and maintain the identity authentication data of the user, wherein the smart account contract is used to add a credit fee payer of the user and manage access and permissions to the fee payer;

[0132] A fee payer management contract is created on the blockchain based on a smart contract, and is used to create a fee payer contract corresponding to the fee payer and maintain the information of the fee payer, wherein the fee payer contract is used to manage the types of tokens supported by the fee payer and the amount of tokens.

[0133] In this embodiment, the system includes an account management contract for the user created on the blockchain based on a smart contract of the account abstraction standard and a fee payer management contract for a compliant third party that provides a transaction fee payment service.

[0134] In this embodiment, through the account management contract of the system, a smart account contract corresponding to the user can be created for the user who has the need to pay transaction fees, and the identity authentication data of the user can be maintained. The smart account contract corresponding to the user is used to add the user's credit fee payer and manage the access and permissions of the fee payer.

[0135] Continuing with this embodiment, through the fee payer management contract of the system, a fee payer contract corresponding to the fee payer that is a compliant third party providing transaction fee payment services can be created, and the fee payer's information can be maintained, wherein the fee payer contract is used to manage the types of tokens supported by the fee payer and the token amounts.

[0136] According to yet another aspect of the present invention, a computer-readable medium is provided, wherein the computer-readable medium stores computer-readable instructions, and the computer-readable instructions can be executed by a processor to implement the aforementioned method.

[0137] It should be noted that the various method embodiments of the present invention can be implemented in software and / or a combination of software and hardware. The software program involved in the present invention can be executed by a processor to implement the steps or functions of the above-mentioned various embodiments. Similarly, the software program of the present invention (including related data structures) can be stored in a computer-readable recording medium.

[0138] In addition, a part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. The program instruction for calling the method of the present invention may be stored in a fixed or removable recording medium, and / or transmitted through a data stream in a broadcast or other signal-bearing medium, and / or stored in a working memory of a computer device that operates according to the program instruction.

[0139] According to another aspect of the present invention, there is provided a device for managing blockchain transaction fee payment, the device comprising: a memory for storing computer program instructions and a processor for executing the program instructions, wherein when the computer program instructions are executed by the processor, the device is triggered to execute the methods and / or technical solutions of the aforementioned embodiments and / or optional embodiments.

[0140] It is obvious to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the present invention can be implemented in other specific forms without departing from the spirit or essential features of the present invention. Therefore, from any point of view, the embodiments should be regarded as exemplary and non-restrictive, and the scope of the present invention is defined by the appended claims rather than the above description, and it is intended that all changes falling within the meaning and scope of the equivalent elements of the claims are included in the present invention. Any figure mark in the claims should not be regarded as limiting the claims involved. In addition, it is obvious that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices stated in the device claim can also be implemented by one unit or device through software and / or hardware. The words first, second, etc. are used to indicate names, and do not indicate any particular order.

Claims

1. A method for managing blockchain transaction fee payment, characterized in that: The method comprises: Based on smart contracts, create account management contracts and fee payer management contracts on the blockchain; Calling the fee payer management contract, creating a fee payer contract corresponding to the fee payer, and maintaining the fee payer information, wherein the fee payer contract is used to manage the types of tokens supported by the fee payer and the amount of tokens; The account management contract is called to create a smart account contract corresponding to the user, and to maintain the identity authentication data of the user, wherein the smart account contract is used to select a credit fee payer of the user from the fee payers of the created fee payer contract, and to manage access and permissions to the fee payer.

2. The method according to claim 1, characterized in that The step of creating a fee payer contract corresponding to the fee payer includes: Create a fee payer contract that complies with the ERC-4337 standard corresponding to the fee payer.

3. The method according to claim 1, characterized in that The maintaining of the information of the party paying the fee includes: The fee payer is marked, enabled, disabled and / or the information of the fee payer is updated.

4. The method according to claim 1, characterized in that: Management of the types of tokens supported by the fee payer, including: Add, delete, enable and / or disable the types of tokens supported by the fee payer, and determine the exchange rules for different types of tokens.

5. The method according to claim 4, characterized in that The management of the token amount includes: Deposit and / or withdraw token amounts; A token amount is allocated to a user to determine the user's available token amount.

6. The method according to claim 1, characterized in that The step of creating a smart account contract corresponding to the user includes: Create a smart account contract that complies with the ERC-4337 standard corresponding to the user.

7. The method according to claim 5, characterized in that The method further comprises: Call the smart account contract corresponding to the user to initiate a transaction fee payment request, wherein the transaction fee payment request at least includes: the fee payer, the type of token to be paid, the estimated fee, and the signature; According to the transaction fee payment request, call the fee payer contract corresponding to the fee payer and verify the payment conditions, wherein the payment conditions at least include: whether the signature verification is passed, whether the fee payer contract is enabled, and whether the required estimated fee is exceeded; If the verification is successful, the fee payment is executed according to the type of token paid on behalf of the user and the estimated fee, and the user's smart account contract is updated and synchronized to the blockchain.

8. The method according to claim 7, characterized in that The performing fee payment according to the type of the token for payment and the estimated fee includes: If the token type of the token injected into the fee payer's contract is different from the token type of the payment, the fee payment will be executed after the token exchange is carried out according to the exchange rules of different token types and the estimated fee.

9. The method according to claim 8, characterized in that The execution of fee payment after the token exchange according to the exchange rules of different token types and the estimated fee includes: Token exchange is carried out according to the exchange rules of different token types and the estimated fees; Determine whether the amount of tokens after the exchange exceeds the available amount of tokens of the user. If not, execute fee payment.

10. A system for managing blockchain transaction fee payment, characterized in that: The system comprises: An account management contract created based on a smart contract on the blockchain is used to create a smart account contract corresponding to the user and maintain the identity authentication data of the user, wherein the smart account contract is used to add the user's credit fee payer and manage the access and authority of the fee payer; A fee payer management contract is created on the blockchain based on a smart contract, and is used to create a fee payer contract corresponding to the fee payer and maintain the information of the fee payer, wherein the fee payer contract is used to manage the types of tokens supported by the fee payer and the amount of tokens.

Images