Taraxa Weekly UPD.
Pre-launch node testing in progress: fixing a few known issues and getting ready to launch pre-staking.
We thank everyone who’s been running the Taraxa nodes to help us pre-test — jump to our Discord to join the team of early Taraxa network testers!
We’re now working on the next big set of patches to address the issue of slow syncing when joining a new node to the network. We ran into some minor consensus issues, but luckily those are not related to the core consensus but center around more structural units.
We’re currently focused on making node synching faster when a new participant is catching up with the block production by introducing the synchronization performance patch.
Another issue was the boot node crash that caused several boot nodes, likely caused by someone trying to join the network with an old version of the node or a corrupted node.
- Small fix for a node having enough next votes for previous PBFT round: no need to update from synced next votes bundle even the next votes are different.
- Debugged and investigated the testnet PBFT crash issue: caused by incorrect TRX status when proposing a new PBFT block.
- Finished fixing review comments on PR985 rewrite verified votes table. Using a shared pointer for votes in all votes table instead of using a voting structure directly to save memory.
On the application side, we’re now in the process of re-writing Marinate’s UI and building out an open API to allow for integrations with popular messenger platforms. We’ve been exploring how to get consistent data from Telegram groups and channels to be able to build a link tracking mechanism.
- Debugging and testing the Docker containers in Windows.
- Checking in on the status of open API deployment.
- Started a new bot assistant with the following initial features: create Twilio numbers, sign up for telegram accounts, keep track of groups and bots.
- Added a solver for Telegram Combot to avoid possible challenges.
- Upgraded the celery approach to support periodic data ingestion.