Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unbond steaks without losing voting power #1457

Closed
kwunyeung opened this issue Jun 29, 2018 · 7 comments
Closed

Unbond steaks without losing voting power #1457

kwunyeung opened this issue Jun 29, 2018 · 7 comments

Comments

@kwunyeung
Copy link
Contributor

My validator owner account: cosmosaccaddr1k6p5my20u58scap7dgqj4vsy8r86m7u4rlk5sr
Validator address: 217763B77127EBA9C94F76F4BBD7457C059B5B69

I have unbond some steaks form my validator but it keeps the voting power.

My voting power was 914. I first unbonded 100 shares.

Committed at block 608309. Hash: 5AE73721C47D5A9CEA172E7DFD5C8207FDC6DE64

I got 82 steaks back. Then I checked my node status and voting power kept at 914. I then unbond 500 more shares but voting power kept the same.

Committed at block 608369. Hash: C7EA451802FFA5D06940421C659A9135FE497486

Then I delegate 200 steaks back to the validator and it recalculated the voting power and it became 523.

Committed at block 608795. Hash: 7E8BD1E1F9905FCD1187BB376D19A38C6973A73D

I sent 10 steaks to another validator. And then delegate all my steaks back to my validator. I had voting power 904.

I unbonded 903 shares back and then I sent 100 steaks to another account cosmosaccaddr1n8l6aedlvpqw4k30ye2gcjnsycvhjlylgg5ld7.

Now, in my validator owner account, I have 639 steaks while keeping my validator with 904 voting power.

@kwunyeung
Copy link
Contributor Author

Just noticed something. One the explorecosmos.network, it showed my validator with voting power 1.

screen shot 2018-06-30 at 1 11 22 am

My node status shows voting power 904.

screen shot 2018-06-30 at 1 11 51 am

If I gaiacli stake validator cosmosaccaddr1k6p5my20u58scap7dgqj4vsy8r86m7u4rlk5sr, the number of shares is

Shares: Status Bonded, Amount: -2211692202923559333/-2987804101225480192
Delegator Shares: -2211692202923559333/-6465574292796005776

which is around 0.74

They don't align.

@kwunyeung
Copy link
Contributor Author

Also checked /consesus_state with the total stake and all the voting power in a recent block, my voting power is really counted as 904.

@kidinamoto01
Copy link
Contributor

how came 100 shares ==82 steaks ?
it should be > 100 streak, right?
@rigelrozanski

@kwunyeung
Copy link
Contributor Author

kwunyeung commented Jun 30, 2018

I don’t get this either. It’s like deflation. The total steaks I got back was 739 steaks for 903 voting power. I can bond less than 1 steak to get 1 share.

And there are 0.74 shares left which doesn’t make sense as this does imply inflation. If I would got 1 steak back, that means I have to bond more than 1 steak to get 1 share.

They contradict to each other. Or the ratio between voting power and share not always 1:1?

@kwunyeung
Copy link
Contributor Author

kwunyeung commented Jul 1, 2018

Some follow up. I was revoked yesterday. After unrevoking the validator, it has voting power 161. It's like the differences between the unbouded steaks and voting power come back...? I delegated the remaining 639 steaks to it and it has voting power 900.

Again, I unbonded 899 shares and now I have 720 steaks and keeping voting power 900.

@cwgoes
Copy link
Contributor

cwgoes commented Jul 4, 2018

It looks like voting power updates are not being passed back to Tendermint correctly:

http://gaia-6002.coinculture.net:46657/validators?height=608308
http://gaia-6002.coinculture.net:46657/validators?height=608309
http://gaia-6002.coinculture.net:46657/validators?height=608310

914 power all three blocks. Your transaction did indeed cause validator set updates:

http://gaia-6002.coinculture.net:46657/block_results?height=608309

[
  {
    "pub_key": {
      "type": "ed25519",
      "data": "wHTLaQJhAosaYySj1ZRirR26Zw4csrBREgMAlGEXIiI="
    },
    "power": 4
  },
  {
    "pub_key": {
      "type": "ed25519",
      "data": "vdqvmWbb4Asvr8qTUnXFzgAKEwYaAQlP6b7bn4OUTZw="
    }
  }
]

but not the right ones.

@cwgoes
Copy link
Contributor

cwgoes commented Jul 6, 2018

Thanks for the report - this is indeed a bug. Closing in favor of #1567 (see explanation there).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants