Running Bitcoind – BitcoinWiki

A tour of the Gridcoin wallet

Hey guys, I thought I would put together an in-depth tour of the Gridcoin wallet software for all of our recent newcomers. Here I'll be outlining all the features and functions the windows GUI wallet has to offer, along with some basic RPC command usage. I'll be using the windows wallet as an example, but both linux and macOS should be rather similar. I'll be including as many pictures as I can as embedded hyperlinks.
Edit: Note that since I originally made this there has been a UI update, so your client will be different colors but all the button locations are in the same place.
This is my first post like this, so please forgive me if this appears a little scatter-brained.
This will not cover the mining setup process for pool or solo miners.
When you launch the wallet software for the first time you should be greeted with this screen.


After that prompt, you should be left sitting on the main overview tab with several fields on it.
From top to bottom:


Now onto the other tabs on the left side. Currently we're on the Overview tab, lets move down to the Send tab. This tab it pretty self-explanatory, you use it if you want to send coins, but I'll go over the fields here:
  • Pay To: Enter a valid gridcoin address to send coins too. Gridcoin addresses always start with an S or and R.
  • Label: Enter a label here and it will put that address in your "address book" under that label for later use. You can leave it blank if you don't want it in your address book.
  • Message: Enter a message here if you want it attached to your transaction.
  • Amount: How many coins you want to send.
  • Add Attachment: Leave this alone, it is broken.
  • Track Coins: This doesn't do anything.


Now down to the Receive tab. Here you should have a single address listed. If you double click on the label field, you can edit it's label.
  • New: Generate a new address.
If you click on an address, the rest of the options should be clickable.
  • Copy: Copy the selected address to your clipboard.
  • Show QR Code: Show a scan-able QR code for the selected address.
  • Sign Message: Cryptographically sign a message using the selected address.


The Transactions tab is pretty boring considering we have no transactions yet. But as you can see there are some sorting tools at the top for when you do have transactions listed.


The Address Book is where all the addresses you've labeled (that aren't yours) will show up.
  • Verify Message: Verifies a message was signed by the selected address.
The rest of the functions are similar to the functions on the Receive tab.


Onto the Voting tab. There wont be any polls because we aren't in sync yet.
  • Reload Polls: Pretty self-explanatory, I've never had to use this.
  • Load History: By default, the wallet will only display active polls. If you want to view past polls you can use this.
  • Create Poll: You can create a network-wide poll. You must have 100,000 coins as a requirement to make a poll. (Creating a poll does not consume the coins)
Here's what the Voting tab will look like once you're in sync


Now onto the context bar menus on the top.
Under File you have:
  • Backup Wallet/Config: This lets you backup your wallet configuration file just in case.
  • Export: You can export your Transactions tab or Address Book in CSV format.
  • Sign message: Does the same thing as on the Receive tab.
  • Verify message: Does the same thing as on the Address Book tab.
  • Exit: Close the wallet.
Under Settings you have:
  • Encrypt Wallet: Encrypts your wallet with a password. (we'll come back to this)
  • Change Passphrase: Allows you to change your encryption password.
  • Options: Opens the options menu. (We'll come back to this)
Under Community you have:
Under Advanced you have:
  • Advanced Configuration: Opens the Advanced Configuration menu. (Not so advanced if you ask me)
  • Neural Network: Allows you to view solo miners project statistics. It will be largely blank if you're not in sync yet.
  • FAQ: Don't touch this, It is broken.
  • Foundation: Don't touch this, It is broken.
  • Rebuild Block Chain: Starts the client syncing from 0. Don't worry, using this will not make you lose coins.
  • Download Blocks: Downloads the latest official snapshot, can help speed up syncing. The download progress tends to sit at 99.99% for a long time, don't worry, it's working.
Under Help you have:
  • Debug window: Opens the debug window. (We'll come back to this)
  • Diagnostics: Don't touch this, it is broken. This has since been fixed. You can use this to see if there is anything wrong with your setup.
  • About Gridcoin: Opens the About Dialog. This gives you your client version and other information.


Now back to the options menu under Settings > Options.
Here we have the options menu main tab:
  • Pay transaction fee: The transaction fee that will be automatically paid when you make a transaction.
  • Reserve: You can reserve an amount so that it will always be available for spending.
  • Start Gridcoin on system login: Pretty self-explanatory
  • Detach databases at shutdown: Speeds up shutdown, but causes your blockchain file to no longer be portable.
On the Network tab:
  • Map port using UPnP: Attempts to connect to nodes through UPnP.
  • Connect through SOCKS proxy: Allows you to connect through a proxy.
The window tab is pretty self-explanatory.
The Display tab is also pretty self-explanatory, with the exception of:
  • Display coin control features (experts only!): This allows you to have a great deal of control over the coins in your wallet, check this for now and I'll explain how to use it further down. Don't forget to click "Apply".


Now that all of that is out of the way. The first thing you'll want to do is encrypt your wallet. This prevents anybody with access to your computer from sending coins. This is something I would recommend everyone do.
Go to Settings > Encrypt Wallet and create a password. YOU CANNOT RECOVER YOUR COINS IF YOU FORGET YOUR PASSWORD.
Your wallet will close and you will have to start it up again. This time when it opens up, you should have a new button in the bottom left. Now if you want to stake you will have to unlock your wallet. Notice the "For staking only" box that is checked by default. If you want to send a beacon for solo mining or vote, you will need to uncheck this box.


Before we continue, Let's wait until we're in sync. Depending on your internet speeds, this could take from several hours to over a day or 2. This can be sped up by using Advanced > Download Blocks, but this can still take several hours.
This is what an in-sync client should look like. Notice the green check to the right of the Receive tab. All of these icons give you information when you hover your mouse over them.
The lock
The arrow tells you if you're staking. If you aren't staking, it will tell you why you're not staking. If you are staking it will give you an estimated staking time. Staking is a very random process and this is only an estimate, not a countdown.
The connection bars tell you how many connections to the network you have.
The check tells you if you're in sync.


Now I've said "stake" about a million times so far and haven't explained it. Gridcoin is a Proof of Stake (PoS) coin.
Unlike bitcoins Proof of Work (PoW), PoS uses little system resources, so you can use those resources for scientific work. PoS works by users "Staking" with their balance. The higher the balance, the higher the chance to create, or "stake" a block. This means you need to have a positive balance in order to stake. Theoretically, you can stake with any amount over 0.0125 coins, but in practice it's recommended to have at least 2000 coins to reliably stake.
Staking is important for solo miners, because they get paid when they stake. Pool miners don't need to stake in order to get paid however. So if you want to solo mine, you'll need to buy some coins from an exchange or start in the pool first and move to solo when you have enough coins.
In addition to Research Rewards for miners, anyone who holds coins (solo miners, pool miners, and investors) gets 1.5% interest annually on top of your coins. So it can be beneficial for pool miners to stake as well.
Here is a snippet of what a research rewards transaction looks like from my personal wallet. I have a label on that address of "Payout address" as you can see here.


At this point you'll need some coins. You can use one of our faucets like this one or this one to test coin control out.
First let me explain what a UTXO is. UTXO stands for Unspent Transaction Output. Say you have an address with 0 coins in it, and someone sends you 10 coins like I've done here. Those 10 coins are added to that address in the form of a UTXO, so we have an address with one 10 coin UTXO in it.
Now we receive another 5 coins at the same address, like so. Now we have an address with one 10 coin UTXO and one 5 coin UTXO. But how do we view how our addresses are split up into different UTXOs?
Earlier we checked the "Display coin control features" box in Settings > Options > Display. Once that's checked you'll notice there's another section in the Send tab labeled "Coin Control Features". If you click the "Inputs" button, you'll get a new window. And look, there's our 2 UTXOs.
All UTXOs try to stake separately from each other, and remember that the chance a UTXO has to stake is proportional to it's size. So in this situation, my 10 coin UTXO has twice the chance to stake as my 5 coin UTXO. Now wallets, especially ones that make a lot of transactions, can get very fragmented over time. I've fragmented my wallet a little so I can show you what I'm talking about.
How do we clean this up? We can consolidate all this into one UTXO by checking all the boxes on the left and selecting OK.
Now pay attention to the fields on the top:
  • Quantity: The total amount of UTXOs we have selected.
  • Amount: The total amount of coins we have selected.
  • Fee: How much it would cost in fees to send all those UTXOs (more UTXOs = more transaction data = more fees)
  • After Fee: Amount - Fees.
  • Bytes: How large the transaction is in bytes.
  • Priority: How your client would prioritize making a transaction with this specific set of UTXOs selected had you not used coin control.
  • Low Output: If your transaction is less than 0.01 coins (I think).
  • Change: What you will get back in change.
  • custom change address: You can set the address you get your change back at, by default it will generate a new address.
So let's fill out our transaction so we end up with 1 UTXO at the end.
In "Pay To:" Just put any address in your wallet, and for the amount put what it has listed in the "After Fee" Field. Just like this.
Notice how we get no change back.
Now click "Send", we'll be prompted to enter our passphrase and we're asked if we want to pay the fee, go ahead and click "Yes".
Now if we go back to the Overview tab we get this funky icon. If you hover your mouse over it, it says "Payment to yourself", and the -0.0002 GRC is the network transaction fee.
(Ignore the first one, that was me fragmenting my wallet)
Now if we look at the Coin Control menu, we can see that we've slimmed our wallet down from 7 UTXOs to 1.
Now why would you want to use coin control?
2 Situations:
  1. UTXOs less than 0.0125 coins cannot stake. So you can combine a lot of tiny, useless UTXOs into 1 bigger one that can stake.
  2. After a UTXO stakes, it cannot stake for another 16 hours. So if you have 1 large UTXO that is big enough to stake more than once every 16 hours, you can split it into smaller UTXOs which can allow you to stake slightly more often.
  3. By default, the wallet will always generate a new address for change, which can make your wallet get very messy if you're sending lots of transactions. Keep in mind that more UTXOs = larger transactions = more fees.
Sidenote - When you stake, you will earn all research rewards owed reguardless of which UTXO staked. However, you'll earn the 1.5% interest for that UTXO. Not your whole wallet.


A fork is when the network splits into multiple chains, with part of the network on each chain. A fork can happen when 2 blocks are staked by different clients at the same time or very close to the same time, or when your client rejects a block that should have been accepted due to a bug in the code or through some other unique circumstance.
How do I know if I'm on a fork?
Generally you can spot a fork by looking at the difficulty on your Overview tab. With current network conditions, if your difficulty is below 0.1, then you're probably on a fork.
You can confirm this by comparing your blockhash with someone elses, like a block explorer.
Go to [Help > Debug Window > Console]. This is the RPC console, we can use to do a lot of things. You can type help to get a list of commands, and you can type help [command you need help with] (without the brackets) to get information on a command. We'll be using the getblockhash [block number] command.
Type getblockhash [block number] in the console, but replace [block number] with the number listed next to the "Blocks:" field on the Overview tab.
This will spit out a crazy string of characters, this is the "blockhash" of that block.
Now head over to your favorite block explorer, I'll be using gridcoinstats. Find the block that you have the hash for, use the search bar or just find it in the list of blocks.
Now compare your hash with the one gridcoinstats gives you. Does it match?
If it matches, then you're probably good to go. If it matches but you still think you're on a fork, then you can try other block explorers, such as or
If it doesn't match, then you need to try to get off that fork.
How do I get off a fork?
  1. Just wait for an hour or two. 95% of the time your client is able to recover itself from a fork given a little time.
  2. Restart the client, wait a few minutes to see if it fixes itself. If it doesn't restart again and wait. Repeat about 4 or 5 times.
  3. Find where the fork started. Using the getblockhash command, go back some blocks and compare hashes with that on a block explorer so you can narrow down what the last block you and the block explorer had in common. Then use reorganize [the last block hash you had in common]. Note that reorganize takes a blockhash, not a block number.
  4. Use Advanced > Download Blocks.
  5. If none of this works, you can take a look at social media (reddit/steemit) and see what other people are saying.


Your configuration file depends on your operation system:
  • On Windows: %appdata%\GridcoinResearch\
  • On Linux: ~/.GridcoinResearch/
  • On MacOS: /Users/USERNAME/Library/Application/Support/GridcoinResearch/
And it should look like this.
If you open up your gridcoinresearch.conf, you'll see the default one it generated. Note that if you entered your email earlier, the first line will have your email on it instead of "investor". If you decided you want to solo mine but didn't enter your email when you first started the wallet, go ahead and put your email on the first line in place of "investor". If you're a pool miner, just leave it as "investor".
Next, it's recommended that you use the addnodes on the gridcoin wiki. So our gridcoinresearch.conf will look like this.
A useful line for solo miners is PrimaryCPID=[YOUR CPID]. Sometimes your wallet can pick up on the wrong CPID so it's good to have that in there if you're solo mining.


A listening node is a node that listens for blocks and transactions broadcasted from nodes and forwards them on to other nodes. For example, during the syncing process when you're getting your node running for the first time, you're downloading all the blocks from listening nodes. So running a listening node helps support the network.
Running a gridcoin listening node is simple. All you need to do is add listen=1 to your gridcoinresearch.conf and you need to forward port 32749 on your router.
If you don't know how to port forward, I'd suggest googling "How to port forward [your router manufacturer]".

QUICK LINKS Official Website Unofficial Website Block Explorer Block Explorer Faucet Faucet
Gridcoin Wiki
Gridcoin Github
Arikado Pool
And that's all I have for now!
I plan to keep this post up-to-date with changes in the client. So if anyone has any suggestions, have clarifications they want made, or maybe I got something wrong, then please feel free to leave a comment below or PM me!
submitted by Personthingman2 to gridcoin [link] [comments]

PIVX Core Wallet 3.0.5 final release (November 13th, 2017) - Mandatory Upgrade

Github release link
Forum Post

Important Notes

Upgrade instructions

1- Download the appropriate release for your platform from the Github release link. For command line installs/updates this link may help.
2- Start up your client and see if you are on the wrong chain by using this link (Am I forked?) or manually comparing your latest block hash against the [block explorer](
3- If you are on the correct chain, let it fully sync (or as far as it will go) and then repeat step 2. If you are still on the right chain move on to step 4. If you're on the wrong chain, download the chainstate from this link (mirror) and follow the instructions to install it. Do NOT delete wallet.dat or your backups folder. Once this is done, restart your client and let it finish syncing
  1. stop your wallet and/or daemon
  2. locate the folder with the blockchain folders (usually ~/.pivx/)
  3. do a complete(!) backup of this folder in case something goes wrong
  4. completely remove the folders "blocks", "chainstate", "sporks" and "zerocoin"
  5. download one of the snapshot-files (preferably the newest one) above into this folder
  6. unpack the snapshot file: 'unzip '
  7. the folders deleted above are now replaced by the ones from the snapshot
  8. restart your wallet and/or daemon
4- On this step you should be fully synced and on the right chain. Using the debug screen or pivx-cli, use the command
spork show 
to output your spork status. Have a look at spork 16 and make sure the value is 1510179528 (now 1609459199). If it is, go ahead and start staking.
If you are having trouble getting the correct value for spork 16, try adding nodes to your pivx.conf file that are protocol 70912. A list of 70912 nodes can be found at . This can be done from the debug menu or with pivx-cli by saying
addnode add 

Notable Changes

libzerocoin Exploit Fix

zPIV relies on a 3rd party library called libzerocoin. All currencies that utilize the zerocoin protocol use libzerocoin, and many of those currencies have been exposed to an exploit which allowed for the creation of multiple zero-knowledge spending proofs for one single zerocoin mint. The PIVX developers were able properly identify the exploit, track down any fraudulent spending proofs, link the fraudulent spending proofs with their one valid proof that they were mutated from, and remove any mints from the accumulators that were derived from the invalid spends.

zPIV Maintenance Mode Spork

Handling the above noted libzerocoin exploit required the PIVX team to immediately release a patched wallet to as many users as possible which rejected bad spends and also disabled all zPIV transactions in general. The process of releasing a patched wallet in such a small time frame is frustrating and difficult for all members of the PIVX team and especially users of PIVX. The PIVX developers have added a new spork which allows for zPIV transacting to be turned on/off without having to release a patched wallet. This will allow much smoother operation if any problems occur in the future, and should also allow exchanges and 3rd party services to continue to operate even if zPIV is in maintenance mode.

Accumulator Code Refactor

The zPIV accumulator code has undergone a major refactor. Accumulators are one of the most essential components of the zerocoin protocol, and also one of the most computationally expensive parts of the protocol. This refactoring speeds up syncing and spending of zPIV by over 5x. The new code also allows for spending of zPIV with only 2 required mints occurring on the network after your mint has been added, whereas before 3 were required. This refactor allows for lighter resource load and a smoother user experience.

Money Supply Indexing

The exploit in libzerocoin threw off some of the wallet's internal money supply calculations for both the zPIV supply and the PIV supply. User's wallet's will automatically recalculate the supply on block 908001. User's also have the ability to recalculate supply using the startup flag reindexmoneysupply.

More Extensive Tracking of zPIV Supply Through RPC

More information has been added to the getinfo and getblock RPC calls, which now display the total zPIV supply as well as the balance for each zPIV accumulator.

Multisig GUI

Provides functionality which is currently only available through raw transactions. Multisignature addresses require signatures from multiple parties before coins belonging to the address are spent. Accessed through the File dropdown menu.



  • Will I lose piv or zpiv?
    • No. Backup your wallet.dat again for good measure and never delete a wallet.dat file.
  • My wallet is stuck on block ?
    • Check if you're forked (Am I forked?) and then check if you're really on v3.0.5. If you're on the right version and chain, just hang tight and your wallet will find a good node to sync with eventually. Contact support if it's more than a few hours and the problem persists
  • My zPIV balance is incorrect
    • Contact support in discord or via the Support Portal. Please note that during the upgrade period and zerocoin maintenance mode there may be delays.
submitted by turtleflax to pivx [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]

The Hempcoin Community Guide Q1 201

Table of contents:

  1. Preface
  2. Tools:
    • Masternode Calculator
    • Fork Preparedness guide
    • Mining Guide
  3. Current projects
  4. Social Platform Links
  5. F.A.Q's


In the past month, we, the team at The HempCoin have been making some huge changes, both internally and business development wise. We have added 3 new roles to the team: Community Outreach Manager, Business Development Manager, and Brand Ambassadors. Thanks to this, we have had many new developments which have shifted our timeframe a little as you may have seen. That being said, we are committed to ensuring our community is kept as up-to-date as possible and provided with as many support materials as we can create. We've spent the better half of two weeks writing up this guide and the tools included in it, in hopes that it will help answer many of the common questions we have been seeing and even some of the less common ones.


Masternode Calculator:
Ever since we have announced that we will be forking into a masternode coin, we have been asked for the details and specifics of the reward payout for a node. Seeing this, we have created a Spreadsheet that is editable by the community. It will calculate the rewards for any number of nodes, and also tell you the expected payout in USD based on a price the user can input. You can find the link to the sheet here.
Fork Preparedness Guide:
This guide will ensure you will be completely prepared for the upcoming fork. We have been seeing many questions about the fork which is understandable, and hopefully, this will alleviate many of those by ensuring all of our investors know how to make sure they are prepared, no matter their platform.
Windows: Currently there are two options for coin storage on windows. Bittrex, the exchange that THC is currently traded on, or our official wallet. the safest and most secure option would be to store your coins in the private wallet, however, Bittrex has also confirmed with us that they will be supporting our fork. If you are planning on storing your coins there, all you need to do is purchase the THC and leave it be, once we fork, you will get the new coin from bittrex automatically and that is all. If you intend on using our private wallet, you can download the most up-to-date version from our GitHub here. Once you install it, you will need to let it run to synchronize, this has been known to take a very long time (due to having to sync all blocks since 2014). Once we fork, we will ensure this is alleviated, however, for now, you can follow the tutorial that was written here which will help you go from needing about 2 weeks to sync to about 3 hours at max. Either of these coin storage options will ensure you are completely supported during our fork.
Mac: At the moment, our current wallet only supports the Windows platform. Once we complete our fork there will be a wallet available for all platforms including mac an Linux. So, if you do not have access to a Windows PC your best option for securely storing your coins during our fork is to store them on Bittrex. They have confirmed with the team that they will be supporting the fork so your coins will be safe with them.
Linux: As you may have read above, our wallet currently only officially supports the Windows platform at the moment, however, there have been users who have reported that they have been successful in installing the wallet on Linux. However, at the time, we do not officially support the platform. Our advice would be the same as provided to the Mac users, storing your coins on bittrex would be the best option until our Linux wallet is available.
Android: Currently, the only wallet we know of that will support THC on android is Coinomi. The community has been asking on their support forum if they will be supporting the fork and the reply that was received was somewhat unsure. They stated that no coins will be lost, but never confirmed if they would be adapting to the new algo and giving out any new coins. As the team, we have not heard whether or not they will be supporting the fork so the best plan for android users would be to either transfer your coins to a windows wallet, or to bittrex to ensure you are supported. We are not saying coinomi will not support the fork, however, it is an unknown, and we would prefer to ensure that there is 100% support.
Mining Guide:
Lately, we have seen quite a few inquiries about the possibility of mining THC. Currently, there is only one pool that we are aware of which is hosted on the The tutorial written below will cover how to get started mining with an NVIDIA GPU using the mining-dutch servers, on a Windows-based PC. AMD GPU's have a very similar process, the main difference will be that you need to swap out the program CCMiner for a program which supports the AMD architecture.
To start mining you'll need a few things:
  • A decent GPU (as many as possible really, these are the brains of the operation).
  • A fairly well-ventilated PC case(if you're just mining with your gaming PC)
  • Instead of a PC case a lot of big-time miners just use shelves and build the multi-GPU rigs on those.
  • A mining program (For this tutorial we will be using CCMiner but there are plenty of great alternatives out there too)
  • A pool to mine from (Think of this as a meeting place for all the GPUs to team up and mine faster)
Now that we know what we need to mine, let's get started on setting it up:
  1. Download the correct version of CCMiner: CCminer for 32bit systems or CCminer for 64bit systems (both of these files are just pulled straight from the github).
  2. You may need to install a program to open 7z files such as WinRar.
  3. Extract these files to somewhere like C:\Program Files, or at least somewhere you won't forget about them.
  4. You should see an api folder, a program called ccminer.exe (sometimes ccminer-x64.exe) and a few other small files. What you want to look for is ccminer.conf, this is your config file. You use this to tell your program what pool to mine from.
  5. Open up ccminer.conf with notepad or notepad++ if you have it installed (or really any other coding software) and now we can get to the file editing.
  6. When you open ccminer.conf you should see something that looks like this. (excuse the pastebin link, reddit doesnt seem to like code in lists.)
  7. Next, go to the mining-dutch link and setup an account. (Direct link to signup page)\
  8. (These next links will likely only work once you register and sign in)
  9. Proceed to the workers page (Normally found under My Account>My Workers)
  10. A worker is essentially telling the pool what machine is working for you. Create a new worker by entering in "Workername" "Password" and check the monitor box. Now just hit create.
  11. Now, go back to the ccminer.conf file that we opened earlier. If you follow this link you should see something that looks very much like your file, however, it also has labels, #1, #2, #3.
  12. On your file, fill in #1 with "stratum+tcp://" (this can be found on the mining dutch website, its just hidden. In the top right, click the cloud with the blue icon (getting started) then scroll down to the Vardiff address for Hempcoin)
  13. #2, enter your "loginname.workername" Login name being your username to login to mining-dutch, then workername being what you just named the worker we created.
  14. #3 can be filled with anything, they don't use passwords.
  15. This should really be all you need. Now save the ccminer.conf and then just run ccminer.exe
If all of this was done correctly you should see a command-prompt window pop up and your machine start to mine. It takes some time to get going so that is not unheard of, and also, if you look at the dashboard you may not see your worker show up for a while. This is normal, it uses averages over time to tell you what performance it is getting so it won't have a proper value for a few minutes.

Current Projects

We are always working on advancing all of our roadmap goals, however, lately, we have been focusing on a few key projects which are listed below (in no specific order).
  • Putting the finishing touches on the new wallet.
  • Ensuring bittrex is ready for the fork.
  • HempPay.
  • Merchant Services
  • Our mobile app
  • Graphics that will better represent the new THC.
  • A brand new website (launching soon!).
  • Connecting with many different owners/affiliates/partners to businesses which would like to use THC locally.
  • Implementing the ambassador program
  • Internal organization to ensure everyone is on the same page at all times.

Social Platform Links

One of the larger changes we have made is to bring a community outreach manager onboard to work on communication. We may have had missteps in the past, however that is in the past, we have changed and want to ensure we show you that change! Keeping in line with that, we have heard your cries for a more community-oriented social stance, so, we have created an official discord chatroom where anyone can come and chat with some of the devs, or the rest of the community to stay in the loop. We have also created a telegram more recently, which as of the date of typing this, has over 1000 members already, and it was only released less than a week ago. We do ask that everyone who joins reads over the rules that are posted in both locations and abides by them so we can have a clean and organized community. We are always looking to expand and if you have any more suggestions feel free to let us know!


Q: I transferred X amount of THC to my wallet, but it's missing? A: The first step to ensuring you never lose any THC is to confirm the wallet address. Always, always, always double and triple-check that the address you input is the same as your address. If there are ANY typos at all, you will not receive your coins. If you have checked and are sure that the address is correct, check your wallet. If you have just installed it, chances are you are still syncing with the blockchain; you will need to wait until you are caught up to see the THC. It's best practice to sync your wallet before you make any transfers. To check the status of your synchronization, check the debug menu in the wallet, it will show you the exact date you are synced to. Lastly, if you are for sure synced, and you have used the correct address, check the transaction ID on the block explorer. This will show what happened with the transaction and allow you to follow where it went. It could also still just be in progress, sometimes it can take up to an hour if there are service delays with the exchange or even just your internet connection.
Q: Why have there been so many delays with THC? You have been around forever! A: Although THC was one of the first 30 cryptocurrencies mined in 2014, the unfortunate truth is that before April 2017, there was no active full-time team. Since then, the original THC FoundeDeveloper and current CEO Tim has worked hard to add incredible new developers, a business outreach team, an entire marketing team, and the brand ambassadorship program. It has taken us a little time to organize, but we are finally in sync as a team and prepared to unleash this business on the world.
Q: When is the fork? A: As many of you have noticed, our whitepaper says fork will occur by Q2, while we previously announced Feb. 23rd. We did this not to provide our community with doubts, but to allow ourselves an added bit of time for our dev team which, like the rest of our team, has added new members in recent months. Due to this, we are far further along with our HempPay platform than we thought possible; as such we will be hiring 3rd party code auditor to audit our code to ensure we run as smoothly as possible. We would much rather delay a fork than risk any of our investor's privacy or security and fork too early. We also want to reiterate that we have a direct line with Bittrex and they will 100% support our fork. We do appreciate everyone’s patience with this transition into the future of THC; we’re working hard to ensure that we fork as early as possible.
Q: Will Bittrex be supporting the fork? A: We have seen this question come up many times now and the answer is, and will always be, yes. Bittrex is well aware of our plans and they know exactly where we stand regarding the fork date. Bittrex has also asked requested our community stop creating support tickets just to confirm the fork. They have been overwhelmed this week with the same question over and over. The final answer here is yes, Bittrex will be supporting the fork and we are in constant contact with them to ensure everything is going as planned.
Q: Will purchases with a credit card to HempPay count as cash advances? A: We are still in the middle stages of building HempPay and finalizing the format for operation and contractual agreements. We intend to partner with exchanges and use their API to make the purchases, so buying THC through our app will have the same effect as using your card to purchase straight from an exchange. Please note that HempPay is still in development so exact details may be subject to change.
Q: What is the cost for a masternode? Some say 10,000 others say 20,000 THC is required. A: To run a masternode, 20,000 THC will be required. We do acknowledge that during our transition, we had originally stated 20,000 and then our team announced 10,000 THC will be required. We have since readjusted our plan, realizing that the low requirement would sink MN profits and lower incentive. Instead, we returned the requirement to 20,000 THC and increased the node reward by 66%. For more information please check the masternode calculator in the Tools section.
Q: I heard Bittrex may delist THC. What?? A: Short answer: No and not even close. Long answer: This rumour was started over a year ago, it was based on a Bittrex Support post from January 27th, 2017. The only post we appear in is the one mentioned above. You will also see that we only appear due to being listed as a potential for removal, due to a lack of volume as most altcoins saw at that time. You will note the size of the list of altcoins here. We are now in direct communication with Bittrex daily and we unequivocally state that there is no need to worry about us being removed at all.
submitted by zacharyd3 to thehempcoin [link] [comments]

Dogecoin on Linux - The Complete Beginner's Guide

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

Release : Bamt v1.6.0 - [Scrypt, Scrypt-N, DarkCoin, QubitCoin, MyriadCoin, and Quark]

Questions or Feature Requests

  • Please search first!


  • Greatly appreciated! I am spending a lot of time on this. Donations make it easier to justify to myself and family.

  • VTC = Vy5xkGANcCdKWmHagTyWNRNzfC2D3f9zSG
  • DOGE = DKLrk9iYXaEqe3DJjoG6vkh97yZzTrwpCT
  • BTC = 1Ju4JCP4ifu4JWn6GdeWMc2g2zDTFQXHge
  • Or just let the mine point to the example pool for a while, the default addresses are mine.

Installing Pick

  • Pick is an awesome version and build utility for miners.
  • Download and follow the instructions. Silly easy. Source
  • Thanks to zettahash for making this!

Installing CGWatcher


What is BAMT?

  • BAMT is a Linux live distribution made specifically for mining cryptocurrency.
    • Out of the box, it can mine Scrypt, Scrypt-N, DarkCoin, QubitCoin, MyriadCoin, and Quark!

About BAMT

  • BAMT is designed with several goals in mind :
    • No installation; runs from a USB drive.
    • Go from assembled parts, to mining, quickly.
    • Very little configuration needed.
    • Multiple miners included.

v1.6.0 New Features & Updates

  • New Features :
    • Added new miners!
      • Vertminer 0.5.2 "the kev"
      • Sgminer 4.0.0 "troky" - Scrypt-N Enabled
      • Sgminer 4.1.0 "sph - DarkCoin/QubitCoin/Quark"
      • Cgminer 3.7.2 "kalroth"
    • All miners and configs selectable from the bamt.conf file.
    • No need to set scrypt type flags inside the bamt.conf file.
    • Secondary USB drives now auto mount.

General Details & Features

  • Driver Details :
    • AMD Catalyst 13.12
    • AMD APP SDK 2.9
    • AMD ADL SDK 6.0
  • Included Miners :
  • Monitoring :


  1. Download Vertcoin BAMT v.1.6.0
    • MD5 : 4D141BEDA91C0845BD4ABB4F96FB163F
    • : here
      • This sometimes goes down. Be patient and wait.
    • Torrent : here
      • Please seed.
  2. Download Win32 Disk Imager or use dd.
    • Win32 : here
    • Write the .img file to a ~2GB or larger USB drive.
  3. Put the USB drive into your machine and boot up.
    • Connect via monitor or Remote Desktop in via your mine's IP.
    • You can find the IP via your network, or you can look on the desktop display of BAMT.
    • Default User Name = root
    • Default Password = live
  4. Select your miner and conf file inside /etc/bamt/bamt.conf.
     # Set to the config of your choosing. # CONFIG OPTIONS : cgminer_opts: --api-listen --config /etc/bamt/vertminer.conf # cgminer_opts: --api-listen --config /etc/bamt/sgminer-troky.conf # cgminer_opts: --api-listen --config /etc/bamt/sgminer-sph.conf # cgminer_opts: --api-listen --config /etc/bamt/cgminer.conf # Set miner over-ride if you want something other than cgminer. # MINER OPTIONS : # Vertminer 0.5.2 "the kev" # Sgminer 4.1.0 "troky" # Sgminer 4.1.0 "sph - aka - DarkCoin/QubitCoin/Quark" # Cgminer 3.7.2 "kalroth" # !! Set all to 0 for cgminer. !! miner-vertminer-thekev: 1 miner-sgminer-troky: 0 miner-sgminer-sph: 0 
  5. Update your selected miner conf file inside the directory /etc/bamt/.
  6. View your mining status.
    • You have a few options :
      • View standard dashboard at your miners IP address.
      • https://youripaddress/
    • View PoolManager dashboard.
      • https://youripaddress/cgi-bin/
      • Page is cool. You can change your pool and add new via Dashboard!
    • View the classic CGmineVertmineWhatever terminal screen.
      screen -r 

Terminal Commands

Note : All commands assumed user has root permissions. 
Save & Reboot :
sync && coldreboot #Note : When making changes to a usb based system, you must run 'sync' to save to USB before restarting. 
Control Mining :
mine stop mine start mine restart 
Display GPU Status :
gpumon #Note : I like screen -r over gpumon. 

Example Results

  • Setup :
    • GPU : Asus DCII 280x @ ~350-400 kH/s Vertcoin or 750-815 kH/s Scrypt
    • CPU : AMD Sempron
    • Memory : G.Skill Ripjaws Series 8GB (2 x 4GB)
    • Motherboard : Gigabyte GA-990FXA-UD3 ATX AM3+
    • PSU : (2) EVGA Supernova 1000w - (w/ add2PSU )

Change Auto-Reboot

Change hours by changing the "#" - or - delete line to remove auto-reboot :
nano /etc/crontab 
Modify this line :
0 */9 * * * root /sbin/coldreboot 


  • Miner ID and Location :
    • miner_id & miner_location in bamt.conf must be lowercase.
    • miner_name may be upper case.
submitted by Bajawah to BAMT [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]

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

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

Release : Vertcoin BAMT

Questions or Feature Requests

What is BAMT?

  • BAMT is a Linux live distribution made specifically for mining cryptocurrency.
    • While it's called "Vertcoin BAMT", it will work with any Scrypt coin or coin using Vertminer. This name will be changed in the future versions.

About BAMT

  • BAMT is designed with several goals in mind :
    • No installation; runs from a USB drive.
    • Go from assembled parts, to mining, quickly.
    • Very little configuration needed.

v1.5.2 New Features & Updates

  • New Features :
    • Select CGminer or Vertminer in bamt.conf flag.
    • Select matching miner .conf file in bamt.conf.
    • Added BAMT Poolmanager
    • Appearence slightly tweeked to match FlatBAMT UI.
    • Standard dashboard still active.
    • GitHub - Thanks to Starlilyth!
  • Updates :
    • Stock .conf settings should run on 99% of hardware.
    • Terminal "mine" commands functional with all miners.
    • Shrunk file size.
    • Bitch'n new subreddit.

General Details & Features

  • Details :
    • Based on Litecoin BAMT v1.5
    • AMD Catalyst 13.12
    • AMD APP SDK 2.9
    • AMD ADL SDK 6.0
    • SGMiner 4.1.0
      • Note : It is called "CGminer" but it is in fact renamed SGMiner.
      • There is a bug with 290x and powertune. Fix is to switch to cgminer:
        mv /opt/miners/cgminer /opt/miners/sgminer; mv /opt/miners/cgminer3.7.2 /opt/miners/cgminer; mine restart; 
  • Added Features :
    • FlatBAMT UI
      • GitHub - Thanks to Wellsriley!
    • TheKev Vertminer 0.5.2
      • BitcoinTalk - Thanks to TheKev!
      • Note : Vertminer is still in /opt/miners if you want to put it back.
    • Auto-Reboot Cronjob
      • Keeps your machine running well 99.9% of the time.
      • Timer set for every 3 hours.


  1. Download Vertcoin BAMT v.1.5.2
    • Mega : here
      • This sometimes goes down. Be patient and wait.
    • Torrent : here
      • Please seed.
  2. Download Win32 Disk Imager or use dd.
    • Win32 : here
    • Write the .img file to a ~2GB or larger USB drive.
  3. Put the USB drive into your machine and boot up.
    • Connect via monitor or Remote Desktop in via your mine's IP.
    • You can find the IP via your network, or you can look on the desktop display of BAMT.
    • Default User Name = root
    • Default Password = live
  4. Change your "miner".conf file.
  5. Select your mining type in bamt.conf.
    • Comment out the one you are not using. ~line 112
      # cgminer_opts: --api-listen --config /etc/bamt/cgminer.conf cgminer_opts: --api-listen --config /etc/bamt/vertminer.conf 
    • Set the value to 1 if using Vertminer. ~line 118
      scrypt-adaptive-N: 0 <-- That value. 
  6. View your mining status.
    • You have a few options :
      • View standard dashboard at your miners IP address.
      • https://youripaddress/cgi-bin/
    • View PoolManager dashboard.
    • View the classic CGmineVertminer terminal screen.
      screen -r 

Terminal Commands

Note : All commands assumed user has root permissions. 
Save & Reboot :
sync && coldreboot #Note : When making changes to a usb based system, you must run 'sync' to save to USB before restarting. 
Control Mining :
mine stop mine start mine restart 
Display GPU Status :
gpumon #Note : I like screen -r over gpumon. 

Example Results

  • Setup :
    • GPU : (4) Asus DCII 280x @ 400 kH/s Vertcoin or 800 kH/s Scrypt - (going to add 2 more)
    • CPU : AMD Sempron
    • Memory : G.Skill Ripjaws Series 8GB (2 x 4GB)
    • Motherboard : Gigabyte GA-990FXA-UD3 ATX AM3+
    • PSU : (2) EVGA Supernova 1000w - (w/ add2PSU )
  • Note : My configs can be found in /etc/bamt/examples.

Change Auto-Reboot

Change hours by changing the "3" - or - delete line to remove auto-reboot :
nano /etc/crontab 
Modify this line :
0 */3 * * * root /sbin/coldreboot 


  • Miner ID and Location :
    • miner_id & miner_location in bamt.conf must be lowercase.
    • miner_name may be upper case.


  • Main Changes :
    • Clean up legacy code.
    • Update graph style ( responsive ).
    • Update Dashboard style ( responsive ).
  • Sync Up :
    • Roll changes into main BAMT BitBucket build.
    • Roll changes into PoolManager GitHub build.
  • Small Irrelevant Things :
    • None currently.


  • Greatly appreciated! This is eating a lot of time up. :)
  • VTC = Vy5xkGANcCdKWmHagTyWNRNzfC2D3f9zSG
  • DOGE = DKLrk9iYXaEqe3DJjoG6vkh97yZzTrwpCT
  • BTC = 1Ju4JCP4ifu4JWn6GdeWMc2g2zDTFQXHge
  • Or just let the mine point to the example pool for 30 min, the default is set to me. :)
submitted by Bajawah to BAMT [link] [comments]

what hidden servers are running on 2017 edition

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

I have created 2 super p2pool nodes. How do I verify they are connected?

I have miners in a two locations and after being frustrated with orphan and rejection rates on my p2pool I decided to create a network of p2pool nodes renting IaaS.
I have ohio and northern california
How do I verify they are connected. I tried editing vertcoin.conf as recommended in this article
and I tried ' - n ' as a command argument as recommended by:
When I look at the connected peers I don't see the ohio IP address in the california node.
Is there any other way to know? am I doing something wrong?
Cheers, James
submitted by Madeof_Tin to VertcoinMining [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 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]

Bitcoin JSON-RPC Tutorial 2 - VPS Setup Bitcoin JSON-RPC Tutorial 3 - bitcoin.conf bitcoin wallet How to Install Bitcoin Core Wallet on Ubuntu 16 Pettycoin: Losing Tiny Amounts of Bitcoin At Scale! [ 2014]

Note that for Windows the location of the configuration folder where bitcoin.conf is located is saved in the registry. Its default path is indeed C:\Users\<username>\AppData\Roaming\Bitcoin but if that location was changed then in order to find the current folder you will have to look in HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt at the REG Forex Software for Linux Otherwise, lnd will attempt to get the configuration from your .Bitcoin And Bitcoin Best Online Trading Platform For Forex Cash . Bitcoin Wallet Android linux bitcoin conf location Bip38 trade stock market simulator You can easily set up Bitcoin in Ubuntu using the commands below: Bitcoin blockchain pruning Start Bitcoin, now you will see all the files are created in the new data directory. Linux. By default Bitcoin will put its data here: ~/.bitcoin/ You need to do a "ls -a" to see directories that start with a dot. If that's not it, you can do a search like this: find / -name wallet.dat -print 2>/dev/null Mac. By default Bitcoin will put its Linux Bitcoin Conf Location; Occasionally the format of those files changes, but the new Bitcoin Core version will include code that automatically upgrades the files to the kryptowährung kostenlos handeln new format so no manual intervention is linux bitcoin conf location required.! The default linux bitcoin conf location settings can result A recurring problem when helping new users getting started with running Bitcoin Core is the config file location; a lot of uncertainty is caused by the config file and the folders it should go in not being created automatically by the in...

[index] [9033] [23021] [27713] [8474] [16715] [1673] [11245] [9304] [8306] [6070]

Bitcoin JSON-RPC Tutorial 2 - VPS Setup

bitcoin ubuntu bitcoin.conf bitcoin linux bitcoin block explorer trade bitcoins buy a bitcoin bitcoin sell ... Location: United States Restricted Mode: Off History Help Bitcoin JSON-RPC tutorial. Set up your bitcoin.conf file and create custom settings with bitcoind. BTC: 1NPrfWgJfkANmd1jt88A141PjhiarT8d9U. Ubuntu -1 Setting up Bitcoin Commands, sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install bitcoin-qt sudo apt-get install bitcoind sudo blkid sudo nano /etc/fstab ... Bitcoin uses a shared ledger: currently 13GB, and fewer nodes will be able to keep up as popularity grows. This talk presents a pre-alpha implementation of an adjunct network where gateways ferry ... In this video we will build Bitcoin Core from source and run a Bitcoin full node on a linux server. ... $ sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev ...

Flag Counter