Tetron.fun - Private RPC Nodes

Configuration and usage of Tetron's RPC node endpoints for blockchain data access

RPC Nodes

TetronFun provides dedicated RPC (Remote Procedure Call) node endpoints to facilitate reliable, low‑latency access to blockchain data. These endpoints support transaction submission, state queries, and event subscriptions across supported networks.

1. Supported Networks & Endpoints

Network	HTTP Endpoint	WebSocket Endpoint
Ethereum	https://rpc.tetronfun.com/eth	wss://rpc.tetronfun.com/eth/ws
Binance	https://rpc.tetronfun.com/bsc	wss://rpc.tetronfun.com/bsc/ws
Polygon	https://rpc.tetronfun.com/polygon	wss://rpc.tetronfun.com/polygon/ws
Solana	https://rpc.tetronfun.com/solana	N/A
Custom	Contact support for private or enterprise nodes	N/A

2. Authentication & Access

All RPC endpoints require inclusion of your API key via HTTP headers:

GET /eth HTTP/1.1
Host: rpc.tetronfun.com
Authorization: Bearer <YOUR_API_KEY>
Content-Type: application/json
WebSocket connections must send an authentication payload immediately after connecting:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "auth",
  "params": {
    "apiKey": "<YOUR_API_KEY>"
  }
}
3. Common RPC Methods

eth_blockNumber
Retrieve the latest block number.
eth_getBlockByNumber
Fetch block details by block height (latest, earliest, or hex value).
eth_call
Execute a read‑only contract call.
eth_sendRawTransaction
Submit a signed transaction payload.
eth_subscribe (WebSocket only)
Subscribe to new blocks, logs, or pending transactions.
4. Usage Examples

HTTP (cURL)
curl -X POST https://rpc.tetronfun.com/eth \
  -H "Authorization: Bearer $TETRONFUN_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{
    "jsonrpc":"2.0",
    "method":"eth_blockNumber",
    "params":[],
    "id":1
  }'
WebSocket (JavaScript)
import WebSocket from 'ws';

const ws = new WebSocket('wss://rpc.tetronfun.com/eth/ws');

ws.on('open', () => {
  ws.send(JSON.stringify({
    jsonrpc: "2.0",
    id: 1,
    method: "auth",
    params: { apiKey: process.env.TETRONFUN_API_KEY }
  }));
  ws.send(JSON.stringify({
    jsonrpc: "2.0",
    id: 2,
    method: "eth_subscribe",
    params: ["newHeads"]
  }));
});

ws.on('message', data => {
  const response = JSON.parse(data);
  console.log(response);
});
5. Rate Limits & Throttling

HTTP: 100 requests per minute per API key
WebSocket subscriptions: 10 active subscriptions per connection
Exceeding limits returns 429 Too Many Requests; retry after the Retry-After interval.
6. Best Practices

Batch Requests: Combine multiple calls into a single batch to reduce overhead.
Connection Pooling: Reuse WebSocket connections for multiple subscriptions.
Backoff Strategy: On 429 or 5xx errors, implement exponential backoff to avoid throttling.
7. Security Considerations

Do not expose your API key in client‑side code.
Restrict API key scopes to only the networks and methods required.
Monitor access logs in the dashboard for unusual activity.
Next Steps

Explore Core Features to see how AI‑driven modules consume RPC data.
Review API Reference for advanced parameters, custom chain support, and error codes.
Contact support at [e-mail] for enterprise‑grade private RPC deployments.