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

[cryptonit]

we getting hit hard 126 diff

diff raise value drop  

solution mine at
http://multipool.bit.diamonds/
as much as u can

info with next payout cycle we will break 1000 DMD total mined DMD on multipool
great job! continue digging for that precious gems

[1714929117]

1714929117

[1714929117]

1714929117

[1714929117]

1714929117

[Timelord2067]

BleuTrade needs to be added - https://bleutrade.com/exchange/2129 they are looking for coins both new and old to add to their exchange, they seem legit, you can even buy shares which pay out on the previous four hours trade.

[cryptonit]

the truth in my opinion about exchanges is that we shouldnt consider any exchange as real

who is below 10 BTC average daily volume

thats what i learned from alcurex and allcrypt.......

every exchange is free to add us but in future we wont even listen such micro exchanges on our ANN thread

[pokeytex]

Ok - something crazy happened - the system seems to have crashed, the difficulty dropped drastically, and now I am getting the error that I can't open my wallet again.  Any advice?  It is the same error after POS went active.

** Assertion Failed ** - error

[danbi]

Ok - something crazy happened - the system seems to have crashed, the difficulty dropped drastically, and now I am getting the error that I can't open my wallet again.  Any advice?  It is the same error after POS went active.

** Assertion Failed ** - error

You are likely on a fork. What do you see as

$ diamondd getcheckpoint
{
    "synccheckpoint" : "0000000002097549fdc9f404acc5db9b03de65c6e6801bbf77fa9bfacf6257c6",
    "height" : 510591,
    "timestamp" : "2014-07-30 18:58:04 UTC"
}

You should see higher height and timestamp than this.

As for the assertion failed, there should be other text in the message. What is it?

[popshot]

Ok - something crazy happened - the system seems to have crashed, the difficulty dropped drastically, and now I am getting the error that I can't open my wallet again.  Any advice?  It is the same error after POS went active.

** Assertion Failed ** - error

What do you mean that 'the system seems to have crashed' - your OS or the Diamond network? If difficulty dropped significantly you might have forked. It's 70 at the moment.
Very strange it gave you this error as Fast Index feature seemed to have fixed that issue, but if that happened it means your database is corrupted and the new one needs to be built. Follow the instructions as with the previous crash.  

[pokeytex]

Ok - something crazy happened - the system seems to have crashed, the difficulty dropped drastically, and now I am getting the error that I can't open my wallet again.  Any advice?  It is the same error after POS went active.

** Assertion Failed ** - error

You are likely on a fork. What do you see as

$ diamondd getcheckpoint
{
    "synccheckpoint" : "0000000002097549fdc9f404acc5db9b03de65c6e6801bbf77fa9bfacf6257c6",
    "height" : 510591,
    "timestamp" : "2014-07-30 18:58:04 UTC"
}

You should see higher height and timestamp than this.

As for the assertion failed, there should be other text in the message. What is it?

Danbi,

This is the error.  I didn't do anything.  I just logged in to your pool and saw that the difficulty was at 3  - I then logged into my machine and checked the wallet.  It matched.  The difficulty then proceeded to climb back up.  I cannot log into my wallet to test the checkpoint since I keep getting this error.

Assertion Failed!
Program: C:\users\pok\desk\crypto\diamond-qt-2.0.3exe
File: src\kernel.cpp, Line 410

Expression: pindex-> pprev || pindex-> GetblockHash() == (!fTestNet ? hashGenesisBlock:hashGenesisBlockTestNet)

Not sure if that helps.

[pokeytex]

Ok - something crazy happened - the system seems to have crashed, the difficulty dropped drastically, and now I am getting the error that I can't open my wallet again.  Any advice?  It is the same error after POS went active.

** Assertion Failed ** - error

What do you mean that 'the system seems to have crashed' - your OS or the Diamond network? If difficulty dropped significantly you might have forked. It's 70 at the moment.
Very strange it gave you this error as Fast Index feature seemed to have fixed that issue, but if that happened it means your database is corrupted and the new one needs to be built. Follow the instructions as with the previous crash.  

No - my machine is working fine and was until I logged into Danbi's and noticed that the difficulty was around 3.  The overall system MH/s was reading 350 and danbi's pool was reading like 1700 mh/s.  I am not sure what happened.  I then logged into my machine at home to see that everything was ok and all seemed fine.  I closed my Diamond Wallet version 2.0.3.  It has been working flawlessly since the birthday download.  However, when I reopened it I got the assertion error.  Do I need to resync and go through that process again?

[pokeytex]

Ok - something crazy happened - the system seems to have crashed, the difficulty dropped drastically, and now I am getting the error that I can't open my wallet again.  Any advice?  It is the same error after POS went active.

** Assertion Failed ** - error

You are likely on a fork. What do you see as

$ diamondd getcheckpoint
{
    "synccheckpoint" : "0000000002097549fdc9f404acc5db9b03de65c6e6801bbf77fa9bfacf6257c6",
    "height" : 510591,
    "timestamp" : "2014-07-30 18:58:04 UTC"
}

You should see higher height and timestamp than this.

As for the assertion failed, there should be other text in the message. What is it?

