Petter Reinholdtsen: How to backport bitcoin-qt version 0 ...
How to compile and install Bitcoin Core on Debian Wheezy
How to compile and install Bitcoin Core on Debian Wheezy ...
Easy UASF Node in Debian VM tutorial
So if you have a moderately powerful gaming desktop with a Quad-Core CPU like an i5 or better and 8+GB of RAM, you can easily run your own little UASF node in the background. Once it's done syncing with the network, you won't even notice it's there. Here's how. You will need :
Some sort of virtualization solution (I used Hyper-V)
Enough disk space for the blockchain (around 130GB, but you also need room for it to grow)
The following assumes you know how to install Linux in a Virtual Machine Step I. - Installation. Go through expert install and set up a base system with only ssh server enabled. For partitioning, you can do just one big disk and everything in one partition, but if you happen to have a computer that has both SSD's and HDD's, it would be optimal to create two virtual disks and use a small one for the OS on the SSD and a larger one on the HDD in a custom mount point for the blockchain. Reboot and ssh into the server. Step II. - Build requirements. A few things need to be taken care of. First, you'll want to edit the /etc/network/interfaces file and set up a static IP. Once that's done, stop by your router and make sure that traffic on port 8333 is forwarded to your debian VM. Then, install some packages we need :
...and wait about thirty hours to sync with the network. You may want to visit the /whereveyou/want/youblockchain directory and create a permanent bitcoin.conf in there. To enable RPC calls to the server and get it to accept bitcoin-cli commands you'll want to use it to create a usepassword and copy that to your user's /.bitcoin/bitcoin.conf. Minimal bitcoin.conf example
Security I recommend you disable password login and use private key authentication only on ssh, and also restrict iptables rules to the bare minimum that must be allowed for this application. You will need this in your iptables script :
# Allows BITCOIN traffic from anywhere -A INPUT -p tcp --dport 8333 -j ACCEPT # Allows RPC calls to the bitcoin server from localhost -A INPUT -p tcp -s 127.0.0.1 --dport 8332 -j ACCEPT
pub 409665FFB764 2012-05-08 [expires: 2019-05-07] uid Wheezy Stable Release Key [email protected] We can clearly see that key B38A8516 is expired. I have tried this command without succes : sudo apt-key adv --keyserver pgp.mit.edu --recv-keys B38A8516 Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.66fa6TtioE --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d/bitcoin-bitcoin.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyserver pgp.mit.edu --recv-keys B38A8516 gpg: requesting key B38A8516 from hkp server pgp.mit.edu gpg: key B38A8516: "Oracle OSS group (Open Source Software group) [email protected]" not changed gpg: Total number processed: 1 gpg: unchanged: 1 I have even tried to remove the key manually with apt-key del B38A8516 and reinstall it. I always end with the same expired keys... Anyone have a hint on this ? I'm completly lost... Cheers, Trustinor
To the moon! Dogemining with BFGMiner, Debian, and ATI.
Visitor from the future! Hello. I'm a newbie digger and recently setup my first dedicated mining box in Debian. I'm not the most experienced Linux user, but the machine had started with Debian Squeeze and I couldn't find its old Windows key. (Also please forgive formatting errors, I'm new to this whole "Reddit" thing as well.) I found a number of guides to misdirect me on my way, so I decided to write up a sort-of (or at least hopefully up-to-date) guide to create a Dogecoin miner on Debian with AMD cards, using BFGMiner to mine coins. Expert digging shibes: I would certainly appreciate feedback to improve this guide. This is not a headless mining guide. I have not reached that level of mastery yet, though I believe it is well within reach. HOWTO
Start by installing Debian Wheezy. Make sure you install the Desktop Environment package. Not only did I fail to make things work when installing X after the fact, but having the web browser will be convenient.
Unpack the BFGMiner source into a directory somewhere.
Open a terminal (shouldn't have to be root), cd to the directory with the BFGMiner source, and run: ./configure --enable-scrypt --enable-opencl
Once that completes, run: ./make
You'll see a lot of output from the build, but if everything goes well you should then be able to run ./bfgminer. You can test it by running: ./bfgminer --scrypt -S opencl:auto -o (pool URL here) -u (your worker's username for that pool) -p (your worker's password for that pool). It won't be very fast, however.
Using your preferred text editor, make a new file in your BFGMiner directory, such as "doge_dig.sh". Add the following: #!/bin/sh export GPU_MAX_ALLOC_PERCENT=100 export GPU_USE_SYNC_OBJECTS=1 ./bfgminer --scrypt --scrypt -S opencl:auto -o (pool URL here) -u (your worker's username for that pool) -p (your worker's password for that pool)
In your terminal, chmod 500 doge_dig.sh
You can refer to this wiki source to understand the output from BFGMiner 3.10.0. The one gotcha I've observed is that BFGMiner will happily start off showing hash rates in KHash/sec, and after the first accepted block it will jump to MHashes/sec. When I first saw my hash speed appear to drop from "250" to "0.2", I panicked a little before seeing it had changed its orders of magnitude. If you think you're still mining slowly, you might need to bump up the intensity for BFGMiner. Higher intensity means more work, and it's possible to create hardware failures if you set it too high. For my HD 5870s, I use an intensity of 12. You can either set the intensity by adding "-I 12" to the ./bfgminer line of doge_dig.sh, or you can adjust the value by pressing M in BFGMiner and working through the menu system from there. Bonus: Multiple cards What happens if I have multiple ATI cards on one rig, you ask? I had the same problem, and OpenCL would only recognize one of them! It turns out that there's an easy solution, but it costs $1.25 in resistors from your local radio shack: http://www.overclock.net/t/384733/the-30-second-dummy-plug Plug the finished product from there into your second card. If you have more than two cards, you'll need to make one for every card you want to recognize without a monitor attached to it. Reboot and restart your mining, BFGMiner should recognize all of your cards now. In theory, the above technique should allow you to run completely headless, as long as you also install SSH and be sure to have your script export DISPLAY=:0 before running BFGMiner. I haven't tried this, though. Happy mining and welcome to the Moon! I hope this is helpful to someone.
I just installed bitcoind, litecoind, and dogecoind on a new VPS running Debian Squeeze. The daemons were built from source. Bitcoin and dogecoin synced fine, and run just fine. Litecoin however, keeps randomly crashing, and I had to constantly restart it to allow it finish syncing as I thought it's something to do with RAM or buffers or the sort. Even after it finished syncing, it still randomly crashes without any clues. None of the logs in /valog/ have any mention to this. Here's a link to the last 20 lines of litecoin's debug.log when it crashes on several occasions: http://pastebin.com/XJUQYwkU And memory usage: http://i.imgur.com/Dnv6wy2.png What on earth is going on here?
Thank GNUtransfer the loan us a VPS and other resources to write this article. While it is a bit tedious to install bitcoind 0.8.0 on Debian Squeeze, improvements in this version make it worth the work, performance is far superior to previous versions and I/O disk have been significantly reduced. Now let’s start with the installation. 1.Change the sources.list to use squeeze repositories; 2.Now you can install Berkeley DB version 4.8 (libdb4.8) Downloading and Compiling Bitcoin Core. Configure the system for compilation ; Compile; Installing and Running Bitcoin Core; Extra; Do you want to use Bitcoin on Linux? This tutorial explains how to install and use Bitcoin Core on Debian Linux. Bitcoin Core is the official Bitcoin ... The new debian source package (version 0.7.2-2) was uploaded yesterday, and is waiting in the NEW queue for one of the ftpmasters to approve the new bitcoin-qt package name. And thanks to the great work of Jonas and the rest of the bitcoin team in Debian, you can easily test the package in Debian Squeeze using the following steps to get a set of working packages: git clone git://git.debian.org ... This tutorial explains how to install and use Bitcoin Core on Debian Linux. Bitcoin Core is the official Bitcoin Wallet from bitcoin.org. I will use the latest version from the GIT repository at bitcoin.org. In order to compile and run, Bitcoin Core depends on some other tools which must be installed prior to compiling : Install some dependencies: Instructions on Building Bitcoin 0.5.3 from Source on Debian 6 (Squeeze) You might have guessed from my last post regarding the utter irrelevance of all work done on "Bitcoin Core" since the 0.5.3 release (and arguably since the wallet encryption fix release, as TXID's aren't terribly important in the ways that most people derping on the topic would like them to be) that I was working on some ...
WOW!! THE BITCOIN PRICE GETTING A LONG SQUEEZE SOON?! BTC Longs At All Time Highs!!
DISCLAIMER: Leverage trading Bitcoin is VERY risky, and 70-80% of all traders lose money. Make sure that you understand these risks if you are a beginner. I only recommend crypto trading to ... Bitcoin halving targets, price analysis, news, update. Bitcoin and chainlink prediction. BTC Halving Bullish or Bearish? 🎰 Follow me on Twit... How to compile and run BTC/LTC Wallet from source on Debian based systems. Good work! DISCLAIMER: Leverage trading Bitcoin is VERY risky, and 70-80% of all traders lose money. Make sure that you understand these risks if you are a beginner. I only recommend crypto trading to ... Is there a big Bitcoin long squeeze incoming when the Bitfinex longs collapse? I'll use technical analysis on the Bitcoin price to make a Bitcoin price prediction. Watch the video to learn more ...