Moving the Bitcoin Core Data Directory - Bitzuma

Step by step in staking Redd with Raspberry Pi 3

Before I start, I would like to pay complete credits to these two guys :)
https://www.reddcointalk.org/topic/2679/reddcoin-staking-via-ubuntu-mate-on-raspberry-pi-3-model-b-march-2018 (most of my steps, if not all, are from this link)
https://github.com/joroob/reddcoin/blob/mastedoc/build-arm.md
All the steps I am writing is ABSOLUTELY NECESSARY, please don't try to skip it because I did, and it doesn't work.
step 1: get a Raspberry Pi B https://www.raspberrypi.org/products/#buy-now-modal
step 2: make sure you get proper power supply 5v 2A - the Pi will mine, it will need sufficient power. Regular USB samsung charger will not work.
step 3: get proper micro SD card (SanDisk for example) 32Gb++
step 4: USB + Mouse keyboard
step 5: flash micro SD card with Ubuntu MATE
Download Ubuntu Mate image: https://ubuntu-mate.org/raspberry-pi/
Download Etcher: https://etcher.io
After finishing downloading, use Etcher to write/flash the image on micro SD card
After this, your SD card contains Ubuntu MATE OS.
step 6: Place SD Card into Raspberry Pi 3 and start it up. You should be able to see Ubuntu OS! Congrats!
step 7: Connect to wifi or internet cable (internet is better and faster)
step 8: OPTIONAL - turn off UI OS, so that things will work faster
Open XTerminal:
sudo systemctl disable lightdm.service (to turn UI off) 
in case you want to turn UI on again, run this:
sudo systemctl start lightdm.service (to turn UI on) 
step 9: install all dependencies
sudo apt-get update && sudo apt-get install git build-essential libqt4-dev libprotobuf-dev protobuf-compiler libtool autotools-dev autoconf libssl-dev libboost-all-dev wget pkg-config sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install db4.8 sudo apt-get install libminiupnpc-dev sudo apt-get install libqrencode-dev Reboot 
step 10: add additional RAM (sort of) in case the App need it, this is call "Create Swap file"
sudo fallocate -l 1G /swapfile sudo chmod 600 /swapfile sudo mkswap /swapfile sudo swapon /swapfile echo ‘/swapfile none swap sw 0 0’ | sudo tee -a /etc/fstab 
step 11: Build Berkeley Database
wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz tar xfvz db-4.8.30.NC.tar.gz cd db-4.8.30.NC cd build_unix ../dist/configure --enable-cxx make sudo make install 
step 11.5: Set BerkeleyDB path
export CPATH="/uslocal/BerkeleyDB.4.8/include" export LIBRARY_PATH="/uslocal/BerkeleyDB.4.8/lib" export LD_LIBRARY_PATH=/uslocal/BerkeleyDB.4.8/lib/ 
step 12: Build Reddcoin Wallet
---download source code ---- only source from joroob/reddcoin will work because some stweak was needed for ARM CPU
cd ~ git clone https://github.com/joroob/reddcoin.git 
---build reddcoin ----
cd reddcoin ./autogen.sh ./configure --with-gui=no --disable-tests cd src make sudo make install 
If you finish this, you are in a great position!!!
step 13: Create reddcoin configuration file
cd ~ mkdir .reddcoin && cd .reddcoin nano reddcoin.conf rpcuser=YOUR OWN USERNAME, YOU DONT NEED TO REMEMBER THIS, MAKE IT AS LONG AS YOU WANT rpcpassword=YOUR OWN PASS WORD, YOU DONT NEED TO REMEMBER THIS, MAKE IT AS LONG AS YOU WANT 
step 14: Use bootstrap
(At this point, you had a running reddcoin daemon, now you can start staking. But syncing the full chain takes long time.)
cd ~/.reddcoin wget https://github.com/reddcoin-project/reddcoin/releases/download/v2.0.1.2/bootstrap.dat.xz xz -d bootstrap.dat.xz 
step 15: start the reddcoin daemon service cd ~/reddcoin/src ./reddcoind -daemon
After this, you can test if the daemon is working, by perform this command: ./reddcoin-cli getblockcount
step 16: if your app is not able to sync, it is probably the firewall issue with OS, run this to allow port 45444 (used by Reddcoin) and redo step 15
sudo iptables -I INPUT 1 -i eth0 -p tcp --dport 45444 -j ACCEPT sudo iptables -A OUTPUT -p tcp --dport 45444 -j ACCEPT 
step 17: open BEER and enjoy! This is a MUST or the daemon will stop working! I am not kidding!
step 18: Actually, i forgot to mention you need to execute this command for the wallet to stake:
reddcoind walletpassphrase $yourpassword 9999999 true 
ADDITIONAL REMARKS:
From my PC: I am using putty to execute the command, winSCP to monitor the file location on raspberry.
Moving Red Coins out of exchange really a big move, start with normal wallet, don't start with this tutorial :) Ever since I move my coins out of exchange, I am free from all of the ups and downs! Really!
So guys and gals, Redd On!
UPDATE 18 Mar: my first stake has arrived after 6 days staking :)
In case you want to tip me: RaF3TeWqgTzAdnaZQffnsxS74dag13zsAY
Edit 1: Format stuff
Edit 2: Add step 18 to execute staking command.
Edit 3: In case you don't want to compile the source code, you can download my compile version here: https://github.com/hieplenet/reddcoin/releases/tag/v2.0.0.0 (but doing this, you should be aware of the risk of me changing source code for my benefit - I don't change any thing, but you should be cautious, this is the internet :) )
submitted by hieplenet to reddCoin [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 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]

PureVPN - poor security and no DNS leak protection... unless you pay up!

PROs:
CONs:
So I decided to try PureVPN after my annual Private Internet Access subscription recently ended. I wanted to check it out after reading positive reviews and reports that they could provide streaming services in other countries - something most VPNs cannot do anymore. I use many different devices, so the fact they provided service on more platforms than other providers seemed like a huge plus to me as well. They even claimed to offer service for Kodi and Apple TV. I was so DTT - down to try!
After installing the program in macOS and Windows, it seemed to be working well. I used various websites to check the information leaking into my browsers, and it seemed to be working. However, it was when I was using their service on linux platforms that I noticed their serious security problem.
First was Ubuntu 16.04. Only Windows and macOS are provided with actual programs from PureVPN to connect to VPN, which I wasn't excited about and only noticed after I purchased the service. I use linux a lot, so I was kind of disappointed. I installed the program via OpenVPN, and while not as easy as point and click or running a deb file, it was relatively easy to set up in ubuntu. I wasn't excited with having to add each VPN server's IP individually to connect and would have rather had a program that allows easy switching of server IPs. It didn't hit me until later why this is such a big security/privacy issue.
After install, I went to the plethora of sites providing anonymity benchmarks for VPN services. I was connected to their VPN server in the Netherlands, but my location was being recorded as local and through Charter - my actual ISP. I was confused at first, and after looking through the tests, I noticed it was because my DNS was leaking. This is a PROBLEM. DNS leak protection is provided by almost every VPN provider, especially the large ones. Without it, your VPN is worthless to use for internet activity.
I went ahead and changed my DNS servers to google on ubuntu (they were already changed to google on my router though), refreshed my ubuntu network services and the browser's history/cookies/etc. Changing to google's DNS from the automatic DNS from the ISP should have fixed that, but it didn't. Instead, I decided to change the OpenVPN config file to fix the DNS leak protection – which is commonly used on OpenVPN for this specific reason. I added these lines at the end of my conf file, then refreshed the OpenVPN service:
script-security 2
up /etc/openvpn/update-resolv-conf.sh
down /etc/openvpn/update-resolv-conf.sh
That should have fixed the issue with DNS leaking. Guess what? Unless I used the exact configuration provided by them, I was unable to connect to their VPN. I was kind of pissed, and looked into their refund policy: no refunds if you pay with bitcoin. Well, shit. Why would they have done this? I can only think of one reason:
PureVPN CHARGES for DNS leak protection via their NAT Firewall -- meaning they want you to pay an additional premium to receive a service that should be included free of charge. Most people won’t notice until after they’ve purchased VPN servcies.
I didn't want to get bait and switched again, so I contacted them about trying the NAT Firewall, an additional $50 for my subscription, for one month first to see if I liked it. I'd even pay the full price without a discount to see how it works. Yeah, I was told to fuck off. I was told I would have to add NAT Firewall for my entire subscription or nothing at all. I was pissed.
In sum: PureVPN offers premium VPN services. Their service is faster than almost any other VPN service. Now is it THE fastest, I’m not sure about that. I saw no difference from my last service with PIA. They also provide a nice GUI program for Windows and macOS for VPN. However, if you want to use their service on ALL the platforms they claim, you will not have the same level of security that is provided on Windows and macOS. I haven’t tried the service on my Apple TV, but I’m doubtful my Apple TV will run the NAT Firewall they wanted me to purchase.
So far, I’m super unhappy with my service and wish I would have stayed with Private Internet Access, or tried another like IPVanish, etc. I was livid with their privacy and security problems, and pissed they wanted me to pay more for a basic service included by any major VPN provider. This issue is an easy fix they could have included, but decided make customers pay an additional premium for basic security.
I decided to let them keep my damn non-refundable by bitcoin payment for their unsecure, unprivate, ISP- and NSA-friendly, DNS-protectionless service. I'm either going back to Private Internet Service or checking out IPVanish. This time, however, I'll buy one month to see how it goes first. Fool me once, shame on me...
submitted by PsycHD_Student to vpnreviews [link] [comments]

