software installation - How do I install Bitcoin in Ubuntu ...

Is installing and compiling libraries as extremely frustrating and impossible for others as it is for me?

I don't know if it's my unconventional programming setup (VirtualBox Ubuntu 18), but I have never been able to simply follow the steps to compile a project or application without major problems happening.
Here are all some examples from me trying to build openpose tonight. It's what prompted me to make this post:
  1. Cmake must be updated because, for some reason, the default apt-get cmake is still the version from 2017!
  2. I had to specifically install python3.7-dev instead of python 3.6-dev even though everyone builds openpose with python3.5-dev (which I couldn't install).
  3. I had to mix and match commands from three different tutorials because following just one of any of them resulted in errors.
  4. Openpose would not compile because there was a typo in one of the third-party libraries that I found out only after diving deep into github. I had to vim and manually edit the source code to fix this one.
This sounds a bit whiny, and it may just be only to whine. But is this really how major packages are dealt with?
This is just one example, a month ago I spent a whole day just to compile a library by Google called mediapipe. In between these examples have been dozens of other libraries and packages where following the instructions was not sufficient and I needed to dive deep into terminology way above my head to try and debug some stupid problems and it seems to not be getting easier with time.
It just seems like such a major headache and the solutions are so arcane that I can't fathom how anyone even came up with them? It just looks like: Oh, simply apt-get llldldlepellelpv=3.5 the lllldldldelep3.5.1 has the bug on line 3,884 and then copy it into this other directory and make sure it's not done past 2PM otherwise you also have to meet this dependency by sacrificing your 3rd most valued possession by chucking it out of the 4 story apartment (incompatible with non-4-story apartments). This result will then be the 5th post on stack overflow and the only one that works. The others just reiterate the exact things you've already tried in judgemental tones or just go off the deep end completely with some insane-tier fixes, including running overcomplicated batch scripts they made which who knows what they do other than probably remotely install a bitcoin miner.
Plus not to mention that I'm trying to code with some of my classmates and the outcome of each of our slightly different setups results in every possible combination of bugs. No single set of instructions will make a major library compile on all of our ubuntu setups.
The setup of libraries (not even talking about incorporating them into my own project so that mine will compile alongside them) is just an extremely frustrating process. What are the secrets to doing it right and being able to know which magic commands fix the bugs?
submitted by Ari2010 to learnprogramming [link] [comments]

Zoin Basics: A Beginner’s Guide to Obtaining Zoin

Welcome to Zoin! We want to start by thanking you for joining our amazing community. Zoin is a community-governed decentralized digital currency with privacy features (based on the Zerocoin protocol) and is developed by a diverse team from all around the world. There is no pre-mine and no founder’s reward for Zoin; additionally, it is strictly CPU-minable (see mining section below). Together, these features ensure fairness and transparency to everyone interested in obtaining Zoin. Through this guide you will learn about the current methods of acquiring Zoin for yourself.

How to Earn / Buy Zoin

Right now, there are two ways you can obtain Zoin. You can either use the Bitcoin/Zoin trading pair on Cryptopia exchange or you can mine for Zoin using your own hardware.

Method 1: Trading Zoin on Cryptopia

To start, the easiest way to buy a cryptocurrency such as Ethereum or Litecoin is through Coinbase, where you can buy up to $500 worth of Litecoins (for example) using a credit card before you need to verify your identity. Coinbase accepts buyers from 33 countries across the world. A simple guide from Coinbase on buying Litecoin (or Ethereum) with your bank account / credit card is all you need to get started.
Once you have purchased either Litecoin or Ethereum (or another altcoin) you may login to Cryptopia exchange, after you’ve created an account. You must create a deposit address for the same coin that you previously bought on Coinbase or another exchange by clicking deposit under your account, and then typing the name of the coin you wish to deposit. This will generate an address for your Cryptopia trading wallet to receive coins. You can either copy / paste the address (never type it yourself without verifying it), or scan the QR code if you are sending from a mobile wallet.
Once you make a deposit to your Cryptopia wallet address you must wait for several confirmations before your funds are trade-able on Cryptopia. This usually takes around 30 minutes.
When the deposit is confirmed you may go to the Exchange Market section of Cryptopia and search for the coin you just deposited. Once you are there, create a sell order and wait for someone to buy it, or choose a buy order for the coin to trade it for Bitcoin right away. Since you just purchased your cryptocurrency, the price probably won’t be very different than when you bought it, but this depends heavily on the current state of the market. Look up how much the current buy orders are (in your country’s currency), if it is close to the price you bought it at then you can sell at that price. Remember, a sell order may not be filled right away, but choosing someone’s buy order will sell it to them instantly.
If you have successfully traded your altcoin for Bitcoin on Cryptopia, you may now use your Bitcoin to buy Zoin. You can buy Zoin through a buy order of your own (bid) or a sell order from someone else; again, this is entirely up to you and how you anticipate the market / price of coins.
Congratulations, you have successfully bought your first Zoin!
The next step is to transfer the Zoin you bought to your own personal Zoin wallet. To do this, download the wallet on your preferred platform and after installing and running the wallet for the first time, wait for the blockchain to fully sync.
  1. Close your wallet (if it’s open).
  2. Delete the following folders from %appdata% on Windows or Library/Application Support/Zoin on Mac: Blocks, Chainstate and the file peers.dat
  3. Download the latest blockchain file, extract using 7Zip or your preferred program.
  4. Paste the newly downloaded folders: Block, Chainstate and file peers.dat in ZOIN folder under %appdata% on Windows or Library/Application Support/Zoin on Mac
  5. Open the wallet and wait for it to synchronize. This should take less time than downloading the entire blockchain and syncing from scratch. The process should take around 30 minutes.
Go to the Receive tab and click on your address, then choose Copy Address. Paste that address on the Cryptopia withdraw page for Zoin and confirm that you want to withdraw. In a few minutes, your Zoin will show up in your wallet (it will be confirmed after 6 confirmations).
After your wallet is up to date and you’ve added some of your coins to it, you will want to make it safe in case something happens.
The first thing you want to do is to encrypt it. You can do this by clicking on Settings Encrypt Wallet
You should type in a passphrase that is safe and that you will remember, confirm this passphrase and proceed to encrypt your wallet.
Please be advised, once you set your passphrase you can’t forget it or all your funds will be lost!
Right after your wallet has been encrypted, you should make a backup of it. Click on File Backup Wallet and save the wallet as a wallet.dat file
If you want to open your wallet on another computer you may save the wallet file onto a flash drive or other backup device / method you may already have. Remember that if you encrypted your wallet before doing this backup you must know the passphrase in order to access your wallet.
Another way of recovering your wallet is by finding the private key for the wallet. This can be done in the wallet debug terminal (advanced). For accessing your wallet private key, you must do the following procedure:
If your wallet is encrypted: Click Help Debug Window Console (tab). In the console window, use the command walletpassphrase first:
walletpassphrase "YourPassphrase" 60 
Where "YourPassphrase" is the passphrase you used when you encrypted your wallet and 60 is the amount of time you want to unencrypt your wallet for (in seconds).
Next, use the dumpprivkey command in the following form:
dumpprivkey "wallet address" 
Replace "wallet address" with your own wallet address.
After entering these commands, you will receive your private key.
You may now write down and save this private key.

Method 2: Mining Zoin

The second way of obtaining Zoin is to earn it by mining, using your own hardware and a mining pool server (we recommend the official pool). Mining Zoin is possible with any modern computer as long as it has a CPU.
To start mining you need to have an account in a “pool”; this is a place where several computers (also known as workers) connect together to mine the blockchain. As we mine the blockchain, we find blocks which contain a reward (currently 12.5 Zoin) which is shared by the number of total miners depending on each person’s mining hashrate. The better your hardware is, the more Zoin you will receive from mining.
To get started, visit our official pool and create your mining account.
You will need to set up a worker. This is your mining device which should be assigned a name and password in order for the network to distinguish your mining rig from others. To do this, visit the Workers page.
The Username must be set for as many workers or computers you want to set up. For example, if the username you chose when signing up to our pool was “john123” and you set your first computer name to worker1. Then your username and worker will be: “john123.worker1”. If you set a second worker as worker2, your second worker name will be “john123.worker2” and so on. The password will be whatever you choose under the password that box, the password can be the same for all the workers.
Mining on Windows:
Now that your workers are set, you can go ahead and download mining software, which you can get from the Resources page of the official pool.
Once you have the mining software, open the compressed folder by extracting its contents and create a batch (.bat) file which will contain all the info necessary to mine Zoin into your account. To do this, open a text editor such as Notepad and save the file as .bat instead of .txt
This batch file must contain just one line:
cpuminer-aes-avx2.exe -a lyra2zoin -o stratum+tcp:// -u username.workername -p workerpassword 
cpuminer-aes-avx2.exe is the .exe file that you want to use, it depends on your CPU.
Lyra2zoin is the algorithm used by Zoin, that should remain the same.
stratum+tcp:// is the link to the official pool.
username.workername should be the username you set. (Example: john123.worker1)
workerpassword is the password you set for each worker.
Once you set this batch file, you can run it by double-clicking on it.
Note: Make sure that your Firewall / AV program isn’t blocking cpuminer-aes-avx2.exe or the .bat file in order for it to run successfully.
Mining on Linux (Advanced):
Type the following into the terminal one line at a time:
sudo chown -R $USER: $HOME 
sudo apt-get update 
sudo apt-get install automake autoconf pkg-config libcurl4-openssl-dev libjansson-dev libssl-dev libgmp-dev -y 
sudo apt-get install autotools-dev automake make libcurl4-openssl-dev g++ libssl-dev libgmp3-dev -y 
sudo apt-get install build-essential screen automake m4 openssl libssl-dev git libjson0 libjson0-dev libcurl4- openssl-dev autoconf python-software-properties -y 
sudo git clone 
cd cpuminer-opt 
./cpuminer -a lyra2zoin -o stratum+tcp:// -u USERNAME.WORKERNAME -p x -t x 
Replace USERNAME.WORKERNAME with your unique pool username and workername
Mining on Mac OS:
  1. Download and install Docker Community Edition
  2. Visit the Zoin Official Pool and create your mining account
  3. Setup a Worker
  4. Edit the line below to match your pool configuration:
docker run hmage/cpuminer-opt -a lyra2zoin -o stratum+tcp:// -u USERNAME.WORKERNAME -p x 
hmage/cpuminer-opt is the miner that will be used by docker.
Lyra2zoin is the algorithm used by Zoin, that should remain the same.
stratum+tcp:// is the link to the official pool.
USERNAME.WORKERNAME should be your unique username and workname (Example: john123.worker1)
If Docker up and running, open Terminal on your Mac (Command + Spacebar and type "Terminal") and paste the line you created. Docker will proceed to download the necessary programs and start mining right away. If you can see the Accepted green message you are mining and you can check all of the mining stats and your earnings from the pool on the main page.
Happy mining!
submitted by Bluish91 to zoinofficial [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:
Register Microsoft Key’s & Install Their repos:
cd /tmp wget -q 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:
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 # “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:

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] 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!
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:]: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:]: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 (, 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 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: 
It should look something like this:
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:
Hit the “Try it out” button which then prompts you for 2 fields:
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:
So now we have our mnemonic, its time to generate the wallet, for this we need to use the API:
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:
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!!
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.

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!
You can check its loaded by going back to the API and executing the following command:
Or execute the following command on the NODE:
curl -X GET "" -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:
Fill in the Wallet name which is “TestWallet” (in this example) and “account 0” (which is the first/default account):
Hit execute and you should have an x42 address within the “Response Body”:
BOOM… ok now we can receive funds! 😊

Step 7 - Check TX History

Go to the API and the following call:
The 2 fields we are most concerned about are:
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:
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: 
this will allow you to easily see all TX’s associated with this address, it should look something like below:
… 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
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
  • If you use the installer, its quick and easy.
  • 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
  • You only run the UI, the x42 node is not installed
  • you dont have a superfluous node running, downloading blocks on your local system
  • 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, 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:

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:
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:
... DONE!

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


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:
Next you need to install NodeJS, download and install the package:
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;

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 
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..
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..
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:

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]

