Finney Testnet RPC Endpoints

Overview

The Finney testnet provides robust infrastructure through two dedicated RPC (Remote Procedure Call) endpoints. These endpoints serve as archive nodes, offering developers and users comprehensive access to the network's historical data and current state.

Available Endpoints

Endpoint	Type	Status
https://finney.uomi.ai	Primary Archive Node	Active
https://finney2.uomi.ai	Secondary Archive Node	Active

Features

Archive Node Functionality

• Complete historical state access

• Full block history from genesis

• State queries at any block height

• Transaction receipt retrieval for all historical transactions

Supported Methods

Both endpoints support the standard JSON-RPC methods including:

• Ethereum JSON-RPC API (eth_*)

• Net API (net_*)

• Web3 API (web3_*)

• Debug API (debug_*)

Usage Examples

Connecting with Web3.js

const Web3 = require('web3');
const web3 = new Web3('https://finney.uomi.ai');

Connecting with Ethers.js

const { ethers } = require('ethers');
const provider = new ethers.providers.JsonRpcProvider('https://finney.uomi.ai');

Best Practices

1. Load Balancing

   • Alternate between both endpoints for optimal performance

   • Implement retry logic with endpoint switching

2. Rate Limiting

   • Respect rate limits to ensure fair usage

   • Implement appropriate caching strategies

3. Error Handling

   • Always implement proper error handling

   • Monitor response times and implement timeouts

Support

For technical issues or questions:

• Join our Discord community

• Open a GitHub issue

• Contact our developer support team

Network Parameters

• Chain ID: 4386

• Block Time: 3s

Monitoring

Both endpoints are continuously monitored for:

• Uptime

• Response time

• Sync status

• Block height consistency