Skip to content

Commit

Permalink
update docs (#8)
Browse files Browse the repository at this point in the history
  • Loading branch information
JasonVranek authored Jan 28, 2024
1 parent 9d5af35 commit 4647516
Show file tree
Hide file tree
Showing 38 changed files with 728 additions and 237 deletions.
4 changes: 0 additions & 4 deletions docs/arch/_catagory_.json

This file was deleted.

Binary file removed docs/arch/img/arch.png
Binary file not shown.
90 changes: 0 additions & 90 deletions docs/arch/overview.md

This file was deleted.

5 changes: 0 additions & 5 deletions docs/background/_catagory_.json

This file was deleted.

17 changes: 17 additions & 0 deletions docs/burst-threshold.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: Burst Threshold
slug: /protocol/burst-threshold
---

:::info
The Burst Threshold is Puffer's commitment to Ethereum's Ethos.
:::


### Burst Threshold

Puffer is [committed to self-capping](https://twitter.com/puffer_finance/status/1697817894900711700?s=20) its validator marketshare to 22% of Ethereum’s validator set, which we refer to as the protocol's *Burst Threshold*. Instead of abruptly pausing staking and NoOp registration once the burst threshold is reached, Puffer introduces a mechanism to organically reduce staker demand as the protocol reaches the threshold.

As the protocol reaches 22%, the number of mintable validator tickets will be reduced such that it can only sustain existing validators but not new ones.

This pledge is critical to ensure that the Puffer Pool never breaches the [dangerous consensus threshold of 33%](https://twitter.com/dannyryan/status/1688644951230267392?s=46&t=bsdBaPIHlTHEWDDdVUJW4g), which threatens the stability of Ethereum. We firmly believe that the burst threshold must be included from day one rather than after the protocol is profitable.
Loading

0 comments on commit 4647516

Please sign in to comment.