[TUTORIAL] Turn your $35 Raspberry Pi into a 21 Bitcoin Computer! (original post deleted)

I noticed that ButtcoinEE deleted his own tutorial from here, and I liked the information provided, so I'm reposting it for others who may not have it saved.
I haven't tested his tutorial on my own RPI yet, but if anyone wants to give it a go, I can update this as needed.
Below is the post directly quoted from OP:
You get your brand new RPI and
curl | sudo bash 
Congratulations, you just saved $365. That's all there is to it.
Just want the python library and not the other stuff?
wget dkpg -i two1_1.0.0-1_all.deb 
This will work on any computer, or if you want you can extract it and just use the python library without installing.
Not an honest option, not everything works and I would be essentially forking. This is not an honest comparison, but it's closer!
You're posting directory dumps and talking about how easy it is to create your own 21 computer, yet don't know what a fork is? You just lost all credibility.
What is forking?
The software would need to be forked to work on whatever miner you attach to RPi. It's not plug and play bro and the nice folks at 21 Inc won't support your kludge.
From their code:
SupportedMiners = collections.OrderedDict([ ("rpi2miner", minerhal.RPi2Miner), ("cpuminer", minerhal.CpuMiner), ]) 
It's supported operation in the code supplied by the company.
That is not honest given that you cannot reproduce everything that the 21 Bitcoin Computer can do right now. You don't have the integrated framework. You would be doing something very different and that is not an honest comparison.
The script linked is literally what sets up the 21 Bitcoin Computer, it's identical in software in every way.
submitted by ecafyelims to Bitcoin [link] [comments]

