BitShares Forum
Main => General Discussion => Topic started by: Bangzi on May 25, 2018, 12:41:33 pm
-
This is what happening now (Credit to Digital (Cipher) Lucifer ):
Proxy works only one level.
Person A gives Person B Proxy.
Person B gives Person C proxy.
Person A Voting Weight only affects Person B, not Person C.
Person B RAW BTS amount/default weight is amount of proxy being given to Person C.
Why this matter because normal users does not know proxy only work for 1 level, even some top proxies:
bitshareseurope (Followers has 54M Voting Weight, Set Bitcrab as Proxy, but when Bitcrab cast a vote, bitshareseurope only contribute 98K Voting Weight (his own account) and his followers 54M Voting Weight equal to Zero)
blockchain-bv (Followers has 11M Voting Weight, Set Xeroc as Proxy)
hellobts (Followers has 6M Voting Weight, Set Seer as Proxy)
Propose Solution: When main proxy such as Xeroc cast a vote or change vote, all his direct and indirect followers at different level should follow as well.
Related Discussion:
https://github.com/bitshares/bsips/issues/79
https://github.com/bitshares/bitshares-core/issues/968
-
Cascading vote tallying over another layer of proxies may cost too many resources during replay.
-
Cascading vote tallying over another layer of proxies may cost too many resources during replay.
I think it won't cost too much more.
-
I had the impression that vote tallying is key part of why maintenance interval is taking so long these days. Adding another "iteration" would only increase time, no?
-
I had the impression that vote tallying is key part of why maintenance interval is taking so long these days. Adding another "iteration" would only increase time, no?
It's true that adding another layer will make it more complicated, and of course will impact calculations in maintenance interval, and likely need more resources to compute, however I don't think it will impact too much, since there are quite some rooms to improve the performance.