RE: Assertion Failure - not able to stake more tokens or vote #64
Comments
|
Hey! I'm really sorry for the late reply. https://github.com/eosrio/simpleos/releases/tag/v0.7.1 Best regards from EOS Rio team =) |
|
Thank you for your response, the issue is solved quite a while ago
Thank you for your support
Howard
…On Tue, Jan 15, 2019 at 7:50 AM VinceCuri ***@***.***> wrote:
Hey! I'm really sorry for the late reply.
I do believe that by now, your issue might be solved. However, I'll paste
here for you the link to our new SimplEOS release (0.7.1) which might offer
you a better user experience and new features to interact.
https://github.com/eosrio/simpleos/releases/tag/v0.7.1
Best regards from EOS Rio team =)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#64 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Am4unUDVGL9vhUeA0Tadj9FelkiiGTi6ks5vDc6VgaJpZM4Wfuof>
.
|
|
I tried to un-stake some EOS using simplEOS, I get a error message
"Account has insufficient ram; needs 9685 bytes has 9447 bytes".
1) In resource I can see 8.87 KB is used out of total of 9.23 KB,
because I voted for some referendum proposals, do I need to wait for
referendum proposals to be expire then I can use the RAM to un-stake?
2) I only have 0.0001 liquid EOS rest are staked, can I use staked EOS
to buy RAM?
Thank you
Howard
|
|
Hey!
You're welcome =) |
|
I heard the RAM you use to vote for referendum when the referendum is over
you get your RAM back, is that true?
Thank you
Howard
…On Mon, Apr 1, 2019 at 3:41 PM VinceCuri ***@***.***> wrote:
Hey!
1.
Usage of RAM does not recover. Once you've spent it - voting or doing
any other action -, you'll need to buy more. You can use SimplEOS to
buy/sell RAM on "Resources" section.
2.
No. You need to unstake your EOS to buy RAM.
You're welcome =)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#64 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Am4unVxN4sFqsKULUZPycGjM1MM2_NvCks5vcn0HgaJpZM4Wfuof>
.
|
|
Part of it is true. You do spend RAM when voting for a referendum, but it does not recover after its expiration. The only way to recover it is by performing an "unvote" action, which is available on its contract, or if the owner of the contract perform a "clnproposal" action. Otherwise, RAM will stay allocated to the referendum contract. |
|
I voted for several proposals because I thought I can help the community
and didn't know it costs RAM to vote. I can't remember which proposal I
voted for. How do I find out which proposals I voted for without unvote
every proposal that are available to vote/unvote?
Thank you
Howard
…On Wed, Apr 3, 2019 at 11:30 AM VinceCuri ***@***.***> wrote:
Part of it is true.
You do spend RAM when voting for a referendum, but it does not recover
after its expiration.
The only way to recover it is by performing an "unvote" action, which is
available on its contract, or if the owner of the contract perform a
"clnproposal" action. Otherwise, RAM will stay allocated to the referendum
contract.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#64 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Am4unRqnf6gA5Yvdf83K-819tJNuaMx4ks5vdMkKgaJpZM4Wfuof>
.
|
|
If there are no transactions in my EOS account for 3 years not including
Voting, but has other transactions such as staking, un-staking, airdrop,
transfers, etc. Will my EOS be taken away?
Thank you
Howard
…On Wed, Apr 3, 2019 at 1:56 PM Howard Jiang ***@***.***> wrote:
I voted for several proposals because I thought I can help the community
and didn't know it costs RAM to vote. I can't remember which proposal I
voted for. How do I find out which proposals I voted for without unvote
every proposal that are available to vote/unvote?
Thank you
Howard
On Wed, Apr 3, 2019 at 11:30 AM VinceCuri ***@***.***>
wrote:
> Part of it is true.
>
> You do spend RAM when voting for a referendum, but it does not recover
> after its expiration.
>
> The only way to recover it is by performing an "unvote" action, which is
> available on its contract, or if the owner of the contract perform a
> "clnproposal" action. Otherwise, RAM will stay allocated to the referendum
> contract.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#64 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/Am4unRqnf6gA5Yvdf83K-819tJNuaMx4ks5vdMkKgaJpZM4Wfuof>
> .
>
|
|
To find out which proposals you've voted for, you just need to type your account name on any block explorer and check your history. I'd encourage you to use bloks.io, go for the "Transactions" field and click on the button "Vote". The list which appears right below the options will be filtered out to voting actions (bp's voting and proposals). I couldn't understand your second question properly, I think. Your EOS will still be yours as long as you have your private keys with you, no matter how long it takes or how many actions you are performing on the mainnet. You're welcome. |
|
I heard if my EOS account doesn't vote for 3 years, my EOS will be taken
away, is that correct?
I also heard if there is no action performed on my EOS account for 3 years,
my EOS will be taken away, is that correct?
Thank you
Have a great weekend
Howard
…On Thu, Apr 4, 2019 at 12:38 PM VinceCuri ***@***.***> wrote:
To find out which proposals you've voted for, you just need to type your
account name on any block explorer and check your history.
I'd encourage you to use bloks.io, go for the "Transactions" field and
click on the button "Vote".
The list which appears right below the options will be filtered out to
voting actions (bp's voting and proposals).
I couldn't understand your second question properly, I think. Your EOS
will still be yours as long as you have your private keys with you, no
matter how long it takes or how many actions you are performing on the
mainnet.
You're welcome.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#64 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Am4unROCYk3vaTuSg0dz-jhq4y20OoFWks5vdip-gaJpZM4Wfuof>
.
|
|
Don't you worry about it. It's just a quote on the interim constitution that even the block producers don't agree so much with that. It would require an enormous effort for something unlogic. There's a big discussion about it so much that there's a proposal to replace the constitution for the EUA (EOS User Agreement), which does not include this 3-year rule. I'll leave here the link for you to understand more about the referendum: https://eosauthority.com/polls_details?proposal=eosuseragree_20190207&lnc=en |
|
I hope EUA will replace the interim constitution so that if I don't vote
for 3 years my EOS won't be taken away. Take away EOS from people because
they didn't vote doesn't seem logical to me and many other people I am
sure. I will check that website often for more updates
You've being a great help
Thank you
Have a great weekend
Howard
…On Thu, Apr 4, 2019 at 2:27 PM VinceCuri ***@***.***> wrote:
Don't you worry about it.
It's just a quote on the interim constitution that even the block
producers don't agree so much with that. It would require an enormous
effort for something unlogic.
There's a big discussion about it so much that there's a proposal to
replace the constitution for the EUA (EOS User Agreement), which does not
include this 3-year rule.
I'll leave here the link for you to understand more about the referendum:
https://eosauthority.com/polls_details?proposal=eosuseragree_20190207&lnc=en
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#64 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Am4unZSpqC8OQbiL-vsWEKZGAT0ifejBks5vdkQCgaJpZM4Wfuof>
.
|
|
Two more questions
1) I un-voted all the proposals I voted for previously but only got back a
small amount of RAM, do you have any idea why it could be this way? Maybe
because of the amount of time passed since I voted in the first place?
Just my guess
2) When trying to claim airdrops if it doesn't say it will cost any RAM, no
RAM should be taken away from my EOS account, right? For example claiming
Trybe token on trybe.one it doesn't say it will cost any RAM to claim the
airdrop
Thank you
Howard
…On Thu, Apr 4, 2019 at 2:39 PM Howard Jiang ***@***.***> wrote:
I hope EUA will replace the interim constitution so that if I don't vote
for 3 years my EOS won't be taken away. Take away EOS from people because
they didn't vote doesn't seem logical to me and many other people I am
sure. I will check that website often for more updates
You've being a great help
Thank you
Have a great weekend
Howard
On Thu, Apr 4, 2019 at 2:27 PM VinceCuri ***@***.***> wrote:
> Don't you worry about it.
>
> It's just a quote on the interim constitution that even the block
> producers don't agree so much with that. It would require an enormous
> effort for something unlogic.
>
> There's a big discussion about it so much that there's a proposal to
> replace the constitution for the EUA (EOS User Agreement), which does not
> include this 3-year rule.
>
> I'll leave here the link for you to understand more about the referendum:
> https://eosauthority.com/polls_details?proposal=eosuseragree_20190207&lnc=en
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#64 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/Am4unZSpqC8OQbiL-vsWEKZGAT0ifejBks5vdkQCgaJpZM4Wfuof>
> .
>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I already staked some of my EOS tokens but I am not able to stake any more of tokens and the error message reads: Eosio_assert_message Assertion Failure
The same message appears when I try to vote without staking more tokens I have the latest version of simplEOS 0.6.4 What is happening?
The text was updated successfully, but these errors were encountered: