Weekly Updates

Weekly Development Snapshot

• Code related to derived and remoteweb3signer has been disabled
• Removed deprecated validator web ui code
• Fix unit tests
• Removed all the codes related to forks other than Capella
• Removed old db migrations
• Renamed the Duties field with CurrentEpochDuties
• Overrided the SecondsPerSlot config field for tests on the validator side that rely on functions such as waitToSlotTwoThirds to have them run much faster
• new explorer/wallet middleware routes to support fee calculation in testnet wallet
• transaction UI work in testnet wallet
• interaction with middleware for automated transaction metadata population
• offline signing of transactions complete

Weekly Development Snapshot

• Updated several E2E tests for qrysm
• Removed AggregatePubKey from sync committee
• Removed non required code related to aggregateKeyRoot from sync committee
• Updated parameters and field parameters for minimal config
• Updated proto files and bazel files
• Demo repo using @theqrl/web3 package to show how to send transactions via nodejs
• Explorer working for latest block / address / transactions. Block by search in progress
• Smart contract example instructions / demo repo updated to Testnet release version
• Release of cli tool to extract hexseed from Zond Testnet node data files (https://github.com/theQRL/hexseed-from-address)
• qrypto.js maintenance update
• Basic wallet to send Zond Testnet QRL in progress

Weekly Development Snapshot

• Added fix related to configuration issues
• Updated protobuf stub files to support the new configuration changes
• Reset Zond Beta testnet with new configurations
• Released v0.1.1 for both zond and qrysm related binaries
• Tests for the beacon-client still in progress
• Dilithium5 JS package refactored to provide both CommonJS and ESM/MJS support with integration test / demo of use repo
• Tests of and enhancements to Windows installer package
• Documentation update
• Explorer routing complete with basic transaction info underway

QRL Zond beta-testnet v1 Released

We are pleased to announce the release of QRL Zond beta-testnet v1, an important step towards allowing blockchain developers to create dApps with EVM smart contract capability and a robust web3 API on a quantum safe backbone. Read more in our blog or jump in right away by going to Test Zond.

• Blog - Project Zond: QRL’s next generation network, with EVM compatibility reaches beta-testnet
• Press Release - The Quantum Resistant Ledger Unveils Beta-Testnet of Zond: A Quantum Secure, Proof-of-Stake Blockchain

Weekly Development Snapshot

• Pre-compiled deposit root contract has been created.
• Deposit contract has been updated to use the pre-compiled deposit root contract to reduce the gas cost required for the calculation of deposit root.
• Implementation of CLI tool that allows broadcasting deposit data file having multiple deposit transactions is in progress.
• CI/CD configurations in progress.
• Unit tests for the beacon-client still in progress.

Zond Testnet Explorer

• Front and backend architecture & scaffolding
• Latest block data
• Address balance
• Interactive metadata navigation
• Configurable API endpoint

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.