You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Section 2 of the CONSTITUTION, there is a sentence:
The ATONE token Unbonding Period shall be a minimum of 3 weeks, and redelegation shall be allowed twice per ATONE Unbonding Period.
I checked the code, and the redelegation is only possible once per ATONE Unbonding Period (i.e. after a redelegation, you need to wait for one full Unbonding Period before you can redelegate again). Same as any Cosmos SDK chain using the standard x/staking module.
I was wondering if I misunderstood the sentence, or if there should be some code change to allow to redelegate twice per Unbonding Period?
The text was updated successfully, but these errors were encountered:
As per the roadmap, the initial launch of the chain was to be done via a simple fork of the gaia repo with minimal changes (mostly to x/gov and removal of some modules). Any change that would require forking other modules is left to be addressed later.
But yours is a good question and I agree with your assessment of the standard x/staking module. My understanding is also that the number of redelegations allowed is basically one per unbonding period. It would also be an interesting discussion to explore the rationale behind the decision (of allowing redelegations twice per period) and how it would be implemented practically. I also need to wrap my head around it as of now.
In Section 2 of the CONSTITUTION, there is a sentence:
I checked the code, and the redelegation is only possible once per ATONE Unbonding Period (i.e. after a redelegation, you need to wait for one full Unbonding Period before you can redelegate again). Same as any Cosmos SDK chain using the standard x/staking module.
I was wondering if I misunderstood the sentence, or if there should be some code change to allow to redelegate twice per Unbonding Period?
The text was updated successfully, but these errors were encountered: