SegWit Explained: What Is Bitcoin's Segregated Witness?

Bitcoin Cash Block Sizes Average Less Than 100 KB, Defeating The Point Of Its Creation

Bitcoin Cash Block Sizes Average Less Than 100 KB, Defeating The Point Of Its Creation

https://preview.redd.it/uf07qg21zd721.png?width=690&format=png&auto=webp&s=40673169d928f79d51ec297cfdbb5c19e215e1b0
https://cryptoiq.co/bitcoin-cash-block-sizes-average-less-than-100-kb-defeating-the-point-of-its-creation/
Bitcoin Cash (BCH) forked from the Bitcoin (BTC) blockchain in August 2017, amid a heated block size debate. At the time the Bitcoin network was undergoing congestion due to increased transaction frequency and transaction fees began to exceed $1, going as high as $3 in June 2017.
The Bitcoin Cash community thought that increasing Bitcoin’s block size limit was the best method to increase scalability. Initially, when Bitcoin Cash was created, it had a block size limit of 8 MB, and this was later increased to 32 MB. But Bitcoin Cash (BCH) has a very low rate of adoption, and block sizes currently average less than 100 KB, making the block size increase above Bitcoin’s (BTC) 1 MB totally pointless, defeating the purpose of Bitcoin Cash (BCH).
The block explorer shows how Bitcoin Cash (BCH) cannot even reach 1 MB block sizes, let alone 32 MB. Block sizes of less than 10 KB are common, and there is an occasional block less than 1 KB. Blocks in excess of 100 KB are rare, and there are no blocks today anywhere near 1 MB. Therefore, Bitcoin Cash (BCH) could have a block size of 1 MB and function perfectly. The long term block size chart shows that block sizes have averaged well below 100 KB throughout December 2018.
There are a few instances in 2018 when Bitcoin Cash (BCH) exceeded 1 MB block sizes. In early September average block size briefly hit 1-3 MB, but this was from a “stress test” to prove transaction fees do not increase from increased transactions on the network.
In November, Bitcoin Cash (BCH) split into Bitcoin Cash ABC (now named Bitcoin Cash) and Bitcoin SV. The war between these Bitcoin Cash forks caused spam attacks that increased block sizes to 1-2 MB on average.
On Jan. 15 the average Bitcoin Cash (BCH) block size approached 5 mb, coinciding with the price of Bitcoin Cash (BCH) crashing from $2,700 to $1,500. This is perhaps the 1 case where Bitcoin Cash’s network legitimately had block sizes over 1 Mb, but it was due to people dumping their Bitcoin Cash (BCH) as fast as possible in a panic selling situation.
In summary, since Bitcoin Cash (BCH) has relatively low network activity when compared to Bitcoin (BTC), it seems that there was no point in creating Bitcoin Cash (BCH), since its block sizes are almost always below 100 KB.
Bitcoin (BTC) seems to have resolved its transaction fee problems with Segregated Witness (SegWit), which increases the block size to 1.2 MB on average. This is done by redefining the block size in terms of 1,000 units instead of 1,000 KB, and separating the witness data (signature data) from the Merkle Tree and counting each KB of the witness data as ¼ of a unit.
Also, the Bitcoin Lightning Network is maturing and can handle as much transaction volume as Bitcoin needs without increasing on-chain transactions or block size. In November 2018, the Lightning Network rapidly grew in capacity due to increasing Bitcoin transaction volume and proved that it is a solution which can completely mitigate rises in Bitcoin transaction fees. The fact that Bitcoin (BTC) has become scalable to increased transaction frequency makes the creation of Bitcoin Cash (BCH) even more pointless.
submitted by turtlecane to CryptoCurrency [link] [comments]

Day 5: I will post this guide regularly until available solutions like SegWit & order batching are mass adopted, the mempool is empty once again, and transaction fees are low. User demand from this community can help lead to some big changes. Have you joined the /r/Bitcoin SegWit effort?

SUMMARY
Segregrated Witness (SegWit) was activated on the Bitcoin network August 24, 2017 as a soft fork that is backward compatible with previous bitcoin transactions (Understanding Segregated Witness). Since that time wallets and exchanges have been slow to deploy SegWit, some admitting in December 2017 that they have not even started work. If users demand SegWit now it will temporarily releive the transaction backlog while bigger solutions like Lightning are developed.
TODAY's NEWS/DEVELOPMENTS/VICTORIES
MEMPOOL/SEGWIT STATISTICS
BACKGROUND
Subhan Nadeem has pointed out that:
If every transaction in the Bitcoin network was a SegWit transaction today, blocks would contain up to 8,000 transactions, and the 138,000 unconfirmed transaction backlog would disappear instantly. Transaction fees would be almost non-existent once again.
A few thousand bitcoin users from /Bitcoin switching to making their next transactions SegWit transactions will help take pressure off the network now, and together we can encourage exchanges/wallets to rapidly deploy SegWit for everyone ASAP. Let's make 80%+ SegWit happen fast. You can help by taking one or more of the action steps below.
ACTION STEPS
  1. If your favorite wallet has not yet implemented SegWit, kindly ask them to do so immediately. In the meantime start using a wallet that has already implemented SegWit.
  2. If your favorite exchange has not yet implemented SegWit, try to avoid making any further purchases of bitcoin at that exchange and politely inform them that if they do not enable SegWit within 30-days they will lose your business. Sign-up for an account at a SegWit deployed/ready exchange now and initiate the verification process so you'll be ready to bail
  3. Help educate newcomers to bitcoin about the transaction issue, steer them towards SegWit wallets from day one, and encourage them to avoid ever purchasing bitcoin through non-SegWit ready exchanges that are harming bitcoin.
  4. Spread the word! Conact individuals, websites, etc that use bitcoin, explain the benefits of SegWit to everyone, and request they make the switch
IMPORTANT NOTE: The mempool is currently still quite backlogged. If you are a long-term holder and really have no reason to move your bitcoins at this time, wait until the mempool starts to clear and transaction fees go down before moving your bitcoins to a SegWit address or SegWit friendly exchange.
SELECTED TOP EXCHANGES BY SEGWIT & BATCHING STATUS
Exchange Segwit Status Batching Status
Binance NOT READY Yes
Bitfinex Ready ?
Bitonic Ready ? Yes
Bitstamp Deployed Yes
Bittrex ? Yes
Coinbase/GDAX NOT READY No
Gemini Ready No
HitBTC Deployed Yes
Huboi ? ?
Kraken Ready Yes
LocalBitcoins Ready ?
OKEx ? ?
Poloniex ? Yes
QuadrigaCX Deployed Yes
Shapeshift Deployed No
Source 1
Source 2
SELECTED WALLETS THAT HAVE SEGWIT ALREADY
Make sure you have a SegWit capable wallet installed and ready to use for your next bitcoin transaction
SegWit Enabled Wallets Wallet Type
Ledger Nano S Hardware
Trezor Hardware
Electrum Desktop
Armory Desktop
Edge iOS
GreenAddress iOS
BitWallet iOS
Samourai Android
GreenBits Android
Electrum Android
FAQs
If I'm a HODLer, will it help to send my BTC to a SegWit address now?
  • No, just get ready now so that your NEXT transaction will be to a SegWit wallet. Avoid burdening the network with any unneccessary transactions for now.
Can you please tell me how to move my bitcoins to SegWit address in Bitcoin core wallet? Does the sender or receiver matter?
  • The Bitcoin core wallet does not yet have a GUI for its SegWit functionality. Download Electrum v3.0.3 to generate a SegWit address.
    A transaction between two SegWit addresses is a SegWit transaction.
    A transaction sent from a SegWit address to a non-SegWit address is a SegWit transaction.
    A transaction sent from a non-SegWit address to a SegWit address is NOT a SegWit transaction. You can send a SegWit Tx if the sending address is a SegWit address.
    Source
What wallet are you using to "batch your sends"? And how can I do that?
  • Using Electrum, the "Tools" menu option: "Pay to many".
    Just enter your receive addresses and the amounts for each, and you can send multiple transactions for nearly the price of one.
Why doesn't the Core Wallet yet support SegWit?
  • The Core Wallet supports SegWit, but its GUI doesn't. The next update will likely have GUI support built-in
Why isn't a large exchange like Coinbase SegWit ready & deployed when much smaller exchanges already are? Why do they default to high fees? Where is the leadership there?
SEGWIT BLOG GUIDES
PREVIOUS DAY'S THREADS
There's lots of excellent info in the comments of the previous threads:
Edit: Bitonic batching status updated to 'Yes'
submitted by Bastiat to Bitcoin [link] [comments]

On "Segwit is a blocksize increase"

Because I still hear this argument all the time, I'd like to discuss the talking point a bit.
Today, I'm not going to discuss as much the context it's brought up in (which can make the argument border on disingenuous.) Instead I'd rather discuss it in terms of actual effectiveness.
As an initial aside, to anyone making this argument, I'll start by saying this.
Now let's look where Segwit has actually left Bitcoin
Both in blocksize,
and transaction throughput
First, notice that what is often claimed to be a "4MB maximum blocksize increase" has only once averaged above 1.3MB for a 1-day period on Feb 11th of this year and maybe a 17% overall increase in transaction capacity.
The reason blocksizes haven't been substantially higher is that SegWit (which stands for Segregated Witness) takes the signature data of a transaction and offloads it to a different blockspace.
Most transactions only have a couple of inputs and thus only need a couple of signatures so there's not much data to offload. The creators of SegWit, however, realized that there would be fringe cases with dozens or hundreds of inputs to a transaction which would have a higher proportion of data:sigdata.
That means in order to use more than ~1.7MB of space with 100% SegWit usage, you need to write transactions that have far more inputs than outputs. In plain English, you're taking balances from a large number of wallets and putting that balance in to one or two.
The obvious problem with this is in order to fulfill that requirement for any reasonable length of time, you would quickly find yourself consolidating all bitcoin to a single address... where the process couldn't possibly continue.
Because the average number of addresses in the system is going to grow instead of shrink, a 4MB benchmark simply doesn't reflect any sane notion of daily usage.
As a side note, I've even seen one user make the argument that "increasing the Signature block size to 4MB was the compromise" in spite of the fact that anything over 2MB will just be unused space in anything but outlier circumstances... And also in spite of the fact that the 2X in SegWit2x stood for... 2x...
Additionally, Schnorr signatures will effectively reduce signature data to 1-per-transaction so after implementation, the effectiveness of SegWit should fall drastically.
The more important point I'd like to make deals with how Segwit adoption has never exceeded 50%.
Now this can be seen as a half empty / half full scenario.
One person can take a look at that and say "the fact that SegWit isn't being used is proof that it's a dumb idea."
Another person can take a look at that and say "the fact that SegWit isn't being used is proof that more scaling isn't needed because there's still more space."
Personally, I think both of these assertions miss the mark in favor of this:
Bitcoin Transactions have different values to different people and the SegWit protocol best scales only when everybody on the system uses it in a preferred and expected way.
A blocksize increase on the other hand, doubles capacity regardless of how users use it.
By relying only on SegWit to scale, you slowly alienate everybody on the network who absolutely needs the extra space and you undermine the transactional utility of the network.
I don't think SegWit was a bad idea, but relying on fee pressure to force SegWit usage will probably have some longer-term adverse side effects.
TL;DR: SegWit scales best when everyone uses the network in a specific way. A blocksize increase scales no matter what.
submitted by CaptainPatent to btc [link] [comments]

Day 9: I will post this guide regularly until available solutions like SegWit, order batching, and Lightning payment channels are mass adopted, the mempool is empty once again, and tx fees are low. Have you done your part?

BACKGROUND
Segregated Witness (SegWit) was activated on the Bitcoin network August 24 2017 as a soft fork that is backward compatible with previous bitcoin transactions (Understanding Segregated Witness). Since that time wallets and exchanges have been slow to deploy SegWit, and the majority of users have not made the switch themselves.
On Dec 18 2017 Subhan Nadeem has pointed out that: If every transaction in the Bitcoin network was a SegWit transaction today, blocks would contain up to 8,000 transactions, and the 138,000 unconfirmed transaction backlog would disappear instantly. Transaction fees would be almost non-existent once again.
Mass SegWit use alone could empty the mempool, result in blocks that are not completely full, and make it possible to include transactions with $0 fee once again.
On Jan 11 2018 when BTC sends went offline at Coinbase the mempool began to rapidly empty. Later in the day when service was restored there was a sharp spike up in the mempool. Subsequently, that afternoon Brian Armstrong finally had to break his silence on the topic and admitted Coinbase is working on SegWit but has still not deployed it. It appears that this is an important data point that indicates if just a few major exchanges would deploy SegWit the high fees bitcoin is experiencing would be eliminated.
SegWit is just one technique available to exchanges and users to reduce pressure on the Bitcoin network. You can make the switch to SegWit on your next transaction, and pressure exchanges to deploy SegWit NOW along with other actions that will reduce their transaction impact on the network. You can help by taking one or more of the action steps below.
ACTION STEPS
  1. If your favorite wallet has not yet implemented SegWit, kindly ask them to do so immediately. If your wallet is not committed to implementing SegWit fast, speak out online any way you can and turn up the pressure. In the meantime start using a wallet that has already implemented SegWit.
  2. If your favorite exchange has not yet implemented SegWit, try to avoid making any further purchases of bitcoin at that exchange and politely inform them that if they do not enable SegWit within 30-days they will lose your business. Sign-up for an account at a SegWit deployed/ready exchange now and initiate the verification process so you'll be ready to bail
  3. Help educate newcomers to bitcoin about the transaction issue, steer them towards SegWit wallets from day one, and encourage them to avoid ever purchasing bitcoin through non-SegWit ready exchanges that are harming bitcoin.
  4. Spread the word! Contact individuals, websites, etc that use bitcoin, explain the benefits of SegWit to everyone, and request they make the switch. Use social media to point out the benefits of SegWit adoption.
IMPORTANT NOTE: The mempool is currently still quite backlogged. If you are a long-term holder and really have no reason to move your bitcoins at this time, wait until the mempool starts to clear and transaction fees go down before moving your bitcoins to a SegWit address or SegWit friendly exchange.
BEYOND SEGWIT - BATCHING, PAYMENT CHANNELS, LIGHTNING
Batching is another great way that exchanges can reduce their fees. See: Saving up to 80% on Bitcoin transaction fees by batching payments. Despite the benefits of batching, some exchanges have been slow to implement it. Users should demand this or walk.
Beyond SegWit & Batching, Lightning Network integration will have even more effect. Lightning is now active and exchanges could setup payment channels between each other so that on-chain transactions need not take place. Some ideas have to outline how that might work are here: Google Doc - Lightning Exchanges. Which two bitcoin exchanges will be the first to establish a lightning channel between themselves and offer free/instant transfers between them for their customers? This will happen in 2018
MEMPOOL/SEGWIT STATISTICS
NEWS/DEVELOPMENTS/VICTORIES
SELECTED TOP EXCHANGES BY BATCHING & SEGWIT STATUS
Exchange Segwit Status Batching Status
Binance NOT READY Yes
Bitfinex Ready Yes
Bitonic Ready Yes
Bitstamp Deployed Yes
Bittrex ? Yes
Coinbase/GDAX NOT READY No
Gemini Ready No
HitBTC Deployed Yes
Huboi ? ?
Kraken Deployed Yes
LocalBitcoins Deployed Yes
OKEx ? ?
Poloniex ? Yes
QuadrigaCX Deployed Yes
Shapeshift Deployed No
Note: all exchanges that have deployed SegWit are currently only sending to p2sh SegWit addresses for now. No exchange will send to a bech32 address like the ones that Electrum generates
Source 1: BitcoinCore.org
Source 2: /Bitcoin
Official statements from exchanges:
SELECTED WALLETS THAT HAVE SEGWIT ALREADY
Make sure you have a SegWit capable wallet installed and ready to use for your next bitcoin transaction
SegWit Enabled Wallets Wallet Type
Ledger Nano S Hardware
Trezor Hardware
Electrum Desktop
Armory Desktop
Edge iOS
GreenAddress iOS
BitWallet iOS
Samourai Android
GreenBits Android
Electrum Android
SegWitAddress.org Paper
FAQs
If I'm a HODLer, will it help to send my BTC to a SegWit address now?
No, just get ready now so that your NEXT transaction will be to a SegWit wallet. Avoid burdening the network with any unnecessary transactions for now.
Why is SegWit adoption going so slowly? Is it a time-consuming process, is there risk involved, is it laziness, or something else?
SegWit will require some extra work to be done right and securely. Also, most exchanges let the user pay the fee, and up to now users have not been overly concerned about fees so for some exchanges it hasn't been a priority.
Once Segwit is FULLY adopted, what do we see the fees/transaction times going to?
Times stay the same - fees will go down. How much and for how long depends on what the demand for transactions will be at that time.
What determines bitcoin transaction fees, to begin with?
Fees are charged per byte of data and are bid up by users. Miners will typically include the transaction with the highest fee/byte first.
Can you please tell me how to move my bitcoins to SegWit address in Bitcoin core wallet? Does the sender or receiver matter?
The Bitcoin core wallet does not yet have a GUI for its SegWit functionality. Download the latest version of Electrum to generate a SegWit address.
A transaction between two SegWit addresses is a SegWit transaction.
A transaction sent from a SegWit address to a non-SegWit address is a SegWit transaction.
A transaction sent from a non-SegWit address to a SegWit address is NOT a SegWit transaction. You can send a SegWit Tx if the sending address is a SegWit address.
Source: HowToToken
What wallet are you using to "batch your sends"? And how can I do that?
Using Electrum, the "Tools" menu option: "Pay to many".
Just enter your receive addresses and the amounts for each, and you can send multiple transactions for nearly the price of one.
Why doesn't the Core Wallet yet support SegWit?
The Core Wallet supports SegWit, but its GUI doesn't. The next update will likely have GUI support built-in
Why isn't a large exchange like Coinbase SegWit ready & deployed when much smaller exchanges already are? Why do they default to high fees? Where is the leadership there?
Draw your own conclusions based on their own words:
March 2016 - Coinbase CEO Brian Armstrong has reservations about Core
Dec 2017 - Coinbase is STILL working on Segwit
P2SH/bech32 FAQs
What are the two SegWit address formats and why do they exist?
It's been a challenge for wallet developers to implement SegWit in a way that users can easily and without too much disruption migrate from legacy to SegWit addresses. The first wallets to enable SegWit addresses – Ledger, Trezor, Core, GreenAddress – use so-called “nested P2SH addresses.” This means they take the existing Pay 2 Script Hash address – starting with a “3” – and put a SegWit address into it. This enables a high grade of compatibility to exist wallets as every wallet is familiar with these addresses, but it is a workaround which results in SegWit transactions needing around 10 percent more space than they otherwise would.
Electrum 3.0 was the first wallet to use bech32 addresses instead of nested p2sh addresses.
Source: BTCManager.com
What is the difference in address format between SegWit address formats P2SH and bech32?
P2SH starts with "3..."
bech32 starts with "bc1..."
Which addresses can I send from/to?
P2SH Segwit addresses can be sent to using older Bitcoin software with no Segwit support. This supports backward compatibility
bech32 can only be sent to from newer Bitcoin software that support bech32. Ex: Electrum
Source: BitcoinTalk.org
Why did ThePirateBay put up two Bitcoin donation addresses on their frontpage, one bech32 and one not?
The address starting with a "3..." is a P2SH SegWit address that can be sent BTC from any bitcoin address including a legacy address. The address starting with a "bc1..." is a bech32 SegWit address that can only be sent to from newer wallets that support bech32.
SEGWIT BLOG GUIDES
PREVIOUS DAY'S THREADS
There's lots of excellent info in the comments of the previous threads:
submitted by Bastiat to Bitcoin [link] [comments]

