Resolves issue where some users are not able to claim their vested SEAM. This fix will need to use the Governor Long process since it is updating a core governance contract. The Tally page for this governor can be found here
A bug was discovered in the esSEAM contract which can prevent a user from claiming their vested SEAM from the esSEAM contract. The pull request for the fix can be found here.
If this is a bug, I’m for resolving this issue to ensure that users are able to claim their vested SEAM for claiming. Thank you for finding a fix. In Favor
Fully support this fix. Great job to the ones who discovered this bug, especially since it seems like it was non-critical and only affecting a very small amount of users. Either way, I believe it is important to fix, so support the upgrade to fix it. Nice find.
Fully support
This proposal is now live onchain. Voting will begin in 2 days. Please note this is the first “constitutional” gov proposal since the launch of Seamless onchain governance. This utilizes a different onchain governor contract which has more onerous requirements to pass. There is also a separate Tally page (since Tally maps governance pages to governance contracts 1:1 by default).
Tally page for proposal: Tally | Seamless Protocol Governor Long | [SIP-28] Bugfix esSEAM claim
Long Governor (constitutional) requirements tldr:
Full specs in Github here