[ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65%

[utahjohn]

LOL.. stuck on 577851. It won't sync. as I suspected. 540 blocks behind and counting.
Fresh database before 577851 is useless.

use connect= to the 4 official addnodes and listen=0, resysnc from last provided dmdchain on OP.  I'm on correct blockchain
u can use connect=67.2.108.164 to get on my chain I'm finding blocks and getting them validated


04:16:15

getcheckpoint


04:16:15

{
"synccheckpoint" : "00000000012af5820ca68a7b5bedb53bde05f75d943443319b462cd1bf3fc615",
"height" : 578426,
"timestamp" : "2014-09-28 10:15:36 UTC"
}

04:16:22

getinfo


04:16:22

{
"version" : "v2.0.4.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : 887.68248400,
"newmint" : 2.00000000,
"stake" : 0.00000000,
"blocks" : 578426,
"moneysupply" : 598228.04978600,
"connections" : 4,
"proxy" : "",
"ip" : "67.2.108.164",
"difficulty" : 82.96020848,
"testnet" : false,
"keypoololdest" : 1404277506,
"keypoolsize" : 102,
"paytxfee" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""
}

Single R9 280X catalyst 14.7 RC3

sgminer 4.1.0 - Started: [2014-09-28 04:02:40]
--------------------------------------------------------------------------------
(5s):18.41M (avg):17.94Mh/s | A:67  R:0  HW:0  WU:0.450/m
ST: 1  SS: 0  NB: 18  LW: 0  GF: 0  RF: 0
Connected to Pool 0 (longpoll) diff 85 as user bogususer
Block: c184229f...  Diff:85  Started: [04:19:43]  Best share: 157
--------------------------------------------------------------------------------
[P]ool management [G]PU management ettings [D]isplay options [Q]uit
 GPU 0:  70.0C 3551RPM | 17.92M/17.94Mh/s | R:  0.0% HW:0 WU:0.450/m I:22
--------------------------------------------------------------------------------
[04:13:28] Network diff set to 72
[04:13:28] New block detected on network
[04:13:52] Network diff set to 75
[04:13:52] New block detected on network
[04:14:16] Network diff set to 79
[04:14:16] New block detected on network
[04:14:36] Network diff set to 82
[04:14:36] New block detected on network
[04:15:53] Network diff set to 81
[04:15:53] New block detected on network
[04:17:07] Network diff set to 80
[04:17:07] New block detected on network
[04:19:43] Network diff set to 85
[04:19:43] New block detected on network

[1714131363]

1714131363

[1714131363]

1714131363

[1714131363]

1714131363

[danbi]

Good to see it works. Not that I had a sleepless night. Ok, I did, but for very different reasons 

[Mister1k]

LOL.. stuck on 577851. It won't sync. as I suspected. 540 blocks behind and counting.
Fresh database before 577851 is useless.

use connect= to the 4 official addnodes and listen=0, resysnc from last provided dmdchain on OP.  I'm on correct blockchain
u can use connect=67.2.108.164 to get on my chain I'm finding blocks and getting them validated


04:16:15

getcheckpoint


04:16:15

{
"synccheckpoint" : "00000000012af5820ca68a7b5bedb53bde05f75d943443319b462cd1bf3fc615",
"height" : 578426,
"timestamp" : "2014-09-28 10:15:36 UTC"
}

04:16:22

getinfo


04:16:22

{
"version" : "v2.0.4.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : 887.68248400,
"newmint" : 2.00000000,
"stake" : 0.00000000,
"blocks" : 578426,
"moneysupply" : 598228.04978600,
"connections" : 4,
"proxy" : "",
"ip" : "67.2.108.164",
"difficulty" : 82.96020848,
"testnet" : false,
"keypoololdest" : 1404277506,
"keypoolsize" : 102,
"paytxfee" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""
}

Single R9 280X catalyst 14.7 RC3

sgminer 4.1.0 - Started: [2014-09-28 04:02:40]
--------------------------------------------------------------------------------
(5s):18.41M (avg):17.94Mh/s | A:67  R:0  HW:0  WU:0.450/m
ST: 1  SS: 0  NB: 18  LW: 0  GF: 0  RF: 0
Connected to Pool 0 (longpoll) diff 85 as user bogususer
Block: c184229f...  Diff:85  Started: [04:19:43]  Best share: 157
--------------------------------------------------------------------------------
[P]ool management [G]PU management ettings [D]isplay options [Q]uit
 GPU 0:  70.0C 3551RPM | 17.92M/17.94Mh/s | R:  0.0% HW:0 WU:0.450/m I:22
--------------------------------------------------------------------------------
[04:13:28] Network diff set to 72
[04:13:28] New block detected on network
[04:13:52] Network diff set to 75
[04:13:52] New block detected on network
[04:14:16] Network diff set to 79
[04:14:16] New block detected on network
[04:14:36] Network diff set to 82
[04:14:36] New block detected on network
[04:15:53] Network diff set to 81
[04:15:53] New block detected on network
[04:17:07] Network diff set to 80
[04:17:07] New block detected on network
[04:19:43] Network diff set to 85
[04:19:43] New block detected on network

thankx for the idea. but its a no go. Its locked on 577851 no matter how many nodes.etc
Three times I've tried

I need a database after 577851.


07:08:30

getcheckpoint


07:08:30

{
"synccheckpoint" : "e5c190cd7bd9a825036cc8c41f5d027f2195b678d10308096bdd2d9b19201b8d",
"height" : 577189,
"timestamp" : "2014-09-20 22:26:06 UTC"
}

[cryptonit]

LOL.. stuck on 577851. It won't sync. as I suspected. 540 blocks behind and counting.
Fresh database before 577851 is useless.

mister1k u always have troubles and later on we discover u didnt follow the steps

so tell us first what u have done exact then we can give u answers

wallet version
what blockchain u did download  and so on....

if u go with
the stuff linked at first ANN page u cant end as u describe

[Reggie0]

tryed another withdraw from cryptsy still working

but deposit is not working.

[paladin281978]

[Mister1k]

LOL.. stuck on 577851. It won't sync. as I suspected. 540 blocks behind and counting.
Fresh database before 577851 is useless.

mister1k u always have troubles and later on we discover u didnt follow the steps

so tell us first what u have done exact then we can give u answers

wallet version
what blockchain u did download  and so on....

if u go with
the stuff linked at first ANN page u cant end as u describe

I have went as instructed since the fork issue.
config as posted
rpcuser=
rpcpassword=
logtimestamps=1
listen=0
daemon=1
server=1
noirc=1
rpcport=17772
rpcallowip=127.0.0.1
rpcconnect=127.0.0.1
connect=193.68.21.19
connect=54.191.208.14
connect=54.255.133.30
connect=54.86.164.216
bantime=600
maxconnections=50
#genproclimit=10
# to disable PoS
#reservebalance=9999999
# for more logging
#debug=1
#printcoinage=1
#printcreation=1
#printpriority=1
#printstakemodifier=1
#printcoinstake=1
#printfee=1
#printjunk=1

latest version of wallet since introduction the other day 2.0.4.0
latest block chain Sept 21 2014.
It starts, loads addresses syncs up fast to 577851.
Then stalls and hangs at 577851.
The Green progress bar
counts the remaining blocks and they are going up.
I tried backup wallet.dats, to no avail.
The wallet was fine yesterday it synced up. I was minting and got back nothing.
I shutdown and waited for 577850 to come around to start mining.
Start up this morning. and it hangs at 577851.
I tried three times to resync. Runs up to 577851 and hangs.
689 blocks remaining. 4 active connections. etc
I tried utahjohn suggestion and the same. 577851.
That's it That's all.

I just tried the 07/31 database
65000 blocks behind. It ran right up to 577851.
and Hangs 746 blocks behind.
 

[Reggie0]

LOL.. stuck on 577851. It won't sync. as I suspected. 540 blocks behind and counting.
Fresh database before 577851 is useless.

mister1k u always have troubles and later on we discover u didnt follow the steps

so tell us first what u have done exact then we can give u answers

wallet version
what blockchain u did download  and so on....

if u go with
the stuff linked at first ANN page u cant end as u describe

I have went as instructed since the fork issue.
config as posted
rpcuser=
rpcpassword=
logtimestamps=1
listen=0
daemon=1
server=1
noirc=1
rpcport=17772
rpcallowip=127.0.0.1
rpcconnect=127.0.0.1
connect=193.68.21.19
connect=54.191.208.14
connect=54.255.133.30
connect=54.86.164.216
bantime=600
maxconnections=50
#genproclimit=10
# to disable PoS
#reservebalance=9999999
# for more logging
#debug=1
#printcoinage=1
#printcreation=1
#printpriority=1
#printstakemodifier=1
#printcoinstake=1
#printfee=1
#printjunk=1

latest version of wallet since introduction the other day 2.0.4.0
latest block chain Sept 21 2014.
It starts, loads addresses syncs up fast to 577851.
Then stalls and hangs at 577851.
The Green progress bar
counts the remaining blocks and they are going up.
I tried backup wallet.dats, to no avail.
The wallet was fine yesterday it synced up. I was minting and got back nothing.
I shutdown and waited for 577850 to come around to start mining.
Start up this morning. and it hangs at 577851.
I tried three times to resync. Runs up to 577851 and hangs.
689 blocks remaining. 4 active connections. etc
I tried utahjohn suggestion and the same. 577851.
Thats it Thats all.
  
 

I have same problem, but I use an older database. No i'm trying maxconnections=1, connect=193.68.21.19, addnode=193.68.21.19

[stillontop]

I am having the same problem, wallet 2.0.4.0, latest Blockchain from mega, settings from the first page, sync. stuck at block 577851.

[paladin281978]

stillontop

Sometimes helps reboot the wallet
or try download latest clean block chain

[Henle]

Damn.  Pretty sure I'm forked.  I have 4 connections (8 a minute ago), so I'm not alone.  I'm using version 2.0.4, and I was fine up until last night.  I solo mined about 600 diamond last night.  What a shame they're not real.

Guess I'll re-download the blockchain.  Again.  I thought this wasn't supposed to happen any more.

[Reggie0]

I've solved my problem. There was an application on quicklanch bar, not link...

[Mister1k]

stillontop

Sometimes helps reboot the wallet
or try download latest clean block chain

I just tried the Sept 23 database. This time it went to 577849 and hangs.
1 active connection
connect=193.68.21.19
and it lost that connection for a second or two.
two tv screens instead of strength bar.
debug log shows 577851

[Henle]

I am having the same issue as Mister1K, but I make it to block 577851 and then it hangs. 

I tried using Sep.21.2014.Diamond.zip from the op, and I tried dmdchain20140923-clean.zip.

I tried using -repairwallet.  I tried -checkblock=0 -checklevel=6 from the readme in dmdchain20140923-clean.zip.  I even tried using an old copy of the wallet to make sure the wallet wasn't corrupted.  Same results every time.

diamond.conf:
server=1
rpcuser=xxx
rpcpassword=xxx
rpcport=17772
listen=1
noirc=1
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
connect=193.68.21.19
connect=54.191.208.14
connect=54.255.133.30
connect=54.86.164.216
bantime=600
rpcallowip=127.0.0.1
rpcallowip=192.168.1.5
rpcallowip=192.168.1.6
rpcallowip=192.168.1.7
rpcallowip=192.168.1.14
rpcallowip=192.168.1.129
rpcallowip=192.168.1.*

Every time I end up with one connection to 193.68.21.19 and an on again/off again connection to 193.68.21.19:17772.

Some help would be appreciated.  Thanks.

[cryptonit]

download wallet 2.0.4 again
there was a few hours a wrong file linked maybe u did get that one
(and make sure u throw away old one)

[hallared]

Cryptsys answer on support ticket regarding DMD wallet maintenance:

Thank you for contacting Cryptsy.

We deeply apologize on the delay and for any issues that may have arisen due to this.
DMD coin wallet is still under maintenance and will try our best to have it back soon.
Our technical support team is currently working on this to upgrade and do whatever is necessary to keep these issues from happening again.

I apologize there is no estimated time given from our tech support. All transactions will be posted in order once wallet is up.

Sorry for the delay and thank you kindly for your patience. Will keep you posted as soon as its back online.

Thank you kindly for your patience.
 
Sincerely,
Michelle
Cryptsy.com

[cryptonit]

im trying to find out why cryptsy have DMD wallet in maintainance mode
maybe they resync even if it wasnt required?
no reply until yet

@hallared its a defaulttext answer for any coin under maintainance

[Mister1k]

download wallet 2.0.4 again
there was a few hours a wrong file linked maybe u did get that one
(and make sure u throw away old one)

That was it. Re downloaded wallet.  Synced
Sept 21 block chain.
Good to go. Thank you

[stillontop]

Redownloading windows wallet solved the issue. imho it would have been better to release a version 2.0.4.1, that would have kept things clearly.

[cryptonit]

Redownloading windows wallet solved the issue. imho it would have been better to release a version 2.0.4.1, that would have kept things clearly.

thx for confirming
agree we will use last version digit in future for that