Weekly Updates

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

Weekly Development Snapshot

• New web3.js package development & unit tests finished, the npm package is expected to be released by the upcoming week.
• Refactoring + Unit tests update for both Consensus and Execution Engine
• Several other bug fixes related to API, Makefile, data directory etc.
• Fix: pk decoding in SignatureAndPublicKeyValues in Execution Engine
• Released beta-testnet for internal testing

Weekly Development Snapshot

QRL Zond

• New web3 package development is in progress
• Updated several dependencies
• Refactoring done in both Beacon Chain and Execution Engine
• Bug fixes + Updated Unit tests

QRL

• back-porting of qrllib into Vite PWA environment underway

Weekly Development Snapshot

• Minor fix in wallet.js having incorrect main file name in package.json
• Some other changes in wallet.js to return hex string with 0x prefix is in progress
• Updated API prefix for go-zond with zond_
• Updating & testing zond-contract-example with new wallet.js with Dilithium5 replacing older version of Dilithium
• Changes in web3.js in progress to support the new transaction format

Weekly Developer Snapshot

• The existing beacon node when restarted has dependency for at least one node to be online for it to get synced from finalized slot to the last unfinalized slot. However, in case of a crash, there could be no node online and thus may halt the network. The changes and testing are in progress for the beacon chain to keep track current unfinalized slot and to continue from the last block even when there is no node online given the flag is passed during the start of the beacon node.
• We are currently testing and mapping out all the changes required for the API of the execution node.
• We are working to fix the js calls made by the client to the API’s of the execution node in Golang to include the Dilithium 5 support, so that one can easily deploy and interact with smart contract and to enable other client based API calls.

Weekly Dev Snapshot

• Changes in Execution Node to unify pqaccounts & account package into single account package
• Fixed unit tests & updated sign function in pqcrypto package
• Added constant DilithiumSignatureLength
• Changes in transaction data & API to support dilithium based wallet
• Updated RPCTransaction API with new fields PublicKey and Signature
• Updated transaction marshalling to support new fields PublicKey and Signature for dilithium compatibility
• Bug fixes + Updated unit tests
• Successfully tested the API required to make & sign transaction from the CLI.
• Successfully tested Transaction Pool in Execution Node, along with the transfer of funds from one dilithium wallet to another

Weekly Dev Snapshot

• Tested exit of validator from staking along with the withdrawal of balance
• Currently changes are in progress to make transaction from Dilithium based address on the execution engine
• Removed non-required flags from the staking-deposit-cli
• Made required changes to completely replace execution changes with Dilithium execution changes
• Bug fix for withrawalCredentials validation & improved error messages
• Added generate dilithium to execution change command in staking-deposit-cli
• Removed default value of chain and execution-address flag and made them required
• Added 0x as prefix for hex string and handling the same while decoding for the staking-deposit-cli
• Added check for DecodeHex to ensure 0x prefix exists for hex string
• Fix: issue with the incorrect indexing for amount while calling NewCredential function
• Fix: issue with the incorrect indexing for credentials while calling NewCredentialsFromSeed function
• Fix: Corrected path while exporting dilithiumToExecutionChange
• Fix: Exported filename for dilithium to execution changes
• Added json field names for DilithiumToExecutionChangeMessage
• Changed type of ValidatorIndex to string to make it compatible with existing CLI

Weekly Dev Snapshot 📸 👇

• Implemented CLI functionality to generate Dilithium to execution change
• Changed default value of execution-address flag in staking-deposit-cli while generating new seed for staking deposit
• Added and initialized DilithiumWithdrawalPrefixByte, ZondAddressWithdrawalPrefixByte & DomainDilithiumToExecutionChange in config, these fields are used in staking-deposit-cli for stakings deposits and withdrawal.
• WithdrawalCredentialsHash function now uses DilithiumWithdrawalPrefixByte to compute hash while generating new staking deposit
• Added validation of withdrawal credentials in validateDeposit function in staking-deposit-cli
• Added proto messages for Dilithium based execution change for validator exit
• Added other helper functions such as DecodeHex, ToSizedDilithiumSignature, ToSizedDilithiumPublicKey for staking-deposit-cli
• Node has been successfully tested for 14000-15000 blocks and intentionally stopped thereafter.
• Fixed bug in richlist

Weekly Dev Snapshot 📸 👇

• Finished implementation of go-zond-wallet-encryptor-keystore
• Implementation of Dilithium Execution Changes file is in progress, it will generate the file with credentials, allowing one to withdraw the locked balance with staking reward for the validator that has exited.
• Implementation of tools and other required changes for the validator exit is in progress.

QRL Monthly: feat QRL Documentation Revision - August 2023

The QRL documentation is currently being revised with the aim of enhancing user engagement and facilitating development. QRL Zond continues to advance with go-zond-types, wallet-types, staking-deposit-cli, and wallet-encryptor-keystore. Finally, the third episode of “History of Cryptography: Behind The Code” discusses Enigma and Alan Turing.

Read more in our blog.

Weekly Dev Snapshot 📸 👇

• Implemented go-zond-types which is a library that has cryptography related data types supported by Zond.
• Implemented go-zond-wallet-types which is a library that has datatypes related to Zond based wallet and using the go-zond-types library for the cryptography related datatypes.
• Implementation of go-zond-wallet-encryptor-keystore is in progress using the go-zond-wallet-types. This will be used to encrypt and decrypt the keystore files generated by staking-deposit-cli. This library will be used by the beacon node while importing validator wallet from the key store files for the purpose of staking.