Taraxa Community Update: February 2020

February 26, 2020 Blog No Comments »

Taraxa Community Update: February 2020

A month full of learnings about Taraxa’s enterprise applications, iterations on the product demo, and more refinements on the tech front.

➕ Community

Engaging with our community is one of our core targets for the year, so we kicked things off with Design Challenge giving our early supporters the opportunity to showcase their talent and contribute to spreading awareness about Taraxa. With an amazing participant rate, we’ll be announcing the winners and giving exclusive rewards shortly!

Moving further with our market research and product development, we constantly come across new findings on the applications side. Here’s one on how getting the grasp of ops data with Taraxa’s can help to optimize change orders management in construction. And another one for Taraxa’s application in asset leasing. Read on to learn how our solutions help to confidently correlate and measure data asset performance to take insight-driven action. As always, we’re here in the chat for all further questions — reach out to learn more. More insights from our Twitter:





➕ The Tech

As we move forward with the vision of a highly-credible cloud-based data collection solution powered by distributed ledger technology, our core developers (along with community bug submissions) have been hard at work adding functionalities and maintaining the persistent state for of nodes of Aphrogenes Testnet.

PBFT Consensus and Execution Schedule

We kept polishing Taraxa’s block proposal scheme to make sure that synchronization queues and database commits are atomic for PBFT:

  • Improvements in PBFT block class design including serialization for storing blocks and sending them over the network and making class- immutable
  • Fixed PBFT block signing
  • Made ETH block available via ETH API strictly after it has been committed

Throughput optimization

We leverage the DAG topology to enhance the overall throughput by enabling the rapid finalization of the block DAG. Among things done on this front:

  • Added new parameters for the soft and hard limit of transaction and DAG blocks in verifying queues when queues get filled up
  • Modified test parameters to be more readable:
    – Simplified transaction insertion and verification to enable easy synchronous and asynchronous verification
    – Implemented a proper RLP serialization in PBFT blocks and used it as the base for hash and signature

Transaction Executor and Concurrent EVM

Taraxa’s concurrent virtual machine is unique in terms of being able to run smart contracts in parallel in order to increase the network’s throughput. Accomplished on the transaction engine side:

  • Developed an algorithm for planning parallel execution (and executing the plan in parallel) of Ethereum state trie hashing or any bubbling-up non-commutative calculation on any tree (python/graphviz garage)
  • Figured a set of techniques to significantly reduce the influence of Ethereum trie operations on transaction execution speed.

Taraxa’s concurrent VM

We’re also happy to see our developer community grow with more contributors onboarded to Taraxa’s GitHub. For those of you who are new to Taraxa, we’ll be publishing a series of video explainers on the network’s design and consensus:

And last but not least: we’re hiring!

Get in touch to learn more about Taraxa’s applications, follow us on Twitter for project updates and announcements, and chat with the team of contributors on Github!

➕ Stay tuned:

Comments are closed.