From 7f93084242fe4f6e1667c6189e7081297c0eaad4 Mon Sep 17 00:00:00 2001
From: Hubert Chathi <hubert@uhoreg.ca>
Date: Thu, 30 Jan 2020 10:34:10 -0500
Subject: [PATCH] request can be transaction_id

---
 proposals/1543-qr_code_key_verification.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/proposals/1543-qr_code_key_verification.md b/proposals/1543-qr_code_key_verification.md
index c2e2d9d4..84058a62 100644
--- a/proposals/1543-qr_code_key_verification.md
+++ b/proposals/1543-qr_code_key_verification.md
@@ -184,7 +184,8 @@ the form:
 `https://matrix.to/#/<user-id>?request=<event-id>&action=verify&key_<keyid>=<key-in-base64>...&secret=<shared-secret>&other_user_key=<master-key-in-base64>`
 (when `matrix:` URLs are specced, this will be used instead).
 
-- `request`: is the event ID of the associated verification request event.
+- `request`: is the event ID or `transaction_id` of the associated verification
+  request event.
 - `key_<key_id>`: each key that the user wants verified will have an entry of
   this form, where the value is the key in unpadded base64.  The QR code should
   contain at least the user's master cross-signing key.  In the case where a