Weekly Updates

Weekly Development Snapshot

• Added more logging during P2P handshake
• Necessary changes made to zond-contract-example using new web3.js and cryptography libraries
• Successfully tested smart contract deployment, on-chain and off-chain calls
• Unit tests for the beacon-client still in progress

Weekly Development Snapshot

• Fixed peer pruning issue related to disconnected peers, which was stopping new nodes from same ip to connect with the bootstrap nodes.
• Tested api to add/remove/list trusted peers.
• Unit tests for the beacon-client still in progress.

Public Beta-testnet v1 Date Set for January 15th, 2024

After months of dedication, development, and collaboration, we are delighted to unveil the official launch date for our public beta-testnet v1: January 15th, 2024!

What to expect

As we unveil the entrance to our public beta-testnet v1 from devnet, developers across the globe are invited to delve into and interact with our platform and ecosystem. This encompasses web3 and EVM smart contract capabilities, all built upon a post-quantum secure foundation. Those with experience in the Ethereum ecosystem will find themselves right at home in this innovative environment.

In this developmental phase, as we refine nodes and work towards public beta-testnet v2 (with additional improvements & incorporating a new address format), there is a prime opportunity to construct essential ecosystem components. This includes the development of wallets, explorers, and various tools that will enhance the overall functionality and user experience within our platform.

More details will be shared through documentation and other media as the release date gets closer.

It is essential to note that the information provided in our development updates is inherently dynamic and subject to change. The nature of ongoing development means that unforeseen circumstances, technical considerations, or strategic decisions may necessitate adjustments to the initially communicated details and timelines.

Weekly Development Snapshot

• Released private testnet with reduced sync committee size 16.
• Parameter changes such as minimum staking reward, epoch size, block reward, decimals etc. are in progress.
• Necessary code changes to support the new parameters are in progress.
• Unit tests for beacon client are in progress.

New Blog - QRL: The Next Chapter

The QRL project has appointed Iain Wood as its new operational manager, entrusting him with strategic goals such as community growth and finalizing the project’s roadmap. The original creator reflects on the journey, expressing excitement for QRL’s future while transitioning to an administrative role. Learn more about these developments in our blog post.

Weekly Development Snapshot

• All upstream changes for both consensus node & execution node completed.
• Modified third party repositories to implement bitvector16 as the datatype is required for the sync committee having size 16.
• Sync committee size reduced from 512 to 16.
• Successful short testing for the node with new configuration.
• Unit tests are in progress.

Weekly Development Snapshot

• Majority of the upstream changes related to execution node has been finished, however few more remaining upstream changes for the execution node is still in progress, expected to be finished by the end of this week.
• Unit tests for beacon node is in progress.
• Changes in progress for the next testing with reduced number of sync committee to decrease the block size from 2.5MB to fewer kilobytes.

Weekly Development Snapshot

• Finished upstream changes for the beacon node
• Merged several critical PR related to optimization, bug fixes and with some new API support for the beacon node.
• Upstream changes for the execution node is in progress.
• Unit tests for beacon node is in progress

Weekly Development Snapshot

• Upstream changes are being merged in beacon node
• New unit tests are in progress and the existing unit tests are being fixed
• Refactoring + Bugs fixes

Weekly Development Snapshot

• Recomputed the time to process the batch of blocks and adjusted the p2p timeouts to fix the syncing issue
• Early testing: 20x increase in syncing speed
• Unit Tests for the beacon client is in progress
• Refactoring and bug fixes for both beacon & consensus engine
• Re-released new testnet with the latest changes along with the fix with syncing issue
• Evaluating the number of sync committee required to securely support the light client

Weekly Development Snapshot

• Increased p2p status response timeout, fixing the timeout resulting into p2p ban
• Changed signature and public key data type
• Added updates from upstream till v4.0.8 into beacon client
• Released new testnet with the latest changes
• internal tooling for node testing