polanskiman
|
|
July 01, 2014, 08:34:57 AM |
|
New clean block chain is available at 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.
|
|
|
|
Coinler
|
|
July 01, 2014, 08: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
|
|
|
|
polanskiman
|
|
July 01, 2014, 08: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.
|
|
|
|
danbi
|
|
July 01, 2014, 09:42:50 AM |
|
New clean block chain is available at 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.zipDiamond Windows Wallet http://diamond.danbo.bg/downloads/diamond-qt-2.0.2.2.exeDiamond OS X Wallet http://diamond.danbo.bg/downloads/diamond-qt-2.0.2.2.dmg
|
BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
|
|
|
pallas
Legendary
Offline
Activity: 2716
Merit: 1094
Black Belt Developer
|
|
July 01, 2014, 09:49:18 AM |
|
New clean block chain is available at 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.zipDiamond Windows Wallet http://diamond.danbo.bg/downloads/diamond-qt-2.0.2.2.exeDiamond OS X Wallet http://diamond.danbo.bg/downloads/diamond-qt-2.0.2.2.dmgwell, 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.
|
|
|
|
popshot (OP)
|
|
July 01, 2014, 09: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
|
|
|
|
polanskiman
|
|
July 01, 2014, 09:59:35 AM |
|
New clean block chain is available at 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.zipDiamond Windows Wallet http://diamond.danbo.bg/downloads/diamond-qt-2.0.2.2.exeDiamond OS X Wallet http://diamond.danbo.bg/downloads/diamond-qt-2.0.2.2.dmgYes, 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.
|
|
|
|
polanskiman
|
|
July 01, 2014, 10: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.
|
|
|
|
Coinler
|
|
July 01, 2014, 10: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.
|
|
|
|
polanskiman
|
|
July 01, 2014, 10: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.
|
|
|
|
Coinler
|
|
July 01, 2014, 10: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.
|
|
|
|
cryptonit
Legendary
Offline
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
July 01, 2014, 11: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
|
|
|
|
danbi
|
|
July 01, 2014, 11:30:27 AM Last edit: July 01, 2014, 11:55:22 AM by danbi |
|
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.7zThe file size is of course much smaller.
|
BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
|
|
|
polanskiman
|
|
July 01, 2014, 11:32:03 AM |
|
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.
Beautiful!
|
|
|
|
polanskiman
|
|
July 01, 2014, 11:37:43 AM Last edit: July 01, 2014, 11:58:55 AM by polanskiman |
|
Since I was borred, I compiled a version where only v.2.0.2.2 clients would be allowed to connect. This is purely for me and for testing.
Here are the connection stats within a 2 hours time frame:
/Diamond:2.0.2.1/ /Diamond:2.0.1/ /Satoshi:0.7.2/ /Diamond:0.7.2/ 114 15 12 9
Still 24% of the clients are using pre-2.0.2.1 wallets.
|
|
|
|
utahjohn
|
|
July 01, 2014, 11:38:43 AM |
|
Beat me to the punch LOL my repack does not have a README for instructions . Glad you are staying on top of things Danbi
|
|
|
|
fips1992
Member
Offline
Activity: 150
Merit: 10
|
|
July 01, 2014, 12:16:16 PM |
|
hello i have a problem, unfortunately I can not connect to my rig to the pool dmdpool.digsys.bg:3345 and I can not get no reward as I do
|
|
|
|
danbi
|
|
July 01, 2014, 12:17:37 PM |
|
Beat me to the punch LOL my repack does not have a README for instructions . Glad you are staying on top of things Danbi Mind you, I am good at writing scripts and have dozens of different compressors, for the collectors But need to spend more time with the real fixes.... Still 24% of the clients are using pre-2.0.2.1 wallets. Unfortunately, due to time limitations, all 2.0.2.2 clients show up as 2.0.2.1 so we can't say who is unprotected, which is sad. But it turns out not only are there several versions numbers in the wallet code, but also each of these is used randomly on different places and some are critical, as for example making the GUI display "version THIS" would make the code overwrite the database version number in the wallet.dat file with version THIS and make it impossible to open on an "older" version. Even if the version difference is just a cosmetic one.... In any case, once we disconnect the older wallets, they will wake up and come here.
|
BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
|
|
|
polanskiman
|
|
July 01, 2014, 12:26:09 PM |
|
Beat me to the punch LOL my repack does not have a README for instructions . Glad you are staying on top of things Danbi Mind you, I am good at writing scripts and have dozens of different compressors, for the collectors But need to spend more time with the real fixes.... Still 24% of the clients are using pre-2.0.2.1 wallets. Unfortunately, due to time limitations, all 2.0.2.2 clients show up as 2.0.2.1 so we can't say who is unprotected, which is sad. But it turns out not only are there several versions numbers in the wallet code, but also each of these is used randomly on different places and some are critical, as for example making the GUI display "version THIS" would make the code overwrite the database version number in the wallet.dat file with version THIS and make it impossible to open on an "older" version. Even if the version difference is just a cosmetic one.... In any case, once we disconnect the older wallets, they will wake up and come here. Sure I was simply fooling around. Yes was wondering why I didn't connect to anyone. 2.0.2.2 are seen as 2.0.2.1 and thus being considered obsolete. Thanks for the clarifications.
|
|
|
|
|
|