Following your recommendations, the block chain archive is repacked. It is still in an ZIP file, slightly better compressed (saved a whooping megabyte), but now unpacks in a folder with the same name as the archive and has README with instructions.
For the 7zip users, here is an archive packaged with that as well: http://diamond.danbo.bg/downloads/dmdchain20140701.7z
The file size is of course much smaller.
Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 777. (Read 1260636 times)
July 01, 2014, 06:30:27 AM
July 01, 2014, 06:09:22 AM
haha im not new to dmd. been at it since december last year. got a decent start from the pumps back then dmd was .002-.003btc each ;p
we should go back there.. this algorithm doesnt need to obey the standard pricing of crypto since we're primarily gpu miners. great coin to invest in atm.
good analyzis!
and if ya would know that we have some more things cooking to prepare diamond for the future
u would be even more enthusiastic
July 01, 2014, 05:35:26 AM
hi does anyone have a config for this coin? i was mining groestlcoin and switched to dmd but for some reason it doesnt connect to the pool at all?
Please be more precise in what problem you are encoutering. It would help us in helping you.
it doesnt connect to the pool. i was trying to use digsys pool
What's the error message? Please post your current config and a print of your miner.
i managed to get it working with the "-k diamond" tag. i was using groestl before. thanks for the assistance.
Good to hear. Welcome to DMD.
haha im not new to dmd. been at it since december last year. got a decent start from the pumps back then dmd was .002-.003btc each ;p
we should go back there.. this algorithm doesnt need to obey the standard pricing of crypto since we're primarily gpu miners. great coin to invest in atm.
July 01, 2014, 05:33:22 AM
hi does anyone have a config for this coin? i was mining groestlcoin and switched to dmd but for some reason it doesnt connect to the pool at all?
Please be more precise in what problem you are encoutering. It would help us in helping you.
it doesnt connect to the pool. i was trying to use digsys pool
What's the error message? Please post your current config and a print of your miner.
i managed to get it working with the "-k diamond" tag. i was using groestl before. thanks for the assistance.
Good to hear. Welcome to DMD.
July 01, 2014, 05:31:19 AM
hi does anyone have a config for this coin? i was mining groestlcoin and switched to dmd but for some reason it doesnt connect to the pool at all?
Please be more precise in what problem you are encoutering. It would help us in helping you.
it doesnt connect to the pool. i was trying to use digsys pool
What's the error message? Please post your current config and a print of your miner.
i managed to get it working with the "-k diamond" tag. i was using groestl before. thanks for the assistance.
July 01, 2014, 05:24:17 AM
Unpacked and removed . for folder name, repacking in a 7zip file and will provide a Mega link as soon as I get it uploaded 
I beleive you should leave that you the coin devs so to avoid confusion and to make sure the source is official.
July 01, 2014, 04:59:35 AM
New clean block chain is available at
It is almost twice less in size than the previous one provided, which was bloated with more than one copy of the same block.
As discussed earlier, it was created by connecting to a known good node (one running current software) ONLY, disabling IRC learning of peers, incoming connections and removing peers.dat. Anyone can create such a distilled blockchain -- we do this all the time to test the new client functions normally, this one is provided just for your convenience.
Code:
ftp://diamond.danbo.bg/dmdchain20140701.zip
It is almost twice less in size than the previous one provided, which was bloated with more than one copy of the same block.
As discussed earlier, it was created by connecting to a known good node (one running current software) ONLY, disabling IRC learning of peers, incoming connections and removing peers.dat. Anyone can create such a distilled blockchain -- we do this all the time to test the new client functions normally, this one is provided just for your convenience.
Small note. The directory unpacks as a hidden folder on MAC.
Yes... it unpacks as the .Diamond folder, which is the appropriate name under all UNIX (except OS X). It is hidden in OS X and Windows, because of the dot.
Maybe, a better idea is to unpack as Diamond folder, which would work in both OS X and Windows. What do you think?
The primary reason I did not do it that was is that on my development computers, Diamond is the directory where the git sources come. I could have inadvertently created a mess. But maybe good idea to change it, as for other OSes it's inconvenience.
By the way, HTTP download links are here:
Diamond Block chain http://diamond.danbo.bg/downloads/dmdchain20140701.zip
Diamond Windows Wallet http://diamond.danbo.bg/downloads/diamond-qt-2.0.2.2.exe
Diamond OS X Wallet http://diamond.danbo.bg/downloads/diamond-qt-2.0.2.2.dmg
Yes, in MAC OS a folder/file starting with a dot makes it a hidden folder/file. Contratry to Windows it is not common in the "MAC world" to have hidden files visible to the user. In fact if the user wants to see the hidden files it requires the use of command line in order to make those folder/files (usually systeme related) visible. I have my own bashfiles with simplified aliases to make it easy to switch between hidden/unhidden. The great majority of people have no idea how to do that though and Apple clearly does not make it easy. I recommend making the folder fully visible, specially because this is a distributed file and intrisically it should be visible
Thanks for the http links. Much easier to download now.
July 01, 2014, 04:51:45 AM
hi does anyone have a config for this coin? i was mining groestlcoin and switched to dmd but for some reason it doesnt connect to the pool at all?
I assume you tried to use sph miner used in Grostl to mine Diamond. This would not work as GRS has different hashing function for signing transaction which causes stratum incompatibility. Please use the sph miner that is adapted to work with Diamond.
You can download it from here:
http://bit.diamonds/mining.html
July 01, 2014, 04:49:18 AM
New clean block chain is available at
It is almost twice less in size than the previous one provided, which was bloated with more than one copy of the same block.
As discussed earlier, it was created by connecting to a known good node (one running current software) ONLY, disabling IRC learning of peers, incoming connections and removing peers.dat. Anyone can create such a distilled blockchain -- we do this all the time to test the new client functions normally, this one is provided just for your convenience.
Code:
ftp://diamond.danbo.bg/dmdchain20140701.zip
It is almost twice less in size than the previous one provided, which was bloated with more than one copy of the same block.
As discussed earlier, it was created by connecting to a known good node (one running current software) ONLY, disabling IRC learning of peers, incoming connections and removing peers.dat. Anyone can create such a distilled blockchain -- we do this all the time to test the new client functions normally, this one is provided just for your convenience.
Small note. The directory unpacks as a hidden folder on MAC.
Yes... it unpacks as the .Diamond folder, which is the appropriate name under all UNIX (except OS X). It is hidden in OS X and Windows, because of the dot.
Maybe, a better idea is to unpack as Diamond folder, which would work in both OS X and Windows. What do you think?
The primary reason I did not do it that was is that on my development computers, Diamond is the directory where the git sources come. I could have inadvertently created a mess. But maybe good idea to change it, as for other OSes it's inconvenience.
By the way, HTTP download links are here:
Diamond Block chain http://diamond.danbo.bg/downloads/dmdchain20140701.zip
Diamond Windows Wallet http://diamond.danbo.bg/downloads/diamond-qt-2.0.2.2.exe
Diamond OS X Wallet http://diamond.danbo.bg/downloads/diamond-qt-2.0.2.2.dmg
well, actually it is hidden on unix/linux as well (if you don't specify "-a" to ls).
I think the best way is to unpack to a directory named "dmd blockchain" which contains a README file which explains how to use it, depending on the OS you have.
July 01, 2014, 04:42:50 AM
New clean block chain is available at
It is almost twice less in size than the previous one provided, which was bloated with more than one copy of the same block.
As discussed earlier, it was created by connecting to a known good node (one running current software) ONLY, disabling IRC learning of peers, incoming connections and removing peers.dat. Anyone can create such a distilled blockchain -- we do this all the time to test the new client functions normally, this one is provided just for your convenience.
Code:
ftp://diamond.danbo.bg/dmdchain20140701.zip
It is almost twice less in size than the previous one provided, which was bloated with more than one copy of the same block.
As discussed earlier, it was created by connecting to a known good node (one running current software) ONLY, disabling IRC learning of peers, incoming connections and removing peers.dat. Anyone can create such a distilled blockchain -- we do this all the time to test the new client functions normally, this one is provided just for your convenience.
Small note. The directory unpacks as a hidden folder on MAC.
Yes... it unpacks as the .Diamond folder, which is the appropriate name under all UNIX (except OS X). It is hidden in OS X and Windows, because of the dot.
Maybe, a better idea is to unpack as Diamond folder, which would work in both OS X and Windows. What do you think?
The primary reason I did not do it that was is that on my development computers, Diamond is the directory where the git sources come. I could have inadvertently created a mess. But maybe good idea to change it, as for other OSes it's inconvenience.
By the way, HTTP download links are here:
Diamond Block chain http://diamond.danbo.bg/downloads/dmdchain20140701.zip
Diamond Windows Wallet http://diamond.danbo.bg/downloads/diamond-qt-2.0.2.2.exe
Diamond OS X Wallet http://diamond.danbo.bg/downloads/diamond-qt-2.0.2.2.dmg
July 01, 2014, 03:44:14 AM
hi does anyone have a config for this coin? i was mining groestlcoin and switched to dmd but for some reason it doesnt connect to the pool at all?
Please be more precise in what problem you are encoutering. It would help us in helping you.
it doesnt connect to the pool. i was trying to use digsys pool
What's the error message? Please post your current config and a print of your miner.
July 01, 2014, 03:38:09 AM
hi does anyone have a config for this coin? i was mining groestlcoin and switched to dmd but for some reason it doesnt connect to the pool at all?
Please be more precise in what problem you are encoutering. It would help us in helping you.
it doesnt connect to the pool. i was trying to use digsys pool
July 01, 2014, 03:34:57 AM
New clean block chain is available at
It is almost twice less in size than the previous one provided, which was bloated with more than one copy of the same block.
As discussed earlier, it was created by connecting to a known good node (one running current software) ONLY, disabling IRC learning of peers, incoming connections and removing peers.dat. Anyone can create such a distilled blockchain -- we do this all the time to test the new client functions normally, this one is provided just for your convenience.
Code:
ftp://diamond.danbo.bg/dmdchain20140701.zip
It is almost twice less in size than the previous one provided, which was bloated with more than one copy of the same block.
As discussed earlier, it was created by connecting to a known good node (one running current software) ONLY, disabling IRC learning of peers, incoming connections and removing peers.dat. Anyone can create such a distilled blockchain -- we do this all the time to test the new client functions normally, this one is provided just for your convenience.
Small note. The directory unpacks as a hidden folder on MAC.
July 01, 2014, 03:02:12 AM
02:01:50

getcheckpoint
02:01:50

{
"synccheckpoint" : "000000000390100991ea4a9fd7e6d8e1c503821dc5ee96449049d9f1367b1703",
"height" : 469658,
"timestamp" : "2014-07-01 07:57:29 UTC"
}
getpeerinfo showing all connections to 2.0.2.1 at moment ... give it a day or so for users to update ...
Unfortuately those on 2.0.2.1 will still be accepting connections from older clients. I would post a new database in a week or so after majority have updated to 2.0.2.2.

getcheckpoint
02:01:50

{
"synccheckpoint" : "000000000390100991ea4a9fd7e6d8e1c503821dc5ee96449049d9f1367b1703",
"height" : 469658,
"timestamp" : "2014-07-01 07:57:29 UTC"
}
getpeerinfo showing all connections to 2.0.2.1 at moment ... give it a day or so for users to update ...
Unfortuately those on 2.0.2.1 will still be accepting connections from older clients. I would post a new database in a week or so after majority have updated to 2.0.2.2.
July 01, 2014, 02:52:20 AM
July 01, 2014, 02:44:29 AM
Great work Danbi My wallet fired right up after placing new clean blockchain in.. Sync'd in a matter of minutes
My wallet fired right up after placing new clean blockchain in.. Sync'd in a matter of minutes July 01, 2014, 02:37:14 AM
This is also possible. However, we have identified only pre 2.0.2.1 nodes doing it...
Anyway, I don't think it is the code/compilation. It is the "old" wallet that corrupted the database, the new just bombs on it, just as the old would.
Did you have any chance to test my build on other OS X versions than Mavericks? maybe it needs adapting -- now that the code is in github, perhaps you could do another compare Thanks!
Anyway, I don't think it is the code/compilation. It is the "old" wallet that corrupted the database, the new just bombs on it, just as the old would.
Did you have any chance to test my build on other OS X versions than Mavericks? maybe it needs adapting -- now that the code is in github, perhaps you could do another compare
Thanks!My current environments are all in 10.9. One in 10.9.2 and one in 10.9.3. My old MAC running 10.7 is dead. Anyone else using MAC among the DMDers? Or I am the only black sheep?
What do you mean another compare? I used the updated code from your github repo to compile yesterday. Both yours and my release are based on the exact same code. The only difference lies on the version I am compiling with. I am currently using Qt 4.8.6 instead of Qt 5.3.0
July 01, 2014, 02:27:47 AM
Just a word of warning, regarding that dreaded block index corruption problem.
The wallet version 2.0.2.2 does NOT fix it. It only makes sure old nodes that apparently send the deadly orphan blocks cannot connect to you.
This problem only affects the block index (blkindex.dat) and not the block chain (blk0001.dat) or the wallet (wallet.dat). There is no corruption there and no coins are lost etc.
We decided to spend the time with this release now in order to give you tools to deal with and recover faster.
The real issue is being investigated and possibly several independent fixes will be implemented. Unfortunately, it seems to happen with other coins too but none has found a solution so far.
The wallet version 2.0.2.2 does NOT fix it. It only makes sure old nodes that apparently send the deadly orphan blocks cannot connect to you.
This problem only affects the block index (blkindex.dat) and not the block chain (blk0001.dat) or the wallet (wallet.dat). There is no corruption there and no coins are lost etc.
We decided to spend the time with this release now in order to give you tools to deal with and recover faster.
The real issue is being investigated and possibly several independent fixes will be implemented. Unfortunately, it seems to happen with other coins too but none has found a solution so far.
I know. Just found it strange that it did work yesterday with the compiled version I did. I closed the wallet several times and all good. This morning I tried to use your compiled version and the assertion pb poped up again. I am aware that this update does not fix per say the assertion problem directly but it does address it indirectly by preventing older wallets predating 2.0.2.1 to connect? Or Perhaps even 2.0.2.1 wallets are also feeding loads of orphans to 2.0.2.2?
This is also possible. However, we have identified only pre 2.0.2.1 nodes doing it...
Anyway, I don't think it is the code/compilation. It is the "old" wallet that corrupted the database, the new just bombs on it, just as the old would.
Did you have any chance to test my build on other OS X versions than Mavericks? maybe it needs adapting -- now that the code is in github, perhaps you could do another compare
Thanks! July 01, 2014, 02:14:13 AM
hi does anyone have a config for this coin? i was mining groestlcoin and switched to dmd but for some reason it doesnt connect to the pool at all?
Please be more precise in what problem you are encoutering. It would help us in helping you.
July 01, 2014, 02:10:45 AM
Just a word of warning, regarding that dreaded block index corruption problem.
The wallet version 2.0.2.2 does NOT fix it. It only makes sure old nodes that apparently send the deadly orphan blocks cannot connect to you.
This problem only affects the block index (blkindex.dat) and not the block chain (blk0001.dat) or the wallet (wallet.dat). There is no corruption there and no coins are lost etc.
We decided to spend the time with this release now in order to give you tools to deal with and recover faster.
The real issue is being investigated and possibly several independent fixes will be implemented. Unfortunately, it seems to happen with other coins too but none has found a solution so far.
The wallet version 2.0.2.2 does NOT fix it. It only makes sure old nodes that apparently send the deadly orphan blocks cannot connect to you.
This problem only affects the block index (blkindex.dat) and not the block chain (blk0001.dat) or the wallet (wallet.dat). There is no corruption there and no coins are lost etc.
We decided to spend the time with this release now in order to give you tools to deal with and recover faster.
The real issue is being investigated and possibly several independent fixes will be implemented. Unfortunately, it seems to happen with other coins too but none has found a solution so far.
I know. Just found it strange that it did work yesterday with the compiled version I did. I closed the wallet several times and all good. This morning I tried to use your compiled version and the assertion pb poped up again. I am aware that this update does not fix per say the assertion problem directly but it does address it indirectly by preventing older wallets predating 2.0.2.1 to connect? Or Perhaps even 2.0.2.1 wallets are also feeding loads of orphans to 2.0.2.2?
Jump to: