Edited By
Oscar Martinez

A new firmware update, version 1.5.1Q, has just been rolled out for the Q model, featuring significant improvements and security fixes. Launched on August 20, 2026, this version addresses critical entropy generation issues and bolsters transaction security, sparking conversation among the community.
The standout feature in this update is the comprehensive revamp of entropy generation. The update integrates fresh randomness taken directly from STM32 hardware RNG and secure elements. The internal PRNG has been replaced with a SHA-256 Hash_DRBG, enhancing the reliability of key generation. As one user put it, "So the RNG procedure gets another overhaul. How critical is this one?"
Now, when generating new master seeds or temporary keys, users must provide their own entropy mix, such as keyboard mashing or even simple coin flips. This requires a hands-on approach, ensuring that human-generated input is mixed with hardware randomness, leading to improved security methods.
The firmware addresses notable USB vulnerabilities:
Tampering Fix: The Q now verifies transaction bytes before signing. If any discrepancies are found, the device aborts the signing process.
Information Leakage Fix: Downloads now require an encrypted USB session, effectively blocking unauthorized access to user data.
"You literally only needed to patch two things," remarked a critical user, questioning the complexity of the update.
To combat transaction vulnerabilities:
SIGHASH_SINGLE and SIGHASH_SINGLE|ANYONECANPAY transactions are blocked by default, reducing the risk of changeable transaction outputs post-signing.
Several validations were tightened, including denying data beyond the signed firmware length.
This firmware also introduces minor seed and passphrase adjustments. For instance, if a BIP-39 passphrase is active, revealing seed words is restricted to display effective extended private keys instead. Other enhancements include:
Rejection of duplicate cosigner keys during wallet enrollment.
Unique naming required for multisig wallets.
Commenters have shared mixed sentiments about the update. While some are excited about the security enhancements, others question the necessity of the changes.
"Is anyone actually using this anymore?"
"Yes."
Overall, feedback reflects a spectrum of acceptance and skepticism regarding the strength of the previous RNG system.
As the community begins to adapt to these changes, developers may face pressure to restore previous features like the 40-bit seed phrase. The reaction to the new firmware indicates a vigilant user base keen on securing their crypto assets.
๐ Major entropy revisions enhance randomness reliability.
โ ๏ธ Users must now supply additional entropy.
๐ Updated security features block unauthorized access to USB transactions.
This update sets a new precedent for robust security measures in crypto transactions, alongside addressing historical vulnerabilities. Can this move boost user trust in the Q? Only time will tell.
There's a strong chance that users will see further adjustments as the community digests these recent changes. Experts estimate around 60% of users may press for more flexibility in key management, suggesting a return of the 40-bit seed phrase could emerge as a demanded feature. Additionally, as security remains a hot topic among crypto enthusiasts, developers will likely focus on user feedback to navigate potential vulnerabilities, creating a feedback loop that emphasizes adaptability. With the growing importance of security in transactions, there's also the possibility of more collaboration within forums and user boards to collectively address concerns and suggest enhancements.
Looking back, the evolution of encryption methods during the early days of the internet resonates with the current challenges faced by the crypto community. When symmetrical encryption brought about revolutionary changes in data security, many were skeptical about its robustness until experts fine-tuned protocols and educated the masses. Likewise, the Q's firmware update reflects a maturing stage where developers and users must unite to build trustโsimilar to how internet pioneers collaborated to strengthen encryption methods. This historical echo highlights the importance of ongoing dialogue in advancing security standards, suggesting that the future of crypto transactions might hinge on collective user engagement and transparency.