Coinbase Staking API support for Ethereum Pectra features is in Beta on the Ethereum Hoodi testnet. Try it out here and share feedback on Discord.
Dedicated ETH Staking must use increments of 32 ETH. You will be staking directly to ETH validators that the API will stand up on your behalf. See the quickstart to familiarize yourself with Coinbase Staking API and basic usage.
Currently, Dedicated ETH staking only supports addresses used with the Coinbase Staking API specifically. Coinbase App addresses and Coinbase Prime addresses are not supported.

​
External Address

The external address model is an address model where the private keys are not managed by the Coinbase SDK. The developer would be responsible for “bringing their own wallet”. All signing operations must be completed off-platform.

​
Stake

To stake, ensure that the address contains an increment of 32 ETH plus additional ETH to cover transaction fees. The example below illustrates how to stake from an external address.
Dedicated ETH Staking can take up to 5 minutes to generate a staking transaction to sign.When a user stakes to Dedicated ETH, dedicated infrastructure is created on the backend, leading to the longer wait times.The Transaction in the StakeOperation will be empty until there is a transaction to sign.
import { Coinbase, ExternalAddress, StakeOptionsMode } from "@coinbase/coinbase-sdk";

// Create a new external address on the ethereum-holesky testnet network.
let address = new ExternalAddress(Coinbase.networks.EthereumHolesky, "YOUR_WALLET_ADDRESS");

// Find out how much ETH is available to stake.
let stakeableBalance = await address.stakeableBalance(Coinbase.assets.Eth, StakeOptionsMode.NATIVE);

// Build a stake operation for an amount <= stakeableBalance, and in multiples of 32. In this case, 64 ETH.
// This step will trigger the provisioning of validator infrastructure for your dedicated usage.
// Infrastructure setup times vary with the number of validators. For 30 validators (960 ETH), it can take up to 5 minutes.
let stakingOperation = await address.buildStakeOperation(64, Coinbase.assets.Eth, StakeOptionsMode.NATIVE);

// Native ETH staking involves setting up infrastructure, which can take time.
// Example of polling the stake operation status until it reaches a terminal state using the SDK.
await stakingOperation.wait();
Refer to the ExternalAddress docs for a full list of supported methods.
Once the stake operation has been built, relay the transactions to your end-user for signing and broadcasting. Refer to the Signing and Broadcasting Transactions section for an example using Ethers.js.

​
Unstake

Unstaking on native ETH requires a voluntary exit message to be signed by the validator and submitted to the network to initiate the unstaking process. For external addresses, this can be done two ways:

​
Coinbase Managed Unstake

import { Coinbase, ExternalAddress } from "@coinbase/coinbase-sdk";

// Create a new external address on the ethereum-holesky testnet network.
let address = new ExternalAddress(Coinbase.networks.EthereumHolesky, "YOUR_WALLET_ADDRESS");

// To know how much ETH balance across all your validators is available for staking
// you can use the `unstakeableBalance` method as shown below.
// Note: For Dedicated ETH Staking, the unstakeable balance depends on the validators owned by the CDP account,
// not your address. We surface the unstakeable balance on the address object for simplicity.
let unstakeableBalance = await address.unstakeableBalance(Coinbase.assets.Eth, StakeOptionsMode.NATIVE);

// Build an unstake operation for an amount <= unstakeableBalance, and in multiples of 32. In this case, 32 ETH.
// This behind the scenes will identify validators to be exited, generate a voluntary exit message per validator,
// sign it with the validator's private key and broadcast them for you.
let stakingOperation = await address.buildUnstakeOperation(32, Coinbase.assets.Eth, StakeOptionsMode.NATIVE, {"immediate": "true"});

// Immediate native eth unstaking is completely handled by the API with no user action needed.
// Example of polling the unstake operation status until it reaches a terminal state using the SDK.
await stakingOperation.wait();
Refer to the ExternalAddress docs for a full list of supported methods.
Once the unstake operation has completed successfully, congrats you’ve just exited a validator. Refer to the View Validator Information section to monitor your validator status. When it changes to WITHDRAWAL_COMPLETE, your funds should be available in the withdrawal_address set during staking.

