sipa: actually my initial question was should I submit a PR with change for sortedmulti() or just create an issue on bitcoin core github
all i'm saying is that i don't think it makes sense to commit to "bitcoin core aims to be interoperable with software X"
dgpv: Seriously, the bitcoin project has been held back for years by misguided efforts towards interoperability with a largely indifferent industry. It's a bit irritating that you're advocating us burning more time here on this particular point of it, because it would be useful in your product.
Hi all, I am having an issue in bitcoin core 0.17.0.1 with the bumpfee rpc call.. It keeps throwing an error "(-4) Transaction does not have a change output". Which is strange because the output for the tx has two outputs, one for the to address and one for change. I have been troubleshooting this issue for 2 days now and cannot seem to find anything related in searches.. Any help would be greatly appreciated.
[bitcoin] vim88 closed pull request #14753: Refactor: Changes postincrement to preincrement for iterator in for loops in src/wallet files (master...postincrement_to_preincrement_src_wallet) https://github.com/bitcoin/bitcoin/pull/14753
look, there's this concern we haven't even ever *thought* about and suddenly it needs to be considered in bitcoin core
(I've seen other people get tricked into thinking that 'classic' is the orignal bitcoin. .. the most amusing of which was some post after BU caught fire that tried to claim that BU's problems were mostly because the original bitcoin software was such crap, and then went after a bunch of bugs in 'classic' that either never were in Bitcoin or had long since been fixed. :P )
you'll note the snaps in this case were pretty clearly some bitcoin classic troll
oh jesus. it's bitcoin "classic"?
no idea, the link to the "developer site" is bitcoin classic
occurs at the early startup stage of bitcoin-qt, it renders bitcoin-qt
[bitcoin] vim88 opened pull request #14753: Refactor: Changes postincrement to preincrement for iterator in for loops in src/wallet files (master...postincrement_to_preincrement_src_wallet) https://github.com/bitcoin/bitcoin/pull/14753
[bitcoin] vim88 closed pull request #14749: Refactor: Changes postincrement to preincrement in for loop in src/consensus files (master...postincrement_to_preincrement_src_consensus) https://github.com/bitcoin/bitcoin/pull/14749
[bitcoin] vim88 opened pull request #14749: Refactor: Changes postincrement to preincrement in for loop in src/consensus files (master...postincrement_to_preincrement_src_consensus) https://github.com/bitcoin/bitcoin/pull/14749
Any reason why `bitcoin/share/rpcauth/rpcauth.py` generates a 16 byte salt instead of a 32 byte salt? I believe RFC 2104 recommends the key length to be larger than or equal to the hash output length: https://tools.ietf.org/html/rfc2104#section-3
Also, this is the development channel. #bitcoin is the place to ask general network usage questions.
anyone around, posting a question I need your help with...question everyone, I have a bitcoin core full node and wallet, I tried sending a transaction today from a wallet on the node that spent all the BTC in all associated addresses at 1 satoshi per byte and the transaction has been unconfirmed now for over 8 hours which it should have been picked up by this 8 hour timeframe, my question is how can I increase the fee when ther
I just built the latest bitcoin from github, and immediately on start, I get a std::bad_alloc exception. I googled this, and I don't think any of the problems people talk about. This is a completely fresh install. No wallets or anything. It's a 64-bit build. I have penty of physical and virtual RAM. Any ideas where to start? I'll try a debugger to get a stack trace....