Solana Beta is now live
Try it free
Query Ethereum's consensus layer over the Beacon REST API: validator duties, finality checkpoints and block data on a dedicated endpoint.
latency
Quick connect
Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.
https://eu.endpoints.matrixed.link/rpc/ethereum-beacon?auth=YOUR_API_KEY
Replace YOUR_API_KEY with your API key.
Get a free key →
Connect
Copy-paste examples for the libraries you already use. Swap the API key, hit run.
const response = await fetch(
"https://eu.endpoints.matrixed.link/rpc/ethereum-beacon/eth/v1/beacon/headers/head",
{
headers: {
"Authorization": "Bearer YOUR_API_KEY"
}
}
);
const data = await response.json();
console.log(data.data.header.message.slot);About Ethereum
Access the Ethereum Beacon Chain (consensus layer) with BoltRPC’s reliable Beacon API infrastructure. Start your free 2-week trial and access both the Beacon API and the Ethereum execution layer from the same provider with one API key.
| Chain ID | N/A (consensus layer) |
| Protocol | Consensus layer (PoS) |
| Slot time | ~12 s |
| Native token | ETH |
| Finality | ~2 epochs (~12.8 min) |
| EVM compatible | No (consensus layer) |
The Ethereum Beacon Chain is the consensus layer of Ethereum, responsible for managing validators, coordinating proof-of-stake, and producing finality. It operates separately from the execution layer (where smart contracts run) and uses a distinct REST API rather than JSON-RPC. Validators, staking infrastructure teams, liquid staking protocols, restaking platforms and bridge operators all query the Beacon API directly for finality checkpoints, validator status and withdrawal credentials. If you are building or operating any staking infrastructure, from a solo validator to an enterprise liquid staking protocol, the Beacon API is a required data source. The execution layer JSON-RPC alone is insufficient for these workloads.
| Endpoint | Description |
|---|---|
/eth/v1/beacon/headers/head | Latest beacon block header |
/eth/v1/beacon/blocks/{slot} | Block by slot number |
/eth/v1/beacon/states/head/validators | Current validator set |
/eth/v1/beacon/states/{state_id}/finality_checkpoints | Finality checkpoint |
/eth/v1/node/syncing | Sync status |
/eth/v1/config/spec | Chain spec configuration |
Beacon API:
GET /eth/v1/node/syncing - check if the beacon node is synced to the chain headGET /eth/v1/beacon/genesis - fetch genesis data including genesis time and validators rootGET /eth/v1/beacon/states/{state_id}/finality_checkpoints - query latest justified and finalized checkpointsGET /eth/v1/beacon/blocks/{block_id} - retrieve a full beacon block by slot or rootGET /eth/v1/config/spec - read the active chain configuration and fork parametersThe Ethereum Beacon API is a REST API, not a JSON-RPC interface. Authentication uses an Authorization: Bearer YOUR_API_KEY header, not the ?auth=YOUR_API_KEY query parameter format of the execution layer endpoint.
Beacon API responses return consensus layer data types: slots, epochs, validators, attestations, and finality checkpoints. There are no addresses, gas values, or transaction hashes in the Beacon data model. State identifiers in API paths use head (latest), finalized, justified, or a specific slot number. For production applications, prefer finalized over head to avoid a chain reorganization affecting the response.
Why BoltRPC
Use BoltRPC's Beacon endpoint alongside the Ethereum execution layer endpoint for complete Ethereum node access from one provider. One API key, one configuration, one invoice. Teams that need both layers do not need separate providers.
The Beacon Chain is the foundation for validator operations, staking infrastructure, and any application that needs consensus layer data: finality checkpoints, validator status, withdrawal credentials. Staking protocols query the Beacon API continuously, and reliable access is non-negotiable for anything touching real ETH.
Applications that need confirmed finality (not just execution layer confirmations) require Beacon API access. Bridges, oracles, and cross-chain protocols rely on finality checkpoints to make security decisions about when assets can safely be processed.
Teams running validator monitoring dashboards or alerting systems use the Beacon API for validator status, missed attestations, and slashing events. Pairing the Beacon endpoint with the execution layer endpoint from one provider simplifies both the architecture and the operational overhead.
BoltRPC runs on Matrixed.Link's ISO/IEC 27001:2022 certified infrastructure. For enterprise staking teams and liquid staking protocols with compliance requirements, certified infrastructure is a procurement requirement, not a nice-to-have.
FAQ
Common questions about connecting to Ethereum over BoltRPC.
Get started
One endpoint format, 20+ networks, no SDK. Drop our URL into the client you already use and your integration is done.
No credit card required. · 14-day trial on any tier.