Get Ubuntu Download Ubuntu

Ubuntu 20.04 Root on ZFS HOWTO

I'm pleased to announce the Ubuntu 20.04 Root on ZFS HOWTO.
This version has some significant changes. Please test thoroughly before using this setup on any production systems. Your feedback is very welcome—here or via the issue tracker.
This now uses a dataset layout that matches that created by the Ubuntu installer and accordingly supports zsys. For more information on zsys, see the articles from didrocks's blog, Ars Technica (written by mercenary_sysadmin), and Phoronix.
Additionally, thanks to work by George Melikov, the documentation (including these HOWTOs) has moved from being Markdown in the GitHub wiki to a Sphinx-based system in a separate openzfs-docs repository. Previously, the wiki only allowed edits by approved contributors and GitHub wikis do not support pull requests. This new repository allows for pull requests, which opens the door to more people to contribute to the OpenZFS documentation. Having a separate repository also means there is a separate issue tracker.
If this or any of my open source work has been useful to you, please consider sponsoring me if you are able. Recurring sponsorship is available via GitHub Sponsors and one-time sponsorship can be done via PayPal. If you prefer Bitcoin, you can use: 3LyXJSiL6C2d6qEF8VcRciT2VJWNhqbWJ4
submitted by rlaager to zfs [link] [comments]

Running a Bitcoin node on a $11.99 SBC

Running a Bitcoin node on a $11.99 SBC
Just wanted to let you guys know that I'm successfully running a (pruned) Bitcoin node + TOR on a $11.99 single board computer (Rock Pi S).
The SBC contains a Rockchip RK3308 Quad A35 64bit processor, 512MB RAM, RJ45 Ethernet and USB2 port and I'm using a 64GB SDCard. It runs a version of Armbian (410MB free). There's a new version available that even gives you 480MB RAM, but I'm waiting for Bitcoin Core 0.19 before upgrading.
To speed things up I decided to run Bitcoin Core on a more powerful device to sync the whole blockchain to an external HDD. After that I made a copy and ran it in pruned mode to end up with the last 5GB of the blockchain. I copied the data to the SD card and ran it on the Rock Pi S. After verifying all blocks it runs very smoothly. Uptime at the moment is 15 days.
I guess you could run a full node as well if you put in a 512GB SDcard.
The Rock Pi S was sold out, but if anybody is interested, they started selling a new batch of Rock Pi S v1.2 from today.
Screenshot of resources being used
Bitcoin Core info
Around 1.5 GB is being transferred every day
---
Some links and a short How to for people that want to give it a try:
  1. This is the place where I bought the Rock Pi S.
  2. Here you find more information about Armbian on the Rock Pi S. Flash it to your SDCard. Follow these instructions.
  3. Disable ZRAM swap on Armbian. If you don't do this eventually Bitcoin Core will crash. nano /etc/default/armbian-zram-config ENABLED=false
  4. Enable SWAP on Armbian sudo fallocate -l 1G /swapfile sudo chmod 600 /swapfile sudo mkswap /swapfile sudo swapon /swapfile sudo swapon --show sudo cp /etc/fstab /etc/fstab.bak echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab
  5. Set up UFW Firewall sudo ufw default deny incoming sudo ufw default allow outgoing sudo ufw allow ssh # we want to allow ssh connections or else we won’t be able to login. sudo ufw allow 8333 # port 8333 is used for bitcoin nodes sudo ufw allow 9051 # port 9051 is used for tor sudo ufw logging on sudo ufw enable sudo ufw status
  6. Add user Satoshi so you don't run the Bitcoin Core as root sudo adduser satoshi --home /home/satoshi --disabled-login sudo passwd satoshi # change passwd sudo usermod -aG sudo satoshi # add user to sudo group
  7. Download (ARM64 version) and install Bitcoin Core Daemon
  8. Download and install TOR (optional). I followed two guides. This one and this one.
  9. Create a bitcoin.conf config file in the .bitcoin directory. Mine looks like this: daemon=1 prune=5000 dbcache=300 maxmempool=250 onlynet=onion proxy=127.0.0.1:9050 bind=127.0.0.1 #Add seed nodes seednode=wxvp2d4rspn7tqyu.onion seednode=bk5ejfe56xakvtkk.onion seednode=bpdlwholl7rnkrkw.onion seednode=hhiv5pnxenvbf4am.onion seednode=4iuf2zac6aq3ndrb.onion seednode=nkf5e6b7pl4jfd4a.onion seednode=xqzfakpeuvrobvpj.onion seednode=tsyvzsqwa2kkf6b2.onion #And/or add some nodes addnode=gyn2vguc35viks2b.onion addnode=kvd44sw7skb5folw.onion addnode=nkf5e6b7pl4jfd4a.onion addnode=yu7sezmixhmyljn4.onion addnode=3ffk7iumtx3cegbi.onion addnode=3nmbbakinewlgdln.onion addnode=4j77gihpokxu2kj4.onion addnode=5at7sq5nm76xijkd.onion addnode=77mx2jsxaoyesz2p.onion addnode=7g7j54btiaxhtsiy.onion ddnode=a6obdgzn67l7exu3.onion
  10. Start Bitcoin Daemon with the command bitcoind -listenonion
Please note that I'm not a professional. So if anything above is not 100% correct, let me know and I will change it, but this is my setup at the moment.
submitted by haste18 to Bitcoin [link] [comments]

Deployed (on server) Django 3 project doesn't sees static files

#Deployed #Django3 #not #loands #static #files Deployed (on server) Django 3 project doesn't sees static and css files(whole static folder), the local on development machine works perfectly.

The guide that I have followed is [this](https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-18-04).
- I have et up a Digital ocean droplet with ubuntu 18.04
- my static files can be found here
STATICFILES_DIRS = [os.path.join(BASE_DIR, 'mymainapp/static/')] #STATIC_ROOT = os.path.join(BASE_DIR, 'static') # Removed based [on](https://stackoverflow.com/questions/60354519/django-base-html-extended-to-homepage-html-static-images-appear-but-home-css-d) STATIC_URL = '/static/' MEDIA_ROOT = os.path.join(BASE_DIR, 'mymainapp/media') MEDIA_URL = '/media/' 
- Than all the other staff with Postgres, Nginx, and Gunicorn as in the [guide](https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-18-04)
- but the static files (image, SVG, css, files doesn't load in)
- I have my bootstrap CSS files downloaded to local directory
- The website is online and if I press F12 in chrome it puts out the following error messages (turning ```DEBUG = True``` does not deliver any more error messages or error page)
Failed to load resource: the server responded with a status of 404 (Not Found) homepage03_comp.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) logo_03c_small.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) jquery.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found) bootstrap.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found) popper.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found) tiktok_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) instagram_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) twitch_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) twitter_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) youtube_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) facebook_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) bootstrap.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found) mobile_features_large_compressed.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) creator_platforms_comp.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) creator_sm_comp.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) reoccuring_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) stripe_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) customerchat.php?app_id=&attribution=setup_tool&channel=https%3A%2F%2Fstaticxx.facebook.com%2Fconnect%2Fxd_arbiter.php%3Fversion%3D46%23cb%3Df2ca0722231e688%26domain%3D159.65.234.146%26origin%3Dhttp%3A%2F%2F159.65.234.146%2Ff167133a445f9a4%26relation%3Dparent.parent&container_width=0&locale=en_US&page_id=2172253486430236&sdk=joey:1 Failed to load resource: the server responded with a status of 500 () paypal_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) googleads1_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) googlepay_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) amazon_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) bitcoin_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) logo_02_Background.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) shirts_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) message_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) sopnsor2_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) socialmedia_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) combinedbarnad_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) applepay_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) check.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) feature_description_laptop_cut.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) self_image_comp.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) reddit_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) linkedin_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) collie_2_comp.jpg:1 Failed to load resource: the server responded with a status of 404 (Not Found) bootstrap.min.css:1 Failed to load resource: the server responded with a status of 404 (Not Found) DevTools failed to parse SourceMap: chrome-extension://hnmpcagpplmpfojmgmnngilcnanddlhb/browser-polyfill.min.js.map DevTools failed to parse SourceMap: chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/include.preload.js.map DevTools failed to parse SourceMap: chrome-extension://hnmpcagpplmpfojmgmnngilcnanddlhb/browser-polyfill.min.js.map DevTools failed to parse SourceMap: chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/include.postload.js.map 
- I had the same errors before going thru the guide and just haveing a basic pulled git version of it and running with ```python3 manage.py runserver``` it loads the site but not the css and the static elements
- I have put the base ```/media``` and ```/static``` folders in to git ignore (these should be the one where collect static collets up the element). The original static is under the ```myowndjango-project/myowndjango/static``` and ```myowndjango-project/myowndjango/media```
- I have also set up the nginx as follows
... location /static/ { root /home/myserverusemyowndjango-project; } location /media/ { root /home/myserverusemyowndjango-project; } ... 
What I have tried to solve it
- look for server access log
- run ```/valog/nginx/access.log``` result: ```-bash: /valog/nginx/access.log: Permission denied```
- run ```sudo /valog/nginx/access.log``` result: ```sudo: /valog/nginx/access.log: command not found```
- changing nginx file
... location /static/ { root /home/myserverusemyowndjango-project/myowndjango/static; } location /media/ { root /home/myserverusemyowndjango-project/myowndjango/media; } ... 
- Running
python3 manage.py collectstatic 
(restarted nginx and gunicorn) and it still does the same error.

