Introduction
WRCode represents a proposed standard for secure, verifiable QR Code-triggered automation. Building on familiar QR Code technology, WRCode introduces strict security guidelines, account-based identity anchoring, and trustless user control while maintaining accessibility and privacy. This paper outlines additional security, resilience, and automation concepts that complete the WRCode ecosystem.
Core Principles
Mandatory Identity for WRCode Issuers: All entities generating WRCode automations—including merchants, service providers, and organizations—must register through wrcode.org and undergo identity verification. Their identities are anchored tamper-proof on the IOTA blockchain as part of WRCode’s foundational security design.
Free Access for Users: Individual users interacting with WRCode automations retain the freedom to do so without mandatory identification. Identity anchoring for users is strictly optional and only applies where specific use cases (e.g., regulatory compliance, service personalization, or recovery) require it.
Optional Identity Anchoring for Users
Users may opt into a lightweight identity anchoring system to:
Unlock faster service in high-trust scenarios (e.g., hotel check-in, car rental).
Enable automated invoicing, business travel expense management, and personalization.
Facilitate optional Vault recovery and revocation in case of device loss, ensuring users can securely disable lost Vaults and restore their identity on a new device.
The identity anchor is derived exclusively from the user’s email address, cryptographically hashed and securely anchored on IOTA. No other personal information is collected, exposed, or shared with WRCode providers, and the email remains private. It is neither published nor shared unless required by lawful authority. WRCode.org’s role is limited to verifying the authenticity and integrity of the anchor without the ability to access or disclose the user’s identity.
Resilience: Trustless Vault Backup and Revocation
To ensure continuity and user safety in case of device loss, WRCode introduces an optional backup and recovery feature based on trustless security by design:
Encrypted Backup: Vaults are backed up locally or optionally in encrypted cloud storage, always tied to the user’s WRCode account (email address). A cryptographic hash of the original device’s hardware fingerprint must be saved by the user (on a USB stick, hardware key, or secure medium). Restoration requires:
The verified email account.
The hardware fingerprint from the original device.
The user-defined passphrase.
Mandatory Multi-Factor Recovery: A portion of the recovery data is stored as an account-bound hash fragment. Without all three factors—account access, device fingerprint, and passphrase—the Vault remains permanently inaccessible. Even if the Vault container is copied, it cannot be decrypted without the full set of credentials.
Tamper-Proof Revocation: In case of device loss, users can revoke the old Vault and issue a new Vault bound to new hardware, ensuring continuity without compromising security. This recovery feature is offered as part of WRCode’s optional premium service tier.
Self-Controlled: Neither WRCode.org nor any third party holds decryption capability. All sensitive operations remain exclusively under user control.
This layered approach ensures that Vaults cannot be stolen, copied, or misused—upholding true trustless security.
Contextual Automation: Local AI Assistance
To enhance usability while preserving privacy, WRCode supports the use of lightweight, device-local language models (LLMs), securely stored and executed within the Vault:
Users can issue simple voice or text commands (e.g., “Late checkout” or “Order coffee”) processed entirely on-device.
The local LLM assists in mapping user preferences to automation templates without exposing data to external servers.
