Withdrawal Address to Staking Configuration

Overview

Blockdaemon now supports the ability for customers to request withdrawal address mappings for Ethereum staking. This allows you to specify which withdrawal address should map to which staking configuration, ensuring that any validator created using that withdrawal address will be deployed to the desired geographic infrastructure.

This functionality is available today through Customer Success–managed configuration and ties directly into the withdrawal_address field in the Ethereum Stake Intent API.

How It Works

When creating an Ethereum stake intent via API, customers include a withdrawal_address. Blockdaemon can map each withdrawal address to a specific plan_id, which corresponds to a regionally-pinned staking plan.

Example Flow

Customer selects or generates a withdrawal wallet address.

Customer requests Blockdaemon to map that withdrawal address to a specific staking configurstion. These include region, provider, MEV relays etc —for example:

• us-east - AWS
• eu-west - GCE
• ap-southeast - Baremetal

Blockdaemon configures the mapping on the backend.

When the customer submits a stake intent using that withdrawal address, Blockdaemon automatically deploys the validator to the correct region based on the mapping.

Why This Matters

Deterministic Regional Deployment

Customers can control infrastructure distribution simply by choosing which withdrawal address to use—no additional parameters required during staking.

Operational Simplicity

Regional diversification becomes as easy as managing wallet addresses. This is especially useful for institutions running multi-region strategies or requiring deterministic routing for compliance or redundancy.

API Usage

When submitting a stake intent, customers provide the mapped withdrawal address:

**Verify that the signature is valid for the given data and public key. The output should be Verified OK, if not, do not use the response body returned by and contact Blockdaemon.

`{
  "network": "eth",
  "amount": "32",
  "withdrawal_address": "0x1234...abcd"
}`

Blockdaemon handles:

• resolving the withdrawal address
• determining the associated plan_id
• deploying the validator into the correct region

No additional action is required from the customer once mappings are in place.

How to Request a Mapping

Customers can request mappings by opening a ticket with Customer Success or their account team.

Required details:

• Withdrawal address
• Desired staking region

(Optional) Description of intended use case or grouping strategy

Blockdaemon will confirm when the mapping is active and ready for use.