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

[frottirzokni]

I don't know if it's only a push of a button, but If you could temporarily disable the shield, the current net hashrate would eat up the remaining blocks in a matter of... idunno, but quickly.
If it isn't possible, than lowering the kick-in block number is a good idea.

[1715418451]

1715418451

[1715418451]

1715418451

[1715418451]

1715418451

[24hralttrade]

There is another option to the current slow chain problem. We are currently on block 142, 473. We could release a 3.0.2 wallet the kicks in multi-algo mining at say block 143,500. Then everyone would have to update their wallet again.

We have seen roughly 1,000 blocks since releasing the wallet over a week ago.

What are your thoughts?

First i really want to thank you for the nice update.  

I think releasing a new wallet so everybody need's to update again just to push it is not that good of a idea.

I am sure the community/supporters within  digibyte is willing to help you with solving the blocks faster so we reach block 145.000 fast enough,
we just have to make sure everybody is updated.

Get some tweets out and mention the last update.


After the update kicks in i will work on accepting Digibyte for my business.
Will contact you and have some questions later on.

Have a good day,

24

[DigiByte]

There is another option to the current slow chain problem. We are currently on block 142, 473. We could release a 3.0.2 wallet the kicks in multi-algo mining at say block 143,500. Then everyone would have to update their wallet again.

We have seen roughly 1,000 blocks since releasing the wallet over a week ago.

What are your thoughts?

First i really want to thank you for the nice update.  

I think releasing a new wallet so everybody need's to update again just to push it is not that good of a idea.

I am sure the community/supporters within  digibyte is willing to help you with solving the blocks faster so we reach block 145.000 fast enough,
we just have to make sure everybody is updated.

Get some tweets out and mention the last update.


After the update kicks in i will work on accepting Digibyte for my business.
Will contact you and have some questions later on.

Have a good day,

24

24 Hr,

Thanks for the feedback. We will get on the twitter account and rally the troops!

[DigiByte]

I don't know if it's only a push of a button, but If you could temporarily disable the shield, the current net hashrate would eat up the remaining blocks in a matter of... idunno, but quickly.
If it isn't possible, than lowering the kick-in block number is a good idea.

Unfortunately this is not possible but would be very helpful right now if it was. In the code the old difficulty code will turn off at block 145,000 and the new code will take over. At this point getting more hash on the network is probably our best course of action.

[tdcooper99]

Glad to have some updates, thanks. I will keep my rigs mining on P2Pool....  ~85MH give or take. Lets get this party started already. I agree with the rest, lets just stick with the plan and raise the hashrate slowly and wait for 145,000.... rather than push out another update.

BTW... NZ_miner...  thanks for your efforts so far. I've noticed the super fluctuations in hashrate and in fact due to your efforts it felt like it was the old days again mining DGB...  found tons of blocks overnight last night.  But then it came to a sudden halt, and I guess this is when you pulled your hashrate and left the difficulty sky high :-) .  Anyway, hopefully we can persuade you to come back and help push things along. Not everyone here has the resources to throw that kind of hashrate at the network...  but that doesn't mean it's not appreciated.

[DigiByte]

Does anyone have any other ideas off the top of their head on how to speed up the block timing up to block 145k  besides another mandatory update?

[DigiByte]

Glad to have some updates, thanks. I will keep my rigs mining on P2Pool....  ~85MH give or take. Lets get this party started already. I agree with the rest, lets just stick with the plan and raise the hashrate slowly and wait for 145,000.... rather than push out another update.

BTW... NZ_miner...  thanks for your efforts so far. I've noticed the super fluctuations in hashrate and in fact due to your efforts it felt like it was the old days again mining DGB...  found tons of blocks overnight last night.  But then it came to a sudden halt, and I guess this is when you pulled your hashrate and left the difficulty sky high :-) .  Anyway, hopefully we can persuade you to come back and help push things along. Not everyone here has the resources to throw that kind of hashrate at the network...  but that doesn't mean it's not appreciated.

Thanks for keeping your hash on the network td!

[RJF]

I agree, I think we are getting really close to the point where if we don't push to the new algo soon I feel like we will lose our momentum.  We really need a coordinated mining effort in order to push through to the change over block.

I can push 25 MH/s at it. Which pool do you all recommend?

[tdcooper99]

I'm all about P2Pool...  so I recommend:

http://limp2pool.fr:9022/static/

It's where I am pointing... it's not my own node, but I've been happy there for a long time.

.... there are other nodes too, just make sure they've updated. Also depends where you are as with P2Pool you should keep the latency low(ish)...

[DigiByte]

I agree, I think we are getting really close to the point where if we don't push to the new algo soon I feel like we will lose our momentum.  We really need a coordinated mining effort in order to push through to the change over block.

I can push 25 MH/s at it. Which pool do you all recommend?

These Scrypt Pools have updated:

CryptoPool Mining
Coinium

P2P Pools
E-Pool.net
French P2P
P2P SK Pool

[RJF]

I'm all about P2Pool...  so I recommend:

http://limp2pool.fr:9022/static/

It's where I am pointing... it's not my own node, but I've been happy there for a long time.

.... there are other nodes too, just make sure they've updated. Also depends where you are as with P2Pool you should keep the latency low(ish)...

Eastern US

[DigiByte]

Moved to: https://bitcointalk.org/index.php?topic=408268.0

[tdcooper99]

I'm all about P2Pool...  so I recommend:

http://limp2pool.fr:9022/static/

It's where I am pointing... it's not my own node, but I've been happy there for a long time.

.... there are other nodes too, just make sure they've updated. Also depends where you are as with P2Pool you should keep the latency low(ish)...

Eastern US

For the moment it appears the only ones that have updated so far are based in Europe. Might be best to go for a normal pool for now where geography isn't as important.

[DigiByte]

I'm all about P2Pool...  so I recommend:

http://limp2pool.fr:9022/static/

It's where I am pointing... it's not my own node, but I've been happy there for a long time.

.... there are other nodes too, just make sure they've updated. Also depends where you are as with P2Pool you should keep the latency low(ish)...

Eastern US

For the moment it appears the only ones that have updated so far are based in Europe. Might be best to go for a normal pool for now where geography isn't as important.

We are working on getting DigiHash.co online for Scypt mining (will be where we point the ASICs we rent). It will be on a server in Dallas, TX.

[RJF]

I'm all about P2Pool...  so I recommend:

http://limp2pool.fr:9022/static/

It's where I am pointing... it's not my own node, but I've been happy there for a long time.

.... there are other nodes too, just make sure they've updated. Also depends where you are as with P2Pool you should keep the latency low(ish)...

Eastern US

For the moment it appears the only ones that have updated so far are based in Europe. Might be best to go for a normal pool for now where geography isn't as important.

We are working on getting DigiHash.co online for Scypt mining (will be where we point the ASICs we rent). It will be on a server in Dallas, TX.

Cool. If you could announce when that goes live I would appreciate it. Until then I'll latch on to one of the others, thanks!

[24hralttrade]

Retweet: https://twitter.com/Alttrade/status/504358326067822595

[NZ_miner]

This could be a problem ...

I pulled all my hash from the network around block 142,410 ... it then ran ok for the next 12+ hours until block 142,473 where the difficulty has now suddenly jumped to 1,000+ the highest digibyte has ever seen... could be stuck on this block for a long time.

I could probably clear it, but am getting a bit bored throwing away my own money to push the blockchain along ... especially as the Devs have not come forward and explained the cause of the problem. Happy to support them if they come up with a solution and need hashing power, but until then I have retreated to the side lines.

Also, does anyone know of a way to monitor the DGB network hashrate? All the usual sources no longer work since the introduction of the new wallet.

First off, thank you very much for putting your hash toward the network and trying to help us ll get over the hump. We dont expect anyone to mine for days on end with no return. As for the problem we have mentioned it several time over the past couple months.

