Celebrating Six Years of Post-Quantum Security: The Journey of QRL

Read More

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.

technical

1st September 2023

Table of Contents

Highlights

Documentation revision for QRL + QRL Zond

Last month in the annals QRL Weekly, we were happy to introduce everyone to the early stages of our revamped documentation for QRL and QRL Zond — redesigned, restructured, and renewed, aimed to elevate the user experience and facilitate more effective interactions with the QRL ecosystem.

The Need for Revamping

Proper documentation can make a significant impact on both users and businesses through enhanced usability, user onboarding, and reduced support loads. For newcomers, the initial impression can make or break their long-term relationship with a product. Revamped documentation aids in smooth user onboarding, acting as an efficient guide that helps users navigate through functionalities with ease.

Why fix something that isn’t broken? This is a common argument against revamping existing documentation. However, it assumes that the current documentation is entirely effective, understandable, and in sync with the product. While the current documentation served us well, with evolving user needs, changes in features, and an upcoming major update (Zond!), documentation needed an overhaul to be effective.

What’s new

The revamped documentation breaks things into a few sections that more easily guides people to do what they want to do.

  1. Use: Any interaction with the QRL blockchain, including creating and working with Wallets, Nodes, other QRL tools, or mining.
  2. Build: For developer related interactions with the QRL development ecosystem. From API calls to address schemes, CLI commands and Docker nodes.
  3. API: Covers the application programmer interface (API)
  4. Tutorials: Guides to get started using the QRL. Walking through basic tasks like setting up a node, requesting blockchain data, or creating a simple application etc.

What’s left?

While a significant portion of the revised documentation is complete, additional review and refinement are required before it can be completely replaced. You may observe, while perusing the documentation, that many of the sections have notices at the top signifying the page’s status. As we work through those, we’ll be closer to completely replacing the current documentation.

Alt text

How can I help?

This is where you come in. By utilising the available documentation and offering constructive input, one may significantly contribute to refining the content and rectifying any imperfections or identifying mistakes. Although it may appear insignificant, maintaining the usability of our documentation may have a substantial influence on users and organisations seeking to incorporate and utilise the QRL in their products and systems.

References

QRL Zond Development

Implemented go-zond-types, go-zond-wallet-types, and staking-deposit-cli with go-zond-wallet-encryptor-keystore in progress. Staking the has been tested successfully to 3000+ blocks.

Overview of components

  • go-zond-types, a library that has cryptography related data types supported by Zond.
  • go-zond-wallet-types, a library that has datatypes related to Zond based wallet and uses go-zond-types for cryptography data types.
  • go-zond-wallet-encryptor-keystore uses go-zond-wallet-types 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.
  • staking-deposit-cli generates multiple dilithium wallet for staking based on the parameters provided along with the keystore files with the dilithium seed encrypted with AES-128-CTR. It also generates files including details such as withdrawal credentials that would be used to create transaction that will be broadcasted further to start staking.

P2P synchronisation, a memory-related crash problem with the beacon chain, and state resumption were all fixed. Code to support account with smart contract code while generating genesis state from genesis.json was added as well, used to deploy deposit contract for staking in genesis block.

Media

History of Cryptography: Behind the Code (Ep #3)

We’re thrilled to release Episode #3 of our series, History of Cryptography: Behind The Code.

In our latest episode, we move from the end of WW1 through the 1940’s (WW2) covering everything from Enigma & codebreaking to Alan Turing & his teams work at Bletchley Park.

Check it out below or on the associated blog if you haven’t already.

Changelog

theQRL/block-explorer

#346 Testnet<>Mainnet

  • [4eb1d] Fix #346
  • [531c7] Merge pull request #431 from jplomas/master

Fix #346

Testnet <> Mainnet

  • [c756c] Merge pull request #423 from theQRL/testnet
  • [a453c] NFT hash display on mobile
  • [41582] Update NFT providers
  • [2dcb1] Merge pull request #424 from jplomas/master
  • [93c00] Bump nft-providers package version
  • [94cd9] Merge pull request #425 from jplomas/master
  • [c60dc] Fix NFT link on tx
  • [888a3] Merge pull request #426 from jplomas/master
  • [0d15f] Re-do NFT tx link fix
  • [e17f4] Merge pull request #427 from jplomas/master
  • [cb174] Scaffolding for richlist from new API
  • [618c1] Basic top 100 richlist for mainnet via richlist-api
  • [32aba] Display balance in Quanta
  • [bf623] Working load more & CSV export, version bump for deploy
  • [8f4a1] Merge pull request #428 from jplomas/master
  • [36755] Fix rounding in address balance
  • [b24b0] Merge pull request #429 from jplomas/master

Fix rounding in address balance

  • [36755] Fix rounding in address balance

theQRL/QRL

Merged Dev branch

  • [b5882] Fix: walletd conversion of binary data in token name and symbol
  • [44683] Flake8 fix
  • [13663] Merge pull request #1777 from cyyber/dev

Fix: walletd conversion of binary data in token name and symbol

  • [2a868] Merge pull request #1776 from theQRL/dev

  • [b5882] Fix: walletd conversion of binary data in token name and symbol

  • [44683] Flake8 fix

theQRL/theqrl.org

QRL Weekly, 2023-August-29

  • [12066] QRL Weekly, 2023-August-29

History of Cryptography ep 3

  • [75d54] History of Cryptography ep 3

QRL Weekly, 2023-August-22

  • [23b50] Quantum news update
  • [049d0] QRL Weekly, 2023-August-22

QRL Weekly, 2023-August-15

  • [7bee5] Quantum news update
  • [0bb0c] QRL Weekly, 2023-August-15

QRL Weekly

Add buildFuture to netlify config for future events

  • [8fc69] Add buildFuture to netlify config for future events

Add Post-Quantum Cryptography Conference event

  • [65766] Extend external_url to upcoming + adjust text/remove video
  • [eafa9] Add removed video to QRL Hackathon 2022 landing page
  • [f1439] Event page style adjustments
  • [3d745] Add Post-Quantum Cryptography Conference event
  • [f3ea2] Merge remote-tracking branch ‘upstream/main’

QRL blog adjustments

  • [d201f] Title fix
  • [da62c] Remove beta testnet estimated timeframe

QRL Monthly - July 2023

  • [2a7f1] QRL Monthly - July 2023
  • [32995] Merge remote-tracking branch ‘upstream/main’
  • [8a0cc] BG Highlight Fixes

QRL Weekly Update - W30

  • [ae553] QRL Weekly Update - W30

Quantum News

technical

1st September 2023