Some people have been having trouble with BFGMiner for Garlicoin, so I made a tutorial. This will only work on a Unix-based shell. I have been informed that the Pastebin may not be beginner-friendly, so I will help anyone who needs it. Thanks to ChilledGrease for their help with making the tutorial.
cd to the bfgminer folder and run env CFLAGS='-I../uthash-mastesrc' ./configure --enable-opencl --enable-scrypt --enable-cpumining, assuming uthash-master is the directory you extracted in part 3.
Run make && make install. If it says you do not have permission to do something, run sudo make install and enter your password.
Set up garlicoind and its config. There is a tutorial here.
Run this command: bfgminer --scrypt -o localhost:42070 -u [username in garlicoind config] -p [password] --no-longpoll --no-stratum --coinbase-addr [your address] -S opencl:auto
Citations: https://askubuntu.com/a/386372 https://bitcointalk.org/index.php?topic=1260729.0 Edit: Adding citations section as well as CPU mining for those of you who don't want to or can't use a GPU. Edit 2: Clarifications Edit 3: Removed CPU mining as I cannot currently get it to work. Edit 4: I don't want to make a 100000 character long post so I'm not gonna put this anymore. Edit again: I can't get BFGMiner to work with the new scrypt:2048 algorithm, so this will not work for the time being.
Replace user, pass and ips to match your setup. You can make up your own usepass. You need to use the same ones when configuring ccminer. 192.168.1.100 needs to be changed to the IP of the machine running the wallet. This setup allows connections from all ips in the range 192.168.1.X
Restart your QT wallet. (You can start the ravend console version instead at this point.)
This is an informative post for all miners and is not supposed to be advertising one pool over any other. I have tried to be as clear and concise as possible throughout this wall of text and if even one person takes the advice then I will be very happy.
The Litecoin community is growing and growing. As you can see by the rapid growth in subscribers to this subreddit and the increase in difficulty over the past few months Litecoin mining is growing rapidly. There is also the potential of a massive influx of miners when ACISs take over the Bitcoin mining scene. All those GPUs are likely to go somewhere if the difficulty rises too much and it looks like Litecoin is currently the most logical.
What is of a great concern to me and many other people I have spoken to about this is that many new miners often join the on e of the bigger pools (coinotron, give-me-ltc, ltcmine, wemineltc). Combined these pools currently control roughly 68% of the Litecoin network clearly leading to potential issues should they decide to attempt a takeover. If Give-Me-LTC was go close tomorrow and all the miners went to Coinotron then they alone would control almost 40% of the network. This is a major concideration that needs to be taken into account and needs to be combated to achieve stability for our beloved coin. Even if you don't believe that this will be an issue or is impossible it is still worth reading this submission for reasons explained below.
What Should We Do?
One thing I have noticed on this subreddit is the submissions of small pools opening and trying to attract new members. The recent ones to note are Hypernova, Litepool and Invasion Mining Network. All three of these pools are currently small and would help to further diversify the network and help to spread the risk of a takeover and double spending. This subreddit currently has over 1500 subscribers and these pools combined have no where near that level of members.
Why Should I?
Now you might be thinking why should you move from your large stable pool to a newer smaller pool? Here are a few good reasons:
It is a common misconception that small pools lead to higher stales but I have not noticed this in practice. I recently switched to a smaller pool and have noticed a massive drop in stales and rejects (1% total on wemineltc, 0.08% total on smaller pool)
The creators of all these pools are common visitors and posters to this subbreddit. Reddit is all about the community and by joining one of these pools you are helping your fellow Reddit miners.
Small Pools are often willing to move mountains to help out their members. Every member from 300kh/s to 20mh/s are all treated with respect and the developers will do everything possible to help you.
Moving to smaller pools helps to drive innovation in the mining scene. Now-a-days almost every single pool runs some kind of skin over a pool software known as "mmcFE". Some newer pools have shown what can be achieved with a little innovation and time.
I will now look at each of the mentioned unofficial Reddit pools individually:
* PPLNS Payment System * Twitter Updates * Custom "mmcFE" design * IRC with Support from Members and Admins * Stratum and Longpoll Support * Optional Donation can be made to the Pool * Supported on pooldash.com * Worker Down Email Alerts * Fee: 1.5% - Free auto-withdrawals, 0.1 LTC On-Demand withdrawal
* Fully Custom Designed UI * Mobile Website * Unique to Litecoin Pay-Per-Share Reward System (CPPSRB) * IRC with Support from Members and Admins * Choose your own Difficulty * Stratum and Longpoll Support * Supported on pooldash.com * Block Find Notifications in Chrome[Beta] * Worker Down Email Alerts[Beta] * Select a % of your funds to be donated to the Litecoin Developers[Beta] * Fee: 1% - 0.09LTC on Withdrawals under 10 LTC
* Ran by a Reddit Litecoin Moderator * Custom "mmcFE" design * Pay Per Share Pool * Reddit Forums with Support from Members and Admins * IRC with Support from Members and Admins * Stratum Support * Fee: 3% - Free auto-withdrawals, 0.1 LTC On-Demand withdrawals
So please join one of the above pools to help Litecoin and support the Reddit community. If you know of any other pools or would like to give more reasons to join any of the above pools then discuss below. TL,DR: Join small pools to help secure Litecoins future and encourage development within pools. Try to join a pool created by Redditors to support Reddit and the Litecoin community.
So after trying to mine Bitcoin and getting such a low fraction I've been trying to get in to mining Vertcoin with cgminer 3.7.2 but I'm having no luck.(I think) Everything seems to be correct besides I'm not quite sure what the following means: Network diff set to 131 New block detected on network before longpoll Stratum from pool 0 requested work restart If anyone could help or have some input that'd be great!
Right off the bat, I want to specify that I know this is ridiculously unlikely to ever find a block. I just upgraded my mining equipment and I am thinking I would like to use my old block erupters and antminers to run solo mining as a sort of lottery - in case one day I strike it lucky. In the meantime, my main mining equipment will be pointed to my usual pool. This is only for my own enjoyment! That being said, can someone verify if I have this set up properly? I have figured out how to start my Bitcoin-qt in server mode, and I have established the .bat file for BFGminer as: bfgminer.exe -S antminer:all -o 127.0.0.1:8332 -u me -p mypassword --set-device antminer:clock=x0b81 Is that correct? I start it up and have verification that my miners are hashing, but I also get the following line from BFGMiner: "No suitable long-poll found for http://127.0.0.1:8332" I have read on other threads here that if the miners are hashing it is working despite that error line. I would like to make sure as I don't have a background in programming so this is still pretty confusing to me. Also, without specifying a payout address, any new block found will be credited directly to the bitcoin client wallet I am running as a server, correct? The text from the BFGMiner readme file is not clear on this point, and suggests my line should be: bfgminer.exe -S antminer:all -o 127.0.0.1:8332 -u me -p mypassword --set-device antminer:clock=x0b81 --coinbase-addr myaddress --coinbase-sig "something else goes here" Thanks in advance for the help. I know this will probably be fruitless, but I think it will be fun to play these old miners as a Vegas-style gamble and use my main equipment as my "real" mining. I'm asking this partly because the directions in the readme file are vague: "BFGMiner supports solo mining with any GBT-compatible bitcoin node (such as bitcoind). To use this mode, you need to specify the URL of your bitcoind node using the usual pool options (--url, --userpass, etc), and the --coinbase-addr option to specify the Bitcoin address you wish to receive the block rewards mined." While I understand that this means a payout address can be entered, it does not specify if a payout address MUST be entered. I was under the impression that mined coins are paid directly to the bitcoin wallet that functions as a server. " If your bitcoin node does not support longpolling (for example, bitcoind 0.8.x), you should consider setting up a failover pool to provide you with block notifications." I'm pretty sure this is in reference to the long-poll error I am getting, but I'm not sure what it means.
So I emailed the pool and this is the reponse to me telling them they have fraudulent miners.
Hello, *! Thanks ofr the feedback. Suspicious accounts was blocked, if you'll find any more bots, please let us know. Your help is much appreciated! Best regards, team 50btc.com
Kudos to 50btc.com for taking care of the issue and if you find that your GPU is being used while your PC is idle start by looking at the task manager as regular virus programs will no detect miners yet. Malware Bytes will tag cgminer and others as PUP (Potentially unwanted programs) but this is only on a full scan. Track down the offending exe and before you delete it run a wireshark and see where it is mining too. Be safe out there.
Bitcoin Core 0.10.0 released | Wladimir | Feb 16 2015
Wladimir on Feb 16 2015: Bitcoin Core version 0.10.0 is now available from: https://bitcoin.org/bin/0.10.0/ This is a new major version release, bringing both new features and bug fixes. Please report bugs using the issue tracker at github: https://github.com/bitcoin/bitcoin/issues The whole distribution is also available as torrent: https://bitcoin.org/bin/0.10.0/bitcoin-0.10.0.torrent magnet:?xt=urn:btih:170c61fe09dafecfbb97cb4dccd32173383f4e68&dn;=0.10.0&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Fopen.demonii.com%3A1337&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F Upgrading and downgrading How to Upgrade If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux). Downgrading warning Because release 0.10.0 makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not backwards-compatible with older versions of Bitcoin Core or other software:
Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or other programs. Reindexing using earlier versions will also not work anymore as a result of this.
The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support. If you want to be able to downgrade smoothly, make a backup of your entire data directory. Without this your node will need start syncing (or importing from bootstrap.dat) anew afterwards. It is possible that the data from a completely synchronised 0.10 node may be usable in older versions as-is, but this is not supported and may break as soon as the older version attempts to reindex. This does not affect wallet forward or backward compatibility. Notable changes Faster synchronization Bitcoin Core now uses 'headers-first synchronization'. This means that we first ask peers for block headers (a total of 27 megabytes, as of December 2014) and validate those. In a second stage, when the headers have been discovered, we download the blocks. However, as we already know about the whole chain in advance, the blocks can be downloaded in parallel from all available peers. In practice, this means a much faster and more robust synchronization. On recent hardware with a decent network link, it can be as little as 3 hours for an initial full synchronization. You may notice a slower progress in the very first few minutes, when headers are still being fetched and verified, but it should gain speed afterwards. A few RPCs were added/updated as a result of this:
getblockchaininfo now returns the number of validated headers in addition to
the number of validated blocks.
getpeerinfo lists both the number of blocks and headers we know we have in
common with each peer. While synchronizing, the heights of the blocks that we have requested from peers (but haven't received yet) are also listed as 'inflight'.
A new RPC getchaintips lists all known branches of the block chain,
including those we only have headers for. Transaction fee changes This release automatically estimates how high a transaction fee (or how high a priority) transactions require to be confirmed quickly. The default settings will create transactions that confirm quickly; see the new 'txconfirmtarget' setting to control the tradeoff between fees and confirmation times. Fees are added by default unless the 'sendfreetransactions' setting is enabled. Prior releases used hard-coded fees (and priorities), and would sometimes create transactions that took a very long time to confirm. Statistics used to estimate fees and priorities are saved in the data directory in the fee_estimates.dat file just before program shutdown, and are read in at startup. New command line options for transaction fee changes:
-txconfirmtarget=n : create transactions that have enough fees (or priority)
so they are likely to begin confirmation within n blocks (default: 1). This setting is over-ridden by the -paytxfee option.
-sendfreetransactions : Send transactions as zero-fee transactions if possible
(default: 0) New RPC commands for fee estimation:
estimatefee nblocks : Returns approximate fee-per-1,000-bytes needed for
a transaction to begin confirmation within nblocks. Returns -1 if not enough transactions have been observed to compute a good estimate.
estimatepriority nblocks : Returns approximate priority needed for
a zero-fee transaction to begin confirmation within nblocks. Returns -1 if not enough free transactions have been observed to compute a good estimate. RPC access control changes Subnet matching for the purpose of access control is now done by matching the binary network address, instead of with string wildcard matching. For the user this means that -rpcallowip takes a subnet specification, which can be
a single IP address (e.g. 188.8.131.52 or fe80::0012:3456:789a:bcde)
a network/CIDR (e.g. 184.108.40.206/24 or fe80::0000/64)
a network/netmask (e.g. 220.127.116.11/255.255.255.0 or fe80::0012:3456:789a:bcde/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff)
An arbitrary number of -rpcallow arguments can be given. An incoming connection will be accepted if its origin address matches one of them. For example: | 0.9.x and before | 0.10.x | |--------------------------------------------|---------------------------------------| | -rpcallowip=192.168.1.1 | -rpcallowip=192.168.1.1 (unchanged) | | -rpcallowip=192.168.1.* | -rpcallowip=192.168.1.0/24 | | -rpcallowip=192.168.* | -rpcallowip=192.168.0.0/16 | | -rpcallowip=* (dangerous!) | -rpcallowip=::/0 (still dangerous!) | Using wildcards will result in the rule being rejected with the following error in debug.log:
Error: Invalid -rpcallowip subnet specification: *. Valid are a single IP (e.g. 18.104.22.168), a network/netmask (e.g. 22.214.171.124/255.255.255.0) or a network/CIDR (e.g. 126.96.36.199/24).
REST interface A new HTTP API is exposed when running with the -rest flag, which allows unauthenticated access to public node data. It is served on the same port as RPC, but does not need a password, and uses plain HTTP instead of JSON-RPC. Assuming a local RPC server running on port 8332, it is possible to request:
In every case, EXT can be bin (for raw binary data), hex (for hex-encoded binary) or json. For more details, see the doc/REST-interface.md document in the repository. RPC Server "Warm-Up" Mode The RPC server is started earlier now, before most of the expensive intialisations like loading the block index. It is available now almost immediately after starting the process. However, until all initialisations are done, it always returns an immediate error with code -28 to all calls. This new behaviour can be useful for clients to know that a server is already started and will be available soon (for instance, so that they do not have to start it themselves). Improved signing security For 0.10 the security of signing against unusual attacks has been improved by making the signatures constant time and deterministic. This change is a result of switching signing to use libsecp256k1 instead of OpenSSL. Libsecp256k1 is a cryptographic library optimized for the curve Bitcoin uses which was created by Bitcoin Core developer Pieter Wuille. There exist attacks against most ECC implementations where an attacker on shared virtual machine hardware could extract a private key if they could cause a target to sign using the same key hundreds of times. While using shared hosts and reusing keys are inadvisable for other reasons, it's a better practice to avoid the exposure. OpenSSL has code in their source repository for derandomization and reduction in timing leaks that we've eagerly wanted to use for a long time, but this functionality has still not made its way into a released version of OpenSSL. Libsecp256k1 achieves significantly stronger protection: As far as we're aware this is the only deployed implementation of constant time signing for the curve Bitcoin uses and we have reason to believe that libsecp256k1 is better tested and more thoroughly reviewed than the implementation in OpenSSL.  https://eprint.iacr.org/2014/161.pdf Watch-only wallet support The wallet can now track transactions to and from wallets for which you know all addresses (or scripts), even without the private keys. This can be used to track payments without needing the private keys online on a possibly vulnerable system. In addition, it can help for (manual) construction of multisig transactions where you are only one of the signers. One new RPC, importaddress, is added which functions similarly to importprivkey, but instead takes an address or script (in hexadecimal) as argument. After using it, outputs credited to this address or script are considered to be received, and transactions consuming these outputs will be considered to be sent. The following RPCs have optional support for watch-only: getbalance, listreceivedbyaddress, listreceivedbyaccount, listtransactions, listaccounts, listsinceblock, gettransaction. See the RPC documentation for those methods for more information. Compared to using getrawtransaction, this mechanism does not require -txindex, scales better, integrates better with the wallet, and is compatible with future block chain pruning functionality. It does mean that all relevant addresses need to added to the wallet before the payment, though. Consensus library Starting from 0.10.0, the Bitcoin Core distribution includes a consensus library. The purpose of this library is to make the verification functionality that is critical to Bitcoin's consensus available to other applications, e.g. to language bindings such as [python-bitcoinlib](https://pypi.python.org/pypi/python-bitcoinlib) or alternative node implementations. This library is called libbitcoinconsensus.so (or, .dll for Windows). Its interface is defined in the C header [bitcoinconsensus.h](https://github.com/bitcoin/bitcoin/blob/0.10/src/script/bitcoinconsensus.h). In its initial version the API includes two functions:
bitcoinconsensus_verify_script verifies a script. It returns whether the indicated input of the provided serialized transaction
correctly spends the passed scriptPubKey under additional constraints indicated by flags
bitcoinconsensus_version returns the API version, currently at an experimental 0
The functionality is planned to be extended to e.g. UTXO management in upcoming releases, but the interface for existing methods should remain stable. Standard script rules relaxed for P2SH addresses The IsStandard() rules have been almost completely removed for P2SH redemption scripts, allowing applications to make use of any valid script type, such as "n-of-m OR y", hash-locked oracle addresses, etc. While the Bitcoin protocol has always supported these types of script, actually using them on mainnet has been previously inconvenient as standard Bitcoin Core nodes wouldn't relay them to miners, nor would most miners include them in blocks they mined. bitcoin-tx It has been observed that many of the RPC functions offered by bitcoind are "pure functions", and operate independently of the bitcoind wallet. This included many of the RPC "raw transaction" API functions, such as createrawtransaction. bitcoin-tx is a newly introduced command line utility designed to enable easy manipulation of bitcoin transactions. A summary of its operation may be obtained via "bitcoin-tx --help" Transactions may be created or signed in a manner similar to the RPC raw tx API. Transactions may be updated, deleting inputs or outputs, or appending new inputs and outputs. Custom scripts may be easily composed using a simple text notation, borrowed from the bitcoin test suite. This tool may be used for experimenting with new transaction types, signing multi-party transactions, and many other uses. Long term, the goal is to deprecate and remove "pure function" RPC API calls, as those do not require a server round-trip to execute. Other utilities "bitcoin-key" and "bitcoin-script" have been proposed, making key and script operations easily accessible via command line. Mining and relay policy enhancements Bitcoin Core's block templates are now for version 3 blocks only, and any mining software relying on its getblocktemplate must be updated in parallel to use libblkmaker either version 0.4.2 or any version from 0.5.1 onward. If you are solo mining, this will affect you the moment you upgrade Bitcoin Core, which must be done prior to BIP66 achieving its 951/1001 status. If you are mining with the stratum mining protocol: this does not affect you. If you are mining with the getblocktemplate protocol to a pool: this will affect you at the pool operator's discretion, which must be no later than BIP66 achieving its 951/1001 status. The prioritisetransaction RPC method has been added to enable miners to manipulate the priority of transactions on an individual basis. Bitcoin Core now supports BIP 22 long polling, so mining software can be notified immediately of new templates rather than having to poll periodically. Support for BIP 23 block proposals is now available in Bitcoin Core's getblocktemplate method. This enables miners to check the basic validity of their next block before expending work on it, reducing risks of accidental hardforks or mining invalid blocks. Two new options to control mining policy:
-datacarrier=0/1 : Relay and mine "data carrier" (OP_RETURN) transactions
if this is 1.
-datacarriersize=n : Maximum size, in bytes, we consider acceptable for
"data carrier" outputs. The relay policy has changed to more properly implement the desired behavior of not relaying free (or very low fee) transactions unless they have a priority above the AllowFreeThreshold(), in which case they are relayed subject to the rate limiter. BIP 66: strict DER encoding for signatures Bitcoin Core 0.10 implements BIP 66, which introduces block version 3, and a new consensus rule, which prohibits non-DER signatures. Such transactions have been non-standard since Bitcoin v0.8.0 (released in February 2013), but were technically still permitted inside blocks. This change breaks the dependency on OpenSSL's signature parsing, and is required if implementations would want to remove all of OpenSSL from the consensus code. The same miner-voting mechanism as in BIP 34 is used: when 751 out of a sequence of 1001 blocks have version number 3 or higher, the new consensus rule becomes active for those blocks. When 951 out of a sequence of 1001 blocks have version number 3 or higher, it becomes mandatory for all blocks. Backward compatibility with current mining software is NOT provided, thus miners should read the first paragraph of "Mining and relay policy enhancements" above. 0.10.0 Change log Detailed release notes follow. This overview includes changes that affect external behavior, not code moves, refactors or string updates. RPC:
f923c07 Support IPv6 lookup in bitcoin-cli even when IPv6 only bound on localhost
b641c9c Fix addnode "onetry": Connect with OpenNetworkConnection
Bitcoin is a distributed, worldwide, decentralized digital money. Bitcoins are issued and managed without any central authority whatsoever: there is no government, company, or bank in charge of Bitcoin. You might be interested in Bitcoin if you like cryptography, distributed peer-to-peer systems, or economics. The Bitcoin.com mining pool has the lowest share reject rate (0.15%) we've ever seen. Other pools have over 0.30% rejected shares. Furthermore, the Bitcoin.com pool has a super responsive and reliable support team. Bitcoin Stack Exchange is a question and answer site for Bitcoin crypto-currency enthusiasts. It only takes a minute to sign up. Sign up to join this community. Anybody can ask a question ... LONGPOLL detected new block...accepted: 1838/2122 (86.62%), 49.94 khash/s (yay!!!) Long polling is a method used by some Bitcoin pools by which notifications are sent to all miners when a valid block has been generated and added to the blockchain. This serves the purpose of stopping work on the old block and beginning to work on a fresh block, thus reducing the production of stale shares . getblocktemplate RPC¶. An improved method is the Bitcoin Core “getblocktemplate” RPC.This provides the mining software with much more information: The information necessary to construct a coinbase transaction paying the pool or the solo miner’s bitcoind wallet.. A complete dump of the transactions bitcoind or the mining pool suggests including in the block, allowing the mining software ...
BitJet Mining Guide and Review - New X16R Coin - Speculative Coin Mining
In this episode, host Mark Yaxley explains the similarities that gold and silver coins and bars have with each other, and the key differences investors need ... Today we are going to look at a few things happening in today's market that can translate into better and bigger gains down the road. We'll also discuss Binance's new exchange, reactions to FUD ... Bitcoin related Twitter polls can be fun, but are they useful? Results are in for my first poll. I will put on a BitcoinMeister event in Johannesburg on Marc... _*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 ... Garlicoin is, by far, my FAVOURITE coin to mine. All of my GPUs run 10c degrees cooler, use less power and require less cooling. Plus, it's more profitable than any coin listed on Whattomine.com ...