For transparency:

After looking at the relevant poll (and its unfortunate lack of participation despite the extremely important subject) and the voting advantage of the yes supporters, I decided I will run the new BitShares Core 5.0.0 release.

Stakeholders that do not agree can manage their vote accordingly.

Quote from: Thul3 on August 17, 2020, 08:12:23 PM
You installed knowingly malcious code and were silent about it.You did it with full intention.You broke once again rules and protocol as witness.

I have no idea what you smoked, but I urge you to stop because it seems to hurt you and makes you think you are omniscient.

Quote from: Thul3 on August 17, 2020, 08:12:23 PM
You did wrong and want to force as a small minority the majority to accept your point of view by creating fud and fear.

You are the one creating fud and spreading bullshit here. Stop claiming or even speculating about me being aware of the latest addition to the 4.0 release. I was not aware of any changes in voting rules, so stop bullshitting around.

Quote from: Thul3 on August 17, 2020, 08:12:23 PM
Wasn't it you personly on telegram chat who asked cn-vote for supporting you as witness with the explanation you will always follow consensus based on voting ?

cn-vote is the same group that kicked me out exactly because I was following the consensus.

If there is really consensus then active witnesses will be changed to reflect community will. I encourage that.
If a fork is going to happen that's exactly because there is a split in consensus (so no real homogeneous consensus).

Quote from: Thul3 on August 17, 2020, 08:12:23 PM
And if you don't understand the patch i recommend reading the forum.There is an explanation from me and cn-vote that reversal of code needs more work so the easiest way was to change parameters only to not change compatibility.

"Not change compatibility" ?
...Applying that patch will create a fork... what other "compatibility" are you trying to preserve? It doesn't make sense.

As a witness I also have to evaluate the risk in running a certain version of the software, and as already stressed, that patch was not tested, it introduce new unspecified behaviour and above all it doesn't reverse the controversial changes that required the patch itself...it will also cause dangerous situations for the current BitShares ecosystem.

I invite you, cn-vote, and everyone that feels a come back is needed, to take the necessary time and make it right instead of rushing it so badly.

I am not sure to understand the point of this patch...

I would understand it if it was a total reversal of the latest voting rules/changes, but from what I saw and from other analyses, it is not. Most of the "concerning" changes are still there, so I don't really see the point in setting up a second node to support that fork.

There is still time to set it up, so if anyone would like to enlighten me, I could change my mind.

As for now, my main witness node and API server will not run the patch.

Since I think a fee schedule overhaul, among other things, is badly needed, I am willing to give a chance and try out proposal 1.10.57236 that I just approved.

I just wanted to mention that all past proposals that have my vote have been verified before approving, even if I did not post here on the forum.

Verified and approved today's one as well.

Verified and approved

Verified and approved

latest proposals verified and approved


$ ruby mm_rewards.rb 2019-12-19 1.10.54384

Date: 2019-12-19

Computing snapshots chucksum...
  f9ac41094820ef5abb7c517713c14c54e027e61a4c2944fe5e6558e06d8a3409

Analyzing snapshots data and computing rewards...
  Total Rewards: 34886.74713 BTS

Let's verify the current proposal
  Getting proposal '1.10.54384' from the blockchain...
  Loading computed rewards data and mimic a proposal...
  Comparing proposals...
    No difference found!



$ ruby mm_rewards.rb 2019-12-18 1.10.54333

Date: 2019-12-18

Computing snapshots chucksum...
  d5cedd9bf884d45ad8c9f6c0ed5395958d05ab5c22904c867f3273d36563c6a7

Analyzing snapshots data and computing rewards...
  Total Rewards: 35462.89133 BTS

Let's verify the current proposal
  Getting proposal '1.10.54333' from the blockchain...
  Loading computed rewards data and mimic a proposal...
  Comparing proposals...
    No difference found!



$ ruby mm_rewards.rb 2019-12-17 1.10.54267

Date: 2019-12-17

Computing snapshots chucksum...
  3705d88968be1e93728856f68d5a8d78599ecd2bad62b58085ee620263337aa4

Analyzing snapshots data and computing rewards...
  Total Rewards: 33919.66987 BTS

Let's verify the current proposal
  Getting proposal '1.10.54267' from the blockchain...
  Loading computed rewards data and mimic a proposal...
  Comparing proposals...
    No difference found!



$ ruby mm_rewards.rb 2019-12-16 1.10.54230

Date: 2019-12-16

Computing snapshots chucksum...
  1a00d42a4a8e6c40e735391dda66ec0bc4ffd65f095da22f2b5700905a786a97

Analyzing snapshots data and computing rewards...
  Total Rewards: 44515.49773 BTS

Let's verify the current proposal
  Getting proposal '1.10.54230' from the blockchain...
  Loading computed rewards data and mimic a proposal...
  Comparing proposals...
    No difference found!



$ ruby mm_rewards.rb 2019-12-15 1.10.54158

Date: 2019-12-15

Computing snapshots chucksum...
  13b2c9aacb1b75e74262d9fd6117b9656948181a0b1f660feb94411b4af6f375

Analyzing snapshots data and computing rewards...
  Total Rewards: 51017.23344 BTS

Let's verify the current proposal
  Getting proposal '1.10.54158' from the blockchain...
  Loading computed rewards data and mimic a proposal...
  Comparing proposals...
    No difference found!



$ ruby mm_rewards.rb 2019-12-14 1.10.54084

Date: 2019-12-14

Computing snapshots chucksum...
  a6755eca96ef4c66c9ceac0b35a60b8bf8bc8371c224e3c17f78ccc2afa4e028

Analyzing snapshots data and computing rewards...
  Total Rewards: 50483.23328 BTS

Let's verify the current proposal
  Getting proposal '1.10.54084' from the blockchain...
  Loading computed rewards data and mimic a proposal...
  Comparing proposals...
    No difference found!



$ ruby mm_rewards.rb 2019-12-13 1.10.54038

Date: 2019-12-13

Computing snapshots chucksum...
  a80c223a87eb59b3487d1a44dea07e54ed54ba646889282cd34ca2c084c1c258

Analyzing snapshots data and computing rewards...
  Total Rewards: 50927.45068 BTS

Let's verify the current proposal
  Getting proposal '1.10.54038' from the blockchain...
  Loading computed rewards data and mimic a proposal...
  Comparing proposals...
    No difference found!