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

Cybnate 2016-04-11 07:14:24 UTC #102

Strange, I’m on 4.01 Linux/Ubuntu 15.04 and minting a lot without issues, maybe we can narrow down to an issue with the Windows wallet?

Sentinelrv 2016-04-11 07:21:50 UTC #103

Well, that wouldn’t explain my issue. As I said I’m using Xubuntu, not Windows. I’ll be going to work in about 3 hours. When I come back I’ll check to see if I minted at all.

About active connections, currently Peerunity has 8, B&C has 3 and Nu has 5. I recently restarted the laptop though, so I’m not sure if that is a reason for the low number.

zoro 2016-04-11 07:25:15 UTC #104

A proxy or tor could explain the low number.

Cybnate 2016-04-11 07:27:19 UTC #105

I have 7 connections without TOR or proxy which is unusual. Should be 8, will keep an eye on it. Hope we are not ending up in a fork.

Sentinelrv 2016-04-11 07:28:40 UTC #106

I don’t use tor and don’t know how to setup a proxy. I just downloaded the client and started minting, so it shouldn’t be that.

masterOfDisaster 2016-04-11 07:44:38 UTC #107

It feels like it’s about time to have a statement from the development team on the nature of the bug in the 4.0.0 version.
My gut tells me what we encounter here is related to it.

@JordanLee, @sigmike, @Eleven, @glv can any of you please explain what’s the nature of the defect in 4.0.0 that makes an upgrade to 4.0.1 mandatory?
Can the trouble with low numbers of connections and the inability to mint (without having changed any setting) be related to the bug?

@Sentinelrv, @Cybnate can you please check the hash of block 401,662? That was the most recent block when I had a look at the blockchain:

getinfo
{
    "version" : "v4.0.1-beta",
    "protocolversion" : "2.0",
    "walletversion" : 1,
    "walletunit" : "8",
    "balance" : 0.0,
    "newmint" : 0.0,
    "stake" : 0.0,
    "parked" : 0.0,
    "blocks" : 401662,
    "moneysupply" : 187861.3671,
    "connections" : 8,
    "proxy" : "",
    "ip" : "redacted",
    "difficulty" : 0.00062953,
    "testnet" : false,
    "keypoololdest" : 1459935949,
    "keypoolsize" : 101,
    "paytxfee" : 0.01,
    "errors" : ""
}

getblockhash 401662
41eec1da306538296d66e2c690783641c2b8b43a48cb809f2b1f43fb4e46915e

masterOfDisaster 2016-04-11 08:08:01 UTC #109

Oh, you have BKS in your wallet!
Are you sure you want to know the world about that?

Cybnate 2016-04-11 08:08:47 UTC #110

getblockhash 401662

41eec1da306538296d66e2c690783641c2b8b43a48cb809f2b1f43fb4e46915e

getinfo
"version" : “v4.0.1-beta”,
“protocolversion” : “2.0”,
“walletversion” : 1,
“walletunit” : “8”,
“balance” : xxx,
“newmint” : 0.0,
“stake” : xxx,
“parked” : 0.0,
“blocks” : 401694,
“moneysupply” : 187861.6871,
“connections” : 7,
“proxy” : “”,
“ip” : “xxxx”,
“difficulty” : 0.00063044,
“testnet” : false,
“keypoololdest” : 1439374527,
“keypoolsize” : 251,
“paytxfee” : 0.01,
“unlocked_until” : 0,
“errors” : “”
}

cryptog 2016-04-11 08:10:18 UTC #111

I am able to mint now again. That is fine here.

Sentinelrv 2016-04-11 08:13:00 UTC #112

Forgot to edit that out. Here is my post again…

getinfo
{
"version" : "v4.0.1-beta",
"protocolversion" : "2.0",
"walletversion" : 1,
"walletunit" : "8",
"balance" : redacted,
"newmint" : 0.0,
"stake" : 0.0,
"parked" : 0.0,
"blocks" : 401686,
"moneysupply" : 187861.6071,
"connections" : 3,
"proxy" : "",
"ip" : "redacted",
"difficulty" : 0.00063023,
"testnet" : false,
"keypoololdest" : 1440005671,
"keypoolsize" : 101,
"paytxfee" : 0.01,
"unlocked_until" : 0,
"errors" : ""
}
getblockhash 401662
41eec1da306538296d66e2c690783641c2b8b43a48cb809f2b1f43fb4e46915e

