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
Wondering if the issue was on my end, I restarted my roles, eibc, and relayer services, cleared the site cookies, and tried a different browser. Despite my rollup being active, this error persists.
Expected result
It is necessary for me to view the number of tokens I have staked in the single vote section.
Actual result
When I first click on the sponsor, I can see the tokens I have staked, but after one or two seconds, they appear as zero, and the error message 'Your available staked amount is less than the minimum sponsorship weight for one sponsorship (1.00%)' is displayed on the screen, even though I have staked more than 50 tokens.
Log Files
No response
Notes
When I try to sponsor someone, I get this error even though there are tokens in the stake.
The text was updated successfully, but these errors were encountered:
Roller version
1.6.4-alpha-rc08
Rollpp type (EVM/WASM) and version
EVM
OS
ubuntu 22.04
Processor Architecture
AMD EPYC
Others
No response
Steps to reproduce it
Wondering if the issue was on my end, I restarted my roles, eibc, and relayer services, cleared the site cookies, and tried a different browser. Despite my rollup being active, this error persists.
Expected result
It is necessary for me to view the number of tokens I have staked in the single vote section.
Actual result
When I first click on the sponsor, I can see the tokens I have staked, but after one or two seconds, they appear as zero, and the error message 'Your available staked amount is less than the minimum sponsorship weight for one sponsorship (1.00%)' is displayed on the screen, even though I have staked more than 50 tokens.
Log Files
No response
Notes
When I try to sponsor someone, I get this error even though there are tokens in the stake.
The text was updated successfully, but these errors were encountered: