---
updatedAt: 2026-06-09T12:37:31.000Z
---

Fetch the complete documentation index at: https://docs.blockdaemon.com/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version.

# Stake ETH via Fireblocks (App)

Stake ETH to Blockdaemon validators from Fireblocks using either legacy 32 ETH validators or compounding validators.

Blockdaemon is available as a validator provider in **Fireblocks**, allowing Fireblocks clients to stake ETH to Blockdaemon validators directly, without leaving the Fireblocks interface or connecting an external wallet.

***

## Prerequisites

* An active Fireblocks account with the Staking Marketplace feature enabled
* A vault account holding ETH on Ethereum Mainnet
* Sufficient ETH balance to cover your stake amount plus gas fees

***

## Supported Validator Types

Both Ethereum validator credential types are supported:

| Type                 | Credential      | Behaviour                                                                                                                                                     |
| -------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Auto-compounding** | 0x02 (EIP-7251) | Rewards compound automatically into the validator balance. Supports top-up (add to stake) and partial or full withdrawal. Accepts 32–2,048 ETH per validator. |
| **Legacy**           | 0x01            | Rewards auto-sweep to your withdrawal address. One validator per 32 ETH.                                                                                      |

***

## Option A: Stake via the Fireblocks UI

### Step 1. Open the Fireblocks Staking Marketplace

1. Log in to your Fireblocks account.
2. In the left-hand navigation, select **Staking**.
3. Select the **Ethereum** staking option to open the ETH staking page.

### Step 2. Select Blockdaemon as Your Provider

1. Click **Stake** to begin a new staking position.
2. From the list of validator providers, select **Blockdaemon**.

### Step 3. Choose Your Validator Type

Select your preferred validator credential type:

* **Compounding** — auto-compounding (0x02), supports 32–2,048 ETH per validator, top-up, and partial/full withdrawal.
* **Legacy** — standard 0x01 validator, 32 ETH per validator, rewards auto-sweep to withdrawal address.

### Step 4. Configure and Submit Your Stake

1. Enter the **amount of ETH** you wish to stake and select the **vault account** to use.
2. Confirm the **fee recipient address** and **withdrawal address**.
   * The withdrawal address cannot be changed after the validator is launched.
3. Review the full staking summary and click **Stake**.
4. Approve the transaction in the Fireblocks mobile app using your PIN and biometric authentication.

Once confirmed on-chain, your validators will appear in a `deposited` state. You can track their status in the [Ethereum Dashboard](https://docs.blockdaemon.com/docs/ethereum-dashboard).

***

### Managing Your Stake (UI)

Once your position is active, you can manage it directly from the Fireblocks UI:

| Action                 | Supported                                 |
| ---------------------- | ----------------------------------------- |
| Add to stake (top-up)  | ✅ Auto-compounding (0x02) validators only |
| Partial withdrawal     | ✅ Auto-compounding (0x02) validators only |
| Full withdrawal (exit) | ✅ Both validator types                    |

***

## Option B: Stake via the Fireblocks API

Blockdaemon is listed as a supported staking provider in the [Fireblocks Staking API](https://developers.fireblocks.com/api-reference/staking/initiate-or-add-to-existing-stake). You can specify Blockdaemon as your provider programmatically using the `POST /staking/chains/{chainDescriptor}/stake` endpoint.

### Key Parameters

| Parameter             | Value / Notes                    |
| --------------------- | -------------------------------- |
| `chainDescriptor`     | `ETH`                            |
| `providerId`          | `blockdaemon`                    |
| `stakeAmount`         | Amount in ETH                    |
| `vaultAccountId`      | Your Fireblocks vault account ID |
| `txNote` *(optional)* | A note for the transaction       |

### Behaviour by Validator Type

* **Auto-compounding validator (0x02 / EIP-7251)**: If you provide the `id` of an existing compounding validator position, the API **adds to that position** (top-up). Otherwise, a new position is created.
* **Legacy validator (0x01)**: A **new position is always created** regardless of existing delegations.

### Example Request

```json
POST /staking/chains/ETH/stake

{
  "vaultAccountId": "0",
  "providerId": "blockdaemon",
  "stakeAmount": "32",
  "validatorType": "COMPOUNDING"
}
```

***

## 👋 Need Help?

Contact us through [email](mailto:support@blockdaemon.com) or our [support page](https://www.blockdaemon.com/support) for any issues, bugs, or assistance you may need.

<br />