RPC Method Routing

Intelligent RPC Method Routing

Backpac's intelligent RPC method routing system streamlines the process of directing RPC requests to the right provider. This system ensures that all RPC calls are routed efficiently based on two key components:

1. Listener Rules: Configurable rules that direct traffic based on RPC methods, source IP, or HTTP headers.
2. Provider Capability Check: A secondary validation to ensure the selected provider supports the requested RPC method.

With these mechanisms, Backpac simplifies blockchain interactions by enabling a single RPC endpoint to handle diverse methods across various providers.

---

How RPC Method Routing Works

1. Listener Rules

Listener rules are applied first to determine how incoming requests are routed. These rules can filter traffic based on:

• RPC Method: Matches requests with specific method names (e.g., qn_fetchNFTCollectionDetails).
• Source IP: Directs traffic based on the client's IP address.
• HTTP Headers: Routes based on custom header values.

For example, a listener rule could route all eth_sendTransaction requests to a specific target group configured for Ethereum providers.

2. Provider Capability Check

After a listener rule is applied, Backpac performs a solid check to verify that the selected RPC provider supports the requested method. This ensures:

• Compatibility between the method and the provider.
• No unnecessary failures due to unsupported operations.

If the primary provider does not support the method, Backpac dynamically selects an alternate provider that meets the criteria.

---

Steps to Configure RPC Method Routing

Step 1: Set Up Listener Rules

1. Navigate to the Listener Rules section in the Backpac management console.
2. Create a new rule or modify an existing one:
   • Filter by RPC Method: Specify the method name to route.
   • Add Additional Filters (optional): Define Source IP or HTTP header conditions.
3. Assign the rule to a target group associated with the relevant blockchain and network.

Step 2: Add RPC Providers to Target Groups

1. Add RPC providers (e.g., QuickNode, Alchemy) to the appropriate target group.
2. Ensure the target group corresponds to the blockchain and network serviced by the providers.

Step 3: Verify Provider Capabilities

1. For each provider, confirm the RPC methods they support.
2. Use Backpac’s management console to review or update provider capabilities.

Step 4: Test Routing Behavior

1. Send a test request to your endpoint.
2. Verify that the request is routed to the correct provider based on the listener rule.
3. Confirm that the provider supports and successfully executes the requested RPC method.

---

Example: Routing qn_fetchNFTCollectionDetails

1. Listener Rule:
   • Match RPC Method: qn_fetchNFTCollectionDetails.
   • Route to the target group containing QuickNode.
2. Provider Capability Check:
   • Backpac validates that QuickNode supports qn_fetchNFTCollectionDetails.
   • If supported, the request is routed to QuickNode; otherwise, an alternate provider is selected.

By leveraging listener rules and capability checks, Backpac ensures seamless and efficient routing for all your blockchain RPC interactions.