Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1346. (Read 3058812 times)

Quote from: hardcoreprime on June 10, 2014, 08:31:32 PM

Everything is fine.
If you have problems with the Mac wallet, a good alternative would be to run the windows wallet in a virtualbox.

that's fine to say if have you windows.

I see here that the last block was:134145:http://explorer.cryptopoolmining.com/chain/DigiByte

Took just 3 minutes under 6 hours to find the next block. Yes, you read that right, 6 hours for all intents and purposes!

If anyone is wondering why no-one is mining DGB, that's your answer right there. You need go no further, need think no longer.

And that was after an 83.185 diff that had already "adjusted" down from a previous 124.777 diff on the previous block just 4 minutes before 124145.

Oh, how I'd like to know what's causing this and why the only coins I've found with similar issues are coins using DigiShield.

Been on BlazingHashes for while now, same 13k coins sitting unconfirmed and nothing new. This is a problem. Not complaining, just reporting...

    Gen Est. Found Valid Orphan Avg Diff   Shares Est.   Shares   Percentage   Amount   Rate Est.
Last Hour    60    0   0   0    0   0   0    0.00%   0   0.00%
Last 24 Hours   1440    0   0   0    0   0   0    0.00%   0   0.00%

Sorry but, going to have to pull the rig at some point if things don't improve.

We are working around the clock right now and will probably be up all night right now. We could use all the hash we can get for another 48 hours. We need to get everything stabilized.

Its because of this, the work, the dedication and the enthusiasm of the Digibyte team that i will continue to invest in their coin.

I'll second that and throw in another 6 MH/s tonight. Thank you for you dedication!

If had MH to throw out, I would.
This will clear up soon, to all the people panicking.

RJF

hero member

Activity: 616

Merit: 500

Online since '89...

Quote from: DigiByte on June 10, 2014, 08:23:29 PM

Quote from: DigiByte on June 10, 2014, 08:23:29 PM

Everything is fine.
If you have problems with the Mac wallet, a good alternative would be to run the windows wallet in a virtualbox.

that's fine to say if have you windows.

I see here that the last block was:134145:http://explorer.cryptopoolmining.com/chain/DigiByte

Took just 3 minutes under 6 hours to find the next block. Yes, you read that right, 6 hours for all intents and purposes!

If anyone is wondering why no-one is mining DGB, that's your answer right there. You need go no further, need think no longer.

And that was after an 83.185 diff that had already "adjusted" down from a previous 124.777 diff on the previous block just 4 minutes before 124145.

Oh, how I'd like to know what's causing this and why the only coins I've found with similar issues are coins using DigiShield.

Been on BlazingHashes for while now, same 13k coins sitting unconfirmed and nothing new. This is a problem. Not complaining, just reporting...

    Gen Est. Found Valid Orphan Avg Diff   Shares Est.   Shares   Percentage   Amount   Rate Est.
Last Hour    60    0   0   0    0   0   0    0.00%   0   0.00%
Last 24 Hours   1440    0   0   0    0   0   0    0.00%   0   0.00%

Sorry but, going to have to pull the rig at some point if things don't improve.

We are working around the clock right now and will probably be up all night right now. We could use all the hash we can get for another 48 hours. We need to get everything stabilized.

Its because of this, the work, the dedication and the enthusiasm of the Digibyte team that i will continue to invest in their coin.

I'll second that and throw in another 6 MH/s tonight. Thank you for you dedication!

hardcoreprime

full member

Activity: 147

Merit: 100

Everything is fine.
If you have problems with the Mac wallet, a good alternative would be to run the windows wallet in a virtualbox.

that's fine to say if have you windows.

I see here that the last block was:134145:http://explorer.cryptopoolmining.com/chain/DigiByte

Took just 3 minutes under 6 hours to find the next block. Yes, you read that right, 6 hours for all intents and purposes!

If anyone is wondering why no-one is mining DGB, that's your answer right there. You need go no further, need think no longer.

And that was after an 83.185 diff that had already "adjusted" down from a previous 124.777 diff on the previous block just 4 minutes before 124145.

Oh, how I'd like to know what's causing this and why the only coins I've found with similar issues are coins using DigiShield.

Been on BlazingHashes for while now, same 13k coins sitting unconfirmed and nothing new. This is a problem. Not complaining, just reporting...

    Gen Est. Found Valid Orphan Avg Diff   Shares Est.   Shares   Percentage   Amount   Rate Est.
Last Hour    60    0   0   0    0   0   0    0.00%   0   0.00%
Last 24 Hours   1440    0   0   0    0   0   0    0.00%   0   0.00%

