Connect first.
Build with context.

The snippet uses the standard wallet_addEthereumChain request. RPC and chain identity are filled with verified DrilByte values. Native currency metadata has not been provided, so the marked placeholders must be completed by the network operator before sending this request.

const network = {
  chainId: "0x98a", // 2442 in hexadecimal
  chainName: "DrilByte",
  rpcUrls: ["https://rpc.drilbyte.com"],
  // The operator must provide these values before submission.
  nativeCurrency: {
    name: "FILL_IN_OPERATOR_VALUE",
    symbol: "FILL_IN_OPERATOR_VALUE",
    decimals: "FILL_IN_OPERATOR_VALUE",
  },
};

await window.ethereum.request({
  method: "wallet_addEthereumChain",
  params: [network],
});

No block explorer URL is included: one has not been provided for this network reference.

03 / RPC reference

A familiar JSON-RPC surface.

Send JSON-RPC 2.0 requests over HTTPS to the endpoint below. The chain identity query is a small way to verify that your provider is pointed at the expected network.

curl https://rpc.drilbyte.com \
  -H "content-type: application/json" \
  --data '{
    "jsonrpc": "2.0",
    "method": "eth_chainId",
    "params": [],
    "id": 1
  }'

04 / Client example

Connect with ethers.

If your application already uses ethers, a JsonRpcProvider is enough to read the latest block. The explicit network object keeps chain ID mismatches visible during development.

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider(
  "https://rpc.drilbyte.com",
  { chainId: 2442, name: "drilbyte" },
);

const blockNumber = await provider.getBlockNumber();
console.log(blockNumber);

DrilByte's stated execution client is Geth 1.13 and its consensus model is Proof-of-Authority. Node operators should use the network operator's approved release, genesis, peer, and validator configuration for their environment.