docs.dydx.community
Open in
urlscan Pro
2606:4700::6812:191
Public Scan
URL:
https://docs.dydx.community/dydx-governance/start-here/epochs
Submission: On April 07 via manual from DE — Scanned from DE
Submission: On April 07 via manual from DE — Scanned from DE
Form analysis
0 forms found in the DOMText Content
Home →Forums →Discord →Trade → Search… main Introduction Start Here Interface Restrictions Allocations Epochs Fee Discounts Treasury Rewards Retroactive Mining Rewards Trading Rewards Liquidity Provider Rewards STAKING POOLS Liquidity Module Safety Module Voting & Governance Architecture Proposal Lifecycle Voting Process Parameters Governance Guide RESOURCES Technical Overview Foundation Market Maker Onboarding Glossary External Links Forums dYdX Layer 2 dYdX Layer 2 API dYdX Trading Inc. Metrics Dashboard 挖矿简介 DYDX 介绍 中文问答 追溯性挖矿教程 交易挖矿教程 DYDX领取教程 交易教程 如何在dYdX上开空单(做空) 公告 关于暂停保险质押池的通知 Epoch 0回顾 Powered By GitBook Epochs An overview of the epoch system All rewards and staking contracts operate on 28 days cycles, referred to as epochs. A new epoch automatically begins when the current epoch ends. The following will occur at the end of each epoch: * Trading Rewards are distributed. Rewards are claimable at dydx.community approximately 7 days after the end of the epoch. * Liquidity Provider Rewards are distributed. Rewards are claimable at dydx.community approximately 7 days after the end of the epoch. * Requested withdrawals for the Liquidity Staking Pool in the ended epoch may be withdrawn. * Requested withdrawals for the Safety Staking Pool in the ended epoch may be withdrawn. The following will occur only at the end of Epoch 0: * Retroactive Mining Rewards will be distributed. Rewards are claimable at dydx.community approximately 8 days after the end of Epoch 0. * Transfers of DYDX are initially restricted. The Initial Transfer Restriction period will be lifted approximately 8 days after the end of Epoch 0. * DYDX will become transferable on September 8th, 2021 at 15:00:00 UTC. Epoch 0 will go live on August 3rd, 2021 at 15:00:00 UTC. The following table outlines epoch start and end dates (which can be modified by dYdX governance): Epoch Start Date (UTC) End Date (UTC) Days Cumulative Years 0 8/3/2021 15:00:00 8/31/2021 15:00:00 28 0.08 1 8/31/2021 15:00:00 9/28/2021 15:00:00 28 0.15 2 9/28/2021 15:00:00 10/26/2021 15:00:00 28 0.23 3 10/26/2021 15:00:00 11/23/2021 15:00:00 28 0.31 4 11/23/2021 15:00:00 12/21/2021 15:00:00 28 0.38 5 12/21/2021 15:00:00 1/18/2022 15:00:00 28 0.46 6 1/18/2022 15:00:00 2/15/2022 15:00:00 28 0.54 7 2/15/2022 15:00:00 3/15/2022 15:00:00 28 0.61 8 3/15/2022 15:00:00 4/12/2022 15:00:00 28 0.69 9 4/12/2022 15:00:00 5/10/2022 15:00:00 28 0.77 10 5/10/2022 15:00:00 6/7/2022 15:00:00 28 0.84 11 6/7/2022 15:00:00 7/5/2022 15:00:00 28 0.92 12 7/5/2022 15:00:00 8/2/2022 15:00:00 28 1.00 13 8/2/2022 15:00:00 8/30/2022 15:00:00 28 1.07 14 8/30/2022 15:00:00 9/27/2022 15:00:00 28 1.15 15 9/27/2022 15:00:00 10/25/2022 15:00:00 28 1.23 16 10/25/2022 15:00:00 11/22/2022 15:00:00 28 1.30 17 11/22/2022 15:00:00 12/20/2022 15:00:00 28 1.38 18 12/20/2022 15:00:00 1/17/2023 15:00:00 28 1.46 19 1/17/2023 15:00:00 2/14/2023 15:00:00 28 1.53 20 2/14/2023 15:00:00 3/14/2023 15:00:00 28 1.61 21 3/14/2023 15:00:00 4/11/2023 15:00:00 28 1.69 22 4/11/2023 15:00:00 5/9/2023 15:00:00 28 1.76 23 5/9/2023 15:00:00 6/6/2023 15:00:00 28 1.84 24 6/6/2023 15:00:00 7/4/2023 15:00:00 28 1.92 25 7/4/2023 15:00:00 8/1/2023 15:00:00 28 1.99 26 8/1/2023 15:00:00 8/29/2023 15:00:00 28 2.07 27 8/29/2023 15:00:00 9/26/2023 15:00:00 28 2.15 28 9/26/2023 15:00:00 10/24/2023 15:00:00 28 2.22 29 10/24/2023 15:00:00 11/21/2023 15:00:00 28 2.30 30 11/21/2023 15:00:00 12/19/2023 15:00:00 28 2.38 31 12/19/2023 15:00:00 1/16/2024 15:00:00 28 2.45 32 1/16/2024 15:00:00 2/13/2024 15:00:00 28 2.53 33 2/13/2024 15:00:00 3/12/2024 15:00:00 28 2.61 34 3/12/2024 15:00:00 4/9/2024 15:00:00 28 2.68 35 4/9/2024 15:00:00 5/7/2024 15:00:00 28 2.76 36 5/7/2024 15:00:00 6/4/2024 15:00:00 28 2.84 37 6/4/2024 15:00:00 7/2/2024 15:00:00 28 2.92 38 7/2/2024 15:00:00 7/30/2024 15:00:00 28 2.99 39 7/30/2024 15:00:00 8/27/2024 15:00:00 28 3.07 The dYdX Foundation has created a public Google Calendar with start / end dates for Epochs and Blackout Windows - you can subscribe here. WHEN WILL THE REWARDS AND STAKING POOLS BE ACTIVATED? * The Retroactive Mining Rewards are now live on the Protocol. These rewards will run until August 31th, 2021, 15:00:00 UTC. * The Trading Rewards are now live on the Protocol. These rewards will run until August 3rd, 2026, 15:00:00 UTC. * The Liquidity Provider Rewards is now live on the Protocol. These rewards will run until August 3rd, 2026, 15:00:00 UTC. * The Liquidity Staking pool is now live on the Protocol. This pool will run until August 2nd, 2026, at approximately 15:00:00 UTC (exact timestamp: 1785682798). * The Safety Staking pool will automatically go live on the Protocol a few days after the end of epoch 0 when transfer restrictions are lifted. This pool will run until September 7th, 2026, at approximately 15:00:00 UTC (exact timestamp: 1788793198). CAN DYDX GOVERNANCE MODIFY THE EPOCH SCHEDULE? The initial epoch length is 28 days. dYdX governance can vote to modify epoch lengths, within the specified bounds. The minimum and maximum epoch lengths are 6 days and 92 days, respectively. WHAT IS THE BLACKOUT WINDOW? For the Liquidity Staking Pool and the Safety Staking Pool, an epoch schedule is enforced for withdrawals in order to provide predictability and a regular cadence for the availability of funds in the pool. A staker must request to unstake funds before the blackout window in order to be able to withdraw the staker's funds after the end of that epoch. If a staker does not request to withdraw, then the staker's staked funds are rolled over into the next epoch. The recommended blackout window for each of the Liquidity Staking Pool and the Safety Pool is 14 days. dYdX governance can vote to modify the blackout window, within the specified bounds. The minimum and maximum blackout windows are 3 days and 46 days, respectively. WHEN CAN I WITHDRAW AND TRANSFER MY EARNED DYDX REWARDS? Earned DYDX tokens via the Retroactive Mining Rewards, Trading Rewards, and Liquidity Provider Rewards are transferable at the end of each epoch. DYDX holders are required to wait approximately 7 days (Waiting Period) after the end of the epoch to claim their tokens. Once tokens have been claimed, they can be transferred or delegated to dYdX governance. Earned DYDX tokens via the Liquidity Staking pool and the Safety Staking pool are claimable every block and can be withdrawn at any time during a given epoch. On September 8th, 2021 at 15:00:00 UTC, 8 days after the end of Epoch 0, the initial transfer restrictions will be automatically lifted, at which point approximately 8.11% of the DYDX supply will become liquid. WHAT IS THE PURPOSE OF THE WAITING PERIOD? HOW ARE REWARDS STORED AT THE END OF EVERY EPOCH? Retroactive Mining Rewards, Trading Rewards, and Liquidity Provider Rewards are stored in a Merkle tree, which contains the cumulative rewards earned by each user since the start of the distribution program. At the end of each epoch, the Merkle root is updated via the ChainLink oracle system on the MerkleDistributorV1 smart contract to reflect rewards earned in the last epoch. An update is performed by setting the proposed Merkle root to the latest value returned by the oracle contract. The proposed Merkle root can be made active after a Waiting Period of 7 days has elapsed. During the waiting period, dYdX governance has the opportunity to freeze the Merkle root, in case the proposed root is incorrect or malicious. If the Merkle root is not frozen, the new Merkle root is activated and users can claim their rewards from the past epoch. Each time the epoch changes, the following occurs in order: * When an epoch ends, rewards data is calculated for all user activity from the last epoch. * This data is added to a data structure on IPFS, stored under a fixed IPNS name. * The ChainLink oracle system, also noticing the change in epoch, queries the latest rewards data using the known IPNS name. * Each oracle signer uses this rewards data to calculate newly earned rewards for each user. * Each oracle signer computes the new cumulative Merkle tree and Merkle root. * Each oracle signer writes the Merkle tree data to IPFS, receiving an IPFS CID. (They should have calculated the same tree and should therefore receive the same CID.) * If the oracle signers agree on the same values, then the RewardsOracle is updated with the new Merkle root, IPFS CID, and epoch number. * An oracle signer (or a third party) calls the public function MerkleDistributorV1.proposeRoot() to set the proposed Merkle root to the new oracle value. * A waiting period takes place, during which governance can call MerkleDistributorV1.pauseRootUpdates() to prevent the proposed Merkle root from taking effect. * After the waiting period, an oracle signer (or a third party) calls the public function MerkleDistributorV1.updateRoot() causing the proposed Merkle root to become active. * Once the new Merkle root is active, users are able to claim rewards from the last epoch. Start Here - Previous Allocations Next - Start Here Fee Discounts Last modified 6mo ago Copy link Contents When will the rewards and staking pools be activated? Can dYdX governance modify the epoch schedule? What is the Blackout Window? When can I withdraw and transfer my earned DYDX Rewards? What is the purpose of the Waiting Period? How are rewards stored at the end of every epoch?