There is a nice wiki page here: https://en.bitcoin.it/wiki/Mining_hardware_comparison
The raspberry pi is listed by its processor in the arm section: ARM1176JZ(F)-S. It gets 0.2 Mhash/s when clocked at 800 MHz.
The Raspberry Pi uses the VideoCore IV series of GPU, which to my understanding are either a single or dual core GPU running at or around 700 MHz. Since the primary benefit of GPU mining is that you can run many parallel processes on the hundreds of cores typically found in most GPUs, the single-core nature of the VideoCore GPU undoes most of that benefit.
Just some thoughts:
As of the time of writing the main net's full blockchain size is 21,670,092,800 bytes, a bit more than 20 GB, that is. So you should have way more disk space that just 20-30 GB.
A Raspberry Pi runs with an SD. SD is known for its limited rewriting capabilities (it's not a heavy duty storage solution, it will bite the dust after a while) ...
I set up my rasp pi b+ and U3 mining rig using the instructions in this forum post, with screen and cgminer.
The command relevant to over clocking the raspi that I used is the following:
sudo ./cgminer --bmsc-options 115200:0.57 -o POOL -u USERNAME -p PASSWORD --bmsc-voltage 0800 --bmsc-freq 1286
Those last two options (bmsc-voltage and bmsc-freq) are ...
Yes and no.
As far as FPGAs are concerned, I see no reason why you should not, technically, be able to handle a getwork on one of these and pass the work units to one or more FPGAs via USB.
These units do not, however, have a PCIe slot nor do they have any connectors which, to my knowledge, are capable of connecting to an external PCIe enclosure box, so ...
You can run a Raspberry Pi with bitcoind no problem. I have several Pi's running bitcoind in various locations and some of them have over 100 connections. Use a 64GB flash card and make sure you have a 512MB swap file. The only limitation you will find is your broadband upload speed , the Pi or it's flashcard will not be the bottlekneck. Use a good quality ...
It will by default use all CPU cores available.
However, if the database cache is too small, your node will spend its time fetching and writing database entries from/to disk, rather than verification
You can set the size of the database cache using a bitcoin.conf setting dbcache=N, where N is the number of megabytes of RAM.
Copying .bitcoin folder should work. Make sure bitcoind is not running (try ps -ef | grep bitcoin) before you attempt to copy. Also make sure bitcoin.conf is same in both places
Also, change the bitcoin.conf file with the new datadir , rpcuser and rpcpassword
Doing it that way for an FPGA or ASIC would be very easy, once you have the FPGA or ASIC. All you need to talk to an FPGA or ASIC is a USB port and the software required is very simple. You would need a PC somewhere to act as the mining controller. Of course, if you're mining in a pool, the pool provides the controller, so no issues there.
Using a GPU is a ...
You can't avoid downloading the block chain with Bitcoin Core or any other full node. That is inherent to their functioning.
You don't have to store it, however, if you enable pruning. This would reduce your storage needs to 1 GB or less.
If all you want is to make transactions, and you're satisfied with having to trust other servers a bit more, you ...
You'll attain about 0.1MH/s with an overclocked and overvolted Raspberry Pi. 963437 years on average to generate a block, or averaged to 0.00000007 BTC a day when using a pool. Not enough to cover the 5W power draw.
Will a bitcoin lightning node run on a raspberry pi zero?
This probably depends on what you are doing on the node, how much traffic it gets, etc. I have one running on a Raspberry Pi 3B with basically no traffic and its currently utilizing virtually no CPU and 0.8% memory.
Does it have to have the full Bitcoin blockchain synced or can it
connect to a ...
Reading this in 2017 with a chuckle. The Pi is pretty much the defacto controller due to its low cost and energy use. I have one running an ASIC over USB with cgminer, compiled on the Pi.
Some of Bitmain's Antminers use Beaglebone Blacks (TI?), I'm not sure why. I'm in a Debian ARM mailing list and there are more little ARM machines than I can count. ...
The one thing I should probably answer on is about the difference between OpenGL / OpenGL-ES and OpenCL. Both OpenGL and OpenCl can be used for SHA256d hashing, but OpenCl is used much more frequently.
Where as GL means Graphics Language and CL stands for Compute Language. GL is for graphics and CL is for mathematical and scientific calculations. While ...
Might as well give this old question an answer.
cgminer 3.7.2 (which was obsolete even when this question was asked) required scrypt to be enabled as a compile-time option with ./configure --enable-scrypt. The asker evidently did not enable it, which is why it does not work.
It appears that current versions of cgminer have removed scrypt support ...
I have 2 u3 antminers running on a raspberry pi b+
I could not get my u3 any faster until i used minera software,set to cgminer (offical)
with command: --au3-volt 830 --au3-freq 250.0 In the settings menu
it will run at 62-63 GH/s.
you can download it hear http://getminera.com/
It possible to inject hardware detecting code into code of your mining software, but to protect the mechanism you cannot publish it as an open-source. That will make your currency not so popular as others. Even if you will be succesful there are people that will change the Raspberry Pi CPU and pass-by your mechanism.
It does work. Yes you need an external HD for the blockchain data (unless you want to run a pruned node) and Raspian is fine.
In my opinion the best tutorial for setting up a full node on RP3 is this:
Damian Mee's Guide
Like others have answered, you don't need to store the entire blockchain, in your bitcoin.conf file, you can just specify the number of blocks to keep and the old blocks will be pruned.
I was doing this last night on my Raspberry Pi 3 b model. I installed Raspbian and then downloaded and installed the btcd full node implementation. It was able to download ...
I don't think this is possible; you'd have multiple node instances trying to read/write a single data directory. This is not the intended operation, you'd likely end up with corrupt data.
If you must run multiple independent nodes and are worried about storage requirements, I'd recommend looking into 'pruning mode', it will limit the storage requirements ...
That sounds like it's going out of memory and is killed by the system. Especially on a low-memory device like an RPi3 this seems very likely.
For information on how to reduce bitcoind memory usage, see https://github.com/bitcoin/bitcoin/blob/master/doc/reduce-memory.md
Based on the source cpuminer has a --coinbase-addr parameter which accepts a bitcoin address (for example: ./cpuminer --coinbase-addr=1abcdef..., I believe you only need to set this.
The program checks if you have provided an address and if not then switches to "getwork" mode, unless you disabled it by adding the --no-gbt command line switch.
Yes it is technically feasible to solo mine with a rpi3. The 'fastest' miner you could run would be minerd. However, there is a slim-to-none chance you will ever mine a block on the bitcoin mainnet, but there is still a chance! I would save the trouble of building minerd and use bitcoind's build in block generator
bitcoin-cli setgenerate true 1
You don't ...
You should uninstall the installed version first completely with sudo apt-get remove bitcoind before manually building the binaries from source. Make sure that you backup your wallet (and eventually Blockchain) first (so Keep your data-directory).
Don't run the build in teh bin folder! The sudo make install command will install more than just the binary on ...
You do need to store data on an external SSD disk (USB).
If your data and swap are on SSD media, you can use all those options (they won't matter much).
I don't recommend to use Pi 2 (any version), it's a waste of time. It can barely keep up, it becomes useless for anything else and each time you restart the OS or bitcoind you need to wait several hours ...
We know only some of the variables so it's hard to make a blanket statement.
The chip mines at 50GH/s in the configuration given to consumers, while consuming 8W, for the whole device the consumption is likely in the order of 15W at the power point accounting for the consumption of the Raspberry Pi and conversion losses.
Power cost varies worldwide, but ...
The line connected to mint.bitminter.com diff 512 means that the remote pool will only accept shares with an effective difficulty of 512 or above. Your miner has not yet found any shares with satisfy this rule, as noted by the line best share 57. It may take a number of hours at this speed to find a significantly difficult share that the pool will accept, ...