Search results

I'm using 0.14.0.2. But, It's moot now as I used another wallet to do the tx. I agree with the comments though. The only possibilities I can think of are 1) the full re-scan failed somehow when the key was imported as @AgnewPickens alluded to, or the UTXO for the masternode collateral was...

Blockchain is fully synced (you can see the balance is being reported as 1000 in the screenshot). OS is Ubuntu 16.04.

Hello, I've imported a private key via the debug console to access 1000 DASH (previously used for staking a Masternode, but the MN is now shutdown and subsequently banned by the network). I'm unable to spend the DASH because QT is reporting an insufficient balance. See attached screenshot. Any...

Yes, I think you're right. Also, I'm seeing the number of total bans flattening out now. For a while it looked like the bans were just going to keep happening, but in the end it looks like only a fraction of the network was/will be affected. I'm re-establishing my masternodes on upgraded...

We are looking at different stats. Maybe you can help me rectify them as I don't want to spread misinformation. The data I am gathering is based on the debug.log from one of my masternodes that has been running since well before the spork activation. Everytime a masternode is punished we see an...

Latest stats (from parsing debug.log): - unique masternode IDs punished: 1,159 (23.7%) - unique masternode IDs banned: 434 (8.9%) This chart is available at: http://sporked.seeger.net and is updated every 10 minutes.

Have the recommended specs changed since v14?

True but with r=0.99 it's compelling. The slope is tapering slowly which means it's probably not truly linear, but asymptotic with a % of nodes banned per time period instead of a fixed number which makes more sense. This defines a masternode half-life under the DKG Spork, new stat coming soon!

Latest stats on DKG spork activation: Slope: bans/day=72.23 Correlation: r=0.991 Estimated network death: 65 days Masternodes banned: 372 (7.5%) Masternodes revived: 74 Revived masternodes banned: 7 (9.5%)

I appreciate the responsiveness and all the info here in this thread. I'm reviewing my config carefully including the blspriv/operator key pairs and have sent my MN info to @codablock. Meanwhile, I'm watching the bans very closely. Here are the latest stats: Since activation: 274 total bans...

Half my nodes on Vultr are banned even though they've never experienced any down time. All of them have a PoSe penalty > 0. I parsed the debug.log to produce this chart - definitely linear, possibly exponential. I don't think it's worth the effort to re-establish my nodes until this is resolved...

Half my nodes on Vultr are banned even though they've never experienced any down time. All of them have a PoSe penalty > 0. I parsed the debug.log to produce this chart - definitely linear, possibly exponential. I don't think it's worth the effort to re-establish my nodes until this is resolved...