GiverofMemory

Results 10 comments of GiverofMemory

I don't support this. There are other more straightforward ways to solve transaction malleability which is not a pressing issue regardless https://en.bitcoin.it/wiki/Transaction_malleability . Also in todays climate, only the blockchain...

I don't support this. There are other more straightforward ways to solve transaction malleability which is not a pressing issue regardless https://en.bitcoin.it/wiki/Transaction_malleability . Also in todays climate, only the blockchain...

> Note: I've added a ["Running Electrum from source on Windows" guide](https://github.com/spesmilo/electrum/blob/master/contrib/build-wine/README_windows.md) now in [941db42](https://github.com/spesmilo/electrum/commit/941db4214c74d51c193c942e9e7ff633a5ff3a36). It is building on brianddk's comment ([#5976 (comment)](https://github.com/spesmilo/electrum/issues/5976#issuecomment-649068984)) using MSYS2. I followed this the MSYS2...

Ya, key arithmetic always sounds cool until you realize it increases vulnerabilities and decreases transparency, like schnorr. My thought for a good direction for this would be autoencrypting private key...

I agree about segwit, it should only be implemented after robust discourse with the community. Malleability is only a problem for lightning, and why should we copy bitcoin on lightning?...

Being able to manage how many connections / how much upload bandwidth is used. Currently it will use all your upload and many residential internets have a max monthly data...

Also making a "pruning node" easy in the core wallet and allow a set amount of GB to save. Bitflate wallet has this and I am assuming newer BTC wallets...

I would expect that our orphan rate is negligible currently, but perhaps setting an acceptable orphan rate % would be wise so we have a target when pursuing changes in...

> See also #3167 - that is proposing this exact update. I'll run the stats I asked for myself. Awesome, ya I saw someone bring it up on reddit about...

I think maintaining backwards compatibility is important, I would wait to deprecate 1.14 QT compilation until 1.21 has high user uptake, otherwise people might have issues (rare but possible).