QRL On-Chain Messages & Memos
Text committed to the QRL chain, newest first — both dedicated message transactions (bytes anchored on their own) and memos attached to transfers (a note riding along with a payment). Each entry is tagged; readable payloads render as text, binary payloads (notarisation hashes, structured proofs) render as hex.
Loading…
FAQ about messages
Common questions about this page
- What is the difference between a message and a memo?
- A **message** is a dedicated `message` transaction — it exists purely to anchor bytes on-chain and moves no coins. A **memo** is a short note attached to a normal `transfer` (proto Transfer.message_data), so it rides along with a payment — like the reference field on a bank transfer. This feed shows both; each row is tagged so you can tell them apart, and you can filter to one kind.
- What is a QRL message transaction?
- QRL has a dedicated `message` transaction subtype that anchors arbitrary bytes on-chain — permanently and immutably. People use it for public notes, proofs of existence, and document notarisation. It is a native subtype, not a smart contract.
- Why do some entries show as binary?
- The payload is raw bytes. When it decodes cleanly as UTF-8 text we show the text; anything else (hashes, timestamps, structured proofs) is shown as hex with a binary label. Both views are the verbatim on-chain payload.
- Can messages be sent on QRL 2.0?
- No — QRL 2.0 is EVM-compatible and has no message subtype. The closest analogue there is transaction calldata. This browser therefore only covers the original Proof-of-Work chain.
- Is sending a message expensive?
- A message transaction pays the normal QRL transaction fee — typically a fraction of a cent. Because the chain is quantum-resistant, a message anchored here inherits post-quantum signature security.