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

[NoobKidOnTheBlock]

Thanks I added some more nodes to my .conf file and now it started downloading the blockchain again so Cheers mate

Hey Noob - welcome to Diamond!  I saw you around on the Spreadcoin forum!

-pokeytex

Hey man Ya I was checking out this coin before but didn't jump on it when I apparently should've lol But now I've encountered another problem with my wallet syncing.  It was at like 121000 blocks left and now I just went to check it and its at 497673 blocks to go?? Why would it have jumped back like that? Can anyone give me any ideas why that might be? I used the nodes that it says for the .conf file in the OP so I don't understand why it would go back like 300k blocks while syncing?

[cryptonit]

Thanks I added some more nodes to my .conf file and now it started downloading the blockchain again so Cheers mate

Hey Noob - welcome to Diamond!  I saw you around on the Spreadcoin forum!

-pokeytex

Hey man Ya I was checking out this coin before but didn't jump on it when I apparently should've lol But now I've encountered another problem with my wallet syncing.  It was at like 121000 blocks left and now I just went to check it and its at 497673 blocks to go?? Why would it have jumped back like that? Can anyone give me any ideas why that might be? I used the nodes that it says for the .conf file in the OP so I don't understand why it would go back like 300k blocks while syncing?

it doesnt go back it just dedected that the chain is longer than it did expect before......
if u wana see progress look how much blocks u have
and compare that with actual blockcount at https://chainz.cryptoid.info/dmd/

problem is we are a very old coin and we had a lot improvements in history that required a hardfork
so when u sync up from 0 u go through this whole history

means in sync process u sometimes talk with very old wallets who are legit communication partners
for that old blocks that u sync but they are long disconnected from real network
and such wallets can report as max blockcount only a number as far as they where able to sync themself
(dont ask my why there wallets outdated 1 year are still up and running and owners dont update them (or at least stop them) the internet have its own kind of undead creatures it seems)

by run with the suggested diamond.conf entries and delete ur peers.dat u should not come in touch with that wallets

listen=1
noirc=1
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
bantime=600

later on when u sync higher u reach triggers that will make ur wallet disconnect old wallets and from that point on u are in clean area

[NoobKidOnTheBlock]

Hey Noob - welcome to Diamond!  I saw you around on the Spreadcoin forum!

-pokeytex

Hey man Ya I was checking out this coin before but didn't jump on it when I apparently should've lol But now I've encountered another problem with my wallet syncing.  It was at like 121000 blocks left and now I just went to check it and its at 497673 blocks to go?? Why would it have jumped back like that? Can anyone give me any ideas why that might be? I used the nodes that it says for the .conf file in the OP so I don't understand why it would go back like 300k blocks while syncing?
[/quote]
it doesnt go back it just dedected that the chain is longer than it did expect before......
if u wana see progress look how much blocks u have
and compare that with actual blockcount at https://chainz.cryptoid.info/dmd/

problem is we are a very old coin and we had a lot improvements in history that required a hardfork
so when u sync up from 0 u go through this whole history

means in sync process u sometimes talk with very old wallets who are legit communication partners
for that old blocks that u sync but they are long disconnected from real network
and such wallets can report as max blockcount only a number as far as they where able to sync themself
(dont ask my why there wallets outdated 1 year are still up and running and owners dont update them (or at least stop them) the internet have its own kind of undead creatures it seems)

by run with the suggested diamond.conf entries and delete ur peers.dat u should not come in touch with that wallets

listen=1
noirc=1
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
bantime=600

later on when u sync higher u reach triggers that will make ur wallet disconnect old wallets and from that point on u are in clean area

[/quote]
Okay I've got all that in my conf file except the bantime=600.  What does that bantime=600 do?

[ajqjjj]

DMD will no longer be minable? almost all fallen pools or maintenance? 

[cryptonit]

DMD will no longer be minable? almost all fallen pools or maintenance? 

diamond will stay mineable but at reduced rewards (0.2 dmd every 100 sec)
https://chainz.cryptoid.info/dmd/#!extraction
regarding the both miningfield pools we have to ask miningfield
maybe he is upgrading them already to new wallet and prepare them for trigger

