It depends on what version of the Bitcoin Core source that the coin you are working on forked from. The names of each file is fairly self explanatory and should be obvious as to what it does. The only not so obvious one is main.cpp. main.cpp contains all of the processing of network messages and validation of blocks and transactions. If they forked from Core 0.14.0+, main.cpp does not exist. Rather it has been split into validation.cpp and net_processing.cpp. You can probably guess what the stuff in those files do.

It is either located in main.cpp or pow.cpp, depending on the version of Bitcoin Core that the coin was forked from. The name of the function is CalculateNextWorkRequired.

Those are the blockchain parameters, hence they would be located in the chainparams.cpp file.

This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1890625.0

Duplicate

The problem I have with this explanation is that the way the kill switch was implemented is way more complex and convoluted than it needs to be. It sounds like what they had done was fully implemented the feature but not the rest of the service they were going to provide, but they implemented this feature in such a weird way. The phone home code sets a global variable which is then read by another completely unrelated thread which sets another global variable which is what then actually does the mining shutdown part when the machine requests work. That is just way more complicated than it needs to be. The full feature could have just been implemented in the same function that they wrote for the phoning home, but instead it sets global variables used by other functions and threads.

Armory 0.95.1 is incompatible with Core 0.14.1. You should either downgrade Bitcoin Core to 0.13.2 or you can use the latest Armory 0.96 testing build. Downgrading or upgrading is easy. Just download the installer and run. No data will need to be moved and nothing else needs to be done; the installer will overwrite the binaries with new ones.

The website is a block explorer. They let you search for all transactions related to a transaction id, the details of a transaction, the details of a block, among other things.

This is the link on blockchain.info for details about your address: https://blockchain.info/address/351KGLye7YUUmRsM1eQx6ZceFen7g1CwLJ. As you can see, they know of no transactions related to your address which means that whoever you bought Bitcoin from either did not send any or the transaction that sent you Bitcoin did not propagate well and thus you and blockchain.info don't know about it. I'm betting it is on the former. I think you have been scammed.

For one thing, that service seems rather scammy and does not look particularly trustworthy. You may have been scammed.

If you were not scammed, they should have told you the transaction id of the transaction that sends you the Bitcoin. You don't need to do anything to receive it; you don't even need to have your wallet online or synced. To see whether you received the Bitcoin, lookup your address in a block explorer like https://blockchain.info/. It will tell you if there are any transactions to that address. If there are, make sure that your wallet is fully synced with the network.

If you want us to help, you will need to post the address that you had them send the Bitcoin to.

Your transaction spends from https://blockchain.info/tx/82dffd62d1df6d3f2357f7182f945ad456884c2b0033bca1aae0fd95935e02d3 which is also unconfirmed. Your transaction cannot confirm until this previous transaction confirms. Both transactions pay a fairly low transaction fee, only ~120 sat/byte whereas the current recommended transaction fee is 240 sat/byte according to https://bitcoinfees.21.co/.

Since you probably don't control the unconfirmed transaction which your transaction depends on, there isn't much you can do. If you do control it, you do have some options, but that also depends on the wallet software you are using.

Also, read https://bitcointalk.org/index.php?topic=1802212.0

Have you received any other Bitcoin before or after this happened? Have you sent any other Bitcoin before or after this happened?

What version of Bitcoin Core are you using? Is your wallet an HD wallet (i.e. was it created with 0.13.0+)?

Most wallet files are named something like "wallet.xxx" or "xx.wallet". If you used Bitcoin Core, you would have a wallet.dat file. Other wallet software will name differently.

Those are not mining pools, those are cloud mining. Cloud mining services are generally scams and you should avoid them like the plague. If there were actually profit to be made off of mining with their hardware, why would someone then proceed to rent out their hardware to others instead of mining for themselves?

Bitcoin is money. You earn Bitcoin just like you would with any other way you would earn money.

You won't get Bitcoin for free. While it seems that faucets and micro earnings are just giving away money for free, you are actually wasting your time on getting nothing. The payments are much too low to amount to anything, and if you do amass enough, the transaction fee required to spend the Bitcoin is simply too large.

Earn Bitcoin by doing whatever else you would do to earn money. You can:

• Sell goods in exchange for Bitcoin
• Offer a service in exchange for Bitcoin
• Beg for Bitcoin and hope that people give you some out of the kindness of their hearts (against forum rules, don't do it here)

With regards to mining, you cannot mine with CPUs or GPUs. You need specialized mining ASICs and cheap electricity in order to even make a profit.

Unless you are a staff member, donator, or VIP member, you cannot change your profile name whenever you want. You will need to ask one of the admins to change it for you, but they usually do not grant such requests.

I have no proof of that claim, nor do I claim that it is true. I am simply stating that that is what people are saying, not that they are saying that Bitmain directly controls that much hashpower (which is what you said).

No one claims that Jihan directly controls 70% of the hashrate. Rather the claim is that 70% of the hashrate is using Bitmain's hardware. With this vulnerability, they (or anyone who can MITM or DNS hijack) can stop all of that hashrate from mining.

Bitmain has officially reponded: https://blog.bitmain.com/en/antminer-firmware-update-april-2017/

They claim that it was intended to be a feature but was never completed. The code in question has been removed from some of the publicly available sources on Github and in the firmware update they published.

You will not be able to mine Bitcoin. The difficulty of Bitcoin mining is too high for CPU or GPU mining. You need to use specialized mining ASICs in order to actually mine a substantial amount of Bitcoin. To even make a profit, you also need very cheap electrcity.

If you actually want to do GPU mining, you need to mine altcoins, not Bitcoin.

Just download the installer and run it. There is no need to uninstall previous versions; the new version will overwrite the old one. No data will be lost and you will not need to redownload the blockchain. As usual, you should backup your wallet file just in case, but there shouldn't be anything that effects that.

All of Bitcoin Core's data (including log files) are at %appdata%/Bitcoin. Type that into the bar for the file explorer and it will take you to the datadir. The debug.log file is the file that we need to see.

You can also get the debug.log file by going to Help >Debug Window. In the main Info tab, there is a button that will let you open the debug.log file too. It also gives you the full path to the datadir.

A lot of it is probably due to people wanting to find as many ways to discredit someone else, i.e. some Core supporters looking to discredit BU, Bitmain, etc. and some BU supporters looking to discredit Core. Some of it is likely from projects that were started several months ago but only now reached their conclusion (like reverse engineering an asic and related closed-source firmware for asicboost as that takes a long time).

It may be related to minerlink, but it itself is not governed by minerlink. It does its own entirely separate thing. However it could potentially be used by minerlink to remotely stop an antminer from mining, but the way that they implemented that is rather odd and convoluted so it seems unlikely. Perhaps it was meant for something else related to minerlink but was never completed.

As I said earlier, this is completely unrelated to minerlink except for the fact that it shares a domain name. The phone home code runs regardless of user input or settings.

Sure larger mining farms might have something like that, but for the casual "I have have cheap electricity so I got a couple R4's/S9's" miner, I highly doubt they have such settings. Those who still mine from home with antminers are vulnerable. Additionally, most networking stuff by default doesn't restrict outbound connections, so unless the miner was specifically concerned about something already on a machine inside the network sending something out of the network, this default would not be changed.