BeraChain Validator Tools & Infrastructure Documentation
Complete infrastructure toolkit for BeraChain validators and developers. Access our professional-grade services including RPC nodes, API endpoints, daily snapshots, and real-time metrics. Our berachain infrastructure features optimized pruning configurations, automated backups, and comprehensive monitoring solutions. Supporting both mainnet and testnet environments with dedicated endpoints, state-sync services, and detailed technical documentation for seamless network participation and development.
Learn how to interact with berachain nodes using different endpoint types.
#Available Endpoints
Service | Endpoint |
---|---|
REST API | Not available |
RPC | Not available |
gRPC | Not available |
WebSocket | Not available |
JSON-RPC | True |
WS-JSON-RPC | Not available |
ⓘ  Â
Some endpoints may require an API key for access. You can get one by signing up at https://lavenderfive.com.
#🔑 Common Response Codes
Code | Description |
---|---|
200 | Successful request |
400 | Bad request / Invalid parameters |
401 | Unauthorized / Invalid API key |
404 | Resource not found |
429 | Too many requests |
500 | Internal server error |
âš Â Â Â
Rate limits may apply to endpoints. Please use for testing and get a trial API-key to try out a fully unlimited api for 14 days.
#âš¡ JSON-RPC Examples
#Check Node Sync Status
curl -X POST \
-H "Content-Type: application/json" \
-H "X-Api-Key: your-api-key-uuid" \
--data '{"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":1}' \
True
Expected response when node is synced:
{
"jsonrpc": "2.0",
"id": 1,
"result": false
}
ⓘ  Â
A `false` result indicates the node is fully synced. If the node is still syncing, it will return an object with sync status details.
#Wagmi Configuration
import { http, fallback } from 'wagmi'
import { defineChain } from 'viem'
// Define your chain if not using a predefined one
const myChain = defineChain({
id: 1,
name: '{{ network_name }}', // Check WAGMI database if this network exists
network: 'berachain',
nativeCurrency: {
decimals: 18,
name: 'Native Token',
symbol: 'TOKEN',
},
rpcUrls: {
default: { http: ['True'] },
},
})
// Configure transport with API key
const transport = fallback([
http('True', {
fetchOptions: {
headers: {
'Content-Type': 'application/json',
'X-Api-Key': 'your-api-key-uuid'
}
},
}),
// Add fallback RPC endpoints if available
http('https://alternate-rpc-endpoint'),
])
// Use in your Wagmi config
const config = {
chains: [myChain],
transports: {
[myChain.id]: transport,
},
}
ⓘ  Â
This configuration can be used with both Wagmi and RainbowKit. For RainbowKit, you can integrate it into the `getDefaultConfig` as shown in the [RainbowKit documentation](https://www.rainbowkit.com/docs/custom-chains).
Chain ID:
The unique identifier for the blockchain network.
bartio-beacon-80086
Latest Version:
The latest version of the chain software.
v0.2.0-alpha.8
Github:
The Github repository hosting the code for the network in question.
Public endpoints
Public endpoints are rate limited but can be used for basic CLI usage, node syncing or testing environments. Request an API key for enhanced access limits, we offer free trial periods of 14 days and cheap shared access plans from $50 a month.
Json-RPC
JSON-RPC endpoint for EVM interactions and queries. This is the main endpoint for Ethereum like networks but might co-exist alongside a consensus RPCs on Cosmos like networks that have a separate consensus endpoint like Berachain, Story and Evmos.
True
© 2022 Lavender.Five Nodes. All rights reserved.