Skip to content
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

Correct 2 typos #564

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
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
4 changes: 2 additions & 2 deletions packages/docs/src/pg/src/plasma/operator.rst
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ Being censored obviously isn't great, but it's not as bad when you can always ta
Decentralizing the Operator
===========================
The one thing that wasn't really mentioned here is the fact that the "operator" can actually consist of multiple people making decisions about what blocks to publish.
This could be as simple as a having a few designed people who take turns making blocks, or as complex as a Proof-of-Stake system that selects block producers randomly.
Either way, it's complicated than just having a single person run everything, but it's probably the way to go for projects that want to get rid of censorship.
This could be as simple as a having a few designated people who take turns making blocks, or as complex as a Proof-of-Stake system that selects block producers randomly.
Either way, it's more complicated than just having a single person run everything, but it's probably the way to go for projects that want to get rid of censorship.
At the same time, it tends to be unimportant research-wise whether the operator is a single person or many people.
As a result, you'll often see people just assuming the operator is a single person for simplicity.