The New iOS Trading Experience Is Now Live!
Learn More
Guides
Bridge
How to bridge guide
Stake
How to stake guide
Vote
How to vote guide
Validator
How to validate guide
Ecosystem
Blog
Read the latest updates
dYdX Ecosystem
Explore the ecosystem
Integrate
Join the dYdX Ecosystem
Trading
API Integration
Clients information
Documentation
Technical information
GitHub
View dYdX github
Media
Press
Latest press features
Podcasts
Latest podcast features
Brand
Our brand assets
Press Enquiry
Get in touch
Explore
dYdX Foundation
About us
Careers
We are actively hiring
Institutions
Integrate
Join the dYdX Ecosystem
Ecosystem Enquiry
Get in touch
Trade App
v4
Trade App
v4

Menu

Overview
All Users
Keplr User
Step 1 - New Keplr User
Step 2 - Import Wallet
Step 3 - Export Phrase
Step 4 - Setup Keplr
Step 5 - Stake DYDX
Leap User
Step 1 - New Leap User
Step 2 - Import Wallet
Step 3 - Export Phrase
Step 4 - Setup Leap
Step 5 - Stake DYDX
How to ClaimHow to UnstakeHow to Redelegate

How to Redelegate?

Overview

Re-delegation in the Cosmos SDK is a feature that allows a delegator to shift 100% or a portion of their staked tokens (delegations) from one Validator to another without having to wait for the un-bonding period. 

During the re-delegation process, the tokens remain staked, meaning they continue to contribute to the network's security and potentially earn rewards for the delegator.

However, a user’s slashing risk with the original Validator remains until the unbonding period concludes. For example, a user stakes 20 DYDX to Validator A for 59 days, on day 60 the user decides to redelegate their 20 DYDX to Validator B. From days 60-90, the user is at a risk of having a portion of their 20 staked DYDX slashed based on the conduct of Validator A. After the 90th day, the slashing risk transitions to Validator B.

After re-delegating, any DYDX that was re-delegated must wait 30 days before it can be re-delegated.

Step 1 - Re-delegate to another Validator

1(a) The Keplr dashboard displays the Validators that you have staked to and the amount of tokens staked to each respective validator. Click on the arrow next to the Validator you’ve staked to previously.
1(b) click “Redelegate”.
1(c) select the Validator that you would like to redelegate your DYDX tokens to and click “Next”.
1(d) enter the number of DYDX tokens that you want to redelegate, click ‘Redelegate’, and pay the gas fee on dYdX Chain.
1(e) Once the transaction to redelegate is complete, you will see your available balance updated on the dashboard.

Step 2 - New balance and option to stake 

Once you have claimed your rewards, you will see your available balance update on the Keplr Dashboard and you can re-stake these claimed DYDX tokens to increase your stake with the same Validator or select another Validator to stake to.

Last updated on November 26, 2023

Get Involved with the Community

Become a part of our journey to reshape the financial landscape

X
Forum
Discord
YouTube
Hedgies nft images
About
Foundation
Careers
Brand
Terms of Use
Privacy Policy
Bug Bounty Program
Video Disclaimer
Guides
Bridge
Stake
Vote
Validators
dYdX Chain Onboarding
Ecosystem
Blog
dYdX Ecosystem
Integrate
Trading
Documentation
GitHub
Public Bridge UIs
dYdX DAO
dYdX Grants Program
dYdX Operations subDAO
Socials

Leaving site

Leaving site. By clicking ‘Continue’, you will be leaving the dYdX Foundation (“dYdX Foundation”) website and accessing a website made available by a third party using dYdX v4 open-source software that is independent from and unaffiliated with the dYdX Foundation. The dYdX Foundation does not deploy or run dYdX v4 software for public use, nor does it operate or control any such infrastructure. The dYdX Foundation is not responsible for any action taken by independent third parties or for content on any third-party websites, including the one you would access by clicking ‘Continue’.

‍

The dYdX Foundation services and products are not available to persons who are residents of, are located or incorporated in, or have a registered office in the U.S., Canada or a Restricted Territory.  More details can be found in our Terms of Use. Learn more about dYdX v4 third-party front end options here.

Continue