Development Updates, Development Spotlight — Command Line Interface

Introduction

As we move into the final week of July, plans for the QRL developer summit in August have been largely laid out, with only the details remaining. As mentioned in the AMA and elsewhere, this gathering of the QRL developers will be focused on Proof-Of-Stake, and will occur in Europe in August. It represents the first time that all of the developers will be in one physical location, as well as the largest gathering of QRL team members to date. We will have more on what comes of that developer summit once it has come and gone. For now, here is some of what went on last week.

Development

qrl-cli: fix: zip release assets

fix: zip release assets go-qrl: Added lock before initializing Downloader

Added lock before initializing Downloader QRL: Merged Dev

Development Spotlight — The QRL CLI

One of the many exciting developments being worked on by the talented team of QRL developers is the QRL Command Line Interface (CLI). For the less technically inclined, a CLI is a text-based user interface used to view and/or manage computer files.

CLIs are an integral tool in the toolbox of a properly mature network. Not everybody wants to download a whole QRL node, or familiarize themselves with a node package manager or golang to be able to access the power of the QRL API and ecosystem. In addition, there are environments in which it makes more sense to run commands in a self-contained fashion locally (network attached), and in the context of an advanced administrator to interoperate with other programs.

One example of a use-case would be an executable function to notarize documents on the QRL blockchain. More features are being added stage-by-stage, aiming to give access to the full suite of features of the platform by the time of public release.