How the decryption pipeline runs
Your 64-digit hex key is parsed to 32 raw bytes. An HMAC-SHA256-based key derivation (the `encryptionLoop` construction from wa-crypt-tools, with the info string 'backup encryption') derives the AES-256-GCM key. Not standard HKDF; matches WhatsApp's Android client. The Crypt15 protobuf header surfaces the IV (12 or 16 bytes). AES-GCM decrypts and authenticates the ciphertext in one step, so wrong keys produce an authentication tag failure rather than garbled output, and bad keys are caught instantly. The plaintext is gzip-compressed SQLite; Chat Hoarding app gunzips it and writes the raw msgstore.db to a staging folder before bundling into .tarc.