Decentralized API Call Routing via Peer-to-Peer Resolver Nodes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing API architectures rely on centralized servers, leading to potential trust issues and single points of failure, which undermines the decentralization of decentralized applications (dApps).
Innovation Solution
A peer-to-peer network of nodes, including relayers and resolvers, handles API calls using a blockchain-based decentralized system with encryption, consensus mechanisms, and off-chain payment channels to ensure secure, decentralized data exchange.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a centralized server is used to handle API calls, then the system architecture is simple and easy to manage, but it creates a single point of failure and undermines decentralization
Solution Approach 1:
The patent segments the centralized API server functionality into multiple distributed nodes across a peer-to-peer network. Each node can independently handle API calls, eliminating the single point of failure. The segmentation is achieved by distributing the API handling capabilities across multiple participants in the decentralized network, allowing the system to maintain functionality even if individual nodes fail.
Solution Approach 2:
The patent introduces smart contracts as intermediaries that mediate between clients and the decentralized API network. These smart contracts manage the routing, authentication, and coordination of API calls across the distributed nodes, providing a layer of abstraction that simplifies the complexity of the underlying decentralized architecture while maintaining reliability through decentralization.
2Reliability
If a decentralized peer-to-peer network is used to handle API calls, then reliability and decentralization are improved, but system complexity increases
Solution Approach 1:
The patent creates universal smart contract templates that can handle multiple types of API calls and interactions across different decentralized applications. These multi-functional smart contracts reduce complexity by providing standardized, reusable patterns for common API operations, eliminating the need to create custom decentralized handling logic for each application.
Solution Approach 2:
The patent changes the operational parameters of the decentralized network by implementing standardized communication protocols and data formats for API interactions. By establishing fixed parameters for request/response structures, authentication mechanisms, and node coordination, the system reduces the complexity of implementing and maintaining the decentralized peer-to-peer network.
3Reliability
If encryption is implemented in the decentralized API system, then security is improved, but processing time and computational overhead increase
Solution Approach 1:
The patent implements preliminary action by establishing encryption keys and authentication credentials before API calls are made. Smart contracts pre-validate user identities and set up encrypted communication channels in advance, so that when actual API calls occur, the encryption and authentication processes are already in place, minimizing processing time delays.
Solution Approach 2:
The patent uses copying by creating and distributing public keys and encryption templates in advance across the decentralized network. Instead of performing complex cryptographic operations for every API call, the system uses pre-copied encryption parameters and standardized cryptographic patterns that can be quickly applied, reducing computational overhead while maintaining security.
Data Source
AI summary
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.