Danbi,

This is the error.  I didn't do anything.  I just logged in to your pool and saw that the difficulty was at 3  - I then logged into my machine and checked the wallet.  It matched.  The difficulty then proceeded to climb back up.  I cannot log into my wallet to test the checkpoint since I keep getting this error.

Assertion Failed!
Program: C:\users\pok\desk\crypto\diamond-qt-2.0.3exe
File: src\kernel.cpp, Line 410

Expression: pindex-> pprev || pindex-> GetblockHash() == (!fTestNet ? hashGenesisBlock:hashGenesisBlockTestNet)

Not sure if that helps.

I just resynced the wallet and this is the check point:

"synccheckpoint" : "00000000000252c67d48a5be604990ab2ea22e8dae067c24b834bc059e5cedb8",
"height" : 510634,
"timestamp" : "2014-07-30 19:49:51 UTC"

[popshot]

It is possible that we are under attack like before, when the PoS had started, however this time the network is not down - just the affected nodes get disconnected.
We are preparing an updated chain. The pool runs correctly with difficulty at around 60.

We're on it

[popshot]

"synccheckpoint" : "00000000000252c67d48a5be604990ab2ea22e8dae067c24b834bc059e5cedb8",
"height" : 510634,
"timestamp" : "2014-07-30 19:49:51 UTC"

Hash and block height match, you're on the right chain.

[danbi]

The network had indeed some issue today, apparently during the moment lots of nodes got banned and are now unable to connect -- the "good" nodes will keep them banned for 24 hours. Which, if we don't do anything will 'heal' the network by tomorrow.

Anyway, I hope to have an clean and reliable block chain to sync faster soon.

Alternatively, you could rebuild the block index with

1. moving blk0001.dat, blkindex.dat and database/* out of the Diamond directory
2. running diamondd -loadblock=blk0001.dat (the one you moved away)

On my hardware, this takes about an hour and a half to complete. The resulting blkindex.dat is clean of the garbage. It is advisable to make copy of the files mentioned in 1) for later recovery of this error.

I am still trying to pinpoint the exact cause of it, and will appreciate any ideas someone might have...

[shveicar]

I am still trying to pinpoint the exact cause of it, and will appreciate any ideas someone might have...

Maybe just someone checks the network Diamond strength, because even half a year ago a lot of coins were split (ftc, trc, and others) some unknown with large computing power.

[danbi]

An current block chain for fast syncing is available at http://diamond.danbo.bg/downloads/dmdchain20140731-fast.7z
Also with .zip extension. Please note this is for the v2.0.3 and later wallets, that support fast index.

[danbi]

I am still trying to pinpoint the exact cause of it, and will appreciate any ideas someone might have...

Maybe just someone checks the network Diamond strength, because even half a year ago a lot of coins were split (ftc, trc, and others) some unknown with large computing power.

Diamond network is protected from such an attack, but the individual nodes are not. As it turns out, they may be disconnected from the network for up to 24 hours.

[stillontop]

From my observations following nodes are doing unusual things:

173.246.103.92:17771
192.75.207.148:17771

I am getting warnings for outgoing connections from Diamond-Qt.exe to 98.142.248.233 as well.

I also had to rebuild the blockchain today.

Btw. what are the exact needs for the Design Contest?

[utahjohn]

I resynced from latest blockchain that Danbi provided.  And already forked again with diff = 7 ... shutting down my DMD solo mining for now and closing wallet   Fortunately I have no DMD on exchanges right now ...

[danbi]

I would suggest those suffering from this issue follow this checklist:

1. Upgrade to the latest wallet version (2.0.3) -- as a bonus you are getting the fast index feature, which besides being.. fast, helps great deal with the block index corruption (does not resolve it 100% yet).
2. Delete your peers.dat file!
3. Then make sure you have noirc=1 in the Diamond.conf file.
4. Make sure you have connect=193.68.21.19 in your configuration file. (or, later switch it to addnode=193.68.21.19)
5. If you do not run your wallet all the time (thus acting as a node for others), it might be helpful to have listen=0 in the configuration file as well.
6. Download the posted recent block chain (or sync from scratch).

So in summary, you need this in the config file:

listen=0
noirc=1
connect=193.68.21.19

The later might be addnode= instead so you get more peers from that node and be connected when it is down or unreachable. Unfortunately, that node might be banning you... because of your past behavior. We are working to make the ban duration shorter.

PS: We want to get rid of wallets version 2.0.2.1. Unfortunately, this also means we need to get rid of 2.0.2.2 as due to some error that shows itself as 2.0.2.1 too... So if you have one of these versions, *please* upgrade.

PPS: Re-arranged the steps appropriately.

[paladin281978]

danbi

after your council all in norm.

[cryptonit]

a crew of a sailing ship can prove their skills only in a storm

we just had hard weather and high waves

thx to all crewmen special danbi who show that our crew and our ship is no easy target
for those who play with wind and weather and feel like gods

they think "we make em - we break em"

but we dont need their pumps and we dont die to their attacks

we might be a playball of elements
but not of intended manipulation by self declared crypto gods......



thx for all the support of our loyal community
u are the real backbone of our coin