IP Library Granted Patent US 12,423,697
Granted Patent B1
US 12,423,697 · App. 19/086,741 · Granted Sep 23, 2025

Decentralized systems and methods for response generation to API calls

Inventors: Sergej Kunz (Stuttgart, DE); Anton Bukov (Amstelveen, NL)
Assignee: 1inch Limited
G06Q20/401G06F9/547G06Q20/389
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,423,697
App. No.
19/086,741
Granted
Sep 23, 2025
Kind
B1
Abstract

The present disclosure provides a system for decentralized handling of application programming interface (API) calls. The system comprises a peer-to-peer network including a plurality of nodes, each node being a user device, a relayer, or a resolver. Each node includes at least one hardware processor and at least one non-transitory memory storing instructions. When executed, the instructions cause the node to receive an encrypted API request from a user device, forward the encrypted API request to at least one resolver node, process the API request to generate an API response, and transmit the API response back to the user device. The peer-to-peer network may comprise a mesh network and utilize a Remote Procedure Call (RPC) architectural style. The system enables decentralized management of API calls without relying on centralized servers.

Claims (60)

1. A system for generating a decentralized response to an application programming interface (API) call, the system comprising:

a blockchain network comprising a relayer registration smart contract; and

a peer-to-peer network comprising a plurality of nodes, wherein each of the plurality of nodes comprises a relayer or a resolver, each node comprising:

at least one hardware processor; and

at least one non-transitory memory storing instructions, which, when executed by the at least one hardware processor, cause the node to:

for at least one relayer:

register on the blockchain network using the relayer registration smart contract;

receive, from a user via a decentralized application, an encrypted user request on the peer-to-peer network, the encrypted user request comprising an encrypted format of the API call that is generated using a public key of at least one resolver selected through the decentralized application;

validate a payment status of the decentralized application;

transmit, to the at least one resolver, the encrypted user request without decrypting the encrypted format of the API call of the encrypted user request;

receive, from the at least one resolver, accessed data; and

transmit the accessed data to the decentralized application; and

for the at least one resolver:

receive, from the at least one relayer, the encrypted user request comprising the encrypted format of the API call;

decrypt the encrypted user request using a private key;

process the API call to obtain a result;

compare the obtained result to a second result obtained by at least one other resolver to reach a validation consensus;

upon reaching the validation consensus, execute the API call to generate a response to the encrypted user request; and

transmit, to the at least one relayer, the response to the encrypted user request.

2. The system of claim 1 , wherein the peer-to-peer network comprises a mesh network.

3. The system of claim 1 , wherein the peer-to-peer network comprises a Remote Procedure Call (RPC) architectural style.

4. The system of claim 1 , wherein the relayer registration smart contract comprises a decentralized autonomous organization (DAO) smart contract.

5. The system of claim 1 , wherein the encrypted user request is encrypted using asymmetric cryptography.

6. The system of claim 1 , wherein reaching a validation consensus comprises using a flooding consensus algorithm.

7. A computer-implemented method for generation of a decentralized response to an application programming interface (API) call, the computer-implemented method comprising:

registering at least one relayer of a plurality of relayers of a peer-to-peer network on a blockchain network using a relayer registration smart contract, wherein the peer-to-peer network comprises a plurality of nodes comprising the plurality of relayers and a plurality of resolvers;

receiving, from a user via a decentralized application by the at least one relayer, an encrypted user request on the peer-to-peer network, the encrypted user request comprising an encrypted format of the API call that is generated using a public key of at least one resolver selected through the decentralized application;

validating, by the at least one relayer, a payment status of the decentralized application;

transmitting, by the at least one relayer to at least one resolver of the plurality of resolvers, the encrypted user request without decrypting the encrypted format of the API call of the encrypted user request;

receiving, from the at least one relayer by the at least one resolver, the encrypted user request comprising the encrypted format of the API call;

decrypting, by the at least one resolver, the encrypted user request using a private key;

processing, by the at least one resolver, the API call to obtain a result;

comparing, by the at least one resolver, the obtained result to a second result obtained by at least one other resolver to reach a validation consensus;

upon reaching the validation consensus, executing, by the at least one resolver, the API call to generate a response to the encrypted user request;

transmitting, by the at least one resolver to the at least one relayer, the response to the encrypted user request; and

transmitting the response to the encrypted user request to the decentralized application, wherein the at least one relayer and the at least one resolver comprise a processor and a memory.

8. The method of claim 7 , wherein the peer-to-peer network comprises a mesh network.

9. The method of claim 7 , wherein the peer-to-peer network comprises a Remote Procedure Call (RPC) architectural style.

10. The method of claim 7 , wherein the relayer registration smart contract comprises a decentralized autonomous organization (DAO) smart contract.

11. The method of claim 7 , wherein the encrypted user request is encrypted using asymmetric cryptography.

12. The method of claim 7 , wherein reaching a validation consensus comprises using a flooding consensus algorithm.

13. The method of claim 7 , wherein executing the API call comprises executing a payment smart contract.

14. A non-transitory computer readable medium having stored thereon instructions for causing a processing circuitry to execute a process, the process comprising:

registering at least one relayer of a plurality of relayers of a peer-to-peer network on a blockchain network using a relayer registration smart contract, wherein the peer-to-peer network comprises a plurality of nodes comprising the plurality of relayers and a plurality of resolvers;

receiving, from a user via a decentralized application by the at least one relayer, an encrypted user request on the peer-to-peer network, the encrypted user request comprising an encrypted format of an application programming interface (API) call that is generated using a public key of at least one resolver selected through the decentralized application;

validating, by the at least one relayer, a payment status of the decentralized application;

transmitting, by the at least one relayer to at least one resolver of the plurality of resolvers, the encrypted user request without decrypting the encrypted format of the API call of the encrypted user request;

receiving, from the at least one relayer by the at least one resolver, the encrypted user request comprising the encrypted format of the API call;

decrypting, by the at least one resolver, the encrypted user request using a private key;

processing, by the at least one resolver, the API call to obtain a result;

comparing, by the at least one resolver, the obtained result to a second result obtained by at least one other resolver to reach a validation consensus;

upon reaching the validation consensus, executing, by the at least one resolver, the API call to generate a response to the encrypted user request;

transmitting, by the at least one resolver to the at least one relayer, the response to the encrypted user request; and

transmitting the response to the encrypted user request to the decentralized application, wherein the at least one relayer and the at least one resolver comprise a processor and a memory.

15. The non-transitory computer readable medium of claim 14 , wherein the peer-to-peer network comprises a mesh network.

16. The non-transitory computer readable medium of claim 14 , wherein the peer-to-peer network comprises a Remote Procedure Call (RPC) architectural style.

17. The non-transitory computer readable medium of claim 14 , wherein the relayer registration smart contract comprises a decentralized autonomous organization (DAO) smart contract.

18. The non-transitory computer readable medium of claim 14 , wherein the encrypted user request is encrypted using asymmetric cryptography.

19. The non-transitory computer readable medium of claim 14 , wherein reaching a validation consensus comprises using a flooding consensus algorithm.

