--- Log opened Wed Jul 28 00:00:22 2021 00:17 < JMBridge> [telegram/mrtvitruly] That's why we need decentralization. In mining, in developing, in the network. 02:22 -!- undeath [~undeath@user/undeath] has joined #joinmarket 02:49 < JMBridge> [telegram/Rajendra Nedumpally] Forwarded from unknown: I can't promise to make you a billionaire But I can show you someone who can teach you how you can work from home and earn $ 3,000 in 1 day and $ 34,000 in 7 days No scam No referral needed No fee 02:49 < JMBridge> [telegram/Rajendra Nedumpally] Click on the link below if you're interested 02:49 < JMBridge> [telegram/Rajendra Nedumpally] 👇👇👇👇👇👇👇 02:49 < JMBridge> [telegram/Rajendra Nedumpally] https://t.me/joinchat/HVNkDX4_bV83ZTk8 02:49 < JMBridge> [agora/coinjoin] Wtf, please kill the spams. 02:58 < JMBridge> [agora/coinjoin] Is the scam bots removed? or need detach the bridge, until ? 03:05 < JMBridge> [agora/coinjoin] Nvm, looks like someone already took care about. thx. 03:48 < waxwing> reading the scrollback again, yeah, fees must be really confusing for the new user especially. `max_cj_fee_abs` and `max_cj_fee_rel` are the way you participate in the market: you choose a maximum fee you're willing to pay makers. 03:48 < waxwing> we prefer this to "just pay the absolute lowest possible" simply to avoid that sybil attackers choose the very lowest fee and try to grab all the joins to snoop. 03:49 < waxwing> obviously fidelity bonds will make that situation *way* better, so it'll be open to discussion but i think we may still want to keep this kind of model. the key point is that your choice, as a taker, below *your* maximum, is random, so it can't be gamed. 03:49 < belcher> as well as grabbing all the takers, it also makes it easy to stall 03:49 < waxwing> and the maximum itself is randomized per user, unless you choose a specific value yourself. it makes it very hard for a gamer. 03:50 < waxwing> right jamming as well as snooping 03:50 < JMBridge> [agora/coinjoin] "you get what you pay for" 03:50 < belcher> hopefully yes 03:51 < belcher> all else is a bug 03:51 < waxwing> well yeah the market. but even then we don't want it to be easy for an attacker to "fix" on a certain fee. 03:55 < belcher> fidelity bonds could conceivably help with stalling too, because they provide an identity which can be banned by a taker, so a stalling maker could only stall once 03:56 < belcher> also for incentive reasons... if a maker has sacrificed some time-value they presumably want to earn some money from that, so they're more likely to complete the coinjoin rather than stall 03:56 < waxwing> definitely to be considered, yeah. i know this is used by other systems e.g. wasabi. but i suppose it is still debatable. 04:04 < JMBridge> [agora/coinjoin] How about the maker identity. actually I get a random identity everytime I would connect a maker. with 2 fresh utxos after each join. with fidelity bond a maker gets a permanent identity for whole time of timelocks. just my thougths before consider locking any funds if the reason is not to earn fees but primary privacy. maker needs identify to takers always with the same key (as long for time o… 04:04 < JMBridge> [agora/coinjoin] f locked ) 04:09 < JMBridge> [telegram/mrtvitruly] I've ran into a problem running tumbler. 04:09 < JMBridge> [telegram/mrtvitruly] After receiving a message that there is an utxo that is not old enough (3 confirms at the time), I've stopped the script. 04:09 < JMBridge> [telegram/mrtvitruly] After the transaction was confirmed 7 times (I haven't changed the default age value of 5 in the config), I've restarted the thumbler using the initial command with --restart, but got the following error: 04:09 < JMBridge> [telegram/mrtvitruly] Traceback (most recent call last): 04:09 < JMBridge> [telegram/mrtvitruly] File "tumbler.py", line 193, in 04:09 < JMBridge> [telegram/mrtvitruly] main() 04:09 < JMBridge> [telegram/mrtvitruly] File "tumbler.py", line 143, in main 04:09 < JMBridge> [telegram/mrtvitruly] raise ValueError("No confirmed coins in the selected mixdepth(s). Quit 04:09 < JMBridge> [telegram/mrtvitruly] ting") 04:09 < JMBridge> [telegram/mrtvitruly] ValueError: No confirmed coins in the selected mixdepth(s). Quitting 04:10 < JMBridge> [telegram/mrtvitruly] Can someone point me in the right direction? 04:10 < waxwing> take a look at the schedule in ~/.joinmarket/logs/TUMBLE.schedule 04:11 < waxwing> check if the mixdepth of the first item in the list (or at least the first item that ends with ,0) corresponds to what you think, i.e. the lowest non-empty mixdepth. 04:12 < waxwing> it does sound like there's some bug about how the restarting works, but if the entry there refers to a transaction that already happened and confirmed, then you could just delete it and let the tumbler run the remaining items in the schedule. 04:13 < JMBridge> [telegram/mrtvitruly] Thanks, I'll take a look. 04:32 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has quit [Remote host closed the connection] 04:32 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has joined #joinmarket 05:17 -!- JMBridged [~CoinJoins@gateway/tor-sasl/jmbridge] has joined #joinmarket 05:18 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has quit [Ping timeout: 244 seconds] 05:18 -!- JMBridged is now known as JMBridge 05:48 -!- JMBridged [~CoinJoins@gateway/tor-sasl/jmbridge] has joined #joinmarket 05:50 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has quit [Ping timeout: 244 seconds] 05:50 -!- JMBridged is now known as JMBridge 06:28 -!- BUSY [~BUSY@user/busy] has quit [Ping timeout: 255 seconds] 06:29 -!- BUSY [~BUSY@user/busy] has joined #joinmarket 07:48 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has quit [Quit: Bridge selfdestructed.] 07:49 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has joined #joinmarket 07:53 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 240 seconds] 10:16 < JMBridge> [telegram/m00ninite] frog6o: The scammy-ass alt space is really fucking with us. Yes they would have eventually come after bitcoin, but with all these rug pulls, shitcoins, defi bugs.. it’s really shown an ugly light on this space. (Re: I agree but I’ve always been ignored when I brough...) 10:17 < JMBridge> [telegram/m00ninite] I don’t think everyone is acting in bad faith when they criticize or attack us. The shitcoin space is hugely visible compared to what’s going on with bitcoin 10:30 < JMBridge> [telegram/mrtvitruly] Here is the first line in the schedule: 10:30 < JMBridge> [telegram/mrtvitruly] 1,0.6772289122256074,9,INTERNAL,198.6,16,0 10:30 < JMBridge> [telegram/mrtvitruly] It seems like it should move 0.6772289122256074 to m2 but the amount in m2 is nowhere near this number. 10:30 < JMBridge> [telegram/mrtvitruly] There is only one amount in m2 and it's a cj-out with corresponding transaction confirmed many times by now. (Re: [libera/waxwing] check if the mixdepth of the firs...) 10:32 < JMBridge> [telegram/mrtvitruly] Here is the first line in the schedule: 10:32 < JMBridge> [telegram/mrtvitruly] 1,0.6772289122256074,9,INTERNAL,198.6,16,0 10:32 < JMBridge> [telegram/mrtvitruly] It seems like it should move 0.6772289122256074 to m2 but the amount in m1 is nowhere near this number. 10:32 < JMBridge> [telegram/mrtvitruly] There is only one amount in m2 and it's a cj-out with corresponding transaction confirmed many times by now. (edit) (Re: [libera/waxwing] check if the mixdepth of the firs...) 10:32 < JMBridge> [telegram/mrtvitruly] Here is the first line in the schedule: 10:32 < JMBridge> [telegram/mrtvitruly] 1,0.6772289122256074,9,INTERNAL,198.6,16,0 10:32 < JMBridge> [telegram/mrtvitruly] It seems like it should move 0.6772289122256074 to m2 but the amount in m1 is nowhere near this number. 10:32 < JMBridge> [telegram/mrtvitruly] There is only one amount in m1 and it's a cj-out with corresponding transaction confirmed many times by now. (edit) (Re: [libera/waxwing] check if the mixdepth of the firs...) 11:18 -!- belcher [~belcher@user/belcher] has joined #joinmarket 11:23 < JMBridge> [telegram/PulpCattel] mrtvitruly: It's a percentage (~67%), not an amount of bitcoin. 11:23 < JMBridge> [telegram/PulpCattel] See https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/master/docs/tumblerguide.md (Re: Here is the first line in the schedule: 11:23 < JMBridge> [telegram/PulpCattel] 1,0.677228...) 11:27 < JMBridge> [telegram/mrtvitruly] Thanks Luke, I was reading this before running the tumbler. 11:27 < JMBridge> [telegram/mrtvitruly] If this is 67% of the amount in m1, then I don't understand what's the problem. 11:27 < JMBridge> [telegram/mrtvitruly] There's certain amount on m1 in cj-out that has been confirmed. 11:27 < JMBridge> [telegram/mrtvitruly] M0 is sweeped, no amount there. 11:27 < JMBridge> [telegram/PulpCattel] mrtvitruly: Could it be frozen? (Re: Thanks Luke, I was reading this before running the...) 11:28 < JMBridge> [telegram/mrtvitruly] Not by me for sure 😊 11:28 < JMBridge> [telegram/mrtvitruly] Can I check somehow? 11:31 < JMBridge> [telegram/PulpCattel] mrtvitruly: Yes, using QT is the easiest way, or through CLI with one of the commands of wallet tool, I don't remember which right now. (Re: Can I check somehow?) 11:34 -!- undeath [~undeath@user/undeath] has quit [Quit: WeeChat 3.1] 12:55 < JMBridge> [telegram/EricYHF] mrtvitruly: python wallet-tool.py wallet.jmdat showutxos has "frozen" field, so you can check that way... (Re: Can I check somehow?) 12:56 -!- RobertMN [~RobertMN@cpe589630a45781-cm589630a4577f.cpe.net.cable.rogers.com] has joined #joinmarket 13:19 -!- RobertMN [~RobertMN@cpe589630a45781-cm589630a4577f.cpe.net.cable.rogers.com] has quit [Quit: Leaving...] 13:24 < JMBridge> [telegram/mrtvitruly] Thanks Eric, this is useful. 13:25 < JMBridge> [telegram/mrtvitruly] Thanks Eric, this is useful. 13:25 < JMBridge> [telegram/mrtvitruly] Not a single one is frozen. (edit) 13:50 < JMBridge> [telegram/mrtvitruly] Looking at the log file, I can see the initial schedule was to sweep from m3 to m4, then m2 to m3, then m1 to m2 and finally m0 to m1. 13:50 < JMBridge> [telegram/mrtvitruly] Everything worked fine until the last sweep, from m0 to m1: 13:50 < JMBridge> [telegram/mrtvitruly] From mixdepth 0, sends amount: XXXX satoshis, without rounding, to destination address: address, after coinjoin with X counterparties. 13:50 < JMBridge> [telegram/mrtvitruly] Txid was: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 13:50 < JMBridge> [telegram/mrtvitruly] Waiting for: 9.64 minutes. 13:50 < JMBridge> [telegram/mrtvitruly] Transaction attempt failed, tweaking schedule and trying again. 13:50 < JMBridge> [telegram/mrtvitruly] The paramaters of the failed attempt: 13:50 < JMBridge> [telegram/mrtvitruly] [1, 0.6772289122256074, 9, 'INTERNAL', 198.6, 16, 0] 13:50 < JMBridge> [telegram/mrtvitruly] Then it tweaks the schedule by marking the sweeps completed: 13:50 < JMBridge> [telegram/mrtvitruly] We tweaked the schedule, the new schedule is: 13:50 < JMBridge> [telegram/mrtvitruly] Looking at the log file, I can see the initial schedule was to sweep from m3 to m4, then m2 to m3, then m1 to m2 and finally m0 to m1. 13:50 < JMBridge> [telegram/mrtvitruly] Everything worked fine until the last sweep, from m0 to m1: 13:50 < JMBridge> [telegram/mrtvitruly] From mixdepth 0, sends amount: XXXX satoshis, without rounding, to destination address: address, after coinjoin with X counterparties. 13:50 < JMBridge> [telegram/mrtvitruly] Txid was: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 13:50 < JMBridge> [telegram/mrtvitruly] Waiting for: 9.64 minutes. 13:50 < JMBridge> [telegram/mrtvitruly] Transaction attempt failed, tweaking schedule and trying again. 13:50 < JMBridge> [telegram/mrtvitruly] The paramaters of the failed attempt: 13:50 < JMBridge> [telegram/mrtvitruly] [1, 0.6772289122256074, 9, 'INTERNAL', 198.6, 16, 0] 13:50 < JMBridge> [telegram/mrtvitruly] Then it tweaks the schedule by marking the sweeps completed: 13:50 < JMBridge> [telegram/mrtvitruly] We tweaked the schedule, the new schedule is: 13:52 < JMBridge> [telegram/mrtvitruly] I've tried to restart the tumbler with —restart, after the utxo got more than 5 confirmations but then I get this error: 13:52 < JMBridge> [telegram/mrtvitruly] Traceback (most recent call last): 13:52 < JMBridge> [telegram/mrtvitruly] File "tumbler.py", line 193, in 13:52 < JMBridge> [telegram/mrtvitruly] main() 13:52 < JMBridge> [telegram/mrtvitruly] File "tumbler.py", line 143, in main 13:52 < JMBridge> [telegram/mrtvitruly] raise ValueError("No confirmed coins in the selected mixdepth(s). Quitting") 13:52 < JMBridge> [telegram/mrtvitruly] ValueError: No confirmed coins in the selected mixdepth(s). Quitting 13:53 < JMBridge> [telegram/mrtvitruly] The current schedule starts with this line: 13:53 < JMBridge> [telegram/mrtvitruly] 1,0.6772289122256074,9,INTERNAL,198.6,16,0 13:53 < JMBridge> [telegram/mrtvitruly] Sorry for the wall of text 😊 13:57 < JMBridge> [telegram/frog6o] I really like JoinMarket given its flexibility .. everything is just a Python script so can be easily tweaked by power users as needed… 13:57 < JMBridge> [telegram/frog6o] however, sometimes I wish there was a “lazy mode” where I just run a script and it promps me and leads me through all the command line switches 13:57 < JMBridge> [telegram/frog6o] basically a less UI heavy version of JoininBox … does that exist somewhere? 13:58 < JMBridge> [telegram/frog6o] would be cool if that was part of the core repo 15:12 < JMBridge> [telegram/R.O] In the History section, i get in between the transactions a sentence: ‘this is wrong TODO handle non-conjoin internal’ 15:12 < JMBridge> [telegram/R.O] What does that mean? 15:14 <+JoinMarketRelay> [hackint/Webuser188] hi, could someone help me? I'm struggling to fund my wallet. all the addresses begin with 'tb1q' which isn't the normal bitcoin format? 15:30 < JMBridge> [telegram/mrtvitruly] You should be able to get all available addresses in 5 mixdepths by python wallet-tool.py wallet.jmdat (Re: [libera/Webuser188] hi, could someone help me? I'm...) 16:00 < openoms[m]> @Webuser188 you are connected to testnet. Connect to a mainnet node, change to mainnet in the joinmarket.cfg and generate a new wallet. 17:13 -!- belcher_ [~belcher@user/belcher] has joined #joinmarket 17:16 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 245 seconds] 20:48 -!- RobertMN [~RobertMN@cpe589630a45781-cm589630a4577f.cpe.net.cable.rogers.com] has joined #joinmarket 20:48 -!- RobertMN [~RobertMN@cpe589630a45781-cm589630a4577f.cpe.net.cable.rogers.com] has left #joinmarket [] 21:55 -!- JMBridged [~CoinJoins@gateway/tor-sasl/jmbridge] has joined #joinmarket 21:56 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has quit [Ping timeout: 244 seconds] 21:57 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has joined #joinmarket 22:00 -!- JMBridged [~CoinJoins@gateway/tor-sasl/jmbridge] has quit [Ping timeout: 244 seconds] 22:01 -!- JMBridged [~CoinJoins@gateway/tor-sasl/jmbridge] has joined #joinmarket 22:01 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has quit [Ping timeout: 244 seconds] 22:01 -!- JMBridged is now known as JMBridge 22:10 -!- JMBridged [~CoinJoins@gateway/tor-sasl/jmbridge] has joined #joinmarket 22:11 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has quit [Ping timeout: 244 seconds] 22:11 -!- JMBridged is now known as JMBridge 23:20 -!- JMBridged [~CoinJoins@gateway/tor-sasl/jmbridge] has joined #joinmarket 23:21 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has quit [Ping timeout: 244 seconds] 23:21 -!- JMBridged is now known as JMBridge 23:23 -!- belcher_ [~belcher@user/belcher] has quit [Ping timeout: 245 seconds] 23:28 -!- belcher_ [~belcher@user/belcher] has joined #joinmarket 23:36 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has quit [Remote host closed the connection] 23:37 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has joined #joinmarket 23:50 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has quit [Ping timeout: 244 seconds] 23:51 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has joined #joinmarket --- Log closed Thu Jul 29 00:00:22 2021