Staked
  • Introduction
  • Staking
    • Yields API
    • Delegations
    • Node Provisioning API
    • Reporting API
  • ETH2
    • Voluntary Exits
    • BLS Withdrawal Changes
  • Resources
    • Public Repos
Powered by GitBook
On this page

Was this helpful?

  1. ETH2

BLS Withdrawal Changes

Validators with a type-0x00 withdrawal credential created with a BLS public key need to submit a SignedBLSToExecutionChange operation in order to withdraw rewards from the beacon chain.

Rewards and validator duties are still performed regardless of withdrawal credential type. However, the validator balance will not get withdrawn to the execution layer until the validator has a type-0x01 withdrawal credential. Exits submitted before having a type-0x01 will stop validator duties but will not withdraw funds until a SignedBLSToExecutionChange is submitted.

Submit signed withdrawal key changes

PUT https://mainnet.staked.cloud/api/delegations/ETH2/bls_to_execution_changes

Submit a list of (decrypted) SignedBLSToExecutionChanges to submit to the beacon chain.

Request Headers

Name
Type
Description

Api-Key*

string

Your API key (preferred method of passing api key is now in headers rather than query params)

Query Parameters

Name
Type
Description

api_key*

String

[Deprecated since March '25 (preferred method of passing api key is now in headers rather than query params)]

Your Staked API key

Request Body

Name
Type
Description

[]*

Array

List of SignedBLSToExecutionChanges to submit

All changes submitted successfully.

{
    "count": 1,
    "numSuccesses": 1, 
    "failures": []
}

Some changes failed to submit. The error for each failed change is returned. Ignored changes were successful.

{
    "count": 2,
    "numSuccesses": 1, 
    "failures": [
        {
            "index": 0,
            "message": "invalid signature",
            "signedBLSToExecutionChange": SignedBLSToExecutionChange
        }
    ]
}

Last updated 1 month ago

Was this helpful?