[bitcoin] practicalswift opened pull request #13214: Enable Travis checking for two Python linting rules we are currently not violating (master...enable-python-lint-rules) https://github.com/bitcoin/bitcoin/pull/13214
So, that's why I'm glad Boost is on its way out -- so that I won't have those problems with Bitcoin in the future.
booyah: I don't know what the specific reasons are for removing it from the Bitcoin project, but due to the various problems I've had with it conflicting with itself in the past, I'm glad it's on the way out.
Hi all, wasn't able to get a clear answer in #bitcoin, so thought I'd ask here: Why is nSequence an input-level field while nLockTime is transaction-level, and what happens when there are multiple inputs with different nSequence values?
you probably want #bitcoin, way more people there to help you out if you clarify what you want to do
DrDraake: you probably want #bitcoin, but, if a transaction is not mine-able and your node is synced, it will be displayed as "conflicted"
Don't know if this is the right channel. If someone has a offline bitcoin core wallet showing a balance and you can do not see the corresponding wallet on chain. If they send you a core to core transaction offline and you bring your core wallet online can that transaction confirm and previously they have sent the same amount of BTC to someone else who gets the BTC? Will it show in my wallet and when I go to spend it wil
[bitcoin] practicalswift opened pull request #13159: Don't close old debug log file handler prematurely when trying to re-open (on SIGHUP) (master...handle-reopen-failed) https://github.com/bitcoin/bitcoin/pull/13159