> ## Documentation Index > Fetch the complete documentation index at: https://docs.teqoin.io/llms.txt > Use this file to discover all available pages before exploring further. # Challenge Period Explained > Understanding the 7-day waiting period for TeQoin L2 withdrawals # Challenge Period Explained Learn why withdrawals from TeQoin L2 to Ethereum require a 7-day waiting period, and how this ensures your funds are always safe. **TL;DR:** The 7-day challenge period is a **security feature** that protects your funds by allowing time to detect and prove fraud. It's not a limitationβ€”it's what makes TeQoin trustless and secure without relying on centralized parties. *** ## πŸ€” What is the Challenge Period? The **challenge period** is a 7-day waiting time between when you initiate a withdrawal on L2 and when you can finalize it on L1. ### Timeline ```mermaid theme={null} gantt title Withdrawal Timeline dateFormat YYYY-MM-DD section L2 Initiate Withdrawal :done, init, 2026-02-22, 1d ETH Burned on L2 :done, burn, 2026-02-22, 1d section Challenge Period Day 1 :active, day1, 2026-02-23, 1d Day 2 :active, day2, 2026-02-24, 1d Day 3 :active, day3, 2026-02-25, 1d Day 4 :active, day4, 2026-02-26, 1d Day 5 :active, day5, 2026-02-27, 1d Day 6 :active, day6, 2026-02-28, 1d Day 7 :active, day7, 2026-03-01, 1d section L1 Ready to Finalize :milestone, ready, 2026-03-01, 0d Finalize on L1 :crit, final, 2026-03-01, 1d ETH Received :milestone, done, 2026-03-01, 0d ``` **Day 0:** Initiate withdrawal on L2\ **Days 1-7:** Challenge period (waiting)\ **Day 7+:** Finalize withdrawal on L1 *** ## 🎯 Why Does It Exist? ### The Problem It Solves Optimistic rollups like TeQoin assume transactions are valid by default. But what if someone tries to cheat? **Without a challenge period:** ``` ❌ Malicious sequencer submits invalid withdrawal ❌ Withdrawal processes immediately ❌ Funds are stolen before anyone can react ❌ No way to stop it ``` **With a 7-day challenge period:** ``` βœ… Malicious sequencer submits invalid withdrawal βœ… 7-day window opens βœ… Anyone can detect and challenge it βœ… Fraud proof submitted to L1 βœ… Invalid withdrawal is blocked βœ… Funds are safe ``` ### Real-World Analogy Think of it like a bank check: **Bank Check (Traditional):** * You write a check * Bank holds it for 3-5 business days * Time for bank to verify funds exist * Protects against fraud **TeQoin Withdrawal (Blockchain):** * You initiate withdrawal * Bridge holds it for 7 days * Time for network to verify it's valid * Protects against invalid transactions *** ## πŸ” How It Provides Security ### Optimistic Rollup Model Transactions are assumed to be valid by default. **Benefit:** Fast processing, low cost **Trade-off:** Need time to verify if challenged During the 7-day period, anyone can: * Download L2 transaction data from L1 * Re-execute transactions independently * Verify the state is correct * Submit fraud proof if something is wrong **This is decentralized security!** If someone detects invalid data: 1. They submit a fraud proof to L1 2. L1 smart contract verifies the proof 3. If proof is valid, invalid withdrawal is reverted 4. Challenger earns a reward 5. Malicious actor is penalized **Your funds are protected by math and code, not trust.** You don't need to do anything: * Multiple parties monitor the network * Automated systems check for fraud * Economic incentives ensure verification * If fraud occurs, it's caught and stopped **Security is built-in and automatic.** *** ## πŸ“Š Challenge Period in Action ### What Happens During 7 Days? **Your perspective:** ``` Day 0: Initiate withdrawal on L2 βœ… Transaction confirmed (~5 seconds) πŸ”₯ Your L2 ETH is burned πŸ“ Withdrawal recorded in bridge Days 1-6: Wait ⏰ Challenge period active πŸ’€ Nothing to do - just wait πŸ“Š Track progress on bridge interface Day 7: Ready to finalize βœ… Challenge period complete πŸ”“ Can finalize on L1 anytime πŸ’° Receive your ETH on L1 ``` **What the network does:** ``` Day 0: Sequencer processes withdrawal πŸ“€ Posts state root to L1 πŸ”— Includes withdrawal in batch Days 1-7: Verification period πŸ‘€ Watchers monitor state roots πŸ” Verifiers check transaction validity πŸ€– Automated systems scan for fraud πŸ’» Full nodes re-execute transactions βœ… Everything checks out (normal case) Day 7: Finalization enabled πŸ”“ Withdrawal proven valid βœ… Ready for user to claim on L1 ``` **Fraud prevention in action:** ``` Day 0: Malicious withdrawal submitted 🚨 Invalid state root posted Day 2: Verifier detects fraud πŸ” Re-executes transactions ❌ State doesn't match πŸ“ Prepares fraud proof Day 3: Fraud proof submitted πŸ“€ Proof sent to L1 contract βš–οΈ L1 contract verifies proof βœ… Proof is valid Day 3: Fraud prevented β›” Invalid withdrawal blocked πŸ† Challenger rewarded πŸ’° Malicious actor penalized βœ… Other withdrawals unaffected ``` **Your legitimate withdrawal is safe!** *** ## πŸ’‘ Why 7 Days Specifically? ### The Calculation | Factor | Consideration | | ---------------------- | ---------------------------------------------------------- | | **Detection Time** | Need enough time for independent verifiers to notice fraud | | **Proof Generation** | Time to compute and submit fraud proofs | | **Network Diversity** | Different time zones, various verification setups | | **Safety Margin** | Extra buffer for unexpected delays | | **Emergency Response** | Time for community to coordinate if needed | **7 days balances:** * βœ… Strong security (enough time to catch fraud) * βœ… Reasonable UX (not too long to wait) * βœ… Industry standard (same as Optimism, Arbitrum) ### Could It Be Shorter? **Technically yes, but:** * ❌ Less time = less security * ❌ Harder for independent verification * ❌ More centralization required * ❌ Higher risk of successful fraud **7 days is the sweet spot** that the industry has converged on through research and experience. *** ## πŸ†š Comparison with Other L2s ### Industry Standard | L2 Solution | Challenge Period | Technology | | ----------------- | ---------------- | ------------------------------- | | **TeQoin** | 7 days | Optimistic Rollup | | **Optimism** | 7 days | Optimistic Rollup | | **Arbitrum** | 7 days | Optimistic Rollup | | **Base** | 7 days | Optimistic Rollup | | **zkSync** | \~Hours | ZK Rollup (no challenge needed) | | **Polygon zkEVM** | \~Hours | ZK Rollup (no challenge needed) | **Why do ZK rollups not need challenge periods?** ZK (zero-knowledge) rollups use cryptographic proofs that are verified instantly on L1. They're mathematically proven correct, so no challenge period is needed. **Trade-offs:** * ZK: Faster withdrawals, higher complexity, more expensive proving * Optimistic: 7-day withdrawals, simpler, cheaper operations TeQoin chose optimistic rollups for lower fees and simpler development. *** ## 🀷 Common Misconceptions **Reality:** It's a deliberate security feature, not a technical constraint. TeQoin could process withdrawals instantly from a technical perspective, but that would require trusting the sequencer. The 7-day period enables **trustless** security. **It's a feature, not a bug!** **Reality:** Your funds are secured by L1 smart contracts during the challenge period. * Your L2 ETH was already burned (can't be double-spent) * Your L1 ETH is reserved in the bridge (can't be taken) * The challenge period is verification time, not a "lock" **Your funds are safe and accounted for.** **Reality:** The network automatically protects you. You don't need to: * Monitor your withdrawal * Submit proofs yourself * Defend against challenges * Do anything during the 7 days Just initiate, wait 7 days, finalize. That's it! **Reality:** It's the oppositeβ€”the challenge period IS the security. Without it: * You'd have to trust the sequencer completely * No way to prove fraud * Centralized control With it: * Trustless verification * Decentralized security * Provable correctness **The challenge period makes TeQoin MORE secure.** **Reality:** Deposits and withdrawals have different security models. **Deposits (L1 β†’ L2):** * Ethereum L1 is the source of truth * L1 transaction is final when confirmed * Safe to credit on L2 immediately * **Fast: \~15 minutes** **Withdrawals (L2 β†’ L1):** * L2 is claiming from L1 * Need to verify L2 state is correct * Challenge period ensures validity * **Secure: 7 days** **Different directions, different security needs.** *** ## ⚑ Can I Avoid the Challenge Period? ### Official Bridge: No The official TeQoin bridge **always requires 7 days** for security. This cannot be bypassed. ### Third-Party Bridges: Yes (with trade-offs) Some third-party services offer "fast withdrawals": **Liquidity Provider Model:** 1. You initiate withdrawal on L2 2. Liquidity provider gives you ETH immediately on L1 3. Provider waits 7 days to claim your withdrawal 4. You pay a fee for the instant liquidity **You're essentially selling your withdrawal to someone willing to wait.** **Pros:** * ⚑ Instant L1 ETH (minutes, not days) * 🎯 Good for emergencies * πŸ’Ό Useful for traders **Cons:** * πŸ’° Fee (typically 0.1-1% of amount) * πŸ”’ Less secure (trust third party) * πŸ“‰ May have liquidity limits * 🚫 Not always available **Common fast bridge providers:** * Across Protocol * Hop Protocol * Connext * Celer cBridge **Use at your own risk!** These are third-party services: * Not endorsed by TeQoin * Additional smart contract risk * Potential for hacks/exploits * Always DYOR (Do Your Own Research) Official bridge = Safest option *** ## πŸŽ“ Technical Deep Dive ### For Developers and Technical Users **How L2 state is committed to L1:** 1. Sequencer batches L2 transactions 2. Computes new state root (Merkle root) 3. Posts state root to L1 every \~X hours 4. State root represents all L2 account balances **Challenge period allows verification that state root is correct.** ```solidity theme={null} // Simplified L1 contract mapping(uint256 => bytes32) public stateRoots; mapping(uint256 => uint256) public stateRootTimestamps; function submitStateRoot(bytes32 _stateRoot) external onlySequencer { uint256 index = stateRootIndex++; stateRoots[index] = _stateRoot; stateRootTimestamps[index] = block.timestamp; } function finalizeWithdrawal(/* params */) external { require( block.timestamp >= stateRootTimestamps[index] + 7 days, "Challenge period not complete" ); // Process withdrawal } ``` **How fraud is detected and proven:** **Detection:** 1. Verifier downloads transaction batch from L1 2. Re-executes transactions locally 3. Computes expected state root 4. Compares with sequencer's posted state root 5. If mismatch β†’ fraud detected **Proof:** 1. Verifier identifies fraudulent transaction 2. Generates Merkle proof showing discrepancy 3. Submits fraud proof to L1 contract 4. L1 contract re-executes single transaction 5. Verifies fraud proof is correct 6. Slashes sequencer, rewards challenger **Economic incentive ensures monitoring happens.** **Under the hood:** ``` L2 Initiation: 1. User calls L2Bridge.initiateWithdrawal(amount) 2. L2 burns user's ETH 3. Emits WithdrawalInitiated event 4. Event included in L2 block 5. Block data posted to L1 L1 Finalization: 1. User calls L1Bridge.finalizeWithdrawal(proof) 2. Contract verifies 7 days passed 3. Contract verifies Merkle proof 4. Contract unlocks ETH from L1 bridge 5. ETH sent to user's L1 address ``` The Merkle proof connects the L2 event to the L1 state root, proving the withdrawal is legitimate. *** ## πŸ’­ Philosophy: Security vs. Convenience ### The Trade-off ``` β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Fast Withdrawals (Instant) β”‚ β”‚ β”‚ β”‚ ❌ Must trust sequencer β”‚ β”‚ ❌ Centralized control β”‚ β”‚ ❌ No fraud protection β”‚ β”‚ ❌ Risk of fund loss β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ vs. β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Secure Withdrawals (7 days) β”‚ β”‚ β”‚ β”‚ βœ… Trustless verification β”‚ β”‚ βœ… Decentralized security β”‚ β”‚ βœ… Fraud proof protection β”‚ β”‚ βœ… Guaranteed fund safety β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ``` **TeQoin chose security.** *** ## πŸ“Œ Key Takeaways The 7-day period is a **security feature**, not a limitation Enables **trustless** operation without relying on centralized parties Protection is **automatic** - you don't need to do anything 7 days is the **standard** for all major optimistic rollups Allows time to detect and **prove fraud** if it occurs During challenge period, your funds are **secured by L1 contracts** *** ## 🎯 Practical Implications ### For Users **Plan Ahead** * Need L1 funds? Start withdrawal 7 days early * Keep some ETH on both L1 and L2 * Don't wait until you urgently need funds * Use third-party bridges only for emergencies ### For Developers **Design Around It** * Don't promise instant L2 β†’ L1 transfers * Educate users about the 7-day period * Consider L2-native solutions where possible * Use deposits (L1 β†’ L2) when speed matters *** ## πŸ“š Learn More Complete guide to withdrawing from L2 to L1 Common questions about the bridge Technical details on TeQoin's security How optimistic rollups work *** **Understand the challenge period?** Ready for [Bridge FAQ](/bridge/faq) β†’