The problem is not with DigiShield alone as it worked fine until we combined it with the 0.9.1 protocol in April (you can see this on several charts.) DigiShield with the 0.6 Bitcoin protocol works great for several coins still and it still works for Dogecoin. We screwed up and did not do enough testing when we released the 0.9.1 wallet. We figured since no hard fork was required everything with the difficulty adjustment would stay the same.

What basically happens with the 2.9.1 protocol is when a sudden hash spike occurs blocks are sometimes discovered only milliseconds apart. Combine this with a single block average (DigiShield only goes back to the previous block) and you get an astronomically high inflated difficulty.

The next problem is when the hash rate drops and the difficulty eventually drops it drops too low and an oscillating effect occurs & the process repeats itself.

The best way to overcome this is with a steady increase in hash, not a sudden spike. Also, a consistent hash base will be a huge improvement. Starting tomorrow we will begin adding hash to the network and we will publicly post the days target hash-rate. This will help speed things up considerably. We ask if you have some hash to contribute we could definitely use it.

We dont expect people to do this for weeks on end but if we could get a rotation going that would be great.

@Digibyte

Thanks for the response, much appreciated.

I admit I don't have all the answers but if it is the new protocol that is causing the problem then it is a concern that it will rear its head after the wallet passes block 145,000. The explanation you gave is plausible, but NOT the whole story and it doesn't explain what I have been observing, examples:

A. Block 142,272 - 142,273 took over 5 hours to find the block at a difficulty of 1022 ... by your reckoning Digishield would then reduce the difficulty far to much ... but it actually increased to 1300+

B. Whilst pointing several GHs of hash at the network I was finding several groups of consecutive blocks, looking at these I often found two or more blocks in quick succession (seconds apart) but rather than increasing the difficulty as you suggest it actually reduced it for the next blocks.

C. It is true the difficulty is oscillating, but it is also oscillating at far too high a range. It never reduces the difficulty to a point where you would find a block on average every minute (ie the correct difficulty) ... any idea why it fails to retarget to the correct level? Even when there has been very little hash pointing at the network it still oscillates roughly in the range 200-400.

D. By increasing the network hash rate x6 I thought the difficulty may have gone up ... but it actually stayed the same and still oscillated in that same range.

Do you have any idea why the hashrate has jumped to record levels over the last two blocks? I just want to make sure we don't replicate that and get it permanently stuck at an even higher difficulty.

Interesting there are no problems with other coins using Digishield, Doge you might expect as it maintains a consistent very high hashrate ... but I would have thought some other coins may have had similar problems by now. Could it be unique to Digibyte and a stray line of code that is not included in other coins?

Anyway, hopefully this will all be resolved and we can cruise to block 145k in no time.

Happy to help with the hash power if you set a daily target. Is there somewhere we can check the Digibyte Network hashrate? Most of the original sources seem to have 'broken' since the wallet update.

[NZ_miner]

@Digibyte

An idea ...

If I have your permission I can ask Josh (CEO) of gawminers if he will donate the hash power to push us past 145,000.

He has been really supportive of the Altcoin community and I dread to think what scrypt hash power they now control, but it must run into THs. They sold Millions of $ of cloud scrypt power in the last week or so, and still have a large surplus under there control.

Presuming I make a case do we know what we require ... before the latest difficulty spike I calculated that 10GH/s for 1.5 days should do ... any idea if that is in the right area???

[,./,./]

@digibyte

when do you expect the Iphone digibyte-wallet?

[DigiByte]

@Digibyte

An idea ...

If I have your permission I can ask Josh (CEO) of gawminers if he will donate the hash power to push us past 145,000.

He has been really supportive of the Altcoin community and I dread to think what scrypt hash power they now control, but it must run into THs. They sold Millions of $ of cloud scrypt power in the last week or so, and still have a large surplus under there control.

Presuming I make a case do we know what we require ... before the latest difficulty spike I calculated that 10GH/s for 1.5 days should do ... any idea if that is in the right area???

NZ,

We are definitely all for it! Any help to get us past block 145,00 would be much appreciated. It would also be very interesting to see happen. 10 GH should do the trick.