Thank you for the help.
submitted by glassAlloy to djangolearning [link] [comments]

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]

Vertnode - An automated solution for installing Vertcoin node(s) on Single Board Computers

Hello Vertcoin Community,
Eager to contribute to the Vertcoin Community I began creating step by step walkthrough guides on how to get a Vertcoin node up and running on a Raspberry Pi, Raspberry Pi Zero and Intel NUC. Along with information to get a Vertcoin node up and running was also optional steps to install p2pool-vtc.
I decided that while this step by step guide might be helpful to a few, a setup script may prove to be useful to a wider range of people. I have this script to a point where I think it may be productive to share with a bigger audience, for those who are brave and have this hardware sitting around or like to tinker with projects; I invite you to test this setup script if you are interested, if you run into errors any sort of verbose console output of the error proves to be extremely helpful in troubleshooting.
The script was designed to produce a “headless” server... meaning we will not be using a GUI to configure Vertcoin or check to see how things are running. In fact, once the server is set up, you will only interact with it using command line calls over SSH. The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc.
Why run a headless node on a Single Board Computer?
The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc.
Required: USB Flash Drive 6GB - 32GB
Please note that the script was designed for Single Board Computers first and looks for an accessible USB Flash Drive to use for storing the blockchain and swap file, as constant writing to a microSD can degrade the health of the microSD.
Supports

Hardware

All of the hardware listed above is hardware that I have personally tested / am testing on myself. The plan is to continue expanding my arsenal of single board computers and continue to add support for more hardware to ensure as much compatibility as possible.
Functionality
It is worth noting that LIT can be ran with multiple configurations, the ones displayed in the Post Installation Report reflect values that run LIT with the Vertcoin Mainnet. Please be aware that the Vertcoin Testnet chain has not been mined 100% of the time in the past, if you make transactions on the Vertcoin testnet that do not go through it is likely because the chain has stopped being mined.
BE CAREFUL WITH YOUR COINS, ONLY TEST WITH WHAT YOU ARE OKAY WITH LOSING IF YOU USE THE MAINNET.

Vertcoin Testnet Coins

https://tvtc.blkidx.org/faucet/
I've included some documentation on LIT I created which includes information I found to be useful: https://github.com/e-corp-sam-sepiol/vertnode/blob/mastedocs/lit.md
Please visit the mit-dci/lit github repository for the most up to date information on lit: https://github.com/mit-dci/lit

Vertnode | Automated Vertcoin Node Installation Script

https://github.com/e-corp-sam-sepiol/vertnode

Recommended: Use Etcher to install the chosen OS to your microSD card / USB flash drive.

If you intend on installing Ubuntu Server 16.04 to your Intel NUC please use Etcher to install the .iso to your USB flash drive.
https://etcher.io/
PLEASE NOTE THIS SCRIPT MAY GIVE AN ERROR. THIS IS THE NATURE OF TESTING. PLEASE REPORT YOUR ERRORS IF YOU WANT THEM TO BE FIXED/RESOLVED. THANK YOU FOR BETTERING THE DEVELOPMENT OF THIS SCRIPT.

Ubuntu Server 16.04 Setup Details

You can use different clients to ssh into your node. One option is using PuTTY or Git Bash on Windows which is included in the desktop version of Git. If you are using Linux you can simply open a new terminal window and ssh to the IP address of your node (hardware you intend installing the Vertcoin node on).
You will need to know the IP address of your node, this can be found on your router page.
ssh 192.168.1.5 -l pi For example, this command uses ssh to login to 192.168.1.5 using the -l login name of pi. The IP address of your node will likely be different for you, in this example I am logging into a Raspberry Pi which has a default login name of pi.
A brief list of commands that can be used to check on the Vertcoin node status:
vertcoin-cli getblockchaininfo | Grab information about your blockchain
vertcoin-cli getblockcount | Grab the current count of blocks on your node
vertcoin-cli getconnectioncount | Grab the current count of connections to your node. A number of connections larger than 8 means that you have incoming connections to your node. The default settings are to make 8 outgoing connections. If you want incoming connections please port forward your Raspberry Pi in your Router settings page.
vertcoin-cli getpeerinfo | Grab the information about the peers you have connected to / are connected to
vertcoin-cli getnettotals | Grab network data, how much downloaded/upload displayed in bytes
tail -f ~/.vertcoin/debug.log | Output the latest lines in the Vertcoin debug.log to see verbose information about the Vertcoin daemon (ctrl+c to stop)
Thank you to all who have helped me and inspired me thus far, @b17z, @jamesl22, @vertcoinmarketingteam, @canen, @flakfired, @etang600, @BDF, @tucker178, @Xer0
This work is dedicated to the users of Vertcoin, thank you for making this possible.
7/20/2018 Thank you @CommodoreAmiga for the incredibly generous tip <3
You can reach me @Sam Sepiol#3396 on the Vertcoin Discord, here on reddit or @ [email protected]
submitted by ecorp-sam-sepiol to vertcoin [link] [comments]

How to install any QT-Wallet on the Raspberry Pi / Pi3B+

Hello and welcome to my first tutorial. Today I will show you how to install almost any QT-wallet on the RaspberryPi. I hope this tutorial will help you. I use the BankSocietyCoin in this tutorial, you can change it also to your fav. Coin.

