Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 789. (Read 1260636 times)
June 27, 2014, 05:24:33 AM
It seems when you close the wallet damaged what the files in a chain of blocks. So you need to re-update the database. A similar bug has already been before, but apparently it until the end has not been eliminated..
June 27, 2014, 05:17:09 AM
It seems that the network has stabilized, but every time after closing the wallet, have to update all database blocks (restart without it is impossible).
appears the same error
appears the same error
the same problem
June 27, 2014, 05:13:52 AM
utahjohn
I hope that they are now engaged in this..
I hope that they are now engaged in this..
June 27, 2014, 04:53:28 AM
It seems that the network has stabilized, but every time after closing the wallet, have to update all database blocks (restart without it is impossible).
appears the same error
Well F*%$K My wallet is closed at moment ...Another re-index! Devs need to get new wallet out ASAP!appears the same error
So much for unattended restart of solo mining in event of power failure ...
June 27, 2014, 04:42:24 AM
It seems that the network has stabilized, but every time after closing the wallet, have to update all database blocks (restart without it is impossible).
appears the same error
appears the same error
June 27, 2014, 12:17:14 AM
I can't tell you how many dozens of mint transactions I got that were all stale, but after almost six hours of chaos I noticed something....I started minting (successfully).
Here's what I did.....
Nothing.
I was at work while the whole fiacso was going on, so I could do nothing and did not have a chance to try any of the items posted so far before I came home and saw...sweetness. Seven minted blocks with beautiful green check marks next to them (okay, two had clocks with many confirmations...all above a whole bunch of red question marks).
And I still haven't done anything yet.
It appears that I eventually ended up on the correct chain. The checkpoint seems to be in order. It matches the checkpoint posted earlier:
{
"synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
"height" : 463183,
"timestamp" : "2014-06-26 16:46:41 UTC"
}
I might re-start later with some of the posted suggestions (backing up my current AppData first), and we'll see what happens. But for now.....
... 
... 
... 
June 26, 2014, 11:25:48 PM
I do not understand, I have a lot of transactions which are more than 7 days, but POS is not working.
only once has come to 3 DMD, but they are the type of Mint and 0 confirmations. Why other transactions don't give POS?
June 26, 2014, 11:24:15 PM
I do not understand, I have a lot of transactions which are more than 7 days, but POS is not working.
only once has come to 3 DMD, but they are the type of Mint and 0 confirmations. Why other transactions don't give POS?
I'm on the right chain.
June 26, 2014, 11:14:32 PM
Can someone please post the quickest method to re-sync?
I deleted blkindex.dat and peers.dat.Edited diamond.conf and removed all addnode lines. Added addnode=193.68.21.19
Bootstrap it from another fully synced machine ... get a copy of blk0001.dat that is on right fork.
From command line:
diamond-qt -loadblock=blk0001.dat
Currently it is saying: Importing blockchain data file
Took about 5 hours on SSD but I'm on right fork now.
Perhaps the Diamond team will post a new blk0001.dat on OP in zip.
Ive got a copy of mine in a 7z file and it's 365M.
Not sure how to post it in thread and it's too big to email LOL.
I don't know how to post a torrent so thats a no-go too.
Thanks, mine took about an hour.
June 26, 2014, 08:36:40 PM
Not staking now ... did I lose my coin-age on first failed stake attempt when forks appeared?
Block chain explorer gives: No information available about transaction(Error Code: -5)
Blockchain explorer probably on wrong fork ...
Clearly as soon as staking started chain forked. Did every new Staking attempt create another fork?
I'd rather have another hard fork with everything working so get to work LOL.
Mining DMD still suspended on my machines till the bugs get worked out Hello wafflepool X11
Block chain explorer gives: No information available about transaction(Error Code: -5)
Blockchain explorer probably on wrong fork ...
Clearly as soon as staking started chain forked. Did every new Staking attempt create another fork?
OK I just got an incoming transaction for 12.82 DMD so I guess it's working
Not showing in Stake balance and transaction reads Mint:
Status: 0/unconfirmed, broadcast through 7 nodes
Date: 6/26/2014 05:21
Debit: 0.00 DMD
Net amount: -103.989716 DMD
Transaction ID: 12f9802f9e27b4aee4c503caf0a95fd99f9b95c8200ee30cc81c6e8cc05090be
Generate Not accepted
Wallet is unlocked. I'm rather dis-appointed, we are all paying 0.05 to the Foundation on each block mined. Come on get it right Dev team Not showing in Stake balance and transaction reads Mint:
Status: 0/unconfirmed, broadcast through 7 nodes
Date: 6/26/2014 05:21
Debit: 0.00 DMD
Net amount: -103.989716 DMD
Transaction ID: 12f9802f9e27b4aee4c503caf0a95fd99f9b95c8200ee30cc81c6e8cc05090be
Generate Not accepted
I'd rather have another hard fork with everything working so get to work LOL.Mining DMD still suspended on my machines till the bugs get worked out
Hello wafflepool X11 June 26, 2014, 08:31:12 PM
Getting the same on the MAC wallet client. Downloading blkindex.dat now and testing.
Code:
Date/Time: 2014-06-27 08:26:49.903 +0700
OS Version: Mac OS X 10.9.3 (13D65)
Report Version: 11
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
Assertion failed: (pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)), function GetStakeModifierChecksum, file ../Diamond/src/kernel.cpp, line 412.
June 26, 2014, 07:40:48 PM
Can someone please post the quickest method to re-sync?
I deleted blkindex.dat and peers.dat.Edited diamond.conf and removed all addnode lines. Added addnode=193.68.21.19
Bootstrap it from another fully synced machine ... get a copy of blk0001.dat that is on right fork.
From command line:
diamond-qt -loadblock=blk0001.dat
Currently it is saying: Importing blockchain data file
Took about 5 hours on SSD but I'm on right fork now.
Perhaps the Diamond team will post a new blk0001.dat on OP in zip.
Ive got a copy of mine in a 7z file and it's 365M.
Not sure how to post it in thread and it's too big to email LOL.
I don't know how to post a torrent so thats a no-go too.
June 26, 2014, 07:19:29 PM
Can someone please post the quickest method to re-sync?
June 26, 2014, 06:46:12 PM
keeping wallets on SSD sure helps re-index times LOL my other machine on HDD is syncing from network and prob will not be back to mining till tomorrow 
Can connect= be used in conjunction with addnode= ?
I ask because I'd like to have each machine in local net connected and still connecting to DMD network also.
Do I have to make one machine primary connected to network and others slaving off of that machine? I'm a bit confused about this LOL.
I've had problems in the past where one machine gets on a forked chain and the other is not forked ...
Can connect= be used in conjunction with addnode= ?
I ask because I'd like to have each machine in local net connected and still connecting to DMD network also.
Do I have to make one machine primary connected to network and others slaving off of that machine? I'm a bit confused about this LOL.
I've had problems in the past where one machine gets on a forked chain and the other is not forked ...
June 26, 2014, 06:37:25 PM
463622 Current Block
02:35:34

getcheckpoint
02:35:34

{
"synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
"height" : 463183,
"timestamp" : "2014-06-26 16:46:41 UTC"
}
I'm on the right chain but I do not have POS
17:36:54

getinfo
17:36:54

{
"version" : "v2.0.2.1",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : 184.01067500,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 463622,
"moneysupply" : 451629.98187800,
"connections" : 12,
"proxy" : "",
"ip" : "63.224.123.61",
"difficulty" : 49.16181211,
"testnet" : false,
"keypoololdest" : 1395368265,
"keypoolsize" : 102,
"paytxfee" : 0.00000000,
"errors" : ""
}
June 26, 2014, 06:34:22 PM
463622 Current Block
02:35:34

getcheckpoint
02:35:34

{
"synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
"height" : 463183,
"timestamp" : "2014-06-26 16:46:41 UTC"
}
I'm on the right chain but I do not have POS
June 26, 2014, 05:04:28 PM
Are there any block checkpoints we can verify that on proper chain after re-sync using debug console? getblock ?
I'd like to get back to mining DMD soon but will not until correct blockchain verified.
Might be wise to do a daily checkpoint for a while
Is this correct?
17:27:53

getcheckpoint
17:27:53

{
"synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
"height" : 463183,
"timestamp" : "2014-06-26 16:46:41 UTC"
}
I'd like to get back to mining DMD soon but will not until correct blockchain verified.
Might be wise to do a daily checkpoint for a while
Is this correct?
17:27:53

getcheckpoint
17:27:53

{
"synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
"height" : 463183,
"timestamp" : "2014-06-26 16:46:41 UTC"
}
June 26, 2014, 04:59:26 PM
so danbi, is your pool on a wrong fork or are these just display problems?
June 26, 2014, 04:17:52 PM
For those experiencing the 412 error.
Make sure you use only the OP config address when syncing. (I've deleted the rest leaving only one of them).
Sync speed is approximately 1000 blocks per minute.
After it syncs as a precautionary measure , make a backup copy of blk0001.dat + blkindex.dat.
Make sure you use only the OP config address when syncing. (I've deleted the rest leaving only one of them).
Sync speed is approximately 1000 blocks per minute.
After it syncs as a precautionary measure , make a backup copy of blk0001.dat + blkindex.dat.
u have update de blockchain for download whit the last block? The original is not good
June 26, 2014, 03:00:17 PM
I in general do not understand, who are now mining and why complexity increased again .. Which they chain and that in general is now happening with the network??
when you restart the wallet are all sorts of errors - for example
I did everything as you describe.
when you restart the wallet are all sorts of errors - for example
I did everything as you describe.
Jump to: