![taraxa.png](https://steemitimages.com/DQmPTKWmA27ZgXMVaJAZufxKP2JpX6iW78wqzu5bg8cHcu3/taraxa.png)

Unfortunately this isn't going to be a full review. I don't have a sneak peek at their GitHub repo and their full whitepaper. I will update and republish as I get more information. 

![steem_separator.png](https://steemitimages.com/DQmUWMWCtcj7MoLW2jdruvew1U8hu1LApdXKqxz8kP8hqST/steem_separator.png)

<h2 style="text-align: center;">What is Taraxa</h2>
Taraxa aims to "democratize Internet-of-Things (IoT)" data. On their website the project will achieve this with infinitely-scalable concurrent contracts, trustless light nodes, and encrypted data markets on top of block lattice. These words are directly from their site. The technology will be based on Nano (formerly known as RaiBlocks) and its lattice structure. If you are unfamiliar with Nano let's do a recap since Taraxa's foundation starts there. But first, let's look at the team.

![steem_separator.png](https://steemitimages.com/DQmUWMWCtcj7MoLW2jdruvew1U8hu1LApdXKqxz8kP8hqST/steem_separator.png)

<h2 style="text-align: center;">The Team</h2>
<ul>
	<li><strong>Steven Pu</strong>, Founder: IoT and healthcare entrepreneur, strategy consultant; LinkSens, EviPath, Monitor Deloitte; Stanford University BS & MS in EE</li>
	<li><strong>Vikram Saraph</strong>, Concurrency: Distributed computing, software concurrency, Ethereum hacker; Facebook; Brown University PhD candidate in CS</li>
	<li><strong>Dr. Ilja Honkonen</strong>, Ledger: Distributed computing, space weather modeling, Ethereum & IOTA hacker; NASA, Finnish Meteorological Institute; University of Helsinki PhD in Physics.</li>
	<li><strong>Professor Paul Gazzillo</strong>, Virtual Machine: Programming languages, security, systems; Google, Bloomberg, University of Central Florida; New York University PhD in CS.</li>
	<li><strong>Willem Wyndham</strong>, Virtual Machine, Storage, Reputation: Programming languages, compilers, security, WebAssembly and Bitcoin hacker; IBM; University of Maryland PhD candidate in CS.</li>
	<li><strong>Dr. Justin Snapp</strong>, Hardware: Analog IC design, microfabricated vacuum electronics, IoT enthusiast; Intersil, Qualcomm; Stanford University BS & MS & PhD in EE.</li>
	<li><strong>Chris Dai</strong>, Business Development and Partnerships: Entrepreneur and blockchain investor; Leland Capital, Longhash Japan, blockchain incubator; Stanford University BS in MS&E.
<div class="col-md-4"></div></li>
</ul>
Incorporated in the Cayman Islands with designs to incorporate in Switzerland, Japan, and other countries as necessary.

![steem_separator.png](https://steemitimages.com/DQmUWMWCtcj7MoLW2jdruvew1U8hu1LApdXKqxz8kP8hqST/steem_separator.png)

<h2 style="text-align: center;"><strong>A Refresher on Nano</strong></h2>
A network offering instant fee-less and miner-less transactions. Instead of a blockchain it uses a lattice. Compared to Bitcoin, Nano's transactions are not stored in the mempool (queue) waiting for a miner to pick up the transaction and add it to a block. Nano differs in that each address/account has its own blockchain. The lattice structure comes from the interconnected blockchains. When an account creates a transaction that record is then stored on a block in that account's blockchain. Sending funds from one account to another would record a <em>send</em> transaction in the sender's blockchain and the receiver would have to create a <em>receiver</em> transaction in their blockchain. The criss-crossing lines of send and receive transactions between chains create a latticed mesh pattern. This structure differs from Bitcoin in that Nano's transactions are asynchronous and handled between the two parties transacting. Transactions on Bitcoin must wait for the entire network to validate the transaction. I mentioned above that Nano is miner-less but that is not exactly true. There is a simpler (than Bitcoin) Proof-of-Work consensus algorithm that the network miners use to validate blocks. Solving this puzzle is much faster than in Bitcoin and gives the illusion of instant transactions.

 
![steem_separator.png](https://steemitimages.com/DQmUWMWCtcj7MoLW2jdruvew1U8hu1LApdXKqxz8kP8hqST/steem_separator.png)

<h2 style="text-align: center;">How are they different</h2>
<strong>Full whitepaper is not released for public consumption</strong>

Unfortunately the full whitepaper is not released for public consumption. The team is still actively working on several key components of their project. Here is my question to the admins in their Telegram chat.

<img class="  wp-image-505 aligncenter" src="https://quantalysus.com/wp-content/uploads/2018/05/Screen-Shot-2018-05-19-at-8.58.10-PM-1024x285.png" alt="Screen Shot 2018-05-19 at 8.58.10 PM" width="612" height="170" />


<strong>Block Lattice from Nano</strong>

Taraxa's core protocol is based on Nano (formerly RaiBlocks) lattice technology. To date, there is no formal link between Taraxa and Nano.

<strong>Smart Contracts on Taraxa</strong>

Taraxa claims their smart contract achieves high throughput because of two primary reasons: 1) single nodes are able to process hundreds of smart contract calls simultaneously, and 2) the ability to break up smart contract processing tasks to reduce wasted work. The second point is vital in comparison to Proof-of-Work protocols especially. With Bitcoin and Ethereum, all miners are working to produce blocks but ultimately one wins and confirms the newest block. All the other miners (<em>n-1)</em> generated work that was redundant and wasted. With Taraxa, once a miner runs a smart contract that node is the sole block producer and thus reduces waste and makes for high speed output.

<img class="aligncenter  wp-image-508" src="https://quantalysus.com/wp-content/uploads/2018/05/feature_vm.png" alt="feature_vm.png" width="464" height="463" />
<p style="text-align: center;"><em>Smart contract parallel calls</em></p>
<strong>Virtual machine (VM)</strong>

Differentiating itself from Ethereum, Taraxa chooses to leverage existing, battle tested technologies. Creating new languages such as Solidity leave the network vulnerable to a wide range of unknown attacks at the time of the technology's development. Taraxa's VM stack is based on WebAssembly (WASM) to enable executing code nearly as fast as running native machine code. WASM is supported by a wide host of mature languages incuding C and C++. Other projects I have covered such as <a href="https://quantalysus.com/2018/04/11/project-ico-review-ontology-network/" target="_blank" rel="noopener">Ontology</a> have used <a href="https://github.com/go-interpreter/wagon" target="_blank" rel="noopener">Wagon</a> for WASM since their platform is written in Go. WASM is built on mature technologies such as asm.js and supported by blue chip firms such as Google and Microsoft.

![steem_separator.png](https://steemitimages.com/DQmUWMWCtcj7MoLW2jdruvew1U8hu1LApdXKqxz8kP8hqST/steem_separator.png)
 
<h2 style="text-align: center;">Ongoing business developements</h2>
Taraxa is currently in serious conversations to become the primary public ledger for <a href="https://www.CarBlock.io" target="_blank" rel="noopener">CarBlock.io</a>. Additionally, they are progressing through conversations with agriculture businesses in Western China to create a public ledger to capture farming equipment sensor data. Please note I use the word conversation since the protocol is still in active development. Once the team launches their testnet they an start rolling up their sleeves for the two conversations mentioned.
<h2 style="text-align: center;">Token Metrics</h2>
<ul>
	<li id="4a0d" class="graf graf--p graf-after--p"><strong>What stage is Taraxa in now: </strong>Currently in private sale but currently oversubscribed</li>
	<li><strong>No pools: </strong>Will not be working with pools (no surprise there!)</li>
	<li><strong>Token standard:</strong> TBD. Considering ERC-20 before swapping into their native mainnet.</li>
	<li><strong>Total supply</strong>: There will eventually be 2⁵³ -1 tokens, or 9,007,199,254,740,991 tokens</li>
</ul>

![steem_separator.png](https://steemitimages.com/DQmUWMWCtcj7MoLW2jdruvew1U8hu1LApdXKqxz8kP8hqST/steem_separator.png)



<strong>Sources</strong>
<ol>
	<li><a href="https://medium.com/taraxa-project/taraxa-faq-work-in-progress-311394e5fbea" target="_blank" rel="noopener">Taraxa FAQ</a></li>
</ol>

![steem_separator.png](https://steemitimages.com/DQmUWMWCtcj7MoLW2jdruvew1U8hu1LApdXKqxz8kP8hqST/steem_separator.png)