Thank you for your feedback AJ and Riccardo.
Nice observation about using nBits from every 2016th block as a short
specifier of chain work. You can get some savings from the 4 byte nBits
encoding over VLQ for total chain work as in my spec.
I tried it out on the current chain. At block height 516
Hey. This idea sounds quite interesting. It'd be helpful to see some more
numbers to evaluate it.
- How much bandwidth is consumed by redundant tx INVs currently? What is
this as a % of overall bandwidth usage?
- How would filtering txs through N=2 links affect network propagation?
This probably r
On Mon, Apr 2, 2018 at 10:18 PM, Gleb Naumenko via bitcoin-dev
wrote:
> Hi all,
> I have a couple of ideas regarding transaction relay protocol and wanted to
> share it with and probably get some feedback.
https://bitcointalk.org/index.php?topic=1377345.0
https://people.xiph.org/~greg/mempool_sy
Yeah, sure.
> How much bandwidth is consumed by redundant tx INVs currently?
Currently, for an average public-IP node all INVs consume 0.05 Mbps or 540
megabytes per day. This number is based on current ratio public-IP
nodes:private-IP nodes and transaction rate. This number is a sum of both
in
I took the liberty of turning this into a BIP proposal -- the
formatted version can be seen here:
https://github.com/kallewoof/bips/blob/bip-typed-wif/bip-extended-privkey.mediawiki
BIP: XXX
Layer: Applications
Title: Typed Private Keys
Author: Karl-Johan Alm
Comments-Summary: No comme
