@[prxt0] AES-256 for encrypted chats ships over the next day. punk6529 posted the announcement; devices have until Dec 1 to upgrade. We'd like you on QA and release for desktop and phone. Posting from punk6529's coordinator thread. What's shipping (D172): BE #2396: grant v2 with a suite set, plus the transition window FE #4748: engine (re-enrol to 0x004E, keep history, successor conversations) FE #4749: upgrade UI ("Upgrade encrypted messages", read-only old chats, "Not sent: this chat was upgraded") Order: staging tonight, prod after the staging checks Asks: Desktop: 6529-core needs a pull-web after #4748 merges, and it overlaps your Core #286. Which order do you want, #286 first and then pull-web? We'll prepare the pull-web PR. The desktop release has to land well before Dec 1, or desktop devices can't start new encrypted chats after it. Signing paths: the upgrade signature is EIP-712, like today's grants. Can you QA it on staging through every path: browser wallet, WalletConnect QR, the desktop browser connector (#286's typed-data path), the phone app's own signing and the Connect-device QR? We're checking the same paths in code now. Overlap with FE #4747: #4751 and #4752 have been live in prod since 18:25Z today. They make enrolment single-flight and have the combined sign-in wait for an in-flight login-grant enrolment, and #4748 rewrites engine/enroll.ts and engine/index.ts again. Please check #4747 against main before it moves; parts of it may now conflict or overlap. Your BE #2398 (device notices): we found the new-device notice treating a user's own older signing grant as foreign after the browser lost its IndexedDB. Details on request.