expect the next few days very chaotic regarding pools they will update wallets
and later on maybe fight with adjustments regarding change pow specs

i suggest as many people as possible setup their rigs for solomining

below a old solomining guide from HR i just adapted the diamond conf section

Okay, I've decided to solo mine. I was looking at my payouts from where I was mining Groestl, and with those payouts being at the bottom of the daily estimated range over a period of 48 to 72 hours (depending on the machine) on a pool accounting for around 25% of the network hashrate which should adequately smooth outliers and give an accurate long term average mine rate, I've decided that solo mining can't be worse, and with it now being stable, I think we should do our best to help get everyone up and running. Here's a quick, appetizer to hopefully get your mouths watering.


The abridged, super simplified, solo mining HOWTO

Okay, this assumes you already have your rig built, OS and miner installed and configured. (I think that is a safe assumption for anyone who is waiting for a pool to come online.)



Solo mining, single rig

ONLY 3 THINGS TO DO:

• set up your wallet config file
• set up your wallet to run as a server
• set up your miner batch file to point to the wallet

Wallet config file key items: everything, but there's only 10 lines

Cut and paste what's posted here

server=1
rpcallowip=127.0.0.1
rpcuser=somesecretuser
rpcpassword=themegaultranooneknowpassword
rpcport=17772
addnode=213.229.0.41
addnode=193.77.159.166
addnode=113.168.158.16
server=1
listen=1
daemon=1

  into your diamond.conf file inside the same directory/folder where your wallet is found

Above the “rpcport” line, add the following line: rpcallowip=127.0.0.1

Change the rpcuser and rpcpassword to something of your choosing

Save it as diamond.conf.

when u restart ur wallet it will run as a server



Setup your miner bat/script startup file by SIMPLY CHANGING 3 THINGS: your -o -u and -p switches (everything else stays the same)

-o 127.0.0.1:17772
-u your chosen user name that you gave to rpcuser in your diamond.conf file
-p your chosen password that you gave to rpcpassword in your diamond.conf file

Save and run. You're now mining solo.




Multiple Rig Setups

All the same as above, except you need to:

