Q: There are a lot of projects in space, many that say they can solve perennial and similar issues in the industry, some of them already have testnets running, or, their mainnets have almost or already arrived. How does Ultrain compete in the terms of time and delivery?
A: Certainly, there are many public chains in the market. Ultrain has already launched the testnet on Sep 30. Our mainnet will be released in early part of second quarter 2019, which is our current focus.
Q: Will there be a burn mechanism within Ultrain’s ecosystem?
A:The burn feature was instituted in our initial ecosystem design. However, due to U.S. security compliance, we are discussing other potential designs to our ecosystem.
Q: How do Ultrain’s smart contracts differ from Ethereum’s?
A: We provide special middleware such as random number generators, ZKPS and PQC wallets, so that users can write unique DApps on Ultrain. Ultrain’s smart contracts are easier to write and run more efficiently. We support similar JS languages and enable WASM instruction set compilations.
Q:How does Ultrain differ from ZIL, since both are considered blockchain 3.0?
A:Sharding is not ready for blockchain right now. ZIL’s main idea is that of sharding, i.e., dividing the mining network into small shards, each capable of processing transactions in parallel to increase TPS and uses PoW for consensus. But Ultrain’s high performance comes from lay0 network optimization and BFT voting acceleration. Ultrain uses R-PoS for consensus. Overall, both projects adopt two totally different approaches.
Q:How is R-PoS different from say consensus mechanism of DAG or hashgraph? And what edge does R-PoS have?
A:This is a rather big question, which may require a whole separate paper on it! DAG-based consensus have long confirmation times, since different nodes have different views. It requires notary nodes to accelerate confirmation, but the consensus between notary nodes have the BFT problem. Generally speaking, R-PoS use VRF to select nodes as proposer and voters to finish the consensus process. Most nodes are listeners, following the decided block result; while DAG and hashgraphs involve gossip. All in all, both have their advantages.
Q:Why is the testnet by invitation only and not open to the public?
A: The testnet is open and can be interacted through our explorer or the JS SDK U3.JS. The invitation is for those who want to host nodes for Ultrain’s testnet. There are two considerations for this: on the one hand, because the test network does not yet beget users to be financially motivated; on the other hand, we need fork for an upgrade.
Q: How can we get access to results and information on your testnet?
A; You may view it here
http://explorer.ultrain.ioPerformance
Q:In the whitepaper, it’s mentioned that there are two consensus that will be applied to the framework to greatly enhance transactions performance and efficiency in confirmation time. What are those two consensus?
A:The two consensus that are mentioned are the technical consensus and the business consensus. For technical consensus, one is for the mainchain and the other is for the sidechain. Our mainchain uses R-PoS, while the sidechain similarly uses R-PoS, D-PoS and so on.
Q:Based on your testnets, what’s the highest TPS Ultrain has achieved?
A:We’ve achieved 3,000 TPS.
Q:Given how the input parameters for the VRF will be the performance of the machine, how will that be measured? Will it be based on computation power?
A:The VRF performance is benchmarked with standard hardware configurations to test the running cost. As it is not akin to PoW, it is not based on computing power. The input parameters of VRF are nonces such as block heights; roles such as proposers, phases and nodes’ private keys. It has nothing to do with computation power.
Q:Ultrain will support DApps, which most of the future projects focus on: will there be data storage for these DApps? You are probably aware that Cryptokitties (as an example) clogged the Ethereum blockchain; how will you overcome those type of issues?
A:Cryptokitties suffered from the low TPS of Ethereum. With Ultrain, its high TPS will overcome that. As for the question on the data storage, the data in users’ smart contracts will be saved on chain. The full nodes, which provide historical information, will have a high level of hardware configuration and distributed storage solutions.
Q:I am told that Ultrain will only use 1% of computing power for normal operations and the remainder will be reserved. Is that true?
A:As described in our whitepaper, 1% of computing power will be used for the consensus, the rest can be used to do other things, like AI computation. For our business model, not all computing power is needed for consensus.
Q:The new consensus mechanism increases performance manyfold, but only use 1% of computing power. Its speed and security still looks good. I would like to know how many nodes are needed for full decentralization?
A:With R-PoS, the proposers and voters are selected by cryptographic algorithm. All nodes that meet the minimal stake requirements have the possibility to be selected. So it’s totally decentralized among all the nodes. The more nodes you have, the more security you have, and it has nothing to do with the degree of decentralization.
Q::Does the oracle machine mechanism maintain a stable operating cost for DApps?
A:As described in our whitepaper, we do use it to monitor and dynamically adjust the computing power price, ensuring that the operating costs of DApps are maintained at a relatively stable level for a period of time.
Q:Does the Dynamic-and-Adaptive sharding improve on current sharding technology? Is it also smart contracts-compatible?
A:It certainly does and a more detailed explanation is in the yellowpaper
https://ultrain.io/downloads/Ultrain%20YellowPaper_v1.0.pdf. And yes, our Dynamic-and-Adaptive Sharding is smart contract-compatible.
Security
Q:Is Ultrain quantum computing proof ?
A:We have no new announcements regarding that at the moment. But the post-quantum wallet can be integrated any time. Please take a look at our middleware, which is based on state-of-art post-quantum public key signature algorithms and multisignatures, which avoid the risk of being attacked by quantum computers.
Q:How does Ultrain prevent attacks?
A:We have strong real action engineering experience to prevent such attacks. Additionally, we have well-known international security companies as our partners to handle attacks.
Q:Will your self-learning smart contracts be reliable enough? Will there be any control over them when users write the smart contracts themselves?
A: There are some limitations. You can refer to our whitepaper for information on Ultrain’s security
https://ultrain.io/downloads/Ultrain%20Whitepaper_v1.1.8.pdf.