Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - blockchained

Pages: 1 2 3 [4] 5 6 7 8 9 10 11 ... 17
46
this is the post THAT WAS DELETED by DL, DL abused his admin rights in my eyes



BitShares Forum »
    Other »
    Graveyard »
    Deleted »
    Voting System


Author Topic: Voting System  (Read 26 times)

Online Thul3

    Hero Member
    *****
    Posts: 564
        View Profile Personal Message (Online)

Voting System
« on: August 20, 2020, 07:21:04 pm »

    Quote

I would like to provide some information regards the upgraded voting system.
Majority of people like some parts of the voting system and think there are currently two groups.
One group called the CN-Vote Group and the other Group called Abit's group.

It is being fudded to many people that CN-Vote Group is against a new voting system and only Abit's group will provide a new voting system.

The truth is majority of us also likes some part of the new voting system.DPOS1 for example has been promoted by myself on telegram chats for a longer period which everyone can check themself.


Our main disagreement is

1.Adding a malcious code (from core member who should audit it) destroying bitshares reputation and its blockchain being vulnerable to a single person.
2.Adding a stacking feature which will mainly benefit a special group and centralize power arround big holders.An example Abit will get soon 70 million vote power making sure he will keep part of his influence on bitshares (as one of the most corrupt member.Here just from today again on telegram chat "How about we remove their admin privileges and kick them out?" , Then they'll never tag you here @favdesu")
3.Corrupt people with low ethics will stay at major key positions which makes corruption possible.Corruption for example was in the past not so much possible because it was limited by committee members with high ethics who followed protocol/rules .
4.Increase of influence of Digital Lucifer and BEOS .Both love to centralize bitshares which majority of foreign  community disagrees.
This part of community is being muted or banned.Businesses are afraid of these people and would fork out instantly (see palmpay) for example.It would also mean that majority of foreign community would leave.

They are well aware about it that they have no support in centralization of bitshares thats why they need to change the voting power in our opinion to implement their agenda since they can't get nearly any support at current situation.


Our main goal is to not let the 4 mentioned points happen and get new features for the voting system voted in via normal BSIP workers
like DPOS1 for committee and witness,Vote Decay and Collateral in some form .It should be done the right way.

There is enough support to get it passed via BSIP workers without giving the corrupt people of bitshares more influence over bitshares and key control positions they currently have (lost a lot)

This fight is not about getting a new voting system added or not as cn-vote group is also for voting system changes.

This fight is about getting  the new voting system added without corruption,malcious code and destruction of bitshares reputation and to have strong limits for bad actors who blocked bitshares progress for a very long time causing enough damage.

Please remember which members were the most corrupted ones, hurting bitshares the most with their ignorant stance that only their point of view matters no important if majority supports it or not
« Last Edit: August 20, 2020, 08:02:33 pm by Thul3 »

47

What will happen to the Witnesses with CN-Vote patch "on August 20"?

If you are planning a new patch with the September 10th update, it makes sense to vote for the nodes that did not install the patch, in order to avoid network problems on August 20th.

Or let the Witnesses update the versions to official github and inform the community about it.

THIS ^^^

dude, it's obvious any capable witness can do this without advice from talking head
Just put back the code, and run new version 10th of September 

48
let the time show which is right, time is the key.
Agree on that
But time will not change abit habits, dev with low ethics will always try "easy way", saw this situation multiple times in different public project, but always with the same result.

49
Quote
They used a consensus mechanism, it probably must be reviewed but not by the dictate of one dev with low ethics. It was implemented without any discussion, any voting or any feedback from the businesses on top of bitshares, if abit don't like bitshares consensus he can fuck off and make abitshares.

“a consensus mechanism”? ok,i have nothing to say, this is the bitshares consensus, i see now, so i don't think what abit did is wrong, that's also a "consensus mechanism", is it not?

not he is not, he abused his core position and his admin position on github, he fucked community trust, and community must kick out him from github, or just start a new github with committee control over it, not one member of the community. We have experience with changing corrupted github for the blockchain, exchange always follows community and top witness consensus, it's not a problem to change github page.



Quote
Yes, he is the one, but without some big proxies supportting(you should know who were them), he can't make it, and if the group of wittness didn't follow it, he can't make it, but all they did, you see, from that moment, all what we have only is a fake consensus, and no one want to change this fake consensus until now, so you want to fight with this fake consensus, tell me, how do you want to do?how do you want to fight with a big vote power of leveraged collateral?

No one think he is a knight, he has his fault, and he only cut a cancer from the bts, now you want to return back the cancer to bts for the fake consensus, ok, very fair, let it back,very fair.

I don't want to see the fraudster dev with law ethic in a core, easy as that
I don't want our community and gateway were attacked by the fraudster in the future when he'll decide that  I talk too much.
All the rest it is your personal opinion, about. Nothing more. 

50
The timeline listed in OP is about correct. However, IMHO, the narrative is too subjective and misleading.

I do hope that we come to a proper solution. However, it should be based on responsible actions.

You must be banned from the community work witness/committee/worker forever, fully agree with cnvote statement


Ok, let's ban him from the community work witness/committee/worker forever.

If we also need to ban the people and union from the vote system forever who used the fake vote with leverage collateral,vote buying,vote exchange,to show we are fair?!

They used a consensus mechanism, it probably must be reviewed but not by the dictate of one dev with low ethics. It was implemented without any discussion, any voting or any feedback from the businesses on top of bitshares, if abit don't like bitshares consensus he can fuck off and make abitshares.

Quote
If not,why ban him from the community work witness/committee/worker forever? or you think the fake vote, vote buying,vote exchange is following our baseline or we have different level baseline?

He was part of all these fake feeds and so on, I personally asked him in public chat "is it ok to fake feeds and do inside deals" he answered something like "it is ok till he has his benefits" So please don't put abit as a knight in a white dress he was part of corruption and milking reserve pool for years.

By this one trojan, he just shows what a shit he really is, don't blame witnesses because sometimes you could let shit happen to show what a snake a community core team occupied the place

51
The timeline listed in OP is about correct. However, IMHO, the narrative is too subjective and misleading.

I do hope that we come to a proper solution. However, it should be based on responsible actions.

You must be banned from the community work witness/committee/worker forever, fully agree with cnvote statement

52
In fact in most condition whether rule A or rule B is not a big deal to me.
What I really concern is the business based on core which make BTS more valuable like gdex\rudex\CNC\magicwallet...
I expected a stable core since years ago, but seems it's still not coming today.

What abit had done is totally not acceptable in my opinion.
But it's already happen. I can accept the changes even some details is not reasonable to me.
The important thing is how to ensure our developer don't do it again.

I don't support fork, it's a disaster to all business based on BTS, what will happen to bitCNY/GDEX.BTC/CNC.. ?
Anybody  will have faith to build business on BTS in the future?
I wish you can resolve disputes, somebody can give a concession,  price will rise, BTS can have a good future.
Please use your votes to stop this chaos in community, the future of BTS is really in your hands.

1\Vote back those witness that didn't update cnvote patch to avoid fork.

2\ Discuss about the new rules among the whole community, and vote for the new rules one by one

3\ Update a new version after the whole community reach consensus(careful code check to avoid abit things again).

it will be no fork because if abit  have money to sustain a fork, he didn't put trojan in the first place, we will see the same faces fighting around the reserve pool after 20th

53
Quote
If you expect something to happen, you'd better work towards it.

Act like a man.

It does not act like a man abit, it's act like a criminal that put trojan in the release, the devs like you must be forever banned from the reserve pool or any work for the community

54
Quote
trojan is trojan
the code is public, everyone can check it, and why nobody check it?

abit was paid to audit it, if you don't see the problem that he put inappropriate code that fully changes consensus, I can't help you. For me personally abit and a core manager are criminals and must be blacklisted from the core forever.
I'm tired that the same group over and over again opens different pandora boxes.

Quote
the cn-vote patch chain will be controlled totally by the CN-VOTE and the debtor. The vote system, the wittness system and the committees will be filled with vote buying and vote each other.

it will happen in both ways if it  abit/beos control or cn vote control, just one way without trojan and another one with it.
Rule number one never trust a dev that put trojan in the release
I don't know how a community will split, I don't believe in this to be honest, I think we will see the same faces fighting for the power even cnvote wins, but I lost the last credibility that I have to abit, he just a fraudster in my eyes. And I will not support anything from him, one trojan already enough

55
he has put trojan in the code, he was paid to audit this code, and he abandoned his duties, easy as that

now you're asking is it ok that abit raped the community trust? it is not ok

why he is not kicked out, and we're discussing this fraud at all

things are not so simple as you think.

before BTS4.0, actually cn-vote was able to control the committee if they like.

so is it possible to implement a DPOS1 to eliminate this kind of risk through the BSIP draft -> voting ->core development process? I don't think so, one reference is BSIP22, although now almost everyone says he agree vote decay, BSIP22 has not yet been approved after about 2 years.

I don't think what abit did is acceptable, but he was definitely not doing evil.

and I don't think to just remove the unplanned features is  a good enough solution to this problem.

maybe a better solution is to plan another protocol improvement with a new version.

1.include the vote decay and DPOS1 features(maybe DPOS1 can also be applied to witness voting)
2.remove, disable or update the Staking Voting Power and the Additional Voting Rules, dependent on some more deep discussion.

things will be done following the BSIP draft->voting and approvment->development and release->code audit and test->protocol improvement process.

trojan is trojan
you knew that these changes will not pass through the community not only cnvote against these changes and core put trojan in the code, and abit was paid quite good from reserve pool for audit. Trojan in release all I need to know, I don't give 1 fuck about intentions or excuses.

56
blckchnd will run a witness with patch installed

57
he has put trojan in the code, he was paid to audit this code, and he abandoned his duties, easy as that

now you're asking is it ok that abit raped the community trust? it is not ok

why he is not kicked out, and we're discussing this fraud at all

58
Stakeholder Proposals / Re: [Witness Proposal] blckchnd
« on: August 05, 2020, 02:40:37 pm »
Hello everyone!
 
Today we are finally ready to present you our latest localization of open source development based on the Bitshares blockchain – it is the RuDEX mobile app for Android!
It’s already available for download in the Google Play Store right now.

This is an improved version of widely known in the Bitshares community bitshares-mobile-app, developed by an independent team with community funding. We created a special RuDEX gateway localization for it and thoroughly adapted it for the maximum ease of use of this product.

Current version of RuDEX mobile app includes the following functions:

- Registering new accounts, logging in with existing ones and back up support
- Account mode and wallet mode support
- Multi-account support
- Viewing all assets and trading in Bitshares markets
- Encrypted stealth transactions (blind transfers)
- Markets, chart, K-line chart, trading history
- Margin trading
- Account search, feed price information, margin position rating
- Sending and receiving tokens
- Issuing and managing of your assets based on Bitshares
- Token deposit/withdrawal
- Voting and government of Bitshares DAC
- FAQ


We also couldn’t miss the opportunity to remind you of some benefits of RuDEX in comparison with centralized exchanges:

- Ability to trade fully decentralized assets
- Multi-language interface and support
- Desktop applications for all major OS
- Full exclusive control over your own account and funds
- The impossibility of blocking the trading platform and the Bitshares blockchain
- Correspondence of the amount of asset tokens to their actual amount in the gateway wallet
- Transparency for audit


Join trading on RuDEX – the mobile application makes it even easier!

In addition, our team is currently preparing a number of interesting updates to existing services that will not disappoint you. Subscribe to our blog to don’t miss updates and other news.

Have a good trade!


RuDEX Mobile v6.2 update

What's new?   
1. Added the function of staking voting.   
2. Add the entry of STAKE in my asset interface.   
3. Fix some bugs.


59
Stakeholder Proposals / Re: [Witness Proposal] blckchnd
« on: July 30, 2020, 07:25:27 pm »
Will have new chain? Sounds great! :)

 I heard that some teams experiment with such idea. I guess Ken meant this

60
please correct your statement from community to a group because i haven't seen a single line of discussion of that topic in telegram.
I think BTS didn't have the community anymore, the holders of BTS had made this choice for themself, they chose to destroy themself and the chain, time will show the fact.

I mean community, not telegram.

In my view, if Bitshares is a DAC, then Committee is just like the Board, no Board need to get approvement from Shareholders in everything.

Every shareholder is authorized to unvote any Committee member.

the BOARD? really? you are not the board dude, come down from heaven to earth
You and only you responsible for this fall from top-100, you and only you be blamed for all you have done to this community to save your position.

 Is market didn't show to everyone that you were wrong with pricefeed manipulation bsips? When manipulation started we were rank top-25
now we already out of top-100, clear sing only blind couldn't see it
 

Pages: 1 2 3 [4] 5 6 7 8 9 10 11 ... 17