Correct.
Alternately, you can make a master wallet file on your computer, then copy it to each of the nodes. That way, you and all your nodes have the same wallets and you don't have to go fish addresses out of the nodes. If you go this route, be sure to stop primecoin, copy the wallet, then restart primecoin.
You can use WinSCP to transfer files to/from your nodes. Your login info will be the same as your PuTTY info.
Before I do something extremely stupid.. This is what I am doing. 1. From the regular primecoin client on my pc , I did Files>Backup Wallet and got the wallet.dat file 2. Then I used that wallet.dat file to replace .primecoin/wallet.dat file in the VPS using the ftp client. That is what you meant right? Sorry for too many questions Btw...if I have just cloned a droplet 3 more times, all 4 droplets have the same wallet.dat. Can I not just grab one of those wallet.dat files to Primecoin client on my PC? You are correct on all counts. As long as all the nodes (including yourself) have the same wallet.dat file, they should stay in sync up to ~100 mined blocks. I'd also recommend that you restart the haveged service. I noticed that it doesn't always run automatically after installation. You can accomplish this with: You can verify it's running with ps aux | grep -v grep | grep haveged |
|
|
|
"blocks" : 106059,
"chainspermin" : 21,
"chainsperday" : 2.44443307,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 9.59809953,
cant say that i find 2 blocks per machine per day.. i am lucky to hit 4 blocks per all 6 mashines per day (All are identical)
If you set up one and cloned it, you may be dealing with conflicting / insufficient entropy. Quick and easy fix: apt-get install haveged -y
update-rc.d haveged defaults
service haveged start |
|
|
|
In case you are interested in the validity of the chains per day metric, with the following setup running on 9 identical machines I managed 8 chains over 24 hours. 8/9=0.8888 chains per day. I would say, close enough for government work in this case. "blocks" : 105938,
"chainspermin" : 3,
"chainsperday" : 0.92945471,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 9.59519291,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"roundsievepercentage" : 70,
"primespersec" : 1707,
"pooledtx" : 0,
"sievepercentage" : 10,
"sievesize" : 1100000,
"testnet" : false Lucky you then. I have 8 machines running at ~1.0 chains/day + a few spare machines on the side. I got 3 blocks in the last 24 hours.  |
|
|
|
So..I have to wait a bit before I can merge the accounts and get private keys from ./myinfo. Till a block is minted..right?
I just got got into bitcoins and cryptocurrencies, this is the first time I am mining (any cryptocurrency).
Correct. Alternately, you can make a master wallet file on your computer, then copy it to each of the nodes. That way, you and all your nodes have the same wallets and you don't have to go fish addresses out of the nodes. If you go this route, be sure to stop primecoin, copy the wallet, then restart primecoin. You can use WinSCP to transfer files to/from your nodes. Your login info will be the same as your PuTTY info. |
|
|
|
Please do not rip me apart, I am one of those complete noobs this guide was written for. I have started mining on a DigitalOcean Droplet. The primepersec is 528 (just in case anyone is wondering) I have a few questions - 1. Using your tutorial on merging the primecoin accounts. I can open 3 other droplets, follow the same instruction to setup Primecoind and merge the - right? 2. The ypool droplet - do I have to keep the putty open? I saw someone complaining that they cannot mine as soon as they close the putty. 3. Amazon EC2 instances are the same thing as Digital Ocean Droplets right? will this work there too? I found this one some forum.. http://aws.amazon.com/big-data/powerof60/terms/ and was planning to use it. 4. If I signup for Linode , I would like to have a gigawatt's referral address. Since you took the time for us noobs, you deserve it. Edit: I just noticed that his links are already referral links and that is totally fine by me. You deserve it sir! Edit2: the command ./myinfo doesn't seem to work. Thanks for enjoying the guide! I'll do what I can to help: - Yes, that's correct. I would recommend a different approach though. 1) Make one node, get it running and updated. 2) Shutdown the node and take a snapshot of the node. 3) Create a new node based on the snapshot. That way all the cloned nodes will have the same wallet files and should stay in sync up to ~100 mined blocks.
- For the ypool one: no, you shouldn't have to. I have the script setup to run in the background, but the catch is that you can't "see" it work. You can only verify that it is doing work, not necessarily what it's accomplished so far. If you have doubts, run the start command in one session, connect with another PuTTY session, then check ps aux | grep miner.
- Yes/no. They're similar, but as others have noted, Amazon EC2 instances require using sudo commands in certain places. If I recall correctly, it should be for each apt-get call. (So change apt-get install blahblah to sudo apt-get install blahblah)
- I personally prefer Linode as well. $20 gets you an 8-core system vs $5 for a 1-core. The only drawback I've noted is that Linode doesn't let you "clone" nodes very easily, so you'll have to run the setup for each node.
- As for ./myinfo: it only dumps the addresses that have a transaction associated with them. Transactions also include minting a block.
If you start having a handful of nodes to manage, I would recommend downloading multi-tabbed PuTTY. It'll let you opened tabbed session for each VPS and send commands to all of them at once. |
|
|
|
|
Well, block payments just dropped below 11 and difficulty passed 9.54
It's amazing how much a software update and better parameters can get you.
On that note, I'm starting to think the chains/day measurement is becoming less accurate. Either that or I've been quite unlucky.
|
|
|
|
|
Wow, I just shot myself in the foot today.
I set up a new node to test out a ./notify-block script.
I had it enabled right from the beginning, but about 20 minutes in things were going really really slow.
Turns out that when primecoin was downloading the blockchain, it triggered the notification script about 90,000 times. Oops.
|
|
|
|
Another round of updates!
Pic Here.error: incorrect rpcuser or rpcpassword (authorization failed) Usually that error is from editing your primecoin.conf file before stopping primecoin. I've tweaked the ~/stop-primecoind script so it force kills it if it doesn't shutdown gracefully on it's own. |
|
|
|
Send a message to gigawatt. He's got some cool settings to optimize EC2 instances.
You say that, but it's more of a setup script. It's in my signature if anybody is interested. I'll probably post an update in a bit. |
|
|
|
What's the default keypool size? Is a key only "used up" when a block is found?
A key is the magic number that allows you to spend the coins at an address. When you find a block it uses up an address/key. But I've mined multiple blocks with the same address... so wouldn't that prove the "used up" aspect incorrect? |
|
|
|
You could also use your wallet until addresses diverge or increase the keypool.
Could you elaborate on this? primecoind --daemon --keypool=10000 I get that part. What did you mean about the addresses diverging? As long as each node has the exact same wallet, that shouldn't be a problem, correct? |
|
|
|
You could also use your wallet until addresses diverge or increase the keypool.
Could you elaborate on this? |
|
|
|
Does hp8 compile with only 256mb of ram ?
No. Compile in a 1 gig of ram machine and then move the compiled script to your 512mb one. Sounds like somebody needs to make a swapfile. This will make a 1GB swapfile so you can compile on < 512mb RAM. sudo dd if=/dev/zero of=/swapfile bs=64M count=16
sudo mkswap /swapfile
sudo swapon /swapfile |
|
|
|
Does running multiple machines using one worker on ypool cause any problems?
Nope. (Unless you're pointing a few thousand machines at it) |
|
|
|
I've updated my awk command to include the new chains/day statistic: grep primemeter ~/.primecoin/debug.log | awk '{s1+=$4;s2+=$6;s3+=$8;s4+=$10} END {printf"%10s: %10d\n%10s: %10d\n%10s: %10d\n%10s: %10.5f\n","Prime/h",s1/NR,"Test/h",s2/NR,"5-Chain/h",s3/NR,"Chains/day",s4/NR}'I apologize for the fact that it's an abominable one-liner. If you don't know what grep or awk are, this probably isn't for you. |
|
|
|
Didn't try, the script is almost working out-of-the-box, you also need to "sudo make install" for gmp.
FYI, XPM priming (hp8, Ubuntu Server 13.04 64 bit) on Amazon EC2 with High-CPU On-Demand Instances:
- Medium (1.7 GiB of memory, 5 EC2 Compute Units): ~1,1kPPS
- Extra Large (7 GiB of memory, 20 EC2 Compute Units): ~4.5kPPS
I think that also may apply to the apt-get commands too. I'd recommend running benchmarks on a few different parameter setups, you'd be surprised what kind of performance you can get. On a 1 CPU (2.4GHz) DigitalOcean droplet, I can manage ~120 5-chain/hr or about ~1k PPS with optimized parameters. Assuming that keep your debug.log file relatively clean ( echo "" > ~/.primecoin/debug.log before you start), you can use this to calculate your running averages: grep primemeter ~/.primecoin/debug.log | awk '{s1+=$4;s2+=$6;s3+=$8} END {printf"%10s: %10d\n%10s: %10d\n%10s: %10d\n","Prime/h",s1/NR,"Test/h",s2/NR,"5-Chain/h",s3/NR}' |
|
|
|
|
It's called the blockchain, and it's the entire "blocks" directory under your primecoin folder.
Right now it's only ~70MB, so it's not too big.
If you're not 100% sure, you can copy everything over but the wallet.dat and the "testnet" folder (if you have one).
|
|
|
|
testing this right now on a linode, we'll see how it goes  Edit : you might get prompted with a EULA & asked to accept the terms, just press <TAB> and Enter to 'press' OK in Putty I totally forgot that I had to deal with that. I actually had to go look it up myself. I'll update the guide. |
|
|
|
This guide will be a bit shorter than the last two, mainly because I'd consider this in "beta" right now. For the time being, I wouldn't consider it 100% "noobproof". The key differences between my previous guides and this one are: - When you sign up for your DigitalOcean or Linode account, you must select a 32-bit version of Ubuntu 13.04, not a 64-bit one. jhPrimeminer was built for windows, so to run it on a *nix VPS it needs to run on Wine. Wine has major issues installing on 64-bit Ubuntu.
  - Because this installation uses Wine, there's a limitation when it comes to running the miner. You can either:
- Watch the miner as it runs in the foreground, but have it stop if you close your session
- Have the miner running in the background regardless of if you're connected but not be able to watch live results
- Have the miner running in the background, be able to watch live results, but have the miner run at half speed
- This setup opts for the 2nd option. The miner runs in the background and you can check your progress on yPool.net
Getting Down to Business- When you create your VPS node, be sure to select Ubuntu 13.04 x32 (not x64)
- Copy this script to notepad and modify the fields at the top of the script. (Highlighted version)
- YPOOL_USERNAME is your yPool username AND worker. It usually looks like "username.workername".
- YPOOL_PASSWORD is your yPool worker's password, not your login password. Usually, it's "x".
- YPOOL_SIEVESIZE and YPOOL_PRIMES are parameters for jhPrimeminer
- Connect to your VPS node via PuTTY, then paste the script.
- Once the script finishes, run ./peek to verify that the jhPrimeminer process is running in the background
NotesIf the parameters for jhPrimeminer change (or if you decide to use a different mining client), you'll need to modify the ./miner script and add them. The ./miner script automatically detects the number of CPU cores available and utilizes all of them. This works regardless of if you've selected a 1 CPU plan or an 8 CPU plan. If you get a message about accepting an EULA, press TAB to highlight the OK button, then press SPACE. Please feel free to let me know if you have any questions, but do keep in mind even though this script is tested and working, it's still currently in a beta phase. Thank you for your cooperation and understanding. Enjoy your Primecoins!  |
|
|
|
Don't expect many blocks using a VPS given the high difficulty now. Also since the price is so low, I doubt if it is really profitable.
People said that about Primecoin too, but I'm looking at 5 minted blocks in the last ~24 hours, so I'm ok if you'd like to sit this one out.  |
|
|
|
|
Show Posts
