๐ Builder Deposit Slots
Returns the builder deposits of EIP-8282, which the Glamsterdam hard fork introduces, for the selected builders. A deposit registers a new builder, tops up an existing one, or is a deposit that the fork onboarded as a builder. Each item is one deposit. The chain does not report these outcomes. beaconcha.in derives each one by applying the protocol rules to the deposit and to the builder registry.
Select the builders with builder. A builder_pubkey returns the deposits of that public key. Any other option returns the deposits of every public key that its registry periods belong to. An index passes to a new builder once its builder exits and withdraws, so the deposits of an earlier holder of the same index are not returned. Pass that earlier builderโs builder_pubkey to see them. A public key whose only fork deposit was dropped never became a builder, so no index selects it. Use its builder_pubkey.
The response is 404 when the selector matches no builder: a builder_pubkey with no record of any kind, or any other option with no registry period. It is also 404 when the chain has not reached the Glamsterdam hard fork.
A deposit waits in the execution layer queue until a block carries it. The execution layer releases at most 64 deposits into each block, oldest first. A deposit that is still queued does not appear. The chain applies each deposit in the block after the one that carried it. slot is that block, and its parent is the block that carried the deposit.
A deposit that the fork onboarded is processed at the last slot before the fork. Its block_root is null when that slot has no block.
outcome is completed when the chain applied the deposit, rejected with a reject_reason when the chain ignored it, and unknown with an unknown_reason when beaconcha.in cannot tell. Only rejected is a rejection. The chain does not retry a rejected deposit. To act again, send a new deposit.
A builder deposit must carry a withdrawal credential that starts with 0xB0, the builder prefix. The chain ignores a deposit with another prefix, both for a new public key and for a top-up. A top-upโs signature is not checked, so an invalid signature on a top-up does not reject it.
Which fields are set depends on type:
type | amount | builder_execution_address | tx_hash |
|---|---|---|---|
registration, top_up | set | set when the credential starts with 0xB0 | null |
onboarded | set | set when the credential starts with 0xB0 | set |
Amounts are in wei.
Every item has observed_stages consensus_layer_processed, because beaconcha.in lists a deposit once the chain has processed it. For that reason this endpoint has no stage filter. Results can be filtered by a time range.
Results are paginated with a default and maximum page size of 10. Items are ordered by slot, newest first. Items in the same block are ordered by their position in that block, last position first.
Once an item has finality finalized and an outcome other than unknown, it does not change. An item with registry_pending gets its outcome once a finalized registry snapshot includes it, so query it again then. Cache items, not pages, because a new deposit adds an item to the first page.
You can combine this endpoint with:
- The builderโs registry periods, one per tenure: v2/ethereum/builders
- The slot of a deposit: v2/ethereum/slot/overview
Premium Endpoint: This endpoint requires a Scale or Enterprise plan.
Authorizations
Authorization header with value: Bearer YOUR_TOKEN. Refer to the API Keys section to create your API key.
Body
Select builders by one of these options. Every endpoint that uses this selector requires a Scale or Enterprise plan:
- builder_pubkey: One builder, by its public key, as in
execution_payload.builder_pubkey. The best way to follow one builder over time. - builder_index: The builder that holds this index now. To select the builder of a past slot, use that slot's
builder_pubkey. - builder_execution_address: Every builder that withdraws to this execution layer address. Use it for all the builders of one operator.
- builder_entity: Every builder that withdraws to an address that beaconcha.in curated under this name. Optionally include
builder_sub_entity. Matching is case-sensitive.
Note: When a builder exits and withdraws its whole balance, the chain gives its index to the next new builder, so one index can name different builders over time. Every option therefore resolves to builder public keys, and every request of such a key is listed, whichever registry period it falls in. Each item's builder_index is the index the key held when the chain processed it. The builder registry exists from the Glamsterdam hard fork on. An option that matches no builder returns 404. A builder that matches but has nothing in the result returns an empty list or zero counts, not 404.
Execution address and entity reach builders that entered the registry. Records of a public key that never became a builder, such as deposits the fork dropped, are found by builder_pubkey only.
- Builder Public Key
- Builder Index
- ๐ Builder Execution Address
- ๐ Builder Entity
Cursor value for pagination. See our pagination guide for more details.
Response
Successful response.
Response containing the deposits of the selected builder, newest processed slot first.
The time span actually covered by the returned results โ from the first to the last matching data point โ specified in slots, epochs, and Unix timestamps.
This reflects the data that was found, not the range that was queried. When the response is 200 but no data is found, it falls back to the requested range, or to the full available history if no range was given. Some endpoints answer 404 instead when no data is found.
For arbitrary (custom) time-range queries the queried range is expanded outward to whole UTC days, so the covered range may be wider than requested. As stated above, the reported range still reflects the data that was actually found โ a touched UTC day with no data for the selected validators will not extend it.

