{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "ethereum-staking-as-a-service",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/ethereum-staking-as-a-service/",
  "collection": "ethereum",
  "title": "Staking as a service: which keys and duties go to the operator?",
  "description": "Compare validator operation, withdrawal control and custody when a provider runs an Ethereum validator for you.",
  "aliases": [
    "Ethereum staking as a service",
    "staking provider withdrawal keys"
  ],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T19:27:58.939Z",
    "dataAsOf": "2026-10-02"
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "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.",
    "claimId": "ethereum-staking-as-a-service-quick-answer",
    "sourceIds": [
      "x425-eth-eth-saas"
    ]
  },
  "keyFacts": [
    {
      "label": "Operation",
      "value": "A provider runs the validator infrastructure.",
      "sourceIds": [
        "x425-eth-eth-saas"
      ],
      "id": "operation",
      "claimId": "ethereum-staking-as-a-service-fact-operation"
    },
    {
      "label": "Signing risk",
      "value": "Misused signing keys can cause penalties or slashing.",
      "sourceIds": [
        "x425-eth-eth-saas"
      ],
      "id": "signing-risk",
      "claimId": "ethereum-staking-as-a-service-fact-signing-risk"
    },
    {
      "label": "Custody",
      "value": "Withdrawal-address control distinguishes materially different arrangements.",
      "sourceIds": [
        "x425-eth-eth-saas"
      ],
      "id": "custody",
      "claimId": "ethereum-staking-as-a-service-fact-custody"
    }
  ],
  "prerequisites": [
    "ethereum-proof-of-stake-finality",
    "ethereum-staking-withdrawals"
  ],
  "sections": [
    {
      "id": "keys",
      "heading": "Separate the two kinds of authority",
      "sourceIds": [
        "x425-eth-eth-saas",
        "x425-eth-eth-keys"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "example",
      "heading": "A responsive validator can still have custody risk",
      "sourceIds": [
        "x425-eth-eth-saas"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "exit",
      "heading": "Check the failure and offboarding path",
      "sourceIds": [
        "x425-eth-eth-saas"
      ],
      "paragraphs": [
        "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."
      ]
    }
  ],
  "faq": [
    {
      "question": "Is staking as a service the same as pooled staking?",
      "answer": "Not necessarily. A service can operate your own funded validator, whereas a pool combines contributions and distributes claims under an additional system.",
      "sourceIds": [
        "x425-eth-eth-saas",
        "x425-eth-eth-pools"
      ]
    },
    {
      "question": "Can retaining withdrawal control prevent all slashing?",
      "answer": "No. Signing behavior can still lead to slashing. Withdrawal control limits a different category of authority and does not make operation error-free.",
      "sourceIds": [
        "x425-eth-eth-saas",
        "x425-eth-eth-rewards"
      ]
    }
  ],
  "claims": [
    {
      "id": "ethereum-staking-as-a-service-quick-answer",
      "articleSlug": "ethereum-staking-as-a-service",
      "statement": "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.",
      "sourceIds": [
        "source-1b2cc02258c65baa"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-1b2cc02258c65baa",
          "locator": "How it works; keys; counterparty risk"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read delegated-staking spectrum and trust model. Signing authority can cause penalties but cannot spend the separate withdrawal address. Current source explicitly supports execution-layer-triggered exits after Pectra, overriding the stale future-EIP7002 paragraph on the keys page. Draft conditions exit control on actual credentials and provider custody."
        ]
      }
    },
    {
      "id": "ethereum-staking-as-a-service-fact-operation",
      "articleSlug": "ethereum-staking-as-a-service",
      "statement": "Operation: A provider runs the validator infrastructure.",
      "sourceIds": [
        "source-1b2cc02258c65baa"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-1b2cc02258c65baa",
          "locator": "How it works; keys; counterparty risk"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read delegated-staking spectrum and trust model. Signing authority can cause penalties but cannot spend the separate withdrawal address. Current source explicitly supports execution-layer-triggered exits after Pectra, overriding the stale future-EIP7002 paragraph on the keys page. Draft conditions exit control on actual credentials and provider custody."
        ]
      }
    },
    {
      "id": "ethereum-staking-as-a-service-fact-signing-risk",
      "articleSlug": "ethereum-staking-as-a-service",
      "statement": "Signing risk: Misused signing keys can cause penalties or slashing.",
      "sourceIds": [
        "source-1b2cc02258c65baa"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-1b2cc02258c65baa",
          "locator": "How it works; keys; counterparty risk"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read delegated-staking spectrum and trust model. Signing authority can cause penalties but cannot spend the separate withdrawal address. Current source explicitly supports execution-layer-triggered exits after Pectra, overriding the stale future-EIP7002 paragraph on the keys page. Draft conditions exit control on actual credentials and provider custody."
        ]
      }
    },
    {
      "id": "ethereum-staking-as-a-service-fact-custody",
      "articleSlug": "ethereum-staking-as-a-service",
      "statement": "Custody: Withdrawal-address control distinguishes materially different arrangements.",
      "sourceIds": [
        "source-1b2cc02258c65baa"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-1b2cc02258c65baa",
          "locator": "How it works; keys; counterparty risk"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read delegated-staking spectrum and trust model. Signing authority can cause penalties but cannot spend the separate withdrawal address. Current source explicitly supports execution-layer-triggered exits after Pectra, overriding the stale future-EIP7002 paragraph on the keys page. Draft conditions exit control on actual credentials and provider custody."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "x425-eth-eth-saas",
      "label": "Staking as a service",
      "publisher": "ethereum.org contributors",
      "url": "https://ethereum.org/en/staking/saas/",
      "locator": "How it works; keys; counterparty risk",
      "note": "Outsourced validator operation and withdrawal-key control need separate assessment.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:26.034Z",
      "contentSha256": "7c61790bc7982bc6cade769163078f32e8e4e69425f477ca078fdbfcba451e70",
      "recordId": "source-1b2cc02258c65baa"
    },
    {
      "id": "x425-eth-eth-keys",
      "label": "Ethereum proof-of-stake keys",
      "publisher": "ethereum.org contributors",
      "url": "https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/keys/",
      "locator": "Validator key; withdrawal key",
      "note": "Online validator signing versus separate withdrawal authority and credentials.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:26.064Z",
      "contentSha256": "bc59c1f6f7c1b4061b0200e322370b653b9f4ac72e8484ebff173f9a7d474896",
      "recordId": "source-c37ef41d3c4ba6d9"
    },
    {
      "id": "x425-eth-eth-pools",
      "label": "Pooled staking",
      "publisher": "ethereum.org contributors",
      "url": "https://ethereum.org/en/staking/pools/",
      "locator": "How it works; risks; liquid staking",
      "note": "Pooled participation, service dependencies, fees and tokenized versus non-tokenized claims.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:26.267Z",
      "contentSha256": "afb35a034170fd9bad572e69276720730fa508302135e522b0f49985d293b3bf",
      "recordId": "source-fb4e302f14876a2b"
    },
    {
      "id": "x425-eth-eth-rewards",
      "label": "Proof-of-stake rewards and penalties",
      "publisher": "ethereum.org contributors",
      "url": "https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/",
      "locator": "Rewards; penalties; inactivity leak; slashing",
      "note": "Reward components, missed duties and penalty distinctions; values are not quoted as live rates.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:26.371Z",
      "contentSha256": "a1279005274988597f18c77dd4dab93e5ab61e3835be5a0b9302c0bea85a5ff9",
      "recordId": "source-5c75a0594463b144"
    }
  ],
  "related": {
    "articles": [
      "ethereum-staking-withdrawals",
      "ethereum-slashing",
      "liquid-staking",
      "ethereum-solo-staking",
      "pooled-ethereum-staking"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "First publication after primary-source research and separate automated verification."
    }
  ],
  "citation": "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/"
}