Taking the initial steps to building on a blockchain can be rather daunting if you don’t know the tips and tricks that will save you hours of development and research time. dfuse is talking to experienced developers in the community so as to pass this valuable information along. This week we spoke with Ross Dold from EOSphere.

Could you introduce yourself?

I’ve worked in IT Integration since 1998, starting as a desktop support engineer and systems administrator. My passion then moved more to the Internetworking and Security space where I progressed through the Cisco Systems education path achieving my CCIE in 2008. I started as an engineer, moved to pre-sales, then solutions-architecture, practice manager and finally professional services management… before I moved to blockchain. I’m certainly more of a hacker than a developer. i.e I can make existing code work for me rather than create it from scratch. I started with mining Litecoin in 2012, then moved to Protoshares / Bitshares, Ethereum, Steemit and finally found EOSIO in 2017. Co-founding EOSphere in January 2018, I now work fulltime on EOSIO initiatives and solutions.

Why did you start EOSphere? What did you envision would set your team apart?

I have always been very pro Dan Larimer’s work, and after he left Steemit I knew his next project would be built with all his past experience and lessons learned in mind. We started EOSphere firstly as an EOS educator in Australia running a series of meetups across the country, it didn’t take long for us to realize that we could add real value to the ecosystem as a Block Producer though our passion for blockchain, education, technical expertise and of course our geographical location. I believe EOSIO is the only blockchain that ticks my three pillars, Performance, Scalability and Developer/User Experience… and let’s not forget about the amazing community. Our strength these days other than our technical expertise and participation in governance is certainly our involvement with the community, support of ecosystem-beneficial services and initiatives as well as our encouragement of building on the EOSIO platform through EOSphere {/dev} and supported dApps.

EOSphere is taking part on many different chains aside from the Mainnet. What does EOSphere use to evaluate each opportunity?

Yes, we are currently running on 9 chains, including the Jungle Testnet. The team decides based on what the sisterchain is trying to accomplish and whether it will bring value to the ecosystem as a whole. Often new chains bring new community and new technical and governance learnings. These communities will most often extend the reach of the EOS Mainnet and learnings used to make the EOS Mainnet stronger. We have also become really good at deployments and have perfected our building block approach to our Data Centre topology.

What are the main challenges when developing on a blockchain? Why did you choose EOS?

In regards to EOS I would say initially it was the lack of developer tools and willingness for heavily invested Ethereum developers to move off solidity. This is certainly not the case anymore and developer support is growing stronger by the day. I chose EOS because of its scalability and performance. I believe that it’s the platform that can actually support and run the dApps that have been conceptualized or have attempted to run without success over the last 3 years on other chains.

You were named as the CTO of Emanate not too long ago. Can you describe the vision of Emanate for those who are not aware? What are some unique challenges the Emanate team is facing?

I met Sean, Jimi and Trent (Emanate Founders) at one of our meetups in Sydney at the beginning of 2018 where we discovered that we share the same passion for EOSIO. It didn’t take long for us to form an EOSphere / Emanate Partnership which ultimately resulted in me being asked to take on the CTO position. Emanate wants to ensure artists are fairly and rapidly compensated for their work, as well as remove the friction between business partners and collaborators on projects where work is shared. As with all startups, funding is always a challenge. Obtaining capital before a product is demonstrable can be quite difficult. However, a unique challenge has been creating a UX for a specific service that has never existed before, how will users / artists / collaborators want to use the platform? In my opinion the Emanate team have done something amazing, with our Alpha platform about to be realized in the next few weeks. You can find out more on the Emanate homepage.

What advice would you give to a developer who wants to get involved with the ecosystem and build a project on blockchain?

From my non-developer point of view, I would say in regards to EOS that the easiest would be to contact you closest EOSIO Block Producer. Join their community, attend their events and offer to get involved with their projects. Not only will you get an introduction to the community, but you will also get a front row seat to opportunities and a platform to share and grow your expertise.


If you think that you have some great insight to share and would like to be featured on “In the Eyes of a Blockchain Developer”, please feel free to reach out to us! We would love to share your story and help inspire the many developers who join the blockchain space each and every day.