Sorry but, going to have to pull the rig at some point if things don't improve.

We are working around the clock right now and will probably be up all night right now. We could use all the hash we can get for another 48 hours. We need to get everything stabilized.

Its because of this, the work, the dedication and the enthusiasm of the Digibyte team that i will continue to invest in their coin.

DigiByte

legendary

Activity: 1722

Merit: 1051

Official DigiByte Account

Everything is fine.
If you have problems with the Mac wallet, a good alternative would be to run the windows wallet in a virtualbox.

that's fine to say if have you windows.

I see here that the last block was:134145:http://explorer.cryptopoolmining.com/chain/DigiByte

Took just 3 minutes under 6 hours to find the next block. Yes, you read that right, 6 hours for all intents and purposes!

If anyone is wondering why no-one is mining DGB, that's your answer right there. You need go no further, need think no longer.

And that was after an 83.185 diff that had already "adjusted" down from a previous 124.777 diff on the previous block just 4 minutes before 124145.

Oh, how I'd like to know what's causing this and why the only coins I've found with similar issues are coins using DigiShield.

Been on BlazingHashes for while now, same 13k coins sitting unconfirmed and nothing new. This is a problem. Not complaining, just reporting...

    Gen Est. Found Valid Orphan Avg Diff   Shares Est.   Shares   Percentage   Amount   Rate Est.
Last Hour    60    0   0   0    0   0   0    0.00%   0   0.00%
Last 24 Hours   1440    0   0   0    0   0   0    0.00%   0   0.00%

Sorry but, going to have to pull the rig at some point if things don't improve.

We are working around the clock right now and will probably be up all night right now. We could use all the hash we can get for another 48 hours. We need to get everything stabilized.

RJF

hero member

Activity: 616

Merit: 500

Online since '89...

Everything is fine.
If you have problems with the Mac wallet, a good alternative would be to run the windows wallet in a virtualbox.

that's fine to say if have you windows.

I see here that the last block was:134145:http://explorer.cryptopoolmining.com/chain/DigiByte

Took just 3 minutes under 6 hours to find the next block. Yes, you read that right, 6 hours for all intents and purposes!

If anyone is wondering why no-one is mining DGB, that's your answer right there. You need go no further, need think no longer.

And that was after an 83.185 diff that had already "adjusted" down from a previous 124.777 diff on the previous block just 4 minutes before 124145.

Oh, how I'd like to know what's causing this and why the only coins I've found with similar issues are coins using DigiShield.

Been on BlazingHashes for while now, same 13k coins sitting unconfirmed and nothing new. This is a problem. Not complaining, just reporting...

    Gen Est. Found Valid Orphan Avg Diff   Shares Est.   Shares   Percentage   Amount   Rate Est.
Last Hour    60    0   0   0    0   0   0    0.00%   0   0.00%
Last 24 Hours   1440    0   0   0    0   0   0    0.00%   0   0.00%

Sorry but, going to have to pull the rig at some point if things don't improve.

DigiByte

legendary

Activity: 1722

Merit: 1051

Official DigiByte Account

Everything is fine.
If you have problems with the Mac wallet, a good alternative would be to run the windows wallet in a virtualbox.

that's fine to say if have you windows...

I see here that the last block was:134145:http://explorer.cryptopoolmining.com/chain/DigiByte

Took just 3 minutes under 6 hours to find the next block. Yes, you read that right, 6 hours for all intents and purposes!

If anyone is wondering why no-one is mining DGB, that's your answer right there. You need go no further, need think no longer.

And that was after an 83.185 diff that had already "adjusted" down from a previous 124.777 diff on the previous block just 4 minutes before 124145.

Oh, how I'd like to know what's causing this and why the only coins I've found with similar issues are coins using DigiShield.

Before the 0.9.1 upgrade things were working as expected. If you look at the chart dates it all adds up. Todays block delay was do to a massive drop in hash combined with DigiShield & 0.9.1 reacting to several blocks found quickly in a row.

If this were other coins like Litecoin or Bitcoin and the same thing happened it could be weeks between blocks.

We are working as fast as we can on the multi-algo implementation and difficulty re-targeting adjustment.

It also appears some multi-pools may be attempting some sort of timing attack. This combined with a very low hash is creating some issues to overcome.

We are still in this for the long term. This is a bump along the way. In the mean time the block chain is still working. We will get through this. Please be patient. And if anyone would like to help coding in a solution, we could use all the help we can get to speed the process up.

HR

legendary

Activity: 1176

Merit: 1011

Transparency & Integrity