Trezor should self-host its customer communication and shipping infrastructure

Overview Debates Related claims Topics Sources

Crypto holders should use offline phones instead of hardware wallets

Regulators should replace identity checks that collect personal data with digital proofs

AI developers should restrict coding assistants from generating potentially malicious code

Microsoft should disable device-code authentication by default

Tech companies should pause autonomous AI agent deployment until sandbox security is guaranteed

Revolut should refuse to pay the $3 million ransom demand

Revolut should pay the $3 million ransom to protect its customers' data

The EU Cyber Resilience Act should not retroactively apply to legacy products

The EU's 24-hour cybersecurity vulnerability reporting deadline is too short

Revolut should publicly identify the compromised government agency

Extensive KYC requirements create unacceptable security risks for financial customers

Third-party data leaks undermine the security of crypto hardware wallets

Coinkite should financially compensate victims of the Coldcard firmware exploit

Hardware wallet makers should never keep customers' home addresses

A leaked home address turns a hardware wallet owner into a physical target

A vendor cannot ship a physical device without a shipping address

Trezor stated that ShipMonk retained customer records from orders placed between November 2019 and August 2021 despite repeatedly providing written assurances that the data had been deleted

Trezor confirmed that its internal systems, devices, private keys, and wallet backups were not compromised, as the breach occurred entirely on ShipMonk's logistics end

Companies are responsible for data breaches at their third-party contractors

Physical security risks of hardware wallets outweigh their digital benefits