A validator operator may conceptually delegate stake to its validator as:
self-bonded stake: by bonding stake from the validator treasury account. Self-bonded stake does not have LNTN minted and forms the validator's Penalty-Absorbing Stake.
delegate stake: by bonding stake using a different account address in the validator's control. Delegated stake has LNTN minted and is not part of a validator's Penalty-Absorbing Stake.
A rationale for doing this would be for a validator to have its self-delegated stake spread across both PAS and non-PAS, thereby spreading its operational risk to slashing (PAS is slashed as first priority). However, if the validator were to transfer its self-delegated LNTN to the validator treasury account, this would then be treated as PAS. If the validator were to do this and then unbond the LNTN, a validator could inadvertently unbond PAS when it intended to only unbond LNTN.
This risk should be clarified in the docs.
Rationale
Explicit clarification of this scenario mitigates operational risk of unbonding PAS inadvertently.
To self-bond stake to your validator node, submit a bond transaction from the account used to submit the registration transaction - i.e. the validator’s treasury account address. For how to do this see the how to Bond stake.
The clarification can be made by:
[ ] converting the notebox to a headed section, making it more apparent
[ ] reviewing the (notebox) wording for clarity
[ ] document the (potentially non-obvious) behaviour of this LNTN transfer scenario, either as a paragraph or as a notebox of type warning.
Description
A validator operator may conceptually delegate stake to its validator as:
treasuryaccount. Self-bonded stake does not have LNTN minted and forms the validator's Penalty-Absorbing Stake.A rationale for doing this would be for a validator to have its self-delegated stake spread across both PAS and non-PAS, thereby spreading its operational risk to slashing (PAS is slashed as first priority). However, if the validator were to transfer its self-delegated LNTN to the validator
treasuryaccount, this would then be treated as PAS. If the validator were to do this and then unbond the LNTN, a validator could inadvertently unbond PAS when it intended to only unbond LNTN.This risk should be clarified in the docs.
Rationale
Explicit clarification of this scenario mitigates operational risk of unbonding PAS inadvertently.
Implementation
Following the docs Register a Validator step https://docs.autonity.org/validators/register-vali/#step-5.-confirm-registration, a notebox titled Bond stake to your validator details how to self-bond stake to oyour validator:
The clarification can be made by: