Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 746. (Read 1260706 times)

Quote from: Mister1k on July 31, 2014, 07:11:19 PM

Minep.it is most likely on the wrong chain with difficulty of 9, unless their stats are showing wrong info for some reason.
Danbi's pool is difficulty 58 at the moment.

They have bee informed.

Isn't Cryptohunger associated with srcxxx ... with two pools on wrong fork the prob will take forever to sort itself out ...

And what's the Cryptohunger's address as the one (cryptohunger.com) has nothing to do with Diamond. Not sure why people refer to it.

uh?
http://cryptohunger.com:81/

diamondcoin
18 Miners
699.09 MH
Pool Algo Workers Valid Invalid Total Blocks Pending Confirmed Orphaned Hashrate
diamondcoin groestl 18 7642217 363233 9402 36 8470 850 708.45 MH

popshot

hero member

Activity: 774

Merit: 554

CEO Diamond Foundation

uh?
http://cryptohunger.com:81/

Thanks. Added to the OP.

Mister1k

hero member

Activity: 896

Merit: 520

Quote from: popshot on July 31, 2014, 07:09:58 PM

Minep.it is most likely on the wrong chain with difficulty of 9, unless their stats are showing wrong info for some reason.
Danbi's pool is difficulty 58 at the moment.

They have bee informed.

Isn't Cryptohunger associated with srcxxx ... with two pools on wrong fork the prob will take forever to sort itself out ...

And what's the Cryptohunger's address as the one (cryptohunger.com) has nothing to do with Diamond. Not sure why people refer to it.

uh?
http://cryptohunger.com:81/

popshot

hero member

Activity: 774

Merit: 554

CEO Diamond Foundation

Minep.it is most likely on the wrong chain with difficulty of 9, unless their stats are showing wrong info for some reason.
Danbi's pool is difficulty 58 at the moment.

They have bee informed.

Isn't Cryptohunger associated with srcxxx ... with two pools on wrong fork the prob will take forever to sort itself out ...

And what's the Cryptohunger's address as the one (cryptohunger.com) has nothing to do with Diamond. Not sure why people refer to it.

Mister1k

hero member

Activity: 896

Merit: 520

Minep.it is most likely on the wrong chain with difficulty of 9, unless their stats are showing wrong info for some reason.
Danbi's pool is difficulty 58 at the moment.

They have bee informed.

Isn't Cryptohunger associated with srcxxx ... with two pools on wrong fork the prob will take forever to sort itself out ...

Jesus look at the orphans at cryptohunger. 850... over 10 percent.
8470 confirmed.

utahjohn

hero member

Activity: 630

Merit: 500

Quote from: cryptonit on July 31, 2014, 05:35:16 PM

Minep.it is most likely on the wrong chain with difficulty of 9, unless their stats are showing wrong info for some reason.
Danbi's pool is difficulty 58 at the moment.

They have bee informed.

Isn't Cryptohunger associated with srcxxx ... with two pools on wrong fork the prob will take forever to sort itself out ...

pokeytex

legendary

Activity: 1504

Merit: 1002

Quote

jhed
Newbie
*
Online Online

Activity: 3
Posts: 3

nice try
appear out of nowhere after a attack with 3 post account all at DMD
and try motivate people dont to use the stable point of our network

i would say thats part2 of an attack plan

multiple attacks failed
now try the social one.....

people trust in danbi's suggested solution
we are on same chain as cryptsy
dmd multipool is one same chain

I can attest that Danbi's solution has worked perfectly. I am now on the correct chain. As always thank you Danbi.

pokeytex

popshot

hero member

Activity: 774

Merit: 554

CEO Diamond Foundation

Minep.it is most likely on the wrong chain with difficulty of 9, unless their stats are showing wrong info for some reason.
Danbi's pool is difficulty 58 at the moment.

They have bee informed.

Mister1k

hero member

Activity: 896

Merit: 520

Quote from: jelt14 on July 31, 2014, 06:25:07 PM

Having out of sync problems with my wallet 2.03 ,work great up till today i notice out of sync and not receiving coin whats up? any suggestions>> Huh

Hi Jelt
If you notice at minept no payouts are confirming at the wallet.
I was on Cryptohunger as well last 24 hours and those don't confirm either, at the wallet.
I resynced the wallet via Danbi method on pg117.
0731 block chain.etc changed up the config.
But the 0731 payouts from both those pools won't confirm.
Shows a diff in the low teens at minept and the net hash makes no sense compared to Danbi pool stats.
Right now!
Danbi pool is 30 blocks ahead.

jelt14

full member

Activity: 195

Merit: 100

last block 511883
block hieght 510609

jhed

newbie

Activity: 26

Merit: 0

Quote from: danbi on July 31, 2014, 05:40:42 PM

Quote from: jhed on July 31, 2014, 05:04:46 PM

Quote from: utahjohn on July 31, 2014, 04:53:24 PM

Quote from: jhed on July 31, 2014, 05:04:46 PM

This will guarantee whatever you mine, will never, ever be accepted on the Diamond block chain.

Exactly why I have quit mining until this repeated forking is resolved. LOL good luck with your ORPHANS if you are on wrong blockchain ...
I have closed wallet until this situation if suitably corrected. Using only connect=193.68.21.19 defeats the whole purpose of de-centralized blockchain and if I use addnode=193.68.21.19 I end up on wrong fork again after a couple hours mining Sad

Thus my frustration Huh

utahjohn, I agree. So why are you adding it into your config?

The network decides who has the right chain and who has the wrong one. Since cryptsy just accepted a transaction from me, I'd say I'm on the right chain.

You all should really check your debug.log for "Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING"

I'd advise against deposit/withdraw from Cryptsy until forking issue is resolved. I would guess Cryptsy also on wrong fork as the difficulty before these problems started showing up was in the 60-110 range and thus had highest hashrate versus the 7-15 I see when I think I'm on wrong fork.

Difficulty and connection count is going up over here on the network-accepted chain:

Code:

> date
Thu Jul 31 22:03:35 GMT 2014
jhed@omnom-tower:~> diamondd getinfo
{
    "version" : "v2.0.3.0",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "blocks" : 512114,
    "moneysupply" : 517784.82106200,
    "connections" : 16,
    "proxy" : "",
    "difficulty" : 18.93459497,
    "testnet" : false,
    "paytxfee" : 0.00100000,
    "errors" : ""
}

You could not be father from the truth. Here is what 193.68.21.19 has to say:

$ date; diamondd getinfo; diamondd getcheckpoint
Fri Aug 1 01:36:01 EEST 2014
{
   "version" : "v2.0.3.0",
   "protocolversion" : 60006,
   "walletversion" : 60000,
   "blocks" : 512169,
   "moneysupply" : 517865.10032700,
   "connections" : 49,
   "proxy" : "",
   "ip" : "193.68.21.19",
   "difficulty" : 40.94398102,
   "testnet" : false,
   "keypoololdest" : 1406761189,
   "keypoolsize" : 101,
   "paytxfee" : 0.00100000,
   "errors" : ""
}
{
   "synccheckpoint" : "00000000039a61acbc4b0533889b217aca1c89eca708927ce06007a8b7bdd316",
   "height" : 512169,
   "timestamp" : "2014-07-31 22:35:02 UTC"
}

Obviously you are on a shorter block chain. We are 30 minutes, but about 55 blocks apart.
What is your last check point?

Hint: at least, you need to generate 25 more blocks in a fast pace. Then, there are some more obstacles.

If you all are actually able to transmit money into Cryptsy than you are on the correct chain. If I was able to from this chain, than I'm on the correct chain. Crypsty couldn't possibly be connected to both chains. Isn't that right?

jelt14

full member

Activity: 195

Merit: 100

Having out of sync problems with my wallet 2.03 ,work great up till today i notice out of sync and not receiving coin whats up? any suggestions>> Huh

utahjohn

hero member

Activity: 630

Merit: 500

Doing a clean re-sync from genesis, by the time that finishes tomorrow hopefully the blockchain will have sorted itself out ...

danbi

sr. member

Activity: 393

Merit: 250

Quote from: utahjohn on July 31, 2014, 04:53:24 PM

Quote from: utahjohn on July 31, 2014, 04:53:24 PM

This will guarantee whatever you mine, will never, ever be accepted on the Diamond block chain.

Exactly why I have quit mining until this repeated forking is resolved. LOL good luck with your ORPHANS if you are on wrong blockchain ...
I have closed wallet until this situation if suitably corrected. Using only connect=193.68.21.19 defeats the whole purpose of de-centralized blockchain and if I use addnode=193.68.21.19 I end up on wrong fork again after a couple hours mining Sad

Thus my frustration Huh

utahjohn, I agree. So why are you adding it into your config?

The network decides who has the right chain and who has the wrong one. Since cryptsy just accepted a transaction from me, I'd say I'm on the right chain.

You all should really check your debug.log for "Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING"

I'd advise against deposit/withdraw from Cryptsy until forking issue is resolved. I would guess Cryptsy also on wrong fork as the difficulty before these problems started showing up was in the 60-110 range and thus had highest hashrate versus the 7-15 I see when I think I'm on wrong fork.

Difficulty and connection count is going up over here on the network-accepted chain:

Code:

> date
Thu Jul 31 22:03:35 GMT 2014
jhed@omnom-tower:~> diamondd getinfo
{
    "version" : "v2.0.3.0",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "blocks" : 512114,
    "moneysupply" : 517784.82106200,
    "connections" : 16,
    "proxy" : "",
    "difficulty" : 18.93459497,
    "testnet" : false,
    "paytxfee" : 0.00100000,
    "errors" : ""
}