Bitcoin, dogecoin. How I tried to make my fortune in 2014 with the sweat of my computer.

Bitcoin, dogecoin. How I tried to make my fortune in 2014 with the sweat of my computer.
Make money just by working on your computer: the rise of electronic currencies, in the wake of bitcoin, can be a little dream, especially in times of crisis. We tried the experiment. Wealth at your fingertips? Not for everybody.
Reading time: 6 min.
We have known at least since March 2013, with the soaring Bitcoin (BTC) price during the closing of Cypriot banks: electronic currencies, it has not much virtual. Since the creation of the enigmatic Satoshi Nakamoto serves as a safe haven, a playground for speculators, interests the States and even makes it possible to pay for his trip to the space where his beer, bigger world would dare to pretend that it only serves to buy prohibited substances on SilkRoad - if it ever was.
At the end of November, James Howells was mocked a lot, this Brit, caught in a household frenzy, inadvertently threw a hard disk containing 7,500 bitcoins, the equivalent of 4.8 million euros. A small fortune now lost in the depths of the Docksway dump near Newport. Nevertheless, before causing the consternation of the global Internet, Jamie still had the nose to undermine the BTC at a time when the experience mobilized a handful of hardcore geeks.
Since the rise (sawtooth) bitcoin, each unit currently weighs more than 800 dollars, nearly thirty cryptocurrencies have emerged. Is it possible, this year again, to let this promising, volatile and risky train pass, or to fall into
  1. Choose your electronic motto.
  2. All are based on the same principle: to summarize (very) big features [1], the issuance of money is governed by an algorithm, and the new corners put in circulation reward the resolution, by participants in a network of peer and mathematical problems, including the validation and archiving of transactions, which are public [2]. Mining a cryptocurrency is like putting the computing power of your computer in the service of the network.
  3. Since the program is decreasing [3], the mining becomes more and more difficult with time (and with the increase of the number of participants): to hope to make his pelote via the only computational activity, one must either have to at its disposal a large fleet of machines, to be a miner from the first hour. Exit the bitcoin, long since out of the reach of a personal computer.
  4. I similarly gave up the litecoin and peercoin, already well launched (they date respectively 2011 and 2012), to set my heart on one of the most recent currencies - and certainly the hippest of the moment: the dogecoin.
  5. As its name suggests, the cryptocurrency favorite Shiba Inus from around the world is a tribute to the Doge, one of the most famous memes of 2013, with its captions in Comic Sans, the font most sorry for the web. A geek joke, therefore, except that - the unfathomable mysteries of the Internet - its value jumped 900% in the third week of December, and she suffered a Christmas robbery online.
  6. Admittedly, at the time when these lines are written, the dogecoin caps at 0.00023 dollars [4] - its quite ridiculous (and quite depressing), but even if you bet on the future, so much to go frankly.
  7. 2. The hands in the engine the billboard.
  8. From there, things get tough (a little). Installing an electronic purse on ones computer is not very complicated (the software is available for Windows, MacOS, Android or, for the more adventurous, on a repository to compile under Linux). It is also possible to use an online wallet, but it is more risky (except, perhaps, when one is called James Howells). When opened for the first time, the purse automatically synchronizes with the Dogecoin network (be careful, it can be long), which gives you a payment address (we can generate more later).
  9. The two most common ways to undermine electronic money are to use the computing power of the computers microprocessor (CPU) or, more efficiently, that of the graphics card processor (GPU). In the first case, the program is simple to install; in the second, it is necessary to choose the most adapted to its material [5]. There are, thankfully, a lot of online tutorials. Still, to operate the corner board requires in all cases to trade the comfort of the GUI for aridity, so confusing to the layman, command lines - we have nothing for nothing.
  10. Finally, at work alone, we prefer collaboration. Mining is best done in groups, or rather in pool: it distributes the gains, of course, but also the difficulty. For the dogecoin as for all the crypto-currencies, the pools are numerous. A quick tour of a dedicated section of the Reddit community site can help you make your choice.
  11. 3. Extension of the field of struggle.
  12. And after? After, we can rest, since it is the machine that works. But the truth of a cryptocurrency - even at the exceptionally high LOL and LOL rates of the Shiba Inu - is cruel and brutal: not all computers are equal. Or rather, some are more equal than others. For while you heat your CPU or your graphics card to grapple some unfortunate corners, others will sweep the game thanks to specialized integrated circuits, computing capabilities much higher.
  13. If the game of buying and reselling corners is basically just another stock exchange mechanism, less the intervention of the central banks - what is at stake, and the big political question they ask: are we certain to prefer speculation pure and perfect to monetary policies, however questionable they may be? -, production, it is the law of the strongest (in calculation). There are even lethal weapons at $ 10,000 each, with which your processors are like mosquitoes in front of an A bomb.
  14. And if you think it does not matter because after all, it does not cost you anything, think again: the components, like humans, wear out faster when they work at full speed, and the bill of electricity can quickly grow. The profitability of the case is anything but certain, as evidenced by the results of online calculators. (Needless to say, our laughing dogecoin does not stand up to this kind of simulation.)
  15. Much more boring, from a collective point of view: the carbon footprint, current and above all expected, of electronic currencies worries more and more. Last spring, Bloomberg estimated that the energy consumption of the Bitcoin network was equivalent to that of 31,000 US households. Not sure, according to the site, that their emission is less damaging to the environment than have been some physical currencies.
  16. For exciting to analyze that is the emergence of cryptocurrencies, it is better to ask now about their cost, economic and ecological. To see it as a potential source of income, except for being a very early adopter with a hollow nose, an individual with a lot of computational capital or a clever trader, you have to make a point.
  17. If the recurrent comparison with the famous Ponzi pyramid [6] is discussed (after all, the decentralized currencies do not make promises), remains that, as long as the value does not collapse, the system benefits mainly to the first entrants - except James Howells.
  18. As the site aptly states: all this is just an experiment, invest only the time and money you can afford to lose. LOLs love was not a worse reason than another to experiment, so I finally submitted my laptop to four days and three nights of intense activity, which makes me happy. owner of a good half a thousand dogecoins. Either the equivalent of 0.115 dollar, or 0.08 euro. It is obviously not worth the electricity consumed to generate them, it increases my carbon footprint, but it amuses my entourage. But laughter is, as everyone knows, a safe bet in times of crisis, less volatile than a real bitcoin.
  19. And then, after all, you never know.
  20. Amaelle Guiton.
  21. 1. For explanations more provided (the case is quite complex), refer, for example, to the series of very detailed notes devoted to blogger Turblog.
  22. 2. And as such, searchable by everyone. It is the identity of the users that is not known, unless they reveal it, hence the reputation of anonymity (relative, therefore) cryptocurrencies.
  23. 3. In the case of bitcoin, the maximum of 21 million units should be reached around 2140.
  24. 4. For a day-to-day follow-up, see the CoinMarketCap site which lists the exchange rates of crypto-currencies, based on the dollar value of bitcoin.
  25. 5. We discover then, unfortunately, that some graphics cards do not allow the mining. This is the case for the author of these lines, reduced to working in conditions of extreme computer deprivation.
  26. 6. Comparison which is at the heart of a hilarious note on the ponzicoin, signed by the economic journalist Matthew OBrien, on The Atlantic (to read if you intend seriously to invest in the dogecoin).
submitted by Mejbah411 to u/Mejbah411 [link] [comments]

How to Mine BiblePay on Linux

This guide is outdated, please refer to:
IMPORTANT - Evolution Upgrade:
Quick Start
Evolution Upgrade Information
Getting Started with Evolution
Generic Smart Contracts
What is BiblePay Evolution?
Recommend 2GB RAM or can get stuck compiling (if 1GB RAM can use Swap File) Use Ubuntu 16.04
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 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 .. ./ #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: # 

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 

cd src ./biblepayd -daemon 
Your GUI program will be located in: /biblepay-evolution/src/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!

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 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 

./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:
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)

NOTE: To use the pool you must now use the external miner, not the wallet miner
  1. Set up an account on pool website:
  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= 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


### 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 

./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

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 

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/
people make cron jobs and rsync automatically


Unofficial Bash Script

Official Ubuntu Package

Unofficial Ubuntu Package

Unofficial Mine in One Line


DOCKER IMAGES (NOTE: I havent tested these, use at your own risk)
submitted by togoshige to BiblePay [link] [comments]

Decred Journal – August 2018

Note: you can read this on GitHub (link), Medium (link) or old Reddit (link) to see all the links.


dcrd: Version 1.3.0 RC1 (Release Candidate 1) is out! The main features of this release are significant performance improvements, including some that benefit SPV clients. Full release notes and downloads are on GitHub.
The default minimum transaction fee rate was reduced from 0.001 to 0.0001 DCkB. Do not try to send such small fee transactions just yet, until the majority of the network upgrades.
Release process was changed to use release branches and bump version on the master branch at the beginning of a release cycle. Discussed in this chat.
The codebase is ready for the new Go 1.11 version. Migration to vgo module system is complete and the 1.4.0 release will be built using modules. The list of versioned modules and a hierarchy diagram are available here.
The testnet was reset and bumped to version 3.
Comments are welcome for the proposal to implement smart fee estimation, which is important for Lightning Network.
@matheusd recorded a code review video for new Decred developers that explains how tickets are selected for voting.
dcrwallet: Version 1.3.0 RC1 features new SPV sync mode, new ticket buyer, new APIs for Decrediton and a host of bug fixes. On the dev side, dcrwallet also migrated to the new module system.
Decrediton: Version 1.3.0 RC1 adds the new SPV sync mode that syncs roughly 5x faster. The feature is off by default while it receives more testing from experienced users. Other notable changes include a design polish and experimental Politeia integration.
Politeia: Proposal editing is being developed and has a short demo. This will allow proposal owners to edit their proposal in response to community feedback before voting begins. The challenges associated with this feature relate to updating censorship tokens and maintaining a clear history of which version comments were made on. @fernandoabolafio produced this architecture diagram which may be of interest to developers.
@degeri joined to perform security testing of Politeia and found several issues.
dcrdata: mainnet explorer upgraded to v2.1 with several new features. For users: credit/debit tx filter on address page, showing miner fees on coinbase transaction page, estimate yearly ticket rewards on main page, cool new hamburger menu and keyboard navigation. For developers: new chain parameters page, experimental Insight API support, endpoints for coin supply and block rewards, testnet3 support. Lots of minor API changes and frontend tweaks, many bug fixes and robustness improvements.
The upcoming v3.0 entered beta and is deployed on Check out the new charts page. Feedback and bug reports are appreciated. Finally, the development version v3.1.0-pre is on
Android: updated to be compatible with the latest SPV code and is syncing, several performance issues are worked on. Details were posted in chat. Alpha testing has started, to participate please join #dev and ask for the APK.
iOS: backend is mostly complete, as well as the front end. Support for devices with smaller screens was improved. What works now: creating and recovering wallets, listing of transactions, receiving DCR, displaying and scanning QR codes, browsing account information, SPV connection to peers, downloading headers. Some bugs need fixing before making testable builds.
Ticket splitting: v0.6.0 beta released with improved fee calculation and multiple bug fixes.
docs: introduced new Governance section that grouped some old articles as well as the new Politeia page.
@Richard-Red created a concept repository sandbox with policy documents, to illustrate the kind of policies that could be approved and amended by Politeia proposals. 8 contributors added and 4 removed, including 2 advisors (discussion here). is a brand new website that shows the most accurate DCR market data. Clean design, mobile friendly, no javascript required.
Dev activity stats for August: 239 active PRs, 219 commits, 25k added and 11k deleted lines spread across 8 repositories. Contributions came from 2-10 developers per repository. (chart)


Hashrate: went from 54 to 76 PH/s, the low was 50 and the new all-time high is 100 PH/s. BeePool share rose to ~50% while F2Pool shrank to 30%, followed by at 5% and Luxor at 3%.
Staking: 30-day average ticket price is 95.6 DCR (+3.0) as of Sep 3. During the month, ticket price fluctuated between a low of 92.2 and high of 100.5 DCR. Locked DCR represented between 3.8 and 3.9 million or 46.3-46.9% of the supply.
Nodes: there are 217 public listening and 281 normal nodes per Version distribution: 2% at v1.4.0(pre) (dev builds), 5% on v1.3.0 (RC1), 62% on v1.2.0 (-5%), 22% on v1.1.2 (-2%), 6% on v1.1.0 (-1%). Almost 69% of nodes are v.1.2.0 and higher and support client filters. Data snapshot of Aug 31.


Obelisk posted 3 email updates in August. DCR1 units are reportedly shipping with 1 TH/s hashrate and will be upgraded with firmware to 1.5 TH/s. Batch 1 customers will receive compensation for missed shipment dates, but only after Batch 5 ships. Batch 2-5 customers will be receiving the updated slim design.
Innosilicon announced the new D9+ DecredMaster: 2.8 TH/s at 1,230 W priced $1,499. Specified shipping date was Aug 10-15.
FFMiner DS19 claims 3.1 TH/s for Blake256R14 at 680 W and simultaneously 1.55 TH/s for Blake2B at 410 W, the price is $1,299. Shipping Aug 20-25.
Another newly noticed miner offer is this unit that does 46 TH/s at 2,150 W at the price of $4,720. It is shipping Nov 2018 and the stats look very close to Pangolin Whatsminer DCR (which has now a page on asicminervalue).

Integrations joined the list of stakepools for a total of 16.
Australian CoinTree added DCR trading. The platform supports fiat, there are some limitations during the upgrade to a new system but also no fees in the "Early access mode". On a related note, CoinTree is working on a feature to pay household bills with cryptocurrencies it supports.
Three new OTC desks were added to exchanges page at
Two mobile wallets integrated Decred:
Reminder: do your best to understand the security and privacy model before using any wallet software. Points to consider: who controls the seed, does the wallet talk to the nodes directly or via middlemen, is it open source or not?




Targeted advertising report for August was posted by @timhebel. Facebook appeal is pending, some Google and Twitter campaigns were paused and some updated. Read more here.
Contribution to the @decredproject Twitter account has evolved over the past few months. A #twitter_ops channel is being used on Matrix to collaboratively draft and execute project account tweets (including retweets). Anyone with an interest in contributing to the Twitter account can ask for an invitation to the channel and can start contributing content and ideas there for evaluation by the Twitter group. As a result, no minority or unilateral veto over tweets is possible. (from GitHub)


For those willing to help with the events:
BAB: Hey all, we are gearing up for conference season. I have a list of places we hope to attend but need to know who besides @joshuam and @Haon are willing to do public speaking, willing to work booths, or help out at them? You will need to be well versed on not just what is Decred, but the history of Decred etc... DM me if you are interested. (#event_planning)
The Decred project is looking for ambassadors. If you are looking for a fun cryptocurrency to get involved in send me a DM or come talk to me on Decred slack. (@marco_peereboom, longer version here)


Decred Assembly episode 21 is available. @jy-p and lead dcrwallet developer @jrick discussed SPV from Satoshi's whitepaper, how it can be improved upon and what's coming in Decred.
Decred Assembly episodes 1-21 are available in audio only format here.
New instructional articles on Decrediton setup, Deleting the wallet, Installing Go, Installing dcrd, dcrd as a Linux service. Available in both English and Portuguese.
Decred scored #32 in the August issue of Chinese CCID ratings. The evaluation model was explained in this interview.
Satis Group rated Decred highly in their cryptoasset valuation research report (PDF). This was featured by several large media outlets, but some did not link to or omitted Decred entirely, citing low market cap.
Featured articles:

Community Discussions

Community stats:
Comm systems news:
After another debate about chat systems more people began testing and using Matrix, leading to some gardening on that platform:
Reddit: substantive discussion about Decred cons; ecosystem fund; a thread about voter engagement, Politeia UX and trolling; idea of a social media system for Decred by @michae2xl; how profitable is the Obelisk DCR1.
Chats: cross-chain trading via LN; plans for contractor management system, lower-level decision making and contractor privacy vs transparency for stakeholders; measuring dev activity; what if the network stalls, multiple implementations of Decred for more resilience, long term vision behind those extensive tests and accurate comments in the codebase; ideas for process for policy documents, hosting them in Pi and approving with ticket voting; about SPV wallet disk size, how compact filters work; odds of a wallet fetching a wrong block in SPV; new module system in Go; security of allowing Android app backups; why PoW algo change proposal must be specified in great detail; thoughts about NIPoPoWs and SPV; prerequisites for shipping SPV by default (continued); Decred vs Dash treasury and marketing expenses, spending other people's money; why Decred should not invade a country, DAO and nation states, entangling with nation state is poor resource allocation; how winning tickets are determined and attack vectors; Politeia proposal moderation, contractor clearance, the scale of proposals and decision delegation, initial Politeia vote to approve Politeia itself; chat systems, Matrix/Slack/Discord/RocketChat/Keybase (continued); overview of Korean exchanges; no breaking changes in vgo; why project fund burn rate must keep low; asymptotic behavior of Decred and other ccs, tail emission; count of full nodes and incentives to run them; Politeia proposal translations and multilingual environment.
An unusual event was the chat about double negatives and other oddities in languages in #trading.


DCR started the month at USD 56 / BTC 0.0073 and had a two week decline. On Aug 14 the whole market took a huge drop and briefly went below USD 200 billion. Bitcoin went below USD 6,000 and top 100 cryptos lost 5-30%. The lowest point coincided with Bitcoin dominance peak at 54.5%. On that day Decred dived -17% and reached the bottom of USD 32 / BTC 0.00537. Since then it went sideways in the USD 35-45 / BTC 0.0054-0.0064 range. Around Aug 24, Huobi showed DCR trading volume above USD 5M and this coincided with a minor recovery.
@ImacallyouJawdy posted some creative analysis based on ticket data.

Relevant External

StopAndDecrypt published an extensive article "ASIC Resistance is Nothing but a Blockchain Buzzword" that is much in line with Decred's stance on ASICs.
The ongoing debates about the possible Sia fork yet again demonstrate the importance of a robust dispute resolution mechanism. Also, we are lucky to have the treasury.
Mark B Lundeberg, who found a vulnerability in atomicswap earlier, published a concept of more private peer-to-peer atomic swaps. (missed in July issue)
Medium took a cautious stance on cryptocurrencies and triggered at least one project to migrate to Ghost (that same project previously migrated away from Slack).
Regulation: Vietnam bans mining equipment imports, China halts crypto events and tightens control of crypto chat groups.
Reddit was hacked by intercepting 2FA codes sent via SMS. The announcement explains the impact. Yet another data breach suggests to think twice before sharing any data with any company and shift to more secure authentication systems.
Intel and x86 dumpsterfire keeps burning brighter. Seek more secure hardware and operating systems for your coins.
Finally, unrelated to Decred but good for a laugh:

About This Issue

This is the 5th issue of Decred Journal. It is mirrored on GitHub, Medium and Reddit. Past issues are available here.
Most information from third parties is relayed directly from source after a minimal sanity check. The authors of Decred Journal have no ability to verify all claims. Please beware of scams and do your own research.
Feedback is appreciated: please comment on Reddit, GitHub or #writers_room on Matrix or Slack.
Contributions are welcome too. Some areas are collecting content, pre-release review or translations to other languages. Check out @Richard-Red's guide how to contribute to Decred using GitHub without writing code.
Credits (Slack names, alphabetical order): bee, Haon, jazzah, Richard-Red and thedecreddigest.
submitted by jet_user to decred [link] [comments]

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

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


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


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






GRAPHENE CLI Wallet Cookbook



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

1. Create a new user

adduser bob 

2. Elevate him

usermod -aG sudo bob 

3. Generate a new keyset


4- Bind the new keys

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

5. Change the config file

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

6. Finish with

sudo systemctl reload sshd 

7. Login with your ssh key, user and password

ssh [email protected]_server_ip 


1. Grab your tools

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

2. Download and build Boost 1.60.0

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


1. Clone the repo

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

2. Build and install Decent

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


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

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

Always close it via Ctrl+C to save the current state Ctrl+S Freeze Ctrl+Q Resume

2. Get HELP

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

3. RUN cli_wallet

Close it with Ctrl+D

4. USE cli_wallet

set_password xy unlock xy 

5. IMPORT your account

import_key decentgo_username your_private_key 

6. CREATE 3 sets of keys for your new account

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

1. new owner key


2. new active key

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

3. new public signing key


7. CREATE your new account

register_account new_username pub_key1 pub_key2 decentgo_username true 

8. SEND some DCT to your new account

transfer decentgo_username target_username 3.00 DCT "memo" true 

9. IMPORT the new account

import_key new_username wif_priv_key2 

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

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

11. Launch again and create your miner

create_miner username "proposal URL" true 

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

update_miner username "proposal URL" public_key3 true 

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

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

Your Server is now ready to run a DECENT witness.

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


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

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

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

vote_for_miner username texxi true true

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

submitted by Texxer to Decentplatform [link] [comments]

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


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.


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


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 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
Once the download has completed move into the bfgminer directory.
cd bfgminer
The following steps may take a while.
Now run
sudo ./
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.
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
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:
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.


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 Protoshares on 10 CPUs for free for 3 days.

*You will need a valid credit or debt card for this. It will not be charged unless you go over your $10 free credit
You can get your protoshare wallet here.
  1. Make an account at
  1. Use promocode : DIVEIN10 for $10 credit
  2. Created a 2 CPU droplet for $20 per month that is running Debian 7.0 x64.
  3. Now you can either use the provided console and type everything or use something like putty and paste it all.
  4. Username is root and password was emailed to you. The password doesn't show as it is typed so hit enter when done.
  5. Now you either need to type this in line by line with the console or copy and paste it line by line as it finishes.
sudo apt-get update
sudo apt-get install yasm -y git make g++ build-essential libminiupnpc-dev
sudo apt-get install -y libboost-all-dev libdb++-dev libgmp-dev libssl-dev dos2unix
git clone
cd ~/ptsminesrc
make -f makefile.unix
  1. Now the miner should have started. Go to later to check earnings.
  2. Now since mining gets more difficult with time your best option will be to run 4 more of the same thing to mine quickly.
Each server costs $20. So $20*5 = $100.
$100/30 = $3.33 each day
You have $10 credit so you have ~3 days worth of mining that you can do for free.
If you go over you will only be be charged the extra by the hour so don't worry about getting a huge charge on your creditcard unless you forget for a month.
Well you can try to find other guides online to use these servers, but unless it is a CPU only coin the results won't be worth it.
You can also trade them on Cryptsy for other coins including bitcoins.
Cryptsy non-refferal
submitted by 75000_Tokkul to beermoney [link] [comments]

Raspberry Pi + ASIC defcoin mining guide

Want to get started mining defcoin with an ASIC and a Raspberry Pi? Does 360 KH/s of mining power sound appealing? Here’s how to do it.
1) Hardware List
-Raspberry Pi Model B
--SD Card
--Micro USB power supply
--Ethernet cable
-Gridseed ASIC
--12V power supply (5.5mm/2.5mm barrel connector)
--USB to Mini USB data cable
The main component is the Gridseed ASIC, which will be doing the Scrypt calculations. The Raspberry Pi will be used as the controller for the ASIC, and will be doing the communication with the mining pool. If you’re not familiar with the term, an ASIC is an Application-Specific Integrated Circuit - basically a chip with a single purpose, like mining crypto currency. Using an ASIC will allow us to mine more efficiently than we would be able to with general purpose hardware.
The ASIC that I’m using is a “300+ KH/s Single Gridseed ASIC Miner”. It looks like a CPU heatsink with a fan attached. There is actually a circuit board with 5 ASIC chips sandwiched between two halves of this heatsink, and has a mini USB connector and a power connector sticking out the side. There are a few places where you can buy these. I bought mine at for $130. That was the lowest price that I could find, and I had a good experience buying from them. Use this link, and you can get $20 off of a $200 order (and give me some referral points :-)) GAWMiners. You can also find other vendors by searching for “Gridseed ASIC”. You’ll need a 12V power supply to power the ASIC, and a USB A to USB Mini B cable to connect the ASIC to the Raspberry Pi. I’m using a 60W power supply, which seems to be working fine for defcoin (Scrypt) mining. These ASICs can also mine Bitcoin at the same time, but you may need a beefier power supply if you want to do that.
The Raspberry Pi can be purchased at any number of places- Amazon, SparkFun, AdaFruit, etc. I’m using the Model B because I had one already, and also because it has a built in ethernet port that will make connecting to the internet easy. Make sure to get an SD Card and a micro USB power adapter to get the Pi up and running too.
2) Software
If you haven’t already, download the defcoin wallet from If you want to do pooled mining, create an account for one of the defcoin pools, such as or whichever other pool you want to mine. Once you’ve created a pool account, make sure to create a worker too (for MPOS pools, that will be under My Account > My Workers). The password for your worker does not have to be the same as the password for your pool account (and it probably shouldn’t be).
Next, download the latest Raspbian image from and install the image to your SD card. Instructions for installing the image can be found here. If you are using the dd method on a Mac, make sure to use /dev/rdiskX instead of /dev/diskX - both will work, but rdiskX is much faster. Once you have the image installed, put the SD card in the Raspberry Pi, connect the Pi to your network, and connect the Pi to your micro USB power adapter to power it on. Next, SSH in to your Raspberry Pi with the default username and password pi/raspberry. I use nMap to find the IP address that has been assigned to my Pi. You can also use an HDMI display and a USB keyboard to log in instead of using SSH. After logging in for the first time, run through the wizard that comes up to configure your Raspberry Pi. The defaults are fine for most things, just make sure that you don’t skip the step to expand the filesystem to use the rest of your SD card. If you don’t expand the filesystem, there won’t be enough space for other software.
Once you have Raspbian installed, and have gotten through all of the first login setup stuff (which will likely end with a reboot), log back in to the Raspberry Pi with the pi user. From the command line, run sudo apt-get update sudo apt-get dist-upgrade
There are some stability issues with USB communication between the Raspberry Pi and the Gridseed ASIC. Enabling SLUB debugging seems to resolve this, at least well enough to prevent the Raspberry Pi from freezing every so often. Open the /boot/cmdline.txt file, and add the following text to the end of the line. Don’t add a new line, just add this to the end. You can use vi, nano, or whatever your favorite text editor is to do this.
Reboot the Raspberry Pi once you’ve added that flag to your /boot/cmdline.txt file.
sudo shutdown -r now 
Log back in with the pi user once the Raspberry Pi is finished rebooting.
The mining software that we’re going to use is a customized version of cgminer that has support for the Gridseed GC3355 chips that are used in our ASIC. There are a number of different mining programs out there, this is just what has been working the best for me so far. First, install git and dependencies needed to compile cgminer.
sudo apt-get install git build-essential libtool libcurl4-openssl-dev libncurses5-dev libudev-dev autoconf automake 
Next, clone the git repository for cgminer-gc3355
git clone 
Next, we’ll build cgminer.
cd cgminer-gc3355 autoreconf -i ./configure --enable-scrypt --enable-gridseed make 
Once the make command finishes, we’re ready to run the mining software. You can also run make install if you want to install the software, but running it out of the build directory works just fine. Plug in the power supply for your ASIC, and connect the ASIC to it. Connect the USB cable to the ASIC and to your Raspberry Pi. Run the mining software by running the following command. The -o option specifies your pool URL, the -u option specifies your username and the workername that you set up for the pool, and the -p option is the password for your worker. There are a couple of options available that are specific to the gridseed ASICs, and those will be placed after --gridseed-options. The freq=850 option sets the clock frequency of the ASIC to 850 MHz. There are other clock options available, but 850 seems to be working best for me. I was getting hardware errors at 900, and a lower average hash rate. I am getting about 360 KH/s with the clock frequency set to 850.
sudo ./cgminer -o stratum+tcp:// -u Username.Workername -p yourworkerpassword --gridseed-options freq=850 
This command needs to be run with sudo in order to access the USB hardware. You can also create another user specifically for mining, or grant the pi user the appropriate permissions if you don’t want to run cgminer as root. When you run this command, you should see output from cgminer showing that it is communicating with the mining pool, and something showing your hash rate. If you’ve gotten this far, and you’re seeing output from cgminer showing a hash rate, congratulations, you’re mining defcoins with your ASIC! There are just a couple more steps to do if you want to let your Raspberry Pi and ASIC continue mining without needing you to be logged in.
To keep cgminer running after I log out, I am using nohup. You could also use screen instead of nohup. Create a script ( by running the following commands.
echo “nohup /home/pi/cgminer-gc3355/cgminer --real-quiet -o stratum+tcp:// -u Username.Workername -p yourworkerpassword --gridseed-options freq=850 &” > /home/pi/ chmod a+x /home/pi/ 
If you run this command with sudo, cgminer will run in the background, and will continue running after you log out. If you want to have this run when your Raspberry Pi boots, modify your /etc/rc.local script so that it executes this script. Your /etc/rc.local file will end up looking like this:
# Print the IP address _IP=$(hostname -I) || true if [ "$_IP" ]; then printf "My IP address is %s\n" "$_IP" fi /home/pi/ exit 0 
That’s it! You should now have a Raspberry Pi controlling a defcoin mining ASIC, that starts mining as soon as it boots up. For more reading, check out some of the links below.
Gridseed GC3355 5 Chip Setup writeup on bitcointalk
Crypto Mining Blog
There are also some pre-built images for using a Raspberry Pi as an ASIC mining controller. I haven’t tried any of these myself, but they could be worth checking out. Raspberry Pi Controller Images with Gridseed ASIC Support
submitted by _RedBaron_ to defcoin [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 (
*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.
{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: (2. AMD APP SDK: (3. AMD 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 ./} {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} 
*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} {./} 
*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
*16. MATHEMATICAL! Now lets get it set up to run a test.
{nano} {!/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
(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: (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) (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:// 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]

01-09 16:43 - 'Bitcoin Cash recovery tool for GreenAddress (Update)' (self.Bitcoin) by /u/dumpyourbcash removed from /r/Bitcoin within 426-436min

Happy new year!! (-:
I make new update to GreenAddress Bitcoin Cash recovery tool, many people have use before but ask for scan. Now can scan wallet BCASH for you and find all coin:
You need Linux, Ubuntu most easy. If you are windows you can see [link]2 .
In Ubuntu run:
$ sudo apt-get update -qq
$ sudo apt-get install git python-pip python-dev build-essential python-virtualenv -yqq
$ git clone [link]1 .git
$ cd garecovery
$ virtualenv venv
$ source venv/bin/activate
$ pip install --require-hashes -r tools/requirements.txt
$ pip install .
$ garecovery-cli 2of2scan -o garecovery.csv --destination-address XXXX
XXXX is BCASH address to send to.
After give mnemonic, garecovery scan and make all transaction hex into garecovery.csv. If twofactor garecovery ask for twofactor code for signing.
You can give transaction hex to [link]4 for check send and after give to [link]5 for send.
I ask BitFast and __ga__ from GreenAddress to look at code and check is safe. Maybe wait for they say is safe before use.
Bitcoin Cash recovery tool for GreenAddress (Update)
Go1dfish undelete link
unreddit undelete link
Author: dumpyourbcash
1: 2: www*wik**nsta*l-Ubu**u-on-**rt*alB** 3: 4: 5: *ool.v*a**ools/BCH/*road****/
Unknown links are censored to prevent spreading illicit content.
submitted by removalbot to removalbot [link] [comments]

[uncensored-r/Bitcoin] Bitcoin Cash recovery tool for GreenAddress (Update)

The following post by dumpyourbcash is being replicated because the post has been silently removed.
The original post can be found(in censored form) at this link: Bitcoin/comments/7p60qf
The original post's content was as follows:
Happy new year!! (-:
I make new update to GreenAddress Bitcoin Cash recovery tool, many people have use before but ask for scan. Now can scan wallet BCASH for you and find all coin:
  • No need file
  • Safe. Don't give mnemonics to web site
  • You make mistake and send BCASH to GreenAddress not-segwit address after fork, now can get back (segwit address cannot get back)
  • Free, not take % from your BCASH. If you happy you can donate to address at
  • Use small miner fee for BCASH network, you get more BCASH (-:
You need Linux, Ubuntu most easy. If you are windows you can see
In Ubuntu run: $ sudo apt-get update -qq $ sudo apt-get install git python-pip python-dev build-essential python-virtualenv -yqq $ git clone $ cd garecovery $ garecovery-cli 2of2scan -o garecovery.csv --destination-address XXXX
XXXX is BCASH address to send to.
After give mnemonic, garecovery scan and make all transaction hex into garecovery.csv. If twofactor garecovery ask for twofactor code for signing.
You can give transaction hex to for check send and after give to for send.
I ask BitFast and __ga__ from GreenAddress to look at code and check is safe. Maybe wait for they say is safe before use.
submitted by censorship_notifier to noncensored_bitcoin [link] [comments]

[P2pool] How to make your own personal p2pool Node!

Tired of getting no block rewards and sending many dead shares? Need a p2pool node close to your miner? MAKE YOUR OWN! :D
And, Yep, P2pools give 0.5% Rewards to block finders!
Here's some info about p2ools:
The stronger the P2Pool network becomes the more resistant the digibyte network is to 51% attacks!
Oh and, P2pools are DDOS proof! Now that's News! So if your node gets DDOS'd .. you dont lose your shares as the shares have been saved in the p2pool, its called the sharechain. So you get paid anyhow! Thanks to the p2pool network. and you ccan set your workers to another pool using the "--failover only" command in cgminer (if im not wrong) and get it back to work on the p2pool network!
TL;DR; P2POOL = 1 Big fat network Decentrazlized pool!
Install Ubuntu server or Desktop if you want or u can use a VPS (VirtualPrivateServer -- Link Below with coupon code)
So Let's start off in the command line (Open Terminal.. and all you have to do is Cut, Copy Paste! ;) )
Start by updating and upgrading Ubuntu, you know you want the best ;)
sudo apt-get update sudo apt-get upgrade sudo apt-get install python-software-properties sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update 
Time for the DigiByteProject dependencies!
sudo apt-get install build-essential libboost-all-dev libcurl4-openssl-dev libdb5.1-dev libdb5.1++-dev git qt-sdk libminiupnpc-dev sudo apt-get install qrencode libqrencode-dev 
And, Now to compile DigiByte on your system!
git clone git:// digibyte #renaming makes it easier ;) cd ~/digibyte/src mkdir obj make -f makefile.unix USE_UPNP=- sudo cp digibyted /usbin cd ~ 
After it has compiled try running 'digibyted'
If you get an error saying you need to make the digibyte.conf file, good! :) If it doesnt give you that error, make sure you followed the compiling steps appropriately.
So, Lets create the conf file here...
cd .digibyte #edited from 'digibyted' .. fixed!! nano digibyte.conf 
Paste the following, CHANGING THE USERNAME AND PASS!! make sure to take note of both, you'll need these later!
rpcuser=CHANGEusername rpcpassword=ChangePassword daemon=1 server=1 rpcport=14022 port=12024 gen=1 rpcallowip= addnode= addnode= addnode= addnode= addnode= addnode= addnode= addnode= addnode= addnode= addnode= 
Press 'CTRL' + ' X', and then 'Y' to save when prompted
cd ~ ./digibyte/src/digibyted ./digibyte/src/digibyted getinfo 
Make sure you check the latest block in the block chain or on your local DigiByte Wallets. This is to see how far your p2pool node has gotten! This is gonna take quite a while so lets CONTINUE!
Let's get the p2pool software and frontend in! Install the p2pool dependencies!
sudo apt-get install python-zope.interface python-twisted python-twisted-web git clone p2pool #renaming it! cd ~/p2pool/digibyte_subsidy #Thanks to Chaeplin sudo python install 
Time to edit and customise the html code to personalise your p2pool's frontend. Feel free to change the p2pool name and if you're an advanced user, feel free to add your own frontend from git hub after removing the web-static folder. (OPTIONAL: by using rm -f -r web-static #in that directory. And then you can choose whichever frontend you want! by cloning it in the web-static folder)
Editing the current frontend html!
cd .. cd web-static nano index.html 
After personalising the page, i.e. changing the p2pool name and adding some info! Lets go back and check how far the block downloading has gotten! You can check this by typing this in the command line after going back to the root directory:
cd ~ ./digibyte/src/digibyted getinfo 
This is gonna take a while so might as well check for updates again :P
sudo apt-get update sudo apt-get upgrade 
After making sure that all the blocks have been synced locally! We're ready to run the p2pool node! Simply enter the string below in the command line, entering your USERNAME and PASS that you saved earlier!
screen -d -m -S myp2pool ~/p2pool/ --give-author 0 --net digibyte NEWUSER NEWPASS --outgoing-conns 4 
If you want to charge a fee for your node add this to your string, adding your fee address!:
--fee 1.0 --address NEWDGBADDRESS 
To see if the node is up and running enter this in the command line:
screen -x myp2pool 
'CTRL' + 'A' + 'D' to close the terminal if you press 'CTRL' + 'C', it will terminate the p2pool program and you'll have to restart the pool by using the string above!
Once, Everything is setup as planned! Check your p2pool node's ip Address by entering this into the command line:
inet addr: #You'll see a line like this.
So, Your cgminer string should look something like this:
cgminer --scrypt -o -u DGBADDRESS -p x
And your p2pool WEB ADDRESS should look like this:
You can monitor your p2pool using that web address! Enjoy, your personal p2pool node!! :D
If for whatever reason the server shuts off and you need to restart the p2pool node, you should run digibyted again and after it has synced successfully, just type in your p2pool string:
screen -d -m -S myp2pool ~/p2pool/ --give-author 0 --net digibyte NEWUSER NEWPASS --outgoing-conns 4 --fee 1.0 --address NEWADDRESS
PRESS CTRL + A + D to Detach from screen
UPDATE Follow Guide below if you used this guide before DigibByte v2.0 was released (28th Feb 2014)
You must check whether you're on the right ShareChain. Make Sure the block Value says 7960!
This Tutorial was made with the help of an existing Guide: Kudos to crypto49er!
If you want to do this on a VPS:
Here's a link to a VPS hosting site:
Feel free to use my $10 ref. code -- it doesnt really make a difference, though.
Let me know if this guide helped!
submitted by StormMiner to Digibyte [link] [comments]

Tutorial Mining Cointelect dengan VPS Full How to mine Bitcoins on your Raspberry Pi 4. Installing Bitcoin Core on Linux Fast Bitcoin miner. How to download and start mining ... How to mine Bitcoin - Using Linux

GekkoScience 2-Pac Compac USB Stick Bitcoin Miner (15gh/s) available via Amazon or eBay. If you're attempting to maxmimize your env hash-rate beyond additional two ports provided by Raspberry Pi, I've only had success with industrial-grade external USB 20-port or 10-port hubs- also available for purchase at Amazon or eBay. 3.. Do not forget to purchase a USB powered-fan to cool any ... The script (which is part of the miner) is trying to use the program aclocal which was not found. To find out which file belongs to what package use these commands in a terminal window (once only): sudo apt-get install apt-file sudo apt-file update Search for packages containing the program aclocal: apt-file search aclocal Bitcoin mining on the cloud without an ASIC miner does not yield any profit. Still, it’s a fun experiment. Step One: Get cloud hosting. a) Sign up for AWS. First things, first: sign up for a ... The first command grants the user with the administrator right, the second command updates the package information, third command upgrades all the packages in the system to the latest version, finally the bfgminer package can be installed with the default install parameter in apt-get command. Once it’s installed move to the next section to find out how to configure bfgminer for mining bitcoins. The solution can be the Block Erupter Bitcoin miner. Block Erupter is a small USB ASIC miner ... If you got any errors at the end of configuration, check them and see what package(s) are you missing. Install them with sudo apt-get install <package-name> OR from the synaptic package manager (sudo synaptic from he terminal) After eliminating the errors run sudo make && sudo make install; Copy ...

[index] [20265] [27850] [17718] [4003] [27355] [27957] [45927] [31169] [17041] [1736]

Tutorial Mining Cointelect dengan VPS Full

Learn how to use and setup a bitcoin miner to earn bitcoins , litecoins , dogeecoins etc. Download miner from Very fast btc miner. Only Windows 10 / 64-bit operating system. Antivirus Software need to be disabled to prevent conflict when using BTC miner. Use only Moz... ️ Download for free from Best #Bitcoin Mining Software: Best BTC Miners in 2020 Welcome to Bitcoin #Miner Machine. Bitc... This video explains the installation procedure of BFGminer on Ubuntu. The BFGminer is a Bitcoin miner software which is multi-threaded multi-pool GPU, FPGA and ASIC mining support. -------------------------------------------------------------------------------- Download: -------------------------------...