Last Month at QRL — November 2021
Table of Contents
Developer expansion update
As the crypto asset space grows into a multi-trillion dollar market, it is worth considering that the vast majority of that market cap still remains painfully vulnerable to quantum theft. The financial stakes have never been higher and our mission to provide a fully post-quantum blockchain ecosystem has never been more important than it is today - especially as crypto seems ready to burst into the mainstream around the world.
Remote team working is difficult and so I was very pleased to recently travel to finally meet with Kaushal who has been overseeing our recruitment round in the UAE. I am thrilled to report we are onboarding several excellent core developer candidates into the team after a lengthy selection process - more details on this to follow.
Swelling the core development team is absolutely critical to accelerate node development and the planned STARK powered PoS hardfork timeline. This incredible cryptographic construction is worthy of a blog post in itself as it enables post-quantum secure blockchain scaling for the first time, eliminating hugely expensive signature data from blockspace entirely.
Additionally we are pleased to welcome back Charlie to the EnQlave development team once again. It will be amazing to finally see post-quantum secure wrapped QRL live on ethereum and for the QRL ledger to become multi-chain once again - but this time in a completely PQ-secure manner.
It would be remiss to fail to announce our new intern developer Liam Arzona. Welcome! He will be (and has already begun) working on migrating qrllib from
rust, this will allow for adding threading, async for better performance, and progress of tree building for a nicer UX.
Exciting times approach,
QIP-016 post-vote determination: APPROVED
QRL Improvement Proposals (QIPs) been a longstanding part of the process to evolve the QRL core-protocol through a decentralized manner since its first QIP back in 2018. Now, we’ve improved this process through the implementation of on-chain voting.
The main goal of voting is to produce a decision which is accepted by the members of the system (in our case, QRL). One can argue that voting upholds the fundamental principle behind democracy, which is “rule by the people”. In the case of blockchain, it provides a way for stakeholders in the system to have their voices heard to steer how decisions are being made. It’s equally important that there’s enough confidence in results of the raw vote to carry a healthy community and ecosystem through to the fruition of different core-protocol changes.
QRL Improvement Proposal #16 (QIP-016)’s proposition was to reduce the emission rate by a multiplication factor of 0.4x due to “Network and transaction analysis [revealing] that the majority of the network hashrate is made up of ~90% for profit miners, with 60% of that from autoswitching bots.”
As part of the QIP process, the draft passed through discussion period, garnering 54 comments before being final adjustments and a vote parameter selection. Before the vote, a pre-vote synopsis was formed which outlined the positive and negative considerations for voting.
Finally, the vote started on November 2nd, lasting for two weeks until November 16th, at which point a post-vote determination needed to be made. More on that determination can be read in our final comment on QIP-016. This moved QIP-016 from “proposal->draft” to “proposal->open->in development”.
QIP-016 development timeline
When we have a better indication of timescales, we’ll be able to give another update as to when, but it should be a few weeks of development time, which has no external dependencies/influences, followed by deployment, and a node upgrade window which needs to be coordinated with key node operators.
Due to needing to coordinate a node update with key node operators (pools, exchanges, etc), that may conflict with staffing holidays, and put the end fork date into early Q1 2022.
Quantum computing race heats up
It’s nearing the end of the 2021 and there’s no denying that the quantum computing space is heating up. In the same month, we’ve broken records for both the largest quantum computing company and physical qubits for a quantum computer.
IBM’s 127-qubit Eagle Processor
IBM quantum broke the 100-qubit processor barrior with their Eagle processor, representing an important milestone in the IBM Quantum Roadmap by “solving challenges across hardware and software to eventually realize a quantum computer capable of solving practical problems in fields from renewable energy to finance and more.”
This processor includes a 3d architecture and readout multiplexing, removing the need for readout electronics for each qubit and thereby reducing the bulk for processors with higher qubit counts, such as their 433 qubit osprey processor slated for 2022, or their 1121 qubit condor processor expected in 2023.
QuEra’s 256-atom qubit simulator
Adding fuel to the fire, QuEra has come out of stealth using Rydberg atoms, with temperatures over a thousand times colder than the superconducting qubits by IBM and Google. and whose conditional gate logic connects through something known as a “Rydberg blockade”.
From QuEra: In Rydberg blockade, laser flashes drive electrons in selected atoms to an outer orbital which causes the parent atoms to briefly “puff up” – but only on the condition that it is not blocked by another puffed up atom. This blockade forms QuEra’s conditional logic gate and can happen in as short of a time period as a few nanoseconds, once again similar to a 1990s Intel CPU.
The roadmap of QuEra is aggressive, with a 64-qubit quantum computer expected “soon”, and a 1024-qubit quantum computer by 2024. For context, by 2024, IonQ is targeting 32 algorithmic qubits, and IBM is targeting 1121-qubits by 2023. Not to be forgotten, currently IBM and PsiQuantum are targeting 1 million physical qubit quantum computers by the end of the decade.
Critically, not all qubits are made equally, and it remains to be seen how well these perform at the end of the day (or year). To try and measure qubits across systems, IonQ has proposed something called Algorithmic Qubits, where as IBM will be measuring using Quantum Volume in conjunction with CLOPS (Circuit Layers Operations Per Second).
Honeywell creates largest global quantum computer company, Quantinuum
The thing that is clear though, is that there is a tremendous amount of money being put into this with a lot at stake. This is noted by Honeywell creating the largest global quantum computer company, Quantinuum, with a majority stake. Their first product is slated to launch in a few weeks (just in time for Christmas?) which promises to be “the first genuine quantum product for use in the real world.”.
If this is true, we could be seeing the beginning of the quantum era, where practical and commercially viable quantum computers start to see some limited use for applications that can’t be reasonably done in polynomial time on classical supercomputers.
Additional quantum news
- Quantum computing would get boost in Senate defense bill
- Digitized adiabatic quantum factorization
- Two of World’s Biggest Quantum Computers Made in China
- Using new quantum computing architectures to create time crystals
First Russian campaign launched (by 4d5a in Discord)
p2pq.trade QRL Nodes and Sticker packs
James P of p2pq Coffee Trades, has released pre-built QRL Nodes. The node dual boots between Windows 10 and Kubuntu and is currently accepting Fiat or QRL/Quanta for the machines. Exciting to see where this goes!
You can also get QRL sticker packs to disperse into the world (or keep for yourself), which were released last month.
- [c8e7a5a] Fix wrapping of message on tx result page
- [ee01224] Windows message tx fixes and version bump to 1.7.3
- [74f595b] Update meteor install in CI
- [32bc1df] sudo for meteor install in CI
- [9da411d] Remove CI cache
-  Return to curl install meteor in CI
- [25c5ba2] update node orb
- [f68f9d9] Install USB packages in CI
When running cmake, it will fail to on the download step for googletest:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
[ 22%] Performing download step (git clone) for 'googletest' Cloning into 'googletest-src'... fatal: invalid reference: master CMake Error at googletest-download/googletest-prefix/tmp/googletest-gitclone.cmake:40 (message): Failed to checkout tag: 'master' gmake: *** [CMakeFiles/googletest.dir/build.make:99: googletest-prefix/src/googletest-stamp/googletest-download] Error 1 gmake: *** [CMakeFiles/Makefile2:83: CMakeFiles/googletest.dir/all] Error 2 gmake: *** [Makefile:91: all] Error 2 CMake Error at CMakeLists.txt:182 (message): Build step for googletest failed: 2 -- Configuring incomplete, errors occurred!
This is due to it trying to fetch the branch “master”, which has been renamed to “main”. This commit updates the repository name so that it will fetch it again.
- [64fb731] Fixed Googletest failing to fetch on compile by updating to new branch location
Googletest was failing to build because the repository changed the primary branch from ‘master’ to ‘main’.
Fixed by changing git tag to reference main instead of master.
- [e5c43ee] Change git tag for googletest from master to main
- [bae1f6b] Add Golang to CI setup
- [877e473] delete cached modules
- [54f7c08] Remove git submodule
- [35cb9b0] Merge remote-tracking branch ‘upstream/main’ into main
- [b28033d] Pull qips from theQRL/qips and add basic qip pages
- [75d388e] Improve comprehensibility that Bittrex is Bittrex Global
- [b1aa47d] Add module files
- [cfdca40] New media blog, how do you create a quantum resistant wallet?
- [d6828a7] Update stats
- [917a947] New media blog pq-cryptography with geometry labs
- [61bf391] webp -> png
- [938e709] Content: Link corrections, additions, and content adjustment
Special thanks to Discord user cooper for the suggestion of scroll-depth
- [8ee61e1] Add maxscrolldepth to universal analytics
- [4a4681c] Add cnet
- [a46f3b6] Merge remote-tracking branch ‘upstream/main’ into main
- [1300fa0] Replace discord.gg links to /discord to prevent link expiry/rot
- [bfdf6f1] Add Ledger Nano S/X instructions to QIP-016 voting guide
- [3e468eb] Add BlogPosting schema to blog-posts
- [d1cf7e9] Improve single page content style to reflect blog-articles
-  Add in-q-tel as an intelligence agency to the-future-of-pq-blockchains
- [926674b] Links for wallet release v1.7.3
- [252d9c6] Fix grammar. Add qcinvolvement image and asset
- [f14c514] grammar fixes. Thanks Ryan.
- [d88c8a3] Updated header asset for last month blog.
- [7cb8a24] Update discord link
- [51768c7] Twitter tag update
- [593bf92] Update Invite Link
- [9ce8ffd] add: blog svg assets
- [618fd68] add: more blog svg assets
- [891752c] add hugo_build.lock to gitignore
-  blog: last month at qrl october 2021
- [7e3f58e] support for youtube-blog-transcripts
- [9f11724] youtube-blog-transcript: is bitcoin a ponzi scheme
- [77fe874] Revert “Twitter tag update”
- [70be5e3] -testnet +special note
- [9125bb5] Better clarity to voting
-  clarification
- [84aac04] Update index.md
- [bcf4597] Update index.md
- [4059bd0] Better margins for images proceeded by headings
- [8a82325] Add timeline context to QIP016
- [14bd30d] Expand Enqlave feature for Ethereum users
- [dc9a6ec] new: multi-signature transactions feature page
- [a4f388a] and image
- [eb4cc2a] Proper image aspect ratio for blog listings
- [624937d] new: page stub for 4d5a
- [51d6d34] add video to multisig page
- [85352be] new blog: on-chain voting guide for QIP-016
- [349eaa6] Add snapshot block-height + minor content fixes
- [e83e89e] post-quantum future update based on chat in discord
Want to learn more?
Want to dig into our audited, MIT open-source, enterprise-grade codebase? Check out our github at: https://github.com/theQRL/QRL/
1st December 2021