--- Day changed Tue Oct 23 2018
07:42 < belcher_> waxwing iv been studying CoinjoinXT in the context of amount correlation, and its pretty good. The crucial point is that CJXT's proposed transaction graph is aiming to be indistinguishable from all the other bitcoin transactions, so an adversary who wants to solve the subset sum problem eventually has to consider a large number of outputs in every block, and because of the behaviour of the nCk() function the anonymity set gets very big
07:43 < belcher_> in that respect CJXT is similar to coinswap, in fact maybe even better because naive coinswap doesnt break the common-input-ownership heuristic so an adversary could find wallet closures for each coinswap party (and even with p2ep) so all that reduces the outputs that must be considered when solving the subset sum problem
07:45 < belcher_> so in conclusion; CoinJoinXT is possibly even better than coinswap, at least in terms of avoid amount correlation attacks
08:04 -!- stoner19 [stoner19@gateway/vpn/privateinternetaccess/stoner19] has joined #joinmarket     
08:47 -!- osiudnv [d598a268@gateway/web/freenode/ip.213.152.162.104] has joined #joinmarket     
08:48 < osiudnv> hello need a bit of help
08:48 < osiudnv> i have instaled jm and configured core and the jm cfg
08:48 < osiudnv> i have generated a wallet
08:48 < osiudnv> when i python wallet-tool.py wallet
08:48 < osiudnv> i get this 
08:48 < osiudnv> jmclient.jsonrpc.JsonRpcError
08:49 < osiudnv> jmcfg
08:50 < belcher_> did you set up the rpc credentials ?
08:50 < belcher_> in joinmarket.cfg
08:50 < osiudnv> blockchain_source = bitcoin-rpc  network = mainnet  rpc_host = localhost  rpc_port = 8332  rpc_user = user  rpc_password = pwd  #rpc_wallet_file =
08:51 < osiudnv> this is how my joinmarket.cfg looks like
08:51 < osiudnv> and bitcoin.conf server=1   4 rpcuser=user   5 rpcpassword=pwd   6 rpc_port=8332
08:52 < belcher_> that looks right
08:52 < osiudnv> should i paste here the whole outup i get?
08:52 < belcher_> use https://pastebin.com/
08:53 < osiudnv> https://pastebin.com/rw29eHgX
08:54 < belcher_> i wonder if its related to accounts/labels
08:54 < osiudnv> when i generate the wallet with python wallet-tool.py generate works fine
08:54 < belcher_> which bitcoin core version are you using?
08:54 < osiudnv> 0.17
08:55 < belcher_> in bitcoin.conf add this line `-deprecatedrpc=accounts` and then restart core
08:55 < belcher_> err, without the -
08:55 < belcher_> so `deprecatedrpc=accounts`
08:55 < Sentineo> hm     
08:55 < belcher_> this is fixed in the master branch of joinmarket but there hasnt been a release yet
08:56 < Sentineo> I do have 0.17 and yet did not need that directive
08:56 < Sentineo> ah ok, am on master :)
08:57 < osiudnv> worked
08:57 < osiudnv> now it asked me to run with rescan
08:57 < osiudnv> cheers mate
08:57 < belcher_> if you created a brand new wallet you dont need to rescan btw
08:58 < belcher_> rescan is only if you're restoring an wallet that has historical transaction
08:58 < osiudnv> oh ok
08:58 < belcher_> (the message already says this but in case you didnt see)
08:58 < osiudnv> thanks for the help. and i did not
09:33 -!- mr_paz [~mr_paz@c-71-57-73-68.hsd1.il.comcast.net] has quit [Read error: Connection reset by peer]     
12:15 -!- reallll [~belcher@unaffiliated/belcher] has joined #joinmarket     
12:19 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 264 seconds]     
12:28 -!- reallll is now known as belcher_     
12:37 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket     
13:34 -!- mr_paz [~mr_paz@c-71-57-73-68.hsd1.il.comcast.net] has joined #joinmarket     
14:02 < waxwing> belcher_, i think i see what you're getting at re: amount correlation. also, i guess you are only considering the "CoinJoinXT" variant not the "CoinJoinUnlimited" variant.
14:02 < waxwing> i didn't even attempt to analyze seriously apart from general thoughts, since there's a such a large variety of ways you could do it.
14:04 < waxwing> and i'm tentative to claim how powerful it is, given that if anybody implements it, what with it being rather complicated (although; mechanically, not, mathematically/crypto wise), it's more likely that people would use it in relatively simple ways.
14:48 < belcher_> CoinJoinUnlimited is just CoinJoinXT with the lightning dual funded channel?
14:49 < belcher_> if so then yes my ideas seem to make the lightning dual funded channel part unnecessary (unless the wanted to open a channel anyway)
14:52 < belcher_> though i think to make a PTG that really is indistinguishable the user would have to wait a long time for all the transactions to be fully mined
15:17 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.2]     
19:07 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Read error: Connection reset by peer]     
19:09 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #joinmarket     
19:22 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]     
19:22 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket     
22:28 -!- mr_paz [~mr_paz@c-71-57-73-68.hsd1.il.comcast.net] has quit [Remote host closed the connection]     
22:29 -!- mr_paz [~mr_paz@c-71-57-73-68.hsd1.il.comcast.net] has joined #joinmarket     
22:35 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Read error: Connection reset by peer]     
22:40 -!- mr_paz [~mr_paz@c-71-57-73-68.hsd1.il.comcast.net] has quit [Remote host closed the connection]     
22:40 -!- mr_paz_ [~mr_paz@c-71-57-73-68.hsd1.il.comcast.net] has joined #joinmarket