THELOGICALINDIAN - n-a
CPChain (for Cyber Physical Chain) is a blockchain for the Internet of Things. Since IoT affairs are accepted to be a key use-case for blockchain tech, there are understandably absolutely a few companies accomplishing absorbing things in this space, from IOTA to the accessible Atonomi. So let’s get into the cipher review.
CPChain is accurately attractive at localized ancillary chains to aggregate abstracts and again broadcast blocks to the capital chain. Nice implementation, so we apprehend to see some inherent ancillary alternation argumentation as able-bodied as an interchain alteration mechanism.
Pre-alpha and Private keys in this repo are for testing purpose(s). 1 commit, 1 branch, 1 contributor. Seems like a checkbox accomplish to me, but let’s avoid that for now and adjudicator this based on the claim of its code.
Nothing agitative in utils.py.
In accumulator you can do either S3 (AWS) upload, or you can do IPFS upload. Nothing ever adorned in the CPChain cipher here, actual straightforward.
So, accepted abstraction actuality currently is accepting a bounded wallet, application it to abundance abstracts in IPFS/S3, and actuality able barter it. I’m academic as allotment of an IOT abstracts marketplace? So not the ancillary alternation or inter alternation implementation. Let’s accumulate looking:
Nice wrappers for absolutely a few ciphers, RSA, AES, EC, ECPEM, and SHA256, acceptable cryptographic account functions, but again, annihilation of absolute actuality here.
Heh, acceptable choice 😉
Let’s attending at the wallet.
Using Qt, haven’t apparent that in awhile. Rest of wallet cipher was the UI components, lots of assignment done, but annihilation interesting.
To login, we accelerate a json burden with the accessible key to login/ as a additional step, again we accelerate a nonce active by our clandestine key to confirm/, this again gives us a token. Seems a bit redundant, but annihilation amiss here.
Publishing articles sends our key and badge (received earlier) and some basal meta capacity to product/publish, adequately beeline advanced JSON-RPC implementation.\
send_request in SellerchainClient, puts the anchored abstracts assimilate IPFS and adds a active bulletin to the proxy alternation (shares the abstracts amid parties).
BuyerChain, will charge to accept a attending at start_client, for now aloof accepting a client burden and signing the message. update_buyer_db updates bounded storage.
SQLite actuality acclimated for bounded storage.
Moving over to Proxy.
Default SSL communication, acceptable to see. Just acceptance and casual letters amid client and agent and befitting bounded storage. Nothing ever fancy.
Let’s attending at market.
Using Django (Python framework), mostly aloof Django wrappers for basal API functions.
For now the blockchain is aloof application Ethereum.
CPChain Code Review Conclusion
Nothing impressive, but annihilation bad. Very aloof about this. It is absolutely a pre-alpha, basically a PoC, article I feel they should accept had afore they started adopting funds. This isn’t a lot of assignment to achieve so it would abundantly depend on how continued they accept been active with this. I can’t anticipate they accept been active with this for added than 1–2 months.
The added botheration actuality is that this is aloof an IPFS exchange backed in Ethereum, I’m not seeing any of their amount arrangement features? Where are they acclamation scalability, or the real-time problems of blockchain? Where is the two band amalgam accord or failing ancillary alternation protocol?
No red flags, but annihilation interesting.
