how do conflicting transactions fit into the most recent sorting of listttransactions? do they get sorted at the original height they were confirmed at? also, are there any guarantees for the ordering of unconfirmed transactions among themselves?
can i not use LoadBlockIndex from wallet.cpp or is there some black magic auto conf thing i need to adjust for the linker to work?
phantomcircuit: bitcoin-wallet doesn't do blockchain stuff
luke-jr, so i should use the chain interface?
im looking at the wallet rpc rescan which ends up calling CWallet::ScanForWalletTransactions which does walk the chain, but through the chain interface
sipa: hello! hashrate graphs! Far as I know, nobody else publishes reliably-accurate graphs.
midnight: yes, what is wrong with them?
sipa, he's saying they're good
sipa: Thank you!
oh, you're welcome :)
[bitcoin] theStack opened pull request #18937: refactor: s/command/msg_type/ in CNetMsgMaker and CSerializedNetMsg (master...20200520-refactor-replace-command-by-msgtype-part-3) https://github.com/bitcoin/bitcoin/pull/18937
[bitcoin] practicalswift opened pull request #18938: tests: Fill fuzzing coverage gaps for functions in consensus/validation.h, primitives/block.h and util/translation.h (master...fuzzers-misc-5) https://github.com/bitcoin/bitcoin/pull/18938