v1 (PoW) on QRL.dev

Know what your node is running

Sun, 27 Sep 2026 09:00:00 +0000

A running container answers one question: did the process start? It does not tell you which image is running, where its data lives, or whether the application is ready. Those distinctions matter when you are debugging a local node.

This note is an inspection checklist for an existing development container. The examples use qrl-node as its name; replace that with your own. It is not an installation recipe.

Start with the image

Inspect both the configured image reference and the immutable image ID. A tag is convenient, but the image ID helps establish what was actually used on this machine.

Keep the wallet boundary small

Sat, 26 Sep 2026 09:00:00 +0000

A wallet interface has two very different jobs: helping someone understand a transaction, and authorising that transaction. Treat them as separate parts of the application.

Separate the states

A transaction preview should describe what the user is about to do without needing access to secret material. The signing layer should receive a clearly defined request only after confirmation.

typescript

// Illustrative UI model; not a QRL signing API.
type TransactionReview = {
  recipient: string;
  amountDisplay: string;
  feeDisplay: string;
};

type ReviewState =
  | { status: 'editing' }
  | { status: 'reviewing'; transaction: TransactionReview }
  | { status: 'submitted'; transactionHash: string };

Keep display formatting separate from the integer amounts used by the underlying protocol. A human-readable amount is not a validated transaction value.

An explorer is a debugging tool

Fri, 25 Sep 2026 09:00:00 +0000

“Something went wrong” is hard to investigate. A transaction reference, an observation time, and the expected outcome give another developer a place to begin.

Capture the context

When recording a blockchain observation, write down the network, the identifier you looked up, and what the explorer showed at that moment. Distinguish an absent record from an error fetching that record.

json

{
  "network": "record the network",
  "transaction": "record the transaction hash",
  "observedAt": "record the UTC observation time",
  "expected": "describe the expected result",
  "actual": "describe the observed result"
}

This is a suggested issue-report structure, not an explorer API response.

Find the right cryptography library

Thu, 24 Sep 2026 09:00:00 +0000

Before adding a cryptography dependency, establish which protocol and runtime your application targets. A familiar repository name is not enough to show that a library is appropriate for your application.

Start with the protocol

QRL v1 uses XMSS. Its one-time signature state is an application concern as well as a cryptographic one. Read the library documentation and the wallet’s state-management approach before integrating signing.

The qrllib repository is the QRL core library. The organisation also maintains go-qrllib, described as a Go implementation of the QRL cryptographic library.