You could not be father from the truth. Here is what 193.68.21.19 has to say:

$ date; diamondd getinfo; diamondd getcheckpoint
Fri Aug 1 01:36:01 EEST 2014
{
   "version" : "v2.0.3.0",
   "protocolversion" : 60006,
   "walletversion" : 60000,
   "blocks" : 512169,
   "moneysupply" : 517865.10032700,
   "connections" : 49,
   "proxy" : "",
   "ip" : "193.68.21.19",
   "difficulty" : 40.94398102,
   "testnet" : false,
   "keypoololdest" : 1406761189,
   "keypoolsize" : 101,
   "paytxfee" : 0.00100000,
   "errors" : ""
}
{
   "synccheckpoint" : "00000000039a61acbc4b0533889b217aca1c89eca708927ce06007a8b7bdd316",
   "height" : 512169,
   "timestamp" : "2014-07-31 22:35:02 UTC"
}

Obviously you are on a shorter block chain. We are 30 minutes, but about 55 blocks apart.
What is your last check point?

Hint: at least, you need to generate 25 more blocks in a fast pace. Then, there are some more obstacles.

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote

jhed
Newbie
*
Online Online

Activity: 3
Posts: 3

nice try
appear out of nowhere after a attack with 3 post account all at DMD
and try motivate people dont to use the stable point of our network

i would say thats part2 of an attack plan

multiple attacks failed
now try the social one.....

people trust in danbi's suggested solution
we are on same chain as cryptsy
dmd multipool is one same chain

jhed

newbie

Activity: 26

Merit: 0

This will guarantee whatever you mine, will never, ever be accepted on the Diamond block chain.

Exactly why I have quit mining until this repeated forking is resolved. LOL good luck with your ORPHANS if you are on wrong blockchain ...
I have closed wallet until this situation if suitably corrected. Using only connect=193.68.21.19 defeats the whole purpose of de-centralized blockchain and if I use addnode=193.68.21.19 I end up on wrong fork again after a couple hours mining Sad

Thus my frustration Huh

utahjohn, I agree. So why are you adding it into your config?

The network decides who has the right chain and who has the wrong one. Since cryptsy just accepted a transaction from me, I'd say I'm on the right chain.

You all should really check your debug.log for "Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING"

I'd advise against deposit/withdraw from Cryptsy until forking issue is resolved. I would guess Cryptsy also on wrong fork as the difficulty before these problems started showing up was in the 60-110 range and thus had highest hashrate versus the 7-15 I see when I think I'm on wrong fork.

Difficulty and connection count is going up over here on the network-accepted chain:

Code:

> date
Thu Jul 31 22:03:35 GMT 2014
jhed@omnom-tower:~> diamondd getinfo
{
    "version" : "v2.0.3.0",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "blocks" : 512114,
    "moneysupply" : 517784.82106200,
    "connections" : 16,
    "proxy" : "",
    "difficulty" : 18.93459497,
    "testnet" : false,
    "paytxfee" : 0.00100000,
    "errors" : ""
}

utahjohn

hero member

Activity: 630

Merit: 500

This will guarantee whatever you mine, will never, ever be accepted on the Diamond block chain.

Exactly why I have quit mining until this repeated forking is resolved. LOL good luck with your ORPHANS if you are on wrong blockchain ...
I have closed wallet until this situation if suitably corrected. Using only connect=193.68.21.19 defeats the whole purpose of de-centralized blockchain and if I use addnode=193.68.21.19 I end up on wrong fork again after a couple hours mining Sad

Thus my frustration Huh

utahjohn, I agree. So why are you adding it into your config?

The network decides who has the right chain and who has the wrong one. Since cryptsy just accepted a transaction from me, I'd say I'm on the right chain.

You all should really check your debug.log for "Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING"

I'd advise against deposit/withdraw from Cryptsy until forking issue is resolved. I would guess Cryptsy also on wrong fork as the difficulty before these problems started showing up was in the 60-110 range and thus had highest hashrate versus the 7-15 I see when I think I'm on wrong fork.

jhed

newbie

Activity: 26

Merit: 0

This will guarantee whatever you mine, will never, ever be accepted on the Diamond block chain.

Exactly why I have quit mining until this repeated forking is resolved. LOL good luck with your ORPHANS if you are on wrong blockchain ...
I have closed wallet until this situation if suitably corrected. Using only connect=193.68.21.19 defeats the whole purpose of de-centralized blockchain and if I use addnode=193.68.21.19 I end up on wrong fork again after a couple hours mining Sad

Thus my frustration Huh

utahjohn, I agree. So why are you adding it into your config?

The network decides who has the right chain and who has the wrong one. Since cryptsy just accepted a transaction from me, I'd say I'm on the right chain.

You all should really check your debug.log for "Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING"

utahjohn

hero member

Activity: 630

Merit: 500