Skip to main content

​
Environment Variables

All configuration is managed through environment variables in your .env file.

​
Quick Reference

​
Solana Configuration

​
string
default:"https://api.mainnet-beta.solana.com"
required
The Solana RPC endpoint URL for fetching blockchain data.Recommendations:
  • Use a dedicated RPC provider (e.g., Helius, QuickNode) for production
  • Public endpoints may be rate-limited
​
string
default:"wss://api.mainnet-beta.solana.com"
The Solana WebSocket endpoint URL for real-time updates.

​
Server Configuration

​
number
default:"3000"
The port on which the API server will listen.
​
string
default:"production"
The Node.js environment. Options: development, production, test

​
DEX Configuration

​
string
default:"Custom"
required
The DEX fork type identifier for CoinGecko compatibility.Supported Types:
  • Custom (recommended for Futarchy)
  • Uniswap V2, Uniswap V3, Uniswap V4
  • Raydium, Raydium CLMM
  • Orca
  • See full list
​
string
required
The factory program address that creates and manages DAO instances.
This must be a valid Solana program ID (PublicKey)
​
string
required
The router program address for executing swaps.

​
Protocol Configuration

​
number
default:"0.0025"
The protocol fee rate used for volume calculation. Default is 0.0025 (0.25%).Formula: volume = protocolFees / feeRate
​
string
Comma-separated list of DAO addresses to exclude from the API responses.

​
Supported DEX Forks

The following DEX fork types are supported for CoinGecko compatibility:
  • Uniswap V2, V3, V4
  • Raydium
  • Raydium CLMM
  • Orca
  • Balancer V2, V3
  • Curve
  • Algebra
  • Algebra Integral
  • Camelot V3
  • Cetus
  • Iziswap
  • Kyberswap
  • Kyberswap Elastic
  • Quickswap V3
  • Maverick V2
  • Solidly V2, V3
  • Traderjoe V2
  • Velocore V2
  • Ston.fi, Ston.fi V2
  • Surge Protocol
  • Dedust
  • Ekubo
  • Jediswap
  • And more…

​
Example Configuration

Here’s a complete example .env file:

​
Validation

The API validates all configuration on startup and will log warnings or errors for invalid settings.
On startup, check the logs for:
  • ✅ RPC connection successful
  • ✅ Factory address valid
  • ✅ Router address valid
  • ⚠️ Any configuration warnings

​
Production Recommendations

Use Premium RPC

Premium RPC providers offer higher rate limits and better reliability

Set Appropriate Fees

Ensure PROTOCOL_FEE_RATE matches your actual protocol fees

Monitor Performance

Use health check endpoint to monitor API status

Secure Your Endpoints

Consider adding authentication for production deployments