Install Raspbian , *Buster produced a lot of failures on my system while compiling Wallets*
(my version: https://downloads.raspberrypi.org/raspbian/images/raspbian-2018-03-14/ )
Run the following commands:

Change Swap Size of the Rasp:

sudo nano /etc/dphys-swapfile
change to CONF_SWAPSIZE=2048
press: ctrl o Enter and ctrl x
enable the swap file with its new size:
sudo dphys-swapfile setup
sudo dphys-swapfile swapon
----------
Install Required Dependencies:

apt-get update
sudo apt-get install git build-essential libtool autotools-dev autoconf pkg-config libssl-dev libcrypto++-dev libevent-dev libminiupnpc-dev libgmp-dev libboost-all-dev devscripts libdb++-dev libsodium-dev
and
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libcrypto++-dev libminiupnpc-dev qt5-default
----------
Install bitcoin PPA files for the compiling process:

cd /etc/apt/sources.list.d/
sudo nano bitcoin.list
paste to following line:
deb-src http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu artful main
press: ctrl o Enter and ctrl x
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv C70EF1F0305A1ADB9986DBD8D46F45428842CE5E
sudo apt-get update
----------
Install working libssl:

cd && sudo apt-get remove libssl-dev
sudo nano /etc/apt/sources.list
change stretch to jessie
press: ctrl o Enter and ctrl x
sudo apt-get update
sudo apt-get install libssl-dev
sudo apt-mark hold libssl-dev
sudo apt-mark hold libssl1.0.0
sudo nano /etc/apt/sources.list
Change jessie" back to stretch
press: ctrl o Enter and ctrl x
sudo apt-get update
----------

Compile and Install BerkeleyDB 4.8.30 :

wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz
sudo tar -xzvf db-4.8.30.NC.tar.gz
cd db-4.8.30.NC/build_unix
sudo ../dist/configure --enable-cxx
sudo make
sudo make install
export CPATH="/uslocal/BerkeleyDB.4.8/include"
export LIBRARY_PATH="/uslocal/BerkeleyDB.4.8/lib"
----------

The wallet:

(my way) mkdir wallets , cd wallets
git clone https://github.com/RGPickles/BankSocietyCoin
cd BankSocietyCoin
chmod 755 src/leveldb/build_detect_platform
chmod 755 src/secp256k1/autogen.sh
cd src/
make -f makefile.unix
./societyd
* for qt wallet*
cd ..
qmake
make
edit society.conf in .society
(rpcuser=SomeCoolRandomUsername
rpcpassword=SOMETHINawesomeYOUdontHaveToRemember
rpcconnect=127.0.0.1
save.
./society-qt
----------

Have fun!
for a Beer - Donations ;)
SOCI - Si6V7EwnJqzmFiNGHSbXrtWUXKH6F4EFm3
BTC - 1HpGF4wMzztpJ4KT4o2ySFvnLJ4gCoYaV5
LTC - LS22MgY9G4KbaKhkR5dFi995MbcQhuyDXW
ETH - 0x6b5EdC3e58Fd84a40aa942964690adA91C398075
TRX - TKBpktt5QQ9WV57QjonQrGr1vmKLCVQBL6

13.07.2019 DennisHilk




**********
if error (makefile.unix:200: obj/rpcclient.o] appears)
[This first step is necessary because you will get linking errors if you don't remove the old Boost library]
sudo apt remove --purge --auto-remove libboost-dev libboost-thread-dev libboost-system-dev libboost-atomic-dev libboost-regex-dev libboost-chrono-dev
mkdir boost
cd boost
wget https://dl.bintray.com/boostorg/release/1.64.0/source/boost_1_64_0.tar.gz
tar xfz boost_1_64_0.tar.gz (can take rly long, dont worry)
cd boost_1_64_0/
./bootstrap.sh
./b2 stage threading=multi link=static --with-thread --with-system
sudo ./b2 install threading=multi link=static --with-thread --with-system
cd ../../
nano .bash_profile
export LIBS="-L/home/YOURS/boost/boost_1_64_0/stage/lib"
export CPPFLAGS="-I/home/YOURS/boost/boost_1_64_0"
cd society root
make clean
cd src
sudo make -f makefile.unix

(if bignum error)
sudo apt-get install libgmp-dev
or delete opensll and reinstall as above.
submitted by dennishilk to u/dennishilk [link] [comments]

Creating a Headless Staking Node on Ubuntu 18.04

Creating a Headless Staking Node on Ubuntu 18.04
##UPDATE## Step 8 - Option 2, has some bugs in the final build process. i haven't had time to work them out yet!

This guide will take you through building and running a headless x42 Full Node! The OS I am using here is Ubuntu 18.04, this guide picks up from a complete/fresh ubuntu install.
This is meant to setup a staking node and so this guide will run you through building, configuring and setting up staking. It will not cover sending transactions or anything else.
The things we are going to do:
  • Step 1 - Install .net core
  • Step 2 - Download The x42 Node Source & Compile It
  • Step 3 - Setting The x42 Node Up To Run On Boot
  • Step 4 - Setup A New Wallet
  • Step 5 - Configure The x42 Daemon
  • Step 6 - Get Address
  • Step 7 - Check Balance
  • Step 8 - Connect The UI Wallet To A Headless Node
  • Step 8 - [Option 1 - Use Installer] Connect The UI Wallet To A Headless Node
  • Step 8 - [Option 2 - Build/Compile UI Only] Connect The UI Wallet To A Headless Node # BROKEN#

Step 1 - Install .net Core

Here is the reference link:
https://dotnet.microsoft.com/download/linux-package-manageubuntu18-04/sdk-current
Register Microsoft Key’s & Install Their repos:
cd /tmp wget -q https://packages.microsoft.com/config/ubuntu/18.04/packages-microsoft-prod.deb sudo dpkg -i packages-microsoft-prod.deb sudo add-apt-repository universe sudo apt -y install apt-transport-https sudo apt update sudo apt -y install dotnet-sdk-2.2 
Microsoft collect telemetry data by default, if you are part of the “tin foil hat brigade” you can set the following environment variable to turn it off:
echo "DOTNET_CLI_TELEMETRY_OPTOUT=1" >> /etc/environment 
now you should be at a point where .net core is installed on your system… that wasn’t so hard was it! You can check by running the following command:
dotnet--list-sdks 
The output should look like this:
$ dotnet --list-sdks 2.2.103 [/usshare/dotnet/sdk] 

Step 2 - Download & Compile The x42 Node

This part assumes you have GIT installed, if not:
apt -y install git 
Now to pull down the source and compile it!
cd ~/ git clone https://github.com/x42protocol/X42-FullNode.git # “cd” into the source folder cd X42-FullNode/src/ 
Now .net core uses NuGet for package management, before we compile, we need to pull down all of the required packages.. its as simple as running (this will take a couple of minutes) inside of “X42-FullNode/src/”:
dotnet restore 
now we are ready to compile the source, execute (inside of “X42-FullNode/src/”):
dotnet build --configuration Release 
ignore the yellow warnings, this is just the rosyln compiler having a grumble.. if you get red ones then something went wrong! The “--configuration Release” will strip out all debug symbols and slim things down.. only a little, this optional parameter is not mandatory.
Once this is done everything is built/compiled, you can run the daemon directly from the repository, this can be done by going to:
cd ~/X42-FullNode/src/x42.x42D/bin/Release/netcoreapp2.1 dotnet x42.x42D.dll 
this will kick off the node, however if you exit SSH at this time it will kill the process! however I always recommend copying out the binaries to a separate folder. This can be done with the following:
mkdir ~/x42node mv ~/X42-FullNode/src/x42.x42D/bin/Release/netcoreapp2.1/*.* ~/x42node/ 
now we have everything we need to run the node outside the git repository! What we need to do now is run the node and have it create the default x42.conf file.. so
cd ~/x42node dotnet x42.x42D.dll 
feel free to hit “CTRL + C” to exit the application after a couple of seconds, by then the folders/files would have been created at the following path:
~/.x42node/x42/x42Main/ 

Step 3 - Setting The x42 Node Up To Run on Boot

Now we are going to create a service file so our x42 node automatically starts when the system is rebooted.
THINGS TO NOTE ABOUT BELOW.. CHANGE THE ##USER## to the username your currently using as these files are within your home directory!
We need to drop to root for this..
sudo -i cat < /etc/systemd/system/x42node.service [Unit] Description=x42 Node [Service] WorkingDirectory=/home/##USER##/x42node ExecStart=/usbin/dotnet /home/##USER##/x42node/x42.x42D.dll Restart=always # Restart service after 10 seconds if the dotnet service crashes: RestartSec=10 SyslogIdentifier=x42node User=##USER## Environment=ASPNETCORE_ENVIRONMENT=Development [Install] WantedBy=multi-user.target EOF 
To enable the service, run the following (as the root user):
systemctl enable x42node.service 
BOOM.. the node isn’t running yet.. but next time the system restarts it will automatically run!
now lets exit out of root!
exit 
We can now start the node up and begin downloading blocks, by running the following command:
sudo systemctl start x42node.service 
if you want to check its loaded and see some of the output, you can run:
sudo systemctl status x42node.service 
an example of the output:
$ sudo systemctl status x42node.service ● x42node.service - x42 Node Loaded: loaded (/etc/systemd/system/x42node.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-01-24 15:47:55 UTC; 14s ago Main PID: 5456 (dotnet) Tasks: 23 (limit: 1112) CGroup: /system.slice/x42node.service └─5456 /usbin/dotnet /home/darthnoodle/x42node/x42.x42D.dll Jan 24 15:48:09 x42staking x42node[5456]: Batch Size: 0 Mb (0 headers) Jan 24 15:48:09 x42staking x42node[5456]: Cache Size: 0/50 MB Jan 24 15:48:09 x42staking x42node[5456]: Jan 24 15:48:09 x42staking x42node[5456]: =======Mempool======= Jan 24 15:48:09 x42staking x42node[5456]: MempoolSize: 0 DynamicSize: 0 kb OrphanSize: 0 Jan 24 15:48:09 x42staking x42node[5456]: Jan 24 15:48:09 x42staking x42node[5456]: info: Stratis.Bitcoin.Connection.ConnectionManagerBehavior[0] Jan 24 15:48:09 x42staking x42node[5456]: Peer '[::ffff:86.184.76.255]:52342' connected (outbound), agent 'x42:1.2.13 (70012)', height 213920 Jan 24 15:48:09 x42staking x42node[5456]: info: Stratis.Bitcoin.Connection.ConnectionManagerBehavior[0] Jan 24 15:48:09 x42staking x42node[5456]: Peer '[::ffff:86.184.76.255]:52342' offline, reason: 'Receiving cancelled.'. All node screen output can be found in the /valog/syslog file. 

Step 4 - Setup a New Wallet

With the Node running, we now need to setup and/or restore a wallet!
Everything will be performed through the API’s, however by default these API’s are listening on localhost (127.0.0.1), if you are connecting in remotely then this would be a problem since you cant hit that IP. The solution, SSH TUNNEL!
Execute the following command on your local system:
ssh -L 42220:localhost:42220 @ 
This binds the local port (on your system) with 127.0.0.1:42220 on the remote system, once you have executed the command you can type the following address in your laptop/desktop’s web browser and be able to access the API’s:
http://127.0.0.1:42220/swaggeindex.html 
It should look something like this:
https://preview.redd.it/9lzeg3vob8d21.jpg?width=482&format=pjpg&auto=webp&s=b5d574998816056140d5d6de7b03c56772a892fe
To Create a new wallet, first we have to generate some mnemonic works (e.g. the seed), you can do that by going to the following API:
/api/Wallet/mnemonic 
Hit the “Try it out” button which then prompts you for 2 fields:
https://preview.redd.it/dvbdllfrb8d21.jpg?width=722&format=pjpg&auto=webp&s=766d14bafba6facbcd56d31c63c0012748e682e5
Enter “English” and I would recommend 24 words as this greatly increases the seed strength! Once that is done you hit execute and then scroll down to see the “Response Body”, this should contain the mnemonic which you are going to use to create the wallet! This looks something like below:
https://preview.redd.it/6p4q0rsub8d21.jpg?width=603&format=pjpg&auto=webp&s=44b9265626467a43ca670b134c4d28187f475c2e
THIS IS VERY IMPORTANT, BACKUP THIS MNEMONIC TO A SAFE SECURE LOCATION THAT IS ENCRYPTED!!!
So now we have our mnemonic, its time to generate the wallet, for this we need to use the API:
/api/Wallet/create
There are a number of parameters which are required in order to create a wallet:
WalletCreationRequest{ mnemonic string password* string passphrase* string name* string } 
It should be noted that the password and mnemonic are is the most important parts of this request where the “password” will encrypt the wallet and Is required to unlock it.
  • Hit the “Try it out” button
  • input the necessary data
  • Insert the mnemonic
  • Put a password & passphrase
  • “Name” is what your wallet will be called
It should look something like the following:
https://preview.redd.it/958ttfbxb8d21.jpg?width=603&format=pjpg&auto=webp&s=ce48336436ea4b469b5e87513da802de0bf444ee
Hit “Execute”, the “Loading” sign may spin for a few minutes while the wallet is created… once the wallet has been created the “Response Body” will return the mnemonic you have just used.. we now have a wallet!!
HOWEVER IT IS NOT LOADED INTO THE NODE JUST YET!
This is where we will now jump back out and to configure the node to automatically load the wallet and automatically start staking when it first loads.
AGAIN BACKUP YOUR MNEMONIC AND PASSWORD, MAKE SURE THEY ARE ENCRYPTED AND STORED SOMEWHERE SAFE!

Step 5 - Configure The x42 Daemon

Now we are going to modify the x42.conf file in order to automatically load our wallet and start staking 😊
First things first, lets stop our node by running the following command:
sudo systemctl stop x42node.service 
CD to the following folder and view its contents:
~/.x42node/x42/x42Main ls -lah 
within that folder there should be 2 files you are interested in:
-rw-r--r-- 1 darthnoodle darthnoodle 18K Jan 28 16:01 TestWallet.wallet.json -rw-rw-r-- 1 darthnoodle darthnoodle 3.1K Jan 24 15:25 x42.conf 
So TestWallet.wallet.json is our physical wallet that will be loaded, but for right now we want to modify the x42.conf file.. fire up your favourite text editor (if you use VI you’re a masochist)..
nano x42.conf 
The area we are interested in is the following:
####Miner Settings#### #Enable POW mining. #mine=0 #Enable POS. #stake=0 #The address to use for mining (empty string to select an address from the wallet). #mineaddress= #The wallet name to use when staking. #walletname= #Password to unlock the wallet. #walletpassword= #Maximum block size (in bytes) for the miner to generate. #blockmaxsize=1000000 #Maximum block weight (in weight units) for the miner to generate. #blockmaxweight=1000000 #Enable splitting coins when staking. #enablecoinstakesplitting=1 #Minimum size of the coins considered for staking, in satoshis. #minimumstakingcoinvalue=10000000 #Targeted minimum value of staking coins after splitting, in satoshis. #minimumsplitcoinvalue=10000000000 
Uncomment (remove the #) of the following lines and change their value:
stake=1 (changed to 1) walletname=TestWallet (changed to our Wallet Name) walletpassword=password123 (changed to the wallet password) 
save the file and exit back to the command prompt, now we shall restart the node with the following command:
sudo systemctl status x42node.service 
now the wallet is automatically loaded and ready for action!
YES I KNOW YOU HAVE PUT YOUR PASSWORD IN CLEARTEXT, THIS IS WHERE YOU SHOULD HARDEN YOUR BOX. IF THEY CAN GET TO THE POINT WHERE THEY CAN READ YOUR CONF FILE THEY CAN JUST GRAB YOUR WALLET AND BRUTEFORCE THE PASSWORD.
You can check its loaded by going back to the API and executing the following command:
/Dashboard 
Or execute the following command on the NODE:
curl -X GET "http://127.0.0.1:42220/Dashboard" -H "accept: application/json" 
both will produce the same output, if you scroll to the bottom you should see something like this:
======Wallets====== TestWallet/account 0, Confirmed balance: 0.00000000 Unconfirmed balance: 0.00000000 
This means the wallet is loaded and ready for action!!

Step 6 - Get Addresses

Next thing you are probably going to want is a receive address and to check the balance and TX history.. so lets start with getting an address!
Go to the following API:
/api/Wallet/unusedaddress 
Fill in the Wallet name which is “TestWallet” (in this example) and “account 0” (which is the first/default account):
https://preview.redd.it/ayri5jk0c8d21.jpg?width=602&format=pjpg&auto=webp&s=2d16bbb78da49c0125d24d0834c9454d702cb7a1
Hit execute and you should have an x42 address within the “Response Body”:

https://preview.redd.it/tmc495j3c8d21.jpg?width=349&format=pjpg&auto=webp&s=b00177f66a9e24c980d3c6d4e532a33cbf3fb0bc
BOOM… ok now we can receive funds! 😊

Step 7 - Check TX History

Go to the API and the following call:
/api/Wallet/history 
The 2 fields we are most concerned about are:
https://preview.redd.it/lw194af6c8d21.jpg?width=602&format=pjpg&auto=webp&s=27e264bc008879355ff5b9c50a0a5cb06f16e960
Input the name of the wallet and account you want to view the history of, then hit execute. The other fields can be black. This will return a list of TX’s that the wallet has received:
This should look like the following:
https://preview.redd.it/x1hgargac8d21.jpg?width=585&format=pjpg&auto=webp&s=4fd25f22772f4bcec523a6e82b321ae8146a2c75
There is an easier way of doing this, that doesn’t require you to be connected to your node.. especially if your only interested in viewing your staking rewards… THE EXPLORER!
Access the following URL:
https://explorer.x42.tech/address/ 
this will allow you to easily see all TX’s associated with this address, it should look something like below:
https://preview.redd.it/e480grscc8d21.jpg?width=601&format=pjpg&auto=webp&s=0f8a9ebc7944dfcc73f7df659bd839bb983ba90c
… and your done! By this point your node should be running, staking and you have an easy way to view transactions/rewards 😊


Step 8 - Connect The UI Wallet To A Headless Node

The UI utilises a combination of technologies, however the important part is the code attempts to access the x42 Node API on 127.0.0.1:42220.
So you have 2 options here:
  1. Download the Wallet Installers
  2. Compile The UI Yourselves
Pick the option that best suits you given the pros/cons below:
Option 1 - Pro's/Cons
Pro's
  • If you use the installer, its quick and easy.
Cons
  • This also installs an x42 node on your system which runs when the UI loads.
  • If you dont setup an SSH tunnel before running the wallet the local node will bind to the port and the tunnel wont work.. you will be connecting to the local wallet!!
Option 2 - Pro's/Cons
Pro's
  • You only run the UI, the x42 node is not installed
  • you dont have a superfluous node running, downloading blocks on your local system
Cons
  • Time Consuming
  • Have to download dependencies and manually compile the code

Pre-Requirement - Needed For Both Options!!
As previously mentioned, the UI attempts to access the API's on 127.0.0.1:42220, however our node isnt running on our local system. IN ORDER TO GET IT WORKING YOU NEED TO HAVE AN SSH TUNNEL, THIS TUNNEL NEEDS TO REMAIN ACTIVE WHENEVER YOU WANT TO ACCESS THE WALLET.
this can be done by executing the following command:
ssh -L 42220:localhost:42220 @ 


Step 8 - [Option 1 - Use Installer] Connect The UI Wallet To A Headless Node

Download and install the UI/Wallet & Node from:
https://github.com/x42protocol/X42-FullNode-UI/releases

DO NOT RUN THE WALLET YET!
Those of us who dont want to run a local node and just want the UI, execute the following commands (as an administrator):
cd C:\Program Files\x42 Core\resources\daemon\ ren x42.x42D.exe x42.x42D.exe.bak 
The above is with Windows, if your are in *NIX then locate the daemon and rename it (i will update how to do that/where to find it shortly)
Setup the SSH tunnel as outlined above, Execute the wallet and it will load, however you will see an exception:

https://preview.redd.it/9os5h8q7scd21.jpg?width=550&format=pjpg&auto=webp&s=ac45ed7bc987917142075c61fb486e7d71f820d1
dont worry, this is just the wallet trying to execute/start the x42 node which we dont want, if all works according to plan.. after you click "OK" you should now be presented with the wallet UI and have the option to select what wallet you would like to load:

https://preview.redd.it/hnyt0b4mscd21.jpg?width=958&format=pjpg&auto=webp&s=a47df710a804375d8363ffcd77d1ede2862b9b4d
... DONE!

Step 8 - [Option 2 - Build/Compile UI Only] Connect The UI Wallet To A Headless Node ###BROKEN

THIS IS STILL A WORK IN PROGRESS, THE ELECTRON BUILD DOESNT WANT TO COMPILE BECAUSE SOME CODE IS MANGLED SOMEWHERE!!

Ok, this is the fun bit! .. we need to install the following dependencies. these instructions are written for a Windows system but it should be easy enough to perform the same on a *NIX system.
Install Dependencies
In order to build the wallet UI, you need to install the following components:
  • git
  • NodeJS
  • Electron Builder
First thing you need to do is install git, so download and install the package:
https://gitforwindows.org/
Next you need to install NodeJS, download and install the package:
https://nodejs.org/en/download/
Next we need to install the node package manager:
npm install npx –verbose 
next we need to make sure we have Visual Studio build tools and Python (2.7) installed, this can be done by executing the following (AS AN ADMINISTRATOR!):
npm install -g --production windows-build-tools 
this will install the necessary tools to build C#/C++ code and python 2.7, this could take some time! When its done you should have something like the following;

https://preview.redd.it/5ekfy5g1kcd21.jpg?width=490&format=pjpg&auto=webp&s=f65196dee6f78f2ececec5ee8b5df1044d68f635

Build & Install - Windows
Create a temp folder to navigate to a folder where you want to download the GIT repository, execute the following command:
git clone https://github.com/x42protocol/X42-FullNode-UI.git 
This will clone the repository into the folder, it will only clone the wallet and not the Node source! now lets CD into the folder and build the UI:
cd X42-FullNode-UI\FullNode.UI npm install 
This will download and install all dependencies (can take a while), at the end you should see something like..

https://preview.redd.it/0zfbfxa8kcd21.jpg?width=601&format=pjpg&auto=webp&s=438d072a6ab2bc7a3d84a8dfe773968acc762bc7
Now the stock UI has a number of third-party libraries which contain some vulnerabilities, being a security conscious person, ive also run:
npm audit fix 
when this is done, we have fixed most of the package vulnerabilities 😊 We also get a complaint about the typescript library being too new for the version of angular in use, so run the following command to install the additional dependency:
npm install [email protected]">=2.4.2 <2.7.0" 
now its time to build the UI, execute the following:
npm run build:prod 
once complete you should see something like the following..

https://preview.redd.it/56vf9zfckcd21.jpg?width=601&format=pjpg&auto=webp&s=31b72daff9ab5001843cba529a7bd38c76fd099d
Next its time to compile the electron binary, it should be noted that the build/package process utilises AppVoyer which is not installed and if you attempt to build right now you will get the following error:
cannot expand pattern "${productName}-v${version}-setup-${os}-${env.arch}.${ext}": env arch is not defined. 
To fix this we need to modify the build file, this is a quick one liner that can do it:
powershell -Command "(gc electron-builder.json) -replace 'env.arch', 'arch' | Out-File electron-builder.json" 
Essentially the offending line for Windows is..
"artifactName": "${productName}-v${version}-setup-${os}-${env.arch}.${ext}" 
The build cannot resolve “env.arch”, so the above one liner replaces “env.arch” with “arch” which works 😊
execute the following command:
npx electron-builder build --windows --x64 
At present i get the following error, no matter what i do.. and ive ran out of time to go hunting about.. if anyone has any ideas on how to fix then please post in here or message me on discord:

https://preview.redd.it/t66rtuqdtcd21.jpg?width=918&format=pjpg&auto=webp&s=a3f1a5ff682586348909c67645ca7ae9454922ff


Happy staking!

If you found this post helpful, then buy me a beer and send a donation to XQXeqrNFad2Uu7k3E9Dx5t4524fBsnEeSw
submitted by D4rthNoodle to x42 [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]

Bitcoin Core & Lightning Network (very easy installation!) No root access!

Hi!
I finished the fine tools as i think
I created Makefile utilities for bitcoind & lnd compilation under $HOME directory (no root access!)
This makefile does everything for full bitcoin node and lightning network node. This kit was created for CentOS 6.* but it works in Ubuntu / Linux Mint OSes too and may be will work in 90% Unix systems.
Details:
It compiles from sources under $HOME directory: compilers (gcc 7.1, go, node.js, python2 & python3) and tools (autoconf & autotools and etc), all libraries (boost, openssl and more), bitcoind daemon, lnd daemon , lncli-web client (and node.js for this) and does all configuration for you! You need only create a wallet in lnd. It works fine with UPnP routers (from sources too!) and can define network configuration (real public IP & network interfaces)
So if you want to have bitcoind & lnd node you need only to do:
make i-want-lightning
make set-up-lightning-mainnet
And after you can run:
mainnet-lightning-start
And after you will have bitcoind full node & lnd node with web interface (lncli-web)
You can setup in one host mainnet & testnet daemons without any conflicts.
Enjoy!
URL: https://github.com/Perlovebitcoin-kit-makefile
Perlover
submitted by Perlover to Bitcoin [link] [comments]

Introducing Litecoin as base currency - Huge Bisq/Bitsquare update - Check out v0.5.1

This release comes with tons of changes and improvements.
Please download at: https://github.com/bitsquare/bitsquare/releases/tag/v0.5.1
Most relevant changes are:
Please see the full release notes below.
As that release has very profound changes it is NOT backward compatible to the earlier versions. It uses a new network which is separated from the current trade network. So your offers from the current application will not be visible for users who are using the new version.
If you want to migrate to the new version you need to close your offers and withdraw your funds to the new application. You can run both applications in parallel as they are using a different data directory. You cannot move over the wallet or application data because the wallet format has changed (BIP44) and we use a different data structure for the data base files. So you need to transfer the Bitcoin with a BTC transaction and set up your payment account(s) manually.
Please double check with cmd+e in the old application if no funds are left over (some bugs might have caused that the balance displayed in the UI is not correct).
Please use small amounts when starting trading in the new application as with so many changes there are some risks for bugs (though it is thoroughly tested).
Release notes:
submitted by heavyuser1337 to litecoin [link] [comments]

Huge Bisq/Bitsquare update - Check out v0.5.1

This release comes with tons of changes and improvements.
Please download at: https://github.com/bitsquare/bitsquare/releases/tag/v0.5.1
Most relevant changes are:
Please see the full release notes below.
As that release has very profound changes it is NOT backward compatible to the earlier versions. It uses a new network which is separated from the current trade network. So your offers from the current application will not be visible for users who are using the new version.
If you want to migrate to the new version you need to close your offers and withdraw your funds to the new application. You can run both applications in parallel as they are using a different data directory. You cannot move over the wallet or application data because the wallet format has changed (BIP44) and we use a different data structure for the data base files. So you need to transfer the Bitcoin with a BTC transaction and set up your payment account(s) manually.
Please double check with cmd+e in the old application if no funds are left over (some bugs might have caused that the balance displayed in the UI is not correct).
Please use small amounts when starting trading in the new application as with so many changes there are some risks for bugs (though it is thoroughly tested).
Release notes:
submitted by heavyuser1337 to BitcoinMarkets [link] [comments]

Running an ABC node on Hetzner. €35/mo, initial block download in less than 4 hours

Inspired by Running an ABC full node for one month on Google Cloud, I set up an ABC node on Hetzner. I had not previously used Hetzner's services and decided this rainy Sunday afternoon would be good time for trying them out.
The server I picked: Intel i7-3770 (4 cores @ 3.40GHz, with hyperthreading), 16GB RAM, 2x2TB HDD, 1Gbit unlimited traffic. Costs ~€35/mo. My criteria was: a decent CPU and 16GB of RAM. Based on my past experience, I don't think having 32GB or more RAM would make much difference for a Bitcoin node. For storage, I also considered going with a SSD instead of the "spinning rust". When I looked, SSD offers were around €42/mo for 240GB of storage. Ultimately I went with the cheaper HDDs, assuming the "hot" data will be cached in RAM anyway.
Hetzner verified my fresh account and sent me login details in about 10 minutes (remember, it's Sunday). Setting up Ubuntu 17.04 on the server was reasonably straightforward: type "installimage" and follow instructions. The installimage script gave more flexibility with partition setup, filesystem types etc. than e.g. DigitalOcean does. A few minutes later I was logged in the freshly baked 17.04 system as a root user.
Create an unprivileged system user, download and extract the Bitcoin ABC client, run it with "-dbcache 12000". Initial block download completed in 3 hours 35 minutes. Now, I don't actually have an use for a node, but will keep this running for at least a month just to see how it do. So far I'm happy with Hetzner: works as advertised and no fuss.
The thing with Google Cloud Platform (which I am also a happy customer of): their network is really fancy: custom hardware, private fiber optic links, and an army of engineers managing all of that. Combine with Google's Global Load Balancer (obviously only available in Google Cloud) and the value proposition for running production web apps is pretty solid. Plus their VMs are server-class hardware, their storage has redundancy etc. But it's an overkill for running an enthusiast bitcoin node which really just needs a big disk, some RAM and a cheap, fast-enough network connection.
PS I've written before about setting up a node on a €50 secondhand laptop. That node is up doing great.
submitted by medieval_llama to btc [link] [comments]

Introducing DOGE as base currency - Huge Bisq/Bitsquare update - Check out v0.5.1

This release comes with tons of changes and improvements.
Please download at: https://github.com/bitsquare/bitsquare/releases/tag/v0.5.1
Most relevant changes are:
Please see the full release notes below.
As that release has very profound changes it is NOT backward compatible to the earlier versions. It uses a new network which is separated from the current trade network. So your offers from the current application will not be visible for users who are using the new version.
If you want to migrate to the new version you need to close your offers and withdraw your funds to the new application. You can run both applications in parallel as they are using a different data directory. You cannot move over the wallet or application data because the wallet format has changed (BIP44) and we use a different data structure for the data base files. So you need to transfer the Bitcoin with a BTC transaction and set up your payment account(s) manually.
Please double check with cmd+e in the old application if no funds are left over (some bugs might have caused that the balance displayed in the UI is not correct).
Please use small amounts when starting trading in the new application as with so many changes there are some risks for bugs (though it is thoroughly tested).
Release notes:
submitted by heavyuser1337 to dogecoin [link] [comments]

My setup vs Hardware Wallets: be the judge.

I am not a big fan of having to keep the master seed of hardware wallets stored. Even if you keep it somewhere safe, someone can still get to it and have access to your funds. So this is my setup:
*1) Live-usb ubuntu, network disconnected. *2) Generate addresses using bitcoin paper wallet downloaded offline site, printing PDFs. *3) Save these PDF on an encripted container using veracrypt, with a very strong password. This encripted file you can store safely online on google drive or something. *4) Split your BTC across some addresses, thinking of how you'll use them. Keep the public addresses handy. *5) When you want to use it, just boot ubuntu again, open the PDF, and use a mobile phone wallet like Mycelium to import the private key using QR Code. *6) Spend the amount needed and send the remaining amount to a new paper wallet and don't use the old one anymore.
This is my setup, what do you think? It's not absolutely 100% if you think of all the possibilities, but I think it's safe enough for even higher values. Main security concern is your phone, that should not be rooted, and should not have automatic backups (reported problems with Titanium backup, MIUI backup), because backups may store files unsecurely on your phone or on the cloud. Also, try to keep apps to a minimum because you never know if that "bitcoin price trackr app or whatever" may be looking to steal from you.
What do you think? Posted this trying to help concerned users. Of course hardware wallets are good, but sometimes you don't have the monies to buy one, just to buy BTC.
Edit: never type the veracrypt password anywhere but the ubuntu live cd and dont store it online.
submitted by cryptosnake to Bitcoin [link] [comments]

Huge Bisq/Bitsquare update - Check out v0.5.1

This release comes with tons of changes and improvements.
Please download at: https://github.com/bitsquare/bitsquare/releases/tag/v0.5.1
Most relevant changes are:
Please see the full release notes below.
As that release has very profound changes it is NOT backward compatible to the earlier versions. It uses a new network which is separated from the current trade network. So your offers from the current application will not be visible for users who are using the new version.
If you want to migrate to the new version you need to close your offers and withdraw your funds to the new application. You can run both applications in parallel as they are using a different data directory. You cannot move over the wallet or application data because the wallet format has changed (BIP44) and we use a different data structure for the data base files. So you need to transfer the Bitcoin with a BTC transaction and set up your payment account(s) manually.
Please double check with cmd+e in the old application if no funds are left over (some bugs might have caused that the balance displayed in the UI is not correct).
Please use small amounts when starting trading in the new application as with so many changes there are some risks for bugs (though it is thoroughly tested).
Release notes:
submitted by heavyuser1337 to btc [link] [comments]

[Guide] Setting up Trezor + Electrum 2.02beta + armory on a Raspberry Pi 2. Cold offline signing for $40

Having just received my Pi 2, I am happy to report that a fresh Raspbian install, on an 8 GB Class 10 MicroSD card : Electrum / Armory / Trezor / BTChip all work with my Single Board Computer setup script (it also works for Pi B, Pi B+ Raspbian and BeagleBone Black Debian & ubuntu, also tested on Odroid C1 Ubuntu 14.4)
The full "!" installation takes about 40 mins on Pi 2, which is at least twice as fast as on the Pi B+ / BBB
Notes
submitted by Aussiehash to Bitcoin [link] [comments]

DECENT MINING SETUP & RESSOURCES SHORTCUT

To all DECENTants,
I would like to encourage you to become a seeder or witness (actually not miner) on DECENT.

SHORT INTRODUCTION ABOUT ME

As a pioneer with Bitcoin I truly believed in the DCT project and it's proposal. The first day of the ICO release I sent all my BTC balance to the DECENT. Not knowing when and what they will deliver. To participate in this great adventure means a lot to me. Another project from my home country I strongly encourage you to get familiar with is Ethereum. I have been an early CPU miner: before Crypto Currency I used to compute for sience projects grid for Clean Water and Cancer Research. If I hadn't bought Rainforest with the Ripple they distributed to all contributors, I'd be a rich man today. :P

DECENT SUPPORT

https://decent.ladesk.com/

DECENT WIKI

https://wiki.decent.ch/doku.php?id=decent:howto#build_decent_from_source

DECENT GITHUB

https://github.com/DECENTfoundation/DECENT-Network

BLOCK EXPLORER

https://explorer.decent.ch/

DECENT DB

https://decent-db.com/

GRAPHENE CLI Wallet Cookbook

https://github.com/bitshares/bitshares-core/wiki/CLI-Wallet-Cookbook

RESSOURCES

https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-16-04
http://www.hamvocke.com/blog/a-quick-and-easy-guide-to-tmux/
https://digitizor.com/create-swap-file-ubuntu-linux/

I - SERVER SETUP

A dedicated server with Linux Ubuntu 16.04 LTS is most recommend for 24/7 operation. I suggest you close the root and create a new user with SSH Key, secure the system with a firewall.

1. Create a new user

adduser bob 

2. Elevate him

usermod -aG sudo bob 

3. Generate a new keyset

ssh-keygen 

4- Bind the new keys

ssh-copy-id [email protected]_server_ip 
Copy the keys to your local drive. You'll need them to connect.

5. Change the config file

sudo nano /etc/ssh/sshd_config 
Change Line PasswordAuthentication no

6. Finish with

sudo systemctl reload sshd 

7. Login with your ssh key, user and password

ssh [email protected]_server_ip 

II - PREREQUISITES

1. Grab your tools

sudo apt-get update sudo apt-get install build-essential autotools-dev automake autoconf libtool make cmake checkinstall realpath gcc g++ flex bison doxygen gettext git qt5-default libqt5svg5-dev libreadline-dev libcrypto++-dev libgmp-dev libdb-dev libdb++-dev libssl-dev libncurses5-dev libboost-all-dev libcurl4-openssl-dev python-dev libicu-dev libbz2-dev 

2. Download and build Boost 1.60.0

mkdir -p ~/dev/DECENTfoundation/DECENT-Network-third-party cd ~/dev/DECENTfoundation/DECENT-Network-third-party rm -rf boost_1_60_0* boost-1.60.0* wget https://sourceforge.net/projects/boost/files/boost/1.60.0/boost_1_60_0.tar.gz tar xvf boost_1_60_0.tar.gz mkdir boost-1.60.0_prefix cd boost_1_60_0 export BOOST_ROOT=$(realpath ../boost-1.60.0_prefix) ./bootstrap.sh --prefix=$BOOST_ROOT ./b2 install cd .. rm -rf boost_1_60_0 boost_1_60_0.tar.gz 

III - INSTALLATION

1. Clone the repo

mkdir -p ~/dev/DECENTfoundation cd ~/dev/DECENTfoundation #via ssh $ git clone [email protected]:DECENTfoundation/DECENT-Network.git #via url $ git clone https://github.com/DECENTfoundation/DECENT-Network.git cd DECENT-Network git submodule update --init --recursive 

2. Build and install Decent

mkdir -p ~/dev/DECENTfoundation/DECENT-Network-build cd ~/dev/DECENTfoundation/DECENT-Network-build cmake -G "Unix Makefiles" -D CMAKE_BUILD_TYPE=Debug ~/dev/DECENTfoundation/DECENT-Network cmake --build . --target all -- -j -l 3.0 cmake --build . --target install 

IV - USE DECENT

You don't want your server to shut down the process when you lose connection or quit.
I use tmux. Though nohup is sufficient for infrequent access. Use it when you fire up decentd after miner setup.
nohup ./decentd & disown 

1. RUN decentd - On first run decentd will create .decent in the home directory.

~/dev/DECENTfoundation/DECENT-Network-build/artifacts/prefix/bin/decentd 
Always close it via Ctrl+C to save the current state Ctrl+S Freeze Ctrl+Q Resume

2. Get HELP

cd ~/dev/DECENTfoundation/DECENT-Network-build/artifacts/prefix/bin/ ./decentd -h 

3. RUN cli_wallet

~/dev/DECENTfoundation/DECENT-Network-build/artifacts/prefix/bin/cli_wallet 
Close it with Ctrl+D

4. USE cli_wallet

set_password xy unlock xy 

5. IMPORT your account

import_key decentgo_username your_private_key 

6. CREATE 3 sets of keys for your new account

suggest_brain_key 
write them down, don't use the ones below. ;)

1. new owner key

{ "brain_priv_key1": "UNBUSH ROAR CHKALIK STRUE PLATTEN DEMOB COLETIT DECAYER SPERONE SPASMED ANATASE LAGGARD BESPETE AXOID SERAL CHEKI", "wif_priv_key1": "5J4brX9bydADigEtsXZhCZ1YLVXkq8frp4xcKAREQ3Gh3P2DE7e", "pub_key1": "DCT5VNJni7HypYi159qiwazZ1WZUt4p2v7NLQmFCJPDvjBpW2oG8a" } 

2. new active key

{ "brain_priv_key2": "FUSION BLART JAIL FESTAL LAXNESS ROSTEL TITI VANADYL PUG BATATA KAIK ROSETY STUCCO TETE BEMUDDY WUDGE", "wif_priv_key2": "5HvsjRsokHSeeUdRkM88JgLzYJ6vnc2e35CzyZNRnmh1fvm91Jz", "pub_key2": "DCT7G7KeUnMPVKXN2y8M7BnyosLRE3LtSnNp7kbxtYd9xHiBoX6wd" } 

3. new public signing key

{ "brain_priv_key3": "DECESS LABBA PLAN DEHUSK FISTY MOSSER SPURTER SCORIAE INDART UNDYE MASTER STEIGH SAFROLE FLURR THAPSIA JOB", "wif_priv_key3": "5JgMsecySgt2BQsmmEE9QnwAGuudC9fGeZJhreyPatcu2TVY9bs", "pub_key3": "DCT6D7TLeVJmPQWR73XHvEhTVHzTDoG6oTSUyvfGa58nuc5wL96UH" } 

7. CREATE your new account

register_account new_username pub_key1 pub_key2 decentgo_username true 

8. SEND some DCT to your new account

transfer decentgo_username target_username 3.00 DCT "memo" true 

9. IMPORT the new account

import_key new_username wif_priv_key2 

10. Close the Wallet and edit the config.ini inside /root/.decent/data/decentd/

private-key = ["pub_key2","wif_priv_key2"] 

11. Launch again and create your miner

create_miner username "proposal URL" true 

12. Change your signing key to 3rd keypair from suggest_brain_key

update_miner username "proposal URL" public_key3 true 

13. Edit the config.ini again inside /root/.decent/data/decentd/

enable-stale-production = true miner-id = "1.4.X" private-key = ["pub_key3","wif_priv_key3"] 

Your Server is now ready to run a DECENT witness.

Be aware that you should not close your daemon at any time.

V - USEFUL COMMANDS

get_brain_key_info dump_private_keys get_private_key public-key get_account texxi get_miner texxi list_my_accounts list_account_balances texxi set_desired_miner_count username 99 

Now get some support for your miner and join the community!

https://decent-project.slack.com/

You can vote for me and I will gladly return the favor. Please make sure your server runs stable and you're not missing any blocks. Good Luck!

vote_for_miner username texxi true true

All voters will receive early preview access to my first cryptocurrency trading tool to be released in 2018. But remember: Always trade for good and invest in green.

submitted by Texxer to Decentplatform [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]

Substratum leads Round 2 of Monthly Community Voting Round - AMA Transcript Inside!

Hey guys, If you haven’t noticed on Binance’s monthly community voting round – it has been a tight battle but Substratum has been taking the lead.
I wanted to explain why Substratum has seemingly come out of no-where but has garnered some attention. Substratum is creating a solution to a very big obstacle in the world web. The below has been taken from Justin Tabb aka the Founder of Substratum and summarises what the purpose of the network is.
I hope you guys can support their vision by voting for Substratum (SUB) on the https://www.binance.com/vote.html.
The Substratum Network will bring the decentralized web worldwide without the need of special software for the average internet user. We will be able to serve Substratum Requests directly to the default browser (Safari, Firefox, Chrome, Internet Explorer) without any special software installed on the average consuming users computer.
How Substratum Works
Ease of Use: currently nearly everything that has to do with crypto or the blockchain is very difficult to use and requires technical knowledge. Through our 10+ years of experience working with companies like Apple we understand the importance of a good user experience.
• The average internet user requires NO special software to use the Substratum Network. The default browser will service all requests for average users so they do not need to do ANYTHING different. Users who wish to service requests and receive SUB coins in return will have a point and click user interface that any user can setup. No technical knowledge required. SubstratumPay will be seamlessly integrated and geared towards high conversions of low technical expertise users. • Serving Up of Decentralized Content: Substratum provides a method for serving Decentralized Content (including Web Sites, Data, and Applications) through a Mac, Windows, and Linux application/service that is easy to install and run (requires no technical expertise) and serves up decentralized content using the toolkit that we have developed. This is a point and click process and requires zero technical knowledge. All the user has to do is install the application, click through a few settings and they are up and running and making Substratum Coin. Incentivizing Users to Serve the Content: in order to incentivize users to run the Substratum Network client on their machine we will be providing Substratum Coin to them for doing so. The coin is issued to the serving machine through a micro-transaction from the hosting site to the serving computer. By breaking fees down to a micro-transaction level this will greatly reduce the overall cost to companies and entities that want to host sites and applications on the internet solving yet another problem with the web as it stands today.
Privacy / Security / Encryption: by allowing millions of Substratum Network users to serve content the biggest concern becomes privacy and security. Substratum solves these issues through advanced cryptography algorithms rooted in Artificial Intelligence that ensures all data remains secure. Following the lead of BitCoin this is the strength of cryptocurrency and the crypto movement. Storage and Serving of Content: in order to serve millions of sites, databases, and applications the Substratum Network employs custom developed advanced compression algorithms and machine learning to geolocate the right Substratum Network machine to serve up the content to the appropriate user based on geolocation, this will ensure the fastest load time with the lowest amount of latency and strain on the Substratum Network and both the serving and receiving machine. DNS (Domain Name System): DNS or the Domain Name System is the system that currently tells your browser where to go when you type in a domain name. For instance when you go to Chrome and type in apple.com a DNS lookup is performed to check where to send that request, the DNS system comes back with an IP address and your request is routed there. In the first version of SubstratumDNS will be a complex, AI enabled DNS server that will receive DNS requests along with the geolocation of the requestor and find based off of that information the closest available SubstratumNode that is able to fulfill the request. Development Tools for the Decentralized Web: the Substratum Network will provide an API and SDK for developing tools on the Substratum Platform. This will bring in strong developer support and will accelerate the growth of the decentralized web on the Substratum Network. Net Neutrality: with the Substratum Network ALL web-sites and applications will have EQUAL ability to be broadcast in an equal and fair manner.
International Digital Barriers: currently countries like China have strict regulations on what their 1.379 billion citizens are able to interact with on the internet. Substratum will break down these barriers through a network of decentralized computers running the Substratum Network Software. Where other solutions that are currently used by residents in these countries require special software to be installed, like TOR, Substratum will take a reverse approach and require no special software for the average user.
High Hosting Costs: currently businesses must pay high hosting fees to get their web-sites on the internet. Amazon Web Services launched a 3.5BIL USD per year business by attempting to solve this problem. They allow you to pay for how many minutes you run a web / database server. Substratum completely solves this problem through the power of cryptocurrency by only charging for each request that is processed. You can check out the website here: • Substratum.net o And the whitepaper is available in multiple languages inclusive of Mandarin.
Furthermore, Substratum and the founders are very active in the slack – which they have recently hosted an AMA (ask me anything); I took the liberty of getting this information and if you are interested about the project to read more into it. Obviously they can’t reveal the inner workings of their product due to product sensitivity and being ahead of their competition but they are always up to date with the community through several videos on Youtube (https://www.youtube.com/channel/UCxUJoTH0XLERKl55zGnFI6g) and announcements through their social media. I recommend you follow them.
Q: Any major talks with exchanges yet? A: We just announced that we are launching on our FIRST official exchange of COSS.IO on 9/30 trading against BTC and ETH. More to follow.
Q: Will I be able to run a supernode? A: From the beginning NO. Supernodes will only be for Substratum; however, they will run the SAME software that are used to run a NODE. In time we will develop a requirement list to run a supernode. If you qualify you can then run a SuperNode and receive a premium payout
Q: Is it possible to show a few examples of SUB payouts you get from running a node, and the tell us the ratios that affect the amount/way to calculate it somehow? (SUB owned, for how long you've been running a node etc..) Or is that still in testing? What's the difference in node rewards from someone who has 0 SUB's as opposed to someone who has X amount of SUB's? A: So the calculations for this are in process; however, you can watch our video "How Substrate Per Request Is Calculated" on our YouTube channel for an idea of what variables go into each calculation
Q: How do we prevent DDoS? A: The first step is not talking about how we prevent DDoS or any other hack. We call that security through obscurity. :slightly_smiling_face: Secondly, one of the primary ways to prevent a DDoS attack is decentralization. Well that's perfect. Lastly, there are other techniques, like black-holing and basically shutting a node down. The great news is that we will be decentralized so we are only talking about a node or specific IP Address that will not disrupt the network. :thumbsup:
Q: Say i got a website i want to publish on Substratum, how does this process go? A: Just a shout out if you ask for a lot of detail regarding technology stack and how exactly something will work we are most likely going to give you general answers. This is not to skirt the question. We want to be 10 steps ahead of anyone with nefarious plans before we get launched. You will be seeing more on this very soon. You should be seeing a video drop on this in the next week or two. The goal is to make this easy to use and powerful, plus empower others to use the tools. We're looking at things to different ways one is towards the average user who just want something sitting on their system and doesn't need any more details and the other is a super user who wants a lot of configuration options.
Q: When more people will use Substratum and more will run nodes, the value of SUB will increase. How will it be calculated how much SUB you get as a reward for running a node as value increases? Will it be calculated by Substratum itself or will it be changed manually every so often? A: We will be calculating against the live value of Substratum
Q: Is substratum detectable, for example if it’s used in a country like china and they are caught on these sites that are blocked by government… Can it be detected? A: The goal is to make it constantly moving. We do not want it to be. fast, easy, powerful, anonymous.
Q: Will there be Master Nodes? A: We will have some services that are available that will help provision nodes into the network. We are still story mapping this flow and architecture.
Q: Could we get more information about what you require to do to be a beta tester? A: To be a beta tester you only need to add yourself to the #beta-tester channel here in Slack. You will be notified when we are ready for you to download and install and the process and requirements to continue to run the software
Q: Will you keep us informed on a at least weekly base to tell/ show us the progress made? A: Yes! We will continue to drop at least 2 professionally made update videos each week (with Jason Burns the guy who does them) and we will be doing more and more candid videos
Q: Who is the winner of 10k subs and what idea did he give? And what about 2nd place and 3rd place. A: To be announced shortly. The Substrate is reserved for the payout
Q: Can we mine Sub without the software? A: I will personally be selling pick-axes on my personal website "pixaxesforsale.biz" for a low cost of $19.99
Q: Unless they disclose intelligent life in space, people are still going to be mad at the end of this. A lot more will be happy though A: Haven't found intelligent life in space. Some would question finding it on earth.
Q: From a legal stand point How are we protected if someone is running illegal content on our Node? A: Take a look at our video of "How Substratum Secures Your Site Content". You will never hold the entire piece of data except perhaps in memory if you are the one serving the request so you could never be culpable. Amazon isn't held responsible if I host illegal content now
Q: What about content control? child porno .. and so on ... ? Is there anything to control the content or? A: Excellent question. This was a big concern for us. We do not want Substratum to become the dark web. The goal is to allow the community to self-govern, vote up and down, call out illegal activity. The utilities will allow those with bad intentions to be called out. The more we grow the better we will be about wiping out things like child porn, and just as bad human trafficking.
Q: When will the raised money going to be donated? A: We have already donated $10K out and we have a pending wire for $40K going out Monday. We are working to find the BEST places with the IMMEDIATE needs.
Q: When will the livestream of the burn be? A: Burn #1 will be a livestream of my computer screen later tonight. I will announce on twitter at least an hour ahead of time and we will record it so people can see it later
Q: What will the final circulating supply be after all three token burns? A: We are still getting a FINAL number on this, we are still doing some FINAL Bonus sends but we will have the number VERY VERY soon and we will be posting it. We will be burning 60MIL tokens tonight so that should give you some kind of an idea.
Q: can you stop slack from freezing my firefox? A: Use the downloadable app, or get better internet, or get a new computer. Sounds like a dumpster fire.
Q: Everyone brings up the obvious choice of child porno that needs to be dealt with via content control. What about grayzones such as weed-selling sites? Its illegal in some countries, some not. How will Substratum deal with these grey-zones? A: Give me liberty or give me death.
Q: Could i have an invite to beta test channel on slack? A: Yes, just let a moderator know.
Q: could i get more information on what beta testers are required to do? I will happily be one if it helps the process and I actually manage to do it. A: Join the #beta-testers channel here
Q: when will we see a new homepage? A: This is being worked on now!
Q: is there a minimum amount of SUB needed to run a node? A: NO! 0 Substrate, don't worry, you will have some soon once you turn it on
Q: What about running an "micronode" on any phone (there is a big % using phones all the time), I mean an app installed on phone to run a node and to host only small content like a photos... Did you think about of this? A: https://youtu.be/h6tZ_ZFuFmY
Q: What if my website ethically and morally right and people downvote it out of jealousy will my website be removed if there are more number of downvotes and my content is clean? A: The process is NOT that simple, we will release more details later but this is being taken into consideration. I answered in a bit more detail above as well
Q: Does the Sub team ever sleep ? A: Only when driving
Q: Can I run a node on a VPS? A: I certainly won't be telling people how or where to run the node software. Do the best you can. I actually answered the VPS question above too. We will have a command line version if that is the question. That you can run on something like Ubuntu Server if you want
Q: Can the voting system for all illegal stuff on the internet also be used in a 'bad' way on the regular websites to for example gain commercial/business advantages? A: It should not, no one will have 'master control' All control, so the market decides always.
Q: Who will profit from cryptopay? How will this bring value to SUB tokens? A: Everyone will as we gain dominance. But also, Substratum the company will take a small percentage. This will enable us to continue building awesome apps. CryptoPay will be the cornerstone of many good things to come. Think retail, goods and services.
Q: I work at a games company with 200+ high powered pcs. If I install sub nodes on every single one of them at night, will IT be able to catch and fire me A: See your HR manual, or HR supervisor for those questions.
Q: How do websites and hosters remain protected from hacking, if sites are created with innate vulnerabilities does that expose other sites hosted by the same node? A: This is a great question. Hosting Nodes will have to vet out their security. Again, being decentralized goes a long way in providing security. So does encryption. We will help hosts be the best hosts possible.
Q: Please explain the earning in SUB by running a node? A: So the SUB comes FROM the HOST (who purchases the SUB) to the NODE for the cost of the transaction. https://youtu.be/LWZ1DIGGOoQ
Q: When will the tokens be sent for the 100 Sub giveaway A: Shortly
Q: How will Substratum market themselves towards countries that needs SUB the most but are hard to reach, such as North Korea, Africa, China? A: Think spider web. The more that join, and use, the less it can be controlled.
Q: How long will this bear market last for? A: Let me put the fortune teller hat on. Crypto is a young demographic currently. It will be bear'ish until we make the technology easier and they get older.
submitted by smf3928 to binance [link] [comments]

Error installing BTCP node

I am geting the following error after downloading the Linux version off https://github.com/BTCPrivate/BitcoinPrivate/releases
[email protected]:~/btcp# Error: Cannot find the Bitcoin Private network parameters in the following directory: "/root/.zcash-params" Please run 'zcash-fetch-params' or './btcputil/fetch-params.sh' and then restart.
Is there a setup guide anywhere?
submitted by BeastMiners to BitcoinPrivate [link] [comments]

Full script for automated installation of OpenBazaar on VPS from $1.79 vps service for your full control.

This is second (improved and simplified) version of my "OpenBazaar-Server installation for 5 minutes on any cheap VPS based on Ubuntu" https://www.reddit.com/OpenBazaacomments/4gi0sv/install_openbazaar_server_on_vps_for_5_minutes/ - basically this script does the same commands, but automatically (except for the part where you need to edit 2 configuration files)
Copy/paste this lines into your obauto.sh (bash script into your Ubuntu server) and OpenBazaar Server should be deployed automatically - almost with the same simplicity as you would install *.exe installer for Windows.
This script compatible only with Ubuntu and might not work if paths and other variables are not the same as in my simple VPS. This installation is recommended for http://firstvds.ru provider which offers VPS servers at $1.79
Commands to setup script.
Copy/paste this into obauto.sh:
#!/bin/bash
after "crontab -e" command you will have to insert this line at the end: */5 * * * * /root/obup-mastecheck.sh 2>&1 | ts [\%Y.\%m.\%d.\%k.\%M.\%S] >> /root/obup-mastecheck.log
This is not the latest version of simplified script for installing OpenBazaar Server on VPS for having your OpenBazaar store online 24/7.
I will be improving things to make your manual installation process even smoother.
Anyone who knows how to improve this script, are welcome to discuss it here.
If you don't know how to order cheap VPS from http://firstvds.ru provider, get your $1.79 vps - by visiting our 24/7 VPS store ob://1fcb9a8beb32f688fef7b61a52d091b9dd8c1f27/store - we will guide you through the whole process!
My technical support topic on /bitcoin https://np.reddit.com/Bitcoin/comments/4h46dn/im_ready_to_provide_voluntary_technical_support/
In order to transfer your OB server from Windows to Linux, follow this instructions: https://www.reddit.com/OpenBazaacomments/4f39d8/export_from_local_win_to_linux_serve
submitted by blksz to OpenBazaar [link] [comments]

Hardware wallet too expensive in Brazil, so this is my setup:

1) Live-usb ubuntu, network disconnected. 2) Generate addresses using bitcoin paper wallet downloaded offline site, printing PDFs. 3) Save these PDF on an encripted container using veracrypt, with a very strong password. This encripted file you can store safely online on google drive or something. 4) Split your BTC across some addresses, thinking of how you'll use them. Keep the public addresses handy. 5) When you want to use it, just boot ubuntu again, open the PDF, and use a mobile phone wallet like Mycelium to import the private key using QR Code. 6) Spend the amount needed and send the remaining amount to a new paper wallet and don't use the old one anymore.
This is my setup, what do you think? It's not absolutely 100% if you think of all the possibilities, but I think it's safe enough for even higher values. Main security concern is your phone, that should not be rooted, and should not have automatic backups (reported problems with Titanium backup, MIUI backup), because backups may store files unsecurely on your phone or on the cloud. Also, try to keep apps to a minimum because you never know if that "bitcoin price trackr app or whatever" may be looking to steal from you.
What do you think? Posted this trying to help concerned users. Of course hardware wallets are good, but sometimes you don't have the monies to buy one, just to buy BTC.
Edit: never type the veracrypt password anywhere and dont store it online.
submitted by cryptosnake to Bitcoin [link] [comments]

