How to Connect Custom RPC Endpoints
Helius, Alchemy, Ankr & Beyond

Chainfolio's BYOK (Bring Your Own Key) architecture lets you use your own RPC infrastructure. This guide walks you through generating API keys from major providers and configuring them in Chainfolio—with zero server dependency.

Not your keys, not your crypto. But what about your RPC endpoints?

Using your own RPC endpoints gives you higher rate limits, better privacy, and censorship resistance. Chainfolio stores them exclusively in your browser's IndexedDB—never on a central server.

Why Use Custom RPC Endpoints?

Performance Benefits

  • Higher rate limits – Avoid public RPC throttling (e.g., 10‑100x more requests/day)
  • Lower latency – Choose endpoints geographically close to you
  • Priority access – Paid tiers get dedicated infrastructure
  • WebSocket support – Real‑time balance/transaction updates

Privacy & Sovereignty

  • No shared infrastructure – Your queries aren't mixed with thousands of others
  • Censorship resistance – Control which nodes you trust
  • Data ownership – RPC providers see only your requests, not your portfolio data
  • Vendor independence – Switch providers anytime without losing historical data

Step 1: Generate RPC API Keys

Helius (Solana)

  1. Visit helius.dev and sign up for a free account
  2. Navigate to Dashboard → API Keys and click "Create New Key"
  3. Select the Solana Mainnet network (free tier offers 24M requests/month)
  4. Copy your RPC URL (format: https://mainnet.helius-rpc.com/?api-key=your_key_here)
  5. Optional: Enable WebSocket for real‑time updates (separate URL provided)

Alchemy (Ethereum & Solana)

  1. Visit alchemy.com and create an account
  2. Click Create App and select Ethereum or Solana chain
  3. Choose Mainnet network (free tier: 300M compute units/month)
  4. Go to your app's details page and click View Key
  5. Copy the HTTPS URL (format: https://eth-mainnet.g.alchemy.com/v2/your_api_key)

Ankr (Multi‑Chain)

  1. Visit ankr.com and sign up
  2. Navigate to RPC Service → Endpoints
  3. Select Ethereum or Solana from the chain list
  4. Click Generate Endpoint and copy the URL
  5. Free tier includes 250K requests/day with rate‑limit headers

Other Providers & Self‑Hosted Nodes

Chainfolio works with any JSON‑RPC compatible endpoint. You can also use:

  • QuickNode – Premium multi‑chain RPC
  • Infura – Ethereum‑focused (requires API key)
  • GetBlock – 40+ blockchain support
  • Chainstack – Enterprise‑grade nodes
  • Your own node – Geth, Erigon, Solana validator

Step 2: Configure in Chainfolio

Onboarding Wizard Method

  1. Open Chainfolio – Navigate to the web app
  2. Start Onboarding – First‑time users see the setup wizard automatically
  3. Select "Custom RPC" – Choose "I have my own RPC endpoints"
  4. Paste Your URLs – Enter Solana and/or Ethereum RPC URLs
  5. Test Connection – Chainfolio validates latency and basic functionality
  6. Complete Setup – Your keys are now stored in browser's IndexedDB

Manual Configuration Method

If you skipped onboarding or want to add more endpoints later:

  1. Click the Settings gear icon (top‑right)
  2. Navigate to RPC Configuration → Add New Endpoint
  3. Select chain (Ethereum or Solana)
  4. Paste your RPC URL and give it a descriptive name (e.g., "Helius US‑West")
  5. Click Save & Test – Chainfolio validates and scores the endpoint
  6. Repeat for additional endpoints (Chainfolio supports multiple per chain for load balancing)

Step 3: Security & Best Practices

Key Management

  • Never share RPC URLs – Treat them like passwords
  • Use environment‑specific keys – Different keys for dev/prod if self‑hosting
  • Rotate keys periodically – Most providers allow multiple active keys
  • Monitor usage – Set up alerts in your RPC provider dashboard

Performance Optimization

  • Add multiple endpoints – Chainfolio automatically load‑balances
  • Choose geographic proximity – Lower latency = faster sync
  • Enable WebSockets – For real‑time balance updates
  • Monitor RPC health – Chainfolio tracks success rate and latency

Important Security Notes

  • Chainfolio never transmits your RPC keys to any server – They stay in your browser's IndexedDB
  • Clearing browser data deletes your RPC configuration – Backup your endpoints or use encrypted cloud sync
  • Browser extensions cannot access IndexedDB – Isolated storage prevents key theft
  • Consider using separate keys per device – If syncing across devices, each has its own encrypted backup

Troubleshooting Common Issues

"Failed to Connect" Error

Solution: Verify your RPC URL is correct and the API key is active. Check provider dashboard for usage limits.

Slow Sync Performance

Solution: Add additional endpoints for load balancing. Chainfolio's built-in load balancer automatically uses the fastest.

Rate Limit Errors (HTTP 429)

Solution: Upgrade your RPC plan or add multiple endpoints. Chainfolio automatically fails over to backup endpoints.

WebSocket Not Connecting

Solution: Ensure your RPC provider supports WebSockets and you've enabled it in their dashboard.

Advanced: Monitoring & Analytics

Chainfolio includes built‑in RPC monitoring. To view performance metrics:

  1. Navigate to Settings → RPC Configuration
  2. Click any endpoint to see detailed metrics:
    • Success Rate – Percentage of successful requests
    • Average Latency – Response time in milliseconds
    • Total Requests – Count of requests made
    • Error Breakdown – Types of failures (timeout, rate limit, etc.)
  3. Use this data to decide which endpoints to keep or replace

Take Control of Your Blockchain Infrastructure
With BYOK RPC Endpoints

No accounts. No servers. No telemetry. Just your device and your RPC endpoints.