Skip to content

Commit 3de1093

Browse files
authored
staking: fill in page explaining basics of Penumbra staking (#61)
1 parent 22aa2b9 commit 3de1093

File tree

2 files changed

+36
-0
lines changed

2 files changed

+36
-0
lines changed

pages/staking.mdx

+36
Original file line numberDiff line numberDiff line change
@@ -1 +1,37 @@
11
# Shielded Staking
2+
3+
Penumbra's innovative shielded staking design enables privacy for delegators while preserving accountability for validators. Penumbra integrates privacy with proof-of-stake: participants can secure the network, participate in governance, and receive monetary rewards, without sacrificing privacy through Penumbra's non-custodial, permissionless staking design.
4+
5+
## How Delegation Works
6+
7+
### Delegation Pools
8+
9+
Each validator maintains a delegation pool that determines their voting power. The total stake in each validator's pool is public. Delegations are anonymous, and associate the quantity of UM tokens to be staked with the specific validator.
10+
11+
### Delegation Tokens
12+
13+
When a delegator delegates the UM staking token to a validator, they receive **delegation tokens** in return. These tokens represent shares in a specific validator's delegation pool, and can be traded similar to liquid staking tokens on other chains.
14+
15+
The chain tracks the exchange rate between each validator's delegation token and staking tokens, capturing the earned staking rewards for that validator. A delegator can undelegate to receive both their original staking tokens (if the validator was not [slashed](#slashing)) and their earned rewards. Note that there is an unbonding delay before the earned rewards can be converted back to staking tokens, see [Unbonding Delay](#unbonding-delay) below for more details.
16+
17+
### Slashing
18+
19+
If a validator misbehaves, it is **slashed**. This means that the validator's delegation token is converted to staking tokens at a reduced exchange rate, penalizing the validator's stake.
20+
21+
### Unbonding Delay
22+
23+
To prevent validators from escaping slashing penalties by quickly withdrawing their stake, the chain imposes an unbonding delay.
24+
25+
When a delegator undelegates, their delegation tokens first convert to **unbonding tokens**. These unbonding tokens are tied to the validator identity, such that they remain exposed to slashing penalties if validator misbehavior occurs. After the unbonding delay, the unbonding tokens can finally be converted back to staking tokens, taking into account the earned staking rewards using that validator's exchange rate.
26+
27+
<picture>
28+
<img src="./images/staking-token-flow.png" />
29+
</picture>
30+
31+
The unbonding delay is currently set to 120,960 blocks, or approximately 7 days on mainnet (set via the `unbondingDelay` chain parameter).
32+
33+
One advantage of this approach is that unbonding tokens can be transferred or traded. Users can elect to exit early by selling the tokens at a discount. Slashing risk stays with the unbonding tokens, so market prices will capture information about the validator's risk profile.
34+
35+
## Validator Selection
36+
37+
The active set of validators consists of the top 100 validators by stake, as measured by the total UM staking tokens delegated to them (this is set via the `activeValidatorLimit` chain parameter).

public/images/staking-token-flow.png

44.9 KB
Loading

0 commit comments

Comments
 (0)