# Staking as a service: which keys and duties go to the operator? Staking as a service delegates validator operation to another party. In a non-custodial arrangement, you retain the withdrawal address while the provider controls the signing operation; a custodial service can control both. Ask who controls withdrawals, who can initiate an exit, how fees are charged and who bears penalties. The service label alone does not answer those questions. Evidence: [Staking as a service](https://ethereum.org/en/staking/saas/) Canonical: https://degreesofsatoshi.com/encyclopedia/ethereum-staking-as-a-service/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Operation:** A provider runs the validator infrastructure. ([Staking as a service](https://ethereum.org/en/staking/saas/)) - **Signing risk:** Misused signing keys can cause penalties or slashing. ([Staking as a service](https://ethereum.org/en/staking/saas/)) - **Custody:** Withdrawal-address control distinguishes materially different arrangements. ([Staking as a service](https://ethereum.org/en/staking/saas/)) ## Separate the two kinds of authority The online validator signing key performs consensus duties. Withdrawal credentials identify the authority and destination for the validator’s funds. A provider that receives signing capability has operational power even if withdrawals point to an address you control. Read the deposit and key-management flow, not only a marketing description. If withdrawals point to the provider, your access can depend on its custody and service terms. Evidence: [Staking as a service](https://ethereum.org/en/staking/saas/); [Ethereum proof-of-stake keys](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/keys/) ## A responsive validator can still have custody risk Suppose a dashboard shows excellent uptime, but the withdrawal address belongs to the service. Those performance statistics do not give you independent control of the underlying stake. Conversely, your own withdrawal address does not prevent an operator from making signing mistakes. Evaluate custody and operational reliability separately. One favorable metric cannot stand in for the other. Evidence: [Staking as a service](https://ethereum.org/en/staking/saas/) ## Check the failure and offboarding path Current Ethereum documentation describes execution-layer exit requests from the withdrawal address. Whether you can use that authority depends on the actual credentials and who controls that address, not merely having access to a provider dashboard. Check fees, operator software, penalty allocation and the documented exit process. An advertised guarantee has a separate counterparty behind it and is not a protocol-level exemption from loss. Evidence: [Staking as a service](https://ethereum.org/en/staking/saas/) ## Questions ### Is staking as a service the same as pooled staking? Not necessarily. A service can operate your own funded validator, whereas a pool combines contributions and distributes claims under an additional system. Evidence: [Staking as a service](https://ethereum.org/en/staking/saas/); [Pooled staking](https://ethereum.org/en/staking/pools/) ### Can retaining withdrawal control prevent all slashing? No. Signing behavior can still lead to slashing. Withdrawal control limits a different category of authority and does not make operation error-free. Evidence: [Staking as a service](https://ethereum.org/en/staking/saas/); [Proof-of-stake rewards and penalties](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/) ## Claims and scope ### ethereum-staking-as-a-service-quick-answer Staking as a service delegates validator operation to another party. In a non-custodial arrangement, you retain the withdrawal address while the provider controls the signing operation; a custodial service can control both. Ask who controls withdrawals, who can initiate an exit, how fees are charged and who bears penalties. The service label alone does not answer those questions. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-staking-as-a-service-fact-operation Operation: A provider runs the validator infrastructure. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-staking-as-a-service-fact-signing-risk Signing risk: Misused signing keys can cause penalties or slashing. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-staking-as-a-service-fact-custody Custody: Withdrawal-address control distinguishes materially different arrangements. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Staking as a service](https://ethereum.org/en/staking/saas/) — ethereum.org contributors. Outsourced validator operation and withdrawal-key control need separate assessment. Locator: How it works; keys; counterparty risk. Retrieved: 2026-10-02T18:55:26.034Z. - [Ethereum proof-of-stake keys](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/keys/) — ethereum.org contributors. Online validator signing versus separate withdrawal authority and credentials. Locator: Validator key; withdrawal key. Retrieved: 2026-10-02T18:55:26.064Z. - [Pooled staking](https://ethereum.org/en/staking/pools/) — ethereum.org contributors. Pooled participation, service dependencies, fees and tokenized versus non-tokenized claims. Locator: How it works; risks; liquid staking. Retrieved: 2026-10-02T18:55:26.267Z. - [Proof-of-stake rewards and penalties](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/) — ethereum.org contributors. Reward components, missed duties and penalty distinctions; values are not quoted as live rates. Locator: Rewards; penalties; inactivity leak; slashing. Retrieved: 2026-10-02T18:55:26.371Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees of Satoshi editorial project. “Staking as a service: which keys and duties go to the operator?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-staking-as-a-service/