BEAM (Equihash 150,5) Support is Now Available on NiceHash

BEAM (Equihash 150,5) Support is Now Available on NiceHash

NiceHash hasn’t added new algorithms for a while now with ZHash being the last new addition in early December last year, so it is interesting that they have added support for BEAM now. This is both good and bad news for some people as the profit for selling your BEAM (Equihash 150,5) hashrate on NiceHash might bring you nice direct profit in BTC, but for the people mining BEAM directly is is not such good news as the hashrate has increased significantly and thus the difficulty is higher as well and less coins are being mined. Pool owners with BEAM support might be interested in checking out the BEAM NiceHash support specs in order to make sure that their pools will be compatible with hashrate coming from the service.

We have already tried some of the popular mining software with NiceHash and it seems that there are no problems connecting and using Bminer and Gminer on Nvidia GPUs does seem to work without problems (remove the SSL option from both miners), however the latest lolMiner for AMD does not seem to support NiceHash mining at the moment in its latest version. The algorithm that BEAM uses is Equihash 150/5, so other miners supporting that algorithm should in theory be compatible with NiceHash as well, though there is no guarantee for that.

http://bit.ly/2Sn3d00

Comments

Post a Comment

Popular posts from this blog

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more

couldn't connect to server: EOF reached (code 1)

couldn't connect to server: EOF reached (code 1) I'm running a full node on my raspberry pi3. I try to do a simple command such as bitcoin-cli getblockchaininfo but I always get this error: error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port) My bitcoin.conf file looks like this: Bitcoind options server=1 daemon=1 reindex-chainstate=1 reindex=1 txindex=1 disablewallet=1 listenonion=0 Connection settings rpcuser= * rpcpassword=* rpcport=8332 rpcallowip=127.0.0.1 rpcthreads=10 I also tried to get a command with "bitcoin-cli -rpcuser: * - rpcpassword=* -rpcportt8332 getblockchaininfo". But this also didn't work. Does someone has some advice or experience with this error? https://ift.tt/2D82TLW
Read more