EOS Block Producer Voting: A Step-By-Step Guide Using the Scatter Browser Extension

The following guide details the process of using the community developed Scatter browser extension and EOS Voting Portal tools to vote for EOS block producers.

Install the Scatter Browser Plugin

1. Visit https://scatter-eos.com to install the Scatter browser plugin. Click the ‘Get Chrome Extension’ button.
2. Click on the ‘Add To Chrome’ button to install the browser extension.
3. Chrome will provide a notification to confirm the Scatter extension has been added to Chrome.
4. Visit https://eosportal.io, the community developed voting portal.

Create a Key Pair in Scatter

5. Click on the Scatter icon in the browser extension tray. Enter a new password and click ‘Create New Scatter’.
6. Click on ‘Key Pairs’ in the Scatter menu.
7. Click on the blue ‘New’ button to create a new key pair.
8. Enter a name (it can be anything), Public Key, Private Key and then click the ‘Save’ button.
9. The new key pair is now stored locally in Scatter.

Create an Identity in Scatter

10. Click on ‘Identities’ in the Scatter menu.
11. Click on the green ‘Use Chain’ button next to ‘Chain Info’ in the upper left of the EOS Portal.
12. Scatter will display a Network Add Request prompt. Click on the blue ‘Accept’ button.
13. Click on the green pencil icon to configure the identity.
14. Select the EOS chain from the drop-down menu that matches the network added in step 12.
15. Select the name of the key pair created in Step 8 from the drop-down menu.
16. Click on the ‘Import’ button below the two drop-down menus.

Pair Scatter

17. Click on the green ‘Pair Scatter’ button next to ‘Chain Info’ in the upper left of the EOS Portal.
18. Scatter will display the Active and Owner accounts. Make sure to select the Active account (@ active).
19. With the @ active account active, click on the blue ‘Use Selected Account’ button.
20. Click on the blue ‘Save’ button to save the pair.
21. Click on the green circle icon next to the pencil icon to display the EOS token balance.
22. Click on the green ‘Pair Scatter’ button next to ‘Chain Info’ in the upper left of the EOS Portal.
23. Click on the ‘Select Identity’ button so that it turns hard blue.
24. Click on the blue ‘Accept’ button to accept the Identity Request.

Vote for EOS Block Producers

25. It’s now time to vote!

Please consider voting for Account ‘stakedstaked’ as a block producer. Our qualification are listed at the bottom of this article. We would sincerely appreciate your support and vote!

26. Click on the ‘Vote’ button next to each block producer to vote. 1 EOS token can be used to vote for up to 30 different block producers. You can search for specific block producer in the search bar above the list of block producers. Once your selections have been made, click on the ‘Vote for Selected Producers ( # / # )’ button above the list of block producers to submit your votes.
27. A Signature Request modal will be displayed with the list of block producers you have selected. Click on the blue ‘Accept’ button to sign the ballot and submit your votes.
28. You should receive a green ‘Voting Successful’ message to confirm that you have successfully voted!

Security Note: Block.one neither developed, nor officially supports the community developed Scatter browser extension or the EOS Voting Portal. Staked makes no representations or warranties with respect to the security of either the Scatter browser extension or the EOS Voting Portal.

Secure Offline Voting

For token holders who would prefer to vote from a secure air-gapped device, we would recommend using Tokenika’s open-source, offline voting tool available on Github at: https://github.com/tokenika/secure-bp-voting.

Tokenika has prepared a video demonstrating the offline voting process: https://youtu.be/_sJYuXOUHCc?t=4m30s

Use the following API endpoint to fetch the chain data: http://eosrpc.staked.us:8888/v1/chain/get_info

About Staked

Staked operates the most secure, performant, and cost-effective block production nodes for decentralized PoS protocols on behalf of investors. Our multi-tier listening and signing node architecture delivers stakeholders the ideal combination of security, scalability and decentralization.

Server Infrastructure

Staked nodes are deployed on high-performance computing resources in a multi-tier configuration that combines security and scalability while minimizing centralization on hardware providers. The infrastructure uses Kubernetes orchestration to ensure high availability and extremely low network latency, and can be scaled on-demand with network growth.

DDoS Protection

AWS Shield, Elastic Load Balancing and advanced IP address obfuscation techniques are used to defend against malicious network, transport and application layer denial of service attacks.

Listening Cloud

The listening cloud is comprised of publicly accessible nodes that dynamically allocate resources from multiple cloud service providers, including AWS, Digital Ocean, and Google Cloud. Orchestrated by Kubernetes, the listening cloud enables near-infinite scale, self-healing and a decentralized hardware infrastructure.

Signing Servers

The signing servers are bare metal servers responsible for producing and signing blocks. They are secured in military grade data centers in the United States, have hardware signing modules for key security, and are fire-walled so they can only communicate with the listening servers.