fix: unstake limits for ERC4626 #491
Merged
+14
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a patch to the
@stakekit/widgetpackage that fixes unstake limits for ERC4626-compliant yield opportunities. The main changes improve how unstake limits are calculated and allow users to change unstake amounts for ERC4626 positions, even when the amount is not explicitly required.ERC4626 Unstake Limit Fixes:
isERC4626utility toyields.tsto detect ERC4626-compliant yield opportunities.stake.tsso that the minimum unstake amount calculation uses higher decimal precision and correctly applies integration minimums for non-Bittensor staking.position-details/state/index.tsx, users can now change unstake amounts for ERC4626 positions, even if the amount is not marked as required.General Maintenance:
isBittensorStakinginstake.ts..changeset/calm-owls-accept.md.