lean by design

Our Team

Eugene Luzgin

Eugene Luzgin

Founder & Chief of Technology

Founder of The Tribe and the technical mind behind our BP operations, Eugene has been active in different areas of cryptography, software engineering, and cybersecurity for over 20 years for government, fortune 500 and startup brands. His contributions to the EOS network are numerous, including founding and organizing EOS SLC, the SES Network EOS Wallet project as well as the EOS Arrowhead and EOS Net Testnet. Eugene has been active in the community internationally since the very beginning, and he looks forward to working with the platform and community for many years to come.

Eugene Luzgin

Steve Floyd

Founder & Chief of Strategy

A lifelong learner of computer science and design theory, Steve has been working in different facets of the web for over 15 years, primarily in User Experience Design and Content Strategy. Steve brings a broad range of entrepreneurial experience to The Tribe and helps the organization think practically about operational and marketing decisions. Steve has also contributed significant time to building the EOS ecosystem through community projects, such as his work with the EOS Rise events, leading the user experience architecture for the Chintai token leasing platform to name a few.

a better future

Our Vision

To leverage, build and promote distributed systems that secure life, liberty, and property for all.

the foundation

Our Core Value

1. People Are The Purpose

We believe that everything we do for EOS is to enrich the lives of people across the globe. People are the reason we do what we do and we try to never lose sight of that.

2. Purpose Over Duty

We will never waiver from our duty of keeping the EOS network stable and secure because of our commitment to the people on the network we serve. We believe doing the right thing while abiding by the rules outlined in the EOS constitution is always our true north in every decision we make. At the same time, we do not operate as a heartless machine, as those are the very types of organizational structures and processes we are trying to free ourselves (and others) from. 

3. Trust Over Control

Block producer trust is paramount for a governed blockchain to function. We embrace the wisdom of the crowd, always leading from behind, humble stewards who only give direction if and when we can truly add value.

4. Transparency Over Position

Our loyalty is always to the EOS token holders and network, not our positions/affiliations. Transparency around our associations and financial interests is more than just a line item in our core values, it's the center of our entire brand promise and communications strategy. If elected we will provide a public wallet address for anyone to audit (and have suggested publicly that other BPs do the same).

5. Integrity Over Pride

Integrity is our lighthouse and the only metric that matters in the outcome of decisions we make. The root of many indiscretions among the human race is often rooted in pride. Greed and many selfish acts are simply projections of self-pride and preservation. Staying rooted and down to earth is very important to The Tribe culture. Integrity in our work, our dealings with others and especially any and all affairs relating to the EOS network are among our highest ideals. 

rules of the node

Our Constitution

After careful consideration, we have chosen to adopt a personal constitution inline with the proposed EOS draft constitution that has been brought forth by the community. We stand behind all the principles in this draft with only one exception - the frequency of security audits. We have opted for quarterly security audits rather than six per month that was proposed as we believe that to be sufficient. As with all things EOS, are always open for more debate on this subject if others do not agree. We have created our own version of this draft constitution you can download here.

truly decentralized

Technical Specifications

EOS Tribe is working in April / May 2018 on laying down the necessary infrastructure for running fault tolerant block producer operations. As some of the most important criteria for a truly decentralized network, we have chosen implicitly to not rely on third-party cloud services and instead choose to run on quality hardware we control and configure in secure hosting locations.

Primary Node

Primary Node

For a primary block producing node, we selected Wyoming state for its favorable state laws. We are currently considering multiple colocation services providers in the state of Wyoming who are independently owned and who also utilize either some or almost all green energy to operate.

The primary node configuration will include a Gigabit-capable security router that will distribute requests to the primary producer node (Intel Xeon 3120A server specs below) and will fall back to our backup server running a full node.

Both servers will be using a file server with additional 80TB storage. Servers will be connected to each other and the file server will be on a gigabit network switch with a lightning fast 10GB fiber internal connection.

In addition, the incoming Internet to the router will be a 1Gb low latency connection.

We are running Ubuntu 17.10 on both servers with hardware specs below:

  1. Cisco CISCO891-K9 891 Gigabit Ethernet Security Router
  2. Intel Xeon Phi 3120A Heptapentaconta-core (57 Core) 1.10 GHz Coprocessor
  3. Intel Xeon Phi 3120A Heptapentaconta-core (57 Core) 1.10 GHz Coprocessor
  4. RAM 448 GB equally divided between servers. (Upgrades to RAM in primary) 

Secondary Node

We want to be sure to account for total power loss at primary location due to natural disasters or any unforeseen reason. Hence we are establishing a second backup full node in a secure location in Bluffdale, Utah. This infrastructure is currently live as we write this and has already proven itself running nodes on multiple testnets (EOSNetArrowheadJungle).

This location runs Ubuntu v16.04 on Enterprise Dell PowerEdge R710 2.93GHz 8-Core Server | 64GB RAM | 9TB of internal storage. We are planning on upgrading the RAM shortly after launch to match the primary backup node RAM size and adding a file server with at least an additional 40 TB of storage as well. 

We will be launching with our own custom-built server "Geronimo" which we have already acquired, is already built and are currently preparing for deployment during late April / early May.

Overall Infrastructure & Cloud Load Balancing

We have selected to run application load balancing between two location as a microservice in a hybrid mix of distributed AWS, Digital Ocean & Linode Cloud infrastructure - and from multiple personal and business accounts for fault tolerance and independence of both locations. 

This will be the only way we utilize any centralized cloud infrastructure in our stack, and even then we are taking precautions to have nodes readily available that can be spun up from multiple services and different accounts in the event one is shut down.

In the unlikely event of power loss at any one location - AWS / Digital Ocean / Linode cloud application load balancer will be able to detect a primary node down situation and trigger block production for another backup node in our alternative Utah location.

Additionally, we may be renting alternative backup server nodes from other BPs in other geographical locations for fall back scenario and have already started the negotiating process with leading BPs in various strategic geographic locations in the EU and South America.

© 2018-3030 EOS Tribe. Announcement | Ownership | Infrastructure | BP Agreement | bp.json