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

[effectsToCause]

Found the problem, now testing the solution to it.

[1714180315]

1714180315

[1714180315]

1714180315

[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...

[souljah1h]

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

Agreed, ready and not buggy is preferred!

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

What are you guys talking about? Verium launched a week ago..

It's not buggy, someone exploited the chain.

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.

Either their system is all messed up or they were trying to manipulate the difficulty adjustment. It successfully did that but the protocol caught it and denied any new block. The system worked perfectly actually.

- Changing a parameter of the adjustment so this can't happen again
- The diff adjustment was a bit too aggressive which made this possible

Just some tweaking now to prevent this from happening.

[wgd]

I am concerned about stuck verium network, dev whether it will be a statement on the cause?

[pwpwpw]

I am concerned about stuck verium network, dev whether it will be a statement on the cause?

He wrote just before you, wallet update coming soon to fix it.

[wgd]

these are user guesses, if the dev has find the cause we are waiting for explanations

[penambang]

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.

[souljah1h]

these are user guesses, if the dev has find the cause we are waiting for explanations

Dude just read this last page. @EffectsToCause is the dev.

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.

[wgd]

f*** I did not seen last effectsToCause  post, sorry dude 

[souljah1h]

f*** I did not seen last effectsToCause  post, sorry dude 

No problem 

[bilbro_baggins]

Good lord, chill TF out people, you ain't gonna get rich mining Verium within 24 hours, especially when no-one can mine in this case. These are some of the best devs out there, they've explained the issue, and have a fix coming. Go grab some coffee, go outside and get some sun, think about your lives for a day or two while the fix is being released. It's not the end of the world. Don't demand anything when you have no place to demand anything. The blockchain will be back up and running normally soon. Breathe.

P.S. There will ALWAYS be bugs, not matter how much testing is done, don't blame the devs for this. You sound like assholes.

[Crypt0Future]

Waiting for Win 64 fixed wallet 

[wgd]

look forward to any fix wallet