Taraxa Weekly Update: Week 9
Another week of refinements and additions to Aphrogenes Testnet
As we’re gearing up for the launch of Taraxa Mainnet, more work on the improved stability of Aphrogenes release, consensus, and node syncing is continuously being done on a weekly basis. Here’s a quick rundown of our most recent accomplishments.
Consensus and PBFT
The efficient block proposal scheme enables Taraxa’s PoS system to produce fair, efficient and non-coordinated block proposals, which is essential for the network’s security.
1. Finished database atomic in the finalization stage and reorganized PBFT.
2. Fixed the number of execution DAG blocks and transactions.
3. Reviewed the code for status message sync.
4. PBFT state machine research and design started.
Optimizing the network’s throughput
Taraxa leverages the DAG topology to maximize the throughput and minimize inclusion and finalization latency by enabling the rapid finalization of the block DAG:
- Looked into the bug where PBFT and DAG proposal seem to get into a deadlock.
- Updated status sync changes with node sending syncing status as part of the status message to avoid node syncing from a node that is not fully synced.
- Refactored the code in transaction manager and queue triggered by incorrect transaction count being reported. Made all the transaction status changes and database updates atomic to avoid any related bugs.
RPC interfaces and concurrent EVM
Taraxa adopts an EVM-compatible toolchain to achieve maximum backward-compatibility to make sure our code is modular and reusable.
- Fixed a few bugs and did some refactoring in CPP-Ethereum integration.
- Finished the batch of optimizations for EVM, tested/measured it. Proposed one more iteration of optimizations to start the work on parallel transaction execution.
If you’d like to contribute to the building of Taraxa, reach out on our Telegram and be sure to keep track of GitHub.