Quantcast

GenerEOS Sydney

GenerEOS Sydney wiki, GenerEOS Sydney review, GenerEOS Sydney history, GenerEOS Sydney founders, GenerEOS Sydney motto GenerEOS Sydney ownership, GenerEOS Sydney email, GenerEOS Sydney address, GenerEOS Sydney phone, GenerEOS Sydney headquarters GenerEOS Sydney news, what is GenerEOS Sydney, where is GenerEOS Sydney GenerEOS Sydney wikipedia
GenerEOS Sydney revenue, GenerEOS Sydney employees, GenerEOS Sydney location, GenerEOS Sydney facts

GenerEOS Sydney is an EOS block producer​ candidate with a mission of promoting and supporting scalable and highly reliable block production whilst giving back block rewards to charities. [1]​ Their mission is to re-engineer the way funds are distributed to charities, through the introduction of fully transparent smart contracts and DApps. [2][3]

 

Image
Another logo of Genereos. 

This revolutionary way of bringing a community together as a co-operative is made possible by the EOS.IO software. They strongly believe they are at the forefront of a new era of bringing decentralised technology into the mainstream. [4]

 

 

Based out of Sydney, Australia​, GenerEOS is founded by a team of like minded blockchain enthusiasts with diverse backgrounds and a passion to make a difference in the world and fostering the spirit of generosity by giving back. [5]

 

Their Block Production is also located in Sydney, Australia​. [6]

 

 

Youtube Video
MULTISIG on EOSIO Explained - GenerEOS.

Checklist

Public Presence

Website: https://www.genereos-sydney.io/ [7]
Steem: https://steemit.com/@genereos [8]
Reddit: https://www.reddit.com/user/GenerEOS [9]

Github: https://github.com/generEOS [10]

Medium: https://medium.com/@generEOS [11]
Facebook: https://www.facebook.com/generEOS [12]

 

 

ID on Steemit

 

  • SteemIt ID: @Genereos [13]
  • Official Name: GenerEOS [14]
  • Location of company headquarters: Sydney, Australia​ [15]
  • Expected location of servers: Sydney, Australia​ [16]
  • Type of servers: 244 GB RAM / 8 CPU in AWS and GCP [17]
  • Current employee list (with background info):
    • Tim Weston (Business Strategy)
    • Nathan Rampel (Smart Contracts and Infrastructure)
    • Ralf Weinand (Block Producing and Infrastructure)
    • Tom Fu (Marketing)
    • Tai Tran (Content And Community) [18]

 

Youtube Video
How are Transactions Feeless on EOSIO?

Tech Specs

During the initial testnet phase they have been experimenting with different configurations in Amazon Web Services (AWS) as well as Google Cloud Platform (GCP) environments. [19]​ They’ve joined several testnets including Jungle and Scholar and currently, they actively participate in community discussions regarding different BIOS boot process options. [20]

 

Their team is researching and practicing the automated / scripted and fully transparent boot process proposed by EOS Canada. They are also exploring the alternative more manual / secretive / security-optimised boot process proposed by HKEOS, EOS RIO, EOS Tribe and other block producer candidates and individuals of the EOS community using Wiregard VPN and secure communicate channels like keybase for exchanging sensitive information (as well as a combination of the two options). They are fully prepared to go with either of these options and will continue to explore those and other BIOS boot processes with the block producer candidates community in readiness for the mainnet launch. [21]

 

Youtube Video
EOSPHERE chat with GenerEOS at the EOS Sydney Meetup.

Failover & Load-balancing

Together with many other block producer candidates, they are discussing and researching different approaches for block producer-node failover and load-balancing solutions as there is currently no built-in support within the EOS.IO software to allow multiple distributed nodes to share the load of producing blocks. If multiple block producing nodes of one appointed or elected block producer are configured to produce blocks with the same signing key at the same time and broadcast those blocks to the network this would result in conflicts and the block producer would very quickly be voted out. [22]

 

Yet, only having one producing node (which solves the aforementioned problem) is not a prudent setup for a serious block producer candidate who wishes to provide as close to 100% up-time (with no missed blocks) as technically feasible. Ideally, they would like full load-balancing support to be implemented by BlockOne before mainnet launch. As this option looks unlikely, they are also researching different approaches to overcome this issue. [23]

 

Scaling Plan

As with most block producer candidates their initial infrastructure set up for the mainnet launch day will look very different from what they envision as their medium-term ideal infrastructure. As a fully self-funded block producer candidate, they need to finely balance the computational, memory, storage and network requirement of the EOS.IO network with their financial risk appetite. They have therefore opted for a cloud-based approach in our initial endeavours of being elected as an EOS.IO block producer. This provides them the required flexibility and agility needed before and shortly after the mainnet launch at a calculable financial risk. [24]

 

