Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 746. (Read 1260636 times)
July 31, 2014, 07:20:24 PM
Thanks. Added to the OP.
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 ...Danbi's pool is difficulty 58 at the moment.
They have bee informed.
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.
http://cryptohunger.com:81/
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 ...Danbi's pool is difficulty 58 at the moment.
They have bee informed.
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.
July 31, 2014, 07:07:54 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 ...Danbi's pool is difficulty 58 at the moment.
They have bee informed.
8470 confirmed.
July 31, 2014, 06:58:15 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 ... Danbi's pool is difficulty 58 at the moment.
They have bee informed.
July 31, 2014, 06:58:10 PM
Quote
jhed
Newbie
*
Online Online
Activity: 3
Posts: 3
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
July 31, 2014, 06:53:56 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.
Danbi's pool is difficulty 58 at the moment.
They have bee informed.
July 31, 2014, 06:36:57 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>> 
Hi JeltIf 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.
July 31, 2014, 06:34:09 PM
last block 511883
block hieght 510609
block hieght 510609
July 31, 2014, 06:26:03 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
Thus my frustration 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"
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?
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>>
July 31, 2014, 06:01:10 PM
Doing a clean re-sync from genesis, by the time that finishes tomorrow hopefully the blockchain will have sorted itself out ...
July 31, 2014, 05:40:42 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
Thus my frustration 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"
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.
July 31, 2014, 05:35:16 PM
Quote
jhed
Newbie
*
Online Online
Activity: 3
Posts: 3
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
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
Thus my frustration 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"
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" : ""
}
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
Thus my frustration 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"
July 31, 2014, 04:47:14 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
Thus my frustration 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"
July 31, 2014, 04:40:50 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
Thus my frustration July 31, 2014, 04:22:52 PM
Still having blockchain problems ... re-indexed from beginning and diff was 35-45 for several hours and then dropped to 9. This is frustrating
yep that what’s happened to me again
If anybody is consistently getting on the wrong block chain, you might consider that 193.68.21.19 actually has the wrong block chain. Check your debug.log to see if you have what I found in mine:
Code:
received block 000000000310f60b9126
ProcessBlock: ORPHAN BLOCK, prev=000000000302b0af011c
received block 000000000302b0af011c
ProcessBlock: ORPHAN BLOCK, prev=0000000004e6b27a0790
received block 0000000000d652bceaa2
connection timeout
ProcessBlock: ACCEPTED
received block 00000000078b6cf20c99
Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING
disconnecting node 193.68.21.19:17771
ERROR: ProcessBlock() : block with too little proof-of-work
I am successfully solo mining right now. Here is getinfo from my diamondd:
Code:
> date
Thu Jul 31 20:20:45 GMT 2014
> diamondd getinfo
{
"version" : "v2.0.3.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"blocks" : 512014,
"moneysupply" : 517671.38180200,
"connections" : 8,
"proxy" : "",
"difficulty" : 13.98245459,
"paytxfee" : 0.00100000,
}
Code:
> date
Thu Jul 31 21:00:31 GMT 2014
> diamondd getinfo
{
"version" : "v2.0.3.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"blocks" : 512050,
"moneysupply" : 517709.18180200,
"connections" : 11,
"difficulty" : 10.46732144,
"paytxfee" : 0.00100000,
}
Try nuking 193.68.21.19 from your configs and deleting your peers.dat to reset it.
This will guarantee whatever you mine, will never, ever be accepted on the Diamond block chain.
But, if you enjoy mining at low difficulty, alone, it's a good method. :-)
July 31, 2014, 04:14:25 PM
Still having blockchain problems ... re-indexed from beginning and diff was 35-45 for several hours and then dropped to 9. This is frustrating
yep that what’s happened to me again
If anybody is consistently getting on the wrong block chain, you might consider that 193.68.21.19 actually has the wrong block chain. Check your debug.log to see if you have what I found in mine:
Code:
received block 000000000310f60b9126
ProcessBlock: ORPHAN BLOCK, prev=000000000302b0af011c
received block 000000000302b0af011c
ProcessBlock: ORPHAN BLOCK, prev=0000000004e6b27a0790
received block 0000000000d652bceaa2
connection timeout
ProcessBlock: ACCEPTED
received block 00000000078b6cf20c99
Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING
disconnecting node 193.68.21.19:17771
ERROR: ProcessBlock() : block with too little proof-of-work
I am successfully solo mining right now. Here is getinfo from my diamondd:
Code:
> date
Thu Jul 31 20:20:45 GMT 2014
> diamondd getinfo
{
"version" : "v2.0.3.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"blocks" : 512014,
"moneysupply" : 517671.38180200,
"connections" : 8,
"proxy" : "",
"difficulty" : 13.98245459,
"paytxfee" : 0.00100000,
}
Code:
> date
Thu Jul 31 21:00:31 GMT 2014
> diamondd getinfo
{
"version" : "v2.0.3.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"blocks" : 512050,
"moneysupply" : 517709.18180200,
"connections" : 11,
"difficulty" : 10.46732144,
"paytxfee" : 0.00100000,
}
Try nuking 193.68.21.19 from your configs and deleting your peers.dat to reset it.
Jump to: