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

[masterOfDisaster]

Reputed signer votes and asset votes are not considered by the client until the protocol changes.

Oh, they are considered by the clients, but not by the network…
Or the clients withhold minting until the protocol supports these votes.

Based on the feedback from
@crypto_coiner

I subscribed to @cryptog feeds on 4/6

I updated on 3/30 and was minting up to 4/6 since then.

@Sentinelrv

I updated on March 31st and minted up until April 4th and then it stopped as well.

the day I stopped minting blocks is the same day you started voting for assets and other things, April 4th…

@Sabreiib

I added signers vote 10 days ago, then I could not mint. Suddenly I realized that the network protocol hadn’t changed to v 4.0, so I deleted my votes, everything is OK.

it’s quite clear that users who configured votes (manually or by data feed) can’t mint blocks.
I can’t tell whether the network rejects them or the client doesn’t even try to create them.
The debug.log might tell.

@Sabreiib, @Sentinelrv, @crypto_coiner are there any error messages in the debug.log file?

Removing the votes from the data feeds seems to move the network into the right direction - maybe it’s only fluctuation:

getprotocolvotes
{
    "2.0" : {
        "blocks" : 1137,
        "block_percentage" : 56.85,
        "switch_to_date_time" : ""
    },
    "4.0" : {
        "blocks" : 863,
        "block_percentage" : 43.15,
        "switch_to_date_time" : ""
    }
}

At block 402,085: 43.35%

[crypto_coiner]

Dont have access to my machine right now - will get to it in about 10h.

[willy]

@masterOfDisaster add me to the list of cryptog subscribers that weren’t minting.

last block minted April 06, 2016 (I subscribed to his feed around that time)

"errors" : "Unable to set key from data feed signature"

[masterOfDisaster]

“errors” : “Unable to set key from data feed signature”

I have no experience with data feeds, but does that not sound like there’s something wrong with the feed itself and not the content it provides?

Btw. - the protocol 4.0 rate is increasing; this are the results from every quarter of an hour of the last two hours:

    "blocks" : 402124,
        "block_percentage" : 43.55,
    "blocks" : 402134,
        "block_percentage" : 43.45,
    "blocks" : 402145,
        "block_percentage" : 43.3,
    "blocks" : 402157,
        "block_percentage" : 43.45,
    "blocks" : 402161,
        "block_percentage" : 43.5,
    "blocks" : 402165,
        "block_percentage" : 43.65,
    "blocks" : 402174,
        "block_percentage" : 43.7,
    "blocks" : 402188,
        "block_percentage" : 43.75,
    "blocks" : 402197,
        "block_percentage" : 43.7,

The 4.0 percentage is slowly increasing.

[Sentinelrv]

Unable to set key from data feed signature

Just got home from work and noticed this same error message at the bottom of my client.

[cryptog]

Sorry. It seems that putting null as values for signerreward caused an issue.
Fixed here
@crypto_coiner , @Sentinelrv , @willy can you check if the error is gone.

It is gone here.
Sorry for the inconvenience.

[crypto_coiner]

The debug log of @Sentinelrv and @crypto_coiner should contain entries pointing to invalid blocks.The blockhashes of all people who had a look were identical.

Got this error several times:

ERROR: CreateCoinStake : generated vote is invalid

when I was not able to mint

[Yurizhai]

43.1%, still rising

[crypto_coiner]

That seems to work

[Cybnate]

It seems that putting null as values for signerreward caused an issue.

There might still be something else at play. I’m only seeing 6 connections. Yesterday I had 7, it should be 8.
Anyone else having a number lower than 8 connections during a sustained period?

Have no trouble with connections with other clients, like Nu or Peercoin

[Sabreiib]

play. I’m only seeing 6 connections. Yesterday I had 7, it should be 8.Anyone else having a number lower than 8 connections during a sustained period?

Have no trouble with connections with other clients, like Nu or Peercoin

Try to delete you address.dat, and restart.

[cryptog]

I have 8.

[Cybnate]

I have 8 now after deleting addr.dat. Problem solved for me.

[Sentinelrv]

Update from me.

can you check if the error is gone.

Yes, it’s gone, thanks.

Try to delete you address.dat, and restart.

Before you posted this I deleted the B&C client completely from my computer including this file and let it resync. Before I was getting only 3 connections, but now I have 8. I also removed the new voting options in my data feed. I did all this before I went to bed.

When I woke up I checked it and I still hadn’t minted any blocks. I ended up completely removing my data feed and it still didn’t mint. After some further digging, I realized that even though I removed the new voting options from my feed, in the reputation and asset sections, voting was still configured from the feed I had previously removed. Removing the feed had not removed the votes for reputation and assets. Once I removed all the voting manually, I immediately minted a new block. So it seems to be minting normally now.

When I come back from work, is there anything else you guys want me to try? While removing the new voting options worked to get me minting again, I hear that @Cybnate and @Yurizhai are having no problem minting with the new options.

[Sentinelrv]

@Cybnate, I was reading your post in your data feed thread…

Cybnate's B&C datafeed - BETA

Monitored this for a while and I’ve kept my asset voting and the data-feed as it worked for me, so it had to be something else, which it appeared to be. My datafeed is only voting for assets as nothing else so there is no harm in subscribing to it. I’m still minting and subscribed to my own datafeed without any known adverse effects or errors in my logs.

The thing that stuck out to me was that you were only voting for assets and not reputation related stuff. Have you ever tried minting with reputation voting options set?

We all had a problem minting with @cryptog’s feed. Nobody seemed to have a problem with your feed though. One difference I can see is that @cryptog had votes set for both assets and reputation while you only had votes set for assets. Maybe the reputation votes are preventing people from minting? Have you ever minted a block with reputation votes set?

When I get home I’d like to try voting for both assets and reputation at the same time and then only with assets and no reputation and see if either mints blocks on my client.

[Sentinelrv]

Quick update. I got home from work about an hour ago, and found my client continued to mint 21 times throughout the day with no problems. As an experiment, I setup asset voting using the same selections that Cybnate is using while leaving the reputation section blank. I was able to mint a block with asset info selected!

Now I’m going to remove the asset voting info, so it’s blank and instead fill out the reputation voting info that I previously had in there and see if I mint a block then. I’ll give it to tomorrow morning when I wake up.

[masterOfDisaster]

Thanks for your tests.
They very much help narrowing down the reason for the problem!

[Cybnate]

Have you ever tried minting with reputation voting options set?

I haven’t as I didn’t see the need for it yet and I still have to get my head around it. But it is good that it is being tested now. Hope it becomes clear what is going on soon.

[Sentinelrv]

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 minting again. So it seems that reputation votes are preventing people from minting any blocks. Can I have other people verify what I’ve found here?

[Sentinelrv]

@CoinGame, I just wanted to make sure you know about this. Please check my responses above when you get some time.