Verus request QR creator · request families in practice

Nine tabs, one pipeline

A reading course through the Verus Request QR Creator: how each request tab builds its VDXF details object, what its flags mean, and how the signed request becomes a QR code a wallet can act on.

Source: BuildWithDreams/verus-identity-update-qr-creator-main · Companion to the primitives book

Every tab does the same four things: validate input, build a details object, wrap it in a GenericRequest, sign and encode. What varies is the details class, the flags, and — twice — that more than one detail is needed.

Contents

  1. 01Orientation — a QR factory for Verus requestsRead
  2. 02The shared pipeline — two functions, nine callersRead
  3. 03Update Identity — the minimal pathRead
  4. 04Service signer — when the service signs, not the userRead
  5. 05Authentication — prove control, constrain the answerRead
  6. 06Invoice — flags are the payment policyRead
  7. 07App Encryption — two details, in orderRead
  8. 08Data Packet — six flags, one payloadRead
  9. 09User Data — ask for named fieldsRead
  10. 10Attestation — a data packet with a prologueRead
  11. 11Transaction signing — the escape hatchRead
  12. 12Synthesis — nine tabs, one recipeRead

Which tab maps to which primitive

TabDetails classNotable additions
Update IdentityIdentityUpdateRequestDetailsBuilt from CLI-shaped JSON
Service signerIdentityUpdateRequestDetailsService key, generated request id, callback + status
AuthenticationAuthenticationRequestDetailsRecipient constraints (ID / system / parent)
InvoiceVerusPayInvoiceDetailsOptional signature; payment-policy flags
App EncryptionAppEncryptionRequestDetailsAuth detail first; round-trip verification
Data PacketDataPacketRequestDetailsSix flags; URL descriptor; flag workaround
User DataUserDataRequestDetailsRequested keys; full/partial modes
AttestationDataPacketRequestDetailssigndata → MMRDescriptor + SignatureData → DataDescriptor
TX SigningGeneralTypeOrdinalVDXFObjectJSON payload in a general-purpose object

Read this first if…

You want to…Go to
Understand how any tab works02, then the tab's chapter
Build a new tab02 → 03 → 12
Debug a QR the wallet rejects02 (signing + redirects), then the tab
Understand attestations10 (and 08 first)
Understand the byte-level meaningthe companion primitives book

Scope note

This book reads the repository as it stands on main, including the transaction-signing tab that post-dates the original tab set. Behaviour described here is the app's wiring of the primitives, not a specification of the wallet's handling — where the two could differ, the text says so.