I removed all the new vote types from my data feed just in case. Still only 3 active connections. I’m leaving for work now. I won’t be back to check on it for a while.
Not too fast – I subscribed to @cryptog feeds on 4/6.
As an experiment, I have removed all new type of vote and I am now minting again.
getvote
{
“custodians” : [
],
“parkrates” : [
],
“motions” : [
],
“fees” : {
“8” : 0.01,
“C” : 0.01
},
“reputations” : [
],
“signerreward” : {
“count” : null,
“amount” : null
},
“assets” : [
]
}
1 Like
Ahh sorry I responded literally a couple minutes after waking up. I think I made up my own context before actually being mentally awake. Can someone summarize the not minting issue? I don’t have time to go searching right now.
2 Likes
Better than responding minutes before you wake up 
My current assessment is that configuration of votes made the 4.0.1 clients create invalid blocks.
Both @Sentinelrv and @crypto_coiner did register data feeds before the minting stopped.
@Cybnate has less than 8 connections.
I was thinking something with 4.0.0 might make trouble, leading to invalid blocks and a low connection count.
Now I think it’s just too early to configure votes. Only after the protocol switch to 4.0 it’s possible to mint valid blocks that have votes for signers, assets, etc. and @Cybnate just has a strangely low connection count.
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.
I dare say, there’s no general (technical) problem and we only have problems with upgrading apathy.
Sorry for the alarm.
1 Like
Reputed signer votes and asset votes are not considered by the client until the protocol changes. If there’s an issue with feeds the client will display a warning as well in the BlockShares info section. So I think either the issue is not there, or should be easy to spot regarding feeds.
3 Likes
@crypto_coiner But you said that you did nothing.
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.
Right. I will modify today my data feeds and remove all votes enabled by version 4.
That incident reminds me that “nothing” is to double-check in quality assurance, indeed.
@cryptog, as I said above, after I upgraded to v4.0.1 on March 31st I was still minting blocks until April 4th. I was following your data feed (I originally thought it was Cybnate’s feed, but it was yours) and it turns out that the day I stopped minting blocks is the same day you started voting for assets and other things, April 4th…
2 Likes
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
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%
1 Like
Dont have access to my machine right now - will get to it in about 10h.
@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"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.
2 Likes
Just got home from work and noticed this same error message at the bottom of my client.
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.
1 Like
Got this error several times:
ERROR: CreateCoinStake : generated vote is invalid
when I was not able to mint
43.1%, still rising 
That seems to work
1 Like
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
Try to delete you address.dat, and restart.
1 Like