​
User Managed Unstake

import { Coinbase, ExternalAddress } from "@coinbase/coinbase-sdk";

// Create a new external address on the ethereum-holesky testnet network.
let address = new ExternalAddress(Coinbase.networks.EthereumHolesky, "YOUR_WALLET_ADDRESS");

// To know how much ETH balance across all your validators is available for staking
// you can use the `unstakeableBalance` method as shown below.
// Note: For Dedicated ETH Staking, the unstakeable balance depends on the validators owned by the CDP account,
// not your address. We surface the unstakeable balance on the address object for simplicity.
let unstakeableBalance = await address.unstakeableBalance(Coinbase.assets.Eth, StakeOptionsMode.NATIVE);

// Build an unstake operation for an amount <= unstakeableBalance, and in multiples of 32. In this case, 32 ETH.
// This behind the scenes will identify validators to be exited, generate a voluntary exit message per validator,
// and relay them back to be broadcasted appropriately to the Ethereum network.
let stakingOperation = await address.buildUnstakeOperation(32, Coinbase.assets.Eth, StakeOptionsMode.NATIVE);

// Native eth unstaking can take some time as we build the voluntary exit message and have it signed by the validator.
// Example of polling the unstake operation status until it reaches a terminal state using the SDK.
await stakingOperation.wait();
After unstaking, voluntary exit messages can be read and stored on your end and broadcasted to the network whenever you want to initiate the unstaking process. Refer to the Broadcasting Exit Messages section for an example.

​
Wallet Address

The wallet address model is an address model where the private keys are managed by the Coinbase SDK. This means that the SDK can sign transactions on behalf of the user. In production, it’s recommend to use a server-signer for increased security. The example below illustrates how to stake from a wallet address.

​
Stake

import { Coinbase, Wallet } from "@coinbase/coinbase-sdk";

// Create a new wallet address on the ethereum-holesky testnet network.
let wallet = await Wallet.create({ networkId: Coinbase.networks.EthereumHolesky });

// A newly created wallet will have no balance. Use wallet.getDefaultAddress()
// to retrieve the default address and fund it with the required ETH.

// Find out how much ETH is available to stake.
let stakeableBalance = await wallet.stakeableBalance(Coinbase.assets.Eth);

// Build a stake operation for an amount <= stakeableBalance, and in multiples of 32. In this case, 32 ETH.
let stakingOperation = await wallet.createStake(32, Coinbase.assets.Eth, StakeOptionsMode.NATIVE);
Refer to the WalletAddress docs for a full list of supported methods.
Once the stake operation has completed successfully, you’ve staked ETH to a dedicated validator!

​
Unstake

Unstaking on native ETH requires a voluntary exit message to be signed by the validator and submitted to the network to initiate the unstaking process. For wallet addresses, this can be done two ways:

​
Coinbase Managed Unstake

Refer to the WalletAddress docs for a full list of supported methods.
import { Coinbase, Wallet } from "@coinbase/coinbase-sdk";

// Create a new wallet address on the ethereum-holesky testnet network.
let wallet = await Wallet.create({ networkId: Coinbase.networks.EthereumHolesky });

// To know how much ETH balance across all your validators is available for staking
// you can use the `unstakeableBalance` method as shown below.
// Note: For Dedicated ETH Staking, the unstakeable balance depends on the validators owned by the CDP account,
// not your wallet. We surface the unstakeable balance on the wallet object for simplicity.
let unstakeableBalance = await wallet.unstakeableBalance(Coinbase.assets.Eth, StakeOptionsMode.NATIVE);

