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
I am unable to unstake on SimplEOS at all. I get an error message that says ":Error: billed CPU time (365us) is greater than the maximum billable CPU time for the transaction (67 us)"
I have had the EOS staked on SimplEOS for months, with the same problem every time.
Does anyone know if there is an actual way to contact SimplEOS?
There version of SimplEOS I have is 1.0.5
The text was updated successfully, but these errors were encountered:
I opened my SimplEOS wallet in April 2018 thru MyEtherWallet. I do not recall ever staking any EOS and had not looked into my SimplEOS wallet since creating it until December 2021 where I found about 10 EOS available/liquid and 31.625 EOS each staked as CPU and Net. I now have SimplEOS version 1.0.5.
I see my account has 42% RAM (3.37KB / 7.96KB) and 0.2369 EOS; 0% CPU (0 us/28us) and 31.625 EOS; 0% NET (0 Bytes/580.08KB) and 31.625 EOS.
I am unable to unstake the 31.625 EOS for both the CPU and the NET. Usually nothing happens when I try to unstake. But two times I got the following error message: "transaction net usage is too high: 184>0". I wonder if I need to Buy more RAM or Power up my CPU and NET with EOS for a day or so?
I also tried to transfer my liquid EOS to Crypto.com with no success. I also have not been successful in contacting anybody at SimplEOS or in receiving any guidance on how to proceed. Any assistance is greatly appreciated.
I am unable to unstake on SimplEOS at all. I get an error message that says ":Error: billed CPU time (365us) is greater than the maximum billable CPU time for the transaction (67 us)"
I have had the EOS staked on SimplEOS for months, with the same problem every time.
Does anyone know if there is an actual way to contact SimplEOS?
There version of SimplEOS I have is 1.0.5
The text was updated successfully, but these errors were encountered: