Encyclopedia Ethereum · Entry 265
Moving an Ethereum validator safely: slashing-protection records
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| History | Key material alone does not contain all prior signing decisions. | [1] |
| Interchange | EIP-3076 defines a format for moving signing history between clients. | [1] |
| Network | The interchange metadata identifies the consensus chain. | [1] |
A restored key can unknowingly repeat a duty
A validator can be penalized for signing incompatible messages, including certain proposals or attestations. A new client holding the key may not know that the old client already signed a conflicting message.
The protection database supplies that missing context. Preserve it when changing software, recovering hardware or following a supported migration procedure.
A backup computer can create a second signer
Suppose the old machine loses monitoring connectivity but continues signing. Starting an independent backup with the same key can leave both active. A backup intended to prevent downtime can then introduce a conflicting-signature risk.
Confirm shutdown and follow the clients’ migration guidance before enabling the replacement. Coordinate signing history as part of the move rather than treating it as an optional log.
Check compatibility and import results
An interchange file identifies the network and contains validator public keys plus relevant signed-message records. Clients can maintain complete or minimal protection histories, and the interchange rules account for those different strategies.
Use the actual client’s supported import and export commands, verify their outcomes and retain secure backups. A valid file format does not certify that every relevant signer or history record was included.
Direct answers
Questions people ask
Is copying the validator keystore enough for migration?
No. It provides key material but may omit previous signing decisions. Use the supported transfer of slashing-protection history as well.
Can slashing protection guarantee no slashing under all failures?
No. Its protection depends on correct client behavior, complete enough history and coordinated operation. Independent duplicate signing remains a material risk.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
Slashing protection records what a validator has already signed so software can refuse conflicting proposals or votes. When moving a key to another client, transfer the relevant signing history using the supported process, such as EIP-3076 interchange. Stop the old signer before enabling an independent replacement; the history file is not permission to run both at once.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimHistory: Key material alone does not contain all prior signing decisions.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimInterchange: EIP-3076 defines a format for moving signing history between clients.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimNetwork: The interchange metadata identifies the consensus chain.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimRevision history
- — First publication after primary-source research and separate automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Slashing protection interchange formatEthereum Improvement Proposals
Signing-history transfer between validator clients does not authorize concurrent independent copies.
Locator: Interchange format; import and export; safety · Version / scope: EIP-3076 · Retrieved: 2026-10-02T18:55:26.323ZOpen source - Home staking Ethereumethereum.org contributors
Running and maintaining execution, consensus and validator infrastructure with a qualifying stake.
Locator: How it works; responsibilities; requirements · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:25.708ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “Moving an Ethereum validator safely: slashing-protection records.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/validator-slashing-protection/