This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0037 [2021/07/30 15:18] murphy |
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0037 [2021/08/05 10:59] (current) murphy |
||
|---|---|---|---|
| Line 25: | Line 25: | ||
| === Motivation === | === Motivation === | ||
| - | : //As Bitcoin grows in usage the amount of [[dido:public:ra:xapend:xapend.a_glossary:b:bandwidth|bandwidth]] needed to download blocks and transaction broadcasts increases. Clients implementing __simplified__ payment verification do not attempt to fully verify the block chain, instead just checking that block headers connect together correctly and trusting that the transactions in a chain of high difficulty are in fact valid. See the Bitcoin paper for more detail on this mode.// | + | : //As Bitcoin grows in usage the amount of [[dido:public:ra:xapend:xapend.a_glossary:b:bandwidth|bandwidth]] needed to download blocks and transaction broadcasts increases. Clients implementing __simplified__ payment verification do not attempt to fully verify the block chain, instead just checking that block headers connect together correctly and trusting that the transactions in a chain of high [[dido:public:ra:xapend:xapend.a_glossary:d:difficulty|difficulty]] are in fact valid. See the Bitcoin paper for more detail on this mode.// |
| : //Today, [[ https://bitcoin.org/en/developer-guide#simplified-payment-verification-spv | SPV]] clients have to download the entire contents of blocks and all broadcast transactions, only to throw away the vast majority of the transactions that are not relevant to their wallets. This slows down their synchronization process, wastes users bandwidth (which on phones is often metered) and increases memory usage. All three problems are triggering real user complaints for the Android "[[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin_wallet|Bitcoin Wallet]]" app which implements [[dido:public:ra:xapend:xapend.a_glossary:s:spv]] mode. In order to make chain synchronization fast, cheap and able to run on older phones with limited memory we want to have remote peers throw away irrelevant transactions before sending them across the network.// | : //Today, [[ https://bitcoin.org/en/developer-guide#simplified-payment-verification-spv | SPV]] clients have to download the entire contents of blocks and all broadcast transactions, only to throw away the vast majority of the transactions that are not relevant to their wallets. This slows down their synchronization process, wastes users bandwidth (which on phones is often metered) and increases memory usage. All three problems are triggering real user complaints for the Android "[[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin_wallet|Bitcoin Wallet]]" app which implements [[dido:public:ra:xapend:xapend.a_glossary:s:spv]] mode. In order to make chain synchronization fast, cheap and able to run on older phones with limited memory we want to have remote peers throw away irrelevant transactions before sending them across the network.// | ||