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

[2tights]

Can someone please post the quickest method to re-sync?

[1714010919]

1714010919

[1714010919]

1714010919

[1714010919]

1714010919

[utahjohn]

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.

[polanskiman]

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.

[utahjohn]

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?

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  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

[2tights]

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.

[paladin281978]

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.

[jepistons]

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?

ya same thing happen to me  over 1200 minted coins all 0 confirmations still awaiting what happen when  the fork kicked in

[Coinish]

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.....


  ... ... ...

[shveicar]

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

[utahjohn]

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!

So much for unattended restart of solo mining in event of power failure ...

[shveicar]

utahjohn
I hope that they are now engaged in this..

[paladin281978]

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

the same problem

[shveicar]

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..

[popshot]

It seems that forking was inevitable as not everyone had updated their clients , and some powerful miners kept mining after the switch. The network is designed in such a way that it will 'heal' itself without any intervention .. the strongest chain will prevail.

The situation with that error is indeed annoying and it might not be a quick fix, especially, because danbi had to go to a few day conference and his time and resources are extremely limited to deal with it at this very  moment. I was hit with it as well and the foundation wallet is dysfunctional and has been syncing since yesterday.

All we can do at the moment is wait and don't despair as these things are fixable - the network can fix itself but the wallet need some more work. Danbi will be back this weekend and will follow up on this issue.

I haven't got access to his pool so cannot share the correct chain.

To some saying about having coins 7 days old and not minting.. Minting does not happen just like that , it's a lottery, you need to wait for your turn (either difficulty falls or the coins will be grouped next time round automatically and that will increase the chance of you successfully staking).

[polanskiman]

It seems that forking was inevitable as not everyone had updated their clients , and some powerful miners kept mining after the switch. The network is designed in such a way that it will 'heal' itself without any intervention .. the strongest chain will prevail.

The situation with that error is indeed annoying and it might not be a quick fix, especially, because danbi had to go to a few day conference and his time and resources are extremely limited to deal with it at this very  moment. I was hit with it as well and the foundation wallet is dysfunctional and has been syncing since yesterday.

All we can do at the moment is wait and don't despair as these things are fixable - the network can fix itself but the wallet need some more work. Danbi will be back this weekend and will follow up on this issue.

I haven't got access to his pool so cannot share the correct chain.

To some saying about having coins 7 days old and not minting.. Minting does not happen just like that , it's a lottery, you need to wait for your turn (either difficulty falls or the coins will be grouped next time round automatically and that will increase the chance of you successfully staking).

If that is the case, you should then be active and keep posting regularly an updated blockchain so that we don't need to be sinking the wallet from too far away. We don't all leave our wallets open all day/night long.

[NoxX]

It seems that forking was inevitable as not everyone had updated their clients , and some powerful miners kept mining after the switch. The network is designed in such a way that it will 'heal' itself without any intervention .. the strongest chain will prevail.

The situation with that error is indeed annoying and it might not be a quick fix, especially, because danbi had to go to a few day conference and his time and resources are extremely limited to deal with it at this very  moment. I was hit with it as well and the foundation wallet is dysfunctional and has been syncing since yesterday.

All we can do at the moment is wait and don't despair as these things are fixable - the network can fix itself but the wallet need some more work. Danbi will be back this weekend and will follow up on this issue.

I haven't got access to his pool so cannot share the correct chain.

To some saying about having coins 7 days old and not minting.. Minting does not happen just like that , it's a lottery, you need to wait for your turn (either difficulty falls or the coins will be grouped next time round automatically and that will increase the chance of you successfully staking).

So are you saying that danbis pool IS on the wrong chain? Just want to know if it makes sense to direct miners elsewhere for the weekend...

[utahjohn]

So wallet must be kept open after re-index or another oh-shit have to re-index if power fails or needing to reboot after winblowz updates ... Closing wallet NOT advisable till new wallet bugfixes LOL

@popshot how about publishing checkpoints regularly on OP so users can verify they are on correct blockchain

[polanskiman]

So are you saying that danbis pool IS on the wrong chain? Just want to know if it makes sense to direct miners elsewhere for the weekend...

Not sure. Cryptohunger pool is on the right fork though.

[popshot]

If that is the case, you should then be active and keep posting regularly an updated blockchain so that we don't need to be sinking the wallet from too far away. We don't all leave our wallets open all day/night long.

I'd love to do that, however the foundation wallet is still 'turning on' (sync seems to be done already).. and has been turning on for hours , there are over 77 thousands of transactions to go through. Once it's operational and I confirm we are on the same chain then I will share the database.
The error message, I can't fix it as it's a deeply rooted problem.

[popshot]

Not sure. Cryptohunger pool is on the right fork though.

They've confirmed they had the updated version of the client.