Discrepancy between actual Stake on Drep and what GovTool thinks

[m-i-k-e]

There are some pretty strange issues with voting power and stake keys.

I have a wallet in Lace with which I've staked to 4 stakepools. There is a lot of inconsistency in how voting power is shown, and it does not make a lot of sense. Is Lace able to change the stake distribution? It looks like it.

In any case, there needs to be some looking into multi-stake wallets and their implications on voting power.

Please have a look at the video

I'm setting this at P0 @bosko-m, as this has really challenged me to understand what my Voting Power is, and it's definitely a bug somewhere.

https://www.loom.com/share/34813c98186e436a8c509f166e6f248c?sid=27a5c649-69e0-43f0-b2b7-515bec3b4944

[m-i-k-e]

Internal (Intersect) comment on Slack:

It appears to me the only potential technical bug is GovTool not showing the accurate stake associated with each key after some event that causes stake distribution drift. This can happen, after establishing your delegation intent (25% per pool), if you interact with a DApp that constructs a transaction, receive funds, or maybe use another wallet with the same seed phrase. The balance is corrected over time when either sending a transaction, using the Lace send form, or using the Rebalance portfolio feature that you had open in your presentation.

We’re currently reviewing the multi-delegation feature in context of these issues, since the friction and confusion is only compounded with voting power concerns in the mix.

[m-i-k-e]

So would this work: Displaying both Voting power at the present time (like ADAstat), and at the last epoch.