★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit

[DigiByte]

Does anyone know who runs the Digi Tools block explorer? http://digitools.pw/chain/DigiByte

They need to update to DigiByte v2.0 DigiShield!

[The_Cashier]

Does anyone know who runs the Digi Tools block explorer? http://digitools.pw/chain/DigiByte

They need to update to DigiByte v2.0 DigiShield!

Do we have a working explorer ?

[zhangxpc]

Does anyone know who runs the Digi Tools block explorer? http://digitools.pw/chain/DigiByte

They need to update to DigiByte v2.0 DigiShield!

hey ,guys ,we need stable net hash ,how we can make it stable、？

[DigiByte]

Does anyone know who runs the Digi Tools block explorer? http://digitools.pw/chain/DigiByte

They need to update to DigiByte v2.0 DigiShield!

Do we have a working explorer ?

These are up to date:

DigiByte Blockchain Explorers

Crypto Pool Explorer | Alt Explorer

[DigiByte]

Does anyone know who runs the Digi Tools block explorer? http://digitools.pw/chain/DigiByte

They need to update to DigiByte v2.0 DigiShield!

hey ,guys ,we need stable net hash ,how we can make it stable、？

We have no control over when someone adds or takes away their hash. The hash has been within a stable range.

[zhangxpc]

Does anyone know who runs the Digi Tools block explorer? http://digitools.pw/chain/DigiByte

They need to update to DigiByte v2.0 DigiShield!

hey ,guys ,we need stable net hash ,how we can make it stable、？

We have no control over when someone adds or takes away their hash. The hash has been within a stable range.

sometimes 1500+,but sometimes 500+,that's ~~~~~~i dont know how to explain,feel it ~

[DigiByte]

Does anyone know who runs the Digi Tools block explorer? http://digitools.pw/chain/DigiByte

They need to update to DigiByte v2.0 DigiShield!

hey ,guys ,we need stable net hash ,how we can make it stable、？

We have no control over when someone adds or takes away their hash. The hash has been within a stable range.

sometimes 1500+,but sometimes 500+,that's ~~~~~~i dont know how to explain,feel it ~

There first few hours people were trying to figure out if there was an "xploit" they could take advantage of. The hash is more stable now verus the first few hours.

Check out the awesome chart on coinium to see: http://digi.coinium.org/

Before DigiShield took effect the same hash swings occurred, accept now we are not "stuck" for 2-3 hours and the difficulty adjusts within a couple blocks to hash swings both up and down.

We tested over 50 different configurations over the course of 5 days including the Kimoto Gravity Well and other approaches. The DigiShield configuration out performed all other configurations and is essentially a sum of what we learned and applied from other setups.

[mintzone]

Does anyone know who runs the Digi Tools block explorer? http://digitools.pw/chain/DigiByte

They need to update to DigiByte v2.0 DigiShield!

hey ,guys ,we need stable net hash ,how we can make it stable、？

We have no control over when someone adds or takes away their hash. The hash has been within a stable range.

sometimes 1500+,but sometimes 500+,that's ~~~~~~i dont know how to explain,feel it ~

There first few hours people were trying to figure out if there was an "xploit" they could take advantage of. The hash is more stable now verus the first few hours.

Check out the awesome chart on coinium to see: http://digi.coinium.org/

Before DigiShield took effect the same hash swings occurred, accept now we are not "stuck" for 2-3 hours and the difficulty adjusts within a couple blocks to hash swings both up and down.

We tested over 50 different configurations over the course of 5 days including the Kimoto Gravity Well and other approaches. The DigiShield configuration out performed all other configurations and is essentially a sum of what we learned and applied from other setups.

"xploit"...
That was a low hanging joke, wasn't it?  

[DigiByte]

Does anyone know who runs the Digi Tools block explorer? http://digitools.pw/chain/DigiByte

They need to update to DigiByte v2.0 DigiShield!

hey ,guys ,we need stable net hash ,how we can make it stable、？

We have no control over when someone adds or takes away their hash. The hash has been within a stable range.

sometimes 1500+,but sometimes 500+,that's ~~~~~~i dont know how to explain,feel it ~

