Here is a recap of IOST AMA with HitHub which held on IOST International community Telegram group.

Welcome to all IOST and HitHub Community members! This is Stephanie, Head of Overseas Marketing from IOST. We are very happy to have @BobbyHitHub here today. @BobbyHitHub is the COO of HitHub. We recently published the exciting news that IOST and HitHub will have a strong partnership, so now let’s start our AMA to learn more about HitHub!

Bobby: Hello, everyone, This is Bobby, COO of HitHub. I am very pleased to be invited by IOST to this AMA session and introduce HitHub to everyone here.

Could you use simple words to explain the HitHub? What kind of problems does HitHub seek to solve?

Bobby: HitHub is a decentralized and collaborative community built to value developer’s work with a transparent credit system using blockchain technology.
It is a community of developers, by the developers, for the developers.
HitHub provides a platform for developers to automatically redeem the value of innovation and creativity with compensation (currency value) and privileges (currency right). The self-governed system will guarantee that each member has the responsibility and the right to participate in community decisions.
HitHub community and the platform it runs on will embrace autonomy, democracy, transparency, and fairness without any third-party intermediaries or centralized supervision.
HitHub members will be among the first developers to recognize the full value of their efforts. As developers who have great faith in our own kind, we invite you to join us in making this long-awaited dreamland a full-fledged reality.

What’s the pain spot in the current opensource ecosystem?

Bobby: As Open-source developers strive to contribute and innovate their income has not yet been upgraded accordingly. There are three main issues in current open-source ecology.
Developers are still at the farthest end in the value chain of the tech industry. The Open-source business model brings the most dexterous and complex development and business practices available to date.
However, an undeniable fact is that the top of the Open-source ecological value chain has been dominated by commercial and technology giants, and the vast majority of hard-working developers are unable to reap from their own contribution.
This will have a fundamentally negative impact on the fairness, justice, and efficiency of Open-source ecology.
Developer’s intellectual property is difficult to be effectively protected
Intellectual property protection has always been a challenge in the field of technological innovation. Many technology giants are struggling with intellectual property problems, not to mention the average individuals.
Particularly the Open-source code is mainly hosted on a centralized platform like GitHub. The Git protocol can’t guarantee that the version information is not tampered with. It brings tremendous risk both technically and administratively as the version information is the only evidence to prove the true owner of the software property.
The current open-source platform is centralized controlled
Current open-source platforms such as GitHub are centralized controlled and not built on the open-source model. Developers have neither a say nor ownership of the community.
So HitHub was born to solve these problems.

Name some key highlights to your products for our members

Bobby: We propose a new code management protocol and code intellectual property identification system combining Git protocol and Blockchain technology to build a complete set of solutions for decentralized code hosting, intellectual property protection, value measurement, service delivery, and so on.
HitHub is a blockchain for software code development, hosting, and transactional activities providing runtime support for the HitHub community. The main components and services involved include hybrid shards, ledgers, consensus mechanisms, isolation witnesses, and smart contracts.

1. HitHub uses hybrid sharding chain technology, organically combining the public chain and shard chain (logical sub-chain) to form a hybrid chain infrastructure. HitHub will keep a small amount of the core content of transaction records on the public chain, major information such as the history of a witness, consensus records, business transactions, and other transaction details will be stored in an independent space.

2. DAG High Concurrency Asynchronous Execution. HitHub’s double-chain parallelism technology can not only verify the integrity of the main chain but also maintain flexibility in the sharding chain. The main chain is the traditional chained structure, while the shard chain is the DAG data structure.

3. Classified Dynamic Ledger Technology: Distributed ledgers are a core component of the blockchain and play a key role in the integrity and transparency of all types of information and transactions. To support the process of code development and activities such as software coding, hosting, distribution, sharing, and trading. HitHub will include a transaction ledger, storage cluster management ledger, and code management ledger.

4. Double Consensus Parallelism Mechanism: HitHub’s hybrid chain applies a dual consensus mechanism in the public chain and the shard (dual consensus of PBFT and DPOS). In the public chain, we use the Practical Byzantine Fault Tolerance (PBFT) algorithm to maintain the legitimacy of underlying transactions. The PBFT Consensus provides (N-1) / 3 fault-tolerance on the premise of ensuring flexibility and security.