masterOfDisaster 2016-04-11 08:20:59 UTC #113

The good news is that

@Cybnate (successfully minting with 4.0.1 on Ubuntu 15.04),
@Sentinelrv (not able to mint with 4.0.1 on Xubuntu Linux) and
@masterOfDisaster (not minting, just running a node with 4.0.1 on Ubuntu 15.10)

are on the same fork (blockhash for 401,662 for all 41eec1da306538296d66e2c690783641c2b8b43a48cb809f2b1f43fb4e46915e).

That still leaves the question open, why @Sentinelrv and @crypto_coiner can’t mint.
Which is even more strange for @Sentinelrv, because Xubuntu is basically Ubuntu with a different GUI, right (and @Cybnate can mint with Ubuntu 15.04)?
@Sentinelrv, what’s your Xubuntu release? If you don’t know where to find it, open a shell and execute
cat /etc/lsb-release

@crypto_coiner do you mind posting the blockhash of block 401,662 (your operating system is Win7, right?)?

Sentinelrv 2016-04-11 08:23:44 UTC #114

How do I do that?

crypto_coiner 2016-04-11 08:32:52 UTC #115

getblockhash 401662
41eec1da306538296d66e2c690783641c2b8b43a48cb809f2b1f43fb4e46915e

getinfo

{
“version” : “v4.0.1-beta”,
“protocolversion” : “2.0”,
“walletversion” : 1,
“walletunit” : “8”,
“balance” : xxx
"newmint" : 0.0,
“stake” : 0.0,
“parked” : 0.0,
“blocks” : 401712,
“moneysupply” : 187861.8671,
“connections” : 8,
“proxy” : xxx
"ip" : “xxx
"difficulty” : 0.00062989,
“testnet” : false,
“keypoololdest” : 1436764011,
“keypoolsize” : 101,
“paytxfee” : 0.01,
“unlocked_until” : 0,
“errors” : “”

machine: win7

Sentinelrv 2016-04-11 08:49:57 UTC #116

Nevermind, I seemed to have figured it out…

Distributor ID:    Ubuntu
Description:    Ubuntu 14.04.4 LTS
Release:    14.04
Codename:    trusty

Cybnate 2016-04-11 08:51:36 UTC #117

Strange, nothing odd in your debug.logs? I had a look in mine, but there is nothing strange there other than that I’m only connected to 7 peers consistently which I think is unusual in itself.

Maybe it is related to the asset voting in the datafeeds somehow? Should we stop it? Maybe peers are banned for some reason? Would be good to hear something from the developers before we do or change something.

CoinGame 2016-04-11 08:57:09 UTC #118

The bug would have prevented users from being able to mint after the protocol upgrade. It has no relation to the current protocol voting lethargy.

masterOfDisaster 2016-04-11 08:57:54 UTC #119

It’s good to have the asset voting prepared, but I hope nobody registered the data feeds yet.
Asset voting is possible once the protocol was changed to 4.0.
If those votes are configured now they might create invalid blocks, although I don’t know how protocol 2.0 treats configured asset votes - whether they are just superfluous information or indeed lead to invalid blocks.

@Sentinelrv, do you have any votes (signer, asset votes, etc.) configured? If yes, please remove them and keep an eye on your client.

I was not referring to lethargy, but to 4.0.1 clients, that aren’t able to mint and hence aren’t producing protocol 4.0 blocks - leading to a lowered percentage of 4.0 blocks.
I was just thinking misbehaving 4.0.0 clients might have to do with that.

Sentinelrv 2016-04-11 09:14:28 UTC #120

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.

crypto_coiner 2016-04-11 10:41:50 UTC #121

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” : [
]
}

CoinGame 2016-04-11 11:19:36 UTC #122

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.