< Euclid2010>
Hello guys I have an old wallet back in 2011 I want to access funds in the wallet now however the wallet is password encrypted and I forgot the password I suppose I can erase the password in db4.8_dump however upon doing so the receiving address change in sending address does anyone know a way to work around this problem?
< luke-jr>
Euclid2010: it's impossible
< luke-jr>
the only way to access an encrypted wallet, is to have the password
< luke-jr>
also, this is not the right channel for this conversation - move to #bitcoin with it please
< Euclid2010>
I also ask the same question in #bitcoin pardon.
< luke-jr>
is Travis fubar'd again? got functional tests failing from Qt-only changes..
< fanquake>
Could be GitHub, I'm seeing unicorns occasionally.
< luke-jr>
nah, GitHub wouldn't cause PSBT tests to fail
< luke-jr>
and feature_shutdown O.o
< luke-jr>
yeah, retrying fixed it for now :x
< promag_>
luke-jr: is your branch rebased?
< promag_>
luke-jr: nevermind, it is
< promag_>
luke-jr: you might want to try #14958
< gribble>
https://github.com/bitcoin/bitcoin/issues/14958 | qa: Remove race between conneting and shutdown on separate connections by promag · Pull Request #14958 · bitcoin/bitcoin · GitHub
< promag_>
s/try/review x)
< bitcoin-git>
[bitcoin] thedevworks closed pull request #15105: gui: Use MINUS (U+2212) instead of HYPHEN-MINUS (U+002D) (master...2019-1-4-hyphenminus) https://github.com/bitcoin/bitcoin/pull/15105
< luke-jr>
promag_: why would it ever get to the stop before everything else is done? O.o
< promag_>
because Thread(...).start() is async?
< promag_>
and then it calls stop_node
< promag_>
at that point waitfornewblock may or not be running
< bitcoin-git>
bitcoin/master fac4e73 MarcoFalke: test: Run invalid_txs.InputMissing test in feature_block
< bitcoin-git>
bitcoin/master 295a1ad MarcoFalke: Merge #15102: test: Run invalid_txs.InputMissing test in feature_block...
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #15102: test: Run invalid_txs.InputMissing test in feature_block (master...Mf1901-testInputMissing) https://github.com/bitcoin/bitcoin/pull/15102
< provoostenator>
promag: the test suite uses the new "wait" parameter, which then causes old node versions to throw an error. I just added versions to the testnode class.
< provoostenator>
promag: selecting wallet B in the main GUI doesn't help. Selecting any of the wallets or no wallet in console UI doesn't help.
< promag>
not in the mainwindow, but in the console
< provoostenator>
Doesn't matter what I select there, same error
< promag>
huh, let me see
< provoostenator>
Oh no
< provoostenator>
Now it's working for None, I'm pretty sure it complained before.
< provoostenator>
Crash
< provoostenator>
When I load it again
< provoostenator>
And then unload with None
< provoostenator>
May want to double check that area of the code (this was on your branch).
< promag>
let me try to reproduce
< provoostenator>
My bitcoin.conf has one wallet in it, called A (in case that matters). I then just load and unload wallet B a bunch of times from the GUI console..
< provoostenator>
"pointer being freed was not allocated"
< promag>
yup, got it
< provoostenator>
Yeah, it's pretty easy to reproduce.
< promag>
provoostenator: pushed a fix, let me know how it looks
< promag>
provoostenator: pushed a fix, let me know how it looks
< promag>
dejavu
< jimpo>
gmaxwall Regarding block filter construction, would you prefer that be in the block validation ConnectBlock code path instead of a separate index?
< bitcoin-git>
[bitcoin] jnewbery opened pull request #15122: [docs] Expand release notes for importmulti changes (master...pr14565_release_notes) https://github.com/bitcoin/bitcoin/pull/15122
< relligions>
hi
< relligions>
which is the general #altcoins chanel, it seems gone?
< relligions>
phantomcircuit: where is the general crypto chat channel
< luke-jr>
##altcoin-dev
< relligions>
no it's a dev channel, the old one ##altcoins seems to be gone for users not devs
< relligions>
luke-jr: bch is bitcoin
< relligions>
I got banned on #bitcoin for discussing bch
< relligions>
lightning network is clearly not the Satoshi's bitcoin
< relligions>
It's following the original bitcoin protocol
< luke-jr>
you're about to be banned here too
< jarthur>
relligions: you probably want #BitcoinCash
< relligions>
for what
< relligions>
jarthur: yes!
< jarthur>
relligions: this is the development/operations channel for a popular Bitcoin reference client, the altcoin chat is off-topic and getting in the way. That's why you'd be banned.
< jamesob>
is it a reasonable to say that in general `cd depends && make` is safer than using distro-specific packaging?
< wumpus>
jamesob: it shouldn't be, really
< wumpus>
the distro dependencies should be as good, as long as they are at least the versions mentioned as minimum in doc/dependencies.md
< wumpus>
'depends' is a tool for convenenience and for building the packaged executables, if it's essential that some dependency matches (such as for secp256k1) the version it's included as subtree
< jamesob>
as well as for cross-compilation, I guess. gotcha.
< jamesob>
didn't know if there was some something-something-deterministic-build-something-something going on or planned
< jamesob>
(have fun parsing that)
< wumpus>
yup, for cross-compilation it's also useful for convenience, not strictly necessary if you build the other dependencies using say, buildroot, yocto
< jamesob>
wumpus: thanks
< wumpus>
deterministic builds that's what gitian is for, which in turn uses depends, using depends on its own is not enough to get deterministic builds
< jnewbery>
meshcollider: what's the eventual plan for private keys in importmulti with descriptors? After #15024, there are two ways of importing the privkeys: either in the descriptor itself or with the keys argument. Would it be better to only allow importing privkeys from the descriptor itself?