PhoenixMiner 5.1c: fastest Ethereum/Ethash miner with ...

Big Star Trek fan, looking for a seedbox + plex server to handle 10 HD streams to my fellow trekkers. 🖖

Are you OK with direct message offers from vendors?
No, thank you.
What are your main reasons for getting a seedbox?
  1. Reliable Plex streaming of 10 HD concurrent streams to my friends (1080p preferred, but 720p is acceptable)
  2. Faster downloads to sync one-way with my large at home (30TB, Synology 1019+)
  3. Use xTeve (and IPTV proxy for Plex) through a VPN. (Mullvad)
Do you have any specific requirements?
I would like to put all xTeve traffic through a VPN specifically, but I'm fine with putting all traffic through a VPN.
Are you looking for a shared or dedicated solution?
I'm not sure. Whichever suits my purposes best.
Are you looking for managed or unmanaged solution?
Managed. I'm a relative newbie and would much prefer a GUI over a command line.
Please describe your Seedbox experience:
I used Bytesize hosting once, but that was a very long time ago (>3 years)
Currently with a provider or used one before?
No provider right now.
What is your Linux experience?
I've used Ubuntu and have done some command line work (navigating folders, basic commands, copy/pasting from the web) in both Ubuntu, DSM from my Synology NAS, and on my mac. But again, I prefer a GUI whenever possible.
What is your monthly budget?
$50-70/month
Payment preferences or requirements?
Bitcoin preferred.
Do you need support for public trackers?
Yes, but they're the only ones I know about. I'm open to learning about others.
Routing: Tell us your continent:
North America
What kind of connection speeds do you need?
This is where I'm unsure. I have a group of friends, some of which are pretty old school, with whom I'm trying to organize a watch party (using Plex's new Watch Together feature) so I need a pretty fast connection for them to all be happy with at least 720p and not get frustrated with trying this out.
How much monthly bandwidth is needed?
Aside from 10 concurrent streams of one movie once per week, there will only be about 5 occasional users at most.
How much disk space do you need?
If there is a clever way for the seedbox to sync data one-way to my NAS at home at reasonably high speeds, (I get about 500MBit down from fast.com at home) I would need about 1TB, maybe 2TB for the Star Trek canon.
List some features you are looking for:
GUI. Reliably, speedy Plex streaming to North America. Privacy focussed.
Anything else you think we should know?
I really appreciate you for reading my ramblings, and thanks for your help. 🖖
submitted by DailiesKaven to seedboxes [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]

Dogecoin on Linux - The Complete Beginner's Guide

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

How to Mine BiblePay on Windows

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/
Windows Guide: 1. Download 32 or 64 bit .exe from https://www.biblepay.org/wallet/ 2. Double Click / Run .exe file and step through Install process 3. Run BiblePay 4. Click Tools >> One Click Mining, (Or set up mining manually with steps a through d below)
     a. Open File Explorer, in address bar type: %appdata%      b. Press Enter      c. Go to BiblepayEvolution folder      d. Open biblepay.conf file for editing, add lines and Save
addnode=node.biblepay.org gen=1 genproclimit=1 
NOTE: addnode is used to give the wallet a starting node to connect to and sync with gen=1 turns on mining by default when the wallet is opened genproclimit=1 sets number of mining threads to 1 by default

5. Close BiblePay and Run it again 6. In BiblePay, go to Tools menu, Click Debug Console 7. Type these commands into the debug console:
getinfo getmininginfo help 
NOTE: getinfo will show you what block number your wallet is currently on and the version number getmininginfo will show you how many threads are running and how much mining hash you have help will show you all the other commands you can use

Threads: 8. To change number of threads to use up for mining
a. Edit %appdata%/BiblepayEvolution/biblepay.conf file: Find with File Explorer or inside the wallet go to Menu >> Tools >> Open Wallet Configuration File
genproclimit=X 
and restart BiblePay -or- b. Menu >> Tools >> Debug Console >> Type command:
setgenerate true X 
(Replace X with the number of threads you want to use Open Task Manager to view CPU usage)

Using the 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 (NOTE: Your Worker Username needs to be unique)
  3. Enable pool and add Worker Username in %appdata%/BiblepayEvolution/biblepay.conf file, add these lines:
    pool=https://pool.biblepay.org workerid=insertWorkerUsernameHere
4. Restart BiblePay
How to Withdraw Coins From Pool? The pool holds onto your coins, go to "Account" >> "Withdraw" to withdraw your coins In your BiblePay Wallet go to "File" >> "Receiving Address" and you can right click and copy the address and paste it into the Pool's Withdraw screen as the "Destination Address", then click the "Withdraw" button and the coins will be sent from the Pool to your Wallet
Setup Auto-Withdraw Navigate to Account >>> Account Settings >>> Verify your BBP Receiving Address >>> Click Authorize-Auto-Withdraws
Why use a Pool? As the network hash rises (as more miners are mining), it can take longer and longer to solve a block, by using the pool, everyone works together with all of their hash power to solve blocks, and the reward gets split between everyone who contributed based on how much they contributed in hash.
With solo mining (not using the pool) it may take 1 month to finally solve a block and get large BBP reward, with pool you can get small frequent BBP rewards every ~30 minutes. (BBP meaning BiblePay coins)

How to Update: Download exe from biblepay.org and install again, your wallet will stay intact

Backup:
Your wallet.dat stores your private keys that contain the access to your coins, this file is backed up every 24 hours in the backups folder, We also recommend that you save a copy of this file in other places, like a flash drive
Learn More about Backing Up your Wallet.dat https://www.reddit.com/BiblePay/comments/7lksp4/backup_walletdat/

FAQ
QUESTION: How long does it take for coins to mature? If you're solo mining, the coins become mature after ~100 blocks. If you're using the pool, they become mature after 24 hours
QUESTION: How do I know if I am currently mining? In your wallet >> In Top left Menu select "Tools" >> Click "Debug Console" Type in the command: getgenerate If it returns true, mining is turned on command: getmininginfo Will show how much "hashps" (hashing) your pc is doing, "genproclimit" will show how many mining threads you are using "poolmining" will be show value of true if you are successfully mining on the pool

How to Buy or Sell BBP coins?
You can buy and sell BBP coins for Bitcoin on the Exchanges we are listed on: SouthXChange: https://www.southxchange.com/Market/Book/BBP/BTC CoinExchange.io: https://www.coinexchange.io/market/BBP/BTC

Misc: Building headless Bitcoin and Bitcoin-qt on Windows https://bitcointalk.org/index.php?topic=149479.0 https://msdn.microsoft.com/en-us/commandline/wsl/install_guide https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux https://bitcointalk.org/index.php?topic=2388064.msg27133702#msg27133702 https://github.com/OleEichhorn/bitcoin-msvc

OUTDATED
Windows Mining Video Tutorial by copper101great https://www.youtube.com/watch?v=K1yKx8KsH60
submitted by togoshige to BiblePay [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]

How To: Manually Set The Fan Speed Of Your Bitmain Antminer S9

Do this at your own risk! I'm very new to bitcoin mining, this is my first miner, an Antminer S9 14TH/s version(manufacture date October 2017), and I was getting very annoyed with the fans constantly going up and down, hours of research led me to the following solution. With that said I have extensive experience as a system/network administrator, so this wasn't foreign to me, but I'll try and keep this as simple as possible.
You will need to download Putty and ssh to the IP of your miner. Once there log in using root as the username and the password you've set up, I believe the default is also root. Once you're logged in you are now at a Linux prompt, with access to the file system inside your miner. Use the following steps to set the fan speed manually.

cd /config

chmod 755 bmminer.conf

vi bmminer.conf

You are now in the vi editor, you should see the entire contents of the bmminer.conf file on your screen, expand the window if you need to. For instructions on using the Vi editor please see the great write-up at the link below. Note you can't change the file until you write it, so don't worry about keystrokes or messing up, just don't write until you're done! http://www.control-escape.com/linux/editing-vim.html
To do this move the cursor down with the arrow keys, navigate to the begining of the line that reads "bitmain-use-vil", click i, this puts you in edit mode, hit enter to add a blank line, click up to position your cursor in the blank line you just created, copy the above two lines, right click to paste them into the config file.
Your config file should now look like the following image. https://imgur.com/a/bkg5F
With the number being the percentage you'd like the fans to run at. NOTICE I do not know what will happen if you overheat your Antminer, I believe there are automatic shutdown protections, but do this at your own risk! I HIGHLY SUGGEST setting this number to 100 to start and lowering it until you find the right spot, I'm told the cutoff temp for the S9 is 115C, and up to 100C is alright, I've been trying to keep mine around 80C though. You can monitor the temps from your web browser at http://IP.Of.Your.Minecgi-bin/minerStatus.cgi and putty into it at the same time, watch the temps and make changes, use the reboot feature in the gui/browser to make the changes apply. Notice the S9 appears to take 5-10min to come online.
Now write the file and exit vi by hitting [Esc] twice and then typing:

:wq

You can view the file to make sure the changes took by typing:

vi bmminer.conf

If it looks good exit by typing:

:q

You'll need to restart the miner for the change to take effect, you can do this via the gui/browser. If your miner will possibly overheat type 'poweroff' from your ssh connection and give it a few minutes before restarting. Currently I'm running at 80% fan and it's keeping my boards at or below 80 degrees in a room with ambient temp of 65-70. Probably going to bump it up to 85% for peace of mind.
Donations welcome BTC: 1Mari5pDGTF4nb4isqzwAbVXW4VsN648ve

Credit to u/qwerty4ever for getting me started on this, I've learned a lot about Linux on this adventure!

submitted by Gunlex to Bitcoin [link] [comments]

Simplified explanation for setting up a UASF Full Node on your Raspberry Pi 3.

I decided to undertake an effort to run a full node on my Raspberry Pi. I followed this tutorial, but still found it was too detailed/complicated, so I reduced it down to the basic steps needed to make it happen.
This tutorial will install the UASF binaries to enforce BIP148 on August 1st. Don't be fooled thinking that the recent Barry Silbert agreement has resolved the ongoing scaling issue. Activating Segwit is necessary and UASF is the way to make that happen. Your support is needed.
This tutorial assumes that you are running Raspian, your RaspPi has internet connectivity, you have an external USB hard drive connected formatted as FAT32 and your Linux username is "pi".
IMPORTANT: For your security, you should change your username to something different than "pi" (also choose a strong password. As you will see below, you should enable UPnP or port forward 8333 on your router to your Raspberry Pi, but this creates a security risk.
These instructions will install Bitcoin Core without wallet functionality.
Create a directory that will act as a mount point for the USB drive:
[email protected]~$ mkdir ~/bitcoinData 
With your USB drive connected, run this command to confirm that your drive is recognized as /dev/sd1:
[email protected]~$ sudo blkid 
In order to tell your Raspberry Pi to mount your USB drive automatically so that anything we put in the bitcoinData directory will be going onto the USB drive we need to edit the /etc/fstab file:
[email protected]~$ sudo nano /etc/fstab 
Add the following line to the fstab file. The following assumes that the drive was /dev/sd1:
/dev/sda1 /home/pi/bitcoinData vfat uid=pi,gid=pi,umask=0022,sync,auto,nosuid,rw,nouser 0 0 
Save the fstab file and reboot. When re-started, navigate with the File Manager to /home/pi/bitcoinData and make sure the folder size corresponds to the approximate size of your external drive. This is important, otherwise, the blockchain will be saved to the micro SD card. Unless your card is 256GB, it won't fit.
Enlarge the swap file, by editing the dphys-swapfile:
[email protected]~/bin/bitcoin$ sudo nano /etc/dphys-swapfile 
Change "CONF_SWAPSIZE=100" to "CONF_SWAPSIZE=1000". Save the file, then exit. Now run:
[email protected]~$ sudo dphys-swapfile setup [email protected]~$ sudo dphys-swapfile swapon 
Update your Raspbian:
[email protected]~$ sudo apt-get update [email protected]~$ sudo apt-get upgrade -y 
Install some packages:
[email protected]~$ sudo apt-get install autoconf libevent-dev libtool libssl-dev libboost-all-dev libminiupnpc-dev -y [email protected]~$ sudo apt-get install qt4-dev-tools libprotobuf-dev protobuf-compiler libqrencode-dev -y 
Make a directory and change to that directory:
[email protected]~$ mkdir ~/bin [email protected]~$ cd ~/bin 
Install Bitcoin:
[email protected]~/bin$ git clone https://github.com/UASF/bitcoin.git -b 0.14-BIP148 [email protected]~/bin$ cd bitcoin/ [email protected]~/bin/bitcoin$ ./autogen.sh [email protected]~/bin/bitcoin$ ./configure --enable-upnp-default --disable-wallet [email protected]~/bin/bitcoin$ make -j2 
It will take about 2 hours for the "make -j2" to finish. Once done, run:
[email protected]~/bin/bitcoin$ sudo make install 
Now, create a bitcoin.conf file:
[email protected]~/bin/bitcoin$ cd ~/bitcoinData [email protected]~/bitcoinData$ nano bitcoin.conf 
Let's run this bad boy:
[email protected]~$ bitcoin-qt 
On the first start, choose the blockchain data directory as "/home/pi/bitcoinData". Expect that it will take 2 to 3 weeks to fully sync the blockchain.
The step that includes "enable-upnp-default" is intended to open the necessary port (8333) in your router. Either way, you may want to consider port-forwarding port 8333 to your Pi.
You should now go to https://bitnodes.21.co/ and click the ‘CHECK NODE’ button to see how your node appears to other nodes on the network. This is important as it lets your node contribute to the network and adds to the UASF support on node statistics.
Enjoy!
submitted by iftodaywasurlastday to Bitcoin [link] [comments]

05-07 20:52 - 'How to check if your Electrum Wallet is legit before using. (For Linux)' (self.Bitcoin) by /u/ayanamirs removed from /r/Bitcoin within 41-51min

'''
Go to Electrum [website]1 , click on [download]2 , then click on ThomasV, this will redirect you to the MIT website, click on a 7F9470E6, this will redirect you to ThomasV public key, select all and save it as ThomasV.asc.
[[link]4
Go back to Electrum website and download Electrum-3.1.3.tar.gz and its signature Electrum-3.1.3.tar.gz.asc
Copy all the 3 files to the same folder, open the terminal and use command 'cd' to navigate to that folder and run these commands.
gpg --import ThomasV.asc
gpg --verify Electrum-3.1.3.tar.gz.asc Electrum-3.1.3.tar.gz
If the message returned says Good signature and that it was signed by ThomasV with a fingerprint that ends with 7F9470E6, then the software is authentic.
'''
How to check if your Electrum Wallet is legit before using. (For Linux)
Go1dfish undelete link
unreddit undelete link
Author: ayanamirs
1: elect*um.*rg/**ome 2: ele*t*um.o*g/#do**loa* 3: *gp.mi*.edu/pk**lookup*****in*ex&s**r*h=*x2BD58*4B7F94*0E6 4: pgp.mit.*du*pks/loo*u*?**=v*ndex&am*;searc**0x2B*5*24B*F*470E*]^^*
Unknown links are censored to prevent spreading illicit content.
submitted by removalbot to removalbot [link] [comments]

Simplified explanation for setting up a UASF Full Node on your Raspberry Pi 3.

I decided to undertake an effort to run a full node on my Raspberry Pi. I followed this tutorial, but still found it was too detailed/complicated, so I reduced it down to the basic steps needed to make it happen.
This tutorial will install the UASF 1.0 binaries to enforce BIP148 on August 1st.
This tutorial assumes that you are running Raspian, your RaspPi has internet connectivity, you have an external USB hard drive connected formatted as FAT32 and your Linux username is "pi".
IMPORTANT: For your security, you should change your username to something different than "pi" (also choose a strong password. As you will see below, you should enable UPnP or port forward 8333 on your router to your Raspberry Pi, but this creates a security risk.
These instructions will install Bitcoin Core without wallet functionality.
Create a directory that will act as a mount point for the USB drive:
[email protected]~$ mkdir ~/bitcoinData 
With your USB drive connected, run this command to confirm that your drive is recognized as /dev/sd1:
[email protected]~$ sudo blkid 
In order to tell your Raspberry Pi to mount your USB drive automatically so that anything we put in the bitcoinData directory will be going onto the USB drive we need to edit the /etc/fstab file:
[email protected]~$ sudo nano /etc/fstab 
Add the following line to the fstab file. The following assumes that the drive was /dev/sd1: /dev/sda1 /home/pi/bitcoinData vfat uid=pi,gid=pi,umask=0022,sync,auto,nosuid,rw,nouser 0 0 Save the fstab file and reboot.
When re-started, navigate with the File Manager to /home/pi/bitcoinData and make sure the folder size corresponds to the approximate size of your external drive. This is important, otherwise, the blockchain will be saved to the micro SD card. Unless your card is 256GB, it won't fit.
Enlarge the swap file, by editing the dphys-swapfile:
[email protected]~/bin/bitcoin$ sudo nano /etc/dphys-swapfile 
Change "CONF_SWAPSIZE=100" to "CONF_SWAPSIZE=1000". Save the file, then exit. Now run:
[email protected]~$ sudo dphys-swapfile setup [email protected]~$ sudo dphys-swapfile swapon 
Update your Raspbian:
[email protected]~$ sudo apt-get update [email protected]~$ sudo apt-get upgrade -y 
Install some packages:
[email protected]~$ sudo apt-get install autoconf libevent-dev libtool libssl-dev libboost-all-dev libminiupnpc-dev -y [email protected]~$ sudo apt-get install qt4-dev-tools libprotobuf-dev protobuf-compiler libqrencode-dev -y 
Make a directory and change to that directory:
[email protected]~$ mkdir ~/bin [email protected]~$ cd ~/bin 
Install Bitcoin:
[email protected]~/bin$ git clone https://github.com/UASF/bitcoin.git bitcoin [email protected]~/bin$ cd bitcoin/ [email protected]~/bin/bitcoin$ ./autogen.sh [email protected]~/bin/bitcoin$ ./configure --enable-upnp-default --disable-wallet [email protected]~/bin/bitcoin$ make -j2 
It will take about 2 hours for the "make -j2" to finish. Once done, run:
[email protected]~/bin/bitcoin$ sudo make install 
Now, create a bitcoin.conf file:
[email protected]~/bin/bitcoin$ cd ~/bitcoinData [email protected]~/bitcoinData$ nano bitcoin.conf 
Let's run this bad boy:
[email protected]~$ bitcoin-qt 
On the first start, choose the blockchain data directory as "/home/pi/bitcoinData". Expect that it will take 2 to 3 weeks to fully sync the blockchain.
The step that includes "enable-upnp-default" is intended to open the necessary port (8333) in your router. Either way, you may want to consider port-forwarding port 8333 to your Pi.
You should now go to https://bitnodes.21.co/ and click the ‘CHECK NODE’ button to see how your node appears to other nodes on the network. This is important as it lets your node contribute to the network and adds to the UASF support on node statistics.
Enjoy!
submitted by iftodaywasurlastday to Bitcoin [link] [comments]

$5 in Bitcoin to whoever can help me figure this program out.

Okay I am trying to configure and run this program. https://pypi.python.org/pypi/rss2email/
I can use Linux (ubuntu 14.04) or windows 7. I would prefer that you PM me and we will skype or something similar as I share my screen with you.
Someone gave me $5 in bitcoin a few weeks ago and I will gladly give it to anyone who gets this working with me.
Edit: here is my changetip account
Edit2: archived the discussion.
ubuntu
pip install feedparser html2text wget https://github.com/wking/rss2email/archive/v3.9.tar.gz tar -xvf rss2email*.tar.gz cd rss2email* python setup.py install cd .. rm -rf rss2email* r2e new youremailaddyhere editor $XDG_CONFIG_HOME/rss2email.cfs 
at this point, grab the info from https://support.google.com/a/answe176600?hl=en
using the restricted settings if you are only using a low volume feed, otherwise use the normal Gmail SMTP server settings
then slap 0 * * * * r2e run into your crontab -e and everything should be done
Having a problem with line 8. Here is my console. (Throwaway email by the way) https://i.imgur.com/Mrnu2vP.png
and the /owl/ dir is just some random folder to keep this all in one place.
pip install html2text worked, yes?
It did/does this
https://i.imgur.com/xaIdrz6.png
your pip is installing to python2.7, your r2e is installing to your python3.4
do pip-3.4 install html2text feedparser
then you should be able to run r2e
(thanks so much so far) Okay now I have problems with #9. It goes into a blank screen. https://i.imgur.com/m31O9p7.png
Edit: by the way I had to use
$ pip3 install html2text feedparser 
hm, ctrl+x out of that, try nano ~/.config/rss2email.cfs ?
Weird. I tried nano and vim but they both don't work. What should I check out?
... that is really weird, anyways, just use editor then, nano's controls are: Ctrl+O,Enter to save, Ctrl+X to exit
the package is just apt-get install nano, but considering how your putty renders it, either something is going weird with putty or your ubu install
I wen't over to my actual ubuntu desktop and tried again but the same thing came up. Should I manually navigate to the file you are talking about and see what I find? Where would that be?
Edit: Here is a screenshot. https://i.imgur.com/3GiRTUe.png
you basically just need to edit the settings in the file so it can use the google servers to send emails
What is the path of the file I need to edit? I can manually get there via desktop interface.
home folder, from there, .config/, then the file should be there
nothing to do with the owl folder, in other words
You're not looking for this are you? https://i.imgur.com/1lewL2F.png
no, run ls -1a in ~, .config should be a hidden folder
I don't know what you mean by
in ~
But I did find this when I typed
ls -la
https://i.imgur.com/M9zev59.png
the .config folder is there, cd into it and ls -1a again?
Sorry.. How do I cd to it since its not a regular dir?
Oh I see.. Okay here is what i got.
https://i.imgur.com/PFtTk6I.png
then do editor rss2email.cfg
I don't think that is where I edit my smtp stuff. Here is what comes up. https://i.imgur.com/HSZB8TY.png
When/where do I edit the earlier screenshot? https://i.imgur.com/1lewL2F.png
you might need to tap page-down a couple times to see the rest of the config file
Okay I see. Will you check these settings so far? I have the email [email protected] getting the emails/rss feeds. And I have [email protected] sending the emails. The only thing left out of the actual text is the gmail login password for [email protected]. Once I change that to the correct password and save is it done correct?
Edit: removed imgur link with semi-private throwaway.
for the smtp-server, you would want to add 465 after the :
and having the from setting match the smtp-username would probably be a good idea
Okay I fixed both of those. Now when I run
.../owl/rss2email-3.9$ r2e run
I get this error: https://i.imgur.com/JWUpWmW.png
the only other thing I can suggest is switch to TLS port / config as opposed to SSL
past that, I probably can't be much more help at this point, sorry x-x
Hmm. How hard is it to set up the 'sendmail' it keeps talking about?
End of conversation
submitted by TheBird47 to learnpython [link] [comments]

Simplified explanation for setting up a Bitcoin 0.15 Full Node on your Raspberry Pi 3.

I decided to undertake an effort to run a full node on my Raspberry Pi. I followed this tutorial, but still found it was too detailed/complicated, so I reduced it down to the basic steps needed to make it happen.
This tutorial assumes that you are running Raspian, your RaspPi has internet connectivity, you have an external USB hard drive connected formatted as FAT32 and your Linux username is "pi".
IMPORTANT: For your security, you should change your username to something different than "pi" (also choose a strong password. As you will see below, you should enable UPnP or port forward 8333 on your router to your Raspberry Pi, but this creates a security risk.
These instructions will install Bitcoin Core without wallet functionality.
Create a directory that will act as a mount point for the USB drive:
[email protected]~$ mkdir ~/bitcoinData 
With your USB drive connected, run this command to confirm that your drive is recognized as /dev/sd1:
[email protected]~$ sudo blkid 
In order to tell your Raspberry Pi to mount your USB drive automatically so that anything we put in the bitcoinData directory will be going onto the USB drive we need to edit the /etc/fstab file:
[email protected]~$ sudo nano /etc/fstab 
Add the following line to the fstab file. The following assumes that the drive was /dev/sd1:
/dev/sda1 /home/pi/bitcoinData vfat uid=pi,gid=pi,umask=0022,sync,auto,nosuid,rw,nouser 0 0 
Save the fstab file and reboot.
When re-started, navigate with the File Manager to /home/pi/bitcoinData and make sure the folder size corresponds to the approximate size of your external drive. This is important, otherwise, the blockchain will be saved to the micro SD card. Unless your card is 256GB, it won't fit.
Enlarge the swap file, by editing the dphys-swapfile:
[email protected]~/bin/bitcoin$ sudo nano /etc/dphys-swapfile 
Change "CONF_SWAPSIZE=100" to "CONF_SWAPSIZE=1000". Save the file, then exit. Now run:
[email protected]~$ sudo dphys-swapfile setup [email protected]~$ sudo dphys-swapfile swapon 
Update your Raspbian:
[email protected]~$ sudo apt-get update [email protected]~$ sudo apt-get upgrade -y 
Install some packages:
[email protected]~$ sudo apt-get install autoconf libevent-dev libtool libssl-dev libboost-all-dev libminiupnpc-dev -y [email protected]~$ sudo apt-get install qt4-dev-tools libprotobuf-dev protobuf-compiler libqrencode-dev -y 
Make a directory and change to that directory:
[email protected]~$ mkdir ~/bin [email protected]~$ cd ~/bin 
Install Bitcoin:
[email protected]~/bin$ git clone https://github.com/bitcoin/bitcoin bitcoin [email protected]~/bin$ cd bitcoin/ [email protected]~/bin/bitcoin$ ./autogen.sh [email protected]~/bin/bitcoin$ ./configure --enable-upnp-default --disable-wallet [email protected]~/bin/bitcoin$ make -j2 
It will take about 2 hours for the "make -j2" to finish. Once done, run:
[email protected]~/bin/bitcoin$ sudo make install 
Now, create a bitcoin.conf file:
[email protected]~/bin/bitcoin$ cd ~/bitcoinData [email protected]~/bitcoinData$ nano bitcoin.conf 
Let's run this bad boy:
[email protected]~$ bitcoin-qt 
On the first start, choose the blockchain data directory as "/home/pi/bitcoinData". Expect that it will take 2 to 3 weeks to fully sync the blockchain.
The step that includes "enable-upnp-default" is intended to open the necessary port (8333) in your router. Either way, you may want to consider port-forwarding port 8333 to your Pi.
You should now go to https://bitnodes.21.co/ and click the ‘CHECK NODE’ button to see how your node appears to other nodes on the network. This is important as it lets your node contribute to the network and adds to the UASF support on node statistics.
Enjoy!
submitted by iftodaywasurlastday to Bitcoin [link] [comments]

Simplified version of installing Bitcoin Full Node on Raspberry Pi 3.

Hey. I'm a total Linux noob, but I decided to undertake an effort to run a full node on my Raspberry Pi. I followed this tutorial, but still found it was too detailed/complicated, so I reduced it down to the basic steps needed to make it happen. This tl;dr tutorial assumes that you are running Raspian, your RaspPi has internet connectivity, you have an external USB hard drive connected formatted as FAT32 and your Linux username is "pi". These instructions will install Bitcoin Core without wallet functionality.
Create a directory that will act as a mount point for the USB drive:
[email protected]~$ mkdir ~/bitcoinData 
With your USB drive connected, run this command to confirm that your drive is recognized as /dev/sd1:
[email protected]~$ sudo blkid 
In order to tell your Raspberry Pi to mount your USB drive automatically so that anything we put in the bitcoinData directory will be going onto the USB drive we need to edit the /etc/fstab file:
[email protected]~$ sudo nano /etc/fstab 
Add the following line to the fstab file. The following assumes that the drive was /dev/sd1:
/dev/sda1 /home/pi/bitcoinData vfat uid=pi,gid=pi,umask=0022,sync,auto,nosuid,rw,nouser 0 0 
Save the fstab file and reboot. When re-started, navigate with the File Manager to /home/pi/bitcoinData and make sure the folder size corresponds to the approximate size of your external drive. This is important, otherwise, the blockchain will be saved to the micro SD card. Unless your card is 256GB, it won't fit.
Enlarge the swap file, by editing the dphys-swapfile:
[email protected]~/bin/bitcoin$ sudo nano /etc/dphys-swapfile 
Change "CONF_SWAPSIZE=100" to "CONF_SWAPSIZE=1000". Save the file, then exit. Now run:
[email protected]aspnode~$ sudo dphys-swapfile setup [email protected]~$ sudo dphys-swapfile swapon 
Update your Raspbian:
[email protected]~$ sudo apt-get update [email protected]~$ sudo apt-get upgrade -y 
Install some packages:
[email protected]~$ sudo apt-get install autoconf libevent-dev libtool libssl-dev libboost-all-dev libminiupnpc-dev -y [email protected]~$ sudo apt-get install qt4-dev-tools libprotobuf-dev protobuf-compiler libqrencode-dev -y 
Make a directory and change to that directory:
[email protected]~$ mkdir ~/bin [email protected]~$ cd ~/bin 
Install Bitcoin:
[email protected]~/bin$ git clone -b 0.14 https://github.com/bitcoin/bitcoin.git [email protected]~/bin$ cd bitcoin/ [email protected]~/bin/bitcoin$ ./autogen.sh [email protected]~/bin/bitcoin$ ./configure --enable-upnp-default --disable-wallet [email protected]~/bin/bitcoin$ make -j2 
It will take about 2 hours for the "make -j2" to finish. Once done, run:
[email protected]~/bin/bitcoin$ sudo make install 
Now, create a bitcoin.conf file:
[email protected]~/bin/bitcoin$ cd ~/bitcoinData [email protected]~/bitcoinData$ nano bitcoin.conf 
Let's run this bad boy:
[email protected]~$ bitcoin-qt 
On the first start, choose the blockchain data directory as "/home/pi/bitcoinData". Expect that it will take 2 to 3 weeks to fully sync the blockchain.
The step that includes "enable-upnp-default" is intended to open the necessary port (8333) in your router. Either way, you may want to consider port-forwarding port 8333 to your Pi.
If you want to show your support for Segwit and BIP148, add the following to the bitcoin.conf file located in /home/pi/bitcoinData: uacomment=UASF-SegWit-BIP148
Enjoy!
submitted by iftodaywasurlastday to Bitcoin [link] [comments]

Simplified version of installing Bitcoin Full Node on Raspberry Pi 3.

Hey. I'm a total Linux noob, but I decided to undertake an effort to run a full node on my Raspberry Pi. I followed this tutorial, but still found it was too detailed/complicated, so I reduced it down to the basic steps needed to make it happen. This tl;dr tutorial assumes that you are running Raspian, your RaspPi has internet connectivity, you have an external USB hard drive connected formatted as FAT32 and your Linux username is "pi". These instructions will install Bitcoin Core without wallet functionality.
Create a directory that will act as a mount point for the USB drive:
[email protected]~$ mkdir ~/bitcoinData 
With your USB drive connected, run this command to confirm that your drive is recognized as /dev/sd1:
[email protected]~$ sudo blkid 
In order to tell your Raspberry Pi to mount your USB drive automatically so that anything we put in the bitcoinData directory will be going onto the USB drive we need to edit the /etc/fstab file:
[email protected]~$ sudo nano /etc/fstab 
Add the following line to the fstab file. The following assumes that the drive was /dev/sd1:
/dev/sda1 /home/pi/bitcoinData vfat uid=pi,gid=pi,umask=0022,sync,auto,nosuid,rw,nouser 0 0 
Save the fstab file and reboot. When re-started, navigate with the File Manager to /home/pi/bitcoinData and make sure the folder size corresponds to the approximate size of your external drive. This is important, otherwise, the blockchain will be saved to the micro SD card. Unless your card is 256GB, it won't fit.
Enlarge the swap file, by editing the dphys-swapfile:
[email protected]~/bin/bitcoin$ sudo nano /etc/dphys-swapfile 
Change "CONF_SWAPSIZE=100" to "CONF_SWAPSIZE=1000". Save the file, then exit. Now run:
[email protected]~$ sudo dphys-swapfile setup [email protected]~$ sudo dphys-swapfile swapon 
Update your Raspbian:
[email protected]~$ sudo apt-get update [email protected]~$ sudo apt-get upgrade -y 
Install some packages:
[email protected]~$ sudo apt-get install autoconf libevent-dev libtool libssl-dev libboost-all-dev libminiupnpc-dev -y [email protected]~$ sudo apt-get install qt4-dev-tools libprotobuf-dev protobuf-compiler libqrencode-dev -y 
Make a directory and change to that directory:
[email protected]~$ mkdir ~/bin [email protected]~$ cd ~/bin 
Install Bitcoin:
[email protected]~/bin$ git clone -b 0.14 https://github.com/bitcoin/bitcoin.git [email protected]~/bin$ cd bitcoin/ [email protected]~/bin/bitcoin$ ./autogen.sh [email protected]~/bin/bitcoin$ ./configure --enable-upnp-default --disable-wallet [email protected]~/bin/bitcoin$ make -j2 
It will take about 2 hours for the "make -j2" to finish. Once done, run:
[email protected]~/bin/bitcoin$ sudo make install 
Now, create a bitcoin.conf file:
[email protected]~/bin/bitcoin$ cd ~/bitcoinData [email protected]~/bitcoinData$ nano bitcoin.conf 
Let's run this bad boy:
[email protected]~$ bitcoin-qt 
On the first start, choose the blockchain data directory as "/home/pi/bitcoinData". Expect that it will take 2 to 3 weeks to fully sync the blockchain.
The step that includes "enable-upnp-default" is intended to open the necessary port (8333) in your router. Either way, you may want to consider port-forwarding port 8333 to your Pi.
If you want to show your support for Segwit and BIP148, add the following to the bitcoin.conf file located in /home/pi/bitcoinData: uacomment=UASF-SegWit-BIP148
Enjoy!
submitted by iftodaywasurlastday to Bitcoin [link] [comments]

Linux Terminal commands and navigation for Beginners ... Navigation in Linux - YouTube Linux Terminal commands and navigation for Beginners ... Bitcoin & Cryptocurrency Mining for Beginners: MinerGate for PC/Mac/Linux Bitcoin Live Btc Price Liquidation Watch: July 18 2020 ...

Added an HTML version of the documentation for better navigation and readability Other small improvements and fixes. Changes in version 4.8c: Added support for the latest AMD drivers under Linux 19.30-934563 and for mining with RX5700 cards under Linux. Note that drivers are quite buggy and most of the overclocking options don't work, as well as most of the hardware monitoring options. Added a ... Begin by renaming the Bitcoin Core data directory. Use the name bitcoin-backup. Don’t move the renamed folder. This allows recovery of the original data directory in case something goes wrong. To recover the original, reinstate the original name of the bitcoin-backup folder (either Bitcoin or .bitcoin). Jump to: navigation, search. There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called bitcoind). They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can ... After downloading Bitcoind and installing / assembling it, the first step is to create a configuration file in the Bitcoin folder (~ / .bitcoin for Linux) with the following contents: rpcuser=user rpcpassword=pass rpcport=8332 txindex=1 It is worth replacing user / pass with your own username and password. Once you do this, change to the directory containing the executable file (/ bin if you ... Linux. By default Bitcoin will put its data here: ~/.bitcoin/ You need to do a "ls -a" to see directories that start with a dot. If that's not it, you can do a search like this: find / -name wallet.dat -print 2>/dev/null Mac. By default Bitcoin will put its data here: ~/Library/Application Support/Bitcoin/ Directory Contents Files. An overview of these is in files.md in the Bitcoin Core ...

[index] [39565] [5628] [38257] [981] [15930] [4767] [30966] [21262] [51485] [44754]

Linux Terminal commands and navigation for Beginners ...

Info Level: Beginner Presenter: Eli the Computer Guy Date Created: September 14, 2010 Length of Class: 45 Minutes Tracks Linux Prerequisites Introduction to ... Bitcoin Live Btc Price Liquidation Watch 24/7 Bull vs Bear Pump or Dump Bitcoin Currency Bitcoin is a cryptocurrency. It is a decentralized digital currency ... In Part 2, of a beginners tutorial on the Linux Shell. In addition to covering basic commands such as: pwd, cd, ls, and clear, I discuss adding arguments to ... Today I'll show you how to how to get started mining Bitcoin and other cryptos super fast using MinerGate. It couldn't be easier! I'll be using MinerGate, an all-in-one tool for PC, Mac, and Linux ... In this video, I'm going to show you how to start mining Bitcoin on Linux/Debian based operating systems. https://bitcoinminingsoftware2019.com/bitcoin-minin...

#