Separation of native and non-native tokens in blockchain transactions

JP2026520740APending Publication Date: 2026-06-24サークル インターネット フィナンシャル リミテッド
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
サークル インターネット フィナンシャル リミテッド
Filing Date
2024-06-08
Publication Date
2026-06-24

Smart Images

  • Figure 2026520740000001_ABST
    Figure 2026520740000001_ABST
Patent Text Reader

Abstract

Several aspects of this disclosure provide techniques and apparatus for efficiently processing transactions on a blockchain. An exemplary method generally involves a relay service receiving a request to execute a transaction on the blockchain. Generally, this request includes a request to transfer a certain amount of tokens of type 1 from a sender wallet to a recipient wallet identified in the request, and incurring transaction overhead on the blockchain with tokens of type 2. This request is modified based on the amount of tokens of type 1, the transaction overhead of tokens of type 2, and a policy defining the source from which the transaction overhead should be obtained. The transaction is executed on the blockchain based on the modified request without transferring tokens of type 2 from the sender wallet to satisfy the transaction overhead.
Need to check novelty before this filing date? Find Prior Art

Claims

1. In a relay service, receiving a request to execute a transaction on the blockchain, the request including a request to transfer a certain amount of a first type of token from a sender wallet to a recipient wallet identified in the request, and generating transaction overhead on the blockchain with a second type of token, Modifying the request based on the amount of the first type of token, the transaction overhead of the second type of token, and a policy defining the source, wherein the transaction overhead is obtained from the source; To satisfy the transaction overhead, the transaction is executed on the blockchain based on the modified request without transferring the second type of token from the sender wallet. Computer implementation methods, including those mentioned above.

2. The method according to claim 1, wherein modifying the request includes modifying the amount of the first type of tokens to be transferred on the blockchain based on the amount of the first type of tokens determined to be equal to the transaction overhead of the second type of tokens.

3. Executing the aforementioned transaction means Identifying a first source, wherein the amount of the first type of token is obtained from the first source. Identifying a second source from which an amount of the first type of tokens, determined to be equal to the transaction overhead of the second type of tokens, is obtained. Executing the transaction on the blockchain based on the identified first source and the identified second source. The method according to claim 1, including the method described in claim 1.

4. The method according to claim 3, wherein the second source includes a third-party source that is not associated with either the sender wallet or the receiver wallet.

5. Incrementing a sequential cumulative amount of the first type tokens used to satisfy the transaction overhead on the blockchain of the parties associated with the recipient wallet, based on the amount of the first type tokens determined to be equal to the transaction overhead of the second type tokens; In accordance with the aforementioned policy, the difference between the sequential cumulative amount and the amount borne by the third-party source is determined, The method according to claim 4, further comprising transferring the difference from a wallet associated with the recipient to a wallet associated with the third-party source.

6. The method according to claim 3, wherein the second source includes the same source as the first source.

7. Executing the transaction on the aforementioned blockchain means Transferring the aforementioned quantity of the first type of token from the sender wallet to the receiver wallet, Transferring an amount of the first type token determined to be equal to the transaction overhead of the second type token from the sender wallet to a third-party wallet associated with a third-party source that is neither the sender wallet nor the receiver wallet, The method according to claim 6, further comprising using a certain amount of the second type of token from the third-party wallet to bear the transaction overhead.

8. The method according to claim 1, wherein the policy specifies the percentage of the transaction overhead incurred by transferring the second type of token from the recipient wallet.

9. The method according to claim 1, wherein the policy specifies the maximum cumulative amount of transaction overhead to be incurred over a defined period by transferring the second type of token from the recipient wallet.

10. The method according to claim 1, wherein the policy includes a policy defined for a party relating to the recipient wallet.

11. Memory containing executable instructions, A processor configured to execute the aforementioned executable instructions and A system comprising, wherein the executable instruction is provided to the system, In a relay service, receiving a request to execute a transaction on the blockchain, the request including a request to transfer a certain amount of a first type of token from a sender wallet to a recipient wallet identified in the request, and generating transaction overhead on the blockchain with a second type of token, Modifying the request based on the amount of the first type of token, the transaction overhead of the second type of token, and a policy defining the source, wherein the transaction overhead is obtained from the source; To satisfy the transaction overhead, the transaction is executed on the blockchain based on the modified request without transferring the second type of token from the sender wallet, system.

12. The system according to claim 11, wherein the processor is configured to cause the system to modify the amount of the first type of tokens to be transferred on the blockchain based on the amount of the first type of tokens determined to be equal to the transaction overhead of the second type of tokens.

13. To execute the aforementioned transaction, the processor provides the system with the following: Identifying a first source, wherein the amount of the first type of token is obtained from the first source. Identifying a second source from which an amount of the first type of tokens, determined to be equal to the transaction overhead of the second type of tokens, is obtained. The system according to claim 11, configured to perform the transaction on the blockchain based on the identified first source and the identified second source.

14. The second source includes a third-party source that is not associated with either the sender wallet or the receiver wallet. The aforementioned processor is configured in the system. Incrementing a sequential cumulative amount of the first type tokens used to satisfy the transaction overhead on the blockchain of the parties associated with the recipient wallet, based on the amount of the first type tokens determined to be equal to the transaction overhead of the second type tokens; In accordance with the aforementioned policy, the difference between the sequential cumulative amount and the amount borne by the third-party source is determined, The system according to claim 13, further configured to transfer the difference from a wallet associated with the recipient to a wallet associated with the third-party source.

15. The system according to claim 13, wherein the second source includes the same source as the first source.

16. In order to execute the transaction on the blockchain, the processor in the system Transferring the aforementioned quantity of the first type of token from the sender wallet to the receiver wallet, Transferring an amount of the first type token determined to be equal to the transaction overhead of the second type token from the sender wallet to a third-party wallet associated with a third-party source that is neither the sender wallet nor the receiver wallet, The system according to claim 15, configured to use a certain amount of the second type of token from the third-party wallet to bear the transaction overhead.

17. The system according to claim 11, wherein the policy specifies the percentage of the transaction overhead incurred by transferring the second type of token from the recipient wallet.

18. The system according to claim 11, wherein the policy specifies the maximum cumulative amount of transaction overhead to be incurred over a defined period by transferring the second type of token from the recipient wallet.

19. The system according to claim 11, wherein the policy includes a policy defined for a party relating to the recipient wallet.

20. A computer-readable medium storing instructions, wherein the instructions, when executed by a processor, In a relay service, receiving a request to execute a transaction on the blockchain, the request including a request to transfer a certain amount of a first type of token from a sender wallet to a recipient wallet identified in the request, and generating transaction overhead on the blockchain with a second type of token, Modifying the request based on the amount of the first type of token, the transaction overhead of the second type of token, and a policy defining the source, wherein the transaction overhead is obtained from the source; To satisfy the transaction overhead, perform an operation that includes executing the transaction on the blockchain based on the modified request without transferring the second type of token from the sender wallet. Computer-readable media.