Background
Currently, an existing node operator can perform a node migration to a new node with the same TLS key as an existing participant, opening the door to some griefing attacks and other potential issues as we assume TLS keys to be unique in several places in the contract. We should not allow duplicate TLS keys.
User Story
As a node operator I would not like another operator to claim that they have my TLS key.
Acceptance Criteria
Operators may not claim existing TLS keys in the contract.
Resources & Additional Notes
No response
Background
Currently, an existing node operator can perform a node migration to a new node with the same TLS key as an existing participant, opening the door to some griefing attacks and other potential issues as we assume TLS keys to be unique in several places in the contract. We should not allow duplicate TLS keys.
User Story
As a node operator I would not like another operator to claim that they have my TLS key.
Acceptance Criteria
Operators may not claim existing TLS keys in the contract.
Resources & Additional Notes
No response