There first few hours people were trying to figure out if there was an "xploit" they could take advantage of. The hash is more stable now verus the first few hours.

Check out the awesome chart on coinium to see: http://digi.coinium.org/

Before DigiShield took effect the same hash swings occurred, accept now we are not "stuck" for 2-3 hours and the difficulty adjusts within a couple blocks to hash swings both up and down.

We tested over 50 different configurations over the course of 5 days including the Kimoto Gravity Well and other approaches. The DigiShield configuration out performed all other configurations and is essentially a sum of what we learned and applied from other setups.

"xploit"...
That was a low hanging joke, wasn't it?  

Don't tell xploited.

What do you think our next move should be. What do you as the community want to see happen with DigiByte next? In your opinion where should we focus our efforts this coming week now that we have resolved the multi pool issue and reduced the reward?

[canman]

hey digibyte.  been mining at coinium and since the new diff took place the diff has been all over the place.  never consistant.  it will go from 8 to 9 then jump to 12 to 15 then back now to 7.  cna you explain as to why it does this.  and im getting much more rejects with this new diff change.  plz explain.

[HollowStorm]

// Maximum 400% adjustment...
        bnResult *= 200;

Is there something we are over looking here? With a much higher (actual) hash load will this adjustment act differently? What are the dangers of allowing very large diff swings like this?

Also, with a higher difficulty # like the 10-20 range we currently see, will we see any other phenomena that we can't test in the low hash test-net environment? Are we on the right path? What are your thoughts?

I think this might give miners a lot (as in, A LOT) of rejects as soon as the difficulty adjusts, unless your tests say otherwise.

Good point to consider! Thanks for the feedback! We will look at that more in depth.

Told you so..

hey digibyte.  been mining at coinium and since the new diff took place the diff has been all over the place.  never consistant.  it will go from 8 to 9 then jump to 12 to 15 then back now to 7.  cna you explain as to why it does this.  and im getting much more rejects with this new diff change.  plz explain.

[grynca]

// Maximum 400% adjustment...
        bnResult *= 200;

Is there something we are over looking here? With a much higher (actual) hash load will this adjustment act differently? What are the dangers of allowing very large diff swings like this?

Also, with a higher difficulty # like the 10-20 range we currently see, will we see any other phenomena that we can't test in the low hash test-net environment? Are we on the right path? What are your thoughts?

I think this might give miners a lot (as in, A LOT) of rejects as soon as the difficulty adjusts, unless your tests say otherwise.

Good point to consider! Thanks for the feedback! We will look at that more in depth.

Told you so..

hey digibyte.  been mining at coinium and since the new diff took place the diff has been all over the place.  never consistant.  it will go from 8 to 9 then jump to 12 to 15 then back now to 7.  cna you explain as to why it does this.  and im getting much more rejects with this new diff change.  plz explain.

Difficulty jumps up and down dynamically but this should not be problem, it is to be expected from retarget each block, also right now there still large swings in net hashrate.
You can mine on PPLNS pool (such as digiforce.cc) which will smoothen rewards for you.
About reject rate, can you provide more data? I am both mining and administrating pool and i did not notice increase in rejects.

[makishart]

// Maximum 400% adjustment...
        bnResult *= 200;

Is there something we are over looking here? With a much higher (actual) hash load will this adjustment act differently? What are the dangers of allowing very large diff swings like this?

Also, with a higher difficulty # like the 10-20 range we currently see, will we see any other phenomena that we can't test in the low hash test-net environment? Are we on the right path? What are your thoughts?

I think this might give miners a lot (as in, A LOT) of rejects as soon as the difficulty adjusts, unless your tests say otherwise.

Good point to consider! Thanks for the feedback! We will look at that more in depth.

Told you so..

hey digibyte.  been mining at coinium and since the new diff took place the diff has been all over the place.  never consistant.  it will go from 8 to 9 then jump to 12 to 15 then back now to 7.  cna you explain as to why it does this.  and im getting much more rejects with this new diff change.  plz explain.

Probably he is talking about shares reject.. How is that connected to the coin?

[vectisitch]

diff at 34

[grynca]

diff at 34

Yes because net hashrate is 2.1GHs

