Matt Corallo

That's totally fair. One warning, from experience, trying to provide an MSRV which even just non-Debian users can reliably access is a massive pain if your dependency tree is at...

Awesome work! Thanks so much for tackling this.

> This is helpful for second layer protocols, including Lightning. I'm not aware of any second layer protocols that are improved by having full-rbf more broadly available.

-0.5. This is really not the right way to go here, I think. Namely, people with high dbcache may also want to use it after IBD completes (ie cause they...

You can use -txindex and getrawtransaction for this, I believe. On January 26, 2017 4:00:29 PM EST, Kristov Atlas wrote: >Related: https://github.com/bitcoin/bitcoin/issues/4007 > >I'm assuming this is non-trivial to do,...

Ahh, so you want to add the mined-at-height to that info? That should be easily doable.

#10984 would make us somewhat more robust to this attack, though at this point we should consider just banning anything that says "bitpeer" in it...

Ugh, bumping MSRV in a patch release is pretty painful for downstream projects. Is the general policy of ahash to provide no MSRV guarantees for a minor release?

``` getwalletinfo { "walletname": "", "walletversion": 169900, "format": "bdb", ... "keypoolsize": 1000, "keypoolsize_hd_internal": 1000, "paytxfee": 0.00000000, "private_keys_enabled": true, "avoid_reuse": false, "scanning": false, "descriptors": false, "external_signer": false } ```

Probably, but just because a transaction was RBF-bumped there shouldn't be an incorrect balance/missing unspent entry :)