BOB RPC — Free Endpoint & Developer Guide

BOB (Build on Bitcoin) is a hybrid layer-2 that combines Bitcoin security with EVM tooling. This guide shows how to connect to a free BOB RPC endpoint on MoltNode — no API key and no signup required.

What is BOB

BOB is a hybrid layer-2 network that aims to bring Bitcoin and Ethereum closer together: it offers a familiar EVM execution environment while orienting itself around Bitcoin security and Bitcoin-native use cases. For developers, the practical upshot is that BOB behaves like an Ethereum-style rollup — you deploy Solidity contracts, use ordinary Ethereum addresses, and call the standard JSON-RPC interface.

Because BOB is fully EVM-compatible, it exposes the standard eth_* JSON-RPC method set and works with the same wallets, libraries, and developer tooling you already use on Ethereum and its layer-2s. The native gas token is ETH, so there is no separate token to acquire just to pay for transactions. The network is identified by chain ID 60808.

BOB RPC endpoint on MoltNode

MoltNode gives BOB one clean URL that is also a working RPC endpoint:

https://moltnode.ag/bob

No API key is required and there is no signup. The endpoint speaks JSON-RPC 2.0 over HTTP POST, and CORS is open so browser apps can call it directly without a proxy. The URL has dual behavior: a GET opened in a browser renders a human-readable page about the chain, while a POST carrying a JSON-RPC body returns a machine response. One address serves both people and programs.

To use the free BOB RPC in a wallet, add a custom network with the RPC URL https://moltnode.ag/bob, chain ID 60808, and currency symbol ETH.

Probe it with curl

To verify the BOB JSON-RPC endpoint is live, ask for the latest block number:

curl -s https://moltnode.ag/bob \
  -X POST \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

The response is a JSON object with the current block height, hex-encoded, in result. Swap the method for any standard eth_* call — eth_chainId, eth_getBalance, eth_getTransactionReceipt — to read whatever your app needs from the BOB node.

Use it from your app

Any JSON-RPC client connects to the BOB RPC endpoint. Here is a minimal viem example pointed at the URL:

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://moltnode.ag/bob"),
});

const blockNumber = await client.getBlockNumber();
console.log("BOB block:", blockNumber);

The same URL drops into ethers, web3.py, wagmi, or any library that accepts an HTTP RPC URL — no special configuration beyond the endpoint itself.

Reliability & failover

Behind the single moltnode.ag/bob URL are upstream node providers, and MoltNode is built to fail over automatically. If an upstream is unavailable or returns an error, requests route to the next available provider so your application keeps reading and writing. The upstream API keys stay server-side and are never exposed to your client, so you get reliable BOB node access without managing any credentials.

There is no hard rate limit, but this is a shared, free resource. Please use it responsibly: cache results where practical, avoid tight polling loops, and for heavy production traffic, treat MoltNode as a fast default and a failover layer rather than your only dependency.

For humans and agents

The dual GET/POST behavior makes the endpoint useful to developers and automated tools alike. You can paste https://moltnode.ag/bob into a browser to read about the chain, while a script or wallet POSTs JSON-RPC to the same URL.

For automated discovery, MoltNode publishes a machine-readable catalog of every supported chain at https://moltnode.ag/api/chains and an agent-oriented summary at https://moltnode.ag/llms.txt. An AI agent can fetch the catalog, locate the BOB entry and its endpoint, and start issuing eth_* calls with no human in the loop.

Closing

The free BOB RPC endpoint at https://moltnode.ag/bob gives you a no-key, JSON-RPC BOB node that works with viem, ethers, wallets, and AI agents — with automatic failover handled for you. Point your client at the URL and start building.