For anyone that follows the Odyssey project, you may have noticed some of the ongoing Github releases and updates, likewise counter notified via their social media outlets:

These updates to GitHub further prove the previous rumors and reports of Odyssey’s ongoing efforts for a fully functional OCoin wallet. What is interesting to see is the fact that upon quick inspection of the available assets on GitHub one finds that this application appears to operate as an operational payment solutions platform, with the token $OCN directly utilized throughout.

A higher level view of the GitHub hiearchy shows the following:

OCPay_admin

OCPay_api

OCPay_app_android

OCPay_h5

OCPay_web_admin

My initial summary would point towards an administration both application and web based, with a repository for an Android application, an HTML 5 (h5?) web version, as well as an API for utilization by other applications and platforms (OCPay_api).

For a payment solutions system to truly see real world application, the API element is key. While many users will be apt to utilize the Odyssey wallet, the ability to integrate Odyssey payments to nearly any appropriate web or application platform truly lowers the barrier to general public and real world adoption of the technology, services and token.

Through the API repository you can view the following:

Interestingly enough the terms point towards a wallet application, as well as a recharge function, similar in nature to how the OBike application and integration occurs. This could potentially point towards more options for acquiring $OCN outside of having to go through the hassle of exchange signup, purchase and sending to the necessary wallet or application.

As has been noted by many of the loyal Odyssey consumer base, more efficient methods of acquirement are necessary to ensure that the average user experience is timely and positive in nature. With an easier method in place, Odyssey’s original credit and reputation system can more fully be showcased and add longterm value to the ongoing incentive of utilizing of the token.

Further Recharge options include:

Ongoing investigation into the wallet generation process reveals the following:

WalletInfo walletInfo = OWalletAPI.generateWallet(); userWalletInfo.setCoinAddress("0x" + walletInfo.getWalletAddress()); userWalletInfo.setMerchantId(merchantInfo.getId()); userWalletInfo.setUserid(userId); userWalletInfo.setPrivatekey(AES.encrypt(walletInfo.getPrivateKey(), initConfig.deskey)); userWalletInfo.setCreatedAt(new Date()); userWalletInfoMapper.insertSelective(userWalletInfo);

The above shows a relatively standard set of wallet address, user ID and private key generation implementations for the infrastructure.

Further building upon their scheduled roadmap items and concepts, specifically allowing for merchants to integrate within the Odyssey ecosystem, we see that MerchantInfo is mentioned frequently throughout: