FailSafe: Advanced Security for Digital Assets
  • Introduction to FailSafe
  • Whitepaper
    • Introduction
      • Defense-in-Depth
      • Forward Security
    • Web3 Threats to Your Crypto
      • The Human Factor: Design with Operator Error in Mind
    • Defense-in-Depth & the Lifecycle of a Transaction
      • Defense 1: de-risk Web3 Asset Positions
      • Defense 2: FailSafe Blockchain Reconnaissance
      • Defense 3: FailSafe Interceptor Service
      • Discussion
    • FailSafe Architecture
      • Forward Security in FailSafe
        • Quantum Threats to EVM-based Blockchains
          • On ECDSA Key Re-use
          • On New Quantum-resilient Alternatives
          • Account Abstraction as a Path to Sunseting ECDSA on Ethereum?
        • Introducing the Quantum Migration Tool (qMig)
          • Assumptions and Goals
          • How Does qMig work?
          • Discussion
          • FailSafe+qMig
    • Conclusion
    • Further Reading
  • How FailSafe helps your Organisation
    • Reduce Attack Surface Area
    • Radar for Security Risks
    • React to Malicious Threats
    • Forward Security against Looming Quantum Computing Threats
  • FailSafe as a tool for Enterprise Risk Management
Powered by GitBook
On this page
  1. Whitepaper
  2. FailSafe Architecture
  3. Forward Security in FailSafe
  4. Introducing the Quantum Migration Tool (qMig)

Assumptions and Goals

Last updated 2 years ago

  • The quantum inflection point (quantum attack breakthrough) may occur when the large majority of Web3 assets and transactions are done on blockchains reliant on ECDSA.

  • Web3 tokens (ERC20, ERC721, etc.) are only allowed to be bridged (e.g., via ) to a quantum resilient network, if and only if these assets have not been hijacked via ECDSA compromise. That is, this transfer must be based on a cryptographic scheme that remains secure even after the above quantum inflection point occurs.

  • While users could reduce their own exposure to the attack by not reusing the same address across transactions, it is not a prerequisite for using qMig. qMig should prevent movement of stolen funds, while supporting EOAs with prior transaction history.

Figure 3: qMig: Timeline and Approach
LayerZero