Taraxa Community UPD — March

3月 25, 2020 ブログ No Comments »

Taraxa Community UPD — March

Tapping deep into the product development for Taraxa’s applications

➕ Community

We’d like to thank our steady supporters and contributors who keep following Taraxa’s progress. This month, our team kept navigating the development roadmap amidst the coronavirus chaos with more sprints accomplished both on the applications and tech sides.

As we move further with our market research, we surface a number of implications that are essential to understand when considering the promise that DLT holds across various industries. In line with our current avenues of research, we looked into how data optimization infrastructure offered by Taraxa might benefit healthcare (enabling better compliance monitoring), telecom (optimizing ID-management), and consumer goods (increasing the supply chain transparency) sectors. We also did a primer on the blockchain’s real value for the enterprise to address the most common questions asked by C-levels when evaluating the tech’s capabilities and cost-efficiency. Read on to learn how our solutions help to collect quality operational and metadata from stakeholders with more confidence.

As always, here’s a compilation of our Twitter highlights to give you a broader outlook of what we’ve been up to this month:

➕ The Tech

As we move forward with our vision of a highly-credible decentralized data collection platform powered by distributed ledger technology, our core developers have been hard at work on Taraxa’s consensus and maintenance of the persistent state for nodes of Aphrogenes Testnet.

PBFT Consensus and Execution Schedule

Efficient proposals enable Taraxa’s PoS to produce fair and non-coordinated block proposals, which is essential for the network’s security. This past month was mainly focused on moving the PBFT chain head DB separate from PBFT chain, fixing the unit tests, and Aleth improvements.

General Ledger Improvements

Taraxa enables the rapid finalization of the block DAG to maximize the throughput and minimize inclusion and finalization latency. We completed code refactoring in Transaction manager and queue, separated transaction classes into separate files for each class, and improved the block class design including serialization for storing blocks.

RPC and Concurrent EVM

We introduce an EVM-compatible toolchain to achieve maximum backward-compatibility to make Taraxa’s code modular and reusable, and the unique concurrent virtual machine that is able to run smart contracts in parallel ultimately increasing the network’s throughput. This month, we’ve accomplished the EVM optimizations and storage improvements, and also completed all the changes for CPPcheck.

We’re happy to see our community grow with more contributors onboarded to Taraxa’s GitHub.

And last but not least: we’re hiring more developers to join our team — both remotely and in our Santa Clara office. For those of you who are new to Taraxa, we keep posting short video explainers on the network’s design and consensus like so:


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!

website: taraxa.io

blog: medium.com/taraxa-project

telegram: t.me/taraxa_project

twitter: twitter.com/taraxa_project

discord: discord.gg/WaXnwUb

reddit: www.reddit.com/r/Taraxa_Project/

Taraxa Community UPD — March was originally published in Taraxa Project on Medium, where people are continuing the conversation by highlighting and responding to this story.