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
Currently, the web app relies on a client-side environment variable to determine the minimum stake amount. However, we can now leverage w3sper's minStake value directly, ensuring consistency and reducing reliance on hardcoded values in the client.
Proposed Solution
Replace the usage of the client-side environment variable with the minStake value provided by w3sper.
Update any logic, validations, or UI elements that reference the minimum stake amount to use the w3sper value.
Add error handling to manage cases where the minStake value is unavailable or returns an invalid value.
Additional Context
This change will help maintain alignment between the client and backend, improving the overall reliability of the staking process. Any dependencies on the environment variable should be identified and updated.
The text was updated successfully, but these errors were encountered:
Description
Currently, the web app relies on a client-side environment variable to determine the minimum stake amount. However, we can now leverage w3sper's
minStake
value directly, ensuring consistency and reducing reliance on hardcoded values in the client.Proposed Solution
minStake
value provided byw3sper
.w3sper
value.Additional Context
This change will help maintain alignment between the client and backend, improving the overall reliability of the staking process. Any dependencies on the environment variable should be identified and updated.
The text was updated successfully, but these errors were encountered: