How To Install And Enable Bitcoin Core Wallet On Linux

Make your own stakebox. Ultimate beginners guide how to compile any wallet on AARCH64 (Raspbery pi and other SBC)

I contemplated to wrote this for a long time, so it's finally time.
As you know a lot of altcoins uses PoS (Proof-of-stake) way of "mining" coins. Which basically means, that you hold coins on your unlocked wallet and you are receiving stakes as a reward. This requires very little power and it can bring you a lot of rewards, at just 10W from the wall.
So first I am using latest Raspbian on RPI4B 4GB in this example.Setting up Raspbian is not part of this process since it's very well documented. I recommend to change user from pi to something else due to security concerns and you can also do other stuff just search "security Raspberry PI" and you find a lot of articles, but this is not the focus of this guide.
I know there are a lot of guides on the internet, but I am using like 5 sources, so it's compiled what other people wrote and some of my research.
I am using AnyDesk insted of SSH or VNC server, because it works it's ligthweit and it just works.
So after you see the gui of Raspbian, just launch terminal (CTRL + ALT + T) and do basic thing:
sudo apt-get update && sudo apt-get upgrade
Than press Y and let it run, after is finished, we need to prepare so dependency packages. Since most of the wallets using Berkeley DB 4.8 we need to obtain it.
So in terminal wrote:
cd cd Downloads wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz tar -xzvf db-4.8.30.NC.tar.gz cd db-4.8.30.NC/build_unix ../dist/configure --enable-cxx make sudo make install 
So wait unti it's finished and than you can delete files in Downloads folder in gui or use:
sudo rm -r [folder] 
So next thing we need to install some libraries.
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 pres y and let it run. After that another set of libraries:
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libcrypto++- dev libminiupnpc-dev qt5-default 
And then again pres y and let it run. Some wallets need older version of libssl1.0-dev, so for for safe compiling we install that as well:
sudo apt-get install libssl1.0-dev 
Pres y and let it run. Warning don't use sudo-apt get autoremove, since it would wipe this package, since it's old.
Next thing we are going to obtain Bitcoin PPA filest, which can be done like this.
cd /etc/apt/sources.list.d/ sudo nano bitcoin.list 
Paste this in there:
deb-src http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu artful main 
And CTRL+X and than y, then do this:
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv C70EF1F0305A1ADB9986DBD8D46F45428842CE5E sudo apt-get update 
So now we are ready for compiling. So we are going create folders. CD yourself where this folder should be situated, if you for example have plugged in some external drive. Then:
mkdir Crypto cd Crypto 
And then we have to choose wallet which you want to compile. I am choosing Streamies (STRMS) as an example, since it's pretty good coin for staking. So:
mkdir Streamies cd Streamies 
Then go to the github page and click on the green button on the left and click copy to clipboard, which gives you git link.
git clone https://github.com/Streamies/Streamies.git 
Watch the output folder which it creates, it's stated in the first two lines and copy then by highliting the text and CTRL+SHIFT+C copy it to your clipboard.
cd Streamies (this is that git created folder) ./autogen.sh ./configure CPPFLAGS="-I/uslocal/BerkeleyDB.4.8/include -O2" LDFLAGS="-L/uslocal/BerkeleyDB.4.8/lib" sudo make (this could take hours) sudo make install 
And you are done, files is going to be in folder /uslocal/bin (DO NOT delete git created folder, because you are going to need it for faster compiling, when wallet get's and update.)
cd /uslocal/bin 
Now you can list files by:
ls 
And then you can copy/move them where ever you want by using:
sudo mv * [destination full path] 
Let it run and go back to folder where you move those files.
sudo chmod +x streamies-qt (since we want to run wallet) 
In most cases compiled files are going to in format of "shared library" so we need to create script to run it. Open up a text editor from gui or through nano. And paste this to that file:
#!/bin/bash ./streamies-qt 
And save it as a sh file, for example run.sh. Then we need to make it runnable so:
sudo chmod +x run.sh 
Now to run it, it's just:
./run.sh 
And here we are glorious GUI wallet appears and you are done, you can paste blockchain, wallet.dat from other sources, so this migration is pretty easy and you, if you have it on for exaple flash disk.
So this is basic how to compile QT wallets on AARCH64. I am running 7 wallets, 2 of those are Masternodes and RPI 4B 4GB would handle way more, I am at best on half of my RAM.
Some wallets need more package, but it's not much of and issue, since compiling stops and you just copy paste nape which is missing put it in the google and add "apt-get" after the name of package and you are going to see, what is the name of the packages so it can be retreived from package assinstant aka apt-get. So basically:
sudo apt-get install [package name] 
Then press y and again wrote:
sudo make 
This process is going to continue where it was left off, so nothing is going to run from beginning.
Updating wallets is basically exactly same, just repeat steps from "git clone" and after that proceed as it was written above.
So I hope this helps some of you, to use this at home and not on some VPS, if you are anxious as me, to host my wallets on remote server.
submitted by M1chlCZ to CryptoCurrency [link] [comments]

How to get Energi Wallet running on Raspberry Pi 4

How to get Energi Wallet running on Raspberry Pi 4
Hello,
I'm new to the Raspberry Pi and trying to get the NRG Core Cryptocurrency wallet running on my Raspberry. Finally I was able to compile the files after this commands:
Download and install the newest updates sudo apt-get update && sudo apt-get upgrade
Install the following major dependencies packages 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
Install the following QT dependencies packages 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 cd /etc/apt/sources.list.d/
sudo nano bitcoin.list
Add this line to the file: deb-src http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu artful main
Close file
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv C70EF1F0305A1ADB9986DBD8D46F45428842CE5E
sudo apt-get update
Clone Github cd git clone https://github.com/energicryptocurrency/energi.git
Install Libdb4.8 Libdb4.8-dev Libdb++ Libdb4.8++-dev
Compile the wallet cd energi ./autogen.sh ./configure --with-boost-libdir=/uslib/arm-linux-gnueabihf make sudo make install
After compiling I see the files in /uslocal/bin
https://preview.redd.it/25m1nm8164k41.jpg?width=2016&format=pjpg&auto=webp&s=3dfec55b307187eea06a279e284a19a6ae5d6d37
No I need to know how to use this files? Can someone help me please?
submitted by FCU4ever to energicryptocurrency [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.4.0.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.4.0.0, August 17th, 2018) from:
 
https://www.bitcoinunlimited.info/download
 
This release is a major release which is compatible with the Bitcoin Cash compatible with the Bitcoin Cash specifications you could find here:
 
A subsequent release containing the implementation of the November 2018 specification will be released soon after this one.
 
List of notable changes and fixes to the code base:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.4.0.0.md
 
Ubuntu PPA repository for BUcash 1.4.0.0 has been updated
submitted by s1ckpig to btc [link] [comments]

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

Intro

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

Overview

 

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Video

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

Extra

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

Credits:

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

Bitcoin Unlimited Cash edition 1.1.1.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.1.1.0, August 10, 2017) from:
https://www.bitcoinunlimited.info/download
Notable changes:
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/BitcoinCash/doc/release-notes/release-notes-bucash1.1.1.0.md
NOTE: This release is for Bitcoin Cash, a FORK of Bitcoin happened on Aug 1,2017! If you are new to Bitcoin or do not understand the prior sentence, you do not want this release. Instead choose the "Latest Official Release".
Ubuntu PPA is in the process of being updated.
submitted by s1ckpig to btc [link] [comments]

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

This tutorial has been updated: https://www.reddit.com/reddCoin/comments/a0wn1v/updated_staking_reddcoin_core_client_gui_wallet/.
   

Intro

I want to stake Reddcoins on my Raspberry Pi, but there is no easy to install package for the Reddcoin Core client. I found some tutorials (mentioned at the bottom, under 'credits'), but I still struggled to get the result I wanted. It took some small adjustments, but I got the GUI Wallet of Reddcoin Core working on my Raspberry Pi Model 3B. See the steps below. :).
 
If you have any questions or comments, please post a comment in this thread, so others can also benefit from it.
 
If you would like to tip me: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
   
Even though Raspbian is the primary OS for the Raspberry Pi, it seems that it's not possible to build and compile the Reddcoin wallet software for Raspbian Stretch. However, I got the wallet compiled using Ubuntu MATE.
     

Overview

     

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Extra

 
 
 
 
     

Credits:

 
Thank you all for sharing your knowledge!
submitted by Yavuz_Selim to reddCoin [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]

Steps to move 2of2 with ntimelock.zip

EDIT: this is about moving bcash coins, not the normal BTC.
Finally, I moved BCH coins off greenaddress so that I can dump them.
I’d like to thank: ‘dumpyourbcash’ https://github.com/dumpyourbcash/garecovery
Jeremy Kauffman ‘jkauffman1’ https://github.com/greenaddress/garecovery
Alex Perev https://github.com/AlexPerev/garecovery
Without their works prior, I won’t be able to move BCH today.
This write up is just for my scenario, my profession is mostly databases and web-based technologies. I only picked up python since the recent BCH run up which gave me enough incentive to dump them.
I spent some spare time to figure out the following steps. It worked for me, and it does not mean I went on the shortest path. Some steps could well be optional, but I list them here in case things not working out, and these steps could help you move further. Be aware this guide is all done in Linux terminal, no GUI involved, and assume you have basic knowledge using Linux and vim editor.
My scenario is the following:
Software needed:
Hope this can help some to get bcash out, it still has some value at this moment 😊
Donations are welcome.
BTC: 3HajumDneidRxGk5s99bBB7WCrCsPxpQZ5 BCH: 1LEvtKNEDMDYMAUQDLZwQLYjAEgsRBcnCz 
submitted by RaggiGamma to greenaddress [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]

Interested in contributing to the BTC network? Here is the steps to get a full node up and running in Linux.

These instructions will work both on a VPS cloud server or a personal computer. You may find cheap VPS somewhere online for rent.
What Is A Full Node?
A full node is a program that fully validates transactions and blocks. Almost all full nodes also help the network by accepting transactions and blocks from other full nodes, validating those transactions and blocks, and then relaying them to further full nodes.
Most full nodes also serve lightweight clients by allowing them to transmit their transactions to the network and by notifying them when a transaction affects their wallet. If not enough nodes perform this function, clients won’t be able to connect through the peer-to-peer network—they’ll have to use centralized services instead.
Many people and organizations volunteer to run full nodes using spare computing and bandwidth resources—but more volunteers are needed to allow Bitcoin to continue to grow. This document describes how you can help and what helping will cost you.
Costs And Warnings
Running a Bitcoin full node comes with certain costs and can expose you to certain risks. This section will explain those costs and risks so you can decide whether you’re able to help the network.
Special Cases
Miners, businesses, and privacy-conscious users rely on particular behavior from the full nodes they use, so they will often run their own full nodes and take special safety precautions. This document does not cover those precautions—it only describes running a full node to help support the Bitcoin network in general.
Please consult an expert if you need help setting up your full node correctly to handle high-value and privacy-sensitive tasks.
Secure Your Wallet
It’s possible and safe to run a full node to support the network and use its wallet to store your bitcoins, but you must take the same precautions you would when using any Bitcoin wallet. Please see the securing your wallet page for more information.
Minimum Requirements
Bitcoin Core full nodes have certain requirements. If you try running a node on weak hardware, it may work—but you’ll likely spend more time dealing with issues. If you can meet the following requirements, you’ll have an easy-to-use node.
Note: many operating systems today (Windows, Mac, and Linux) enter a low-power mode after the screensaver activates, slowing or halting network traffic. This is often the default setting on laptops and on all Mac OS X laptops and desktops. Check your screensaver settings and disable automatic “sleep” or “suspend” options to ensure you support the network whenever your computer is running.
Possible Problems
Legal: Bitcoin use is prohibited or restricted in some areas.
Bandwidth limits: Some Internet plans will charge an additional amount for any excess upload bandwidth used that isn’t included in the plan. Worse, some providers may terminate your connection without warning because of overuse. We advise that you check whether your Internet connection is subjected to such limitations and monitor your bandwidth use so that you can stop Bitcoin Core before you reach your upload limit.
Anti-virus: Several people have placed parts of known computer viruses in the Bitcoin block chain. This block chain data can’t infect your computer, but some anti-virus programs quarantine the data anyway, making it more difficult to run a full node. This problem mostly affects computers running Windows.
Attack target: People who want to disrupt the Bitcoin network may attack full nodes in ways that will affect other things you do with your computer, such as an attack that limits your available download bandwidth or an attack that prevents you from using your full node’s wallet for sending transactions.
Linux Instructions
The following instructions describe installing Bitcoin Core on Linux systems.
Ubuntu 14.10 Instructions for Bitcoin Core 0.10.0.
If you use Ubuntu Desktop, click the Ubuntu swirl icon to start the Dash and type “term” into the input box. Choose any one of the terminals listed:
Alternatively, access a console or terminal emulator using another method, such as SSH on Ubuntu Server or a terminal launcher in an alternative desktop environment.
Type the following line to add the Bitcoin Personal Package Archive (PPA) to your system:
sudo apt-add-repository ppa:bitcoin/bitcoin
You will be prompted for your user password. Provide it to continue. Afterwards, the following text will be displayed:
Stable Channel of bitcoin-qt and bitcoind for Ubuntu, and their dependencies
More info: https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin
Press [ENTER] to continue or ctrl-c to cancel adding it
Press enter to continue. The following text (with some variations) will be displayed and you will be returned to the command line prompt:
gpg: keyring /tmp/tmpixuqu73x/secring.gpg' created gpg: keyring/tmp/tmpixuqu73x/pubring.gpg' created gpg: requesting key 8842CE5E from hkp server > > > >keyserver.ubuntu.com gpg: /tmp/tmpixuqu73x/trustdb.gpg: trustdb created gpg: key 8842CE5E: public key "Launchpad PPA for Bitcoin" imported gpg: no ultimately trusted keys found gpg: Total number processed: 1 pg: imported: 1 (RSA: 1) OK
Type the following line to get the most recent list of packages:
sudo apt-get update
A large number of lines will be displayed as different update files are downloaded. This step may take several minutes on a slow Internet connection.
To continue, choose one of the following options
sudo apt-get install bitcoin-qt
sudo apt-get install bitcoind
sudo apt-get install bitcoin-qt bitcoind
After choosing what packages to install, you will be asked whether you want to proceed. Press enter to continue.
If you’re logged in as an administrative user with sudo access, you may log out. The steps in this section should be performed as the user you want to run Bitcoin Core. (If you’re an expert administrator, you can make this a locked account used only by Bitcoin Core.)
Before using the Bitcoin Core daemon, bitcoind, you need to create its configuration file with a user name and password. First create the .bitcoin directory, create (touch) the file, and set the file’s permissions so that only your user account can read it. From the terminal, type:
mkdir ~/.bitcoin touch ~/.bitcoin/bitcoin.conf chmod 600 ~/.bitcoin/bitcoin.conf
Then you can run the command bitcoind. It will print output similar to this:
bitcoind Error: To use the "-server" option, you must set a rpcpassword in the configuration file: /home/bitcoinorg/.bitcoin/bitcoin.conf It is recommended you use the following random password: rpcuser=bitcoinrpc rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions. It is also recommended to set alertnotify so you are notified of problems; for example: alertnotify=echo %s | mail -s "Bitcoin Alert" [email protected] The “rpcpassword” displayed will be unique for your system. You can copy the rpcuser and rpcpassword lines into your configuration file using the following commands. Note that in most Ubuntu terminals, you need to press Ctrl-Shift-C to copy and Ctrl-Shift-V to paste because Ctrl-C and Ctrl-V have different meanings in a Unix-style terminal.
echo rpcuser=bitcoinrpc >> ~/.bitcoin/bitcoin.conf echo rpcpassword=XXXXXX >> ~/.bitcoin/bitcoin.conf (Warning: Don’t use XXXXXX as your RPC password. Copy the rpcpassword displayed by bitcoind for your system.)
Now you can start Bitcoin Core daemon for real. Type the following command:
bitcoind -daemon
It will print a message that Bitcoin Core is starting. To interact with Bitcoin Core daemon, you will use the command bitcoin-cli (Bitcoin command line interface). Note: it may take up to several minutes for Bitcoin Core to start, during which it will display the following message whenever you use bitcoin-cli:
error: {"code":-28,"message":"Verifying blocks..."}
After it starts, you may find the following commands useful for basic interaction with your node:
to safely stop your node, run the following command:
bitcoin-cli stop
A complete list of commands is available in the Bitcoin.org developer reference.
When Bitcoin Core daemon first starts, it will begin to download the block chain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection bandwidth. You can stop Bitcoin Core at any time using the stop command; it will resume from the point where it stopped the next time you start it.
Optional: Start Your Node At Boot
Starting your node automatically each time your computer boots makes it easy for you to contribute to the network. The easiest way to do this is to start Bitcoin Core daemon from your crontab. To edit your crontab, run the following command:
crontab -e
@reboot bitcoind -daemon Save the file and exit; the updated crontab file will be installed for you. Now Bitcoin Core daemon will be automatically started each time your reboot your computer.
If you’re an Ubuntu expert and want to use an init script instead, see this Upstart script.
You have now completed installing Bitcoin Core. If you have any questions, please ask in one of Bitcoin’s many communities, such as Bitcoin StackExchange, BitcoinTalk technical support, or the #bitcoin IRC chatroom on Freenode.
To support the Bitcoin network, you also need to allow incoming connections. Please read the Network Configuration section for details.
Network Configuration
If you want to support the Bitcoin network, you must allow inbound connections.
When Bitcoin Core starts, it establishes 8 outbound connections to other full nodes so it can download the latest blocks and transactions. If you just want to use your full node as a wallet, you don’t need more than these 8 connections—but if you want to support lightweight clients and other full nodes on the network, you must allow inbound connections.
Servers connected directly to the Internet usually don’t require any special configuration. You can use the testing instructions below to confirm your server-based node accepts inbound connections.
Home connections are usually filtered by a router or modem. Bitcoin Core will request your router automatically configure itself to allow inbound connections to Bitcoin’s port, port 8333. Unfortunately many routers don’t allow automatic configuration, so you must manually configure your router. You may also need to configure your firewall to allow inbound connections to port 8333. Please see the following subsections for details.
Testing Connections
The BitNodes project provides an online tool to let you test whether your node accepts inbound connections. To use it, start Bitcoin Core (either the GUI or the daemon), wait 10 minutes, and then visit the GetAddr page (https://getaddr.bitnodes.io/). The tool will attempt to guess your IP address—if the address is wrong (or blank), you will need to enter your address manually.
For more instruction and reviews based off BTC please follow my subreddit /BTC_Reviews
all material from this post was found here --> https://bitcoin.org/en/full-node
submitted by Mattjhagen to Bitcoin [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.4.0.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.4.0.0, August 17th, 2018) from:
 
https://www.bitcoinunlimited.info/download
 
This release is a major release which is compatible with the Bitcoin Cash compatible with the Bitcoin Cash specifications you could find here:
 
A subsequent release containing the implementation of the November 2018 specification will be released soon after this one.
 
List of notable changes and fixes to the code base:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.4.0.0.md
 
Ubuntu PPA repository for BUcash 1.4.0.0 has been updated
submitted by s1ckpig to Bitcoincash [link] [comments]

Bitcoin Unlimited Cash edition 1.1.1.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.1.1.0, August 10, 2017) from:
https://www.bitcoinunlimited.info/download
Notable changes:
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/BitcoinCash/doc/release-notes/release-notes-bucash1.1.1.0.md
NOTE: This release is for Bitcoin Cash, a FORK of Bitcoin that is happening on Aug 1,2017! If you are new to Bitcoin or do not understand the prior sentence, you do not want this release. Instead choose the "Latest Official Release".
A new Ubuntu PPA will be set up shortly.
submitted by s1ckpig to bitcoin_unlimited [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.4.0.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.4.0.0, August 17th, 2018) from:
 
https://www.bitcoinunlimited.info/download
 
This release is a major release which is compatible with the Bitcoin Cash compatible with the Bitcoin Cash specifications you could find here:
 
A subsequent release containing the implementation of the November 2018 specification will be released soon after this one.
 
List of notable changes and fixes to the code base:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.4.0.0.md
 
Ubuntu PPA repository for BUcash 1.4.0.0 has been updated
submitted by s1ckpig to bitcoin_unlimited [link] [comments]

Litecoin Compilation Guide Linux Ubuntu 16.04

If you are on Linux Ubuntu 16.04, follow those steps (cut and paste one line at a time in a new Terminal window):
\*** ensure that the system is up to date ***** sudo apt-get update sudo apt-get upgrade sudo apt-get dist-upgrade sudo apt-get autoremove sudo reboot
\*** download the source code ***** mkdir Github && cd Github sudo apt-get install git git clone https://github.com/litecoin-project/litecoin cd litecoin
\*** Install the dependencies ***** sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev sudo apt-get install bsdmainutils libboost-system-dev libboost-filesystem-dev libboost-chrono-dev sudo apt-get install libboost-program-options-dev libboost-test-dev libboost-thread-dev sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev sudo apt-get install libqrencode-dev protobuf-compiler miniupnpc
\*** To install the deprecated version of Berkeley DB 4.8 ***** sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8+±dev
\*** Compile ***** ./autogen.sh ./configure make
\*** Optional ****** sudo make install
\*** Execute ***** cd ~/Github/litecoin/src/qt ./litecoin-qt
submitted by senisende to litecoin [link] [comments]

How To Setup a Seed Node for Snatcoin for Free

Seed nodes are important for the strength of the Snatcoin Network. By adding a seed node you will be supporting Snatcoin and helping it grow.
These instructions below are for Windows users.
Go to https://aws.amazon.com/free and get yourself a free Amazon web services account
After you are logged into Amazon AWS select "Launch a virtual machine".
Select "get started" on EC2 Instance. After this you will name your instance
Now select a free tier eligible Ubuntu Server 16.04.
Open up a new tab for your Security Group. Click on Actions -> Edit Inbound Rules. Change Source to My IP and save. Down the bottom you should see the IP of that computer.
Launch your AWS instance, after a while on the "Instance State" tab you should see that it is running with a green dot next to it You will create a security pair key. Download this file and keep it safe.
Download Putty from https://www.putty.org/ Then install it.
Run Puttygen and convert your *.pem file to a *.ppk file
Open Putty. Make sure the port is the same port on your AWS Security Group tab. If you didn't change anything it will be 22.
Then go to Connection -> SSH -> Auth and add your *.ppk file to private key for authentication
Add in the Public IP shown in your EC2 Management Console for your virtual machine to Putty as the Host Name
Click Open on Putty. Click Yes. Then as your username use ubuntu You should now be inside your AWS virtual machine.
Install dependencies on your Ubuntu AWS Instance
sudo apt-get install git sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils sudo apt-get install libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-program-options- dev libboost-test-dev libboost-thread-dev sudo apt-get install libboost-all-dev sudo apt-get install software-properties-common sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev sudo apt-get install libminiupnpc-dev sudo apt-get install libzmq3-dev sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler sudo apt-get install libqt4-dev libprotobuf-dev protobuf-compiler git clone https://github.com/snatcoinOfficial/snatcoin cd snatcoin cd src 
Your instance will run out of memory on rpcbitcoin.cpp if you do not run these lines below before you compile snatcoind
sudo dd if=/dev/zero of=/swapfile bs=64M count=16 sudo mkswap /swapfile sudo swapon /swapfile 
You can now run
make -f makefile.unix 
Now you can run your snatcoind daemon
./snatcoind -daemon 
This will fail and will tell you to add some extra information to your snatcoin.conf file
Now you will have to edit your snatcoin.conf file
cd .. cd .. cd .snatcoin vi snatcoin.conf 
Now you have to set up your snatcoin.conf file in the .snatcoin directory
Add to snatcoin.conf file:
addnode=18.218.135.144 addnode=159.65.182.125 rpcuser=somethinghere rpcpassword=anythinghere 
Then save the file by typing :wq
This is to verify you wrote to your snatcoin.conf file
cat snatcoin.conf 
Now go back to your snatcoin directory and run the snatcoind
cd .. cd snatcoin ./snatcoind -daemon 
Wait for the server to load and sync up to the network
You are now connected so lets find out what else we can run from snatcoind
./snatcoind help 
On Amazon AWS select Action -> Change Instance Settings -> Change Termination Protection
Then turn termination protection on to make sure it doesn't terminate
You can now close Putty and your Instance will still be alive
The new seed node I added during this process was 18.218.135.144
submitted by Myshakiness to snatcoin [link] [comments]

The Qtum Test Network has been RELEASED!

The Qtum Test Network Has Been Released:
https://github.com/qtumproject/qtum/releases/tag/testnet-sparknet
Instructions on how to compile from source are listed in the Git. Please see the documentation provided:
Quickstart Build on Ubuntu This is a quick start script for compiling Qtum on Ubuntu sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils git cmake libboost-all-dev sudo apt-get install software-properties-common sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev # If you want to build the Qt GUI: sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler git clone https://github.com/qtumproject/qtum cd qtum # Update cpp-ethereum submodule git submodule update --init --recursive # Note autogen will prompt to install some more dependencies if needed ./autogen.sh ./configure make -j2 
If you would like to receive Test Network tokens, please PM this account with your address and we will get them sent ASAP. These test tokens will have no value, so you are free to share them with others for testing. We will have a faucet set up shortly, along with a Win64 QT shortly.
Right now the team is preparing for our launch event in Shanghai, so it may be a touch busy on our side for the next day.
Visit the Qtum Website: https://qtum.org/en/ Join the Qtum Slack: https://qtumslack.herokuapp.com/
submitted by Vindyne8 to icocrypto [link] [comments]

Optional Beginner Guide to Litecoin: TESTED 12/7/2013

Plan B: BAMT Live USB
This option is a last resort, hopefully not necessary. Download BAMT from the link below and "dd" via terminal to USB formatted to FAT32 in gparted. You can install gparted in xubuntu by typing:
sudo apt-get install gparted 
Next, launch gparted and format your USB drive. Be careful not to format your HDDs! You might double-check the storage sizes as a reference in the upper-right drop-down menu.
Download link: https://mega.co.nz/#!NI5W2QLT!dYt2UTZz0hrFoiMUAu0d01eSD4pjqXHT6U2UtnAAGJ4
Extract the file and locate "litecoinbamt1.1.img"
Put image on 2GB or greater USB formatted to FAT32 by opening terminal and running:
sudo dd if=/path/to/litecoinbamt1.1.img of=/dev/sdX (The "X" is the device name of your usb key. The one you will have seen in gparted, for example "sdb, or sdc, or sdd..." Try to get the right device on the first try. Use raw device *not* a partition.) sudo dd if=(you can drag and drop file into the terminal here to get the path) of=/dev/sdX 
CAN TAKE 15 MINUTES or more.
Perhaps try newer release of BAMT: https://mega.co.nz/#!qZ1TXRxD!Mcw8pkrP4SQE8D7bIfmZZEola01hxVFtbOBg6Cr3Zeo
sudo dd if=/path/to/litecoinbamt1.2.img of=/dev/sdX 
(source: http://www.bitcointrading.com/forum/linux-distros/bamt-version-0-5-easy-usb-based-mining-linux-with-farm-wide-management-tools/)
Plan A: Xubuntu BFGminer
Step 1: Get prepared. This is for a FRESH install of Xubuntu 13.10. Start with a fresh installation. Run the following in the terminal, line by line, one at a time. Press enter after each.
sudo apt-get install fglrx-updates fglrx-amdcccle-updates fglrx-updates-dev sudo aticonfig --lsa sudo aticonfig --adapter=all --initial sudo reboot 
(source: http://www.cryptobadger.com/2013/04/build-a-litecoin-mining-rig-linux/)
sudo apt-get install libcurl4-openssl-dev pkg-config libtool libncurses5-dev libudev-dev screen xterm sudo apt-get install git-core sudo apt-get install openssh-server byobu sudo apt-get install autoconf sudo apt-get install automake 
(source: https://coinaxis.com/index.php/entry/how-to-configure-linux-and-build-cgminer-for-bitcoin-and-litecoin)
sudo add-apt-repository ppa:unit3/bfgminer sudo apt-get update sudo apt-get install bfgminer sudo apt-get upgrade 
To launch:
bfgminer --scrypt -o stratum+tcp://world.wemineltc.com:3334 -u workername -p password -I 13 
(source: http://jarco.be/install-bfgminer-ubuntu-mint/)
submitted by Marco_X to litecoinmining [link] [comments]

Unmet dependicies when installing/upgrading software

I've tried some solutions online that didn't work. I don't remember where they were or if I did them correctly so I figured I'd start from scratch.
When I boot I get this long list to choose from. http://i.imgur.com/wktxT2d.png The top one doesn't work and just goes to blackscreen, but the bottom(non recovery mode) does work. I haven't tried the rest.
When I sodo apt update everything goes normally:
[email protected]:~$ sudo apt update [sudo] password for jason: Get:1 http://security.ubuntu.com/ubuntu yakkety-security InRelease [102 kB] Hit:2 http://us.archive.ubuntu.com/ubuntu yakkety InRelease Get:3 http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease [102 kB] Hit:4 http://ppa.launchpad.net/bitcoin-unlimited/bu-ppa/ubuntu yakkety InRelease Get:5 http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease [102 kB] Get:6 http://security.ubuntu.com/ubuntu yakkety-security/main i386 Packages [120 kB] Get:7 http://security.ubuntu.com/ubuntu yakkety-security/main amd64 Packages [123 kB] Get:8 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages [241 kB] Get:9 http://security.ubuntu.com/ubuntu yakkety-security/main Translation-en [54.8 kB] Get:10 http://security.ubuntu.com/ubuntu yakkety-security/main amd64 DEP-11 Metadata [10.9 kB] Get:11 http://security.ubuntu.com/ubuntu yakkety-security/main DEP-11 64x64 Icons [15.7 kB] Get:12 http://security.ubuntu.com/ubuntu yakkety-security/universe amd64 DEP-11 Metadata [18.7 kB] Get:13 http://security.ubuntu.com/ubuntu yakkety-security/universe DEP-11 64x64 Icons [18.4 kB] Get:14 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main i386 Packages [236 kB] Get:15 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main Translation-en [108 kB] Get:16 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 DEP-11 Metadata [146 kB] Get:17 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main DEP-11 64x64 Icons [87.3 kB] Get:18 http://us.archive.ubuntu.com/ubuntu yakkety-updates/universe i386 Packages [145 kB] Get:19 http://us.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 Packages [147 kB] Get:20 http://us.archive.ubuntu.com/ubuntu yakkety-updates/universe Translation-en [78.4 kB] Get:21 http://us.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 DEP-11 Metadata [112 kB] Get:22 http://us.archive.ubuntu.com/ubuntu yakkety-updates/universe DEP-11 64x64 Icons [155 kB] Get:23 http://us.archive.ubuntu.com/ubuntu yakkety-backports/main amd64 DEP-11 Metadata [3,328 B] Fetched 2,126 kB in 0s (3,062 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 2 packages can be upgraded. Run 'apt list --upgradable' to see them. 
Errors occur when I try to update:
[email protected]:~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: linux-image-extra-4.8.0-41-generic : Depends: linux-image-4.8.0-41-generic but it is not installed linux-image-extra-4.8.0-44-generic : Depends: linux-image-4.8.0-44-generic but it is not installed linux-image-extra-4.8.0-45-generic : Depends: linux-image-4.8.0-45-generic but it is not installed linux-image-extra-4.8.0-46-generic : Depends: linux-image-4.8.0-46-generic but it is not installed linux-image-generic : Depends: linux-image-4.8.0-46-generic but it is not installed linux-signed-image-4.8.0-41-generic : Depends: linux-image-4.8.0-41-generic (= 4.8.0-41.44) but it is not installed linux-signed-image-4.8.0-44-generic : Depends: linux-image-4.8.0-44-generic (= 4.8.0-44.47) but it is not installed linux-signed-image-4.8.0-45-generic : Depends: linux-image-4.8.0-45-generic (= 4.8.0-45.48) but it is not installed linux-signed-image-4.8.0-46-generic : Depends: linux-image-4.8.0-46-generic (= 4.8.0-46.49) but it is not installed E: Unmet dependencies. Try using -f. 
Using -f still encounters errors:
[email protected]:~$ sudo apt upgrade -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: linux-headers-4.8.0-26 linux-headers-4.8.0-26-generic linux-headers-4.8.0-27 linux-headers-4.8.0-27-generic linux-headers-4.8.0-28 linux-headers-4.8.0-28-generic linux-headers-4.8.0-30 linux-headers-4.8.0-30-generic linux-headers-4.8.0-32 linux-headers-4.8.0-32-generic linux-headers-4.8.0-41 linux-headers-4.8.0-41-generic linux-headers-4.8.0-44 linux-headers-4.8.0-44-generic linux-headers-4.8.0-45 linux-headers-4.8.0-45-generic linux-image-4.4.0-43-generic linux-image-4.8.0-26-generic linux-image-4.8.0-27-generic linux-image-4.8.0-28-generic linux-image-4.8.0-30-generic linux-image-4.8.0-32-generic linux-image-4.8.0-41-generic linux-image-4.8.0-44-generic linux-image-4.8.0-45-generic linux-image-extra-4.4.0-43-generic linux-image-extra-4.8.0-26-generic linux-image-extra-4.8.0-27-generic linux-image-extra-4.8.0-28-generic linux-image-extra-4.8.0-30-generic linux-image-extra-4.8.0-32-generic linux-image-extra-4.8.0-41-generic linux-image-extra-4.8.0-44-generic linux-image-extra-4.8.0-45-generic linux-signed-image-4.4.0-43-generic linux-signed-image-4.8.0-26-generic linux-signed-image-4.8.0-27-generic linux-signed-image-4.8.0-28-generic linux-signed-image-4.8.0-30-generic linux-signed-image-4.8.0-32-generic linux-signed-image-4.8.0-41-generic linux-signed-image-4.8.0-44-generic linux-signed-image-4.8.0-45-generic Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: linux-image-4.8.0-41-generic linux-image-4.8.0-44-generic linux-image-4.8.0-45-generic linux-image-4.8.0-46-generic The following packages will be upgraded: libpci3 pciutils 2 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. 24 not fully installed or removed. Need to get 266 kB/94.2 MB of archives. After this operation, 291 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 pciutils amd64 1:3.3.1-1.1ubuntu4.1 [242 kB] Get:2 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 libpci3 amd64 1:3.3.1-1.1ubuntu4.1 [24.0 kB] Fetched 266 kB in 0s (1,036 kB/s) (Reading database ... 563318 files and directories currently installed.) Preparing to unpack .../0-linux-image-4.8.0-46-generic_4.8.0-46.49_amd64.deb ... Examining /etc/kernel/preinst.d/ run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.8.0-46-generic /boot/vmlinuz-4.8.0-46-generic Done. Unpacking linux-image-4.8.0-46-generic (4.8.0-46.49) ... dpkg: error processing archive /tmp/apt-dpkg-install-sO47oq/0-linux-image-4.8.0-46-generic_4.8.0-46.49_amd64.deb (--unpack): cannot copy extracted data for './boot/vmlinuz-4.8.0-46-generic' to '/boot/vmlinuz-4.8.0-46-generic.dpkg-new': failed to write (No space left on device) No apport report written because the error message indicates a disk full error dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.8.0-46-generic /boot/vmlinuz-4.8.0-46-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.8.0-46-generic /boot/vmlinuz-4.8.0-46-generic Preparing to unpack .../1-linux-image-4.8.0-41-generic_4.8.0-41.44_amd64.deb ... Examining /etc/kernel/preinst.d/ run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.8.0-41-generic /boot/vmlinuz-4.8.0-41-generic Done. Unpacking linux-image-4.8.0-41-generic (4.8.0-41.44) ... dpkg: error processing archive /tmp/apt-dpkg-install-sO47oq/1-linux-image-4.8.0-41-generic_4.8.0-41.44_amd64.deb (--unpack): cannot copy extracted data for './boot/vmlinuz-4.8.0-41-generic' to '/boot/vmlinuz-4.8.0-41-generic.dpkg-new': failed to write (No space left on device) No apport report written because the error message indicates a disk full error dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.8.0-41-generic /boot/vmlinuz-4.8.0-41-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.8.0-41-generic /boot/vmlinuz-4.8.0-41-generic Preparing to unpack .../2-linux-image-4.8.0-44-generic_4.8.0-44.47_amd64.deb ... Examining /etc/kernel/preinst.d/ run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.8.0-44-generic /boot/vmlinuz-4.8.0-44-generic Done. Unpacking linux-image-4.8.0-44-generic (4.8.0-44.47) ... dpkg: error processing archive /tmp/apt-dpkg-install-sO47oq/2-linux-image-4.8.0-44-generic_4.8.0-44.47_amd64.deb (--unpack): cannot copy extracted data for './boot/vmlinuz-4.8.0-44-generic' to '/boot/vmlinuz-4.8.0-44-generic.dpkg-new': failed to write (No space left on device) No apport report written because the error message indicates a disk full error dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.8.0-44-generic /boot/vmlinuz-4.8.0-44-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.8.0-44-generic /boot/vmlinuz-4.8.0-44-generic Preparing to unpack .../3-linux-image-4.8.0-45-generic_4.8.0-45.48_amd64.deb ... Examining /etc/kernel/preinst.d/ run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.8.0-45-generic /boot/vmlinuz-4.8.0-45-generic Done. Unpacking linux-image-4.8.0-45-generic (4.8.0-45.48) ... dpkg: error processing archive /tmp/apt-dpkg-install-sO47oq/3-linux-image-4.8.0-45-generic_4.8.0-45.48_amd64.deb (--unpack): cannot copy extracted data for './boot/vmlinuz-4.8.0-45-generic' to '/boot/vmlinuz-4.8.0-45-generic.dpkg-new': failed to write (No space left on device) No apport report written because MaxReports is reached already dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.8.0-45-generic /boot/vmlinuz-4.8.0-45-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.8.0-45-generic /boot/vmlinuz-4.8.0-45-generic Preparing to unpack .../4-pciutils_1%3a3.3.1-1.1ubuntu4.1_amd64.deb ... Unpacking pciutils (1:3.3.1-1.1ubuntu4.1) over (1:3.3.1-1.1ubuntu4) ... Preparing to unpack .../5-libpci3_1%3a3.3.1-1.1ubuntu4.1_amd64.deb ... Unpacking libpci3:amd64 (1:3.3.1-1.1ubuntu4.1) over (1:3.3.1-1.1ubuntu4) ... Errors were encountered while processing: /tmp/apt-dpkg-install-sO47oq/0-linux-image-4.8.0-46-generic_4.8.0-46.49_amd64.deb /tmp/apt-dpkg-install-sO47oq/1-linux-image-4.8.0-41-generic_4.8.0-41.44_amd64.deb /tmp/apt-dpkg-install-sO47oq/2-linux-image-4.8.0-44-generic_4.8.0-44.47_amd64.deb /tmp/apt-dpkg-install-sO47oq/3-linux-image-4.8.0-45-generic_4.8.0-45.48_amd64.deb E: Sub-process /usbin/dpkg returned an error code (1) 
Attempting to autoremove gives the same error as upgrade:
[email protected]:~$ sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: linux-image-extra-4.8.0-41-generic : Depends: linux-image-4.8.0-41-generic but it is not installed linux-image-extra-4.8.0-44-generic : Depends: linux-image-4.8.0-44-generic but it is not installed linux-image-extra-4.8.0-45-generic : Depends: linux-image-4.8.0-45-generic but it is not installed linux-image-extra-4.8.0-46-generic : Depends: linux-image-4.8.0-46-generic but it is not installed linux-image-generic : Depends: linux-image-4.8.0-46-generic but it is not installed linux-signed-image-4.8.0-41-generic : Depends: linux-image-4.8.0-41-generic (= 4.8.0-41.44) but it is not installed linux-signed-image-4.8.0-44-generic : Depends: linux-image-4.8.0-44-generic (= 4.8.0-44.47) but it is not installed linux-signed-image-4.8.0-45-generic : Depends: linux-image-4.8.0-45-generic (= 4.8.0-45.48) but it is not installed linux-signed-image-4.8.0-46-generic : Depends: linux-image-4.8.0-46-generic (= 4.8.0-46.49) but it is not installed E: Unmet dependencies. Try using -f. 
Likewise with autoremove -f:
[email protected]:~$ sudo apt autoremove -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-4.8.0-46-generic Suggested packages: fdutils linux-doc-4.8.0 | linux-source-4.8.0 linux-tools The following packages will be REMOVED: linux-headers-4.8.0-26 linux-headers-4.8.0-26-generic linux-headers-4.8.0-27 linux-headers-4.8.0-27-generic linux-headers-4.8.0-28 linux-headers-4.8.0-28-generic linux-headers-4.8.0-30 linux-headers-4.8.0-30-generic linux-headers-4.8.0-32 linux-headers-4.8.0-32-generic linux-headers-4.8.0-41 linux-headers-4.8.0-41-generic linux-headers-4.8.0-44 linux-headers-4.8.0-44-generic linux-headers-4.8.0-45 linux-headers-4.8.0-45-generic linux-image-4.4.0-43-generic linux-image-4.8.0-26-generic linux-image-4.8.0-27-generic linux-image-4.8.0-28-generic linux-image-4.8.0-30-generic linux-image-4.8.0-32-generic linux-image-extra-4.4.0-43-generic linux-image-extra-4.8.0-26-generic linux-image-extra-4.8.0-27-generic linux-image-extra-4.8.0-28-generic linux-image-extra-4.8.0-30-generic linux-image-extra-4.8.0-32-generic linux-image-extra-4.8.0-41-generic linux-image-extra-4.8.0-44-generic linux-image-extra-4.8.0-45-generic linux-signed-image-4.4.0-43-generic linux-signed-image-4.8.0-26-generic linux-signed-image-4.8.0-27-generic linux-signed-image-4.8.0-28-generic linux-signed-image-4.8.0-30-generic linux-signed-image-4.8.0-32-generic linux-signed-image-4.8.0-41-generic linux-signed-image-4.8.0-44-generic linux-signed-image-4.8.0-45-generic The following NEW packages will be installed: linux-image-4.8.0-46-generic 0 upgraded, 1 newly installed, 40 to remove and 0 not upgraded. 26 not fully installed or removed. Need to get 0 B/23.5 MB of archives. After this operation, 2,445 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 563317 files and directories currently installed.) Removing linux-image-extra-4.8.0-41-generic (4.8.0-41.44) ... depmod: FATAL: could not load /boot/System.map-4.8.0-41-generic: No such file or directory run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.8.0-41-generic /boot/vmlinuz-4.8.0-41-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.8.0-41-generic /boot/vmlinuz-4.8.0-41-generic update-initramfs: Generating /boot/initrd.img-4.8.0-41-generic depmod: WARNING: could not open /lib/modules/4.8.0-41-generic/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/4.8.0-41-generic/modules.builtin: No such file or directory depmod: WARNING: could not open /vatmp/mkinitramfs_hMgmED/lib/modules/4.8.0-41-generic/modules.order: No such file or directory depmod: WARNING: could not open /vatmp/mkinitramfs_hMgmED/lib/modules/4.8.0-41-generic/modules.builtin: No such file or directory gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-4.8.0-41-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-4.8.0-41-generic (--remove): subprocess installed post-removal script returned error exit status 1 Removing linux-image-extra-4.8.0-44-generic (4.8.0-44.47) ... depmod: FATAL: could not load /boot/System.map-4.8.0-44-generic: No such file or directory run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.8.0-44-generic /boot/vmlinuz-4.8.0-44-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.8.0-44-generic /boot/vmlinuz-4.8.0-44-generic update-initramfs: Generating /boot/initrd.img-4.8.0-44-generic depmod: WARNING: could not open /lib/modules/4.8.0-44-generic/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/4.8.0-44-generic/modules.builtin: No such file or directory depmod: WARNING: could not open /vatmp/mkinitramfs_H5VNpA/lib/modules/4.8.0-44-generic/modules.order: No such file or directory depmod: WARNING: could not open /vatmp/mkinitramfs_H5VNpA/lib/modules/4.8.0-44-generic/modules.builtin: No such file or directory gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-4.8.0-44-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-4.8.0-44-generic (--remove): subprocess installed post-removal script returned error exit status 1 Removing linux-image-extra-4.8.0-45-generic (4.8.0-45.48) ... depmod: FATAL: could not load /boot/System.map-4.8.0-45-generic: No such file or directory run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.8.0-45-generic /boot/vmlinuz-4.8.0-45-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.8.0-45-generic /boot/vmlinuz-4.8.0-45-generic update-initramfs: Generating /boot/initrd.img-4.8.0-45-generic depmod: WARNING: could not open /lib/modules/4.8.0-45-generic/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/4.8.0-45-generic/modules.builtin: No such file or directory depmod: WARNING: could not open /vatmp/mkinitramfs_7CaoZU/lib/modules/4.8.0-45-generic/modules.order: No such file or directory depmod: WARNING: could not open /vatmp/mkinitramfs_7CaoZU/lib/modules/4.8.0-45-generic/modules.builtin: No such file or directory gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-4.8.0-45-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-4.8.0-45-generic (--remove): subprocess installed post-removal script returned error exit status 1 Removing linux-signed-image-4.8.0-41-generic (4.8.0-41.44) ... Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-4.8.0-39-generic Found linux image: /boot/vmlinuz-4.8.0-37-generic Found linux image: /boot/vmlinuz-4.8.0-34-generic Found initrd image: /boot/initrd.img-4.8.0-34-generic Found linux image: /boot/vmlinuz-4.8.0-32-generic Found initrd image: /boot/initrd.img-4.8.0-32-generic Found linux image: /boot/vmlinuz-4.8.0-30-generic Found initrd image: /boot/initrd.img-4.8.0-30-generic Found linux image: /boot/vmlinuz-4.8.0-28-generic Found initrd image: /boot/initrd.img-4.8.0-28-generic Found linux image: /boot/vmlinuz-4.8.0-27-generic Found initrd image: /boot/initrd.img-4.8.0-27-generic Found linux image: /boot/vmlinuz-4.8.0-26-generic Found initrd image: /boot/initrd.img-4.8.0-26-generic Found linux image: /boot/vmlinuz-4.4.0-43-generic Found initrd image: /boot/initrd.img-4.4.0-43-generic Adding boot menu entry for EFI firmware configuration done Removing linux-signed-image-4.8.0-44-generic (4.8.0-44.47) ... Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-4.8.0-39-generic Found linux image: /boot/vmlinuz-4.8.0-37-generic Found linux image: /boot/vmlinuz-4.8.0-34-generic Found initrd image: /boot/initrd.img-4.8.0-34-generic Found linux image: /boot/vmlinuz-4.8.0-32-generic Found initrd image: /boot/initrd.img-4.8.0-32-generic Found linux image: /boot/vmlinuz-4.8.0-30-generic Found initrd image: /boot/initrd.img-4.8.0-30-generic Found linux image: /boot/vmlinuz-4.8.0-28-generic Found initrd image: /boot/initrd.img-4.8.0-28-generic Found linux image: /boot/vmlinuz-4.8.0-27-generic Found initrd image: /boot/initrd.img-4.8.0-27-generic Found linux image: /boot/vmlinuz-4.8.0-26-generic Found initrd image: /boot/initrd.img-4.8.0-26-generic Found linux image: /boot/vmlinuz-4.4.0-43-generic Found initrd image: /boot/initrd.img-4.4.0-43-generic Adding boot menu entry for EFI firmware configuration done Removing linux-signed-image-4.8.0-45-generic (4.8.0-45.48) ... Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-4.8.0-39-generic Found linux image: /boot/vmlinuz-4.8.0-37-generic Found linux image: /boot/vmlinuz-4.8.0-34-generic Found initrd image: /boot/initrd.img-4.8.0-34-generic Found linux image: /boot/vmlinuz-4.8.0-32-generic Found initrd image: /boot/initrd.img-4.8.0-32-generic Found linux image: /boot/vmlinuz-4.8.0-30-generic Found initrd image: /boot/initrd.img-4.8.0-30-generic Found linux image: /boot/vmlinuz-4.8.0-28-generic Found initrd image: /boot/initrd.img-4.8.0-28-generic Found linux image: /boot/vmlinuz-4.8.0-27-generic Found initrd image: /boot/initrd.img-4.8.0-27-generic Found linux image: /boot/vmlinuz-4.8.0-26-generic Found initrd image: /boot/initrd.img-4.8.0-26-generic Found linux image: /boot/vmlinuz-4.4.0-43-generic Found initrd image: /boot/initrd.img-4.4.0-43-generic Adding boot menu entry for EFI firmware configuration done Errors were encountered while processing: linux-image-extra-4.8.0-41-generic linux-image-extra-4.8.0-44-generic linux-image-extra-4.8.0-45-generic E: Sub-process /usbin/dpkg returned an error code (1) 
submitted by chairs_on_wheels to linux4noobs [link] [comments]

NEON & Web Wallet: I wish it had a password as well, which would be needed for sending & 12 word passphrase. And seed generation TIPS

I'm on Linux which is good but I did get hacked via Teamviewer once and actually saw the person on my PC. I had recycled a password in the dim and distant past from the linkedin hack...
What saved me even if I hadn't been in the office was 2FA on all my accounts.
However as far as I know the official Neo Web Wallet @ https://neowallet.cn/ allows you to send without re-entering your password like say electron. The Neon wallet definitively does not prompt you from the private key.
In these situations I use kde-connect to secure over from phone to pc clipboard my deterministic passwords etc
What would be cool for both wallets is allow you to enter either a 12 word passphrase which you could generate in electrum for example OR your private key.
You can for example user electrum to generate your 12 word passphrase and use one of the private keys generated from your addresses as a Neo/Neon private key.
Or you can even use electrum to firstly generate your passphrase
electrum make_seed --entropy=193862769152946304546066490817889639328
useless welcome frame safe door scrap lock swear frame height hotel endless depth
This is a thirteen word pass phrase, more entropy actually doesn't make a difference according to Thomas Vögtlin.
So if you remove a few of the decimal numbers at the end of that string you can be a 12 word pass phrase if you want.
##### Full notes to seed generation from dice #########'
So working backwards and starting at the top, here is how I do it:
http://www.swansontec.com/bitcoin-dice.html Download Dice to Key https://github.com/swansontec/dice2key
wget -O dice2key.zip https://github.com/swansontec/dice2key/archive/master.zip unzip dice2key.zip
./dice2key.sh 123456123456123456123456123456123456123456123456123 51 dice rolls – the dice2key software will now warn you it’s not 100, but we’re not using it for the actual key, just the entropy, but more than 51 rolls in Electrum v2.4 creates a seed phrase greater than 13 words.
Next we need the number for Electrum as a decimal, which we can do from the command line:
echo "ibase=16; 91D89C79009852800BFFCCDC406B1BA0"|bc
We should get something like this
193862769152946304546066490817889639328
Go to the command line, NOT the console within electrum and run
electrum make_seed --entropy=193862769152946304546066490817889639328
It will generate a SEED PHRASE with thirteen words like:
useless welcome frame safe door scrap lock swear frame height hotel endless depth
Then you can run standard electrum - new it in as a new wallet, paste in the pass phrase from the process above.
Go to "View"->"addresses"
Pick a key pair and use the private key as you Neo / Neon private key.
Thus you could have generated your private key offline.
Step TWO - back up your private key. I use qreator for ubuntu etc
sudo add-apt-repository ppa:qreator-hackers/qreator-stable sudo apt update sudo apt install qreator python-qrencode
Then run "qreator" on the terminal and you can paste in your private key and it will generate a QR code which you can print and scan.
Step three On your internet connected ubuntu install zbarcam
sudo apt-get install zbar-tools sudo apt-get install libzbar0 libzbar-dev sudo apt-get install python-dev sudo pip install zbar
Application usage:
[email protected]:~$ zbarcam
zbarcam will then pick up your web cam and scan a QR code which you can paste into Neo/Neon
So now the exposure is only in your clipboard. I'm sure all this is possible on windows/mac
The best situation for Neo/Neon is if they were to create a cross-platform app which would scan the QR and inject it into their app via a secure channel. IE modified Neon which incorporated the zbarcam codebase so the scanned private key as QR code never hit the clipboard. It would also then require a rescan of the QR code to send assets.
Hope this is of some use to your all!
Cheers MX
submitted by m1bxd to NEO [link] [comments]

The Qtum Test Network has been RELEASED!

The Qtum Test Network Has Been Released:
https://github.com/qtumproject/qtum/releases/tag/testnet-sparknet
Instructions on how to compile from source are listed in the Git. Please see the documentation provided:
Quickstart Build on Ubuntu This is a quick start script for compiling Qtum on Ubuntu sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils git cmake libboost-all-dev sudo apt-get install software-properties-common sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev # If you want to build the Qt GUI: sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler git clone https://github.com/qtumproject/qtum cd qtum # Update cpp-ethereum submodule git submodule update --init --recursive # Note autogen will prompt to install some more dependencies if needed ./autogen.sh ./configure make -j2 
If you would like to receive Test Network tokens, please PM this account with your address and we will get them sent ASAP. These test tokens will have no value, so you are free to share them with others for testing. We will have a faucet set up shortly, along with a Win64 QT shortly.
Right now the team is preparing for our launch event in Shanghai, so it may be a touch busy on our side for the next day.
Visit the Qtum Website: https://qtum.org/en/ Join the Qtum Slack: https://qtumslack.herokuapp.com/
submitted by Vindyne8 to altcoin [link] [comments]

The Qtum Test Network has been RELEASED!

The Qtum Test Network Has Been Released:
https://github.com/qtumproject/qtum/releases/tag/testnet-sparknet
Instructions on how to compile from source are listed in the Git. Please see the documentation provided:
Quickstart Build on Ubuntu This is a quick start script for compiling Qtum on Ubuntu sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils git cmake libboost-all-dev sudo apt-get install software-properties-common sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev # If you want to build the Qt GUI: sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler git clone https://github.com/qtumproject/qtum cd qtum # Update cpp-ethereum submodule git submodule update --init --recursive # Note autogen will prompt to install some more dependencies if needed ./autogen.sh ./configure make -j2 
If you would like to receive Test Network tokens, please PM this account with your address and we will get them sent ASAP. These test tokens will have no value, so you are free to share them with others for testing. We will have a faucet set up shortly, along with a Win64 QT shortly.
Right now the team is preparing for our launch event in Shanghai, so it may be a touch busy on our side for the next day.
Visit the Qtum Website: https://qtum.org/en/ Join the Qtum Slack: https://qtumslack.herokuapp.com/
submitted by Vindyne8 to CryptoCurrency [link] [comments]

The Qtum Test Network has been RELEASED!

The Qtum Test Network Has Been Released:
https://github.com/qtumproject/qtum/releases/tag/testnet-sparknet
Instructions on how to compile from source are listed in the Git. Please see the documentation provided:
Quickstart Build on Ubuntu This is a quick start script for compiling Qtum on Ubuntu sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils git cmake libboost-all-dev sudo apt-get install software-properties-common sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev # If you want to build the Qt GUI: sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler git clone https://github.com/qtumproject/qtum cd qtum # Update cpp-ethereum submodule git submodule update --init --recursive # Note autogen will prompt to install some more dependencies if needed ./autogen.sh ./configure make -j2 
If you would like to receive Test Network tokens, please PM this account with your address and we will get them sent ASAP. These test tokens will have no value, so you are free to share them with others for testing. We will have a faucet set up shortly, along with a Win64 QT shortly.
Right now the team is preparing for our launch event in Shanghai, so it may be a touch busy on our side for the next day.
Visit the Qtum Website: https://qtum.org/en/ Join the Qtum Slack: https://qtumslack.herokuapp.com/
submitted by Vindyne8 to BitcoinAll [link] [comments]

4. Installing Bitcoin Core on Linux How to install Bitcoin on Ubuntu 16.04 Installing Ubuntu Builder On Ubuntu 12.04 Working with Ubuntu PPAs How to install Y-PPA-Manager on Ubuntu

One of the benefits of using Ubuntu is the wide availability of a range of third party repositories. These repositories or PPAs are really useful to install packages not available in official Ubuntu repositories or to upgrade existing packages to newer versions. What is a PPA? A “Personal Package Archive” or a PPA is an […] This refreshes all of the software sources for Ubuntu and will allow it to see the new Bitcoin PPA we’ve just added. sudo apt update. After refreshing the software updates, it’s important to use the upgrade tool to install any pending Ubuntu updates. Do this to ensure that your Bitcoin Core wallet will install on the system correctly. BitTicker is a live bitcoin-USDT Ticker for Ubuntu. It is a simple tool that connects to bittrex.com market and retrieves the latest price for BTC-USDT and display Ubuntu clock on system tray. It is simple but very useful too if you invest in Bitcoin regularly and have to study price fluctuations regulary. 89. Organize My Files sudo apt-add-repository ppa:bitcoin/bitcoin This will add the bitcoin package repository. You may be greeted with the following message: Stable Channel of bitcoin-qt and bitcoind for Ubuntu, and their dependencies Note that you should prefer to use the official binaries, where possible, to limit trust in Launchpad/the PPA owner. So I did a bit more research and somehow realized that I probably need to have the Cuda drivers installed, as they are pretty much essential for Bitcoin mining with nVidia GPUs. Opened the Apps -> Terminal again, and then run the following: sudo add-apt-repository ppa:graphics-drivers/ppa. sudo apt update. sudo ubuntu-drivers autoinstall. reboot

[index] [4142] [26474] [17640] [20003] [6984] [8098] [23444] [12156] [11318] [17962]

4. Installing Bitcoin Core on Linux

This video explains the installation of Y PPA Manager on Ubuntu. Y PPA Manager is a tool used for adding, removing, purging PPAs easier, or even for searching the packages in all the Launchpad ... Aptik - A Backup Tool For Packages & PPAs in Linux Mint: ( Ubuntu) Installation of Aptik: sudo apt-add-repository ppa:teejee2008/ppa sudo apt-get update sudo apt-get install aptik ... 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/bitcoin sudo apt-get update “sudo apt ... Y PPA Manager is a powerful PPA Manager tool. It features “Add PPA”, “Remove PPA” and “Purge PPA.” It can also be used to search all the available PPAs installed on the system. sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install bitcoin-qt bitcoind Linux terminal new stuff: clear, ll, cd, touch, echo, cat, shutdown www.bitcoinhackers.org

#