The delegation process bonds stake to a validator, converting stake
dPEN. Delegations may be performed in any block, but only
take effect in the next epoch.
Delegations are accomplished by creating a transaction with a
Delegate description. This specifies a validator ,
PEN from the transaction’s balance, produces a new shielded note
dPEN associated to that validator, and includes an
encryption of the delegation amount to the validators’
shared decryption key . Here is the index of the next epoch, when the
delegation will take effect.
In the last block of epoch , the validators sum the encrypted bonding amounts from all delegate descriptions for validator in the entire epoch to obtain an encryption of the total delegation amount and decrypt to obtain the total delegation amount without revealing any individual transaction’s delegation amount . These total amounts are used to update the size of each validator’s delegation pool for the next epoch.
Revealing only the total inflows to the delegation pool in each epoch helps avoid linkability. For instance, if the size of each individual transaction’s delegation were revealed, a delegation of size followed by an undelegation of size could be correlated if an observer notices that there are some epochs so that
This risk is still present when only the total amount – the minimum disclosure required for consensus – is revealed, because there may be few (or no) other delegations to the same validator in the same epoch. Some care should be taken in client implementations and user behavior to mitigate the effects of this information disclosure, e.g., by splitting delegations into multiple transactions in different epochs involving randomized sub-portions of the stake. However, the best mitigation would simply be to have many users.