[Passed]Motion to elect Sigmike as B&C's technical leader

[crypto_coiner]

SIgmike can decide technical problem, other developers must obey him when writing code for B&C.

You introduce then a hierarchy as for the development – why?
Sigmike > eleven.
That will give ideas to others and create hierarchy for aspects of Nu governance, like LPC for example –

[Sabreiib]

When you check B&C, signed by “Siglee”, which means Sigmike and Jordan Lee.

A software development team is a hierarchy structure from the very beginning, including BTC dev team, so not my introduce.

It’s open sourced project, anyone dislikes dev leader can fork the source code, feel free to modify it, as long as he/she can persuade most coin holders to download his version, he is successful.

[crypto_coiner]

A software development team is a hierarchy structure from the very beginning, including BTC dev team, so not my introduce

Sigmike could push code decision over the blockchain and that hierarchy vanishes but that is not useful for 2members org or decision making process

[Sabreiib]

If eleven doesn’t obey sigmike, shareholders can stop pay salary to eleven.

If this motion passed, it means majority of BKS holders support sigmike’s code, of course some may refuse to download sigmike’s version and use other version, then B&C blockchain forks.

[Sabreiib]

vote ratio drops within several hours, why? Any data feed problem?

[backpacker]

It’s OK for votes to fluctuate during a course of the day, as some nodes go up and down all day along

[crypto_coiner]

no major feed provider has added it yet

[cryptog]

c1e9a92ca18591e78c7489b658bf414da7bd1a2e

voting.

[Sabreiib]

B&C V5.0 is released! Windows and Linux are ready. Thank @sigmike and other developers!

https://bitbucket.org/JordanLeePeershares/bcexchange/downloads

[cryptog]

Wo nice!

Is it safe to use it now?

[Sabreiib]

I’ll upgrade after this motion passed.

BTW, MacOS users can follow

https://bitbucket.org/JordanLeePeershares/bcexchange/src/e472f471107c14fee592ae64eff843708f682ba0/doc/?at=master
https://bitbucket.org/JordanLeePeershares/bcexchange/src/e472f471107c14fee592ae64eff843708f682ba0/doc/build-osx-brew-mavericks.txt?at=master&fileviewer=file-view-default

[Cybnate]

B&C V5.0 is released! Windows and Linux are ready. Thank @sigmike and other developers!

This is great news. Hope we can get the majority to the new protocol soon.

Will add this motion to my B&C datafeed within the next 24h.

[sigmike]

B&C V5.0 is released!

Yes I built it but I couldn’t find the time to post about it. This release only includes the lower threshold to switch to the new protocol (described in the 4.0 release) because the other changes are not ready and it’s not clear whether they will be finished shortly given the current state of the project.

[Sabreiib]

So after majority of BKS nodes switch to V5.0.0, we can vote reputed signers.

Technically there can be up to 15 reputed signers, how many should we vote? 15? 12?

I believe these reputed signers are something like “board of directors”, and this group is very important for B&C’s decision making in this special situation.

[Sabreiib]

@Sentinelrv please advertise v5.0, @tomjoad please update the B&C websites, thanks!

[Sentinelrv]

Before I advertise this, I want to get a confirmation from @sigmike and @CoinGame that the reputation voting bug has been fixed in this release. In the last release I discovered that setting reputation votes will prevent you from minting any blocks. Has this been fixed in this release? If you want to know more about this issue, check my replies throughout this thread, where I did tests to discover the issue…

[Mandatory Upgrade] All minters need to upgrade to B&C Exchange 4.0.1

Alright, last night I set the number of reputed signers eligible for reward to 4 and the reward amount per block to 0.01 BKS. Both settings are in the reputation voting section. I didn't mint a single block all night after doing this. I also tried removing one of the two settings and keeping the other and then switching later on to see if only one of these settings was causing the problem, but it didn't make a difference. No blocks were minted. As soon as I removed reputation votes I started…

[sigmike]

I want to get a confirmation from @sigmike and @CoinGame that the reputation voting bug has been fixed in this release.

It has not been fixed. I can make a quick fix and release a 5.0.1.

[Sentinelrv]

I want to get a confirmation from @sigmike and @CoinGame that the reputation voting bug has been fixed in this release.

It has not been fixed. I can make a quick fix and release a 5.0.1.

It would probably be best to wait for this then before encouraging people to upgrade.

[Sabreiib]

getprotocolvotes

{
“2.0” : {
“blocks” : 869,
“block_percentage” : 43.45,
“switch_to_date_time” : “”
},
“4.0” : {
“blocks” : 1130,
“block_percentage” : 56.5,
“switch_to_date_time” : “”
},
“5.0” : {
“blocks” : 1,
“block_percentage” : 0.05,
“switch_to_date_time” : “”
}
}

It’s weird why only always one 5.0 block? I’ve minted several blocks with v5.0 client.

[Sentinelrv]

It’s weird why only always one 5.0 block? I’ve minted several blocks with v5.0 client.

Are the numbers supposed to update immediately or is it delayed?