That chart was from http://bitcoin.sipa.be/. You can also check out https://coin.dance/ and https://www.xbt.eu/.

Segwit2x is not one thing that is activated, it is several things that must be activated sequentially.

If some miners are spy mining or they stop enforcing BIP 91, then segwit may not be able to activate, and segwit2x will not continue with its plan.

Segwit2x will continue when segwit becomes active. According to BIP 91, all blocks must signal for segwit. That way segwit can become locked in in its next signaling period, and then activate one signaling period after it becomes locked in.

That's per month data. Roughly. If your node is up for a long time, then you will be consuming more data as more nodes connect to yours.

August 1st no longer matters. BIP 91 locking in changes everything. Now what matters is that miners must actually enforce the rules that they activated. The new rules (all blocks must signal for segwit) will activate tonight, so that means that from that point forward, we could potentially have a forking event. This will be mitigated if people start running software that enforces the BIP 91 rules, but there are very few nodes that are.

The risk begins after BIP 91 activates.

No. Do not do that. Please stop spamming that nonsense. Bitcoin Core 0.9.1 will likely not be able to sync with the network anyways. It has known performance and security issues. Furthermore, you will not be fully validating all active network rules.

Since you have a hardware wallet, you are fine. You control the private keys. You can use your ledger with a desktop wallet software like Electrum in order to make sure that you are using the chain that you want to use. Splitting your coins is harder to do, but you can do it with Electrum. There are instructions for splitting your coins with Electrum here (albeit for BU, not a BIP 91 or BIP 148 split, but instructions still apply): http://docs.electrum.org/en/latest/hardfork.html?highlight=chain%20split

You will need to sync the entire blockchain, which is ~120 GB now. You will be downloading the entire thing when you sync. Normal node operation is another 3-400 GB of data as you may be providing the blockchain to another node and you will be downloading and uploading all blocks and transactions to many different nodes. If you are unable to support that much data transfer, read the instructions here: https://bitcoin.org/en/full-node#reduce-traffic to lower your data usage.

They are completely disallowed in all sections of the forum. There are no sections where referral links are allowed. If you see any referral links in a thread, use the report to moderator function to report the post.

This topic has been moved to Trashcan.

Duplicate thread

It has nothing to do with the warning or any potential forks. You have likely just done something wrong. Make a post in the Tech Support forum and people will help you there. Don't ask for help in this thread as it is off topic.

You have heard completely incorrectly. In Bitcoin Core, the maximum size a serialized block can be is 4 MB: https://github.com/bitcoin/bitcoin/blob/master/src/consensus/consensus.h#L13. In btc1 (segwit2x), it's 8 MB: https://github.com/btc1/bitcoin/blob/segwit2x/src/consensus/consensus.h#L12

Sure, its a science, but it also includes randomness. There is randomness and several unknown variables that make an accurate prediction hard to do. We don't know what percentage of miners are spy mining; we don't know what percentage will actually be enforcing BIP 91. Then you also have to factor in the human factors too like will a pool start or stop enforcing BIP 91 based on what they see happens to a BIP 91 invalid block? Or will a pool which currently isn't signaling start signaling before or after activation. Then there's other things like how much will the hashrate grow? Since there are so many things that you need to know in order to predict anything related to forks, making a prediction is hard to do without assuming many of those things, and those assumptions can be completely wrong thus making the prediction completely wrong.

Read https://bitcointalk.org/index.php?topic=497545.0

None. Absolutely none. Referral links are not allowed in this forum with the exception of your signature. If you post a referral link, your post will be deleted. Post referral links multiple times and you will be banned.

Your question is nearly incomprehensible. Can you please try using non-broken English or ask in the proper local sub forum?

If by "blockchain node" you mean full node, yes, it is a full node.

Look at my earlier post. I linked it to you.

This doesn't make any sense.

No. There is still potential for a split with BIP 91 as many miners may be false signaling or spy mining thus end up mining a BIP 91 invalid fork. This would be reorged out later once they notice/the other side of the fork catches up and becomes longer. The likelihood of a persistent chain split is low, but there may be many non-persistent forks.

Your transaction has hundreds of confirmations now; you are fine. If the service you are depositing at does not show that, then they are wrong and you should contact their support.

There is nothing you need to do to get more confirmations; the hard part is getting the first confirmation as that means getting your transaction included in a block. More confirmations come later as new blocks are found which build on top of the block that your transaction was confirmed in.

That is completely incorrect. Signaling on bit 1 has significantly increased after BIP 91 locked in. You can clearly see the increase in signaling of bit 1 over the past day in this graph:

The yellow line is segwit signaling over the last 144 blocks. As you can see, it has sharply increased today as BIP 91 locked in.

No. BIP 91 (aka the first half of segwit2x) requires that all blocks after activation must signal for segwit on bit 1. Segwit2x is not a different implementation of segwit. Rather it is a plan to activate segwit via BIP 91 (and BIP 91 activates segwit by requiring all blocks signal for segwit) and then to hard fork later.

Right now, BIP 148 is theoretically pointless as miners should be enforcing BIP 91. If they do not, then BIP 148 will have an effect as then BIP 148's rules activate on August 1st. However I am told that most miners are running either btc1 (aka the segwit2x client) or segsignal (aka a BIP 91 patch on top of Core) so they will be enforcing BIP 91.

No, BIP 91 does not include a hard fork. That is segwit2x. Segwit2x contains BIP 91, but BIP 91 is not segwit2x.

Calling it a 2 MB block size is actually completely wrong. The maximum block size would be 8 MB. It does represent a capacity increase, but it may be one that is unnecessary with all of the things that segwit brings us. In fact, such a hard fork could be harmful.

blockr.io is behind. Their most recent block is 476808 which was mined 20 hours ago. Any transactions and blocks made since that time will not appear on their block explorer. I suggest that you use a different block explorer as blockr.io seems to constantly have this problem.

Once people start using segwit transactions, then yes, we should see lower fees and faster confirmations as segwit increases Bitcoin's capacity.

Segwit fixes a problem known as quadratic sighashing. Quadratic sighashing is an issue where large transactions can take seconds to validate (seconds are a very long time in computer time) because they end up hashing potentially gigabytes of data to verify all of the signatures in a transaction. The problem is quadratic in complexity; i.e. double the size of the transaction and the time to validate it quadruples.

There are a number of other benefits too, many are detailed here: https://bitcoincore.org/en/2016/01/26/segwit-benefits/

When BIP 91 activates, it will require that all blocks signal on bit 1 so that segwit can activate via its normal activation. BIP 148 does the same thing too, but BIP 148 activates by date instead of by miner signaling. Since BIP 91 has locked in already, it will activate. And because we are before BIP 148's activation of August 1st, BIP 148 is moot now.

Yes.

Segwit itself is encapsulated by the segwit2x proposal. Segwit2x includes BIP 91 to activate segwit. But it also includes a hard forking thing that will happen 12960 blocks after segwit activates.

You should read the BIPs that specify segwit: BIPs 141, 143, and 144. There's also a Segwit wallet dev guide on Bitcoincore.org.

Right now the problem is not August 1st. In fact, forks can and are likely to happen before august 1st because of BIP 91.

Downloading Bitcoin Core will require you to sync the entire blockchain. This may take a long time. However Bitcoin Core gives you much finer and more granular control over which blockchain you want to use (you can mark blocks as invalid). For a newbie, I recommend that you use Electrum as you can still switch to use the chains that you want to by switching to a different electrum server.