// Build an unstake operation for an amount <= unstakeableBalance, and in multiples of 32. In this case, 32 ETH.
let stakingOperation = await wallet.createUnstake(32, Coinbase.assets.Eth, StakeOptionsMode.NATIVE, {"immediate": "true"});
Once the unstake operation has completed successfully, congrats you’ve just exited a validator.Refer to the View Validator Information section to monitor your validator status. When it changes to WITHDRAWAL_COMPLETE, your funds should be available in the withdrawal_address set during staking.

​
User Managed Unstake

Refer to the WalletAddress docs for a full list of supported methods.
import { Coinbase, Wallet } from "@coinbase/coinbase-sdk";

// Create a new wallet address on the ethereum-holesky testnet network.
let wallet = await Wallet.create({ networkId: Coinbase.networks.EthereumHolesky });

// To know how much ETH balance across all your validators is available for staking
// you can use the `unstakeableBalance` method as shown below.
// Note: For Dedicated ETH Staking, the unstakeable balance depends on the validators owned by the CDP account,
// not your wallet. We surface the unstakeable balance on the wallet object for simplicity.
let unstakeableBalance = await wallet.unstakeableBalance(Coinbase.assets.Eth, StakeOptionsMode.NATIVE);

// Build an unstake operation for an amount <= unstakeableBalance, and in multiples of 32. In this case, 32 ETH.
let stakingOperation = await wallet.createUnstake(32, Coinbase.assets.Eth, StakeOptionsMode.NATIVE);
After unstaking, voluntary exit messages can be read and stored on your end and broadcasted to the network whenever you want to initiate the unstaking process. Refer to the Broadcasting Exit Messages section for an example.
The functionality below applies to both External and wallet addresses.

​
Broadcasting Exit Messages

The example below broadcasts pre-signed voluntary exit messages surfaced during an unstake process. Ethereum validator exit messages are special transaction types which are pre-signed by the validator keys and must be broadcast directly to the consensus layer. 
// For Holesky, publicly available RPC URL's can be found here https://chainlist.org/chain/17000
stakingOperation.getSignedVoluntaryExitMessages().forEach(async signedVoluntaryExitMessage => {
    let resp = await axios.post("HOLESKY_RPC_URL/eth/v1/beacon/pool/voluntary_exits", signedVoluntaryExitMessage)
    console.log(resp.status);
});

​
Signing and Broadcasting Transactions

The example below signs and broadcasts transactions surfaced via the staking operation resource. These transaction are traditional EIP-1159 transactions that can be signed and broadcasted to the execution layer via a normal transaction flow. 
// Load your wallet's private key from which you initiated the above stake operation.
const wallet = new ethers.Wallet("YOUR_WALLET_PRIVATE_KEY");

// Sign the transactions within staking operation resource with your wallet.
await stakingOperation.sign(wallet);

// For Holesky, publicly available RPC URL's can be found here https://chainlist.org/chain/17000
const provider = new ethers.JsonRpcProvider("HOLESKY_RPC_URL");

// Broadcast each of the signed transactions to the network.
stakingOperation.getTransactions().forEach(async tx => {
    let resp = await provider.broadcastTransaction(tx.getSignedPayload()!);
    console.log(resp);
});

​
View Staking Rewards

After staking an asset, you can view your staking rewards. This allows you to track the rewards earned over time from your staked assets.
SDK DocumentationRefer to the StakingReward docs for a full list of supported methods.Look up staking rewards for a list of addresses.
import { Coinbase, StakingReward } from "@coinbase/coinbase-sdk";

let now = new Date();
let tenDaysAgo = new Date();
tenDaysAgo.setDate(now.getDate() - 10);

let rewards = await StakingReward.list(
    Coinbase.networks.EthereumMainnet, Coinbase.assets.Eth,
    ["VALIDATOR_ADDRESS1", "VALIDATOR_ADDRESS2"],
    tenDaysAgo.toISOString(), now.toISOString(),
);

// Loop through the rewards and print each staking reward
rewards.forEach(reward => console.log(reward.toString()));
View the USD value of rewards including conversion price and time.
// Loop through the rewards and print each staking reward's USD conversion information
rewards.forEach(reward => {
    console.log(
        `USD value: ${reward.usdValue()},
        Conversion price: ${reward.conversionPrice().toString()},
        Conversion time: ${reward.conversionTime().toISOString()}`,
    );
});

