[ANN][VRM] Verium PoWT | CPU mining | scrypt² | Scaling | New Roadmap Released

[Kazadar]

deleted blockchain, trying to resync now but its very slow, only 1 connection has current block and the rest -1 height, its very how there was 60+ connections before, now its nothing, where is everyone ?

For the last couple of hours of activity there has been a lot of hashpower mining on and off every few blocks. Perhaps someone is trying to fork the chain?

[wgd]

deleted blockchain, trying to resync now but its very slow, only 1 connection has current block and the rest -1 height, its very how there was 60+ connections before, now its nothing, where is everyone ?

For the last couple of hours of activity there has been a lot of hashpower mining on and off every few blocks. Perhaps someone is trying to fork the chain?

I did not notice anything alarming with a drastic increase hashpower

[thesilex]

deleted blockchain, trying to resync now but its very slow, only 1 connection has current block and the rest -1 height, its very how there was 60+ connections before, now its nothing, where is everyone ?

For the last couple of hours of activity there has been a lot of hashpower mining on and off every few blocks. Perhaps someone is trying to fork the chain?

I did not notice anything alarming with a drastic increase hashpower

Network hash rate was going up to 600 Mhs, then down to 130 again and again.

[hulahoof]

...

For the last couple of hours of activity there has been a lot of hashpower mining on and off every few blocks. Perhaps someone is trying to fork the chain?

I did not notice anything alarming with a drastic increase hashpower

Network hash rate was going up to 600 Mhs, then down to 130 again and again.

I didn't see this either, but that is a lot of hash power...

[pwpwpw]

true, there were big bounces in the past 24hours. Can someone tell me why am I syncing from only one source ?

Code:


[
{
"addr" : "104.197.90.102:42596",
"services" : "00000001",
"lastsend" : 1473373151,
"lastrecv" : 1473373469,
"conntime" : 1473373150,
"version" : 80000,
"subver" : "/Veritoshi:1.0/",
"inbound" : true,
"startingheight" : 2394,
"banscore" : 0
},
{
"addr" : "209.181.66.82:57134",
"services" : "00000000",
"lastsend" : 0,
"lastrecv" : 1473374536,
"conntime" : 1473374536,
"version" : 0,
"subver" : "",
"inbound" : true,
"startingheight" : -1,
"banscore" : 0
}
]

if there is any new connection, it looks like the 2nd, no version/subversion/ height -1 and it lost after a few seconds.
Right now I got a few new connections with version and I'm stuck at block #2000

[hulahoof]

true, there were big bounces in the past 24hours. Can someone tell me why am I syncing from only one source ?

Code:


[
{
"addr" : "104.197.90.102:42596",
"services" : "00000001",
"lastsend" : 1473373151,
"lastrecv" : 1473373469,
"conntime" : 1473373150,
"version" : 80000,
"subver" : "/Veritoshi:1.0/",
"inbound" : true,
"startingheight" : 2394,
"banscore" : 0
},
{
"addr" : "209.181.66.82:57134",
"services" : "00000000",
"lastsend" : 0,
"lastrecv" : 1473374536,
"conntime" : 1473374536,
"version" : 0,
"subver" : "",
"inbound" : true,
"startingheight" : -1,
"banscore" : 0
}
]

if there is any new connection, it looks like the 2nd, no version/subversion/ height -1 and it lost after a few seconds.
Right now I got a few new connections with version and I'm stuck at block #2000

That's odd, did you resync from scratch or from bootstrap? The one miner I did refresh blockchain on I started with bootstrap it's now connected to ~24 peers and stuck again on the 2394 block

[pwpwpw]

I resynced from scratch but its stuck at the same block you are on, sync was only from one connection but it finished slowly now I have 20+ connections. Right now mining does use wattage but produces 0 hash in client so its useless ?

[effectsToCause]

Hey guys,

looking into problem.  The blockchain froze so we are on pause till we resolve the issue, it looks like someone submitted a block with a future timestamp and that threw the difficulty calculation off.  I'm looking deeper into the problem, but likely we will need to release an updated wallet that handles this problem specifically before we get going again.  Thanks for your patience while we work this out.

[hulahoof]

Hey guys,

looking into problem.  The blockchain froze so we are on pause till we resolve the issue, it looks like someone submitted a block with a future timestamp and that threw the difficulty calculation off.  I'm looking deeper into the problem, but likely we will need to release an updated wallet that handles this problem specifically before we get going again.  Thanks for your patience while we work this out.

Thanks for the update, I'll keep my miners off until is resolved then

[bilbro_baggins]

Hey guys,

looking into problem.  The blockchain froze so we are on pause till we resolve the issue, it looks like someone submitted a block with a future timestamp and that threw the difficulty calculation off.  I'm looking deeper into the problem, but likely we will need to release an updated wallet that handles this problem specifically before we get going again.  Thanks for your patience while we work this out.

Thanks for the update! Good luck squashing the bug.

[monsanto]

Might be a good thing after all that it hasn't been added to an exchange yet 

[effectsToCause]

Found the problem, now testing the solution to it.

[wgd]

When will resume network?

[effectsToCause]

When will resume network?

Releasing update today with tweak to difficulty calculation to fix problem and prevent it from happening again. Mining will resume from block 2394 with new difficulty parameter. Basically the difficulty adjustment was set too aggressive such that when an aberrant block timestamp came in the difficulty adjustment was too severe for the protocol to allow, so the work from that point on was not accepted. I've made a change to the difficulty adjustment which averages the exponential adjustment rate of the difficulty over a longer period and prevents this from happening again. This new difficulty rate will actually be better for the network overall too. The difficulty was purposely set aggressive so that the variable block time quickly ensures that the chain with the most power will always have the shortest block time and be longest chain. It was just set a bit too aggressive for a larger deviation in the block time stamping.

[Dreikesehoch]

Could you please give an estimated time for fixing the problem? Not a good start at all!

[ljglug]

When will resume network?

Releasing update today with tweak to difficulty calculation to fix problem and prevent it from happening again. Mining will resume from block 2394 with new difficulty parameter. Basically the difficulty adjustment was set too aggressive such that when an aberrant block timestamp came in the difficulty adjustment was too severe for the protocol to allow, so the work from that point on was not accepted. I've made a change to the difficulty adjustment which averages the exponential adjustment rate of the difficulty over a longer period and prevents this from happening again. This new difficulty rate will actually be better for the network overall too. The difficulty was purposely set aggressive so that the variable block time quickly ensures that the chain with the most power will always have the shortest block time and be longest chain. It was just set a bit too aggressive for a larger deviation in the block time stamping.

So now you can normally use it？

[souljah1h]

When will resume network?

Releasing update today with tweak to difficulty calculation to fix problem and prevent it from happening again. Mining will resume from block 2394 with new difficulty parameter. Basically the difficulty adjustment was set too aggressive such that when an aberrant block timestamp came in the difficulty adjustment was too severe for the protocol to allow, so the work from that point on was not accepted. I've made a change to the difficulty adjustment which averages the exponential adjustment rate of the difficulty over a longer period and prevents this from happening again. This new difficulty rate will actually be better for the network overall too. The difficulty was purposely set aggressive so that the variable block time quickly ensures that the chain with the most power will always have the shortest block time and be longest chain. It was just set a bit too aggressive for a larger deviation in the block time stamping.

So now you can normally use it？

Today update will be released. Please wait for that.

[souljah1h]

Could you please give an estimated time for fixing the problem? Not a good start at all!

Time = today. No fixed time.

[metropolia]

The launch time has been delayed? Actually test more before launch, a good but delayed launched is better than a buggy on time launch.

[boy2k]

Agreed, ready and not buggy is preferred!

Just check DNET for what happens when you rush things out...