Is EOS full decentralized?
up vote
2
down vote
favorite
Today, I research how to people can vote 21 BPs in EOS system, so I am wondering, is EOS full decentralized or it still uses a server center?
voting
add a comment |
up vote
2
down vote
favorite
Today, I research how to people can vote 21 BPs in EOS system, so I am wondering, is EOS full decentralized or it still uses a server center?
voting
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Today, I research how to people can vote 21 BPs in EOS system, so I am wondering, is EOS full decentralized or it still uses a server center?
voting
Today, I research how to people can vote 21 BPs in EOS system, so I am wondering, is EOS full decentralized or it still uses a server center?
voting
voting
asked 3 hours ago
Onotoko
267
267
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
DPoS (the consensus Algorithm of EOS.IO) is a trade-off between full decentralization and speed.
While PoW algorithms allow almost all nodes on the network to create blocks, DPoS gives this privilege to selected Block-Producers (BPs). These are elected by the community. 21 in EOS that are active and 21 in stand by if some BP fails.
In theory BPs should be heterogeneous and geographically distributed. There are several guidelines how to select "good" BPs. Also the community profits from BPs that have their own servers. If all the Nodes are setup on the same cloud e.g. AWS there would be less decentralization.
The actual state of decentralization depends on the active BPs. You can check them e.g. here. Almost every BP has a website or information why you should vote for them. Also reddit has good information about trustful BPs and the latest activities.
However DPoS is often criticized for the whales (people/institutions that hold many tokens - voting power). They may vote multiple BPs they like or they participate with into the pool. Nevertheless the technology is able to provide a good grade of decentralization.
add a comment |
up vote
0
down vote
EOS does not have a central server or a single point of failure.
All 21 block producers can be replaced and there is a reserve pool 100 block producers waiting at any moment.
Here you get a geo map of active producers https://www.eos-radar.com/
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
DPoS (the consensus Algorithm of EOS.IO) is a trade-off between full decentralization and speed.
While PoW algorithms allow almost all nodes on the network to create blocks, DPoS gives this privilege to selected Block-Producers (BPs). These are elected by the community. 21 in EOS that are active and 21 in stand by if some BP fails.
In theory BPs should be heterogeneous and geographically distributed. There are several guidelines how to select "good" BPs. Also the community profits from BPs that have their own servers. If all the Nodes are setup on the same cloud e.g. AWS there would be less decentralization.
The actual state of decentralization depends on the active BPs. You can check them e.g. here. Almost every BP has a website or information why you should vote for them. Also reddit has good information about trustful BPs and the latest activities.
However DPoS is often criticized for the whales (people/institutions that hold many tokens - voting power). They may vote multiple BPs they like or they participate with into the pool. Nevertheless the technology is able to provide a good grade of decentralization.
add a comment |
up vote
1
down vote
DPoS (the consensus Algorithm of EOS.IO) is a trade-off between full decentralization and speed.
While PoW algorithms allow almost all nodes on the network to create blocks, DPoS gives this privilege to selected Block-Producers (BPs). These are elected by the community. 21 in EOS that are active and 21 in stand by if some BP fails.
In theory BPs should be heterogeneous and geographically distributed. There are several guidelines how to select "good" BPs. Also the community profits from BPs that have their own servers. If all the Nodes are setup on the same cloud e.g. AWS there would be less decentralization.
The actual state of decentralization depends on the active BPs. You can check them e.g. here. Almost every BP has a website or information why you should vote for them. Also reddit has good information about trustful BPs and the latest activities.
However DPoS is often criticized for the whales (people/institutions that hold many tokens - voting power). They may vote multiple BPs they like or they participate with into the pool. Nevertheless the technology is able to provide a good grade of decentralization.
add a comment |
up vote
1
down vote
up vote
1
down vote
DPoS (the consensus Algorithm of EOS.IO) is a trade-off between full decentralization and speed.
While PoW algorithms allow almost all nodes on the network to create blocks, DPoS gives this privilege to selected Block-Producers (BPs). These are elected by the community. 21 in EOS that are active and 21 in stand by if some BP fails.
In theory BPs should be heterogeneous and geographically distributed. There are several guidelines how to select "good" BPs. Also the community profits from BPs that have their own servers. If all the Nodes are setup on the same cloud e.g. AWS there would be less decentralization.
The actual state of decentralization depends on the active BPs. You can check them e.g. here. Almost every BP has a website or information why you should vote for them. Also reddit has good information about trustful BPs and the latest activities.
However DPoS is often criticized for the whales (people/institutions that hold many tokens - voting power). They may vote multiple BPs they like or they participate with into the pool. Nevertheless the technology is able to provide a good grade of decentralization.
DPoS (the consensus Algorithm of EOS.IO) is a trade-off between full decentralization and speed.
While PoW algorithms allow almost all nodes on the network to create blocks, DPoS gives this privilege to selected Block-Producers (BPs). These are elected by the community. 21 in EOS that are active and 21 in stand by if some BP fails.
In theory BPs should be heterogeneous and geographically distributed. There are several guidelines how to select "good" BPs. Also the community profits from BPs that have their own servers. If all the Nodes are setup on the same cloud e.g. AWS there would be less decentralization.
The actual state of decentralization depends on the active BPs. You can check them e.g. here. Almost every BP has a website or information why you should vote for them. Also reddit has good information about trustful BPs and the latest activities.
However DPoS is often criticized for the whales (people/institutions that hold many tokens - voting power). They may vote multiple BPs they like or they participate with into the pool. Nevertheless the technology is able to provide a good grade of decentralization.
answered 1 hour ago
TeeAttack42♦
1,702224
1,702224
add a comment |
add a comment |
up vote
0
down vote
EOS does not have a central server or a single point of failure.
All 21 block producers can be replaced and there is a reserve pool 100 block producers waiting at any moment.
Here you get a geo map of active producers https://www.eos-radar.com/
add a comment |
up vote
0
down vote
EOS does not have a central server or a single point of failure.
All 21 block producers can be replaced and there is a reserve pool 100 block producers waiting at any moment.
Here you get a geo map of active producers https://www.eos-radar.com/
add a comment |
up vote
0
down vote
up vote
0
down vote
EOS does not have a central server or a single point of failure.
All 21 block producers can be replaced and there is a reserve pool 100 block producers waiting at any moment.
Here you get a geo map of active producers https://www.eos-radar.com/
EOS does not have a central server or a single point of failure.
All 21 block producers can be replaced and there is a reserve pool 100 block producers waiting at any moment.
Here you get a geo map of active producers https://www.eos-radar.com/
answered 1 hour ago
Mikko Ohtamaa
363114
363114
add a comment |
add a comment |
Thanks for contributing an answer to EOS.IO Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2feosio.stackexchange.com%2fquestions%2f3438%2fis-eos-full-decentralized%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown