Skip to content

Panic when maxAmount exceeded in IncrementFiStakingConnectors#155

Merged
Kay-Zee merged 1 commit intokan/fix-lint-issuesfrom
jrbbink/increment-fi-max
Mar 21, 2026
Merged

Panic when maxAmount exceeded in IncrementFiStakingConnectors#155
Kay-Zee merged 1 commit intokan/fix-lint-issuesfrom
jrbbink/increment-fi-max

Conversation

@jribbink
Copy link
Contributor

Fixes issue uncovered by flow cadence lint where the maxAmount passed to IncrementFiStakingConnectors.Sink was less than the amount returned by the staking pool (see #154).

Adding an assertion ensures that the maxAmount value is respected and that the caller will not receive more tokens than they are able to handle

@jribbink jribbink changed the base branch from main to kan/fix-lint-issues March 20, 2026 23:50
@jribbink jribbink requested a review from Kay-Zee March 20, 2026 23:51
@jribbink jribbink assigned nvdtf and unassigned nvdtf Mar 20, 2026
@jribbink jribbink requested a review from nvdtf March 20, 2026 23:53
@Kay-Zee Kay-Zee merged commit 206b32d into kan/fix-lint-issues Mar 21, 2026
3 checks passed
@Kay-Zee Kay-Zee deleted the jrbbink/increment-fi-max branch March 21, 2026 02:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants