Skip to content

Fix last link in the vanilla blocks info into smooth doc #448

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,3 +39,5 @@ $ GIT_USER=<Your GitHub username> yarn deploy
```

If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

### Contributing
6 changes: 4 additions & 2 deletions docs/smooth/deep-dive-into-smooth/vanilla-blocks.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,8 @@ title: What is a vanilla block?

---

**What is a vanilla block?**



In the context of the Smooth protocol, we define a vanilla block as a block build locally by the execution client, as opposed to a block built by professional block builders with sofisticated algorithms for extracting MEV and sometimes private transactions that do not appear in the mempool.

Expand All @@ -29,4 +30,5 @@ Update Your Node Configuration: If you are running a validator in Smooth, make s
**How does Smooth act on Vanilla blocks?**

In order to maximize the rewards for all the participants in Smooth, vanilla block proposers will be banned after 3 consecutive vanilla blocks proposed if they had the chance to be MEV blocks/had MEV opportunity.
This banning process requires a voting phase by the SmoothDAO to effectively ban the withdrawal address of the validator. You can read more about it [here](https://https://discourse.dappnode.io/t/proposal-sip1-smooth-terms-of-use-policy/2388)
This banning process requires a voting phase by the SmoothDAO to effectively ban the withdrawal address of the validator. You can read more about it [here](https://discourse.dappnode.io/t/proposal-sip1-smooth-terms-of-use-policy/2388)

Loading
Loading