It uses encryption to prevent spoofing and replay attacks and to detect corrupted messages. Each message contains a post-quantum public-key signature (RSA256 algorithm), message authentication code (MAC), collision-free hash function generated message digest, and so on.

The DPOS Consensus Mechanism will be used in the shard chain to validate the management in the Hit code hosting business layer. DPOS completes the transaction confirmation by voting at the supernode in the election, which can significantly increase the transaction concurrency and confirmation speed.

What is the primary of HIT token in the HitHub ecosystem? How it will be helpful for long term investors?

Bobby: HitHub’s economic model includes three major value transfer scenarios: reward for sharing of idle computing resources, a public reward for community contributions, and transactions involving developers’ works. The first two are the main approach to obtain cryptocurrency, and the last one is the main marketplace of crypto-currency circulation.

In HitHub, participants or users are defined as developers generally. They actually are software developers, miners, Open-source software users, Open-source application services agencies, certification authorities, third-party component developers, education and research institutions, business partners, and more.

In the HitHub system, all community participants are decentralized co-hosts and co-governors who work together for code hosting, copyright management, crowdfunding, paid use, basic network construction, resource sharing, and so on as per HitHub’s framework.

The cryptocurrency is the core coordination mechanism. HitHub uses a dual token system: basic token and fuel token.
The base token is used in the following scenarios

C2C Trade to pay for HitHub operating expenses including code hosting, copyright management, crowdfunding rewards, paid use, and so on.

Copyright Authorization To fund the transfer of copyrights and intellectual property. Voting Right Weighted Voting Rights.

Code Hosting When fuel tokens are not enough to pay, basic tokens are automatically converted into fuel tokens to ensure the deal is completed.

Fuel tokens are used in the following scenarios

Mining Reward

Miners provide the basic network infrastructure and the cost of the transaction ledger

Resource Reward

Fees charged by P2P resource sharers

Advanced Service

What’s the difference between HitHub and GitHub?

Bobby: Github is currently the most widely used code management protocol for software development. Major development communities like GitHub, GitLab, and OSChina are all based on Git protocol. But, it has inherent weaknesses such as large file support and slow access to large-scale small files.

HitHub’s goal is to overcome the limitation of Git protocol by upgrading to a new Hit protocol that combines Blockchain technology for more efficient large-scale, distributed software management and service worldwide.

There are some main differences between Hithub and Github

1. Business Area Github focus on project development and support for the basic social function, HitHub has high concurrent code authentication, decentralized transparent transaction, and strong social function

2. Value system
The developer of GitHub is difficult to get paid and private hosting of GitHub is expensive but Hithub has lots of advantages such as Incentive mechanism, zero platform intermediary fee, encryption digital identity authentication, and artificial intelligence capability appraisal

3.Tool support
The transfer protocol of github is not secure and file processing is inefficient while HitHub optimizes the file storage and has reliable code transmission, multi-granularity detection control. solution
Github’s centralized storage has a single point of failure and security issues. Hithub, on the other hand, uses decentralized storage, free sharing of storage, and free sharing of incentives

What’s the latest product updates of HitHub?

Bobby: HitHub is a code hosting platform based on blockchain technology. It aims to provide developers around the world with a free, borderless, safe, and efficient code hosting platform, where code assets are permanently stored on the chain.

HitHub is compatible with the Git protocol and operation method, and the code warehouse information is chained through the Ethereum smart contract and the distributed file storage IPFS technology is used to store the warehouse content.

HitHub will continue to improve user experience, reduce the cost of on-chain and storage, support HIT token incentives, HitHub project wallets, and transactions around code warehouses/projects.

Some Key HitHub commands:
Repository related operations: hit clone, hit add, hit commit, hit push, hit a pull
PullRequest submission/merger: hit pull request, hit am
Repository migration: hit migrate
HitHub configuration commands: hit cfg, hit contract, hit token

If you have any additional question about HitHub, please refer to HitHub website and social media
Twitter Link:
They have a very active community!