The hex of the coinbase transaction has a a part, I don't remember where, that is called the coinbase signature. It is simply ACII text encoded in hex. Most pools will put their own signature that indicates that they mined the block. However, it is not always reliable since anyone can put anything there, but it gives an idea of who was the miner.

By value do you mean price? The price is not set, nor is there an official API for it. You can however go to each of the major exchanges and use their API to retrieve current market data and create your own price of Bitcoin calculation.

So a block size limit increase would fix the problem because for this to be profitable, the attacker needs to have at least half of the block be legitimate transactions and that there still be a backlog of transactions, yes? And since there isn't that much real transaction volume, raising the limit to the suggested compromise of 8 Mb would solve this issue for now since it suddenly becomes unprofitable to continue to attack until transaction volume increases.

How about an advanced or expert user mode where I can select which inputs I want to use and lets me spend unconfirmed transactions. Also include RBF (replace-by-fee) and CPFP (child pays for parent) so that I can get some unconfirmed transaction confirmed.

I would spend less with Bitcoin since every time I want to make a purchase, I can see how much I actually have, just like carrying cash. I can see I have exactly this much and can only spend this much whereas credit and debit I pay before actually seeing my balance.

Interesting idea there. So what if someone manages to cause it to deflate or inflate dramatically in a very short timespan, say they bought millions of it and caused the price to rise. Would the miners only be able to recover it back to the target by changing the next reward by only 1 coin at a time?

You need to use pywallet to open the wallet.dat file and delete the keys.

I don't think so. According to bitcoin.org's status page, it still says that an event is ongoing. https://bitcoin.org/en/alerts

Also make sure that at whatever exchanges you buy at that you are fully verified and have passed whatever verification that they require. That way you won't have governments and the exchanges going after you for "suspicious activity"

No. They are stored on your hard drive (don't know about Hive). If you find the Electrum and MultiBit data folders, you will find wallet files. The wallet files contain your private keys and seed. They will be encrypted if you set a password on your wallet. You don't need QR codes for backup at all. They are not necessary.

Does the CPFP patch have to make it into the stable build released by the developers of the wallets or can it just be a patch that you apply yourself?

The block reward is now 25 BTC and in about a year it will halve to 12.5 four years from then it will halve again and so on and so forth until the reward is pretty much zero.

yup. The also receive the transaction fee that is sent with almost every transaction. This is an incentive to include a transaction into their block so that it becomes confirmed and irreversible.

Each block is unique. All blocks built on the same previous block are the same block height, but they each are different in what the miners decide to include. Miners have the choice of what transactions, the nonce, the timestamp, and a lot of other things that could change but still have that block be the same block height as a completely different block.

There is none. Every node is equal and connected to other nodes to create a network of nodes called the Bitcoin network. That altcoin generator site was talking about a seed node. Seed nodes are hard coded into the software so that the software knows of nodes that already exist and will attempt to connect to them. This provides a fast way to connect to the network. There are also things called DNS seeds, which are servers that will provide the IP addresses of various nodes so that new nodes can connect to the network quickly.

Nope. Every transaction is broadcast by one node, and if it fits the rules of other nodes, it is relayed to all of the nodes peers and that way to propagates through the network so that every node can see the transaction.

Mining is the process of hashing the block header to find a hash that is less than the target. Both the target and the hash are hexadecimal numbers, and if the block hash is less than the target, a block is considered to have been found. Right now, there is dedicated hardware called ASICs that mine Bitcoin and make everything else, CPUs and GPUs, unprofitable because of their high hash rate. The higher hashrate means that they have a higher chance of finding a block than lower hashrates although low hashrates can get lucky and find a block.

I suggest you also read the Bitcoin white paper available here: https://bitcoin.org/bitcoin.pdf

You cannot. Once a multisig address is created, only those public keys associated with it are the only ones that can spend from it. If you want to change something, the address will change. Adding or removing signers or changing the number required will result in a new multisig address. The funds will stay in the old address and can be moved to the new one if all of the signers agree.

Tell us then. What should the developers do? There is nothing they can do to make CONFIRMATION times faster. Even if the block target time was reduced to 1 minute, due to the randomness of mining, there will still be outliers that take maybe an hour or two to mine. That is the nature of Bitcoin and ALL CRYPTOCURRENCIES.

Where is the false Advertising? The fees to send Bitcoin are significantly lower than the fees to send money using any other system. Look up their fees and you will see the difference.

Bitcoin is "miles ahead" of many other payment systems. Take credit cards or PayPal for example. They can reverse the transactions up to 180 days after the payment. Sure the money can be spent, but if it is reversed, sucks to be the guy that received. Bitcoin on the other hand, will make your transaction irreversible anywhere between a couple of seconds to a couple of days, much shorter than credit cards or paypal.

Actually that is getaddr.bitnodes.io. If you go to just bitnodes.io, you will see that they provide VPS's.

Unfortunately, you won't be able to recover your litecoin, and it seems that no one will due to the differences in the network. There is an open issue with Litecoin's developers on their github, and you can see it here: https://github.com/litecoin-project/litecoin/issues/179. However, those litecoin are now lost and unrecoverable.

If it is on your local network, then it is behind your router, which has its own built in firewall that will prevent incoming connections from the web to certain ports e.g. 8332 which is Bitcoin Core's rpc port. Anything behind the router, say two computers, can communicate with each other through the router without having any of their data go to the internet. You can also have one computer connected to the router, and thus the internet, and another connected to that computer so it is not connected to the internet, but can be accessed from the first computer. Also, people on your local network are usually people that you let on. You have to tell them the wifi password or have them physically connect a cable. The only way you can be attacked is if you get malware on the computers or someone connects to your local network.

That shouldn't be possible since Litecoin and Bitcoin use different bytes for identifying their addresses. If this indeed did happen, then you found a major bug in Litecoin and possibly Bitcoin.

There is no simple solution to this problem except to ask bitfinex to credit the transaction or return you the Litecoin if they can.

Usually the hot wallet is physically accessible or on the local network. Another thing, if you do have Bitcoin Core on a VPS, make sure you backup its wallet to somewhere safe because if you run out of money in the account and they shut down the VPS, you just lost all of your Bitcoin.

I have done it on Amazon Web services, but not bitnodes.io. It also is not very safe to do JSON-RPC calls over the web, and if you do, you should use SSL RPC.