user-1: Does anyone know why Bitcoin requires miners to broadcast blocks that contains full transactions?
When a user want to make a payment on Bitcion, he/she needs to broadcast a signed transaction, and miners will gather all transactions in a transaction pool. Later, when a miner successfully mined a 1MB block, he/she will broadcast this block including thousands of transactions. My question is that why cannot the miner only include transaction hashes in the block so that more transactions can be included? 

user7272: You mention in your comment that They can still put full transactions to the full blockchain. This is exactly what they are doing. The full blockchain is simply a collection of the blocks. Since the blocks contain the full transactions, the transactions are in the blockchain. 
If the blocks contained only the transaction hashes, the raw transaction data would have to be stored and transmitted separately. This adds more overhead. 
There have been proposals to allow nodes to broadcast a tx hash list and the block header, based on the assumption that most nodes will have most transactions in their mempool. They can then assemble the full block themselves before validate and saving it, requesting any missing transactions from the network.
I'm not sure if any such proposal was implemented, however.

user30668: Transaction should be verifiable (and may be verified) by each full node. If block only contained the transaction hashes, any node who has not been online during the transactions propagation, or simply has not received the transactions, would not be able to verify the correctness of the transactions referred in the block.
Furthermore, when new nodes join the network they request the whole blockchain from their peers, and verify that each block ever included in the blockchain is correct, which refers to the previous statement. (Actually there are certain checkpoints in the process, but lets keep it simple. You can refer to this question for further information about them.) 

user38618: 
only include transaction hashes

Blocks must include transactions. It's the way how transactions are archived. Otherwise, over 100 GB of transactions had to be stored in mempool.
However, you're right. Each transaction is broadcast twice: Once when a user makes a transactions, once when a miner creates a block containing it. There have been various solutions to that: (The primary goal is: relay the least amount of transaction data (smaller than TXID!) to other nodes.)

Xthin: Uses bloom filters
Compact Blocks: Slightly better Xthin
Graphene: Yet the best (without a properly tested implementation) way to relay new blocks, using both bloom filters and IBLTs.


user5406: In current versions of Bitcoin Core, most transactions are only relayed once and all transaction are only validated once.
New blocks and transactions in Bitcoin are usually advertised to peers by use of inv (inventory) messages. Blocks are thereby identified with the hash of their header, while transactions are identified by a hash over the complete transaction (also called txid). The peer that receives the inv message will respond by requesting the block header, the full block, a compact block, a Merkle block, or the transaction data if they want it. 
Transactions are only relayed twice on older implementations of Bitcoin Core that always request the full block when it is announced by a peer for the first time. Newer implementations use Compact Blocks which transfer only the block header, an encoding of the transactions and up to a handful of transactions that the sending node didn't have when it received the block itself. Nodes don't revalidate transactions that they already had in their mempool, as transactions get validated before a node adds them to their the mempool.

via Compact Blocks FAQ
The full list of transactions must be stored in the blockchain to allow new peers to independently validate the entire transaction history of Bitcoin.

-1: <p>Does anyone know why Bitcoin requires miners to broadcast blocks that contains full transactions?</p>

<p>When a user want to make a payment on Bitcion, he/she needs to broadcast a signed transaction, and miners will gather all transactions in a transaction pool. Later, when a miner successfully mined a 1MB block, he/she will broadcast this block including thousands of transactions. My question is that why cannot the miner only include transaction hashes in the block so that more transactions can be included? </p>
 7272: <p>You mention in your comment that <code>They can still put full transactions to the full blockchain</code>. This is exactly what they are doing. The full blockchain is simply a collection of the blocks. Since the blocks contain the full transactions, the transactions are in the blockchain. </p>

<p>If the blocks contained only the transaction hashes, the raw transaction data would have to be stored and transmitted separately. This adds more overhead. </p>

<p>There have been <a href="https://gist.github.com/gavinandresen/e20c3b5a1d4b97f79ac2" rel="nofollow noreferrer">proposals</a> to allow nodes to broadcast a tx hash list and the block header, based on the assumption that most nodes will have most transactions in their mempool. They can then assemble the full block themselves before validate and saving it, requesting any missing transactions from the network.</p>

<p>I'm not sure if any such proposal was implemented, however.</p>
 30668: <p>Transaction should be verifiable (and may be verified) by each full node. If block only contained the transaction hashes, any node who has not been online during the transactions propagation, or simply has not received the transactions, would not be able to verify the correctness of the transactions referred in the block.</p>

<p>Furthermore, when new nodes join the network they request the whole blockchain from their peers, and verify that each block ever included in the blockchain is correct, which refers to the previous statement. (Actually there are certain checkpoints in the process, but lets keep it simple. You can refer to <a href="https://bitcoin.stackexchange.com/questions/1797/what-are-checkpoints">this question</a> for further information about them.) </p>
 38618: <blockquote>
  <p>only include transaction hashes</p>
</blockquote>

<p>Blocks <strong>must</strong> include transactions. It's the way how transactions are archived. Otherwise, over 100 GB of transactions had to be stored in mempool.</p>

<p>However, you're right. Each transaction is broadcast twice: Once when a user makes a transactions, once when a miner creates a block containing it. There have been various solutions to that: (The primary goal is: relay the least amount of transaction data (smaller than TXID!) to other nodes.)</p>

<ul>
<li><p><a href="https://medium.com/@peter_r/towards-massive-on-chain-scaling-presenting-our-block-propagation-results-with-xthin-da54e55dc0e4" rel="nofollow noreferrer">Xthin</a>: Uses bloom filters</p></li>
<li><p><a href="https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki" rel="nofollow noreferrer">Compact Blocks</a>: Slightly better Xthin</p></li>
<li><p><a href="https://people.cs.umass.edu/~pinar/ozisik.cbt.2017.pdf" rel="nofollow noreferrer">Graphene</a>: Yet the best (without a properly tested <a href="https://github.com/BitcoinUnlimited/BitcoinUnlimited/pull/973" rel="nofollow noreferrer">implementation</a>) way to relay new blocks, using both bloom filters and IBLTs.</p></li>
</ul>
 5406: <p>In current versions of Bitcoin Core, most transactions are only relayed once and all transaction are only validated once.</p>

<p>New blocks and transactions in Bitcoin are usually <a href="https://bitcoin.org/en/developer-guide#block-broadcasting" rel="nofollow noreferrer">advertised to peers by use of <code>inv</code> (inventory) messages</a>. Blocks are thereby identified with the hash of their header, while transactions are identified by a hash over the complete transaction (also called <code>txid</code>). The peer that receives the <code>inv</code> message will respond by requesting the block header, the full block, a compact block, a Merkle block, or the transaction data if they want it. </p>

<p>Transactions are only relayed twice on older implementations of Bitcoin Core that always request the full block when it is announced by a peer for the first time. Newer implementations use Compact Blocks which transfer only the block header, an encoding of the transactions and up to a handful of transactions that the sending node didn't have when it received the block itself. Nodes don't revalidate transactions that they already had in their mempool, as transactions get validated before a node adds them to their the mempool.</p>

<p><a href="https://i.stack.imgur.com/YwM01.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/YwM01.png" alt="Comparison of legacy relay, high bandwidth and low bandwidth compact blocks"></a>
<sup>via <a href="https://bitcoincore.org/en/2016/06/07/compact-blocks-faq/" rel="nofollow noreferrer">Compact Blocks FAQ</a></sup></p>

<p>The full list of transactions must be stored in the blockchain to allow new peers to independently validate the entire transaction history of Bitcoin.</p>