AWS instance types 1xe and GCP’s n1-ultramem series allow them to scale their nodes to 4TB RAM, 160 CPUs, 2x2 TB SSD and 25 Gbit of peek network bandwidth in a matter of minutes. By the time the EOS.IO network requirements outgrow established cloud providers’ hardware options, they will be in a financial position to architect, implement and maintain our own server centres and customise them to the specific needs of the EOS community. [25]

 

During their ongoing mainnet launch preparation and participation in various testnets, they are mainly working with small virtual server configurations (8 GB RAM / 2 CPU machines on AWS as well as GCP). For their participation in performance testnets (which are yet to be scheduled for after the official Dawn 4 release) they are planning to upgrade their producing nodes to 122 GB RAM / 4 CPU machines. They are also experimenting with auto-scaling options for their array of smaller size non-producing nodes. [26]

 

They will determine our initial server size for the mainnet launch according to the results of our performance tests. Based on discussions with other block producer candidates they were initially planning to provision servers equivalent to AWS EC2 x1e.2xlarge machines for their block producing servers (i.e. 244 GB RAM / 8 CPU) in AWS and GCP. [27]

 

Community Projects

Fireside Chat

Whilst GenerEOS will primarily give back to the community through their charity work they will also keep the EOS and wider community updated. Their Fireside chats will be a podcast themed update series that keeps the EOS community informed of EOS and blockchain related updates. This will be a less formal way for them to communicate with their followers and the EOS community on what has been happening in the space and for them to get a chance to understand the work they do as a block producer. [28]

 

They will specifically cover these topics to ensure that you as the community stay engaged and informed of all the new updates and progress that EOS is making: [29]

  • Interviews and discussions with other block producers
  • General EOS updates and news
  • Airdrop updates for EOS
  • Interviews and discussions with new projects on the EOS blockchain
  • Exploring and breaking down complicated technical updates [30]

Meetups

Team GenerEOS are active participants at Sydney’s Blockchain meetup events. Our Community and Content Partner, Tai, runs the Crypto Traders Sydney meetup, where attendees gather to discuss Crypto trading, Technology and other developments, including EOS, in a relaxed and friendly setting. Tai also guest MCs at the Bitcoin Crypto Sydney meetup attracts a different set of attendees. [31]

 

Furthermore, they actively work at building their relationships with the other Australian Block Producer candidates, having helped promote their message on Youtube and and assisting with venue selection for their Sydney gatherings. [32]

Community Presence

GenerEOS has participated in the EOS Jungle Testnet (Koala) and Scholar testnet (EOS Sydney). [33]

 

Participating in the ongoing improvement and development of the aforementioned testnets has given us great insight into adapting to the changing conditions in the network. Actively supporting and working with other block producer candidates has been a challenging and rewarding experience that ensures a healthy ecosystem. [34]

 

GenerEOS worked closely with the VP of product at Block.one to analyse modelling for - Block Production revenue analysis. This collaboration has given us a deep understanding of the economic. [35]

 

Telegram + Testnet

 Telegram: https://t.me/joinchat/FfqLYBDQkv5vSkiLsh34IA [36]

Testnet:

During the initial testnet phase we have been experimenting with different configurations in Amazon Web Services (AWS) as well as Google Cloud Platform (GCP) environments. They’ve joined several testnets including Jungle and Scholar and currently, they actively participate in community discussions regarding different BIOS boot process options. Their team is researching and practicing the automated / scripted and fully transparent boot process proposed by EOS Canada. [37]

 

They are also exploring the alternative more manual / secretive / security-optimised boot process proposed by HKEOS, EOS RIO, EOS Tribe and other block producer candidates and individuals of the EOS community using Wiregard VPN and secure communicate channels like keybase for exchanging sensitive information (as well as a combination of the two options). They are fully prepared to go with either of these options and will continue to explore those and other BIOS boot processes with the block producer candidates community in readiness for the mainnet launch. [38]

 

Image
The Genereos RoadMap.

Block Producer Roadmap

Their Roadmap illustration. [39]

Position on Dividends

GenerEOS will not engage in any form of vote buying nor will it give dividends to voters and will do everything in its power to stop this occurring in the ecosystem. [40]

All information for GenerEOS Sydney's wiki comes from the below links. Any source is valid, including Twitter, Facebook, Instagram, and LinkedIn. Pictures, videos, biodata, and files relating to GenerEOS Sydney are also acceptable encyclopedic sources.
This is a discussion about GenerEOS Sydney. Concerns about the topic, its accuracy, inclusion of information etc. should be discussed here. Off-topic discussion not pertaining to GenerEOS Sydney or this wiki will be removed.
Other wiki pages related to GenerEOS Sydney.
Created: 05/29/2018 05:35:03 PM UTC
Last Modified: 08/15/2018 05:04:51 PM UTC