In your diamond.conf file change 127.0.0.1 to your subnet, for example 192.168.0.* (that's the most common, you could go with 192.168.*.* when in doubt)

(Don't forget to create any necessary firewall exceptions on your wallet machine.)

Change the -o switch in your bat/script startup file to the IP of your wallet machine, followed by a colon, and the rpcport number used (for example 192.168.0.30:17772 )

And you're off and running mining.  



This was meant to be deliberately simplified so as to remove some of the fear from this 'endeavor' and encourage newbies to get their feet wet. Hopefully you'll all find lots of other helping hands here to help fill in the gaps and correct any mistakes I've made and/or add to what I've left out.

It's easy as 1-2-3. Good luck, and good mining!


And as nerioseole reminded us, there's a wealth of info out there, starting with google https://www.google.com/#q=multiple+rig+solo+mining , but I doubt you'll need it.

[imihal44]

thx...i will try solo mining...but still waiting my wallet to sync...

[popshot]

thx...i will try solo mining...but still waiting my wallet to sync...

No need to sync from 0 unless you're particularly keen to do so.

You can dowload and use a recent chain from OP (March,2015).

Here's a link for your convenience:
https://mega.co.nz/#!TI9nFZpC!gqigF7aDxgGtru0vQNCJKaO-xdGWDMuQuUyIYI0n08c

[imihal44]

thx...i will try solo mining...but still waiting my wallet to sync...

No need to sync from 0 unless you're particularly keen to do so.

You can dowload and use a recent chain from OP (March,2015).

Here's a link for your convenience:
https://mega.co.nz/#!TI9nFZpC!gqigF7aDxgGtru0vQNCJKaO-xdGWDMuQuUyIYI0n08c

yeah,i just downloaded it..it is full sync,and my diamonds are in wallet...will prepare and make solo .bat but with multiple rigs:)...thx

[feldenthorne]

Okay I've got all that in my conf file except the bantime=600.  What does that bantime=600 do?

Ban time is the number of seconds the client waits before trying to reconnect to "misbehaving" nodes. These are nodes that send nonsense packets to the client or the ones that send bad blocks.

You're probably good with the default.

[pokeytex]

Okay I've got all that in my conf file except the bantime=600.  What does that bantime=600 do?

Ban time is the number of seconds the client waits before trying to reconnect to "misbehaving" nodes. These are nodes that send nonsense packets to the client or the ones that send bad blocks.

You're probably good with the default.

Yes Noob - run the conf exactly as Cryptonit recommends. Good to have you on board.

Also, if you are still have problems syncing from zero block do as Popshot recommends:

You can dowload and use a recent chain from OP (March,2015).

Here's a link for your convenience:
https://mega.co.nz/#!TI9nFZpC!gqigF7aDxgGtru0vQNCJKaO-xdGWDMuQuUyIYI0n08c

-pokeytex

[Trimegistus]

Guys, where can I get the latest wallet for Windows?

Github only has the source code and Sourceforge still has the old one (2.0.4.0)

Am I missing something?

Thanks

[cryptonit]

Okay I've got all that in my conf file except the bantime=600.  What does that bantime=600 do?

You're probably good with the default.

guess we would not write it into our suggested default conf for no reason

[cryptonit]

Guys, where can I get the latest wallet for Windows?

Github only has the source code and Sourceforge still has the old one (2.0.4.0)

Am I missing something?

Thanks

we where in extended beta our download links will be soon updated with links to new wallet

[Trimegistus]

Guys, where can I get the latest wallet for Windows?

Github only has the source code and Sourceforge still has the old one (2.0.4.0)

Am I missing something?

Thanks

we where in extended beta our download links will be soon updated with links to new wallet

Ok, got it! Thanks

[cryptonit]

there will be another wallet 2.0.5.3 which will replace the Extended beta test wallet 2.0.5.2

please wait with compile ur own wallets until sources are updated which will happen in the next 48 hours

[NoobKidOnTheBlock]

Okay I've got all that in my conf file except the bantime=600.  What does that bantime=600 do?

Ban time is the number of seconds the client waits before trying to reconnect to "misbehaving" nodes. These are nodes that send nonsense packets to the client or the ones that send bad blocks.

You're probably good with the default.

Yes Noob - run the conf exactly as Cryptonit recommends. Good to have you on board.

Also, if you are still have problems syncing from zero block do as Popshot recommends:

You can dowload and use a recent chain from OP (March,2015).

Here's a link for your convenience:
https://mega.co.nz/#!TI9nFZpC!gqigF7aDxgGtru0vQNCJKaO-xdGWDMuQuUyIYI0n08c

-pokeytex

Thanks mate Finally got my wallet all synced up and finally mining this thing now lol Good to be on board this coin though, like I said it peeked my interest before and I'm kind of regretting not jumping into it when I had thought about it because I would have a lot more of them by now Well time to start minting these babies.  The minting stake is 50% annually right?

[pokeytex]

Okay I've got all that in my conf file except the bantime=600.  What does that bantime=600 do?

Ban time is the number of seconds the client waits before trying to reconnect to "misbehaving" nodes. These are nodes that send nonsense packets to the client or the ones that send bad blocks.

You're probably good with the default.

Yes Noob - run the conf exactly as Cryptonit recommends. Good to have you on board.

Also, if you are still have problems syncing from zero block do as Popshot recommends:

You can dowload and use a recent chain from OP (March,2015).

Here's a link for your convenience:
https://mega.co.nz/#!TI9nFZpC!gqigF7aDxgGtru0vQNCJKaO-xdGWDMuQuUyIYI0n08c

-pokeytex

Thanks mate Finally got my wallet all synced up and finally mining this thing now lol Good to be on board this coin though, like I said it peeked my interest before and I'm kind of regretting not jumping into it when I had thought about it because I would have a lot more of them by now Well time to start minting these babies.  The minting stake is 50% annually right?

Correct

[DMDCreeper]

I am hoping someone can answer a technical question.

I have a couple of HIS R9 290 ICEq X2 cards I use to mine.  For some reason when I mine diamond with them I cannot get the gpu clock speed to match the sgminer setting.  One of them, if I set gpu-engine to 1100 sgminer reports it running at only 847 and that's with powertune set to 20.  If I set powertune to 0 it runs at only 580!

This is only happening with diamond/groestl kernel and sgminer 4.1.   When I use them to mine other coins, they run at my clock speed settings and are actually noticeably faster than my other cards.

Needless to say, with the GPU clock running that slowly, the hash rates for DMD are very low, 15 mh/s compared to my other cards which get anywhere from 25 mh/s to 28 mh/s.  I'd like to use the cards to mine DMD  but at those hash rates, it makes no sense. I am better off mining another coin where I can get the most out of them.

I have tried moving them to different rigs but that didn't work.  I've tried AMD driver packages 14.9 and 14.12.   

My rigs are running Windows 7 64 although I doubt that matters.

I posted this once before and someone posted an answer about voltage.  However, GPU-Z reports the voltages are about the same as for my other cards. Unfortunately, VBE7 does not support R9 290s so I cannot see the BIOS settings to compare them to my other cards.  If anyone is aware of a BIOS edit/view program that supports the R9 290, let me know.

Like I said, I would like to switch these over to mine DMD but not at 60% of the hashrate.  I get 24 mh/s out of my 280xs.

Does anyone have any knowledge of this? 

Thanks.

[stillontop]

Hello DMDCreeper, I had similar issues. My solution was to update everything.

My setup consists of:

Catalyst 14.12
AMD APP SDK 3.0 Beta

sgminer 5.1.0 64Bit from w0lf:
https://ottrbutt.com/sgminer/master/wolf-sgminer-master-12242014.zip

thread here:
https://litecointalk.org/index.php?topic=17533.0

pallas optimized DMD Kernel v2, Tahiti GPU only: https://dl.dropboxusercontent.com/u/40353042/Diamond/diamondHawaiiw128l8.bin

thread here:
https://bitcointalk.org/index.php?topic=779598.260

I get 30,4 Mh/s with my 290x with no overclocking or overvolting, I:20

[davembg]

1100 is probably too high, try lower engine/memory rates and increase until mining is stable.
Every opencl kernel has a different impact/requirement on the GPU, diamond-groestl tuning is no more difficult than X11, etc.

Search this thread (and the web) for other's configs and consider using a Linux distro like BAMT or PiMP.
Windows is evil, and almost all crypto software for WIN is a port.

Pallas once noted that using pre-built wallets is not safe - I think that also should/would apply to miners.

I am hoping someone can answer a technical question.

I have a couple of HIS R9 290 ICEq X2 cards I use to mine.  For some reason when I mine diamond with them I cannot get the gpu clock speed to match the sgminer setting.  One of them, if I set gpu-engine to 1100 sgminer reports it running at only 847 and that's with powertune set to 20.  If I set powertune to 0 it runs at only 580!

This is only happening with diamond/groestl kernel and sgminer 4.1.   When I use them to mine other coins, they run at my clock speed settings and are actually noticeably faster than my other cards.

Needless to say, with the GPU clock running that slowly, the hash rates for DMD are very low, 15 mh/s compared to my other cards which get anywhere from 25 mh/s to 28 mh/s.  I'd like to use the cards to mine DMD  but at those hash rates, it makes no sense. I am better off mining another coin where I can get the most out of them.

I have tried moving them to different rigs but that didn't work.  I've tried AMD driver packages 14.9 and 14.12.   

My rigs are running Windows 7 64 although I doubt that matters.

I posted this once before and someone posted an answer about voltage.  However, GPU-Z reports the voltages are about the same as for my other cards. Unfortunately, VBE7 does not support R9 290s so I cannot see the BIOS settings to compare them to my other cards.  If anyone is aware of a BIOS edit/view program that supports the R9 290, let me know.

Like I said, I would like to switch these over to mine DMD but not at 60% of the hashrate.  I get 24 mh/s out of my 280xs.

Does anyone have any knowledge of this? 

Thanks.