Know what your node is running
A small Docker inspection routine that makes local QRL development easier to understand, reproduce, and debug.
Read noteTHE JOURNAL
Latest notes
Keep the wallet boundary small
Separate interface state from signing state, and make the irreversible steps easy to review.
Read noteAn explorer is a debugging tool
Use blocks, addresses, and transaction references to turn a vague report into a reproducible observation.
Read noteFind the right cryptography library
A starting map of QRL’s cryptographic code, with version boundaries kept explicit.
Read noteA map of the Zond developer stack
Get oriented across clients, browser wallets, and the example dApp before choosing where to contribute.
Read note