wiki, review, history, founders, motto ownership, email, address, phone, headquarters news, what is, where is wikipedia revenue, employees, location, facts is an EOS block producer ​ candidate with the mission to translate their knowledge and skills the Blockchain ​ space, and into a positive and dependable platform while helping the EOS community achieve great things through thoughtful action. [1] [2]

Logo of SaltBlock that has been shared on their Website.

The company will have their Block Production servers in Salt Lake City, Utah ​. [3] [4]


Public Presence

Website URL: [5]

Twitter: [6]

Illustration of the SaltBlock values.

ID on Steemit


Adrian Hunter

Adrian is currently a Technical Specialist at Google in Paris, France ​ where he focuses on solving technical challenges on demand side platforms and scaling programmatic solutions across Europe. Adrian was introduced to computers and technology at a young age and has made them a part of his life both personally, and professionally. [14]

He co-founded Geekbox, a high-end custom gaming PC company and systems integrator, which was acquired in 2013. Through his personal and professional experiences, Adrian brings a unique skillset to the EOS ecosystem. He has proven to be an inclusive community builder, technical collaborator, and overall motivator as he continues his work with EOS contributors. [15]

Marshall Anderson

Marshall is the president and owner of Tektonic, an IT infrastructure management company in Salt Lake City, Utah ​. Through his company, Marshall specializes in maintaining the availability of Tektonic's clients' critical infrastructure. [16]

With a long history of successful technology startups, Marshall has honed his skills as a technology leader. Marshall is able to combine his pragmatism, empathy, and patience with technical knowledge to provide solutions and to empower others. He brings his value system, a wealth of technology expertise, leadership, and genuine passion for blockchain technology to the EOS community. [17]

Tech Specs

They believe for the EOS network to achieve its full potential it requires smart design when it comes to the infrastructure it runs on. A network map that is subject to change is available based on new information that they may receive in the future regarding the EOSIO software. [18]

They’ll be hosting their own hardware in a datacenter located in Salt Lake City. This gives them a secure and highly redundant home for our hardware that will reduce the possibility of downtime. [19]

The facility features redundant power systems, backup generators, biometric security, fire suppression, redundant cooling systems, and multiple upstream internet providers. The datacenter is also powered using energy that is 100% wind-generated. [20]

Illustration of the SaltBlock Block Producers.

Design Decisions


Along with the datacenter being completely N+1 redundant, they’ll be implementing redundant hardware themselves to give them some resiliency when it comes to issues and failures. [21]

Active/Passive Firewall/Routers

They’ll have 2 Firewall/Routers working in an active/passive high availability pair. This means they can lose complete functionality on one of their firewalls and continue to operate. This also gives them the ability to update firmware and change network configurations without taking the network offline. [22]

Failover Cluster

Their servers will be running in a failover cluster configuration using shared storage. They’ll be running EOSIO nodes inside of virtual machines hosted on this failover cluster. This means either ClusterNode1 or ClusterNode2 can run any or all of their virtual machines. In the event of a hardware failure on one of their cluster nodes, they can instantly migrate their block producing or full nodes to the other cluster node with no downtime. [23]

Running a failover cluster also allows them to easily move virtual machines off of a particular cluster node when they need to update the underlying operating system. They’ll live migrate the virtual machine from one cluster node to the other, update the operating system, and then migrate the virtual machine back to the original cluster node. [24]

Upgrading their hardware is also made easier by using a cluster. When they upgrade our infrastructure, they’ll be able to live migrate our EOS nodes to the new hardware with no downtime. [25]

They’ll be using 2 direct attached storage arrays to host their virtual machines. This gives them storage redundancy in the event an entire storage enclosure fails. This is easily expandable in the future to include more enclosures and capacity. [26]

Load Balancing

They’ll be using a hosted load balancer to handle requests from their full nodes. This will give them the ability to offer a reliable service for anyone wanting to query the blockchain. It will also allow them to continue adding more infrastructure seamlessly down the road as requests increase. [27]

Cloud Hosted Backup Node/Producer

They’ll be running a non-block producing node on Microsoft Azure to be used in the unlikely event there’s downtime at their primary location. They’ll switch from non-producing to a block producing node to make sure there’s no significant downtime while they bring their primary site back online. [29]

