Jump to content

NEWS
  • WELCOME TO CRYPTOCURRENCYTALK!
  • We've upgraded the website with a lot of new features!
  • 3 NEW THEMES! Click on the + Themes button above!
  • Notice about SOCIAL LINKS: UPDATE YOUR SOCIAL LINKS
  • New video section, add your videos: VIDEO SECTION
  • Advertising will be available shortly, hold tight.
  • If you have any issues with the new site, please submit a support ticket: SUPPORT
derrend

Easy One Line of Code CPU Pool Mining Setup DigitalOcean VPS Instructions

Recommended Posts

### IMPORTANT NOTES:

## If you do not have an address to send the coins you are mining to, you can download the clients from their respective websites if one is available or by cloning the directory tree from GitHub and following the instructions. You can even use google to look for an online wallet if one exists but you usually CANNOT send them directly to your trading wallets on sites such as 'Cryptsy' Taken from cryptsy website --> "Notice: Do NOT use p2pool to deposit directly to your Cryptsy wallets, as it will not show the address in our wallet and we will be unable to credit your account."

 

## Signing up for multiple accounts using the same info is against their terms of service. If you do this you may have your account removed by DigitalOcean and lose access to any coins you've mined.

 

## I have tested this script on the "Ubuntu 12.04.3 x64" droplet without a problem so I suggest you use that one. It's just as good as any other version, trust me.

 

## What this script will do:

# Ultimately, it will configure a freshly instantiated droplet ready for CPU pool mining right out of the box regardless of size.

# Prompt you to change the root password to something more memorable.

# Prompt you to create a non-privileged user with sudo privileges and set a password for it.

# Create a swap file and add it to your fstab for persistence over reboots.

# Download and install all required software plus some extra functionality such as ability to download megalinks with "megatools" for example.

# Download and compile a multi-threaded CPU pool miner compatible with the Litecoin, Bitcoin and Quarkcoin algorithms.

# End with you logged in as the new non-privileged user you created earlier located in the same folder as your compiled miner all ready for launch.

 

## Remember:

# Digitalocean still charges for droplets even if they are switched off, they must be destroyed to avoid fees.

# To save yourself having to rebuild droplets from scratch all the time, you should take a snapshot of an already setup droplet and just restore it whenever you need a new one.

# Digitalocean dont charge for snapshots.

 

## If you would like to inspect the source code it is available here

 

 

### INSTRUCTIONS:

## 01) Go to DigitalOcean and sign up for an account. <- Please use this link to earn me some credits for making this guide, better they go to someone rather than to waste :)

# Or you can 'tip me' at the following BTC address:

Tip_Me_QR.png

# 1TipMe1CTQ1igpqfspn6chAMKix8wVDxD

 

## 02) Create an Ubuntu 12.04.3 x64 droplet with the size you want.

 

## 03) You will be emailed an IP address and password with instructions on how to SSH into your new instance.

 

## 04) Copy and paste this single line of code directly into the root terminal window as soon as you log into a new droplet and press [ENTER].

wget -O setup.sh http://pastebin.com/raw.php?i=dZHyqRY9 && sed 's/'"$(printf '\015')"'//g' setup.sh > setup.sh.tmp && mv setup.sh.tmp setup.sh && chmod +x setup.sh && ./setup.sh
## 05) Once the script has finished you should find an executable file name 'minerd' in your current directory, this is your CPU miner!

 

## 06) Find a mining pool of your choice using google. 'P2Pool' isn't bad. It's on sites like these that you can find settings for mining pools, usernames, passwords, IP addresses so you know where to point your miner, etc.

 

## 07) The syntax for the miner is this. (when you are located in the same directory as 'minerd' that is).

./minerd --url http://whatever.poolyouwant.com:Port/ --userpass USERNAME:password
# So to mine litecoins using the settings displayed on p2pool.org would be:

./minerd --url http://p2pool.org:9327/ --userpass <YOUR-LITECOIN-ADDRESS>:Anything
# You can also specify a particular number of processor cores to use with the '-t N' option where N is the number of cores you wish to dedicate, this may be useful if using your home computer to mine for example. Leaving out the '-t' option uses all available cores by default.

./minerd -t N --url http://whatever.poolyouwant.com:Port/ --userpass USERNAME:password
## All done. Good luck in your mining endeavours. If the first pool you try returns errors try connecting again or try your miner on a few more pools before concluding your miner is broken. I find errors on mining pools are sometimes not uncommon.

 

## Also be aware that mining for bitcoins with your CPU is not very efficient now that the difficulty level is so high so perhaps targeting a newer alternative coin or 'alt coins' as they are known and exchanging them for bitcoins once the value of that alt coin has increased might be a better strategy since the difficulty level on these should be considerably lower.

Share this post


Link to post
Share on other sites

Sorry for taking over this thread, but it is not advisable to use cpu-mining for high-difficulty coins (such as BTC, LTC, NMC, etc).

There is no way to break even... Ever!

 

My oppinion is that those "cloud mining" posts have 2 aspects:

1) Help users understand how to setup a linux-based ecoin daemon (no GUI involved)

2) Get referral bonuses for the thread authors (which I think is the most obvious reason).

 

In other words, don't mine with CPU. It is not cost-efficient 

Share this post


Link to post
Share on other sites

i get an error when i put this 

 

sudo dd if=/dev/zero of=/swapfile bs=64M count=16; sudo mkswap /swapfile; sudo swapon /swapfilesudo mkswap /swapfilesudo swapon /swapfile

 

error bad syntx can someone help me?

"sudo mkswap /swapfilesudo swapon /swapfile" is repeat text and should be removed from the end of the command. I don't know why it repeated in the original post but i've fixed it now. sorry about that ;)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

×

Important Information

By using CRYPTOCURRENCYTALK.COM, you agree to our Terms of Use.