diff options
| author | cocoyeal <ricodigging@gmail.com> | 2024-05-29 16:18:11 +0800 |
|---|---|---|
| committer | cocoyeal <ricodigging@gmail.com> | 2024-05-29 16:18:11 +0800 |
| commit | 46a2440718ce96681155e4c96bfc373d079d2eef (patch) | |
| tree | b49a43a013d085727b1ffe38f7a83031ac4f45c0 /bip-0352.mediawiki | |
| parent | 758a58ab54fddce0c6d062ed8fdf2b28c2eb7790 (diff) | |
remove duplicated words
Diffstat (limited to 'bip-0352.mediawiki')
| -rw-r--r-- | bip-0352.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0352.mediawiki b/bip-0352.mediawiki index 0eff355..4cbf9d7 100644 --- a/bip-0352.mediawiki +++ b/bip-0352.mediawiki @@ -451,7 +451,7 @@ This distinction makes the problem for light clients more clear: light clients n Recall that a silent payment eligible transaction follows [[#scanning-silent-payment-eligible-transactions|certain conditions]] and should have at least one unspent taproot output. Full nodes (or any index server backed by a full node, such as electrum server) can build an index which collects all of the eligible public keys for a silent payments eligible transaction, sums them up, multiplies the sum by the ''input_hash'', and serves them to clients. This would be 33 bytes per silent payment eligible transaction. -For a typical bitcoin block of ~3500 txs, lets assume every transaction is a silent payments eligible transaction. This means a client would need to request ''33 bytes * 3500'' of data per block (roughly 100 kB per block). If a client were to request data for every block, this would amount to ~450 MB per month, assuming 100% taproot usage and all outputs remain unspent for > 1 month. As of today, these numbers are closer to 2–10 kB per block (10–50 MB per month)<ref name="appendix_data">''' Data for Appendix A ''' These numbers are based on data from January 2023 until June 2023 (the last 6 months of data at time time of writing). See [https://github.com/josibake/bitcoin-data-analysis/blob/main/notebooks/silent-payments-light-client-data.ipynb Silent payments light client data] for the full analysis.</ref>. +For a typical bitcoin block of ~3500 txs, lets assume every transaction is a silent payments eligible transaction. This means a client would need to request ''33 bytes * 3500'' of data per block (roughly 100 kB per block). If a client were to request data for every block, this would amount to ~450 MB per month, assuming 100% taproot usage and all outputs remain unspent for > 1 month. As of today, these numbers are closer to 2–10 kB per block (10–50 MB per month)<ref name="appendix_data">''' Data for Appendix A ''' These numbers are based on data from January 2023 until June 2023 (the last 6 months of data at the time of writing). See [https://github.com/josibake/bitcoin-data-analysis/blob/main/notebooks/silent-payments-light-client-data.ipynb Silent payments light client data] for the full analysis.</ref>. === Transaction cut-through === |