Download - Bitcoin

How to get a public static ip for your local lightning node

My lightning node is a node that is running locally on my server hardware in my house down under, far from the New Jersey Digitalocean datacenter, which is what will come up if you look up the ip of the node. This is done via an OpenVPN tunnel from your local machine to a VPS. I am doing this by renting a VPS from Digitalocean for $20 a month (2 vCPUs, 2GB RAM) running Ubuntu 18.04. You can do this just as easily on a $5 a month VPS with 1 vCPU and 1GB RAM or even a $2.50 a month VPS from Vultr with 512MB RAM. I needed the extra power because I have many web services running there as well.
This setup allows me to have a highly available lightning node, not affected by my home IP address changing. If you are using a mobile connection or have a CGNAT, you wont be able to port forward for your lightning node. This setup allows you to do so. You can also use this to make a portable lightning node, which can get you a full lightning node wherever you have power and internet, without having to mess with network settings. If you don't want others to know your home IP, this is a good option for privacy.
  1. Setup a local lightning node, preferably on a linux machine. I followed the Raspibolt tu`ial (with some tweaks) on a 2 vCPU and 8GB RAM VM running Ubuntu 16.04.
  2. Get a VPS with a static IP address. Digitalocean and Vultr VPSs already are. This VPS wont need much power, so get the cheapest one you can.
  3. Secure the VPS. I used this tutorial. Essentially, setup a non root user, use ssh keys, and setup ufw. Also make sure to allow port 9735 through ufw for lightning. I also additionally made adjustments to the ssh config and installed fail2ban.
  4. Setup an OpenVPN server on the VPS. I used this tutorial.
  5. Install on OpenVPN client on the local linux machine and connect to the server. The tutorial from step 4 shows how to this. Keep this connected for step 6.
  6. SSH into the VPS and figure out the OpenVPN IP address of the client. It should be 10.8.0.x. To figure out the x, setup a simple python web server or something on the local machine on port 8000 or something and open the port on ufw in the local machine. Keep the OpenVPN connection, and use a new ssh session when accessing your local machine. Don't kill the OpenVPN connection, as it may complicate things when finding the ip.
    mkdir testweb
    cd testweb
    echo hello >> index.html
    sudo ufw allow 8000
    python -m SimpleHTTPServer 8000
  7. SSH back into the VPS. Run the curl command below, and try all the numbers between 2-10 for x. When you get hello as your output, then you found the right IP. I found mine at 6. You may have to try higher numbers, but this is unlikely. You can kill your python webserver on your local machine once you find it.
    curl 10.8.0.x:8000
  8. Once you have the IP, you want to make this static, so it doesn't change when you reconnect. This is done on the VPS side, so ssh back into the VPS. This tutorial worked for me. Just make sure to change values like the CommonName and and the IP to match yours (client1 and 10.8.0.x). If it doesn't work search "make openvpn ip static" and look around.
  9. SSH into your local machine, and make the OpenVPN connection persistent. You can kill the OpenVPN connection now. Doing this and this worked for me. If it doesn't work search "openvpn keepalive" or "openvpn auto connect linux" or "make openvpn connection persistent linux".
  10. Restart your local machine, and make sure it connects on boot. Do the python webserver test again, and make sure the same ip is shown on the VPS, and it is still accessible.
  11. SSH back into the VPS. Now, you have to port forward with iptables. you have to add the 2 lines below starting with -A PREROUTING in the same place in your /etc/ufw/before.rules file. Here is what mine looks like. Change the x to your OpenVPN IP. Do sudo ufw disable and sudo ufw enable to restart ufw to update your changes.
    *nat
    :POSTROUTING ACCEPT [0:0]
    -A PREROUTING -i eth0 -p tcp -m tcp --dport 9735 -j DNAT --to-destination 10.8.0.x:9735
    -A PREROUTING -i eth0 -p udp -m udp --dport 9735 -j DNAT --to-destination 10.8.0.x:9735
    -A POSTROUTING -s 10.8.0.0/8 -o eth0 -j MASQUERADE
    COMMIT
  12. SSH into your local machine. Change your lnd.conf to match with this setup, like changing the externalip. Here is what my config looks like, a slight tweak from the Raspibolt one:
    [Application Options]
    debuglevel=info
    maxpendingchannels=5
    alias=GCUBED [LND]
    color=#68F442
    listen=0.0.0.0:9735
    externalip=157.230.95.74:9735
    [Bitcoin]
    bitcoin.active=1
    bitcoin.mainnet=1
    bitcoin.node=bitcoind
    [autopilot]
    autopilot.active=1
    autopilot.maxchannels=5
    autopilot.allocation=0.6
  13. Do a sudo service lnd restart to restart lnd and apply the changes. Remember to do a lncli unlock after any restarts. Your lnd node should now have a public static ip. Look it up a few hours after you do this on 1ml, your ip should be the one of your VPS now.
I am monitoring this for free with uptimerobot. It will notify you if it has gone down. So far mine has been running for 3 days and hasn't gone down.
EDIT: Formatting
EDIT 2: The main reason I didn't use a ddns or a hidden service was mainly for high uptime, and low latency. I am planning on developing a lapp with this node and I didn't want to risk any downtime. Running lightning as a hidden service is a great idea as well, this tutorial shows how to achieve something similar with the clearnet.
EDIT 3: You can achieve a similar result from using TOR
submitted by ggelango to Bitcoin [link] [comments]

Bitcoin Rhodium Mining Guide

Bitcoin Rhodium Mining Guide
Happy Mining!

All available XRC pools can be found on MiningPoolStats

Bitcoin Rhodium Mining Hardware

Baikal Giant+: 1.6 GH/s
Baikal Quad Cube: 1.2 GH/s
Baikal Giant: 900 MH/s
Baikal Quadruple Mini Miner: 600 MH/s
Baikal Miner Cube: 300 MH/s
Baikal Mini Miner: 150 MH/s

Mining Setup

To mine Bitcoin Rhodium you need to set up an XRC wallet and configure your miner of choice. You can choose between Web wallet, Electrum-XRC or Magnum wallet. To set up a web wallet please visit wallet.bitcoinrh.org. Or download and install Electrum-XRC wallet (recommended) for Windows, Linux and MacOS.
Web wallet: wallet.bitcoinrh.org
Electrum-XRC wallet: electrum.bitcoinrh.org
Magnum wallet: https://magnumwallet.co

Sign up for XRC web wallet if not yet done so

  1. Create an account, with your username, password and secure question.
  2. Sign in and click “Create Wallet”.
  3. Set up a strong transaction password. Make sure you store it securely in a secure password manager of choice.
  4. Copy the seed somewhere safe. It’d be a good idea to write seed on a hardcopy and keep it safe.
  5. Paste it to confirm you got it right.
  6. Grab an address for the mining step. Your wallet is now ready to mine XRC.

Instructions for mining XRC on the official pool

Pool link: poolcore.bitcoinrh.org
  1. Any miner that supports X13 will be able to mine XRC. We have a few examples below of miners that are well tested with Bitcoin Rhodium network.
  2. For any miner, configure the miner to point to:
(0–0.8 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3061
(0.8–2 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3062
(3–4 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3063
(5+ GH/s) stratum+tcp://poolcore.bitcoinrh.org:3064
with your XRC address as username and x as password. You don’t need to open an account on pool. You will be mining to XRC address and mined coins will be transferred to your wallet
after blocks reach 10 block maturity
after you mined up minimal amount of coins (currently 0.1 XRC)
sometimes mined blocks could get rejected by network (orphaned) after they were counted as valid blocks. This is normal network behavior to follow longest chain
  1. http://poolcore.bitcoinrh.org is used to follow your miner and network statistics.

CPU Miner-Multi

Source: https://github.com/tpruvot/cpuminer-multi
Sample configuration with CPU Miner tested on UBUNTU.
{
“url” : “stratum+tcp://poolcore.bitcoinrh.org:3061”, “user” : “YOUR XRC ADDRESS”,
“pass” : “x”,
“algo” : “x13”, “threads” : 1,
“cpu-priority” : 5,
“cpu-affinity” : 1, “benchmark” : false, “debug” : true, “protocol”: true, “show-diff”: true, “quiet” : false
}
Command to run your CPUMiner: cpuminer -c cpuminer.json

SGMiner (ATI GPU)

SGMiner is a GPU-based mine: https://github.com/nicehash/sgminereleases
The configuration below was tested on Windows:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
cd C:\Software\sgminer-5.6.1-nicehash-51-windowsamd64 sgminer.exe
— gpu-platform 1 — algorithm x13mod -url stratum+tcp://poolcore.bitcoinrh. org:3062 — pool-user — userpass :x — auto-fan — temp-target 70 — temp-over- heat 82 — temp-cutoff 85 — gpu-fan 65–85 — log-file log.txt — no-adl — no-extra- nonce -P –T

CCMiner (NVIDIA GPU)

CCMiner is a GPU-based miner (NVIDIA)
Command to run your CCMINER:
ccminer-x64.exe -a x13 -o stratum+tcp://poolcore.bitcoinrh.org:3062 -O :without -D — show-diff

Baikal miner

Settings: Url:
(0–2 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3062
(3–4 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3063
(5+ GH/s) stratum+tcp://poolcore.bitcoinrh.org:3064
Algo: x13User: your XRC receiving address (make sure you set 2 distinct addresses for each hashing board)
Pass: x
Extranonce: leave off Priority set to 0 and 1
Once pool stratum address and your wallet as user are set up you should see your miner mining against XRC pool. When miner is working the status column is green. The pool and miner are incorrectly configured now as status says “Dead” highlighted in red.

Instructions for mining XRC on BSOD pool

Pool link: bsod.pw/en/pool/dashboard/XRC/
Use this code for your miner: -a x13 -o stratum+tcp://pool.bsod.pw:2582 -u WALLET.rig
BSOD pool allows both solo and party mining.
For solo mining use code: -a x13 -o stratum+tcp://pool.bsod.pw:2582 -u WALLET.rig -p m=solo And for party mining use: -a x13 -o stratum+tcp://pool.bsod.pw:2582 -u WALLET.rig -p m=party.yourpassword
NOTICE: You can use us for North America and asia for Asia instead of euin your .bat file or config.
You can also use BSOD pool’s monitor app for Android and iOS.

Instructions for mining XRC on ZERGPOOL

Zergpool offers low fees (just 0.5%) and also SOLO and PARTY mining with no extra fees.
To mine XRC on Zergpool use this command lines for your miner:
Regular: -a x13 -o stratum+tcp://x13.mine.zergpool.com:3633 -u -p c=XRC,mc=XRC Solo: -a x13 -o stratum+tcp://x13.mine.zergpool.com:3633 -u -p c=XRC,mc=XRC,m=solo Party: -a x13 -o stratum+tcp://x13.mine.zergpool.com:3633 -u -p c=XRC,mc=XRC,m=party
Use your coin wallet address as username in mining software. Specify c=SYMBOL as password to identify payout wallet coin, and the same coin in mc=SYMBOL to specify mining coin.
For more information and support please visit http://zergpool.com
Notice that when there are more pools mining XRC in different geographic/availability locations choose the nearest to you as lowest priority and then add desirable fall back pool options in different geographic locations or pools. This is useful when one pool experiences issues, to fall back to different pool in Bitcoin Rhodium network.

Calculate your Bitcoin Rhodium mining profitability

WhatToMine: https://whattomine.com/coins/317-xrc-x13
CoinCalculators: https://www.coincalculators.io/coin/bitcoin-rhodium

Feel free to ask questions in Discord community. There are lots of helpful people around the world watching XRC 24x7.

Bitcoin Rhodium Dev Team
submitted by BitcoinRh to BitcoinRhodium [link] [comments]

(Updated) [Staking] Reddcoin Core client GUI wallet on a Raspberry Pi Model 3B

Intro

This thread is an update to my first Reddcoin staking tutorial that was written 7 months ago.
 
The reason for the update
My Reddcoin Core software crashed and became unusable. My Raspberry Pi 3B would lag and freeze, I couldn't stake anymore.
 
Instead of just redoing everything the same way, I wanted to see if I could improve on 3 points:
 
The updates
 
If you would like to tip me
Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
     

Overview

 

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Video

https://www.youtube.com/watch?v=Snr5e8bzftI
This video shows how long it takes to start Reddcoin Core.   TL;DR:
     

Extra

Backup
Backup your wallet to prevent losing the RDDs in your wallet! There are two methods to backup, do both. Make new backups if you create a new receiving address!
 
 
   
Boot with only 1 USB drive plugged in:
Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly.   If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
   
Connection issues If you have issues syncing the blockchain because you have 0 network connections, please follow the instructions in this thread.
   
Start Reddcoin Core easier
Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.
   
Minimization options
Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
   
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
 
   
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.
   
Updates / Upgrades
If Software Updater shows up and tells you that there is updated software available, do not install the updates using Software Updater. Use LXTerminal to update Lubuntu.  
     

Credits:

   
Credits in previous tutorial:
submitted by Yavuz_Selim to reddCoin [link] [comments]

Dogecoin on Linux - The Complete Beginner's Guide

I'm writing this because I couldn't find a single condensed guide on compiling the wallet and running mining software on linux, specficially Ubuntu/Linux Mint. I combed Bitcoin and Litecoin forums for similar problems I was running into and eventually got everything nailed down, so here it is in one place, for new Shibes.
If you want to make a Dogecoin directory in your downloads folder to keep things organized, you will need to modify these commands to refelct the change. So instead of going to ~/Downloads/ you will need to go to ~/Downloads/Dogecoin and be sure to put the zipped files there when you download them, but the commands will be the same otherwise.
cwayne18 put in the work to make a PPA for the QT client here.
Ubunutu/Mint/Debian users should be able to install the client with the following commands:
sudo add-apt-repository ppa:cwayne18/doge sudo apt-get update && sudo apt-get install dogecoin-qt 
To update using this method, run
sudo apt-get update && sudo apt-get upgrade dogecoin-qt 
Compiling the Wallet Manually
I suggest using the PPA above, but if you want to compile manually, here you go.
1)Download the newest source from here. If you want to check out the Github page, click here
2)Unzip the package with the native client OR, navigate to your downloads and unzip
cd ~/Downloads unzip dogecoin-master.zip 
3)Now it's time to compile. You will need to install the dependencies, just copy and paste the following code. It will be a fairly large download and could take some time. It is always important to update before installing any new software, so we'll do that first and then install the dependencies.
sudo apt-get update sudo apt-get upgrade sudo apt-get install libssl-dev libdb-dev libdb++-dev libqrencode-dev qt4-qmake libqtgui4 libqt4-dev sudo apt-get install libminiupnpc-dev libminiupnpc8 libboost-all-dev build-essential git libboost1.53-all-dev 
4)Once that is done, go to the doge-coin master directory and compile:
cd ~/Downloads/dogecoin-maste sed -i 's/-mgw46-mt-sd-1_53//g' dogecoin-qt.pro qmake USE_UPNP=- USE_QRCODE=0 USE_IPV6=0 make -j3 
After running the qmake command you will likely see some text similar to
Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target language has less forms. If this sounds wrong, possibly the target language is not set or recognized. 
It's perfectly normal, so don't worry about that.
Your Dogewallet is ready to go! The executable is in ~/Downloads/dogecoin-maste and called dogecoin-qt. Your wallet information is in ~/.dogecoin. You can run the wallet at any time by opening terminal and typing
cd ~/Downloads/dogecoin-maste ./dogecoin-qt 
Future upgrades to dogewallet are easy. Back up your wallet.dat, and simply follow the same directions above, but you'll be unzipping and building the newer version. You will likely need to rename the old dogecoin-master directory in ~/Downloads before unzipping the newest version and building. Also, it is likely that you will not need to install the dependencies again.
Alternate Method For Installing Dogecoin Wallet from Nicebreakfast
After installing the dependencies listed in step 3, open terminal, then navigate to where you want Dogecoin Wallet stored and run:
git clone https://github.com/dogecoin/dogecoin ./autogen.sh ./configure make 
then when the wallet is updated just run
git pull 
from the dogecoin directory.
GPU Mining
GPU mining requires CGminer. My suggestion is to get the executable already built. The creator of cgminer has removed the built file from his website, but I've uploaded it here
sudo apt-get install pkg-config opencl-dev libcurl4-openssl-dev autoconf libtool automake m4 ncurses-dev cd ~/Downloads tar -xvf cgminer-3.7.2-x86_64-built.tar.bz2 
Don't use anything newer than 3.7.2. The newer versions of CGMiner don't support GPU mining.
That's it! You have cgminer ready to go! You will run cgminer with the following syntax
cd ~/Downloads/cgminer-3.7.2-x86_64-built/ ./cgminer --scrypt -o stratum+tcp://SERVERNAME:PORT -u WORKER.ID -p PASS 
A good guide for fine tuning cgminer can be found here; follow the litecoin example.
EDIT
I had trouble getting cgminer running with a single line command, but running it via an executable .sh file works. This is covered in the cgminer setup guide I posted above but I'll put it here too. In the same directory that has the cgminer executable, you need to make a file called cgminer.sh and make it executable. It should contain the follwing:
export GPU_USE_SYNC_OBJECTS=1 export GPU_MAX_ALLOC_PERCENT=100 export DISPLAY=:0 find *.bin -delete sleep 5 ./cgminer 
Then you can call cgminer in terminal by doing ./cgminer.sh You will need a cgminer.conf file containing all your options. All of this is covered in the guide that is linked above.
A quick note about AMD drivers: They used to be a huge PITA to install and get working, but the newest Catalyst drivers are great. There's a GUI installer, everything works out of the box, and there is a lot of documentation. You can download them here: AMD Catalyst 14.6 Beta Linux
CPU Mining
For CPU mining I use minerd because it doesn't require any work to get running, simply download it and get to work. Download the built file for your machine 32-bit or 64-bit, and then unzip it and you're ready to go!
cd ~/Downloads tar -xvf pooler-cpuminer-2.3.2-linux-x86.tar.gz 
The executable is called minerd and it will be in ~/Downloads but you can move it to wherever you like. To run it, pull up terminal and do
cd ~/Downloads minerd --url=stratum+tcp://SERVER:PORT --userpass=USERNAME.WORKERNAME:WORKERPASSWORD 
You're done! Happy mining!
Common Issues
I ran into this and I've seen others with this problem as well. Everything installs fine but there is a shared library file that isn't where it should be. In fact, it isn't there at all.
 libudev.so.1: cannot open shared object file: No such file or directory 
In terminal, do
sudo updatedb locate libudev.so.0.13.0 
And it will probably return a path /lib/x86_64-linux-gnu. Inside that directory there's a library file called libudev.so.0.13.0. You'll need to make a symlink (aka shortcut) that links libudev.so.1 to libudev.so.0.13.0 So, assuming you're working with libudev.so.0.13.0 do this
cd /lib/x86_64-linux-gnu sudo ln -s libudev.so.0.13.0 libudev.so.1 
Now if you do
ln -l 
You should see
libudev.so.1 -> ./libudev.so.0.13.0 
Meaning you've made the symlink. Also, the text for libudev.so.1 will be blue.
submitted by Boozybrain to dogecoin [link] [comments]

IMPORTANT wallet advice I think every user should know - don't get burned by not following these tips, it's important to use wallets in a SAFE way!

iOS, Android & Exchange wallets = NOT SECURE enough!

There are RISKS to storing your ETH in an iOS/Android wallet, and you are obligated to TEST YOUR WALLET if you used myetherwallet.com to generate your wallet (their wallets should work just fine but they even tell you to test your wallet before offloading to it). Also if you use freewallet I suggest REMOVING YOUR FUNDS FROM IT ASAP see here for why.
An example: Jax for iOS is a closed source wallet -- all iOS and Android wallets are compiled and sent to the app store. It is impossible to know what got inserted into there by the time you use it. For that reason I strongly encourage not keeping your ether in any iOS or Android wallet and also not keeping your ether in any exchange at. Both wallet apps and exchanges have been hacked or behaved dishonestly in the past and have stolen user bitcoin and ether. I believe the founder of jaxx has said as much as well - that his wallet is designed for convenience and not for large or long term storage!
you may think I am paranoid, however:
  1. here is an iOS wallet that just stole 8 million dollars from its users - this could happen to jaxx or any, any wallet you download from the app store
  2. here is a user who lost $50,000 because he generated a wallet at myetherwallet without first testing sending and receiving money
It is very important that you:
  1. generate a wallet from a source that you absolutely trust and that you
  2. store that wallet in a secure environment and that you
  3. test that wallet before sending all your ether to it.
If you search the sub you will discover some horror stories from folks who failed to follow through with these steps. They are not overly hard but are extremely important towards securing your investment.
FAILURE TO COMPLY with these pieces of advice may result in the absolute and total loss or inaccessibility of your ether, and in such a circumstance your ether is both non-recoverable and you are fully liable for the loss.

How to generate a wallet in a safe way: air gapped paper wallet

  1. get a USB stick and create a bootable version of ubuntu, there are many guides on how to do this. Here is one for Windows Users. Here is one for Mac users. Here is a video on YouTube for how to do it. By the end of this first step you should have a USB stick that you can boot Ubuntu from.
  2. download this website from here. Extract the contents of this zip to a folder on a flash drive. You can use the same flash drive that you just created for Ubuntu, just make a folder such as flashdrive/myetherwallet and stick the website contents in there
  3. You have to now boot your computer from the USB stick. Mac users can just insert the USB stick, hold option, power up their computer and then select "Ubuntu live cd" or "ubuntu". Windows users have to follow these steps with the usb stick inserted and then pick the usb stick from a list of boot options.
  4. at some point booting from the usb stick, select "live cd" or "try ubuntu before installing". NEVER EVER SETUP WIFI, UNPLUG YOUR INTERNET CORD IF YOU ARE WIRED IN!
  5. once ubuntu boots, find the flash drive in the file explorer with the website, and open up index.html
  6. think up a password (you absolutely shouldnt forget this) and click "generate wallet". Then click "download keystore file" and find the file that got downloaded and STICK THIS ON THE FLASH DRIVE - you absolutely shouldnt lose this!
  7. write down the private key that they give you. Write it on paper, double and triple check it. Copy it to a text file and save it onto the flash drive. You absolutely shouldnt lose this!
  8. you shouldnt print your wallet unless you can connect to a usb printer. Otherwise you would need network access to print. What you can do though is click on "print", cancel the print dialogue and then go to "file > save" and save the webpage on your flash disk.
  9. click next, select "Keystore File (UTC / JSON)" and then "select a file" and open the .json file you saved on the flash disk earlier
  10. you have now generated a wallet. Nice job. I highly suggest you now insert a second flash disk and copy EVERYTHING from the first one onto the second. Then store them in different places. The idea here is that you make several copies of your public and private key so you don't lose them.
  11. NEVER EVER PLUG THESE USB STICKS INTO ANOTHER COMPUTER AGAIN - only access these USB sticks from ubuntu, booting it up the same way you did in the steps above ^
  12. You should now try sending something small like 0.001 ETH to this new wallet, and then use http://etherscan.io to make sure the transfer goes through.
  13. You should now try sending 0.001 ETH out of your new wallet to make sure it works. You should only ever send money from this new wallet by booting Ubuntu up and sticking the USB sticks into your computer. From an online computer go here and put your new wallet's public address in, then click "generate information" and copy down gas price and nonce to a textfile on A NEW usb stick. Go back to your offline computer with ubuntu and open up index.html again and click "Send Offline" on the navigation at the top. Where it says "Step 2" insert the to address of your old wallet, and put 0.001 in for value, and then fill in gas price and nonce from the text file you saved on that new usb stick. Check the "keystore JSON" box and click "SELECT WALLET FILE" and give it the .json file you saved from step 6. It will now give you some long string of text. SAVE THIS TO THAT NEW USB STICK DONT REUSE THE ONE WITH THE .JSON FILE AND YOUR PRIVATE KEY! Stick this new USB stick into another computer, go here again, in the box labeled "signed transaction" paste that text you just saved in and click "send transaction". BOOM.
if this works then you now a) know your brand spanking new wallet works and b) know how to do a super secure offline transaction - hackers be damned you're pretty secure and safe now!

Hardware wallet

I believe an air gap generated paper wallet is the most secure approach, but if you want a hardware wallet I would read up on the Ledger and the TREZOR, although these are difficult to find right now due to large demand.
submitted by dont_forget_canada to ethtrader [link] [comments]

How to Mine BiblePay on Linux

This guide is outdated, please refer to:
https://wiki.biblepay.org/POBH_Setup
https://wiki.biblepay.org/PODC_Setup
 
 
 
 
 
 
 
 
IMPORTANT - Evolution Upgrade:
Quick Start https://wiki.biblepay.org/Quick_Start
Evolution Upgrade Information https://wiki.biblepay.org/Evolution_Upgrade
Getting Started with Evolution https://wiki.biblepay.org/Getting_Started_with_Evolution
Generic Smart Contracts https://wiki.biblepay.org/Generic_Smart_Contracts
What is BiblePay Evolution? https://www.reddit.com/BiblePay/comments/bifvpk/biblepay_evolution_what_is_it/
Recommend 2GB RAM or can get stuck compiling (if 1GB RAM can use Swap File) Use Ubuntu 16.04
INFO
https://github.com/biblepay/biblepay-evolution/blob/masteBuildBiblePay.txt
INSTALL COMMANDS
apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils apt-get install libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-program-options-dev libboost-test-dev libboost-thread-dev apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler apt-get install git apt-get install curl build-essential libtool autotools-dev automake pkg-config python3 bsdmainutils cmake sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev git clone http://github.com/biblepay/biblepay-evolution prefix=x86_64-pc-linux-gnu cd biblepay-evolution/depends make -j4 # Choose a good -j value, depending on the number of CPU cores available cd .. ./autogen.sh #Note: if echo `pwd` does not return your working directory, replace it with your working directory such as /biblepay-evolution/ ./configure --prefix `pwd`/depends/x86_64-pc-linux-gnu make # See more here: #https://github.com/biblepay/biblepay-evolution/blob/mastedoc/build-unix.md 

SWAP FILE
NOTE: if server is 1GB RAM, before running last command "sudo make", set up a swap file
free #check if swap is 0 dd if=/dev/zero of=/vaswap.img bs=1024k count=1000 mkswap /vaswap.img swapon /vaswap.img free #check if swap is 1024 sudo make 

RUN COMMAND LINE
cd src ./biblepayd -daemon 
OR
RUN GUI
Your GUI program will be located in: /biblepay-evolution/src/qt
./biblepay-qt 
You can also run it in the background (to free up your terminal) if you call it with:
./biblepay-qt & 
To start mining, instructions are the same as for Windows: Go to Tools -> Debug Console
Execute this command (to start mining with 8 threads)
setgenerate true 8 
From there you can use all other commands such as getmininginfo, getwalletinfo, etc. Execute help command to get the list of all available commands.
Note: GUI will be built automatically only if you meet the requirements for qt library, i.e. make sure you ran this line before compiling:
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler 
BIBLEPAY is now Running!

SETUP CONFIG
Stop BiblePay and set up the config file to get starting nodes to sync with and enable mining:
./biblepay-cli stop cd ~/.biblepayevolution/ vi biblepay.conf addnode=node.biblepay.org gen=1 genproclimit=1 
Escape Key + : (Colon Key) + w + q + Enter (saves file and quits)

addnode --- adds a node to the list of nodes to connect to gen=1 --- turns on mining genproclimit --- sets number of threads to use when mining

Run BiblePay again and fully sync with network
cd ../biblepay-evolution/src ./biblepayd -daemon ./biblepay-cli getinfo 

USEFUL COMMANDS
./biblepay-cli help ./biblepay-cli getaccountaddress "" ./biblepay-cli getinfo ./biblepay-cli getmininginfo ./biblepay-cli setgenerate true 8 ./biblepay-cli sendtoaddress "insertAddressHere" 777 "" "" true ./biblepay-cli stop ./biblepayd -daemon top #CPU usage q to quit 

MINING THREADS: To change number of threads to use up for mining
a. Edit home/yourusername/.biblepayevolution/biblepay.conf file:
genproclimit=X 
and restart BiblePay -or- b. Menu >> Tools >> Debug Console >> Type command:
setgenerate true X 
(Replace X with number of threads Use top command to view CPU usage)

POOL
NOTE: To use the pool you must now use the external miner, not the wallet miner https://whitewalr.us/2019/biblepay-nomp-pool-mining.html
  1. Set up an account on pool website: https://pool.biblepay.org/
  2. Create Worker Username(s) - Workers tab >>> Add
  3. Enable pool and add Worker Username in ~/.biblepayevolution/biblepay.conf file, add these lines and save:
    pool=https://pool.biblepay.org workerid=insertWorkerUsernameHere
4. Restart BiblePay
./biblepay-cli stop ./biblepayd -daemon 
Setup Auto-Withdraw Navigate to Account >>> Account Settings >>> Verify your BBP Receiving Address >>> Click Authorize-Auto-Withdraws

UPDATE:

### Turn off/stop BiblePay
cd /home/yourname/biblepay-evolution/src ./biblepay-cli stop 

### Pull down latest Biblepay code and build it
cd /home/yourname/biblepay-evolution git pull origin master sudo make 

### Turn BiblePay back on and check version number
cd src ./biblepayd -daemon ./biblepay-cli getinfo ./biblepay-cli setgenerate true 8 

UPDATE IN ONE COMMAND:
./biblepay-evolution/src/biblepay-cli stop ; cd && cd biblepay-evolution/ && git pull origin master && sudo make && cd src && ./biblepayd -daemon && sleep 90 && ./biblepay-cli getmininginfo 
Note: the ";" says do this after, regardless of the outcome Note: && says do this after only if previous command finished with no errors

SPEED UP COMPILE:
To speed up the compile time, add -j4 or -j8 after make. This way it compiles using 4 or 8 threads instead of just 1.
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/" sudo make -j8 
Reference: http://www.linux-databook.info/?page_id=2319

RSYNC stop biblepay from your nodes compile on your fastest machine then rsync with your machines only src folder is required
rsync -avuz /root/biblepay-evolution/src/ [email protected]:/root/biblepay-evolution/src/ 
https://stackoverflow.com/questions/3299951/how-to-pass-password-for-rsync-ssh-command https://www.thegeekstuff.com/2008/11/3-steps-to-perform-ssh-login-without-password-using-ssh-keygen-ssh-copy-id/
people make cron jobs and rsync automatically

OUTDATED

Unofficial Bash Script
https://gist.github.com/anonymous/d1c1d35e3c8f67f5fb2e204479fa5c6b

Official Ubuntu Package
https://launchpad.net/~biblepay-official

Unofficial Ubuntu Package
https://www.reddit.com/BiblePay/comments/7rwqqs/unofficial_ubuntu_packages_available/

Unofficial Mine in One Line
https://www.reddit.com/BiblePay/comments/7ryuk1/mine_in_one_line/
NOTE: DONT RUN ON A COMPUTER WITH COINS -- THIS IS A CLEAN INSTALL SCRIPT

COMPILE WITHOUT GUI: https://bitcointalk.org/index.php?topic=2042657.msg21878317#msg21878317 https://bitcointalk.org/index.php?topic=2042657.msg21878389#msg21878389
ADVANCED:

DOCKER IMAGES (NOTE: I havent tested these, use at your own risk) https://hub.docker.com/gagaha/biblepay/ https://hub.docker.com/cryptozero/biblepay-opt/
submitted by togoshige to BiblePay [link] [comments]

[Reupload][Tutorial] Install Armory Wallet 0.96.4 on Fedora Workstation 29

note: I had to reupload this because reddit is banning my original account for no reason. I appealed but I thought maybe someone wanted to have this content online.
Armory is a very cool open source bitcoin wallet for the power user. You can do neat things with it, read here: https://www.bitcoinarmory.com/
Disclaimer: follow these steps at your own risk. I am not responsible for any damage / loss of funds you might face for following or not following correctly my instructions here. I may have made a typo somewhere or be wrong so do your own research and learn for yourself what I am doing at each step, and what consequences may have for you, at your own risk. These instructions may be wrong somewhere. It worked for me, it doesn't mean it has to work for you.
Requirements for this tutorial:
We are going to build the code from source.
Install dependencies.
I followed these instructions to find the equivalent Fedora packages:
Open the terminal app and run this command:
sudo dnf install git nano qt qt-devel python-devel libtool pyqt4 pyqt4-devel lmdb swig 
And more python packages that I had to install:
sudo pip install twisted qt4reactor psutil 
Importing the signing key to verify the software
Install KGPG to easily manage keys.
sudo dnf install kgpg 
Go to
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x8C5211764922589A
and copy paste the code below the title from
-----BEGIN PGP PUBLIC KEY BLOCK-----
to
-----END PGP PUBLIC KEY BLOCK-----
both included. Then open KGPG from terminal with
kgpg -k 
and click 'Import Key...' > Clipboard > Ok . You should see a confirmation message. Double check the info and close the dialog.
Repeat the process with this other key:
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xA4FC919E85C595BA
You can verify both keys are mentioned at the Armory webpage.
Clone and compile the code plus some edits
Before, we installed some dependencies that are named differently than the equivalent Ubuntu/Debian package specified at the Armory documentation. The build process fails for Fedora as the name for the dependency during checks won't match the Fedora version. There's this pull request addressing that, but the code is not part of any release yet.
So the fastest workaround (maybe a bit dirty) was to edit the build config file and correct the name for my Fedora install. Let's begin.
Clone the Armory repository
git clone https://github.com/goatpig/BitcoinArmory.git 
Enter the BitcoinArmory dir
cd BitcoinArmory 
Switch to release code
git checkout 'v0.96.4' 
Verify commit signature
git tag -v 'v0.96.4' 
you should see the following message:
> object fee1f91a3137ef1056e15cc606a186b0e508f84c > type commit > tag v0.96.4 > tagger goatpig  1522530739 +0200 > > v0.96.4 > gpg: Signature made Sat 31 Mar 2018 11:12:19 PM CEST > gpg: using RSA key 8C5211764922589A > gpg: Good signature from "goatpig (Offline signing key for Armory releases) " > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the owner. > Primary key fingerprint: 745D 707F BA53 968B DF63 AA8D 8C52 1176 4922 589A 
if it looks the same, everything is ok.
Edit the file 'Makefile' file with
gedit Makefile 
And click the three dot menu > Find and Replace...
Configure the options as follows:
https://i.imgur.com/hpS01Kd.png
Click Replace All and close.
Go back to the terminal and run the following commands in order from inside the BitcoinArmory dir. Wait for the previous one to finish before running the next one:
./autogen.sh 
...
./configure 
...
make 
if everything finishes without error you are all done! Run this to start Armory:
python ./ArmoryQt.py 
you are all set. Please let me know if I missed something.
submitted by RedditShadowbangedMe to Bitcoin [link] [comments]

[Tutorial] Install Armory Wallet 0.96.4 on Fedora Workstation 29

Armory is a very cool open source bitcoin wallet for the power user. You can do neat things with it, read here: https://www.bitcoinarmory.com/
Disclaimer: follow these steps at your own risk. I am not responsible for any damage / loss of funds you might face for following or not following correctly my instructions here. I may have made a typo somewhere or be wrong so do your own research and learn for yourself what I am doing at each step, and what consequences may have for you, at your own risk. These instructions may be wrong somewhere. It worked for me, it doesn't mean it has to work for you.
Requirements for this tutorial:
We are going to build the code from source.
Install dependencies.
I followed these instructions to find the equivalent Fedora packages:
Open the terminal app and run this command:
sudo dnf install git nano qt qt-devel python-devel libtool pyqt4 pyqt4-devel lmdb swig 
And more python packages that I had to install:
sudo pip install twisted qt4reactor psutil 
Importing the signing key to verify the software
Install KGPG to easily manage keys.
sudo dnf install kgpg 
Go to
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x8C5211764922589A
and copy paste the code below the title from
-----BEGIN PGP PUBLIC KEY BLOCK-----
to
-----END PGP PUBLIC KEY BLOCK-----
both included. Then open KGPG from terminal with
kgpg -k 
and click 'Import Key...' > Clipboard > Ok . You should see a confirmation message. Double check the info and close the dialog.
Repeat the process with this other key:
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xA4FC919E85C595BA
You can verify both keys are mentioned at the Armory webpage.
Clone and compile the code plus some edits
Before, we installed some dependencies that are named differently than the equivalent Ubuntu/Debian package specified at the Armory documentation. The build process fails for Fedora as the name for the dependency during checks won't match the Fedora version. There's this pull request addressing that, but the code is not part of any release yet.
So the fastest workaround (maybe a bit dirty) was to edit the build config file and correct the name for my Fedora install. Let's begin.
Clone the Armory repository
git clone https://github.com/goatpig/BitcoinArmory.git 
Enter the BitcoinArmory dir
cd BitcoinArmory 
Switch to release code
git checkout 'v0.96.4' 
Verify commit signature
git tag -v 'v0.96.4' 
you should see the following message:
> object fee1f91a3137ef1056e15cc606a186b0e508f84c > type commit > tag v0.96.4 > tagger goatpig  1522530739 +0200 > > v0.96.4 > gpg: Signature made Sat 31 Mar 2018 11:12:19 PM CEST > gpg: using RSA key 8C5211764922589A > gpg: Good signature from "goatpig (Offline signing key for Armory releases) " > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the owner. > Primary key fingerprint: 745D 707F BA53 968B DF63 AA8D 8C52 1176 4922 589A 
if it looks the same, everything is ok.
Edit the file 'Makefile' file with
gedit Makefile 
And click the three dot menu > Find and Replace...
Configure the options as follows:
https://i.imgur.com/hpS01Kd.png
Click Replace All and close.
Go back to the terminal and run the following commands in order from inside the BitcoinArmory dir. Wait for the previous one to finish before running the next one:
./autogen.sh 
...
./configure 
...
make 
if everything finishes without error you are all done! Run this to start Armory:
python ./ArmoryQt.py 
you are all set. Please let me know if I missed something.
edit: cd git dir.
submitted by AmbitiousSpeed0 to Bitcoin [link] [comments]

IMPORTANT safety advice for new users - know how to store your ETH safely so you don't lose it!

this is a repost from my old guide BUT we have a lot more new users so I thought it was important to re-iterate through this advice:
https://www.reddit.com/ethtradecomments/6h46qw/important_wallet_advice_i_think_every_user_should/

iOS, Android & Exchange wallets = NOT SECURE enough!

There are RISKS to storing your ETH in an iOS/Android wallet, and you are obligated to TEST YOUR WALLET if you used myetherwallet.com to generate your wallet (their wallets should work just fine but they even tell you to test your wallet before offloading to it). Also if you use freewallet I suggest REMOVING YOUR FUNDS FROM IT ASAP see here for why.
An example: Jax for iOS is a closed source wallet -- all iOS and Android wallets are compiled and sent to the app store. It is impossible to know what got inserted into there by the time you use it. For that reason I strongly encourage not keeping your ether in any iOS or Android wallet and also not keeping your ether in any exchange at. Both wallet apps and exchanges have been hacked or behaved dishonestly in the past and have stolen user bitcoin and ether. I believe the founder of jaxx has said as much as well - that his wallet is designed for convenience and not for large or long term storage!
you may think I am paranoid, however:
  1. here is an iOS wallet that just stole 8 million dollars from its users - this could happen to jaxx or any, any wallet you download from the app store
  2. here is a user who lost $50,000 because he generated a wallet at myetherwallet without first testing sending and receiving money
It is very important that you:
  1. generate a wallet from a source that you absolutely trust and that you
  2. store that wallet in a secure environment and that you
  3. test that wallet before sending all your ether to it.
If you search the sub you will discover some horror stories from folks who failed to follow through with these steps. They are not overly hard but are extremely important towards securing your investment.
FAILURE TO COMPLY with these pieces of advice may result in the absolute and total loss or inaccessibility of your ether, and in such a circumstance your ether is both non-recoverable and you are fully liable for the loss.

How to generate a wallet in a safe way: air gapped paper wallet

  1. get a USB stick and create a bootable version of ubuntu, there are many guides on how to do this. Here is one for Windows Users. Here is one for Mac users. Here is a video on YouTube for how to do it. By the end of this first step you should have a USB stick that you can boot Ubuntu from.
  2. download this website from here. Extract the contents of this zip to a folder on a flash drive. You can use the same flash drive that you just created for Ubuntu, just make a folder such as flashdrive/myetherwallet and stick the website contents in there
  3. You have to now boot your computer from the USB stick. Mac users can just insert the USB stick, hold option, power up their computer and then select "Ubuntu live cd" or "ubuntu". Windows users have to follow these steps with the usb stick inserted and then pick the usb stick from a list of boot options.
  4. at some point booting from the usb stick, select "live cd" or "try ubuntu before installing". NEVER EVER SETUP WIFI, UNPLUG YOUR INTERNET CORD IF YOU ARE WIRED IN!
  5. once ubuntu boots, find the flash drive in the file explorer with the website, and open up index.html
  6. think up a password (you absolutely shouldnt forget this) and click "generate wallet". Then click "download keystore file" and find the file that got downloaded and STICK THIS ON THE FLASH DRIVE - you absolutely shouldnt lose this!
  7. write down the private key that they give you. Write it on paper, double and triple check it. Copy it to a text file and save it onto the flash drive. You absolutely shouldnt lose this!
  8. you shouldnt print your wallet unless you can connect to a usb printer. Otherwise you would need network access to print. What you can do though is click on "print", cancel the print dialogue and then go to "file > save" and save the webpage on your flash disk.
  9. click next, select "Keystore File (UTC / JSON)" and then "select a file" and open the .json file you saved on the flash disk earlier
  10. you have now generated a wallet. Nice job. I highly suggest you now insert a second flash disk and copy EVERYTHING from the first one onto the second. Then store them in different places. The idea here is that you make several copies of your public and private key so you don't lose them.
  11. NEVER EVER PLUG THESE USB STICKS INTO ANOTHER COMPUTER AGAIN - only access these USB sticks from ubuntu, booting it up the same way you did in the steps above ^
  12. You should now try sending something small like 0.001 ETH to this new wallet, and then use http://etherscan.io to make sure the transfer goes through.
  13. You should now try sending 0.001 ETH out of your new wallet to make sure it works. You should only ever send money from this new wallet by booting Ubuntu up and sticking the USB sticks into your computer. From an online computer go here and put your new wallet's public address in, then click "generate information" and copy down gas price and nonce to a textfile on A NEW usb stick. Go back to your offline computer with ubuntu and open up index.html again and click "Send Offline" on the navigation at the top. Where it says "Step 2" insert the to address of your old wallet, and put 0.001 in for value, and then fill in gas price and nonce from the text file you saved on that new usb stick. Check the "keystore JSON" box and click "SELECT WALLET FILE" and give it the .json file you saved from step 6. It will now give you some long string of text. SAVE THIS TO THAT NEW USB STICK DONT REUSE THE ONE WITH THE .JSON FILE AND YOUR PRIVATE KEY! Stick this new USB stick into another computer, go here again, in the box labeled "signed transaction" paste that text you just saved in and click "send transaction". BOOM.
if this works then you now a) know your brand spanking new wallet works and b) know how to do a super secure offline transaction - hackers be damned you're pretty secure and safe now!

Hardware wallet

I believe an air gap generated paper wallet is the most secure approach, but if you want a hardware wallet I would read up on the Ledger and the TREZOR, although these are difficult to find right now due to large demand.
submitted by dont_forget_canada to ethtrader [link] [comments]

Lore v2 QT on Raspberry Pi

Hello,
 
To follow up to mindphuk's excellent piece on building the headless client on Raspberry Pi (https://www.reddit.com/blackcoin/comments/6gkjrw/wip_blackpi_a_stake_device_based_on_raspberry/), I thought if anyone was interested I'd show you how to get the full QT version running on the Pi on the Jessie with Pixel desktop. This works and has been soak tested for several days now on a standard Raspberry Pi 3. I have since added some coins and it stakes a handful of times a day.
 
Running staking Lore clients paves the way for some of the future use cases of BLK utilising the Bitcoin 0.12 (and newer) core tech, including colored coins. So I'm going to leave this one going indefinitely to kickstart the number of Lore clients staking. It's certainly not mandatory but it will be good in the longer term to have a nice distribution of Lore staking clients.
 
The cross-compile which lets you create binaries for multiple platforms didn't work for the QT version on the Pi, so there is more to do than just running the binary unfortunately, as below. There are folks working on some much cleaner solutions than this for the Pi, with a custom front end, and where you won't have to do any mucking about. That is coming soon. In the meantime, if you enjoy a fiddle with such things, here's how to get this QT client working on your Pi.
 
These instructions assume you are starting from scratch with a completely blank OS.
 
Download Jessie with Pixel from: http://downloads.raspberrypi.org/raspbian/images/raspbian-2017-07-05/2017-07-05-raspbian-jessie.zip
 
Note they have since (August 2017) released a version called 'Stretch' which does not work with this guide. I'll see if I can come up with something new for that at some point and link to it here when I have. In the meantime the guide should work with the Jessie image above.
 
Unzip the file and extract the .img file to burn it onto Fresh SD card to boot from (to be safe, use 16GB or larger), using a tool like win32diskimager or Etcher.
 
Assuming you have keyboard/mouse and monitor plugged into your pi, boot it up and the Jessie Desktop will show.
 
Before we do anything else, you should increase the default swap size on the pi, as compiling certain libraries can exhaust the RAM and get stuck otherwise. To do this, launch a Terminal window and type:
 
sudo nano /etc/dphys-swapfile 
 
and Change the CONF_SWAPSIZE from 100 to:
 
CONF_SWAPSIZE=1024 
 
Exit nano with control + x to write out the file.
 
Then, run the following to restart the swapfile manager:
 
sudo /etc/init.d/dphys-swapfile stop sudo /etc/init.d/dphys-swapfile start 
 
Now, launch the browser and download the Lore 2.12 binaries for ARM here: https://mega.nz/#!k2InxZhb!iaLhUPreA7LZqZ-Az-0StRBUshSJ82XjldPsvhGBBH4 (Version with fee fix from 6 September 2017)
 
(If you prefer to compile it yourself instead, it is possible by following the instructions in the original article by Mindphuk just taking into account this is the newer version of the Lore client than when that was written (https://github.com/janko33bd/bitcoin/releases) and the versions of Boost and the Berkeley DB need to be the same as below.)
 
Double click the zip and extract the Lore binary files. Yes, at the moment they are all called 'bitcoin', not 'blackcoin' or 'Lore' - this is because the code derives from a recent bitcoin core implementation so this has not yet been updated. You can place these wherever you like.
 
In the Terminal window, change directory to where you put the binaries, e.g.:
 
cd Downloads/lore-raspberrypi-armv7-jessie-pixel chmod +x * 
 
That marks the binaries as executable.
 
Now, we need the Boost libraries installed for any of the Lore binaries to work. The project was done with Boost 1.62.0. Unfortunately the Jessie repository only goes up to 1.55, so we need to download and build 1.62 manually on the device.
wget https://sourceforge.net/projects/boost/files/boost/1.62.0/boost_1_62_0.tar.gz/download tar -xvzf download cd boost_1_62_0 sudo ./bootstrap.sh sudo ./b2 install 
 
(This will take almost 2 hours. Have a nice cup of tea and a sit down.)
 
When I came to run the binaries, I found they couldn't find Boost. Running this command fixes that:
sudo ldconfig 
 
Now we are going to install the packages which aren't already included in the default OS installation which the binaries need in order to run:
sudo apt-get install qrencode libprotobuf-dev libevent-pthreads-2.0-5 
 
Now we need to install the Berkeley Database version 6.2.23. This is the version Lore v2 uses. Bitcoin still uses 4.8 which is 10 years old! This doesn't take too long.
wget http://download.oracle.com/berkeley-db/db-6.2.23.tar.gz tar -xvzf db-6.2.23.tar.gz cd db-6.2.23/build_unix ../dist/configure --prefix=/usr --enable-compat185 --enable-dbm --disable-static --enable-cxx 
 
I find this next section of the Berkeley instructions worked better just switching to root, which can be fudged by running sudo su before the rest:
sudo su make make docdir=/usshare/doc/db-6.2.23 install chown -v -R root:root /usbin/db_* /usinclude/db{,_185,_cxx}.h /uslib/libdb*.{so,la} /usshare/doc/db-6.2.23 
 
Now we're going to go up a couple of directories to where the binaries were:
cd ../.. 
 
Then run the client!
./bitcoin-qt 
 
And there you have it. Should hopefully end up looking a bit like this: http://imgur.com/a/eEHGa
 
Using the Bootstrap can save a while syncing. Download it at: https://www.reddit.com/blackcoin/comments/6b3imq/blackcoin_bootstrapdat_up_to_block_1631800
 
Place the bootstrap.dat file into the ~/.lore directory.
 
Run ./bitcoin-qt again, it will say 'Importing Blocks' rather than 'Synchronising with Network'. My pi sync'ed fully in about 5-6 hours.
 
If you want peace of mind that Lore will always start on bootup into the Jessie w/Pixel desktop (i.e. after a power cycle), then you need to create a .desktop file in the following place.
sudo nano ~/.config/autostart/Lore.desktop 
 
And in it, enter the following (tailoring the Exec line below to the whereabouts of your bitcoin-qt file):
[Desktop Entry] Name=Blackcoin Lore Comment=Mining without the waste Exec=/home/pi/Downloads/lore-raspberrypi-armv7-jessie-pixel/bitcoin-qt Type=Application Encoding=UTF-8 Terminal=false Categories=None; 
 
Power usage and payback time
 
After a good while leaving it going by itself, the CPU load averages got down to almost zero, all of the time. Idling, the Pi uses a bit less than 3 watts. This means it would take two weeks to use one 1Kw/h of electricity.
 
If you pay e.g. 12.5 cents a unit, that's what you'd expect this to cost to run in a fortnight. That's around $0.25 a month or $3 a year. Green and cheap and helping to secure the BLK network. I paid for the year's worth of electricity in 2 days staking with 25k BLK. Makes mining look silly, huh? ;)
 
Securing your Pi
 
With staking, your wallet needs to be unlocked and as such, the keys to your wallet are on the device. In a clean and newly installed environment as described above, and if you don't allow others to use your device and there is no other software or nasties running on it, there is no real cause for concern. However, there are some basic security precautions you can take.
 
Firstly, if you have enabled SSH and are playing with your pi across your LAN (or worse, the Internet), you should immediately change the password for the default 'pi' user (which is preconfigured to be 'raspberry'). Simply log in as normal, then type:
 
passwd 
 
You'll be prompted to enter the old and the new passwords.
 
Security by default
 
Your Pi is likely, by default, to not be exposed to incoming connections from the outside world because your router is likely generating a private address range for your LAN (192.168.x.x or 10.0.x.x or 172.x.x.x) which means all incoming connections are effectively blocked at the router anyway unless you set up a 'port forward' record to allow packets arriving on certain ports to be forwarded to a specific internal IP address.
 
As for accessing your Pi across the internet, if you have set up a port forward, this likely has security ramifications. Even basic old fashioned protocols have proven in recent times to have uncaught flaws, so it's always advisable to lock down your device as much as possible, and even if you only plan to access the Pi over your LAN, install a firewall to configure this. I used one called ufw, because it's literally an uncomplicated firewall.
 
sudo apt-get install ufw sudo ufw allow from 192.168.0.0/16 to any port 22 sudo ufw --force enable 
 
This allows just port 22 (SSH) to be open on the Pi to any device on my LAN's subnet (192.168.0.x). You can change the above to a single IP address if paranoid, or add several lines, if you want to lock it down to your LAN and a specific external static IP address (e.g. a VPN service you use). To find out what subnet your router uses, just type:
 
ifconfig 
 
and you'll see on the interface you are using (either hard wired or wifi) the 192.168 or 10. or 172. prefix. Change the above rule so it matches the first two octets correctly (e.g. 10.0.0.0/16 if you're on a 10.0. address).
 
You may already use VNC to access your Pi's desktop across your LAN, this uses port 5900. Add a line like above to lock it down to an internal address. It's not a good idea to expose this port to the wider world because those connections are not encrypted and potentially could be subjected to a MITM attack.
 
You can query the status of the firewall like this:
ufw status 
 
And of course, try connecting remotely once you change the rules to see what works. You should consult the official documentation for further options: https://help.ubuntu.com/community/UFW
 
Back up & Recovery
 
There are again many ways to tackle this so I'll just speak about my basic precautions in this regard. Don't take it as a be-all-and-end-all!
 
The wallet.dat file is the key file (literally) containing all the private/public keys and transactions. This can be found in:
 
~/.lore 
 
You can navigate there using Jessie w/Pixel's own file manager or in a terminal window (cd ~/.lore). You can copy this file or, if you'd rather keep a plain text file of all your public and private keys, use the 'dumpwallet' command in the console. In Lore, go to Help > Debug Window > Console and type 'dumpwallet myfilename' where myfilename is the file you want it to spit out with all your keys in it. This file will end up in the same place you launch bitcoin-qt from.
 
The instructions earlier on, when running Lore for the first time intentionally left out encrypting your wallet.dat file because in order for the wallet to stake upon startup, it needs to have a decrypted key already. This isn't perfect, but after a power cycle, it would never stake unless you left it decrypted. So the best practice here is as soon as the wallet.dat file has left your device, i.e. you copy it to a USB stick for example, put it in an encrypted folder or drive (or both).
 
In Windows, one way is to use Bitlocker drive encryption for the entire drive. You should follow the instructions here to encrypt your flash drive before your wallet.dat is on there, and don't forget the password!!
http://infosec.nmsu.edu/instructions-guides/how-to-enable-bitlocker-to-go-for-external-hard-drives-and-usb-flash-drives/
 
On the Mac, I use a software package called Concealer to encrypt files I store on the Mac itself: http://www.belightsoft.com/products/conceale   There are almost certainly free packages with similar functionality, I have just used that one for years.
 
Either way, if you want to just make sure your USB drive is encrypted, you can do so in one-click in Finder before you put the sensitive files on it: http://lifehacker.com/encrypt-a-usb-stick-in-finder-with-a-click-1594798016
 
Note that these disk encryption methods may mean having to access the USB stick on a PC or Mac in order to retrieve the files in the event of a disaster. Be aware this may mean exposing them to more security issues if your computer is in any way compromised or someone nefarious has access to your computer. There are more 'manual' ways of backing up and recovering, such as literally writing down private/public key pairs which this guide doesn't go into, but may suit you better if paranoid about your setup.
 
Recovery
 
The wallet.dat file has everything in it you need to recover your wallet, or if you used 'dumpwallet', the file you saved out has all the keys.
 
Wallet.dat method: Install Lore as normal then replace any auto-generated wallet.dat in ~/.lore directory with your backup. If a lot of time has elapsed and many transactions have occurred since your backup, launch lore with:
./bitcoin-qt -rescan 
 
And if that doesn't do the job, do a full reindex of the blockchain:
 
./bitcoin-qt -reindex 
 
If you used the dumpwallet command, install Lore then place the file containing all the keys that you saved out in the same directory as bitcoin-qt. In Lore, go to Help > Debug Window > Console and type 'importwallet myfilename' where myfilename is that file containing all the keys. The wallet should automatically rescan for transactions at that point and you should be good to go.
 
There are a million ways to do effective security and disaster recovery, but I hope this shows you a couple of basic precautionary ways. There are discussions about better ways to stake without compromising too much security which are happening all the time and developments in this regard will happen in time.
 
In the meantime, feel free to comment with your best practices.
 
submitted by patcrypt to blackcoin [link] [comments]

Zeus/Gaw ASIC Setup Guide for Linux/Raspberry Pi

So I recently I became quite interested in mining and cyptocurrencies in general. So interested in fact that I bit the bullet and decided to buy myself a GAW Fury.
I then spent some time doing research on how to set up a GAW or Zeus ASIC on Linux, in particular on a Raspberry Pi, and have found most guides to be awful. The reason they are so bad IMHO is that they assume quite a bit of prior knowledge, either with Linux or mining, and give very little instructions. So I have tried to put together a guide that requires very little prior knowledge.
It is my aim that anyone could get their shiny new asic up and mining in no time using this guide. Anyway, I present...

The Complete Noobs Guide to Setting Up a Zeus or Gaw ASIC on Debian/Ubuntu/Raspberry Pi

Resources

About Cyrptocurrencies and Their Jargon

If you are new to cryptocurrencies and how they work I suggest taking a look at this series of KhanAcademy videos. They are for Bitcoin but the theory is the same. I found them very helpful when it came to understanding what mining actually does and the mechanics of cyrptocurrencies.
Also take a look at sircamm22 his info found here, is great and breaks down a large number of concepts. I slightly disagree with no. 21 regarding preordering. Just exercise common sense.

Linux

If you are new to Linux you could follow along by simply typing in the commands. However I highly recommend taking the time to learn what you are doing. This course is a great place to start.

Computer Setup

By the end of this section you will have your device turned on, fully setup and connected to the internet with.
Note: Commands to be typed into the command line will be displayed like this:
echo Hello World

Desktop/Laptop

For laptops and desktops already running Ubuntu or Debian I will assume you have setup your internet setup as part of the installation.
If not: There are plenty of guides out there and the installation/setup process is very easy. A good place to start for Ubuntu is here.
Now open up a terminal window. Ctrl + alt + t on a standard Ubuntu installation.
If you plan on using this PC without a monitor I would suggest installing an SSH Server.
These commands will be discussed later on in the guide.
sudo apt-get -y install openssh-server
sudo service openssh-server start

Raspberry Pi

The Raspberry Pi Foundation has put together a great guide in PDF format.
Use NOOBS it will save you a lot of trouble. NB: Some SD cards don't support NOOBs but will work fine if the image is put on using a different method.
Here is a great guide for setting up the Raspberry Pi SD card from Elinux.org. In fact it's a great place to start for anything RPi related. Raspberry Pi hub at Elinux.
Once the SD card is setup you will need to insert it into the Raspberry Pi and boot. Install Raspbian from the NOOBs menu and wait.
Follow this guide by Adafruit for first time setup. You will need to enable SSH Server.
I suggest not starting the desktop on boot. It can be easily run from the command line by typing startx.
Follow this guide by Adafruit to setup your network. Found here. No need to do this if you set up previously in the first time config.
We will also at this point want to setup ssh. Again I will point you to an Adafruit guide.
Once done exit back to a standard command line interface. This can be done in LXDE by using the power off menu located in the bottom right corner.

Miner Setup

Installing BFGMiner

If you want to the Raspberry Pi or PC without a monitor go ahead and SSH into your device.
So now you should be staring at a command line interface whether on the device with a monitor or via SSH.
First things first lets make sure we are all up to date. This will update our package list from the repositories and upgrade them to the newest version. "-y" Will simply say yes to any prompts.
sudo apt-get update && sudo apt-get -y upgrade
We are going to need to install some useful tools. Git-core is how we will clone and download BFGMiner from GitHub and Screen allows multiple command line instances and means if we exit out of ssh session or quit Terminal on Ubuntu, BFGMiner will continue to run.
sudo apt-get install git-core screen
We also need to download some other tools/dependencies to ensure that BFGMiner will compile successfully.
sudo apt-get -y install build-essential autoconf automake libtool pkg-config libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libevent-dev libmicrohttpd-dev libc-bin
Ok now change into your home directory.
cd ~
And clone BFGMiner by Darkwinde.
git clone https://github.com/Darkwinde/bfgminer.git
Once the download has completed move into the bfgminer directory.
cd bfgminer
The following steps may take a while.
Now run autogen.sh
sudo ./autogen.sh
You will need to make the configure script execuitable.
sudo chmod +x ./configure
Now configure bfgminer
sudo ./configure CFLAGS="-O3" --enable-scrypt
Now lets make!
sudo make
Install BFGMiner
sudo make install
One more thing...
sudo ldconfig

Running BFGMiner

If you haven't already plug in your ASIC.
Just confirm your system is recognising the ASIC.
lsusb
Its output should look similar to this (no need to type this in):
Bus 001 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Yep there it is our ASIC listed as device 005. There is no need to install any drivers, unlike in windows, as they come in the kernel.
Now lets actually start BFGMiner.
You will want to start a screen session to ensure BFGMiner doesn't quite when you exit.
"-S" is the option for starting a new screen session. You can replace "miner" with anything you like.
screen -S miner
Now you can run the commands below.
Here is a sample of what you should type. You will need to replace somethings with your own values.
sudo bfgminer --scrypt -o stratum+tcp://URL:PORT -u USERNAME -p PASSWORD --zeus-cc CHIPCOUNT --zeus-clk 328 -S zeus:/dev/ttyUSB0
Where:
URL:PORT is the address and port of the pool you wih to use. Now I won't suggest a pool. I will leave that decision up to you. If you do wish to mine DOGE take a look at this site for a list of pools and comparisons.
USERNAME this is the username you use on the pool. Every pool is different. Check your pool's website for details. PASSWORD same as above. Specific to your pool, not every pool requires one.
CHIPCOUNT this is specific to which ASIC you are using.
For GAWMiner ASIC's:
  • War Machine: 256
  • Falcon: 128
  • Black Widow: 64
  • Fury: 6
For ZeusMiner ASIC's:
  • Blizzard: 6
  • Cyclone: 96
  • Hurricane X2: 48
  • Hurricane X3: 64
  • Thunder X2: 96
  • Thunder X3: 128
Now to make sure you don't stop mining when you exit ssh or terminal. Press:
ctrl + a + d
To come back to the BFGMiner screen simply run:
screen -r miner
You're done!!

Start on Boot

First off you will want to make sure you have BFGMiner running correctly. Ensure you have the miners set up properly and your pool correctly configured.
Start a BFGMiner instance, detailed above.
Once the instance has started and you are happy with how everything is working press "s" on your keyboard to enter the settings menu.
Now press the "w" key. Don't press enter. We want to specify where our config will go. Type:
/home/USERNAME/bfgminer.conf
Substitute USERNAME for your user. On a standard RPI install its pi. On ubuntu it's what you set during the instillation.
Now press the enter key to return back to the main BFGMiner screen. Press "q" on your keyboard to exit BFGMiner. You should now be back in the command line.
Now we want to edit a file called rc.local. Any commands in this file will be executed on boot.
sudo nano /etc/rc.local
Depending on your system this file may already contain some commands. Be careful not to delete them.
After the last command and before "exit 0" type the following on one line:
sudo -u USERNAME screen -d -m sudo bfgminer --config /home/USERNAME/bfgminer.conf
Where USERNAME = your username
Hit ctrl + x then y to save and exit nano.
The above command will create a new screen session and run bfgminer using the config we created earlier. All while as our username so that we can easily reattach.
Lets reboot to ensure it is working correctly:
sudo reboot
Once rebooted and logged in, show all running screen sessions:
screen -ls
Reattach to the session. You only need to use the numbers before the first dot.
e.g Mine looks like: 2480..hostname (13/07/14 12:02:09) (Detached). So I type:
screen -r 2480
Verify everything worked as expected. Then ctrl + a + d to exit.
You have now setup BFGMiner to restart on reboot.

Power Failure

If you are using a Raspberry Pi and it loses power it will automatically reboot on receiving power again.
For standard desktop PCs there is an option in some BIOS/UEFI to turn the computer on when it receives power. Consult your motherboard's manual and manufacturer's website.

Sources

Here is where I got my info from.
And of course /dogemining

Wrap Up

Congrats you've done it. You have managed to successfully get your shiny new asic mining away.
I do plan to make another guide detailing how to setup and use StarMiner a ready to go RPi mining distro.
So I hope this is helpful for you guys. I have seen lots of posts asking the exact same questions again and again and I have tried to answer these as best I can. I am still learning about this stuff so if there is something I have missed or a mistake I have made please tell me.
Anyway good luck. And I'll see you at the moon.
Cheers Frogsiedoodle
Edit 1: Layout and formatting.
Edit 2: Added instructions for screen which I initially forgot.
Edit 3: Removed 1 unneeded dependency
Edit 4: Added section on start on reboot and power failure.
submitted by Frogsiedoodle to dogemining [link] [comments]

Colored coin client preview #1 (based on Bitcoin Armory)

I think it's already good enough for people to play with it. (Although certainly it's not ready for anything serious.)
For people who are not familiar with concept, colored coins is a technology which allows people to represent arbitrary tokens (e.g. issue private currencies, stocks, bonds, etc.) using small quantities of bitcoins. It is interesting because it would allow us to create decentralized and secure markets. (As decentralized and secure as Bitcoin itself, at least in theory.) See here.
Notes about current release:
Windows binaries: http://killerstorm.xen.prgmr.com/alex/ArmoryX-0.2.5.zip
There are no Linux binaries, but it's really easy to build it on Ubuntu or Debian:
(Note: if you're already using Armory, it is a good idea to hide you ~/.armory so it won't be seen by this experimental Armory mod. Or, perhaps, just don't run this experimental mod.)
Before you run it, make sure that bitcoind or Bitcoin-Qt is running and fully sync'ed. Armory takes up to 10 minutes to start (this version is slower because it additionally scans for colored transactions) and requires ~ 1 GB of RAM.
At start it will offer to create a wallet, do not enable encryption, otherwise issuing colored coins won't work.
Send some bitcoins to this new wallet, 0.02 BTC is probably enough to issue some colored coins and to pay for tx fees.
There is a drop down to choose color. Balance is displayed for a currently chosen color (i.e. if you chose TESTcc it will show how many TESTcc units this wallet owns), and when you send coins you send coins of that color.
Initially 'uncolored' is selected, it means normal BTC. This drop down also has TESTcc ("test colored coins") and "All colors" (this mode is just for debugging, you cannot send coins in this mode).
Here's what you can do now:
  1. Ask somebody to send you TESTcc. (We want to make it automatic, Satoshi Dice style, but unfortunately that code isn't quite ready.)
  2. Find and install other color definitions.
  3. Issue your own colored coins and send them to somebody who wants them. (LOL.)
Let's start from option #3. There is 'Hallucinate' menu. (It is called 'hallucinate' because colors do not exist on blockchain level, it is a client-side convention.) Choose 'Issue colored coins'. Likely all you need to change is name, but you can tweak satoshi-per-unit and number of units if you want.
When you click Issue it will create a new transaction (using your uncolored BTC) and will create a color definition. Optionally it will also upload your color definition to color definition registry. (This registry runs on my server, it might be down.)
You should note ColorID, this is how other people can refer to these coins (name is ambiguous).
You can now choose this new color in drop down and it will show your balance. (E.g. 1000 units.)
Now you'll perhaps want to send these coins to somebody. That person would need to install your color definition first. If you send colored coins without warning they might be lost, i.e. mixed with uncolored ones. For same reason it makes no sense to send them to wallet which isn't color aware.
For example, you can post on some forum:
I've issued LOLwut coins (ColorID: 36738fe78a443656535503efb585fee140a37d54), each unit represents a bond with face value of 0.1 BTC payable by me, Trololo, via buy back. I promise to buy back all bonds in a month.
Now people who are interested in this LOLwut coin issue will copy ColorID, paste it into Hallucinate > Download color definition dialog, and if this color definition is published it will be downloaded and installed. Armory restart is required to complete installation.
After installation that person will be able to see these LOLwut coins.
Note that if you do not trust my registration server, you can publish color definition yourself: go to ~/.armory/colordefs, find 36738fe78a443656535503efb585fee140a37d54.colordef and upload it to your web server. Then you can give people URL like http://example.com/36738fe78a443656535503efb585fee140a37d54.colordef and they can download it by URL.
Or they can just obtain this file by any means and copy it to ~/.armory/colordefs directory. It is decentralized, nobody can prevent you from issuing colored coins.
I think that's all. There is also Hallucinate > Manage color definitions dialog, but I hope it's easy to figure out how it works.
We are working on improved version, particularly on p2p exchange feature.
I've set up an IRC channel for people to talk about trying out colored coins: #colored-coins-otc on Freenode.
submitted by killerstorm to Bitcoin [link] [comments]

New Level of Jackassery: A Long-Winded Story of a Minor BitCoin Folly

[Throwaway for reasons soon be obvious.]
TLDR: I spent a lot of effort making a nice paper wallet that I promptly left on the trunk of my car as I drove away. I found it in the street four hours later.
I had been trying to put together a secure setup for creating paper wallets. My plan involved a spare laptop and a bootable USB drive running some Linux distribution. Once complete I would use BitCoin Paper Wallet to print a high quality wallet in full color on card stock, and even use the hologram stickers sold to seal them. Then I'd store them somewhere safe.
With small children, I do not get as much time as I like to work on these types of projects, but after a week had passed, after I switched from Tails to Ubuntu, and after I finally came to a solution to persistent encrypted storage on the USB drive when Ubuntu is running the LiveCD (LiveUSB), I did it.
A laptop of mine recently lost its screen in a tragic fall from a precarious position, it made for a perfect air gapped computer to boot my USB drive to. Boot, login to encrypted drive, install the necessary fonts, install the printer driver, print, cut, seal with hologram, insert into plastic sleeve, import address, transfer 1 BTC to address and store paper wallet in secure location.
A few days later I pull one of the paper wallets I printed from my secure location to take to a birthday party my daughters were attending at the house of a friend of mine. I thought my friend might appreciate it. I carried it in my hand along with my two kids, a present for the birthday boy, and everything else a father needs when wrangling small children. I struggled loading the gear and the children safely, and decided to set the wallet on the trunk of my car.
I distinctly remember thinking to myself, "Don't forget to pick that up." I loaded the car and drove away.
Two hours later, at a pirate-themed birthday party at which I saw two small children in a Jeep power wheels toy run over other children because they didn't realize there was a steering wheel, I froze and I am sure I turned ghostly white.
My instinct was to rush home immediately, but my kids were having a great time and I couldn't quite explain to our host that I had to leave to retrieve $800 worth of card stock I printed on my computer and left on my car. I simply had to wait. I felt myself start into the five stages of denial. First up, denial. Maybe I had gotten it, and just forgot. Maybe the aerodynamics of the car are such that the paper just happened to stick to the trunk just in front of the spoiler (if that's what Honda wants to call that little nub).
After we left the party, at which I saw a piñata with a trap door that the parents just opened to release the candy, we left for home. As I entered our neighborhood I retraced my path from earlier in the day. I scanned the streets looking for anything that looked like a plastic sleeve. I saw nothing on the streets that led to mine.
As I turned the last corner onto my street a small glimmer caught my eye. I focused on it and made out a rectangular shape. I quickly parked, pulled out the child old enough to not wildly run into the street, and proceeded to run into the street myself without looking for traffic.
There is was, my BitCoin, snug in its plastic sleeve no worse for wear. My fears that someone had found it and I would spend a lifetime following how it would be spent over the years were gone. And it was in pretty good shape. I don't live on a high traffic street, but we were gone for four hours and my BitCoin must have had a few close calls. The sleeve looked great, and my holograms do not appear to have been tampered with.
I'm still transferring the funds to a new address ASAP.
Edit: Moved TLDR to top.
Edit Again: temper = tamper.
submitted by bitreckless to Bitcoin [link] [comments]

HOdlcoin CPU Solo Mining Guide

Windows guide

https://github.com/HOdlcoin/HOdlcoin/blob/HODLCoin0.11.3/doc/README.md

Linux/Ubuntu 14.04 build guide

Enter each of these on your command line (you may need to Press [Y] or [enter] sometimes)
Code:
 sudo apt-get update sudo apt-get install checkinstall subversion git git-core sudo apt-get install libssl-dev libminiupnpc-dev sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev sudo apt-get install build-essential libboost-all-dev automake libtool autoconf sudo apt-get install pkg-config git clone https://github.com/FreeTrade/HOdlcoin cd HOdlcoin ./autogen.sh && ./configure --without-gui make sudo make install mkdir -p ~/.hodlcoin/ echo -e "rpcuser=rpc\nrpcpassword=1234\nserver=1\np2pport=1989\nrpcport=11989\ndaemon=1\ngen=1\nminermemory=4\ngenproclimit=8\nminingaddress=yourwalletaddresshere" > ~/.hodlcoin/hodlcoin.conf 
minermemory= the amount of Ram in 1gb increments (1,2,3)
genproclimit= the number of threads per 1gb of ram from "minermemory" (this number must be a power of 2 so 2,4,8,16,)
miningaddress= yourwalletaddresshere this is the address all your mined blocks will be sent to (example "HodlDsNuts57MFNiN8CMrMjC2CYAy8pwi9")
NOTE: If you do not want to mine all your blocks to the same address Omit from above \nminingaddress=yourwalletaddresshere

Once built follow steps below to start the wallet mining

Start server
Code:
 hodlcoind 
If this is your first time running this wallet wait 10 mins for the blockchain to sync then Stop
Code:
 hodlcoin-cli stop 
wait a few seconds then and restart
Code:
 hodlcoind 
To see your hashrate use this
Code:
 cd ~/.hodlcoin/ tailf debug.log 
To exit from this debug file Press [Ctrl] + [C]
To monitor your Ram/CPUs install this Code:
sudo apt-get install htop 
Use it with this
Code:
 htop 
To exit Press [F10]
Insure the proper amount of CPUs are running at 100%

For Help or to Chat

We have an active Slack community use this link to join the chat
http://slack.hodlcoin.com
Also on IRC
#hodlcoin on freenode 
submitted by Hodl_coin to Hodl [link] [comments]

Debian OS issue(s) with Trezor hardware wallet and Electrum software wallet

My goal is to move my stored bitcoin from mytrezor web wallet to electrum wallet with trezor integration, but I am finding this task to prove challenging.
I was able to get electrum running on Debian without an issue by following electrum's writeup which is as simple as it gets. My problems started when I attempted to plug my trezor in and create a new hardware wallet. I did not install the trezor python plugin/API's for electrum prior to installing electrum, which resulted in Ledger Wallet being the only option listed under "create new - hardware wallet." I then started over trying to install the API's first. However, I could not get them installed successfully.
sudo apt-get update sudo apt-get install python-dev python-setuptools cython git libusb-1.0-0-dev libudev-dev git clone https://github.com/trezopython-trezor.git cd python-trezor sudo python setup.py install 
This resulted in an error:
Error compiling Cython file: ------------------------------------------------------------ ... cdef extern from "stdlib.h": void free(void* ptr) void* malloc(size_t size) cdef extern from *: object PyUnicode_FromWideChar(const wchar_t *w, Py_ssize_t size) ^ ------------------------------------------------------------ hid.pyx:14:46: Expected ')', found '*' hid.c:1:2: error: #error Do not use this file, it is the result of a failed Cython compilation. error: Setup script exited with error: command 'gcc' failed with exit status 1 
I am also unable to get the Trezor Bridge installed, my install just hangs at around 50%. I am essentially a linux noob, but I did have Trezor working with mytrezor wallet service alongside a much earlier version of electrum when I had Ubuntu installed as my last OS. I don't know if I am just still in need of practice with my Debian system or if perhaps someone out there has a fix for me. Thanks for any response.
Edit: I just realized it would probably be helpful to note I am attempting to access mytrezor web wallet with Iceweasel which may or may not be an issue
submitted by DeborahIan to TREZOR [link] [comments]

The straightforward Bitcoin safety and security guide

Seen those posts of people who come here to commiserate about how they got their coins robbed?
OK, let's make sure that does not happen to you.

Make sure your computer is safe

Pirated Windows? You're gonna have a bad time.
Those pirated copies normally have slipstreamed key logger software and remote control software. If you receive bitcoins or log into an exchange there, you will lose your money. Also think of our bank accounts and credit card numbers.
How to recover from this situation? Back up your data, blow away your computer's disk, install original Windows from the CD, install drivers from the CD, install Windows updates.
Never use that Windows machine to browse for porn or warez. Do not install software you did not get from the manufacturer. Disable Flash (or use Chrome's sandboxed Flash) and do not think of installing Java. Do not visit sites whose security has been compromised (Chrome will tell you).
"Too expensive"? Install Ubuntu then, possibly dual-booting Windows too. Make sure to encrypt your disk (the Ubuntu installer can do that automatically, so choose full disk encryption by default).
The password must not be your login password. It should be a long phrase with made-up words that makes sense only to you. Take measures to keep a copy of that password somewhere you and only you can access. Bank safes are not safe -- they are the first place governments subpoenapilfer private info from.
Then do Ubuntu updates, weekly.
When you are on Ubuntu, do your normal Bitcoin stuff. Refrain from doing any of that while on Windows. Refrain from using "browser sync" of Firefox or Chrome under Windows.
If you behave like this, then Windows programs can't see the Ubuntu data, and Windows malware generally can't jump into Ubuntu and watch what you do, so you are safe that way. Ubuntu by default also locks your screen after a few minutes of inactivity, so there's more security out of the box. You can also Ctrl+Alt+L to lock it by hand.
This way you can watch your furry porn on Windows while keeping your money safe.
"Too hard"? Well then, I'm sure being robbed possibly hundreds of thousands will be easier for you. Irresponsibility costs you and your family, be prepared to pay.

Encrypt your wallet

Whatever choice of wallet software you use, encrypt it from the start. You did not encrypt it? You're gonna have a bad time.
Encrypting your wallet makes it so malicious people who obtain access to your wallet.dat file, cannot spend it. They need the password as well.
The password must not be your login password, or your disk encryption password. It should be a long phrase with made-up words that makes sense only to you. Take measures to keep a copy of that password somewhere you and only you can access. Bank safes are not safe -- they are the first place governments subpoenapilfer private info from.

Never leave money floating in exchanges

Exchanges fail (some because the owners are frauds, most of the time because of government sabotage). Left lots of money on those exchanges? You're gonna have a bad time.
Always transfer as much as you can to your computer walled. Once you have it in your computer, and your computer is secure, it will be very hard for anyone to rob you without threatening or initiating physical violence against you.
In the Bitcoin world, exchanges are not banks. Your computer is. Trust first the environment you control, over the environment strangers control.

Don't squawk about your holdings

You don't blabber about your bank account balances or your credit purchasing power.
Don't do it about Bitcoin either.
This is just common sense.
Now for the tech advice: whenever you receive Bitcoin from anybody, use a new address every time. This prevents any single address from pooling enormous amounts of bitcoins.
Why is that something you want do prevent? Because the balance of addresses will be visible to the next person you send money to, as he can see the size of the transaction inputs.
You are the owner of what you keep to yourself, and a slave to what you say.

Back your data up

At the very least, back up your user profile / home directory. Regularly. Optimally after receiving or sending money.
Make sure your backup is encrypted too. A smallish external hard disk is not hard to buy. You can encrypt, unlock and mount, and lock and eject the disk, using the Disks tool that ships with Ubuntu.
You can do the backup by hand if you know what files to copy, or you can use a simple terminal command like rsync -av --delete $HOME/ /mnt/whereverthediskwasmounted/ which will back everything up in your home directory.
Stay away from El Cheapo USB sticks, as they can eat your data silently. Never remove the disk while on the middle of writing data to it. Make sure it is safe to remove before unplugging it. The Disks utility will allow you to know, for sure, when that is safe.
Try to keep the disk away from the computer. Computers catch fire sometimes.

Conclusion

You have the tools necessary to protect yourself from theft of invaluable assets. Use them. Or pay the price.
Feel free to ask me any questions.
submitted by throwaway-o to Bitcoin [link] [comments]

Problem securing cold wallet (Multibit won't run from jar file on live CD)

Lurker here, having difficulties setting up a cold wallet. Not sure where best to post this (bitcoin or BitcoinWallet and so on).
I'm trying to create a cold wallet following the How to set up a secure offline savings wallet instructions, but step 7 ("Run bitcoin while disconnnected from the internet.") has been a headache. I simply cannot get the jar file to run and I can't install Java (remember: connecting to the net with the live Ubuntu CD would defeat the purpose of this). I have scoured the net and found no solutions to this problem, only forums where people go through the commands I've been fiddling with. Can anyone provide a solution?
I'm also afraid that if I get this to work now, by the time I go back to check my cold wallets, I won't be able to get this to work then, and the wallets would be rendered inaccessible. So if this procedure can't be followed what do you recommend? I would most like if my main wallet never touched a Windows system, nor an online system, but I am open to other options (the most secure you can provide).
Here are the alternatives I'm considering (critique welcome):
  1. Install Ubuntu on old PC. Install Java and Multibit, then remove network card (i.e. ability to connect to net). Use this computer only for offline things and cold storage of Bitcoin wallets. Back-up wallets on USB sticks. Isn't this almost effectively as safe as running the live Ubuntu CD?
  2. Save main bitcoin 2fa wallet on USB stick (and back-ups). Maybe encrypt USB stick(s).
What do you think of these alternatives?
tl;dr How do you get the Multibit jar file to run with the Ubuntu live CD without connecting to the net; if not possible what are the best, most secure solutions for cold storage of wallet?
submitted by Mad_Marx_Beyond_Capi to BitcoinBeginners [link] [comments]

Bitcoin Install and Update on Ubuntu Linux ( my experience ) How to install Linux without CD or USB - YouTube How to Bitcoin Miner with Ubuntu VPS - Setup Nicehash Miner via Ubuntu VPS How to install Bitcoin Armory in Ubuntu 14.04 Install Ubuntu by booting ISO image on hard disk (without burn CD/DVD or USB flash drive)

Bitcoin Core is a community-driven free software project, released under the MIT license. Verify release signatures Download torrent Source code Show version history. Bitcoin Core Release Signing Keys v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+ Or choose your operating system. Windows exe - zip. Mac OS X dmg - tar.gz. Linux (tgz) 64 bit. ARM Linux 64 bit - 32 bit. Linux (Snap Store) Support ... In this step-by-step guide we will show you 'How to install blockchain on Ubuntu Blockchain.' Blockchain is, quite literally, a chain of blocks that contain and distribute digital information (the block) stored in a public database (the chain). The blocks store different types of information. Say, for instance, blockchain is being used to store customers’ information. Fresh install of Ubuntu 19.10. There are many online guides for this. A fast, unmetered, and reliable internet connection. If you have VDSL or better, you are good to go. At least 400Gb of free ... To install Ubuntu without CD/DVD or USB pendrive, follow these steps: Download Unetbootin from here. Run Unetbootin. Now, from the drop-down menu under Type: select Hard Disk. Next select the Diskimage. Browse to the directory where you downloaded the iso file of Ubuntu. Press OK. Next when you reboot, you will get a menu like this: In summary - if you dont want to install. a new versions of bitcoin either via ppa's or from the latest source on the bitcoin website, or; update the wxwidget libraries, you should logout of Unity and choose the session "Ubuntu classic (no effects)" - i.e. running ubuntu without any compiz effects.

[index] [25746] [49339] [46756] [47603] [33297] [1771] [28692] [34984] [41633] [24986]

Bitcoin Install and Update on Ubuntu Linux ( my experience )

In this videos, I am going to show how to install Linux without CD or USB. To install any type of Linux base OS, No need any USB, CD, DVD. Just use internal ... minar bitcoin con nicehash en ubuntu aki os dejo los comandos: sudo apt-get install cmake build-essential libboost-all-dev git clone -b Linux https://github.... Get Bitcoin Wallet In Linux Mint ( Ubuntu ), No Installation Required - Duration: 5:11. linuxforever 11,087 views. 5:11 . How to quickly start mining bitcoins [Easy] - Duration: 7:59. Vague Man ... sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install bitcoin-qt bitcoind Linux terminal new stuff: clear, ll, cd, touch, echo, cat, shutdown www.bitcoinhackers.org How to mining Bitcoin with your Ubuntu VPS? Earn 0.0001 BTC per VPS, if you have 10 VPS, you will earn 0.001 BTC per day (~2.5 USD), if you have a lot of VPS, you will earn more BTC per day. Setup ...

#