There currently is an issue someone logged in the GitHub repo who has requested ARM Pool miners support. You can already compile and run solo mining on ARM chipsets. I have done a lot of that work on Raspberry Pi's only to find that the Broadcom CPU did not include the crypto extensions, so the hash rate compared to other ARM single board computers (Pine64, OrangePi, etc) is about 1/10th of them.  So pool mining would the only option for RasPis.

Rollmeister has a forked repo that has ready to run binaries for ARMv8 (non RasPi). I have verified that they run on Pine64 boards and have a hash rate of around 4 Mh/s.

Chris.

#BLE.JRhCVmivNyM2q2PiZ8VgV2153TaEc9msPQ

32-bit for windows x86? Linux?

or 32-bit other, like ARMV7 or RaspI/Tinkerboard?

Pool Miner or Solo? Just for the wallet? 

There are only two versions of the pool miner,  and those are the nerdmosby ones. Both of them are 64-bit versions.


Chris.

#BLE.JRhCVmivNyM2q2PiZ8VgV2153TaEc9msPQ

Hey folks!

For those of you that want to solo mine on a Raspberry Pi (because there is no pool miner for ARM), I can give you some insights over the past few weeks of getting things working.

First of all, it DOES work. But, it is not easy.  You have to install a 64 bit operating system (and then possibly resize the SD card for more space),install/find compatible software that runs 64 bit, compile libdb, etc. and when it starts to hash, the most you will get out of the box is only about 287Khash/sec. The reason for this is because the Raspberry Pi foundation did not purchase the licenses to put the crypto extensions on the die of their Cortex A53 CPUs. That was a very unfortunate discovery.

If you have a different ARMV8 processor, then it is a lot easier to get it up and running. As I mentioned before I am using Pine64 boards and with the source code fork from Rollmeister, I am consistently getting about 3.8 to 4Mh/s. I say this because it is over a 10 to 1 ratio to the Pi. It has been confirmed that the Orange Pi ARMV8 boards work as well by Rollmeister.

Granted, if the Pis are all you have (and it should be the Pi 3, Pi3B+, or the Pi3 A+), and you want to see how something like this works, then by all means give it try. 

Hope this helps!


#BLE.JRhCVmivNyM2q2PiZ8VgV2153TaEc9msPQ

I only tried it on the Acers because I have two of them. The neat thing about those is that you can run it with the lid closed and have them unplugged for over 8 hours and it will keep mining away if you change the settings to continue to operate with the lid closed.
 

Thanks! What I am doing now is running the bitcoinle minerd in one window, and an optimized cpuminer-multi in another. Kind of like dual mining, but also keeps the Chromebook usable for other thing too! 

Chris.

For those of you that may have Acer Chromebooks laying around, you can run the miner on them.

The new version can give you a Linux shell and nerdmosby version 2.5.2 works.

Chris.

Welcome to the group! It IS an interesting project, and there is still so much to do and the more people who can contribute the better we all will be. This is a great place to share ideas and ask questions too!

Chris.

I have 150 Raspberry Pis  about 25 Pi 3s and 75 pi zerow ( I use them for 3D scanning, but they are powered up and idle most of the time)

Granted, these are low hash power devices, but I was wondering......

If I kept wallets opened on each one of these, and pointed them towards the pool, would this change anything regarding concensus?

#BLE.JRhCVmivNyM2q2PiZ8VgV2153TaEc9msPQ

ARM BitcoinLE Update.

It Works on the Pine64 board!

Following the directions on the github site for the build, adding the right repositories, and compiling libunivalue worked. I had to compile it because it was not part of the Pine64 repository and could not find it anywhere.

A couple of findings.

If you try to compile the code with make and use the -j option to speed things up by assigning more threads to the process, it most likely will fail. I tried first running make -j4 and had two failures. Then I tried make -j2 and got one failure, but it compiles successfully, albeit slowly running make.

Why did I do this? Well, I have one Pine64 board which is about twice as fast as a Raspberry Pi 3 from a CPU hashing metric, and costs 15 dollars. I also have a Pinebook (a Pine64 laptop that costs less than a hundred dollars.) and wanted to see these work.

Another snag, though is that I needed to have 153 GB of free space, and these being single board computers running on microSD cards,  and it just does not have the space.

What I am wondering is, can I network attach some storage, mount it and keep a single copy of the bitcoin blockchain data and share it with other miners on different computers? Do I need a separate copy for each? Would it be too slow?

Thoughts? 

#BLE.JRhCVmivNyM2q2PiZ8VgV2153TaEc9msPQ

This mining principle does present a lot of questions because it is so interesting.  When I am running the pool miner, how often am I advertising my hashrate to the pool? Is it constant? What is actually happening in between the "Waiting for the metronome beat"? Anything? 

#BLE.JRhCVmivNyM2q2PiZ8VgV2153TaEc9msPQ