20. The non-transitory computer readable medium of claim 14 , wherein executing the API call comprises executing a payment smart contract.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 7, 2026
From: 1INCH LIMITED
To: DEGENSOFT LTD.
Reel/Frame 073393/0905 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 14, 2025
From: KUNZ, SERGEJ; BUKOV, ANTON
To: 1INCH LIMITED
Reel/Frame 070829/0533 →
Continuity (2)
Continuation 19079026 · Mar 13, 2025
Provisional Application 63566109 · Mar 15, 2024
References Cited (47)
US 6422373B1 · Yellop et al. · 2002 [cited by applicant]
US 11123456B2 · Masinaei et al. · 2021 [cited by applicant]
US 11234567B2 · Thorne et al. · 2022 [cited by applicant]
US 11456789B2 · Hou et al. · 2022 [cited by applicant]
US 11544786B2 · Diamond · 2023 [cited by applicant]
US 11567890B2 · Bussing et al. · 2023 [cited by applicant]
US 11678901B2 · Scoggins et al. · 2023 [cited by applicant]
US 11789012B2 · Janes et al. · 2023 [cited by applicant]
US 11890123B2 · Boone et al. · 2024 [cited by applicant]
US 12099978B2 · Bukov et al. · 2024 [cited by applicant]
US 12277536B2 · Dominique et al. · 2025 [cited by applicant]
US 20030200439A1 · Moskowitz · 2003 [cited by applicant]
US 20080264043A1 · Kawakita et al. · 2008 [cited by applicant]
US 20100235277A1 · Van et al. · 2010 [cited by applicant]
US 20130157711A1 · Lee et al. · 2013 [cited by applicant]
US 20140040114A1 · Baumgart et al. · 2014 [cited by applicant]
US 20140289163A1 · Michaud et al. · 2014 [cited by applicant]
US 20180352033A1 · Pacella · 2018 [cited by examiner]
US 20190349261A1 · Smith · 2019 [cited by examiner]
US 20190373521A1 · Crawford · 2019 [cited by examiner]
US 20190379595A1 · Ur et al. · 2019 [cited by applicant]
US 20190385156A1 · Liu · 2019 [cited by applicant]
US 20190392511A1 · Mahajan et al. · 2019 [cited by applicant]
US 20200082025A1 · Zhou et al. · 2020 [cited by applicant]
US 20200104835A1 · Day et al. · 2020 [cited by applicant]
US 20200119925A1 · Wang · 2020 [cited by applicant]
US 20210035246A1 · Schouppe et al. · 2021 [cited by applicant]
US 20210073913A1 · Ingargiola · 2021 [cited by applicant]
US 20210352142A1 · Jayaram et al. · 2021 [cited by applicant]
US 20220126438A1 · Cristache · 2022 [cited by applicant]
US 20230198886A1 · Ur et al. · 2023 [cited by applicant]
US 20230206329A1 · Cella et al. · 2023 [cited by applicant]
US 20230267456A1 · Garner et al. · 2023 [cited by applicant]
US 20230385822A1 · Shanmugam et al. · 2023 [cited by applicant]
US 20240273486A1 · Bukov et al. · 2024 [cited by applicant]
US 20240273487A1 · Bukov et al. · 2024 [cited by applicant]
US 20240420227A1 · Bukov et al. · 2024 [cited by applicant]
US 20240428209A1 · Bukov et al. · 2024 [cited by applicant]
US 20250165937A1 · Bukov et al. · 2025 [cited by applicant]
Anonymous: “1inch.io”, Jan. 4, 2023, XP093135078, Retrieved from the Internet on Feb. 26, 2024: URL:http://1inch.io. [cited by applicant]
Benligiray et al., “Decentralized APIs for Web 3.0”, api3.org, Jan. 9, 2024, pp. 1-40. [cited by applicant]
Breidenbach et al., “Chainlink 2.0: Next Steps in the Evolution of Decentralized Oracle Networks”, Retrieved from the Internet: URL:https://research.chain.link/whitepaper-v2.pdf, Apr. 15, 2021, pp. 1-136. [cited by applicant]
Fang Lucius et al.: “How to DEFI (Advanced)”, May 31, 2021, pp. 1-290, XP055960691, ISBN: 9798530318443, Retrieved from the Internet on Feb. 27, 2024: URL:https://cp0x.com/applications/core/interface/file/attachment.php… [cited by applicant]
International Search Report and Written Opinion received for PCT Patent Application No. PCT/IB25/052695, mailed on May 27, 2025, 15 pages. [cited by applicant]
Patent Application as filed of U.S. Appl. No. 18/408,376, filed Jan. 9, 2024, 81 pages. [cited by applicant]
Xu, J. et al., “SoK: Decentralized Exchanges (DEX) with Automated Market Maker (AMM) protocols” Arxiv.Org, Cornell University Library, Apr. 19, 2021, XP081930404. [cited by applicant]
Xue, Y. et al., “Invited Paper: Fault-tolerant and Expressive Cross-Chain Swaps”, arxiv.org, Cornell University Library, Nov. 1, 2022, XP091357638. [cited by applicant]
Cited By (2)
US 12,574,234 US 12,700,033