Explain the unbonding period before users undelegate
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 26
- Avg merge
- 11h 58m
- Merged PRs (30d)
- 16
Description
### Is your feature request related to a problem?
_Part of the Delegator UX Analysis RFP._
Today, the unbonding period isn't shown until after the user has already undelegated. A 7-day token lock without prior explanation looks like a bug, not a feature, and damages trust at exactly the moment trust is most fragile.
### Describe the solution you'd like
Move the unbonding period disclosure to before the user acts. Inline copy at the undelegation step should explain how long the period lasts, why it exists, and what the user can and can't do during it.
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the undelegation flow and the existing disclosure that appears after the user acts. Trace where the undelegation step is rendered, then add the requested inline explanation before the action. Done means users can see the 7-day duration, why the period exists, and what they can and cannot do during it before undelegating.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100