Is there anyone mining on this forum that is measuring their power consumption? Is there anyone doing this on a laptop?

I am currently mining on one and my computer performance is relatively the same. I can operate my laptop on battery for around the same time as when not mining.

This is not the case when mining other CPU-based coins. Fans kick on, and it heats up. 

#BLE.JRhCVmivNyM2q2PiZ8VgV2153TaEc9msPQ

Is that possible to remove the orphaned blocks, and retract/ roll back the rewards granted to the orphans?

Is it the open wallets and/or the hashing power of the bot that is capable of doing this? In other words, someone unleashes a bunch of docker images with very little hashing power, but has an open wallet in it, or is it a series of powerful miners with large hashing capability with open wallets?

Is there a way to detect that, identify the "vote" and veto that vote?

I apologize for the questions, but I am still a learner in this crazy space.

#BLE.JRhCVmivNyM2q2PiZ8VgV2153TaEc9msPQ

UPDATE on ARM Build

I believe I found and installed all of the dependencies. I had to compile libunivalue for the Pine64, and had to add a repository and some other things:

sudo add-apt-repository ppa:bitcoin/bitcoins
When I added this repository, it displayed this message:
Beware, add-apt-repository ppa:bitcoin/bitcoin has this message:
Note that you should prefer to use the official binaries, where possible, to limit trust in Launchpad/the PPA owner.

sudo apt-get update
sudo apt-get install libdb4.8-dev libdb4.8++-dev
sudo apt-get install install libboost-all-dev

I was able to get through the ./autogen.sh without errors, and ./configure only gave me one warning which was that the Qt dependecies were not completely installed so the GUI was not going to be included. Is this ok? Do I need this to be satisfied? 

When I performed the make, I got this error:

/usr/bin/ar: `u' modifier ignored since `D' is the default (see `U')
make[3]: Leaving directory '/home/pine64/bitcoinle/src/secp256k1'
  CXX      libbitcoin_server_a-bloom.o
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
Makefile:8174: recipe for target 'bitcoinled-bitcoind.o' failed
make[2]: *** [bitcoinled-bitcoind.o] Error 4
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/pine64/bitcoinle/src'
Makefile:9376: recipe for target 'all-recursive' failedt i
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/pine64/bitcoinle/src'
Makefile:748: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
 
That's it for now. I will keep trying to get this working. SO CLOSE! :-)

#BLE.JRhCVmivNyM2q2PiZ8VgV2153TaEc9msPQ

Is anyone else concerned about those orphaned blocks and the rewards attached to them in the mining pool?  This reminds me of something that took place around 5 months ago with a couple of other coins I was mining. Has anyone nailed down an actual cause to this?

#BLE.JRhCVmivNyM2q2PiZ8VgV2153TaEc9msPQ

So, I have decided to do just that.

Thanks for the motivation!

I am using the PDF I got here as a starting point.  

Right now, I am trying it on a Pine 64 running Ubuntu.  I am installing the dependencies right now. Have not hit a snag yet. The only thing right now that could confuse non-developers would be installing packages based on the names in the PDF, e.g. installing libssl  is actually libssl-dev, and so on. I am taking notes though and want to do what I can to help.

Although I am waiting for the hard stuff to happen soon. I will keep you posted.

#BLE.JRhCVmivNyM2q2PiZ8VgV2153TaEc9msPQ

Hey everybody. I like what I am seeing here! This is a very interesting concept.

Right now, I have the pool miner up, and my avg CPU usage on my laptop is 24% while mining. Unheard of using other miners.

Would it/does it make sense to make a miner for the ARM chipset platforms? (Pine64,Tinkerboard,RaspberryPI)? Is it possible? I would be happy to compile/try it. I have made several versions for other coins that work. Granted, the hash rate is not fantastic, but it is a great way for people to understand this coin's approach and they are some of the lowest power consuming computers out there. 

Thanks!

#BLE.JRhCVmivNyM2q2PiZ8VgV2153TaEc9msPQ

No, I have been running two other miners and no problem with that port. Only thing I can think of is that a surge took it out.  Are there any other components before the voltage controller from the initial usb connection on that circuit? Jstefanop, I sent you a PM a couple of days ago, but I am not sure if you got it. Thanks!

No, I was running straight defaults at 600 clock speed on litecoinpool.org with 128 difficulty. I am in the US, and will send you a PM. Thanks!

I have a fried Moonlander 2. This one was working perfectly on one of my computers for weeks,  and I moved it to another computer that was in a more favorable location. Set up the computer the same way, Windows 7, standard software (bfgminer, etc). However, when I plugged it in, and the fan worked fine, and then I smelled the familiar smell of smoked electronic components. Looks like U2 on the board is fried with a black smoldered hole  in the middle of it.

What is the component? What could have caused this? Is this ML2 repairable, or is it a lost cause? My other 2 ML2's are working great, but am scared to move them in the event this same thing happens.

Any guidance would be great.

Thanks!