​
View Historical Staking Balances

Detailed information about the historical staking balances for given validator address, including bonded and unbonded stakes.
  • Bonded Stakes: The total amount of stake that is actively earning rewards to this address. Pending active stake is not included.
  • Unbonded Balance: This amount includes any ETH balance that is under the control of the wallet address but is not actively staked.
SDK DocumentationRefer to the StakingBalance docs for a full list of supported methods.Look up staking balances for an address.
import { Coinbase, StakingBalance } from "@coinbase/coinbase-sdk";

let now = new Date();
let tenDaysAgo = new Date();
tenDaysAgo.setDate(now.getDate() - 10);

let stakingBalances = await StakingBalance.list(
    Coinbase.networks.EthereumMainnet, Coinbase.assets.Eth,
    "VALIDATOR_ADDRESS",
    tenDaysAgo.toISOString(), now.toISOString(),
);

// Loop through the historical staking balances and print each balance
stakingBalances.forEach(stakingBalance => console.log(stakingBalance.toString()));

​
View Validator Information

Detailed information is available for any validators that you’ve created. The validator status (i.e. provisioned, active, etc) is available in the response and is printed to stdout in the example below. 
// Get the validators that you've provisioned for staking.
const validators = await Validator.list(Coinbase.networks.EthereumHolesky, Coinbase.assets.Eth);

// Loop through the validators and print each validator
validators.forEach(validator => {
    console.log(validator.toString());
});
The Validator object documentation is available here

​
Validator Statuses

A validator can have the following statuses, provided in the status field of the response:
StatusDescriptionOnchain State EquivalentAction Required
ProvisioningValidator is being created by Coinbase:no_entry_sign: (Coinbase Only Status)Wait :hourglass_flowing_sand:
ProvisionedValidator has been created by Coinbase and is ready for a deposit:no_entry_sign: (Coinbase Only Status)Sign and broadcast the provided deposit transaction
DepositedDeposit transaction has been signed, broadcasted, and finalized on the Ethereum network:no_entry_sign: (Coinbase Only Status)Wait :hourglass_flowing_sand:
PendingValidator is in the activation queue. This means the Ethereum network has successfully executed the deposit transactionpending_queuedWait :hourglass_flowing_sand:
ActiveValidator is active and earning rewardsactive_ongoingNone
ExitingValidator is in the exit queue. The validator is still earning rewardsactive_exitingWait :hourglass_flowing_sand:
ExitedValidator is waiting to enter the withdrawal queue. This means the validator has exited the active set and rewards are no longer being earned.exited_unslashedWait :hourglass_flowing_sand:
Withdrawal AvailableValidator is in the withdrawal queue. The network will sweep available funds to the withdrawal_address on a predetermined schedulewithdrawal_possibleWait :hourglass_flowing_sand:
Withdrawal CompleteValidator has completed its lifecycle. It no longer has any validating responsibilities and the available funds (rewards and initial stake) have been swept to the withdrawal_addresswithdrawal_doneNone
UnavailableValidator was provisioned, but a deposit transaction was never broadcasted. Coinbase has spun down the provisioned validator:no_entry_sign: (Coinbase Only Status)None
Active SlashedValidator has been slashed in a previous epoch. The validator is still in the active set, but rewards cannot be earned and a voluntary exit cannot be performedactive_slashedWait :hourglass_flowing_sand:
Exited SlashedValidator has been slashed in a previous epoch. The validator has exited the active setexited_slashedNone

​
Filtering By Validator Statuses

You can filter the list of validators to view all validators with a specific status. 
// Show all your validators with an active status.
const validators = await Validator.list(
    Coinbase.networks.EthereumHolesky,
    Coinbase.assets.Eth,
    ValidatorStatus.ACTIVE,
);