BitShares Forum
Main => General Discussion => Topic started by: binggo on July 30, 2020, 03:01:31 pm
-
As the topic...
-
https://bitsharestalk.org/index.php?topic=32546.0
-
Any chance for a volunteer translator please?
The automatic translation sounds quite weird.
-
As the topic...
It seems he retrospectively believes BSIP-22 was a great idea, but with added bs cherry picking and zero BSIP participation.
https://github.com/bitshares/bsips/blob/master/bsip-0022.md
The implementation is a variant of BSIP 22 plus BSIP 24, with ideas discussed in https://github.com/bitshares/bsips/issues/83 .
-
Where have these BSIPs being voted active
The onest fork can't come soon enough, seriously. Absolute amateur hour going on here.
These people are totaly out of control.
Digital Lucifer
Abit
anyone else involved in that shit ?
2 People who decide to change voting system on their own point of view and give a fuck about the rest of voters.
Tomorrow they will make your BTS disappear ?
-
There are first decleration coming from businesses with their own communities to leave bitshares because of the high risk staying here.
Soon CMC 150 and milking reserve pool?
-
There are first decleration coming from businesses with their own communities to leave bitshares because of the high risk staying here.
Soon CMC 150 and milking reserve pool?
Less the number of committees which your support for now and the account who set a proxy need to revote someting to recover full vote power...
-
Main concern is not the voting power but how a single person decides about everything with no consent,no discussion no announcement using trojan horse tactics.
Yesterday it was banning admins who didn't likes his actions
today its adding new vote system based on his personal view
tomorrow its forking out your bts ?
And each time people will say i can't do anything against it ?
-
Main concern is not the voting power but how a single person decides about everything with no consent,no discussion no announcement using trojan horse tactics.
Yesterday it was banning admins who didn't likes his actions
today its adding new vote system based on his personal view
tomorrow its forking out your bts ?
And each time people will say i can't do anything against it ?
Recover the full vote first，then let's wait and see
-
Wtf, changes to vote recalculation even not mentioned in release notes? https://github.com/bitshares/bitshares-core/releases/tag/4.0.0
The relevant commit is 7f4c08b031e1ac1c54967bc3d08f29e40649b88d
-
Translation from the above link:
1. Voting weight decay mechanism (vote decay)
For newly registered accounts, the voting weight is zero, and the votes will only take effect after actively voting.
After each active update of the vote, the voting weight is updated to 100%, and it decreases by 12.5% on the 360th day, and then decreases by 12.5% of the total weight every 45 days, and the voting is completely invalid on the 675th day.
For proxy voting, the voting weights of the proxy and the proxy are superimposed according to the [multiplier relationship].
-
Quote
For newly registered accounts, the user's voting power (VP) is zero. VP only apply after you begin voting.
That's it
If an old account never have any voting operations , its voting power (VP) is zero too，VP only apply after you begin voting.
One committee one vote，if you support many committees，so every your supporting committees will get the total VP you have/the numbers of your supporting committees
Locked bts you will have more VP；
Locked 180 days, you will get 2X VP；
Locked 360 days, you will get 4X VP；
Locked 720 days，you will get 8X VP；
Locekd forever，you will lose these bts，but you will get 8X VP if your account have equal available amount bts，and these VP will decay 2X every 180 days.
There have four levels above, they need to update to next level, the VP will become full as the time，15 days will get full VP;
You can cancle the update in 15 days，but the fund will be vesting in 7 days.
Every account can creat many separate locked positions，these locked positions can be splited but can't be merged.
Every locked positions can change in the process of updating to a Locekd forever positions, if a locked position become a true formal Locekd forever positions already，then can't be changed.
4. If a true formal Locekd forever position appears on the chain, then:
The acccount which didn' have Locekd forever[/b] position will didn't have any VP;
The margin position and orders book will didn't have any VP.
-
Any chance for a volunteer translator please?
The automatic translation sounds quite weird.
see my response here:
https://bitsharestalk.org/index.php?topic=32546.msg343192#msg343192
-
Any chance for a volunteer translator please?
The automatic translation sounds quite weird.
see my response here:
https://bitsharestalk.org/index.php?topic=32546.msg343192#msg343192
4.1 Accounts that do not hold any amount in "permanently locked state" have a voting weight of zero
You just need to lock 1 bts in a "permanently locked state", then you will have a "permanently locked state" :)