We really need to start pushing for SegWit support. Stop waiting for the Lightning Network to fix everything.

What is SegWit ?
The formal title "Segregated Witness (Consensus layer)" had Bitcoin Improvement Proposals number BIP141. It is intended to solve a blockchain size limitation problem that reduces Bitcoin transaction speed. It does this by splitting the transaction into two segments, removing the unlocking signature ("witness" data) from the original portion and appending it as a separate structure at the end. (https://en.wikipedia.org/wiki/SegWit)
What's the problem?
It has been more than 3 months since SegWit was activated. The current level of support for Segwit is abysmal at only 13% of all transactions using SegWit (http://segwit.party/charts/). If everyone right now switched to a SegWit supported wallet, the mempool would likely be empty again allowing for instant transactions once again. While we're all looking at the Lightning Network to solve the congestion issues, the is a much easier and faster fix right in front of us and that is SegWit.
Why isn't everybody using SegWit yet?
That is likely due to the fact that some very large exchanges have yet to activate SegWit on their site yet. Once they do activate SegWit , we should see the number of SegWit transactions rise up. This doesn't just benefit the users as the exchanges themselves will also pay less fees. In other words, we need to pressure all big exchanges into activating Segwit. Not next year, not next month but NOW.
How can I check if my wallet is Segwit compatible?
Good news is, most hardware and software wallets use SegWit. SegWit (P2SH) addresses begin with a “3”, like multisig addresses so they are easy to spot. If your wallet address does not begin with a 3, then it's not SegWit compatible. Those are the addresses we need to get changed and updated to SegWit compatible ones.
So who hasn't activated SegWit yet?
It's time to name and shame the exchanges that haven't activated SegWit yet. You can find a list of all major exchanges and players that have activated SegWit right here: https://bitcoincore.org/en/segwit_adoption/ If your wallet or exchange is NOT highlighted in green, it means it still hasn't activated SegWit yet and needs some serious encouragement from their paying customers. Those will either be marked in yellow as a work in progress or marked in white as planned. Neither of those two statuses are acceptable. It has been more than 3 months now and neglecting to activate Segwit is becoming a serious problem for the whole blockchain and needs to be dealt with right now.
You can help speed up SegWit activation!
This is where big numbers hold big power. You can all help by first checking if your wallet is SegWit compatible (needs to start with a 3). If it's not SegWit compatible, then please make whoever provided the wallet is aware of this issue you are facing and request them to provide a SegWit wallet as soon as possible. So for example if you have a wallet on Coinbase, you will notice it has not activated SegWit yet. You help the cause greatly by sending the exchange support a message that you want to see SegWit activated on their exchange. If you want to take it one step further, you could move your Bitcoins and other funds away from your non-SegWit wallet and exchange to one that does have SegWit activated.
The time for action is now. If you have any questions, please ask them.
tl;dr: SegWit adoption is seriously low. If we can increase it we get faster transactions at lower costs.
submitted by ForeverDutch92 to Bitcoin [link] [comments]

Day 8: I will post this guide regularly until available solutions like SegWit, order batching, and Lightning payment channels are mass adopted, the mempool is empty once again, and tx fees are low. BTC Core SegWit GUI coming May 1, Coinbase incompetence exposed, more exchanges deploy SegWit

BACKGROUND
Segregated Witness (SegWit) was activated on the Bitcoin network August 24 2017 as a soft fork that is backward compatible with previous bitcoin transactions (Understanding Segregated Witness). Since that time wallets and exchanges have been slow to deploy SegWit, and the majority of users have not made the switch themselves.
On Dec 18 2017 Subhan Nadeem has pointed out that: If every transaction in the Bitcoin network was a SegWit transaction today, blocks would contain up to 8,000 transactions, and the 138,000 unconfirmed transaction backlog would disappear instantly. Transaction fees would be almost non-existent once again.
Mass SegWit use alone could empty the mempool, result in blocks that are not completely full, and make it possible to include transactions with $0 fee once again.
On Jan 11 2018 when BTC sends went offline at Coinbase the mempool began to rapidly empty. Later in the day when service was restored there was a sharp spike up in the mempool. Subsequently, that afternoon Brian Armstrong finally had to break his silence on the topic and admitted Coinbase is working on SegWit but has still not deployed it. It appears that the high fees bitcoin is experiencing could be easily addressed and need not exist.
SegWit is just one technique available to exchanges and users to reduce pressure on the Bitcoin network. You can make the switch to SegWit on your next transaction, and pressure exchanges to deploy SegWit NOW along with other actions that will reduce their transaction impact on the network. You can help by taking one or more of the action steps below.
ACTION STEPS
  1. If your favorite wallet has not yet implemented SegWit, kindly ask them to do so immediately. If your wallet is not committed to implementing SegWit fast, speak out online any way you can and turn up the pressure. In the meantime start using a wallet that has already implemented SegWit.
  2. If your favorite exchange has not yet implemented SegWit, try to avoid making any further purchases of bitcoin at that exchange and politely inform them that if they do not enable SegWit within 30-days they will lose your business. Sign-up for an account at a SegWit deployed/ready exchange now and initiate the verification process so you'll be ready to bail
  3. Help educate newcomers to bitcoin about the transaction issue, steer them towards SegWit wallets from day one, and encourage them to avoid ever purchasing bitcoin through non-SegWit ready exchanges that are harming bitcoin.
  4. Spread the word! Contact individuals, websites, etc that use bitcoin, explain the benefits of SegWit to everyone, and request they make the switch. Use social media to point out the benefits of SegWit adoption.
IMPORTANT NOTE: The mempool is currently still quite backlogged. If you are a long-term holder and really have no reason to move your bitcoins at this time, wait until the mempool starts to clear and transaction fees go down before moving your bitcoins to a SegWit address or SegWit friendly exchange.
BEYOND SEGWIT - BATCHING, PAYMENT CHANNELS, LIGHTNING
Batching is another great way that exchanges can reduce their fees. See: Saving up to 80% on Bitcoin transaction fees by batching payments. Despite the benefits of batching, some exchanges have been slow to implement it. Users should demand this or walk.
Beyond SegWit & Batching, Lightning Network integration will have even more effect. Lightning is now active and exchanges could setup payment channels between each other so that on-chain transactions need not take place. Some ideas have to outline how that might work are here: Google Doc - Lightning Exchanges. Which two bitcoin exchanges will be the first to establish a lightning channel between themselves and offer free/instant transfers between them for their customers? This will happen in 2018
MEMPOOL/SEGWIT STATISTICS
NEWS/DEVELOPMENTS/VICTORIES
SELECTED TOP EXCHANGES BY BATCHING & SEGWIT STATUS
Exchange Segwit Status Batching Status
Binance NOT READY Yes
Bitfinex Ready Yes
Bitonic Ready Yes
Bitstamp Deployed Yes
Bittrex ? Yes
Coinbase/GDAX NOT READY No
Gemini Ready No
HitBTC Deployed Yes
Huboi ? ?
Kraken Deployed Yes
LocalBitcoins Deployed Yes
OKEx ? ?
Poloniex ? Yes
QuadrigaCX Deployed Yes
Shapeshift Deployed No
Note: all exchanges that have deployed SegWit are currently only sending to p2sh SegWit addresses for now. No exchange will send to a bech32 address like the ones that Electrum generates
Source 1: BitcoinCore.org
Source 2: /Bitcoin
Official statements from exchanges:
SELECTED WALLETS THAT HAVE SEGWIT ALREADY
Make sure you have a SegWit capable wallet installed and ready to use for your next bitcoin transaction
SegWit Enabled Wallets Wallet Type
Ledger Nano S Hardware
Trezor Hardware
Electrum Desktop
Armory Desktop
Edge iOS
GreenAddress iOS
BitWallet iOS
Samourai Android
GreenBits Android
Electrum Android
SegWitAddress.org Paper
FAQs
If I'm a HODLer, will it help to send my BTC to a SegWit address now?
No, just get ready now so that your NEXT transaction will be to a SegWit wallet. Avoid burdening the network with any unnecessary transactions for now.
Why is SegWit adoption going so slowly? Is it a time-consuming process, is there risk involved, is it laziness, or something else?
SegWit will require some extra work to be done right and securely. Also, most exchanges let the user pay the fee, and up to now users have not been overly concerned about fees so for some exchanges it hasn't been a priority.
Once Segwit is FULLY adopted, what do we see the fees/transaction times going to?
Times stay the same - fees will go down. How much and for how long depends on what the demand for transactions will be at that time.
What determines bitcoin transaction fees, to begin with?
Fees are charged per byte of data and are bid up by users. Miners will typically include the transaction with the highest fee/byte first.
Can you please tell me how to move my bitcoins to SegWit address in Bitcoin core wallet? Does the sender or receiver matter?
The Bitcoin core wallet does not yet have a GUI for its SegWit functionality. Download the latest version of Electrum to generate a SegWit address.
A transaction between two SegWit addresses is a SegWit transaction.
A transaction sent from a SegWit address to a non-SegWit address is a SegWit transaction.
A transaction sent from a non-SegWit address to a SegWit address is NOT a SegWit transaction. You can send a SegWit Tx if the sending address is a SegWit address.
Source: HowToToken
What wallet are you using to "batch your sends"? And how can I do that?
Using Electrum, the "Tools" menu option: "Pay to many".
Just enter your receive addresses and the amounts for each, and you can send multiple transactions for nearly the price of one.
Why doesn't the Core Wallet yet support SegWit?
The Core Wallet supports SegWit, but its GUI doesn't. The next update will likely have GUI support built-in
Why isn't a large exchange like Coinbase SegWit ready & deployed when much smaller exchanges already are? Why do they default to high fees? Where is the leadership there?
Draw your own conclusions based on their own words:
March 2016 - Coinbase CEO Brian Armstrong has reservations about Core
Dec 2017 - Coinbase is STILL working on Segwit
P2SH/bech32 FAQs
What are the two SegWit address formats and why do they exist?
It's been a challenge for wallet developers to implement SegWit in a way that users can easily and without too much disruption migrate from legacy to SegWit addresses. The first wallets to enable SegWit addresses – Ledger, Trezor, Core, GreenAddress – use so-called “nested P2SH addresses.” This means they take the existing Pay 2 Script Hash address – starting with a “3” – and put a SegWit address into it. This enables a high grade of compatibility to exist wallets as every wallet is familiar with these addresses, but it is a workaround which results in SegWit transactions needing around 10 percent more space than they otherwise would.
Electrum 3.0 was the first wallet to use bech32 addresses instead of nested p2sh addresses.
Source: BTCManager.com
What is the difference in address format between SegWit address formats P2SH and bech32?
P2SH starts with "3..."
bech32 starts with "bc1..."
Which addresses can I send from/to?
P2SH Segwit addresses can be sent to using older Bitcoin software with no Segwit support. This supports backward compatibility
bech32 can only be sent to from newer Bitcoin software that support bech32. Ex: Electrum
Source: BitcoinTalk.org
Why did ThePirateBay put up two Bitcoin donation addresses on their frontpage, one bech32 and one not?
The address starting with a "3..." is a P2SH SegWit address that can be sent BTC from any bitcoin address including a legacy address. The address starting with a "bc1..." is a bech32 SegWit address that can only be sent to from newer wallets that support bech32.
SEGWIT BLOG GUIDES
PREVIOUS DAY'S THREADS
There's lots of excellent info in the comments of the previous threads:
submitted by Bastiat to Bitcoin [link] [comments]

Day 7: I will post this guide regularly until available solutions like SegWit & order batching are mass adopted, the mempool is empty once again, and tx fees are low. Do you want low tx fees, because this is how you get low tx fees

TL/DR
Bitcoin users can help lower transaction fees and improve bitcoin by switching to SegWit addresses and encourage wallets/exchanges to do the same.
SUMMARY
Segregated Witness (SegWit) was activated on the Bitcoin network August 24 2017 as a soft fork that is backward compatible with previous bitcoin transactions (Understanding Segregated Witness). Since that time wallets and exchanges have been slow to deploy SegWit, some admitting in December 2017 that they have not even started work on integrating it. Others, such as Zebpay in India have already implemented SegWit and are reaping the benefits of reduced transaction fees. If bitcoin users demand SegWit now it will temporarily relieve the transaction backlog while more even more advanced solutions such as Lightning are developed.
Batching is another great way that exchanges can reduce their fees. See: Saving up to 80% on Bitcoin transaction fees by batching payments. Despite the benefits of batching, some exchanges have been slow to implement it.
There is an opportunity now for all bitcoin users to individually contribute to help strengthen and improve the bitcoin protocol. At this point, the process requires a bit of work/learning on the part of the user, but in doing so you'll actually be advancing bitcoin and leaving what could turn out to be a multi-generational legacy for humanity.
MEMPOOL/SEGWIT STATISTICS
BACKGROUND
On Dec 18 Subhan Nadeem has pointed out that:
If every transaction in the Bitcoin network was a SegWit transaction today, blocks would contain up to 8,000 transactions, and the 138,000 unconfirmed transaction backlog would disappear instantly. Transaction fees would be almost non-existent once again.
A few thousand bitcoin users from /Bitcoin switching to making their next transactions SegWit transactions will help take pressure off the network now, and together we can encourage exchanges/wallets to rapidly deploy SegWit for everyone ASAP. Let's make 80%+ SegWit happen fast. You can help by taking one or more of the action steps below.
ACTION STEPS
  1. If your favorite wallet has not yet implemented SegWit, kindly ask them to do so immediately. In the meantime start using a wallet that has already implemented SegWit.
  2. If your favorite exchange has not yet implemented SegWit, try to avoid making any further purchases of bitcoin at that exchange and politely inform them that if they do not enable SegWit within 30-days they will lose your business. Sign-up for an account at a SegWit deployed/ready exchange now and initiate the verification process so you'll be ready to bail
  3. Help educate newcomers to bitcoin about the transaction issue, steer them towards SegWit wallets from day one, and encourage them to avoid ever purchasing bitcoin through non-SegWit ready exchanges that are harming bitcoin.
  4. Spread the word! Conact individuals, websites, etc that use bitcoin, explain the benefits of SegWit to everyone, and request they make the switch
IMPORTANT NOTE: The mempool is currently still quite backlogged. If you are a long-term holder and really have no reason to move your bitcoins at this time, wait until the mempool starts to clear and transaction fees go down before moving your bitcoins to a SegWit address or SegWit friendly exchange.
SELECTED TOP EXCHANGES BY BATCHING & SEGWIT STATUS
Exchange Segwit Status Batching Status
Binance NOT READY Yes
Bitfinex Ready Yes
Bitonic Ready Yes
Bitstamp Deployed Yes
Bittrex ? Yes
Coinbase/GDAX NOT READY No
Gemini Ready No
HitBTC Deployed Yes
Huboi ? ?
Kraken Deployed Yes
LocalBitcoins Ready Yes
OKEx ? ?
Poloniex ? Yes
QuadrigaCX Deployed Yes
Shapeshift Deployed No
Note: all exchanges that have deployed SegWit are currently only sending to p2sh SegWit addresses for now. No exchange will send to a bech32 address like the ones that Electrum generates
Source 1: BitcoinCore.org
Source 2: /Bitcoin
Official statements from exchanges:
SELECTED WALLETS THAT HAVE SEGWIT ALREADY
Make sure you have a SegWit capable wallet installed and ready to use for your next bitcoin transaction
SegWit Enabled Wallets Wallet Type
Ledger Nano S Hardware
Trezor Hardware
Electrum Desktop
Armory Desktop
Edge iOS
GreenAddress iOS
BitWallet iOS
Samourai Android
GreenBits Android
Electrum Android
SegWitAddress.org Paper
FAQs
If I'm a HODLer, will it help to send my BTC to a SegWit address now?
  • No, just get ready now so that your NEXT transaction will be to a SegWit wallet. Avoid burdening the network with any unneccessary transactions for now.
Why is SegWit adoption going so slowly? Is it a time-consuming process, is there risk involved, is it laziness, or something else?
  • SegWit will require some extra work to be done right and securely. Also, most exchanges let the user pay the fee, and up to now users have not been overly concerned about fees so for some exchanges it hasn't been a priority.
Once Segwit is FULLY adopted, what do we see the fees/transaction times going to?
  • Times stay the same - fees will go down. How much and for how long depends on what the demand for transactions will be at that time.
What determines bitcoin transaction fees, to begin with?
  • Fees are charged per byte of data and are bid up by users. Miners will typically include the transaction with the highest fee/byte first.
Can you please tell me how to move my bitcoins to SegWit address in Bitcoin core wallet? Does the sender or receiver matter?
  • The Bitcoin core wallet does not yet have a GUI for its SegWit functionality. Download Electrum v3.0.3 to generate a SegWit address.
    A transaction between two SegWit addresses is a SegWit transaction.
    A transaction sent from a SegWit address to a non-SegWit address is a SegWit transaction.
    A transaction sent from a non-SegWit address to a SegWit address is NOT a SegWit transaction. You can send a SegWit Tx if the sending address is a SegWit address.
    Source: HowToToken
What wallet are you using to "batch your sends"? And how can I do that?
  • Using Electrum, the "Tools" menu option: "Pay to many".
    Just enter your receive addresses and the amounts for each, and you can send multiple transactions for nearly the price of one.
Why doesn't the Core Wallet yet support SegWit?
  • The Core Wallet supports SegWit, but its GUI doesn't. The next update will likely have GUI support built-in
Why isn't a large exchange like Coinbase SegWit ready & deployed when much smaller exchanges already are? Why do they default to high fees? Where is the leadership there?
P2SH/bech32 FAQs
What are the two SegWit address formats and why do they exist?
  • It's been a challenge for wallet developers to implement SegWit in a way that users can easily and without too much disruption migrate from legacy to SegWit addresses. The first wallets to enable SegWit addresses – Ledger, Trezor, Core, GreenAddress – use so-called “nested P2SH addresses.” This means they take the existing Pay 2 Script Hash address – starting with a “3” – and put a SegWit address into it. This enables a high grade of compatibility to existing wallets as every wallet is familiar with these addresses, but it is a workaround which results in SegWit transactions needing around 10 percent more space than they otherwise would.
    Electrum 3.0 was the first wallet to use bech32 addresses instead of nested p2sh addresses.
    Source: BTCManager.com
What is the difference in address format between SegWit address formats P2SH and bech32?
  • P2SH starts with "3..."
    bech32 starts with "bc1..."
Which addresses can I send from/to?
  • P2SH Segwit addresses can be sent to using older Bitcoin software with no Segwit support. This supports backwards compatibility
    bech32 can only be sent to from newer Bitcoin software that support bech32. Ex: Electrum
    Source: BitcoinTalk.org
Why did ThePirateBay put up two Bitcoin donation addresses on their frontpage, one bech32 and one not?
  • The address starting with a "3..." is a P2SH SegWit address that can be sent BTC from any bitcoin address including a legacy address. The address starting with a "bc1..." is a bech32 SegWit address that can only be sent to from newer wallets that support bech32.
SEGWIT BLOG GUIDES
PREVIOUS DAY'S THREADS
There's lots of excellent info in the comments of the previous threads:
submitted by Bastiat to Bitcoin [link] [comments]

Day 6: I will post this guide regularly until available solutions like SegWit & order batching are mass adopted, the mempool is empty once again, and tx fees are low. Refer a friend to SegWit today. There's no $10 referral offer, but you'll both get lower fees and help strengthen the BTC protocol

TL/DR
Bitcoin users can help lower transaction fees and contribute to bitcoin by switching to SegWit addresses and encourage wallets/exchanges to do the same.
SUMMARY
Segregated Witness (SegWit) was activated on the Bitcoin network August 24 2017 as a soft fork that is backward compatible with previous bitcoin transactions (Understanding Segregated Witness). Since that time wallets and exchanges have been slow to deploy SegWit, some admitting in December 2017 that they have not even started work on integrating it. Others, such as Zebpay in India have already implemented SegWit and are reaping the benefits of reduced transaction fees. If bitcoin users demand SegWit now it will temporarily relieve the transaction backlog while more even more advanced solutions such as Lightning are developed.
Batching is another great way that exchanges can reduce their fees. See: Saving up to 80% on Bitcoin transaction fees by batching payments. Despite the benefits of batching, some exchanges have been slow to implement it.
There is an opportunity now for all bitcoin users to individually contribute to help strengthen and improve the bitcoin protocol. At this point, the process requires a bit of work/learning on the part of the user, but in doing so you'll actually be advancing bitcoin and leaving what could turn out to be a multi-generational legacy for humanity.
MEMPOOL/SEGWIT STATISTICS
BACKGROUND
On Dec 18 Subhan Nadeem has pointed out that:
If every transaction in the Bitcoin network was a SegWit transaction today, blocks would contain up to 8,000 transactions, and the 138,000 unconfirmed transaction backlog would disappear instantly. Transaction fees would be almost non-existent once again.
A few thousand bitcoin users from /Bitcoin switching to making their next transactions SegWit transactions will help take pressure off the network now, and together we can encourage exchanges/wallets to rapidly deploy SegWit for everyone ASAP. Let's make 80%+ SegWit happen fast. You can help by taking one or more of the action steps below.
ACTION STEPS
  1. If your favorite wallet has not yet implemented SegWit, kindly ask them to do so immediately. In the meantime start using a wallet that has already implemented SegWit.
  2. If your favorite exchange has not yet implemented SegWit, try to avoid making any further purchases of bitcoin at that exchange and politely inform them that if they do not enable SegWit within 30-days they will lose your business. Sign-up for an account at a SegWit deployed/ready exchange now and initiate the verification process so you'll be ready to bail
  3. Help educate newcomers to bitcoin about the transaction issue, steer them towards SegWit wallets from day one, and encourage them to avoid ever purchasing bitcoin through non-SegWit ready exchanges that are harming bitcoin.
  4. Spread the word! Conact individuals, websites, etc that use bitcoin, explain the benefits of SegWit to everyone, and request they make the switch
IMPORTANT NOTE: The mempool is currently still quite backlogged. If you are a long-term holder and really have no reason to move your bitcoins at this time, wait until the mempool starts to clear and transaction fees go down before moving your bitcoins to a SegWit address or SegWit friendly exchange.
SELECTED TOP EXCHANGES BY BATCHING & SEGWIT STATUS
Exchange Segwit Status Batching Status
Binance NOT READY Yes
Bitfinex Ready Yes
Bitonic Ready Yes
Bitstamp Deployed Yes
Bittrex ? Yes
Coinbase/GDAX NOT READY No
Gemini Ready No
HitBTC Deployed Yes
Huboi ? ?
Kraken Deployed Yes
LocalBitcoins Ready Yes
OKEx ? ?
Poloniex ? Yes
QuadrigaCX Deployed Yes
Shapeshift Deployed No
  • Note: all exchanges that have deployed SegWit are currently only sending to p2sh SegWit addresses for now. No exchange will send to a bech32 address like the ones that Electrum generates
Source 1: BitcoinCore.org
Source 2: /Bitcoin
Official statements from exchanges:
SELECTED WALLETS THAT HAVE SEGWIT ALREADY
Make sure you have a SegWit capable wallet installed and ready to use for your next bitcoin transaction
SegWit Enabled Wallets Wallet Type
Ledger Nano S Hardware
Trezor Hardware
Electrum Desktop
Armory Desktop
Edge iOS
GreenAddress iOS
BitWallet iOS
Samourai Android
GreenBits Android
Electrum Android
FAQs
If I'm a HODLer, will it help to send my BTC to a SegWit address now?
  • No, just get ready now so that your NEXT transaction will be to a SegWit wallet. Avoid burdening the network with any unneccessary transactions for now.
Why is SegWit adoption going so slowly? Is it a time-consuming process, is there risk involved, is it laziness, or something else?
  • SegWit will require some extra work to be done right and securely. Also, most exchanges let the user pay the fee, and up to now users have not been overly concerned about fees so for some exchanges it hasn't been a priority.
Once Segwit is FULLY adopted, what do we see the fees/transaction times going to?
  • Times stay the same - fees will go down. How much and for how long depends on what the demand for transactions will be at that time.
What determines bitcoin transaction fees, to begin with?
  • Fees are charged per byte of data and are bid up by users. Miners will typically include the transaction with the highest fee/byte first.
Can you please tell me how to move my bitcoins to SegWit address in Bitcoin core wallet? Does the sender or receiver matter?
  • The Bitcoin core wallet does not yet have a GUI for its SegWit functionality. Download Electrum v3.0.3 to generate a SegWit address.
    A transaction between two SegWit addresses is a SegWit transaction.
    A transaction sent from a SegWit address to a non-SegWit address is a SegWit transaction.
    A transaction sent from a non-SegWit address to a SegWit address is NOT a SegWit transaction. You can send a SegWit Tx if the sending address is a SegWit address.
    Source: HowToToken
What wallet are you using to "batch your sends"? And how can I do that?
  • Using Electrum, the "Tools" menu option: "Pay to many".
    Just enter your receive addresses and the amounts for each, and you can send multiple transactions for nearly the price of one.
Why doesn't the Core Wallet yet support SegWit?
  • The Core Wallet supports SegWit, but its GUI doesn't. The next update will likely have GUI support built-in
Why isn't a large exchange like Coinbase SegWit ready & deployed when much smaller exchanges already are? Why do they default to high fees? Where is the leadership there?
P2SH/bech32 FAQs
What are the two SegWit address formats and why do they exist?
  • It's been a challenge for wallet developers to implement SegWit in a way that users can easily and without too much disruption migrate from legacy to SegWit addresses. The first wallets to enable SegWit addresses – Ledger, Trezor, Core, GreenAddress – use so-called “nested P2SH addresses.” This means they take the existing Pay 2 Script Hash address – starting with a “3” – and put a SegWit address into it. This enables a high grade of compatibility to existing wallets as every wallet is familiar with these addresses, but it is a workaround which results in SegWit transactions needing around 10 percent more space than they otherwise would.
    Electrum 3.0 was the first wallet to use bech32 addresses instead of nested p2sh addresses.
    Source: BTCManager.com
What is the difference in address format between SegWit address formats P2SH and bech32?
  • P2SH starts with "3..."
    bech32 starts with "bc1..."
Which addresses can I send from/to?
  • P2SH Segwit addresses can be sent to using older Bitcoin software with no Segwit support. This supports backwards compatibility
    bech32 can only be sent to from newer Bitcoin software that support bech32. Ex: Electrum
    Source: BitcoinTalk.org
Why did ThePirateBay put up two Bitcoin donation addresses on their frontpage, one bech32 and one not?
  • The address starting with a "3..." is a P2SH SegWit address that can be sent BTC from any bitcoin address including a legacy address. The address starting with a "bc1..." is a bech32 SegWit address that can only be sent to from newer wallets that support bech32.
SEGWIT BLOG GUIDES
PREVIOUS DAY'S THREADS
There's lots of excellent info in the comments of the previous threads:
submitted by Bastiat to Bitcoin [link] [comments]

The Great Bitcoin Bull Market Of 2017 by Trace Mayer

By: Trace Mayer, host of The Bitcoin Knowledge Podcast.
Originally posted here with images and Youtube videos.
I just got back from a two week vacation without Internet as I was scouring some archeological ruins. I hardly thought about Bitcoin at all because there were so many other interesting things and it would be there when I got back.
Jimmy Song suggested I do an article on the current state of Bitcoin. A great suggestion but he is really smart (he worked on Armory after all!) so I better be thorough and accurate!
Therefore, this article will be pretty lengthy and meticulous.
BACKGROUND
As I completely expected, the 2X movement from the New York Agreement that was supposed to happen during the middle of my vacation flopped on its face because Jeff Garzik was driving the clown car with passengers willfully inside like Coinbase, Blockchain.info, Bitgo and Xapo and there were here massive bugS and in the code and miners like Bitmain did not want to allocate $150-350m to get it over the difficulty adjustments.
I am very disappointed in their lack of integrity with putting their money where their mouths are; myself and many others wanted to sell a lot of B2X for BTC!
On 7 December 2015, with Bitcoin trading at US$388.40, I wrote The Rise of the Fourth Great Bitcoin Bubble. On 4 December 2016, with Bitcoin trading at US$762.97, I did this interview:

As of 26 November 2017, Bitcoin is trading around US$9,250.00. That is an increase of about 2,400% since I wrote the article prognosticating this fourth great Bitcoin bull market. I sure like being right, like usual (19 Dec 2011, 1 Jul 2013), especially when there are financial and economic consequences.
With such massive gains in such a short period of time the speculative question becomes: Buy, Hold or Sell?
FUNDAMENTALS
Bitcoin is the decentralized censorship-resistant Internet Protocol for transferring value over a communications channel.
The Bitcoin network can use traditional Internet infrastructure. However, it is even more resilient because it has custom infrastructure including, thanks to Bitcoin Core developer Matt Corrallo, the FIBRE network and, thanks to Blockstream, satellites which reduce the cost of running a full-node anywhere in the world to essentially nothing in terms of money or privacy. Transactions can be cheaply broadcast via SMS messages.
SECURITY
The Bitcoin network has a difficulty of 1,347,001,430,559 which suggests about 9,642,211 TH/s of custom ASIC hardware deployed.
At a retail price of approximately US$105/THs that implies about $650m of custom ASIC hardware deployed (35% discount applied).
This custom hardware consumes approximately 30 TWh per year. That could power about 2.8m US households or the entire country of Morocco which has a population of 33.85m.
This Bitcoin mining generates approximately 12.5 bitcoins every 10 minutes or approximately 1,800 per day worth approximately US$16,650,000.
Bitcoin currently has a market capitalization greater than $150B which puts it solidly in the top-30 of M1 money stock countries and a 200 day moving average of about $65B which is increasing about $500m per day.
Average daily volumes for Bitcoin is around US$5B. That means multi-million dollar positions can be moved into and out of very easily with minimal slippage.
When my friend Andreas Antonopolous was unable to give his talk at a CRYPSA event I was invited to fill in and delivered this presentation, impromptu, on the Seven Network Effects of Bitcoin.
These seven network effects of Bitcoin are (1) Speculation, (2) Merchants, (3) Consumers, (4) Security [miners], (5) Developers, (6) Financialization and (7) Settlement Currency are all taking root at the same time and in an incredibly intertwined way.
With only the first network effect starting to take significant root; Bitcoin is no longer a little experiment of magic Internet money anymore. Bitcoin is monster growing at a tremendous rate!!

SPECULATION
For the Bitcoin price to remain at $9,250 it requires approximately US$16,650,000 per day of capital inflow from new hodlers.
Bitcoin is both a Giffen good and a Veblen good.
A Giffen good is a product that people consume more of as the price rises and vice versa — seemingly in violation of basic laws of demand in microeconomics such as with substitute goods and the income effect.
Veblen goods are types of luxury goods for which the quantity demanded increases as the price increases in an apparent contradiction of the law of demand.
There are approximately 16.5m bitcoins of which ~4m are lost, ~4-6m are in deep cold storage, ~4m are in cold storage and ~2-4m are salable.
(http://www.runtogold.com/images/lost-bitcoins-1.jpg)
(http://www.runtogold.com/images/lost-bitcoins-2.jpg)
And forks like BCash (BCH) should not be scary but instead be looked upon as an opportunity to take more territory on the Bitcoin blockchain by trading the forks for real bitcoins which dries up more salable supply by moving it, likely, into deep cold storage.
According to Wikipedia, there are approximately 15.4m millionaires in the United States and about 12m HNWIs ($30m+ net worth) in the world. In other words, if every HNWI in the world wanted to own an entire bitcoin as a 'risk-free asset' that cannot be confiscated, seized or have the balance other wise altered then they could not.
For wise portfolio management, these HNWIs should have at least about 2-5% in gold and 0.5-1% in bitcoin.
Why?