Data sources

Everything Farbeam serves comes from public sources or from rows built from them. This page lists each source, what is read, how long it is cached, and the effect of a failure. Live results are on Status and the status page.

Outbound calls have a timeout, a shared cache and per-source health counters. Redirects are refused.

#Sources

Token metadata on EVM (symbol, name, decimals, supply) comes from the chain RPC and is cached for 24 hours.

#Timeouts

#What happens on failure

#A source can answer with nothing

An empty GoPlus result counts as a failed source. sources[] shows goplus with ok: false, the matching checks read unknown, and the result is not cached, so the next read tries again.

Partial answers also happen. GoPlus often returns some fields for a contract and omits others, as the USDC example shows.

#Reading source health

curl -s "https://farbeamlabs.com/api/v1/status" | jq '.data.sources[] | {name, ok, failures, error}'

const res = await fetch("https://farbeamlabs.com/api/v1/status");
const { data } = await res.json();
console.table(data.sources.map(({ name, ok, calls, failures, error }) => ({ name, ok, calls, failures, error })));

import requests

sources = requests.get("https://farbeamlabs.com/api/v1/status", timeout=30).json()["data"]["sources"]
for s in sources:
    print(s["name"], s["ok"], s["calls"], s["failures"], s["error"])

A source shows here only after its first call. A failing fallback may not matter while its primary works.

#Limits and trust

• Public RPC providers throttle, and results can differ by a block or two between providers.
• Third-party fields can be wrong, late or absent. Farbeam reads and shows them with their field names, and it does not correct them.
• These providers are named so you can check their data yourself. Naming them does not mean they endorse this service.
• Prices and checks are for information only and are not financial advice.

To report a data problem, write to contact@farbeamlabs.com with the request_id, the address and the UTC time.