LITE NODE COMMUNITY RPC Checking status

PUBLIC BETA / FAIR-USE ACCESS

Public LiteForge RPC
for builders on LitVM

Independently operated infrastructure for the LitVM LiteForge testnet. Connect wallets, deploy contracts, and query the chain through HTTPS/WSS endpoints.

View LitVM docs

Independent endpointLiteForge testnetChain ID 4441

01 JSON-RPC 2.0 02 EVM COMPATIBLE 03 TESTNET ONLY 04 NON-CUSTODIAL ACCESS

01 / CONNECT

Network configuration

Public addresses terminate on HTTPS/WSS. Backend addresses and service ports are not exposed here.

ENDPOINT MANIFEST LITEFORGE
HTTP RPC
https://rpc.lite-node.com
WEBSOCKET
wss://ws.lite-node.com
CHAIN ID
4441
HEX CHAIN ID
0x1159
NETWORK
LitVM LiteForge
CURRENCY
zkLTC / 18 decimals
Explorer ↗ Faucet / Hub ↗ Official docs ↗
WALLET_NETWORK.JSON 
{
  "chainId": "0x1159",
  "chainName": "LitVM LiteForge",
  "nativeCurrency": {
    "name": "zkLTC",
    "symbol": "zkLTC",
    "decimals": 18
  },
  "rpcUrls": [
    "https://rpc.lite-node.com"
  ],
  "blockExplorerUrls": [
    "https://liteforge.explorer.caldera.xyz"
  ]
}
EIP-3085 COMPATIBLE

02 / TEST + INTEGRATE

Builder console

Verify read-only RPC behavior, generate framework configuration, and add an explicit testnet fallback.

READ-ONLY RPC PLAYGROUND ALLOWLISTED
RESPONSEWaiting for request 
Select a safe read method and run it against the community endpoint.

The Vercel function only permits the four methods listed above. Arbitrary RPC proxying is disabled.

INTEGRATION RECIPE GENERATED LOCALLY
litvm-liteforge.json

Recipes contain public network configuration only. Private keys are referenced as environment variables.

RESILIENT TESTNET CLIENT

Community first, canonical fallback

Keep lite-node.com as the primary transport and use the official Caldera endpoint as an explicit fallback. This preserves developer flow during maintenance without hiding which provider answered.

  1. PRIMARYhttps://rpc.lite-node.com
  2. FALLBACKhttps://liteforge.rpc.caldera.xyz/http
VIEM_FALLBACK.TS 
import { createPublicClient, fallback, http } from "viem";

const client = createPublicClient({
  chain: litvmLiteForge,
  transport: fallback([
    http("https://rpc.lite-node.com"),
    http("https://liteforge.rpc.caldera.xyz/http")
  ])
});

03 / EXECUTE

Quickstart

Minimal commands for verifying the network, reading the head, and deploying a contract.

POST ETH_CHAINID 
curl -s https://rpc.lite-node.com \
  -H "content-type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
POST ETH_BLOCKNUMBER 
curl -s https://rpc.lite-node.com \
  -H "content-type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
CLI FOUNDRY 
forge create src/Counter.sol:Counter \
  --rpc-url https://rpc.lite-node.com \
  --private-key $PRIVATE_KEY

Never commit private keys. Use a local environment variable or hardware-backed signer. Official Foundry guide ↗

JS HARDHAT 
networks: {
  litvmLiteForge: {
    url: "https://rpc.lite-node.com",
    chainId: 4441,
    accounts: [process.env.PRIVATE_KEY]
  }
}

MANUAL WALLET SETUP

MetaMask parameters

Use these values if your wallet does not support automatic network requests.

Official wallet guide ↗
Network name
LitVM LiteForge
RPC URL
https://rpc.lite-node.com
Chain ID
4441
Currency symbol
zkLTC
Block explorer
liteforge.explorer.caldera.xyz

04 / OBSERVE

Operational posture

Measured checks, transparent limits, and no invented availability numbers.

The status console calls a same-origin Vercel function that checks RPC response, network identity, and relative head position. Results are timestamped and refreshed periodically; they are operational signals, not an uptime guarantee.

  • 01
    Endpoint response

    JSON-RPC requests are checked for a valid response.

  • 02
    Chain identity

    eth_chainId is expected to return 0x1159.

  • 03
    Head comparison

    Local block height is compared against the canonical LiteForge RPC.

  • 04
    Gateway isolation

    Backend service ports are intended to remain behind the public proxy.

05 / FAIR USE

Shared endpoint, responsible access

This service exists to make testnet development easier, not to replace dedicated infrastructure.

01

Testnet only

Do not send mainnet funds. zkLTC on LiteForge is a testnet gas token.

02

No guaranteed SLA

Availability is best-effort. Maintenance, upgrades, or upstream testnet changes may interrupt service.

03

Expensive calls

Heavy indexing and wide eth_getLogs ranges may be throttled to protect shared capacity.

04

Abuse controls

Spam, recursive polling, and abusive traffic may be rate-limited or blocked without notice.

WORKLOAD FIT CHECK

Shared endpoint or dedicated access?

Estimate the operational shape of your testnet workload. The calculation runs only in this browser and sends no project data.

Workload characteristics

CURRENT FIT

Public endpoint fits

The fair-use endpoint should suit this light testnet workload. Use backoff and avoid aggressive polling.

  • Use exponential retry with jitter.
  • Keep log ranges narrow.
Discuss dedicated access

NEED CONSISTENT CAPACITY?

Dedicated access and higher limits are planned for active builders.

Contact operator on GitHub
MANUAL COPY

Automatic clipboard access was blocked. The value below is selected—press ⌘C or Ctrl+C.