Help Troubleshooting Bitcoin Code Full Node

Hi guys, I'm having a problem running my Bitcoin Core full node. If anyone can help me that would be amazing. I'll try my best to give all the details.
2017-11-05 11:50:54 Bitcoin version v0.15.0.1
2017-11-05 11:50:54 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-11-05 11:50:54 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures.
2017-11-05 11:50:54 Using the 'standard' SHA256 implementation
2017-11-05 11:50:54 Using RdRand as an additional entropy source
2017-11-05 11:50:54 Default data directory /home/darius/.bitcoin
2017-11-05 11:50:54 Using data directory
2017-11-05 11:50:54 Using config file bitcoin.conf
2017-11-05 11:50:54 Using at most 125 automatic connections (1024 file descriptors available)
2017-11-05 11:50:54 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2017-11-05 11:50:54 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2017-11-05 11:50:54 Using 4 threads for script verification
2017-11-05 11:50:54 scheduler thread start
2017-11-05 11:50:54 libevent: getaddrinfo: address family for nodename not supported
2017-11-05 11:50:54 Binding RPC on address ::1 port 8332 failed.
2017-11-05 11:50:54 HTTP: creating work queue of depth 16
2017-11-05 11:50:54 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2017-11-05 11:50:54 HTTP: starting 4 worker threads
2017-11-05 11:50:54 init message: Verifying wallet(s)...
2017-11-05 11:50:54 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2017-11-05 11:50:54 Using wallet wallet.dat
2017-11-05 11:50:54 CDBEnv::Open: LogDir=database ErrorFile=db.log
2017-11-05 11:50:54 Cache configuration:
2017-11-05 11:50:54 * Using 56.2MiB for block index database
2017-11-05 11:50:54 * Using 8.0MiB for chain state database
2017-11-05 11:50:54 * Using 385.8MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-11-05 11:50:54 init message: Loading block index...
2017-11-05 11:50:54 Opening LevelDB in blocks/index
2017-11-05 11:50:54 IO error: blocks/index/LOCK: Permission denied
2017-11-05 11:50:54 Database I/O error
2017-11-05 11:50:54 : Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
: Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
2017-11-05 11:50:54 Aborted block database rebuild. Exiting.
2017-11-05 11:50:54 scheduler thread interrupt
2017-11-05 11:50:54 Shutdown: In progress...
2017-11-05 11:50:54 Shutdown: done
submitted by KomodoDragonJesus to Bitcoin [link] [comments]

what hidden servers are running on 2017 edition

How unique is your hidden service?
2206 Server: nginx 1011 Server: Apache 326 Server: nginx/1.6.2 142 Server: Apache/2.4.10 (Debian) 89 Server: Apache/2.2.22 (Debian) 88 Server: lighttpd/1.4.31 87 Server: Apache/2.4.18 (Ubuntu) 81 Server: Apache/2.4.7 (Ubuntu) 60 Server: i337-xfog 55 Server: nginx/1.4.6 (Ubuntu) 48 Server: lighttpd/1.4.35 43 Server: lighttpd/1.4.33 43 Server: globaleaks 42 Server: nginx/1.12.0 40 Server: nginx/1.2.1 39 Server: Apache/2.4.25 (Win32) OpenSSL/1.0.2j PHP/5.6.30 38 Server: nginx/1.10.3 35 Server: TwistedWeb/12.0.0 32 Server: nginx/1.10.2 31 Server: nginx/1.10.0 (Ubuntu) 30 Server: nginx/1.13.1 30 Server: cyclone/1.1 27 Server: Apache/2.2.15 (CentOS) 23 Server: nginx/1.10.1 21 Server: mini_httpd/1.19 19dec2003 19 Server: iTor Server ! 16 Server: Apache/2.4.6 (CentOS) PHP/5.4.16 15 Server: Apache/2.2.22 (Ubuntu) 14 Server: Microsoft-IIS/8.5 13 Server: Apache-Coyote/1.1 11 Server: sorrynotgivingthataway 11 Server: Microsoft-IIS/7.5 11 Server: Apache/2.4.10 (Raspbian) 10 Server: lighttpd/1.4.45 10 Server: lighttpd 8 Server: nginx/1.9.13 8 Server: nginx/1.8.0 8 Server: Microsoft-IIS/10.0 8 Server: Apache/2.4.25 (Debian) 7 Server: TorHosting 7 Server: Apache/1.3.29 (Unix) mod_perl/1.29 PHP/4.4.1 mod_ssl/2.8.16 OpenSSL/0.9.7g 6 Server: PopFiles (http://popfilesxuru7lsr.onion) 6 Server: nginx/1.7.4 6 Server: FobbaWeb/0.1 6 Server: Caddy 6 Server: Apache/2.4.25 (Unix) 6 Server: Apache/2.4.23 (Win32) OpenSSL/1.0.2h PHP/5.6.28 5 Server: OpenBSD httpd 5 Server: nginx/1.13.2 5 Server: Monkey/1.5.6 5 Server: lighttpd/1.4.28 5 Server: Apache/2.4.6 (Ubuntu) 5 Server: Apache/2.4.6 (CentOS) mpm-itk/2.4.7-04 OpenSSL/1.0.1e-fips mod_fcgid/2.3.9 PHP/5.4.16 5 Server: Apache/2.4.26 (FreeBSD) PHP/5.6.30 5 Server: Apache/2.4.18 (Win64) PHP/5.5.0RC3 5 Server: Apache/2.4.10 5 Server: Apache/2.2.31 (Amazon) 5 Server: Apache/2 4 Server: tor_httpd 4 Server: nginx-1.8.1 4 Server: nginx/1.6.3 4 Server: nginx/1.10.1 (Ubuntu) 4 Server: mini_httpd/1.23 28Dec2015 4 Server: Microsoft-IIS/6.0 4 Server: lunarhttpd.china 4 Server: Apache/2.4.6 (CentOS) mpm-itk/2.4.7-01 OpenSSL/1.0.1e-fips mod_fcgid/2.3.9 PHP/5.4.16 4 Server: Apache/2.4.25 (Unix) OpenSSL/1.0.1t PHP/5.6.30 mod_wsgi/4.5.11 Python/3.6 4 Server: Apache/2.4.25 (Ubuntu) 4 Server: Apache/2.4.23 4 Server: Apache/2.4.18 (Win64) PHP/5.6.18 4 Server: Apache/2.4.12 (Ubuntu) 3 Server: WebServer 3 Server: thttpd/2.27 19Oct2015 3 Server: thttpd 3 Server: The web is lovely, dark, and deep... 3 Server: nginx/1.9.9 3 Server: nginx/1.8.1 3 Server: nginx/1.11.1 3 Server: nginx/1.10.3 (Ubuntu) 3 Server: Jetty(9.3.0.M2) 3 Server: gunicorn/19.7.1 3 Server: FUCKYOU 3 Server: Follow the white rabbit. 3 Server: CERN/3.0A libwww/2.17 3 Server: BitCloak 3 Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.6.30 mod_perl/2.0.10 Perl/v5.16.3 3 Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16 3 Server: Apache/2.4.25 (Unix) OpenSSL/1.1.0e 3 Server: Apache/2.4.18 (Fedora) PHP/5.6.23 3 Server: Apache/2.4.10 (Debian) OpenSSL/1.0.1t 3 Server: Apache/2.2.22 (@[email protected]) 3 Server: Apache/1.3.28 (Unix) mod_perl/1.29 PHP/4.4.0 mod_ssl/1.6.12 OpenSSL/0.6.3f Protector_Facto0.2.17 3 Server: anon 3 Server: !......? 2 Server: WSGIServe0.1 Python/2.7.12 2 Server: Werkzeug/0.12.2 Python/3.5.2 2 Server: webserver 2 Server: VmxkMGIxTXlUa2hUYmxKcVRXMVNjRlp1Y0hOT1ZtUnpWR3RPVmxJeFNqQlZiVFZQWVRGSmVXVkVSbGhpUlRWSFZVWkZPVkJSUFQwPQ== 2 Server: TwistedWeb/14.0.2 2 Server: TornadoServe4.4.2 2 Server: thttpd/2.26 14aug2014 2 Server: PAMttpd v6.6.6 2 Server: nginx/1.9.14 2 Server: nginx/1.9.10 2 Server: nginx/1.7.6 2 Server: nginx/1.6.0 2 Server: nginx/1.2.9 2 Server: nginx/1.1.19 2 Server: nginx/1.10.0 2 Server: Mojolicious (Perl) 2 Server: MochiWeb/1.0 (Any of you quaids got a smint?) 2 Server: mitmproxy 2.0.2 2 Server: Leave_a_message_in_the_URL 2 Server: Jetty(9.2.z-SNAPSHOT) 2 Server: IIS 2 Server: httpd 2 Server: Globaleaks 2 Server: D3vil May Card! 2 Server: Apache/2.4.6 (Win32) PHP/5.4.17 2 Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.6.30 2 Server: Apache/2.4.25 (Unix) OpenSSL/1.1.0f 2 Server: Apache/2.4.25 (Amazon) mod_wsgi/3.5 Python/2.7.12 2 Server: Apache/2.4.23 (Win64) PHP/5.6.26 2 Server: Apache/2.4.23 (Unix) PHP/5.6.23 2 Server: Apache/2.4.23 (Amazon) PHP/5.6.25 2 Server: Apache/2.4.20 (Unix) PHP/5.5.9 2 Server: Apache/2.4.18 (FreeBSD) 2 Server: Apache/2.4.18 2 Server: Apache/2.4.16 (Win32) 2 Server: Apache/2.4.10 (Debian) PHP/5.6.30-0+deb8u1 OpenSSL/1.0.1t 2 Server: Apache/2.2.3 (CentOS) 2 Server: Apache/2.2.31 (Unix) 2 Server: Apache/2.2.15 2 Server: Apache/2.0.64 (Win32) PHP/5.2.14 2 Server: Abyss/2.6.0.0-X1-Linux AbyssLib/2.6.0.0 1 Server: Zoidberg/1.1 1 Server: WWW File Share Pro 1 Server: Windows Server 2012 IIS 7.5 1 Server: Whaanhjej 1 Server: Werkzeug/0.9.6 Python/3.4.2 1 Server: Werkzeug/0.12.1 Python/2.7.13 1 Server: Werkzeug/0.11.2 Python/2.7.9 1 Server: WebServer(IPCamera_Logo) 1 Server: Web Serve1.0 1 Server: Webserver 1 Server: WEBrick/1.3.1 (Ruby/2.2.4/2015-12-16) 1 Server: webfs/1.21 1 Server: WebCit 903 / Citadel 903 1 Server: TwistedWeb/17.1.0 1 Server: TwistedWeb/15.0.0 1 Server: Torsrv v something 1 Server: TornadoServe4.5.1 1 Server: tor httpd 1 Server: thttpd/2.25b 29dec2003 1 Server: thin 2.0.0.pre 1 Server: thin 1.5.0 codename Knife 1 Server: TheOnionRouter 1 Server: Strange web server 1 Server: SimpleHTTP/0.6 Python/3.5.2 1 Server: SimpleHTTP/0.6 Python/2.7.9 1 Server: SimpleHTTP/0.6 Python/2.7.3 1 Server: senginx/1.6.1 1 Server: Savant/3.1 1 Server: Resin/4.0.13 1 Server: Rate Limiting May Cause Temporary Outages, We Apologize For The Inconvenience. 1 Server: -=RASH=- 1 Server: Proxy 1 Server: openresty 1 Server: onion 1 Server: Null 1 Server: none 1 Server: Njalla 1 Server: nginx/1.9.3 (Ubuntu) 1 Server: nginx/1.9.15 1 Server: nginx/1.7.5 1 Server: nginx/1.6.2 (Ubuntu) 1 Server: nginx/1.6.1 1 Server: nginx/1.4.7 1 Server: nginx/1.4.6 (Trisquel GNU/Linux) 1 Server: nginx/1.4.1 (Ubuntu) 1 Server: nginx/1.11.9 1 Server: nginx/1.11.8 1 Server: nginx/1.11.7 1 Server: nginx/1.11.3 1 Server: nginx/1.11.13 1 Server: nginx/1.11.12 1 Server: nginx/1.11.10 1 Server: nginx/1.11.0 1 Server: nginx/1.10.2 + Phusion Passenger 5.1.2 1 Server: nginx/1.0.5 1 Server: nginx/1.0.15 1 Server: nginx/0.8.38 1 Server: nginx/0.7.67 1 Server: nginx/0.7.65 1 Server: MS IIS-5.0 1 Server: Microsoft-IIS/8.0 1 Server: Microsoft-IIS/4.0. 1 Server: Mastodon 1 Server: lunarhttpd 1 Server: localhost 1 Server: LiteSpeed 1 Server: lighttpd/1.4.44 1 Server: lighttpd/1.4.39 1 Server: LightTPD/1.4.35-1-IPv6 (Win32) 1 Server: Jetty(8.y.z-SNAPSHOT) 1 Server: Indymedia 2.0 1 Server: Icecast 2.4.3 1 Server: Hiawatha v9.14 1 Server: Hiawatha v10.6 1 Server: Hiawatha v10.5 1 Server: gunicorn/19.6.0 1 Server: gunicorn/19.4.5 1 Server: GlassFish Server Open Source Edition 4.1.2 1 Server: GlassFish 1 Server: Gatling/0.13 1 Server: Etherpad (http://etherpad.org) 1 Server: Etherpad a07f9db (http://etherpad.org) 1 Server: Etherpad 9f51432 (http://etherpad.org) 1 Server: DWMinistries 1 Server: Donations are welcome, BTC adress: 1LZqhG1KHa2vYx8TUKJW65YcnvmwMVChoH 1 Server: CherryPy/6.0.2 1 Server: CherryPy/3.2.0 1 Server: Cherokee/1.0.8 (Debian GNU/Linux) 1 Server: Cherokee 1 Server: Candle 1 Server: Candle 1 Server: bozohttpd/20170201 1 Server: Bazaar 1.0.0 1 Server: BaseHTTP/0.6 Python/3.6.1 1 Server: ATS/7.0.0 1 Server: Apache or maybe IIS? 1 Server: Apache/2.4.9 (Win32) PHP/5.5.12 1 Server: Apache/2.4.9 (Fedora) OpenSSL/1.0.1e-fips 1 Server: Apache/2.4.7 (CentOS) 1 Server: Apache/2.4.6 (Win64) OpenSSL/1.0.1e PHP/5.5.5 1 Server: Apache/2.4.6 (Linux/SUSE) 1 Server: Apache/2.4.6 (CentOS) PHP/5.4.16 Phusion_Passenge5.0.27 1 Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips mod_fcgid/2.3.9 PHP/5.4.45 1 Server: Apache/2.4.6 (CentOS) mpm-itk/2.4.7-04 OpenSSL/1.0.1e-fips PHP/5.6.30 1 Server: Apache/2.4.5 (FreeBSD) 1 Server: Apache/2.4.26 (Unix) OpenSSL/1.0.2k Phusion_Passenge5.0.30 mod_wsgi/4.5.7 Python/2.7 PHP/5.6.30 1 Server: Apache/2.4.26 1 Server: Apache/2.4.25 (Unix) (Red-Hat/Linux) 1 Server: Apache/2.4.25 (Unix) PHP/7.1.5 1 Server: Apache/2.4.25 (Unix) PHP/7.1.2 1 Server: Apache/2.4.25 (Unix) OpenSSL/1.0.2k mod_apreq2-20090110/2.8.0 mod_perl/2.0.10 Perl/v5.24.1 1 Server: Apache/2.4.25 (Raspbian) 1 Server: Apache/2.4.25 (FreeBSD) OpenSSL/1.0.1s-freebsd mpm-itk/2.4.7-03 PHP/5.6.18 1 Server: Apache/2.4.25 (Fedora) PHP/7.0.17 1 Server: Apache/2.4.25 (Fedora) OpenSSL/1.0.2k-fips PHP/7.0.18 mod_perl/2.0.10 Perl/v5.24.1 1 Server: Apache/2.4.25 (Fedora) 1 Server: Apache/2.4.25 (Amazon) OpenSSL/1.0.1k-fips PHP/5.5.38 1 Server: Apache/2.4.25 (Amazon) OpenSSL/1.0.1k-fips 1 Server: Apache/2.4.25 1 Server: Apache/2.4.23 (Win64) PHP/5.6.25 1 Server: Apache/2.4.23 (Win32) OpenSSL/1.0.2h PHP/7.0.9 1 Server: Apache/2.4.23 (Unix) OpenSSL/1.0.1e-fips PHP/7.0.9 1 Server: Apache/2.4.20 1 Server: Apache/2.4.18 (Vine) OpenSSL/1.0.2h build-1vl6n20h2 vm3 1 Server: Apache/2.4.18 (Unix) OpenSSL/1.0.2h PHP/7.0.8 mod_perl/2.0.8-dev Perl/v5.16.3 1 Server: Apache/2.4.18 (Red Hat) PHP/5.6.25 1 Server: Apache/2.4.17 (Win32) OpenSSL/1.0.2d PHP/5.5.35 1 Server: Apache/2.4.10 (Ubuntu) 1 Server: Apache/2.4.10 (Fedora) Phusion_Passenge3.0.21 1 Server: Apache/2.4.10 (Fedora) PHP/5.5.26 1 Server: Apache/2.4.10 (Debian) mod_fcgid/2.3.9 OpenSSL/1.0.1t 1 Server: Apache/2.4.10 (Debian) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.6.30-0+deb8u1 OpenSSL/1.0.1t 1 Server: Apache/2.4 1 Server: Apache/2.2.3 (YellowDog) 1 Server: Apache/2.2.29 (Unix) mod_apreq2-20090110/2.8.0 mod_perl/2.0.8 Perl/v5.20.1 1 Server: Apache/2.2.29 (Unix) DAV/2 SVN/1.7.20 mod_ssl/2.2.29 OpenSSL/0.9.8zg 1 Server: Apache/2.2.29 (Unix) DAV/2 mod_apreq2-20090110/2.8.0 mod_perl/2.0.8 Perl/v5.20.1 1 Server: Apache/2.2.26 (Unix) mod_ssl/2.2.26 OpenSSL/0.9.8y DAV/2 1 Server: Apache/2.2.25 (Win32) 1 Server: Apache/2.2.22 (Win32) mod_ssl/2.2.22 OpenSSL/1.0.1c PHP/5.3.13 1 Server: Apache/2.2.22 (Win32) mod_ssl/2.2.22 OpenSSL/1.0.0g PHP/5.3.13 DAV/2 1 Server: Apache/2.2.22 (Win32) 1 Server: Apache/2.2.22 (Debian) mod_ssl/2.2.22 OpenSSL/1.0.1t 1 Server: Apache/2.2.22 1 Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8y DAV/2 1 Server: Apache/2.2.16 (Debian) 1 Server: Apache/2.2.14 (Ubuntu) 1 Server: Apache/1.3.29 (Unix) mod_perl/1.29 PHP/4.4.1 mod_ssl/2.8.16 1 Server: Agrika 1 Server: Adeptorum v6.6.6 1 Server: Abyss/2.11-X1-Win32 AbyssLib/2.11 1 Server: Abyss/2.11.2-X1-Win32 AbyssLib/2.11.2 1 Server: 532 X-Content-Type-Options: nosniff 415 X-XSS-Protection: 1; mode=block 260 X-Frame-Options: SAMEORIGIN 184 X-Frame-Options: sameorigin 120 X-Frame-Options: DENY 114 X-Xss-Protection: 1; mode=block 102 X-Xss-Protection: 1 99 X-Powered-By: PHP/5.5.9-1ubuntu4.21 76 X-Powered-By: PHP/5.4.45-0+deb7u7 61 X-Powered-By: PHP/5.6.30 61 X-Download-Options: noopen 59 X-Robots-Tag: noindex 47 X-Clacks-Overhead: GNU Terry Pratchett 43 X-Content-Security-Policy: default-src 'self' 38 X-Powered-By: PHP/5.3.3 38 X-Frame-Options: deny 37 X-Powered-By: PHP/5.4.45-0+deb7u8 34 X-Powered-By: PHP/5.5.9-1ubuntu4.5 32 X-XSS-Protection: 1 24 X-Powered-By: Express 20 X-Powered-By: PHP/5.4.45-0+deb7u2 20 X-Powered-By: PHP/5.4.16 20 X-Pad: avoid browser bug 18 X-Powered-By: PHP/5.5.38 16 X-Powered-By: ASP.NET 15 X-XSS-Protection: 1; mode=block; 15 X-Powered-By: PHP/5.4.45 14 X-Powered-By: PHP/5.5.9-1ubuntu4.20 14 X-Powered-By: PHP/5.5.38-1~dotdeb+7.1 13 X-Powered-By: PHP/5.5.9-1ubuntu4.14 13 X-DNS-Prefetch-Control: off 12 X-Permitted-Cross-Domain-Policies: none 10 X-Spip-Cache: 86400 10 X-Generator: Drupal 7 (http://drupal.org) 9 X-Varnish-Ttl: 86400 8 X-UA-Compatible: IE=Edge,chrome=1 8 X-UA-Compatible: IE=edge 8 X-Powered-By: PHP/5.6.22-2 8 X-Powered-By: PHP/5.4.41 7 X-Powered-By: PHP/5.6.30-0+deb8u1 7 X-Powered-By: PHP/5.3.10-1ubuntu3.26 7 X-Drupal-Cache: HIT 7 X-Cache: HIT 6 X-UA-Compatible: IE=Edge 6 X-Robots-Tag: noindex, nofollow, nosnippet, noarchive 6 X-Powered-By: PHP/7.1.5 6 X-Powered-By: PHP/7.0.20 6 X-ID: f465c2e1 6 X-Cache: MISS 6 X-AspNet-Version: 4.0.30319 5 X-UA-Compatible: IE=edge,chrome=1 5 X-Powered-By: VPS Server 5 X-Powered-By: PHP/5.5.0RC3 5 X-Powered-By: PHP/5.4.4-14+deb7u12 5 X-Permitted-Cross-Domain-Policies: master-only 5 X-Content-Security-Policy: default-src 'none'; child-src *; frame-src *;base-uri 'self'; frame-ancestors *; plugin-types none; form-action: 'self'; 5 X-AspNetMvc-Version: 5.2 4 X-UA-Compatible: IE=7 4 X-Powered-By: PHP/7.0.11 4 X-Powered-By: PHP/5.5.3-1ubuntu2.6 3 X-Varnish-Age: 0 3 X-Ua-Compatible: IE=edge 3 X-Robots-Tag: none 3 X-Powered-By: PHP/7.1.6 3 X-Powered-By: PHP/7.1.3 3 X-Powered-By: PHP/5.6.18 3 X-Powered-By: PHP/5.5.9-1ubuntu4.9 3 X-Powered-By: PHP/5.5.9-1ubuntu4.17 3 X-Powered-By: PHP/5.5.9-1ubuntu4.16 3 X-Powered-By: PHP/5.4.45-0+deb7u5 3 X-Powered-By: PHP/5.4.17 3 X-Powered-By: PHP/5.3.10-1ubuntu3.24 3 X-Page-Speed: Hidden 3 X-Generator: Drupal 8 (https://www.drupal.org) 3 X-Frame-Options: SAMEORIGIN, SAMEORIGIN 3 X-Drupal-Dynamic-Cache: UNCACHEABLE 3 X-Drupal-Cache: MISS 3 X-Content-Security-Policy: default-src 'self' 'unsafe-inline' 3 X-Aspnet-Version: 4.0.30319 2 X-XSS-Protection: 0 2 X-WebKit-CSP: default-src 'self' 'unsafe-inline' 2 X-Ua-Compatible: IE=edge,chrome=1 2 X-UA-Compatible: chrome=1 2 X-TTL: TTL3000.000 2 X-Rack-Cache: miss 2 X-Powered-By: Phusion Passenger 5.0.29 2 X-Powered-By: Phusion Passenger 4.0.53 2 X-Powered-By: PHP/7.1.4 2 X-Powered-By: PHP/7.0.19 2 X-Powered-By: PHP/7.0.18 2 X-Powered-By: PHP/7.0.10 2 X-Powered-By: PHP/5.6.30-1~dotdeb+7.1 2 X-Powered-By: PHP/5.6.28 2 X-Powered-By: PHP/5.6.25 2 X-Powered-By: PHP/5.6.23 2 X-Powered-By: PHP/5.6.20 2 X-Powered-By: PHP/5.6.16 2 X-Powered-By: PHP/5.5.9 2 X-Powered-By: PHP/5.4.45-0+deb7u6 2 X-Powered-By: PHP/5.4.45-0+deb7u4 2 X-Powered-By: PHP/5.3.29 2 X-Powered-By: PHP/5.2.14 2 X-Powered-By: :) 2 X-Pingback: http://yinyang2bmaetyoo.onion/xmlrpc.php 2 X-Micro-Cache: EXPIRED 2 X-Hudson-Theme: default 2 X-Hudson: 1.395 2 X-Garden-Version: Vanilla 2.1.10 2 X-Frame-Options: Sameorigin 2 X-Discourse-Route: list/latest 2 X-Content-Type-Options:: nosniff 2 X-Backend-Status: MISS 1 X-Xss-Protection: 1;mode=block 1 X-XRDS-Location: https://nameid.org/?xrds=general 1 X-XHR-Current-Location: / 1 X-Webkit-Csp: default-src 'self' 'unsafe-inline' 1 X-WebKit-CSP: default-src 'self' ;script-src 'self' 'unsafe-inline' 'unsafe-eval';referrer no-referrer;style-src 'self' 'unsafe-inline' ;img-src 'self' data: *.tile.openstreetmap.org *.tile.opencyclemap.org ; 1 X-WebKit-CSP: default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.google.com https://*.gstatic.com https://*.googleapis.com https://*.google-analytics.com https://assets.zendesk.com https://connect.facebook.net https://cdnjs.cloudflare.com https://cdn.jsdelivr.net https://*.keycaptcha.com https://platform.twitter.com; img-src 'self' https://*.google-analytics.com https://*.googleapis.com https://*.tapatalk-cdn.com https://tapatalk.com https://www.google.com https://www.google.com.ua https://www.google.ru https://www.google.be https://www.google.md https://*.gstatic.com https://stats.g.doubleclick.net https://s-static.ak.facebook.com https://assets.zendesk.com https://*.keycaptcha.com https://www.facebook.com https://syndication.twitter.com; style-src data: 'self' 'unsafe-inline' https://*.googleapis.com https://assets.zendesk.com https://maxcdn.bootstrapcdn.com; font-src 'self' https://themes.googleusercontent.com https://maxcdn.bootstrapcdn.com https://fonts.gstatic.com; child-src 'self' https://*.youtube.com https://accounts.google.com https://vk.com https://fonts.gstatic.com https://assets.zendesk.com https://www.facebook.com https://staticxx.facebook.com https://tautt.zendesk.com https://*.keycaptcha.com https://www.google.com; object-src 'self' https://*.keycaptcha.com https://platform.twitter.com https://www.google.com; connect-src 'self' https://*.google-analytics.com; report-uri https://psylab.report-uri.io/default/csp/enforce; upgrade-insecure-requests 1 X-Webkit-Csp: default-src 'self'; script-src 'none'; frame-src 'none'; object-src 'none'; style-src 'self' 'unsafe-inline' 1 X-WebKit-CSP: allow 'self'; 1 X-WAG-ID: WS:ew3-a1 1 X-Vhost-SecurityProfile: default 1 X-Varnish-Cache: HIT 1 X-Varnish-Age: 8493 1 X-Varnish-Age: 728 1 X-Varnish-Age: 42404 1 X-Varnish-Age: 42278 1 X-Varnish-Age: 17319 1 X-Varnish-Age: 12651 1 X-Varnish-Age: 1049 1 X-Varnish: 8599495 1 X-Varnish: 750672853 750672635 1 X-Varnish: 592016 1 X-Varnish: 4960315 1 X-Varnish: 406771 1 X-Varnish: 2558990 917653 1 X-Varnish: 2556512 1081456 1 X-Varnish: 201441541 1 X-Varnish: 18219271 328572 1 X-Varnish: 1737790 1049351 1 X-Varnish: 13930494 1704581 1 X-Varnish: 13736779 5210129 1 X-Varnish: 1279167 1 X-Varnish: 123953481 1 X-Varnish: 12354605 1310729 1 X-Varnish: 1231818739 1 X-Varnish: 11819611 1 X-Varnish: 10880654 1 X-Varnish: 10636 10631 1 X-Varnish: 1047319896 1 X-Varnish: 1016427 1 X-Ua-Compatible: ie=edge 1 X-UA-Compatible: IE=9 1 X-Ua-Compatible: IE=7 1 X-Ua-Compatible: chrome=1 1 X-TemplateHeader: dokuwiki 1 X-Sql-Time-Spent: 0.0ms 1 X-Sql-Queries: 0 1 X-Runtime: 0.760664 1 X-Runtime: 0.399850 1 X-Runtime: 0.343910 1 X-Runtime: 0.331721 1 X-Runtime: 0.248619 1 X-Runtime: 0.100307 1 X-Runtime: 0.078857 1 X-Runtime: 0.066585 1 X-Runtime: 0.055833 1 X-Runtime: 0.046604 1 X-Runtime: 0.040742 1 X-Runtime: 0.038651 1 X-Runtime: 0.036826 1 X-Runtime: 0.032528 1 X-Runtime: 0.032493 1 X-Runtime: 0.023483 1 X-Runtime: 0.023369 1 X-Runtime: 0.021013 1 X-Runtime: 0.020903 1 X-Runtime: 0.017691 1 X-Runtime: 0.014886 1 X-Runtime: 0.014398 1 X-Runtime: 0.007907 1 X-Runtime: 0.005247 1 X-Runtime: 0.004288 1 X-Runtime: 0.003696 1 X-Runtime: 0.002933 1 X-Runtime: 0.001736 1 X-Runtime: 0.001690 1 X-Runtime: 0.001574 1 X-Runtime: 0.001404 1 X-Runtime: 0.001221 1 X-Runtime: 0.001008 1 X-Robots-Tag: nofollow, noindex 1 X-Robots-Tag: nofollow 1 X-Response-Time: 28.104ms 1 X-Request-Time: 87.409019sms 1 X-Request-Id: ffb649bb-0c50-4ef0-82ee-d56529d268cb 1 X-Request-Id: fe1f9fcc-8603-4346-87d1-fd180263f96d 1 X-Request-Id: ef93d51e-a9d7-42a2-93dc-bda5e25fc891 1 X-Request-Id: e902ade2-8a67-48ee-b170-45ebb1a912d1 1 X-Request-Id: d6f7bf12-eb43-48c3-81ff-710c18f22447 1 X-Request-Id: d6a98ae3f441d53311c19178c87a26d9 1 X-Request-Id: d39b4958-6ebe-4456-9437-39199d48b79f 1 X-Request-Id: c21385da-25e2-4788-9784-881df34b8307 1 X-Request-Id: b8b1b608-7c86-4005-a23f-f16dbb94e497 1 X-Request-Id: a6d8dac4-bd95-45ea-86be-45f7a1b8aca4 1 X-Request-Id: 8c6c8995-90e8-4cb9-9636-06f61ebddda9 1 X-Request-Id: 8a2f43c3-79a8-4eb8-8de7-b31e5671dbf3 1 X-Request-Id: 867a6b8c-e81e-46b9-9859-0fa91a2fce0e 1 X-Request-Id: 7aa56313-7472-44e5-8343-0f161b0872fd 1 X-Request-Id: 6b82fe18-1fa0-4fd2-90d5-adeac8db1d63 1 X-Request-Id: 60a44387-29fb-4463-b586-0747c123db7c 1 X-Request-Id: 5d3734d3-4cd3-4b4c-b2d1-c5c9228e8166 1 X-Request-Id: 578361cb-0afe-4d68-8c1e-1cda53274dbd 1 X-Request-Id: 525f0831-75f6-4033-a32b-20079c37ea70 1 X-Request-Id: 4f800d3d-ac1b-409e-96e4-e975d4d85cc2 1 X-Request-Id: 4aec48b3-d902-4027-a6dd-655f41dc4ab1 1 X-Request-Id: 4288b4e8-a030-434c-867f-8b6a483cbafb 1 X-Request-Id: 40311c55-54d3-48d1-b0f6-4259463bbe14 1 X-Request-Id: 39a35782-f766-4022-9fda-cbf8e50df73f 1 X-Request-Id: 32c66aa5-bd2c-466f-af19-7a8e8bcd244f 1 X-Request-Id: 30301c4a30c3928d1949b67c45a3deb2 1 X-Request-Id: 2352595b-5af7-4ac9-b255-66601c10cea5 1 X-Request-Id: 1c5f59ba-70ca-4671-adc5-338c77cf5900 1 X-Request-Id: 1a4a9346-bbed-4f2f-b6b3-a5f25433f2e4 1 X-Request-Id: 16ee37a2-0deb-462b-b579-5ee62a5da15e 1 X-Request-Id: 04caac8f-13ac-45d0-a99f-e5ecac178f76 1 X-Request-Id: 03a85f6c-b9bd-4017-8ce0-a4ae8bebead3 1 X-Request-Id: 02e2a3c6-522f-45ca-ae87-66815ae27221 1 X-Queued-Time-Spent: 0.4ms 1 X-Python-Time-Spent: 24.2ms 1 X-Proxy-Cache: MISS 1 X-Proxy-Cache: EXPIRED 1 X-Powered-By: total.js v1.9.3 1 X-Powered-By: Servlet/3.1 JSP/2.3 (GlassFish Server Open Source Edition 4.1.2 Java/Oracle Corporation/1.7) 1 X-Powered-By: Servlet 2.4; JBoss-4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)/Tomcat-5.5 1 X-Powered-By: rehash 17.05 1 X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.21 1 X-Powered-By: Phusion Passenger 5.1.2 1 X-Powered-By: Phusion Passenger 5.0.25 1 X-Powered-By: PHP/7.1.2 1 X-Powered-By: PHP/7.1.1 1 X-Powered-By: PHP/7.0.7-1~dotdeb+8.1 1 X-Powered-By: PHP/7.0.6 1 X-Powered-By: PHP/7.0.15-0ubuntu0.16.04.4 1 X-Powered-By: PHP/7.0.13 1 X-Powered-By: PHP/5.6.30-pl2-gentoo 1 X-Powered-By: PHP/5.6.30-pl0-gentoo 1 X-Powered-By: PHP/5.6.29-0+deb8u1 1 X-Powered-By: PHP/5.6.29 1 X-Powered-By: PHP/5.6.28-1~dotdeb+zts+7.1 1 X-Powered-By: PHP/5.6.26 1 X-Powered-By: PHP/5.6.24-0+deb8u1 1 X-Powered-By: PHP/5.6.24 1 X-Powered-By: PHP/5.6.15 1 X-Powered-By: PHP/5.6.14-0+deb8u1 1 X-Powered-By: PHP/5.6.10 1 X-Powered-By: PHP/5.6.0 1 X-Powered-By: PHP/5.5.9-1ubuntu4.3 1 X-Powered-By: PHP/5.5.9-1ubuntu4.19 1 X-Powered-By: PHP/5.5.35 1 X-Powered-By: PHP/5.5.33-1~dotdeb+7.1 1 X-Powered-By: PHP/5.5.30 1 X-Powered-By: PHP/5.5.15 1 X-Powered-By: PHP/5.5.14 1 X-Powered-By: PHP/5.5.12 1 X-Powered-By: PHP/5.4.42 1 X-Powered-By: PHP/5.4.41-0+deb7u1 1 X-Powered-By: PHP/5.4.37 1 X-Powered-By: PHP/5.4.36-0+deb7u3 1 X-Powered-By: PHP/5.4.36-0+deb7u1 1 X-Powered-By: PHP/5.4.34-1~dotdeb.0 1 X-Powered-By: PHP/5.4.12 1 X-Powered-By: PHP/5.3.29-0ubuntu4 1 X-Powered-By: PHP/5.3.13 1 X-Powered-By: PHP/5.3.10-1ubuntu3.25 1 X-Powered-By: PHP/5.3.10 1 X-Powered-By: PHP/5.2.17 1 X-Powered-By: PHP/5.1.6 1 X-Powered-By: PHP/5.0.3 1 X-Powered-By: LiveStreet CMS 1 X-Powered-By: Indymedia 1 X-Powered-By: HHVM/3.20.2 1 X-Powered-By: HHVM/3.11.1 1 X-Powered-By: Goddess 1 X-Powered-By: Freedom 1 X-powered-by: Freedom 1 X-Powered-By: FILE FROZR 1 X-Powered-By: DaKnObNET 1 X-Powered-By: a team of hamsters 1 X-Pingback: http://kxojy6ygju4h6lwn.onion/xmlrpc.php 1 X-Pingback: http://jf5idgu5b4ohmgd4.onion/xmlrpc.php 1 X-Pingback: http://iocn3sgeh4qpzr3y.onion/xmlrpc.php 1 X-Pingback: http://icocainpsv5u5vat.onion/xmlrpc.php 1 X-Pingback: http://gpostalfauulvzhs.onion/xmlrpc.php 1 X-Pingback: http://dgreentdiwapb3zp.onion/xmlrpc.php 1 X-Pingback: http://cleversfsg2ctqk4.onion/xmlrpc.php 1 X-Pingback: http://bumornbntwldvbjx.onion/xmlrpc.php 1 X-Pingback: http://3pq7hs3cxj7xzuqn.onion/xmlrpc.php 1 X-Pecto: Patronum 1 X-Page-Speed: 1.11.33.4-0 1 X-ob_mode: 0 1 X-Mod-Pagespeed: 1.11.33.5-0 1 X-Men: Mutatis mutandis 1 X-Memcached-Time-Spent: 8.0ms 1 X-Memcached-Queries: 3 1 X-Jenkins-Session: 209b985f 1 X-Jenkins-Session: 146f5faa 1 X-Jenkins-CLI-Port: 43581 1 X-Jenkins-CLI-Port: 39543 1 X-Jenkins-CLI2-Port: 43581 1 X-Jenkins-CLI2-Port: 39543 1 X-Jenkins: 2.60.1 1 X-Jenkins: 2.46.3 1 X-Irritate: Be irritated. 1 X-Ipfs-Path: /ipns/graffen.dk/ 1 X-Instart-Request-ID: 9908987689145856382:BEQ01-CPVNPPRY07:1499091159:1678 1 X-Instart-CacheKeyMod: desktop;NONATIVE;origin2-www.walgreens.com 1 X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAum4aa7P9GFmt7jJFpK3V8/UGXIKDSk9PbLtBVpY7PkhONUkuLnb0TaruGQoWK/h7jIvhmujT7T4cz5unrQRcbMCYrfqNWmuvsr1asoJSL93hFXX7AdNTgw5JDzwIzAKL4PtPYlcA2vtFP0O6x84cx1lDWLihNrQw8pBJOVIiC20f5XNWEzlaSoF0PatfsBuBhp8WJvDb6iLO/CAhcln8qtm1zrLtrn7do5iMIeJ8edunq3iUGHDy4tnlgaDF0mYVmwxgPsE1WVPFZMDgv6Z8fu0zP0FdgqUIkxUCV9n49DmlcfWpDThaoJi8TWqP5lq2V3WLXx+OadZvjKjIY0t/FQIDAQAB 1 X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsh2qQQo9cbkJLA670iZv2l9WIg+G1fkIJ7gSXT946qD9gd/PFzFsIG+qBWJcuQ93AX8pKKD9vfCWHQhLV8epHyKXHXGzZAsXS9CWUJVDslo853LGfbNfUMke30kyNo1bJdY6O+wHqlBfyk8RJ3bnsgIrqBfah8sJzoOA6Fxa/SfTaYq/XYEXppptbYx9qf+zYx7PWd1up4u3EnLr4cpz05sr4BbidCt86a3qnMNzBbSkbAu6xVHkDN9N2+0aliaXGfxKfYFX/1+Nyv+EbRH7aGOuznJFcMiZKoCf0atgq7L1OPWGizMgk9pIzgAH7wVM9N1BWmTF9Gged9MA33h2TwIDAQAB 1 X-Hudson-CLI-Port: 43581 1 X-Hudson-CLI-Port: 39543 1 X-Hello-Hacker: I like meeting new people. Get in touch if you want to chat. 1 X-Git-Update: 2017-06-25 22:43:19 +0000 1 X-Git-Update: 2017-05-30 07:48:29 +0000 1 X-Git-Revision: b6164e4d69fec2723eb0027db0a7b8cd4b8df8b9 1 X-Git-Revision: 681c4917929ecd0c72d955fa63b2e496cb89af9a 1 X-GEO: None 1 X-Generator: Indymedia 1 X-Future: Gopher ftw! 1 X-Frame-Options: Deny 1 X-Frame-Options: 1 X-FB-Debug: RqYw93ex/2cLweiZCjxP4V+eHkgJlANNlfsFH6vBI8FtmIhD41SoKMfYMSrMUBEnMb9e+lE5BGtUM78VyiW45w== 1 X-FB-Debug: 8OkWj28qEQLmwUlKPf+is9uU4eG0ZzRlYdrsXjD1KxfwQyYDuSrkdOvxhVdjRnUTfkfpmI312AEc/LxPESNlfA== 1 X-FB-Debug: 39CdFdD28BWWUNZUb48aDvvwCj4lczdDqtSiyVhXyfDP/Lohs7kz1feiB6efQqOYx4t0ojnuxPKBbs2k5uiiew== 1 X-Fastcgi-Cache: MISS 1 X-ExecutiveServer: 127.0.0.1,torhidden.cluster.ticktoo.net,Time=D=17831 1 X-dynaTrace: PT=176846913;PA=-1068580461;SP=Walgreen-Prod;PS=-882636849 1 X-DNS-Prefetch-Control: on 1 X-Dns-Prefetch-Control: off 1 X-DIS-Request-ID: e6f5ea7d0adc5b41e86ef661de23ccae 1 X-DIS-Request-ID: c29c4256cc108716c18d38bd15c01058 1 X-DIS-Request-ID: 9e71589fb9956695c8a6fbf2358b50de 1 X-Diaspora-Version: 0.6.99.0-p681c4917 1 X-Diaspora-Version: 0.6.6.0-pb6164e4d 1 X-Content-Security-Policy: upgrade-insecure-requests; block-all-mixed-content; reflected-xss block; report-uri https://vsund.report-uri.io/default/csp/enforce; 1 X-Content-Security-Policy: default-src 'self' 'unsafe-inline' https://cdn.tig.as https://d2p12wh0p3fo1n.cloudfront.net https://*.staticflickr.com https://ajax.googleapis.com https://fonts.googleapis.com http://*.staticflickr.com https://grtp.co https://platform.venmo.com https://fonts.gstatic.com https://www.paypalobjects.com data: 1 X-Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.google.com https://*.gstatic.com https://*.googleapis.com https://*.google-analytics.com https://assets.zendesk.com https://connect.facebook.net https://cdnjs.cloudflare.com https://cdn.jsdelivr.net https://*.keycaptcha.com https://platform.twitter.com; img-src 'self' https://*.google-analytics.com https://*.googleapis.com https://*.tapatalk-cdn.com https://tapatalk.com https://www.google.com https://www.google.com.ua https://www.google.ru https://www.google.be https://www.google.md https://*.gstatic.com https://stats.g.doubleclick.net https://s-static.ak.facebook.com https://assets.zendesk.com https://*.keycaptcha.com https://www.facebook.com https://syndication.twitter.com; style-src data: 'self' 'unsafe-inline' https://*.googleapis.com https://assets.zendesk.com https://maxcdn.bootstrapcdn.com; font-src 'self' https://themes.googleusercontent.com https://maxcdn.bootstrapcdn.com https://fonts.gstatic.com; child-src 'self' https://*.youtube.com https://accounts.google.com https://vk.com https://fonts.gstatic.com https://assets.zendesk.com https://www.facebook.com https://staticxx.facebook.com https://tautt.zendesk.com https://*.keycaptcha.com https://www.google.com; object-src 'self' https://*.keycaptcha.com https://platform.twitter.com https://www.google.com; connect-src 'self' https://*.google-analytics.com; report-uri https://psylab.report-uri.io/default/csp/enforce; upgrade-insecure-requests 1 X-Content-Security-Policy: default-src 'self'; script-src 'none'; frame-src 'none'; object-src 'none'; style-src 'self' 'unsafe-inline' 1 X-Content-Security-Policy: default-src 'self' ;options inline-script eval-script;img-src 'self' data: *.tile.openstreetmap.org *.tile.opencyclemap.org ; 1 X-Content-Security-Policy: default-src 'none'; img-src 'self'; style-src 'self' 'unsafe-inline' 1 X-Content-Security-Policy: allow 'self'; 1 X-Content-Options: nosniff 1 X-Contact: BM-Bc7Rspa4zxAPy9PK26vmcyoovftipStp 1 X-Clearnet-URL: https://l.daknob.net/ 1 X-Cache-Status: HIT 1 X-Cache-Status: EXPIRED 1 X-Cache: MISS from proxy.rutracker.org 1 X-Cache-Lookup: MISS from proxy.rutracker.org:3128 1 X-Cache-Hits: 3 1 X-Cache-Hits: 1 1 X-Cache-Hits: 0 1 X-Bitcoin: 1SniffrSX5qDL5HinYvzAxQFuyTd68DBc 1 X-Bender: The modern world can bite my splintery, wooden ass! 1 X-Aspnetmvc-Version: 5.2 1 X-AspNetMvc-Version: 4.0 1 X-Aspnetmvc-Version: 4.0 1 X-Akamai-Native: NO 1 X-Akamai-DeviceType: desktop 1 X-Akamai-DeviceOS: Windows 7 1 X-A: 050-conf 
submitted by angstyhooker to onions [link] [comments]

Zeus/Gaw ASIC Setup Guide for Linux/Raspberry Pi

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

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

Resources

About Cyrptocurrencies and Their Jargon

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

Linux

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

Computer Setup

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

Desktop/Laptop

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

Raspberry Pi

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

Miner Setup

Installing BFGMiner

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

Running BFGMiner

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

Start on Boot

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

Power Failure

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

Sources

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

Wrap Up

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

How To Mine Doge with Ubuntu 13.10. (Part 1, for AMD Graphics Cards)

I feel the community really needs a resource like this. Because if I had a Doge for every-time taught a newbie how to Mine on Ubuntu, I would be a very rich doge!
EDIT: Sorry if it looks funny, Reddit doesn't like the numbers I put in for some reason.
If you have Ubuntu you have likely not upgraded because you think you cant mine on 13.10, and while that has been true in the past, a few people have got it figured out. So feel free to upgrade. If you are not on Ubuntu, Seriously you should consider using it. Even if its just on an older desktop.
Alright, so lets get a few things clear, I am assuming that you just FRESHLY installed Ubuntu 13.10 x64 on your system. I am assuming that you have no drivers, and no miners. You will need at least a key board and a mouse. The guide will be done in several parts, this first part is for most AMD Graphics cards. If you have an Nvidia, or just want to mine with your CPU, please check back later for those guides!
When reading this guide, please remember that as I give you commands to type into the terminal, Anything between { and} must be included. Do not copy and paste the {}.
Lets get started, If you have not already done so, Install Ubuntu 13.10 64Bit From Here (http://www.ubuntu.com/index_asus.html)
*1. Lets start by making sure you are up to date. Open up the terminal and enter this:
{sudo apt-get update && sudo apt-get upgrade} 
Let that run for a bit.
*2. Once that has finished we are going to download some applications we will need:
{sudo apt-get install dh-make dh-modaliases execstack libxrandr2 libice6 libsm6 libfontconfig1 libxi6 libxcursor1 libgl1-mesa-glx libxinerama1 libqtgui4} 
*3. Once that has run its course we are going to install the ssh server. Remember this command is going to make your computer shut down. While it is shut down, carefully install your graphics cards. If you don't have any experience with this, I suggest you 3 minutes to watch this guide, because failure to install a graphics card the right way can destroy it.
(http://www.youtube.com/watch?v=O9x097QRXeA)
{sudo apt-get install openssh-server sudo shutdown now} 
*4.Install your Card(s) and turn the computer back on.
*5. Make a new folder called "AMD DRIVERS123" inside of your download folder. Downoad the following 3 things into that folder. (1. AMD Drivers: http://support.amd.com/en-us/download/incomplete) (2. AMD APP SDK: http://developer.amd.com/tools-and-sdks/heterogeneous-computing/amd-accelerated-parallel-processing-app-sdk/downloads/) (3. AMD ADL SDK:http://developer.amd.com/tools-and-sdks/graphics-development/display-library-adl-sdk/)
*6. Ok, now we need to unzip and compile those drivers. So, open a terminal my right clicking inside of "AMD DRIVERS123". The enter this:
{unzip amd-catalyst*.zip chmod +x amd-catalyst*.run} {sudo ./amd-catalyst*.run --buildpkg Ubuntu/saucy} 
*7. Now we need to install the drivers. Enter the code exactly as you see it, don't worry, the first command will fail, we are expecting it too.
{sudo dpkg -i fglrx*.deb} {sudo apt-get -f install} {sudo dpkg -i fglrx*.deb} {sudo reboot} 
Your computer should now reboot.
(If this failed, you probibly need to remove the old drivers. Do this
{cd /etc/default sudo pico grub} 
Change the line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" 
Now save by pressing [CTRL+x]
{sudo update-grub} this will make the change perminent. {sudo reboot -n} Reboot with new settings. Once it starts back up try installing the new drivers again.) 
*8.GREAT! You are really on a roll! Now we need to update AtiConfig
{sudo aticonfig --initial --adapter=all} 
*9.Time to install the APP ADK:
{tar xvf AMD-APP-SDK*.tgz} {sudo ./Install-AMD-APP.sh} {sudo reboot} 
*10. WOOT! You are so close to diggin that sweet Doge!! Its time to download CGMiner. IMPORTANT NOTE! You need to get CGminer 3.7, IT IS THE ONLY ONE THAT WILL WORK. Do not get any older or newer, Just this. :
{sudo apt-get install git unzip git clone -b 3.7 https://github.com/ckolivas/cgminer} 
*11. Ok, now go back to "AMD DRIVERS123", Unzip AMD SDL SDK 6.0. Once you have it unzipped, go the file called "include", open it up, copy everything inside, then go find CGminer. Copy these files into the CGminer file called ADL_SDK.
*12. To install CGminer, we are going to need a few things. Get all of these.
{sudo apt-get install build-essential autoconf libtool libcurl4-openssl-dev libncurses5-dev pkg-config libudev-dev} 
*13. Lets go ahead and compile CGminer.
{cd cgminer} {./autogen.sh} 
*14. Ok, when you did that, it told you GPU was not supported, time to fix it.
{./configure --enable-opencl --enable-scrypt} 
(if you did it right you should now get this: OpenCL...............: FOUND. GPU mining support enabled scrypt...............: Enabled ADL..................: SDK found, GPU monitoring support enabled)
*15. If everything has been good so far then
{make} 
*16. MATHEMATICAL! Now lets get it set up to run a test.
{nano test.sh} {!/bin/bash export DISPLAY=:0 export GPU_MAX_ALLOC_PERCENT=100 export GPU_USE_SYNC_OBJECTS=1} {./cgminer -n} 
*17. Now save by hitting [Control+x][y][Enter]
*18.Lastly lets CHmod test.sh
{chmod+x test.sh} 
*19. TIME TO RUN THE TEXT!!!
{./test.sh} 
(If your output looks like this your ready to go!!! CL Platform 0 vendor: Advanced Micro Devices, Inc. CL Platform 0 name: AMD Accelerated Parallel Processing CL Platform 0 version: OpenCL 1.2 AMD-APP (1214.3) Platform 0 devices: 1 0 Tahiti GPU 0 AMD Radeon HD 7900 Series hardware monitoring enabled 1 GPU devices max detected)
*20. Excellent! Now we have it installed, its time to pick 2-3 pools, and get accounts set up at each of them. I currently use These 2, and If I find another I like I'll update. If you have a really awesome pool you would like me to include on the list, feel free to message me.
Pools: http://doge.cryptovalley.com/ (great community, server not super stable, but they have a chat. I hang out here a lot under the handle 'StrongBad' feel free to stop buy and ask questions)
https://dogehouse.org/ (Super stable pool, Great contests, super friendly, and they pay your miner a bonus if you find the block!)
Choose your pools, go to their sites and sign up. VERY IMPORTANT!!! Use different usernames and passwords for every mining site. If one site gets hacked, you don't want to give them a way to steal everything!!!!! Don't worry about the worker names and passwords being unique or complex tho, the most they can do with this is mine for you.
*21. Ok, now go to the CGminer folder, and open up a Terminal Window.
{sudo ./cgminer} 
This should start ./cgminer up with some really basic settings, and not pointed at any pool. Lets fix that: First press [p] to go to pool settings Now [A] and enter the information for the 1st pool. For instance if you are signing on for dogehouse: (Input server details: stratum+tcp://stratum.dogehouse.org:3333 Username: 'yourusername.workername password: 'yourpassword') If you got no errors, you did it right! Your miner should now connect and start to mine very slowly.
Now, do the same thing for all your other pools. the reason we do this is because Doge Coin pools are constantly being DDoS attacked, and this way your worker automatically switches over to a good pool if one go's down.
*22. time to save your current settings press [Enter] to get back out to the main menu, then [s] to bring up settings. Now press [W] to write a Config file. Name it DogeCoin.conf, and make sure to save it in the location it directs you too.
*23.OK! So, now we have everything set up to its basics. What you need to do now is sit down, and fine tune your Card(s). Its really early in the morning, and I need to get some sleep, I will add more on how to tune your card tomorrow in another post, and link it HERE:
Or, I will help you find the best configuration for your card(s). However as this is quite a bit of work, I do charge a small fee. Contact me with your card(s) information and I will get back to you right away. I generally let you decide how much to pay me.
This is my first ever guide on reddit! If you enjoyed it, or if it helped you please remember to upvote! I am going to start doing an educational YouTube series about Bitcoin, and will likely be doing a side program about Doge, if I find time and funding!! You can find that here: All tips are appreciated! DPTwcQreASwzt6TeWBWFb6Kz9ZU5Sezvr9 If you have any Questions, feel free to ask, I will get back to you ASAP.
Happy Digging everybody!
submitted by Sonofchange to Dogecoinmining [link] [comments]

12-02 22:02 - 'bitcoind unable to start ~NEED HELP' (self.Bitcoin) by /u/Light_of_Lucifer removed from /r/Bitcoin within 122-132min

'''
Bitcoin Client Software and Version Number: Bitcoin Core 0.15.1
Operating System: Ubuntu 16.04
System Hardware Specs: 2.4 GHz Intel Core CPU with 16 GB RAM, 250GS ssd boot & 750 hdd gb storage hub.
Description of Problem: bitcoind refuses to start up. Keep getting the same error over and over.
Screenshot of the problem: [link]1
debug.log: [link]2
bitconi.conf: [link]3
Hello everyone. I have been running my own full node for a few weeks now. Ive been in the space for a long time but just recently started to get into developing on bitcoin. I turn off my node at the end of each day, I just use it to practice coding. A few days ago I was no longer able to start bitcoind because of this error
EXCEPTION: N5boost10filesystem16filesystem_errorE boost::filesystem::space: Operation not permitted bitcoin in AppInit()
I tried to -reindex and -reindex-chainstate but then bitcoind is stuck on block 0..... I have found virtually no resources on line to help me with this issue. Bitcoin is saved on my ssd home folder and the data direction is on my hdd storage folder located within media. ANY help is welcomed. Thank you
'''
bitcoind unable to start ~NEED HELP
Go1dfish undelete link
unreddit undelete link
Author: Light_of_Lucifer
1: https://imgur.com/pj2KFrh 2: https://pastebin.com/2LCw5BJt 3: https://pastebin.com/ZsQArYRy
submitted by removalbot to removalbot [link] [comments]

[uncensored-r/Bitcoin] bitcoind unable to start ~NEED HELP

The following post by Light_of_Lucifer is being replicated because the post has been silently removed.
The original post can be found(in censored form) at this link:
np.reddit.com/ Bitcoin/comments/7h4tkf
The original post's content was as follows:
Bitcoin Client Software and Version Number: Bitcoin Core 0.15.1
Operating System: Ubuntu 16.04
System Hardware Specs: 2.4 GHz Intel Core CPU with 16 GB RAM, 250GS ssd boot & 750 hdd gb storage hub.
Description of Problem: bitcoind refuses to start up. Keep getting the same error over and over.
Screenshot of the problem: https://imgur.com/pj2KFrh
debug.log: https://pastebin.com/2LCw5BJt
bitconi.conf: https://pastebin.com/ZsQArYRy
Hello everyone. I have been running my own full node for a few weeks now. Ive been in the space for a long time but just recently started to get into developing on bitcoin. I turn off my node at the end of each day, I just use it to practice coding. A few days ago I was no longer able to start bitcoind because of this error
EXCEPTION: N5boost10filesystem16filesystem_errorE boost::filesystem::space: Operation not permitted bitcoin in AppInit()
I tried to -reindex and -reindex-chainstate but then bitcoind is stuck on block 0..... I have found virtually no resources on line to help me with this issue. Bitcoin is saved on my ssd home folder and the data direction is on my hdd storage folder located within media. ANY help is welcomed. Thank you
submitted by censorship_notifier to noncensored_bitcoin [link] [comments]

Bitcoin JSON-RPC Tutorial 3 - bitcoin.conf Ubuntu Coin Wallet How to Install Bitcoin Core Wallet on Ubuntu 16 Ubuntu -1 Setting up Bitcoin How to Bitcoin Miner with Ubuntu VPS - Setup Nicehash Miner via Ubuntu VPS

This is on Ubuntu-16.04, 64-bit where bitcoin was installed via PPA. Yes; I am working with Bitcoin code for the first time. Yes; I am working with Bitcoin code for the first time. bitcoind ubuntu bitcoin.conf Note that for Windows the location of the configuration folder where bitcoin.conf is located is saved in the registry. Its default path is indeed C:\Users\<username>\AppData\Roaming\Bitcoin but if that location was changed then in order to find the current folder you will have to look in HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt at the REG ... "C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe" -datadir=d:\BitcoinData Start Bitcoin, now you will see all the files are created in the new data directory. 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: Provided by: bitcoind_0.3.24~dfsg-1_amd64 NAME bitcoin.conf - bitcoin configuration file SYNOPSIS All command-line options (except for '-datadir' and '-conf') may be specified in a configuration file, and all configuration file options may also be specified on the command line. How To crypto exchange without verification Install Bitcoin Core on Ubuntu linux bitcoin conf location Bitcoin.conf) -daemon Run in the background as a daemon and accept commands -datadir= Specify data directory -dbcache= Set database cache size in megabytes (4 to 1024, default: Bitcoin Configuration File (bitcoin.conf) – Ishwar Chandra ...

[index] [34463] [17394] [10586] [30854] [18096] [20469] [17672] [28672] [6351] [20053]

Bitcoin JSON-RPC Tutorial 3 - bitcoin.conf

In this video, we show you how the Ubuntu Coin Wallet works! #ubuntucoin #buy #digital #gold #blockchain #movement. Ubuntu -1 Setting up Bitcoin Commands, sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install bitcoin-qt sudo apt-get install bitcoind sudo blkid sudo nano /etc/fstab ... Bitcoin JSON-RPC Tutorial 3 - bitcoin.conf - Duration: ... m1xolyd1an 13,513 views. 8:10. Bitcoin Mining on Ubuntu 18.10 - Bitcoin Mining Software 2019 ... Location: United States Restricted ... This video covers the method to install BitCoins on Ubuntu 16.04 Bitcoin is a virtual and crypto-currency created by Satoshi Nakamoto. For more explanation o... Bitcoin JSON-RPC tutorial. Set up your bitcoin.conf file and create custom settings with bitcoind. BTC: 1NPrfWgJfkANmd1jt88A141PjhiarT8d9U.

#