Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 552. (Read 1260677 times)

You're probably good with the default.

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.

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

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

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

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

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.

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?

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

-pokeytex

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

Compiles and runs fine for days with libboost-dev 1.54. I doubt it fails because of that.
Since you're compiling it yourself, don't strip the executable (compile the debug version) and run it through gdb to see where it fails.

I wonder if it has to do with the new libraries like boost 1.40 and boost 1.55 or  ?? after the distro upgrade I wasn't able to use the older libs.

Hey quick question I downloaded the windows qt wallet from the main page and I added the diamond.conf file to the folder and now my wallet is stuck syncing on block 121045?? Does anyone know why this might be or possibly a way that I can fix that?

If you take a look here https://chainz.cryptoid.info/dmd/#!extraction you will notice that there are 3 public pools danbi's, MiningField US and Donkey's . the first two are the biggest and both operators are part of the Diamond community. Not sure about the Donkey, but haven't heard any complaints about that pool.

Even though there is no risk of 51% attack coming from the biggest two pools it's always advisable to spread hash among different pools.

You can of course mine solo and possibly get best results, but to do that effectively you need to have a reasonable amount of hashing power.

We're gonna have sharp reward reduction soon so better hurry with mining, you won't be able to mine as many coins as you can now.  

@Spidersbox u run into same problem with old and new wallet version
old wallet version is used by a few pools without issue

so i expect something at ur setup/compile must be different to them

maybe someone who runs a pool can give ya a hint what might be the difference

it would be good if one pool owner upgrade to new wallet and confirm it runs fine