This is a continuation of Part 1 here. In part 1, I wrote a wrapper to call Citibank's API. In this part of the tutorial, I call the RESTful wrapper services that I wrote in part 1 to give users an interface to see their accounts and transfer funds to external accounts.
I run geth on my cloud server to sync with the Ethereum Blockchain. I start geth whenever I code and it goes into a round of resynchronization with the Blockchain. This takes anything from minutes (that's if the last time I code is yesterday), or hours (if the last time I did this was months ago).
As of the time of writing, Ropsten (which I work on because ETHs are free here) is in block 1,911,915 and the main ethereum has reached block 4,399,227. If you do a complete sync, it will take you 2 to 3 days or more.
This is a continuation of the Going Dutch Smart Contract project that I started on 2nd Sep 2017. It has been a month, which is probably the equivalent of a year if you count in blockchain-time. Geth has gone from 1.6.7 to 1.7.2 and after upgrading my setup, I had to let it run overnight (in fast mode!) to sync my node to the block again.
This is a continuation of my post about Ethereum on the Cloud and Smart Contract execution with MetaMask. MetaMask is a Google Chrome extension and runs only on desktops. I wanted to execute Dapps on a mobile device on the go. Enters Status. Status is a mobile application on Android and iPhone. It allows you to run Decentralized apps, stores your ETH in a wallet and send/receive ETH from another person. It also runs like chatbot.
In part 1, I developed the Zoe Helper hardware, a button that sends a Sigfox message to the Sigfox backend, and through a callback, route the message to jacksonn.org.
In part 2, my web API at jacksonng.org takes the message, determines who the recipient is, and send it as a notification to my OneSignal account. OneSignal then forwards it to Firebase and then to the mobile device that has been configured to receive this notification.
In part 3, I develop a Cordova mobile app to display the message on the mobile device.