--- Log opened Sun Jun 28 00:00:03 2020
00:24 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has joined #joinmarket
01:11 -!- EvanitoC [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Read error: Connection reset by peer]
01:11 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket
01:36 -!- slivera [~slivera@103.231.88.30] has joined #joinmarket
02:03 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
02:09 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Read error: Connection reset by peer]
02:45 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
02:46 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket
03:04 -!- Rosemary62Hilll [~Rosemary6@static.57.1.216.95.clients.your-server.de] has joined #joinmarket
03:33 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
03:34 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket
03:48 < waxwing> DeanWeen, not sure exactly what you need, but i would advise against doing something like this: you have an instance of Bitcoin Core, you have coins in it, you want to run joinmarket, you import the private keys from the existing Core instance to the joinmarket wallet.
03:48 < waxwing> first thing, set rpc_wallet_file = something in joinmarket.cfg and make sure that wallet name is specified in the bitcoind config
03:48 < waxwing> that way all your Joinmarket stuff will be in one particular label.
03:49 < waxwing> generally, importing keys is not a good idea. tbh i would never have added that feature myself, but it does exist, it does work and there are some situations where it could be useful ... but yeah it would need a rescanblockchain to see old transactions
03:50 < waxwing> as an example where it could be useful in future, it could be used for snicker where you create a custom private key which is a tweak of an existing one (and therefore not on the HD tree)
03:50 < waxwing> but importing keys is not a good way to transfer coins to a new wallet. most wallets use what they call 'sweep' (confusingly we in JM use 'sweep' for something else), where they do a transaction to move the coins.
03:51 < waxwing> import is kind of a fraught thing, it's always very bad to be handling private keys directly
04:03 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
04:42 < waxwing> re: earlier conversation about possible Qt checklist, here is a first stab: https://0bin.net/paste/ooy-7FNNAYqpzKyG#bSGHOL4ZlEEcWuib+fzgDZ6HuX5tL+Nt3VO6Lnuczyg
07:24 -!- jules_ [~jules@pool-68-134-219-181.bltmmd.fios.verizon.net] has joined #joinmarket
07:27 < jules_> hi! the most recent commit on master is failing on my machine just want to make sure this is expected
07:28 < jules_> storage.data[cls._BIP39_EXTENSION_KEY] = entropy_extension.encode("utf-8")
07:28 < jules_> this line
07:29 < jules_> AttributeError: 'bytes' object has no attribute 'encode'
07:34 -!- slivera [~slivera@103.231.88.30] has quit [Remote host closed the connection]
08:01 -!- jules_ [~jules@pool-68-134-219-181.bltmmd.fios.verizon.net] has quit [Ping timeout: 256 seconds]
08:12 < DeanWeen> <waxwing> first thing, set rpc_wallet_file = something in joinmarket.cfg and make sure that wallet name is specified in the bitcoind config
08:13 < DeanWeen> How am I specifying the wallet in the bitcoind config?  I have lots of wallets.  Normally if I want to use it I use `loadwallet`
08:14 < DeanWeen> and then -rpcwallet=walletname command
08:17 < DeanWeen> Do I really have to get funds into a jm wallet by transferring on-chain?  Seems like a waste
08:21 -!- jules23 [c18adacd@193.138.218.205] has joined #joinmarket
08:27 < qubenix> DeanWeen: you can add `wallet=<joinmarket-wallet-name>` in your bitcoin.conf and this wallet will be loaded each time bitcoind starts. you either have to make an on-chain tx or you can import a privkey.
08:30 < waxwing> DeanWeen, most wallets have moved to sweeping rather than importing as i explained. there are several reasons for it. importing is possible but again i strongly discourage it. it is not just 'you might make a mistake'. it is also that joinmarket uses the bitcoind wallet as a backend and there are cases where bitcoind's accounting system gets confused.
08:30 -!- Rosemary62Hilll [~Rosemary6@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 265 seconds]
08:31 < waxwing> that's why i specifically mentioned the bitcoin core scenario.
08:31 < DeanWeen> Ah ok thank you both for the explanations. I didn't realize jm just used a bitcoin wallet - a reference to .jmdata threw me off.  Cool!
08:32 < DeanWeen> *.jmdat
08:32 < waxwing> it uses bitcoind's wallet as a backend. it imports JM's addresses as watch only.
08:32 < waxwing> hence you can't e.g. run JM with bitcoind compiled without wallet support (something people sometimes run into).
08:32 < waxwing> but the wallet's keys are entirely under the control of the jmdat file
08:33 < waxwing> there's a lot of stuff about how the wallet works and how to use it in the usage guide: https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/master/docs/USAGE.md
08:33 < DeanWeen> excellent.  thank you.
08:53 -!- TheBlueAndYellow [b3d09a9d@179.208.154.157] has joined #joinmarket
08:53 -!- TheBlueAndYellow [b3d09a9d@179.208.154.157] has quit [Remote host closed the connection]
09:05 -!- fiatjaf [~fiatjaf@2804:7f2:2984:8276:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 272 seconds]
09:06 -!- jules23 [c18adacd@193.138.218.205] has quit [Ping timeout: 245 seconds]
09:07 -!- fiatjaf [~fiatjaf@2804:7f2:2a82:d93:ea40:f2ff:fe85:d2dc] has joined #joinmarket
10:19 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket
11:43 -!- vrana [~mvranic@gateway/tor-sasl/vrana] has quit [Ping timeout: 240 seconds]
12:05 -!- vrana [~mvranic@gateway/tor-sasl/vrana] has joined #joinmarket
13:01 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Read error: Connection reset by peer]
13:02 -!- Zenton [~user@unaffiliated/vicenteh] has joined #joinmarket
13:40 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has quit [Quit: Leaving]
13:46 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has joined #joinmarket
14:37 < DeanWeen> so I created a jmdat with `python wallet-tool.py generate` , then I used `python wallet-tool.py -m 0 wallet1.jmdat importprivkey MYPRIVKEY`
14:37 < DeanWeen> Then: python sendpayment.py -m 0 -f 1000 -N 2 wallet2.jmdat 1000000 myreceipientaddresshere
14:37 < DeanWeen> if found makers but then errored with: [INFO]  ABORT:Failed to get a change address
14:37 < DeanWeen> *it found
14:38 < DeanWeen> I'm not super well versed with python.  Which file would I look in to see what's going wrong?  Or is there a such thing for python like bash -x ?
14:39 < DeanWeen> *also another typo, this is all for wallet2.jmdat, so the funds should be in there, after importprivkey
14:40 -!- slivera [~slivera@103.231.88.10] has joined #joinmarket
15:03 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has quit [Quit: Leaving]
15:11 < waxwing> can you do `python wallet-tool.py walletname.jmdat` and does it show the imported address?
15:12 < waxwing> honestly i would rather someone else go into this case in detail as i kind of advised against it. but if i must, i'll try to help a bit. you will need the wallet to sync; in this case, syncing will involve recognizing that the key you imported has coins on it.
15:12 < waxwing> oh i just thought of something: doesn't our importprivkey function just assume the same address type? iirc it does, so if your address type is not p2sh-p2wpkh it won't work.
15:13 < waxwing> and if your address type (i.e. the scriptpubkey corresponding to the import, that actually contains coins) is native (p2wpkh), then you could get a joinmarket wallet to recognize it with `native=true` in policy, but then you can't do coinjoins.
15:13 < waxwing> since our native wallet support is only for payjoin currently, not for normal coinjoin.
15:24 -!- xochon [~user@gateway/tor-sasl/xochon] has quit [Remote host closed the connection]
15:24 -!- xochon [~user@gateway/tor-sasl/xochon] has joined #joinmarket
16:43 < DeanWeen> ok thanks for pointing me in the right direction.  I'm not using things like most people (as usual :D) but I will make it work.
16:43 < DeanWeen> didn't mean to take up your time waxwing.  Thanks for everything you do
17:06 -!- nixbitcoin_ is now known as nixbitcoin
17:36 -!- MaxSan [~four@185.206.225.51] has joined #joinmarket
17:42 -!- DSRelBot [~DSRelBot@p54866aac.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds]
17:43 -!- HackRelay [~jmrelayha@p54866aac.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
17:54 -!- HackRelay [~jmrelayha@p5de4a14b.dip0.t-ipconnect.de] has joined #joinmarket
17:57 -!- DSRelBot [~DSRelBot@p5de4a14b.dip0.t-ipconnect.de] has joined #joinmarket
20:26 -!- viasil [~nobody@37.120.141.36] has quit [Ping timeout: 240 seconds]
20:31 -!- viasil [~nobody@37.120.141.36] has joined #joinmarket
22:40 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has quit [Remote host closed the connection]
22:40 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has joined #joinmarket
--- Log closed Mon Jun 29 00:00:04 2020