Bitcoin Mining on Ubuntu - YouTube Ubuntu -1 Setting up Bitcoin How to Bitcoin Miner with Ubuntu VPS - Setup Nicehash Miner via Ubuntu VPS Bitcoin Mining on Android using Termux 2020(Without root) How to install Bitcoin Core wallet in any Linux distribution

I have used various sizes for my root partition. On one machine I have regular Ubuntu and Ubuntu Studio, each installed in 10GB partitions. The regular ubuntu has used 6.04Gib and studio has used 3.08Gib. You can always change the partition size later anyway if you need more space. Just need to boot from a live CD and use GParted to change the ... Download Ubuntu desktop, Ubuntu Server, Ubuntu for Raspberry Pi and IoT devices, Ubuntu Core and all the Ubuntu flavours. Ubuntu is an open-source software platform that runs everywhere from the PC to the server and the cloud. Make a habit of logging to your server using a non-root account. This will prevent the accidental deletion of files if you make a mistake. For instance, the command rm can wipe your entire server if run incorrectly using by a root user. SSH to your server. ssh [email protected] Create a new user called cardano. useradd -m -s /bin/bash cardano. Set the password for cardano user ... Although Ubuntu carries Bitcoin Core in the Software Center, the release tends to be out-of-date. For this reason, this tutorial won’t use the Software Center. Compilation from source offers one alternative, but involves many steps. A more direct route is to install a precompiled binary from the command line. Searching for the Terminal application. The method described here uses Terminal, an ... sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-0.20.1/bin/* If you use su to run commands as root, use the following command line: su -c 'install -m 0755 -o root -g root -t /usr/local/bin bitcoin-0.20.1/bin/*' To continue, choose one of the following options. To use Bitcoin Core Graphical User Interface (GUI), proceed to the Bitcoin Core GUI section below. To use the Bitcoin ...

[index] [36840] [47248] [50477] [24788] [33319] [13360] [24907] [46290] [11534] [14122]

Bitcoin Mining on Ubuntu - YouTube

Bitcoin 101 - Getting Your BTCs out of Your Paper Wallets & Cold Storage - Fun with Sloppy Wallets - Duration: 10:54. CRI 82,619 views How to install Bitcoin on Ubuntu 16.04 On this video, I will show you how to install Bitcoin on Ubuntu 16.04 Commands sudo apt-add-repository ppa:bitcoin/bi... This video covers the method to install BitCoins on Ubuntu 16.04 Bitcoin is a virtual and crypto-currency created by Satoshi Nakamoto. For more explanation o... Ubuntu -1 Setting up Bitcoin Commands, sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install bitcoin-qt sudo apt-get install bitcoind sudo blkid sudo nano /etc/fstab ... Use the VanityGen tool to generate a Bitcoin address that stands out from the others. Decide for yourself the first part of the address, and have an address ...

#