QUOTE(whyseej00 @ Feb 21 2020, 10:04 PM)
Please ask your boss why is he scamming HGT early investors?
Did not fulfil his promises and 0 development in that space.
To say that we have not spend significant effort on the blockchain is wildly off the mark. Bearing in mind that we started building the blockchain back in 2017 when the technology was very nascent, we have done a number of things which we wouldn’t have tried then if we knew then what we know now.
We tried to replace CWS (transaction engine written in Ruby) with blockchain where every transaction was recorded in blockchain with plan to connect HG mobile clients directly to our blockchain nodes.
To support that idea, we designed the HG mobile clients that we have today to create a key and store it securely when user signs up / recover account and it's not stored in the cloud. It works like multisig contract.
On consensus side, we first tried with PoW (Geth), followed by PoA Clique (Geth) and lastly on PoA Aura (Parity).
We developed our own ERC20 token explorer as well (front-end in React, back-end in Go).
When all this was completed and when we ran the blockchain transaction engine in parallel with CWS for few months, we found that it was too slow and couldn't catch up with CWS.
The first migration itself took us around 20 hours to generate keys, deploy smart contracts for our customers (we saved private keys in server for our customers in the first phase of the project), airdrop ETH and MYR/GLD tokens.
We also built helper daemons that monitor keys with low ETH balance and auto-topup them with ETH from coinbase/etherbase account.
We also built an API service for CWS to call when customer completed account recovery (to change multisig owner from old key to new key). But, we have no chance to integrate it with CWS because the focus was just to evaluate blockchain performance at handling big transactions capacity and not covering all mutation points in CWS.
We then moved to PoA Parity and removed the gas requirement when submitting transactions - but we still couldn't catch up with CWS transaction speed.
Next we changed our strategy and focused on DB backups where we store DB hashes in the PoA chain (hourly and daily) and form merkle root tree using the hashes. And this is where we are at