Many of those algos are chained together in what is X11, X13, X15, being that X11 has 11 chained algorithms, x13 13 algos etc. Maybe you should check out www.getpimp.org for a mining patform that supports mining many of these new algorithms. Each algo will give a different hashrate, so answering your question is pretty hard. You'll have to read up on what you would like to start mining and find your card settings and compare. |
|
|
|
For larger GPU setups, open air rigs and riser cables are pretty much the only option. I used to have something like this, albeit a much smaller scale. One can connect 6-8 GPUs to a motherboard with the use of extended cables, risers and multiple PSUs. So, for a larger setup, 6-8 GPUs per frame, and then you add more frames as you go.   |
|
|
|
What a great promotional video! Excellent work and it will surely help many new (and old!) users to cryptocurrencies in general and Dash in particular! With the promotion budget approved, I'd love to see more high quality pieces like this come out  |
|
|
|
........
Having approx 500 MN I get to see examples of this and a couple did go to 13 days before being paid, I raised the isue with Holger:
MN 216 & 311 are now 12 days without reward, I assume it's just variance but maybe best to make sure that they're Ok:
XqqkU2z7LjKz2NGMSnoNrq3yrL8Bwc4y1b ENABLED 8 minutes ago 8/19/15 3:14 PM in: 63 out: 62 12 days ago 0.00000
XikUPCjJ6wkpHQu6CKX9gvX5hU3Wyp6NN2 ENABLED 6 minutes ago 8/20/15 12:33 PM in: 62 out: 61 12 days ago 0.00000
XoKfP4uRUYNfpoQhjzAJA9jXsPV1to9WJA ENABLED 13 minutes ago 8/19/15 3:21 PM in: 40 out: 39 9 days ago 0.00000
XuvT2eupfEn5CKYkwBbEjkVbdcYLFixetm ENABLED 11 minutes ago 8/19/15 3:17 PM in: 63 out: 62 7 days ago 0.00000
XkmezdKHMAT9jN96pPMxByQPnARDpK5jFw ENABLED 6 minutes ago 8/19/15 3:12 PM in: 65 out: 64 7 days ago 0.00000
XqXsjYX9EDSNRDjyJdv5u1rbb9r2KLvoH8 ENABLED 9 minutes ago 8/19/15 3:14 PM in: 75 out: 74 7 days ago 0.00000
...
Interesting and helpful information Otoh, with such a portfolio I see that you get a great insight in how the payout system is working. ---------------------------------- also, a few hours after my post my masternode got it's payment... maybe I should have posted earlier? Everything seems to be working. Note to self: just wait and stop worrying  |
|
|
|
RE: WastedLTC,
$ dash-cli masternode winners 2000 | grep Xb7qiTRzJJewfby9eXGeAcYMN7RNGgPnBw
"333774" : "Xcaj3MuJNCYWy5GQD3LxBq4fsc2X9h5obW:8, XdcKK8eFkabsHGrngymy3zfUKgQe2ZE7jv:1, Xb7qiTRzJJewfby9eXGeAcYMN7RNGgPnBw:1",
"333828" : "XfThq3Rj9w1cnsUk7aAdPqnniV7Fexq1A2:9, Xb7qiTRzJJewfby9eXGeAcYMN7RNGgPnBw:1",
I guess someone else got more votes, thing I dont understand is, don't the people in the pool that didn't win, get put back in the pool for another chance? Gotta Read eduffield's post again....
When you see 1 vote, that's not enough to actually make the system skip. It skips on 2 or more. Exactly, so why isn't he paid in 12 days? I see nothing where he won 2 or more votes. His MN payments seem to have been regular untill 01-09-2015 at which he made a selfpayment of 28,5 Dash, making his balance 1000 again. At this point i would seriously think about stopping the server and at least remove the peers.dat & mncache before restarting it, maybe some clients got him blocked ? More draconic measures would be to delete everything (except dash.conf & wallet.dat & masternode.conf) and resync from scratch. Then keep an eye on the number of votes that masternode is getting afterwards with command : "$ dash-cli masternode winners 2000 | grep Xb7qiTRzJJewfby9eXGeAcYMN7RNGgPnBw" to see if it gets more votes. sound suggestions, thanks! Thanks all for taking notice of my issue and looking into it. I assume this is not the only MN that is having this "luck"? My other nodes have had no issues and now we are passing 13 days with no payment. We are waiting a bit longer and then we will just wipe and restart that server which will end up taking longer than the permitted time and shove it to the back of the list. Might be close to a full month without a payment which .. well, we all know that sucks. =) It would be nice to find out why this happened so it doesn't happen to many more nodes. thnx all! It sucks to be without payment for so long! Personally I am at 7+ days at the moment since my last payment, and running dash-cli masternode winners 2000 | grep Xk8KPR6WrSiKGW6PDyBUsmHeYxagL5pVJu gives no output. Only when listing the previous 5000 winners does my masternode show up for block 331905. I don't know the status, but there was a comment that nodes could "restart" for some unknown reason. And whether they used masternode.conf for starting could affect this or not. I am still waiting for s official statement about this, but so far I have not heard any news. My masternode has otherwise been running for more than 3 weeks according to dashninja, and I have not had my cold wallet opened since it started. So, I'll just wait and see what happens. Coming up on 8 days is the longest I have waited yet, but it's still a bit to go before hitting 12 days! |
|
|
|
I suppose that they are in a hurry, being that they will soon not be available due to "climate change" |
|
|
|
|
This is just as much as an experiment in human behavior as it is testing the Bitcoin network.
People panicing for free BTC while blockchain.info taks a hit.
Anyway smart played from coinwallet.eu, let the people do the legwork.
|
|
|
|
So far the list of private keys and their associated Bitcoin address: 15RuRxJWbFZSCEMHRQXna3cZW7A8RXUU53 : KxTn6JTCcu7DgbJsoMnoVNc6bAaYWAEggtFjuwy9zQEP576Cr1Ee
19Fua2AHaJ82P3vorNyhHe9aFi3aYAEY8x : KxSzV3yCyaQEufJ8PQkkk8FvF4tKcwh1mpbumTjCJt3UPoc9QjAT
18Ke1cYQKwfx1QS397Ze2Lw6Zhfdj4m335 : KxvN1EWmuAPTPuVft1HBCsVgKzBG2hzn3hPfnpThCoZ8rwrwGyLo
12dGLRtZvvVzATPPkht5R8icr2wiQc8xBS : L5kUSSyU9v4dY82nkDzpJcVesZvJftvsmLMQEYSrL71LPbKKjDLe
1NT5z4ujJVvpAve6vENr8YKjW8ejd1y9vW : L1J7tM78SyDXYchdFmLLZafxz3TW36fHnK9QYKxQjsvC6VmkLTX2
175hfo7BQLmZvBAgLW4Hs2gtVNJj13eXRK : L3Yyqu7PXsn74AYUWp3iom4GHVR3MxeNEigMcYVvf3jPoP8Vf1YY
1LtQMbHKAorqVFGJUfy1S9fmMkfXWQxuHH : Kzv9m5Dvf6MLo3PsjBCwUETG4p667ScEs2t3wfUHx7wpYtLxphYN
1J1npARAR39Bo5xnh6265ZN8aqta36qm6g : KxrZ7GWwMQggTUT1kCKJykwWP4j9w2QJAdq7ZzBHgR2ZxVxnVPGD
18QhEALNPE1hGD7riLy1Add51C36P5yRya : L32dWAJV4TFr1UZucUh4dRP2GaSttgsTPEs5VZSBDWmNzM7X56YZ
1NJ5pJTGhtu8m3QZadAEPsBWS3ucAf8yiH : L2pFTGoiefeApRpoBENebddkdac9ZjVqDZrBmKTUuJPB4Gk2NR7w
1JHN9q3vPe25NPzjXX4u1SiAUem6FShu3z : L1JgvFFgUi1MLCaq5ToXR16es8KrbpakV8mWZRvfebHiaeabNuJB
1JYMqE28v6KUW51f5yAj43nQichntQ1yz2 : L1uxiDhGgDDLqcmof1D3sbGqe9aZTNnkAPtHnPGbFKE5kgSiJi73
15yraqng57fKrHMjuQmxZSKAjvPfrFRVeM : Ky4MMN1D6YsBi9whrMiQCzKFSV5rRajozPDFnAbTjSKzLygYdQcK
1E6v5j2xVfQtNriKFe61ytoYzc75U3wL9t : L3MwcPy9gc6VmfuHyR3EtHjkyn7gq2q5hyG38MAfdwsZmYQriV63
1K5LLbrwYoXRb4cg1eGatG5qtTDGfkSScX : KwMd5sbn2Rg4MrEtVaCMGkCtrZTHPzS7eSut8Q7Y4uCMhsrD2teF
1Dd2s5vNJqELGawEMPvSguhGbX2byt8FUn : L4VZSCJsYMA2d8NBcKJFQGUf9j1vBbq3VuQkqnkRkWSRJZnUzxMU
1Dc8eheByee3hh5dPu6BQ15zekDTHh2C8a : L3gGhY6DQtVRvkQTbqndXeBH9ehzCxVzUazpUPCrbLAS9W4ce8Rt
14WCrzmqVCD7Thf79vutWTB6y1hUc8pP19 : L4pvdFwouE864kVLgScmbpDZVZxm7w1LzA5jmGqRKDaT931xnvyF
1NvdMgwXMcCyMeG26VpwhSHYez3aEXQFKP : KwnVPvvyjxGBga15mrT5NcddYtDxThUndQ5e17kuoYc2iYHBL6Xv
1Hh3abLFg2RgMD5Gi3JSxn6fCgiAf2JJbg : L1T5ZRa5byi9NbbMbymv6Q3UQy6isnEZ8nwFNBbTKVA7mhgtjSjh
1JLd3YMioeYYENoukbsyHCeaN21CYxDqR : L2VwYXcWkXuk93PPwWQZgxahtAcPsun5ao8yHNnwZz96EVBaydos
1AiSe5Ky9gEBdyJe1r2Bwh2n3SMv4oZ9RA : L3MJzCf6U7LDzWvYRpAeZdnD2BfsRDrUYtzrr4PWLWg9Yb7MDfTf
18cif9QYoSPSrmv9MN157mUejyNMr5wYVx : L2HcNb8wPCQ2gpL4oT5Mn6cvKqfAFjCqK3qWquak9BvYasbgWxxF
1PGoidScvGLp6LRgVgZoAdWxvMruZWhavC : L4KepuTEJRZgbZDtZM2zbbVE6JZu2f7ihtDWEDGjBnV3R1yQVTPd
1KDAsGVFGMruzJHpS7QQ5Jzy3ooVMSbXyw : Kwwn4imBfo9eqDcvaoSvUjDDVKRQGMdfkJT7y4YV1A29sC4jsj6Y
1EuMU9jGTJUzQN3xhhCdybKbvvoayMkSY8 : L3PjeCNMrW4AKJ6QVgkj5RozpdhHeM8Zo7DUZUUsXAR4kQKEDNgK
1Mxpfmy7Mhkr8K3GLJ1G2WaPBdvXsAxYtD : KysBwc1VSj1V5cG3EqLUixwLQjB2we2WUneYuhTxkAy5ANCbpvyc
14zpoo6FfuY9x6yRnA7rA3qwGghPpcrMUp : L1VKFTepC6gSabHQi2uVjueQRqbhWgakJsifsSPCkXwd988GgP9a where did you find those? They are on the first and second pages of this thread. |
|
|
|
.......
Dashwhale Android and iOS apps are currently in app review process and will also make mobile masternode monitoring a breeze.
Wow, sounds great Dashwhale! That's a feature that I definitely will be looking forward to! |
|
|
|
|
@moocowmoo Working great as usual. Thank you for the update!
|
|
|
|
Probably bad news for everyone running their nodes with "masternode start" (i.e. using local dash.conf): I guess there's a bug with masternode self-activation somewhere. If you are using local dash.conf to start your remote masternode do NOT run this local wallet while masternode=1 is still in local dash.conf, I think it will try to self-activate for some reason and will drop your node to the end of the queue. Either set it to masternode=0 before you run it OR better option would be to use masternode.conf even if you only have one masternode. Sorry about that  PS. Code there became a bit messy actually because of many different options. I think we should stop using this one, clean it up and stick to masternode.conf method only to activate remote nodes while old dash.conf method should only be used for activating local Hot masternodes from now. PPS. Users with masternode.conf setup should not be affected by this. https://dashtalk.org/threads/v12-release.5888/page-52#post-66578Thankyou for this information UdjinM6, this could perhaps explain why some payments have been intermittent. I'll have to check my setup, unfortunately I had the cold wallets sync up yesterday. Would have been a downer if this put my masternode last in queue again. |
|
|
|
Interesting blogpost, thanks for sharing the link! ~50 Dash per day is some serious mining power. Unfortunate people who are running bad torrents on oversized gaming rigs... |
|
|
|
..... My setup is this: mkdir ~/bin
ln -s ~/.dash/dash-cli ~/bin
ln -s ~/.dash/dashd ~/bin
echo 'export PATH=~/bin:$PATH' >> ~/.bashrc
With my single addition of ~/bin to PATH (the .bashrc addition), adding things to the search path (run anywhere) is just a matter of symlinking them into ~/bin ...... Thanks for the tip! So I decided to bite the bullet and use a local ~/bin and use symlinks from there. Apparently .bashrc and .bash_profile didn't exist for my user, but once these files where setup and paths added, everything seems to work as expected. Thank you once again for a great tool moocowmoo! |
|
|
|
Working great moocowmoo! May I perhaps ask for a future feature? When looking for the dash-cli path, could we perhaps make a local setting that is not overwritten after each update? I am running the dashd and dash-cli binaries in a local folder (not in path) rather than in .dash I was thinking if we had a dashman_local.conf where the paths could be specified. if this file is not present than the dasman tool looks into .dashman-functions.sh for the "normal" paths for the binaries. Additionally, when updating dashman or making a new install, the dashman_local.conf is not created/overwritten so the user must make this modification themselves. I am aware that this takes some time to create so if you are too busy or think that this is unnecessary, I will continue to adjust my paths by hand  |
|
|
|
So, I just saw that the latest release on https://www.dashpay.io/downloads/ is back to v51 again. Was v52 released prematurely or was there some problems with the updated daemon and wallet? Should we who have upgraded to v52 roll back to the older client again? |
|
|
|
WOWZERS !!
...
Sorry to hear that GhostPlayer, I for one enjoy the insightful postings of the people hear in the Dash thread, and I appreciate the info even if the posts relate to other topics. Not everyone has the time to keep track on all other topics, so I thank you for your posts even if they have now been taken down. |
|
|
|
Is there a simply guide how to build the Dash Linux daemon from source?
i read the instructions in the source but I was having building problems and thought that there might be something that I was missing or that the build environment is incorrect.
This one https://github.com/dashpay/dash/blob/master/doc/build-unix.md ? What kind of build problems did you have? Post error here and we'll try to help. And btw, check "Dependencies" section there first. Thanks UdjinM6 for the pointer, I'm checking it out and correcting a few errors; I had the wrong version of libdb and also no swap space. Fixing these problems and trying again. Update: seems now that when running make, it crashes when attempting to build libbitcoin_server_a-main.o ~/dash_git/dash$ make
Making all in src
make[1]: Entering directory `/home/****/dash_git/dash/src'
make[2]: Entering directory `/home/****/dash_git/dash/src'
CXX libbitcoin_server_a-main.o
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[2]: *** [libbitcoin_server_a-main.o] Error 4
make[2]: Leaving directory `/home/****/dash_git/dash/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/****/dash_git/dash/src'
make: *** [all-recursive] Error 1
****@masternode01:~/dash_git/dash$ free
total used free shared buffers cached
Mem: 501800 174040 327760 16 1780 25236
-/+ buffers/cache: 147024 354776
Swap: 1048572 205620 842952 In most cases this "g++: internal compiler error: Killed (program cc1plus)" means you need even more memory for compiler otherwise OS see that it running out of memory and kill the heaviest process. Make swap 2Gb for example and try again (I have 4Gb just in case). Thanks a lot sir! This indeed was the case, I changed the swap to 3GB and the compiler error went away. Cheers! |
|
|
|
|
Show Posts