[HollowStorm]

Difficulty jumps up and down dynamically but this should not be problem, it is to be expected from retarget each block, also right now there still large swings in net hashrate.
You can mine on PPLNS pool (such as digiforce.cc) which will smoothen rewards for you.
About reject rate, can you provide more data? I am both mining and administrating pool and i did not notice increase in rejects.

hey digibyte.  been mining at coinium and since the new diff took place the diff has been all over the place.  never consistant.  it will go from 8 to 9 then jump to 12 to 15 then back now to 7.  cna you explain as to why it does this.  and im getting much more rejects with this new diff change.  plz explain.

Ask canman man.. I'm mining too..  I havent noticed any change in rejects either

[makishart]

keep it steady people!
there are many miners that have DiGi in their profit list!
the diff is low and its easily manipulated.
when the diff will start to grow this will change a lot

[DigiByte]

// Maximum 400% adjustment...
        bnResult *= 200;

Is there something we are over looking here? With a much higher (actual) hash load will this adjustment act differently? What are the dangers of allowing very large diff swings like this?

Also, with a higher difficulty # like the 10-20 range we currently see, will we see any other phenomena that we can't test in the low hash test-net environment? Are we on the right path? What are your thoughts?

I think this might give miners a lot (as in, A LOT) of rejects as soon as the difficulty adjusts, unless your tests say otherwise.

Good point to consider! Thanks for the feedback! We will look at that more in depth.

Told you so..

hey digibyte.  been mining at coinium and since the new diff took place the diff has been all over the place.  never consistant.  it will go from 8 to 9 then jump to 12 to 15 then back now to 7.  cna you explain as to why it does this.  and im getting much more rejects with this new diff change.  plz explain.

Probably he is talking about shares reject.. How is that connected to the coin?

We have not noticed an increase in rejects. We have, however, noticed an increase the amount of coins we mine as the diff/reward is more consistent that before when we would be "stuck" for a few hours following a large hash down swing.

Yes there are some big jumps and dips in the difficulty. Its suppose to do that with big up or down turns in net hash. It is far more responsive to net hash changes then the Kimoto Gravity well. Which be by the way, we found could still get "stuck" for awhile with a large hash down turn. It also can get isntamined for awhile with a large hash increase.

We now have the most responsive difficulty retarget system of any coin out there. It litterally only takes 2-4 blocks to adjust to a doubling of the net hash or a massive downswing.

[canman]

// Maximum 400% adjustment...
        bnResult *= 200;

Is there something we are over looking here? With a much higher (actual) hash load will this adjustment act differently? What are the dangers of allowing very large diff swings like this?

Also, with a higher difficulty # like the 10-20 range we currently see, will we see any other phenomena that we can't test in the low hash test-net environment? Are we on the right path? What are your thoughts?

I think this might give miners a lot (as in, A LOT) of rejects as soon as the difficulty adjusts, unless your tests say otherwise.

Good point to consider! Thanks for the feedback! We will look at that more in depth.

Told you so..

hey digibyte.  been mining at coinium and since the new diff took place the diff has been all over the place.  never consistant.  it will go from 8 to 9 then jump to 12 to 15 then back now to 7.  cna you explain as to why it does this.  and im getting much more rejects with this new diff change.  plz explain.

Difficulty jumps up and down dynamically but this should not be problem, it is to be expected from retarget each block, also right now there still large swings in net hashrate.
You can mine on PPLNS pool (such as digiforce.cc) which will smoothen rewards for you.
About reject rate, can you provide more data? I am both mining and administrating pool and i did not notice increase in rejects.

it is a problem as the diff changes all the time. this gives me knew block and can get lots of rejects.  i try to stay under 1 percent and now i get 3 to 5 percent.  not good as thats shares im not getting.  

edit now diff is 46  wow

[canman]

also it seems that when the diff changes and no shares are accepted, the diff will change again then i will get the rejects. 


so it would say "network diff set to 9
stratum from pool 0 detected new block."
"network diff set to 10"
stratum from pool 0 detected new block"


as my miners are still hashing at diff of 9 then changes to 10, at the 10 diff is where i would get the rejects of shares. 

can someone explain