Seems my days and night are completely switched around at the moment. It's currently just after midnight and for breakfast I'm hoovering down a few handfuls of Jelly Belly jellybeans for breakfast and getting my ass in gear in an attempt to get a Hive.Loans and Hive Side Chain public alpha test going here in the next week or two, with the Hive.Loans launch date goal creeps up closer and closer it's starting to become a bit more stressful, however stress is a great motivation tool for me. :)
After struggling a wee bit over the week with getting a HIVE bridge properly implemented into the Hive Side Chain (HSC) in order to facilitate the properly permissioned / authorized remote deployment of some smart contracts written in Solidity that will end up making the backbone of the Hive.Loans (HL) core business logic. While having gotten the bridging between the 2 chains to successfully initialize and properly parse blocks coming in with basically real-time side chain reaction speed and surprisingly stable connection between the two node it looks to me that the "Hacky" looking hiverpc-go library I cobbled together from an abandoned library targeted for use on the old chain without paying proper attention to how that process would handle somewhat important things like "how should I shut down? or my personal favourite "SIGTERM has been detected, Yeaaaaah, Fuck you I'm not shutting down"..
Now obviously for the software architects amongst the crowd gathered around you're either muttering to your self or shouting heckles along the lines of "Incompetent Fool! The Library is fine, you're just buggering up your GO syntax and have the tom implement you shutdown context properly and this may very well be the case, however in the drive to do things better and be t service of the HIVE network has me rewriting an old "steem-go" into a HIVE version and modernizing it's calls.
I'll make the new Hive-go library that will be getting used on the HSC a public release as well so other programmers using GO are able to easily interface with the HIVE blockchain in the future.