They chose to use Azure as it seems to be less popular than Amazon amongst block producer candidates. This will give the network some resiliency in case there’s any Amazon specific downtime. [28]


They're monitoring their hardware and software using PRTG. PRTG uses SNMP to query our infrastructure and alerts them via email to any warnings or failures. [29]

Current Hardware Specs for Testnet

Cluster Nodes - 2x Intel Xeon@2.93Ghz 192GB RAM
Shared Storage – 12TB of SAS storage for each device (upgradable to 120TB each)
Firewalls – 7.4Gbps throughput [30]

Scaling Plan

They plan to scale their hardware as needed. The community is still in the process of figuring out benchmarks and what specifications may be required. Should they need to upgrade hardware before launch, they're prepared to do so. Their design decisions give them the ability to either upgrade current infrastructure or install new hardware with little or no downtime. [31]

They anticipate upgrading their Cluster Nodes to servers with larger amounts of installed RAM and larger RAM capacity (1TB+) they'll be able to install new servers into their failover cluster and decommission old hardware. [32]

They’re currently running on a WAN port provisioned at 1Gbps. Should/when they need to scale to 10Gbps they can do so easily on the WAN side. They'd then replace their firewalls with higher throughput models to achieve 10Gbps+. [33]

Scaling their storage means adding more drives to our shared storage hardware. Currently they are using SAS drives. Should they need SSD storage, they’ll be installing new DAS/SAN enclosures. [34]

Community Projects

They’ve been involved in the Community Testnet spearheaded by Eric (@xebb/ Along with other great block producer candidates and individuals, they’ve been running a block producing node since the beginning of the testnet. [35]

SaltBlock producer name on Community Testnet: Spiderman [36]

Telegram + Testnet

Telegram: [37]


The aim of EOS Portal is to become a tool to be used by the sprawling ecosystem. Developed as an open source project by the community, for the community. The Portal will allow participants to both identify and advocate for likeminded voters, proxies and BPs among the global community of interested contributors. [38]

This is a community driven project, with participation from:

Eric @

Michael Yeates @

Adrian/Marshall @

Zara @ EOS Brazil

marcin @ EOS Green

David P @ EOS42 [39]

Block Producer Roadmap

  • They are currently finalizing their launch infrastructure for the EOS launch in June. They previously released a network diagram that will change slightly. They’ll be releasing an updated diagram before launch. [40]

  • They continue to participate in multiple EOSIO testnets. They’ve been a member of the original community testnet since the beginning and plan to continue even after EOSIO is released. [41]

  • They’ll be part of the community launch group along with many other Block Producer candidates on June 2nd. Finalization of the boot method is currently underway. [42]

  • If elected, they’ll be duplicating our infrastructure to another geographic location to provide extra redundancy and resiliency. They already have a cloud VM running as a failover in the case of an outage at our primary location. [43]

  • After establishing SaltBlock as a reliable and trustworthy Block Producer, they’ll be bringing on additional development staff to focus on application development to enrich the EOS ecosystem. [44]

  • Increase their storage capacity in preparation for EOSIO storage. Plan for multi-threading by upgrading our infrastructure with new servers. [44]

Position on Dividends

SaltBlock is first and foremost focused on being a reliable and trustworthy Block Producer. They believe the most important responsibility of an elected Block Producer is to reliably provide service to the network. Without reliable Block Producers, the EOS ecosystem will suffer. [45]

The company believes that offering dividends or buying votes may negatively affect the health of the EOS network. They believe the BPs with the best track record of block production and community involvement should be elected. When the EOS network is healthy, the voters will reap the rewards through a more valuable ecosystem. They believe there’s a way to give back to the voters through EOS development and community involvement and not by directly paying for votes. [46]

For those reasons, SaltBlock doesn’t plan to offer dividends or pay voters directly for their vote. They plan to show the community we’re worth voting for based on our reliability, honesty, and our contributions to the EOS ecosystem. [47]

All information for's wiki comes from the below links. Any source is valid, including Twitter, Facebook, Instagram, and LinkedIn. Pictures, videos, biodata, and files relating to are also acceptable encyclopedic sources.
Other wiki pages related to