Overview on Technical Aspects of Our Latest Galton Version Update

Hi, I’m Amit the CTO of Stox.

I’m here to review the technical aspect of the last version, released on 25th December 2017.

In this highlight of the version, we integrated the Stox Galton integration with the Ethereum Blockchain. Up until now, all the predictions were done within our central Stox Server. In Galton, we’ve added two new major components:

A Private Ethereum Node running our Smart contracts

Private Ethereum Node — This Node runs a local instance of the Ethereum Network. Every prediction that the users perform over the Stox website is sent to this Node. Private Node means that predictions aren’t sent yet to the public Ethereum network (sorry, no Etherscan just yet, but as you know from the Roadmap, it is coming). We prefer deploying our Smart Contracts on a private node where we have full control, and only after extensive testing we’ll deploy it to a test on the public network. In short, it is about safety first and ensuring full scalability prior to finalised release.

2. Stox API based on Node.JS that connects the Stox Server to the Private Ethereum Node over Json RP /Web3.

Stox Blockchain API — Smart contracts are all nice and well, but without an API to connect our server, we can’t use do anything over the Ethereum Network. Thus, the Stox Blockchain API web3 interface over Json RPC is to connect our Stox server to our Ethereum Node.

So, here’s what that means: we store the predictions and all the relevant data (i.e. dates, outcomes), the user’s votes, user data (accounts) and their balance, which is also on the blockchain.

A short background of the architecture:

The standard flow is commenced with the client side base on React.JS, execute by the server via Node.JS. The data is stored on the PostgreSQL database. And now, we replicate the relevant data to the blockchain via the Stox API based on Node.Js.

To view the captions, please simply click settings & captions.