RPC
A fast, stable RPC connection is essential for running Leap efficiently. Because Leap interacts directly with live blockchain data, node quality directly impacts speed, reliability, and transaction su
Node Access Overview
Leap offers two primary access options for Solana users, along with separate requirements for BNB traders.
🆓 Leap Standard (Free Plan)
Leap Standard users bring their own Solana RPC + gRPC connections. You can use any provider of your choice, but it must support:
High request throughput
Low latency (<150ms preferred)
gRPC connectivity for full functionality
If your node is slow or inconsistent, you may experience:
“Context deadline exceeded” or timeout errors
Failed transactions
Delays in token data or position updates
To prevent this, use a premium RPC service or upgrade to Leap Pro.
⚡ Leap Pro (Subscription Plan)
Leap Pro users gain access to Leap’s built-in in-house RPC + gRPC infrastructure — no setup required. Simply leave the RPC fields blank in settings, and the bot will auto-connect to the optimized Leap node network.
Benefits
Ultra-low latency execution, purpose-built for Leap
Automatic region balancing between multiple server locations
Fully managed and monitored for uptime and stability
Optimized transaction routing for 0-block copytrading
Current Node Regions
🇺🇸 Virginia (VA)
🇩🇪 Frankfurt (DE)
Leap Pro automatically selects the fastest location available, ensuring consistent sub-100ms response times for all tasks.
💛 BNB License Holders
BNB Module users must bring their own BNB RPC endpoint. Leap does not currently include a built-in BNB node.
Requirements:
Use a high-speed BNB RPC provider with low latency to your region
Ensure the provider supports WebSocket or HTTP-based event subscriptions (for real-time trading)
Reliable providers include Ankr, QuickNode, GetBlock, or any private BSC endpoint
Tip: If you experience delayed or failed transactions on BNB, it is almost always caused by a slow or overloaded RPC. Switching to a faster node resolves 99% of issues.
🧠 Best Practices
Always use a dedicated RPC, not a shared public endpoint.
For Leap Standard users, test node speed before starting multiple tasks.
If running multiple modes (Scraper, AFK, Copytrader), ensure your RPC can handle simultaneous calls.
Leap Pro users: leave the RPC fields blank to use the built-in network automatically.
BNB users: use a premium provider close to your geographic region for best performance.
💬 Troubleshooting
If you see errors such as:
context deadline exceededfailed to fetch account inforpc connection timeout
These are typically caused by slow or unreliable node responses. Try switching to a faster RPC, verify your gRPC connection, or contact Leap support via Discord.
📊 Summary
Leap Standard
Bring your own RPC + gRPC
Manual
User-defined
Works with any Solana provider
Leap Pro
Built-in in-house RPC + gRPC
Automatic (leave blank)
🇺🇸 Virginia · 🇩🇪 Frankfurt
Optimized for Leap, no setup
BNB License
Bring your own BNB RPC
Manual
User-defined
Required for all BNB trades
Leap’s node infrastructure ensures that Leap Pro users benefit from the fastest Solana execution available, while Leap Standard and BNB License users retain full flexibility to use their own nodes and configurations.
Last updated