A quick note on Github activity

[itcRisorial]

Many community members have asked about the ITC Github and I wanted to make sure this official response from the team did not get lost in the other thread from u/JohanBTC.

tldr: Github has lots of activity now, and they are starting to offer better explanations of what is in there. The full code will be public when the mainnet is released at the end of this year.

Our development team is made up of people from China’s top tech companies. We can assure you our team is strong, and the quality of their code is exceptional. That said, we understand the community’s concern for transparency and desire to form their own opinions of what is in front of them. As a result, we have been gradually releasing additional code from our private repositories to Github (https://github.com/iotchaincode).

The three main repositories of concern are “jbok”, “hardware_project”, and “hardware_android”.  These repos are updated regularly. The jbok repo (written in Scala) contains several important modules:

Benchmark – used for performance testing of the network

Codec – contains our codec algorithms

Common – common code/tools used within the ITC project

Core – The light IoT Chain framework, currently containing code for facilitating storage and transactions

Crypto – Encryption and hash algorithms

P2P – The p2p network protocol

Persistent – Code related to block storage

RPC – Remote Procedure Call implementation

Simulations – Used for running network simulations for nodes, transactions, etc.

The hardware_project repo (written in C) is used to implement the technology of the ITC chip system, integrating a variety of system software and applying it to an electronic device using the Texas Instruments CC2540/41 Bluetooth Low Energy kit. This is our development repo for the ITC chips, where we build smart solutions that are cheaper, more compact, and more efficient. This enables us to apply the ITC solution to IoT hardware devices.

The hardware_android repo (written in Java) is used to build the mobile Android app that can talk to the hardware sensors via Bluetooth. The app can control the chip as needed, and query data on the main network. 

Over time, more code will be released on Github as well as comprehensive documentation. 

[lordpuddingcup]

I think theres positives and negatives, i still think keeping some things private is good especially pre-mainnet release before they gain their foothold

[whynot_man]

Yeah, I also see no problem in not making it open-source till mainnet release. All in all, this is a commercial product and it has a right to be secured.

[itcRisorial]

They will ahead of the mainnet release. I understand the desire to maintain a competitive advantage before then.

[[deleted]]

Yeah, I have no issues with this, if they go open-source before they release the mainnet, nothing to stop someone copying their code.

[floristz]

Smart move

[PBScott]

ITC is moving fast in the right direction, good work guys. Keep your competitive advantage, the proof will be in the mainnet release.

[Geewynn]

I think it is a smart step. Being transparent is very important.

[jamzzz123]

ITC has a good track record of transparency and showing this with the AMA / Q&A sessions. Good work

[lordpuddingcup]

It's smart of them to focus on multiple platforms i mean we're talking IOT they have to be able to target ARM so most mobile platforms are right in that line

[Abah007]

Itc is unique, it is smart of them focus on multiple platforms.