Below is a collection of Q&A from the previous weekly reports for better reading experience.
I. Tech（Node）
【It has been mentioned that INT will use machine learning and cloud computing to model strategies and process data. What are the planned capabilities and uses of this? Will the INT router be the nodes of this computing network? Will the supernodes?】
A:
This is actually on the INT blockchain cloud, and data analysis based on the data collected by the INTChain, and then make intelligent decisions. This piece of the function is still in preparation stage. Because the limited power of the INT router, it cannot act as a master node, and can only act as a light node.
【You mentioned using EOS’ supernode structure of voting on consensus nodes. Will this provide economic incentive for voters by enabling a shared block reward?】
A:
Our token economic mechanism is still in design and will not completely imitate EOS, because dBFT automated election logic is still being optimized.
【Will the DHT be used for data storage like BitTorrent or is it strictly as a node table?】
A:
Yes, DHT is together with node, and is used as data storage, and can store related node table as well.
II. Tech（ Function）
【Can setPrice buy and sell function in the contract manipulate the price?】
A:
First of all, these functions are used to do the transactions between tokens and Ethereum. If there are exchanges or transactions occurred, they are performed in respect of the wishes of both parties. In addition, the INT team has never called this function to set the price, and INT has solemnly promised not to use the setPrice method to manipulate price in future. Currently, except the setPrice can be called by the contract owner, the other two functions are unavailable, so manipulating the price is inexistent.
【Will there be overflow problems?】
A:
For this problem, INT has made an official statement before. Although the amount * sellPrice may overflow, the final transfer calls the _transfer () function (see 169 lines and 176 lines of the code for details), this function strictly control the conditions for each transfer. This can be referred from lines 130 to 137 of the code. Therefore, errors similar to overflows will not occur.
III. Tech（ Others）
【INT will utilize zero knowledge proofs to hide user intent and hide node identity. Is there any plan to use ZKP in other use cases like private transactions of data or assets?】
A:
Zero-knowledge proofs are designs in the single chain 1.0 architecture with an aim to better protect data privacy. In the 2.0 architecture, a new double-chain architecture is adopted. Meanwhile, the consensus mechanism has also changed, and many areas need to be redesigned. Many problems have also been encountered. After solving the current problems, ZKP will be considered in other situations.
【Are you planning on having several established subchains of different functionality on main net launch?】
A:
The semi-open “smart contract” module will be set on the INT chain to deal with the “fragmentation” of IoT applications. It is possible to evolve sub chains with different functions based on the strong industry attributes of IoT applications. The easy plug scheme of the consensus module can proceed under the condition of relatively stable cross-chain communication technology well as the completion of a more complete isolation witness program.
【Can you explain more about INT’s new consensus?】
A:
INT new chain adopt the dBFT+DPoS consensus, which is a huge advance for DPoS. On one hand, it oriented to differentiation application in the IoT more practically, on the other hand helping to select the “supernodes” in a stable and efficient way to realize service availability.
【Why there has been no updates in github?】
A:
The open source disclosure of the INT project codes is strictly in line with the project R&D progress. The disclosure of data involves the core of projects such as technology R&D and debugging. The team will submit and disclose it periodically and designedly according to the actual progress under the precondition of ensuring the project safety. Our codes have been updated to our own database, some of which have not been publicized and some have not yet been submitted. Next, we will devote efforts to updating the github. Please stay tuned.
IV. INT supply
【Will the total supply increase?】
A:
There is indeed a minToken function in the INT contract. This function can be called by the contract, creating privilege to implement the token issuance, but INT party never calls this method, and others have no privilege to call. With regard to the issue of token issuance, INT officially promised that no additional issuance will be implemented. In addition, INT is planning to implement token migration after completing the development of the wallet and the launch of mainnet, and INT will be more cautious with the planning of token quantity.
【 When is the remaining 680 million unlocked? How much is the team holding?】
A:
There are detailed explanations about the Token’s distribution and operation spending planning in this financial report. The team holds 10% (100 million Token). Due to the existence of uncontrollable factors, INT may make appropriate adjustments and publicize it to the public at the first time based on the precondition of ensuring the project safety and normal development.
V. Partnership
【Why do not specify the partners in the bi-weekly/weekly report?】
A:
You may pay more attention to our bi-weekly/weekly report. Our project progress, business cooperation and event promotion have never stopped. Due to the confidentiality of business cooperation, we would not specify which companies we are cooperating with. This has been explained specially in the previous bi-weekly/weekly reports. we will publicize the details to the public when the time is appropriate.
