02:44:18 for solo mining you get absolutely nothing unless you find a block right? 02:46:28 correct 04:18:53 Revuo Issue 102: Jan 02-09, 2022. https://localmonero.co/revuo/weekly/102 07:44:15 Mochi102: not entirely correct. you get the good feeling in your heart knowing you contributed to making the network more secure. 10:16:17 leonardus: actually, you don't. No blocks found when mining solo == as if you never mined at all 10:17:31 The network difficulty is based on the actual blocks found, not the "real" hashrate of the miners working 11:12:50 A couple of pow-priority questions if/when anyone has time: 11:12:57 - (1) Where can I learn best practices to understand and defend against various attacks, and specifically avoid any "gotchas" which might compromise privacy for myself or others? 11:13:06 - (2) Where can I learn about integrating payments into an existing real-world business? Is there a de-facto standard payment processor with reasonable integration? The company currently accepts fiat only, via Stripe. 11:13:11 - (2.1) A key factor here is that payments would make their way to the company-registered KYC exchange account to be converted to fiat and tax reported- so the "privacy" from the company's receiving wallet and beyond is noncritical. But we don't want to do anything which would impact privacy for those actually making (typically monthly or annual) payments. 11:14:06 Any guidance would be appreciated, even if the answer is "you shouldn't do it that way". Done. 11:40:50 if I didn't want my ISP to see that I am running a monero node but only that I have copied the blockchain and synced with it can I just sync the blockchain fully with my non-tor connection and then copy the blockchain file over to tails for example and use tor to actually run the node? 12:25:31 Yes, though if your ISP really wants to know, they could analyze the timing and size of your tor packets and see if that correlates with monero blocks being found. 14:37:12 there is no official monero-gui for arm ? 14:57:57 MalMen: I don't think so, could compile it yourself tho 15:03:55 moneromooo: that wouldn't work if I'm using a tor bridge, right? 16:31:11 MalMen: monero-gui runs on ARM but you have to self compile it 16:31:17 no binaries yet 16:32:43 ok 16:32:49 good to know 16:33:02 trying it on ubports :) 21:25:28 I'm getting a lot of blocked hosts on my node: https://paste.debian.net/hidden/e3bcb5b2/ 21:25:32 Has anyone else noticed it? 21:31:01 Me too. Everything works fine though 21:44:21 selsta sent me more peers to add to the DNS based bin yesterday. If you use that, it's possibly the reason. 21:51:33 sech1: yes 22:01:33 sech1: it should only print once in the logs 22:02:31 moneromooo: I think the code to only print it once doesn't work with subnets 22:02:54 doesn't work or wasn't added 22:05:48 I made my own node to make the failed transaction disappear from the list 22:05:50 but it's here again 22:06:10 which list? 22:06:23 the list of transactions in monero gui 22:07:21 there was a command to type maybe, flush_txpool or something like that, I'll try it 22:10:38 moneromooo I use DNS blocklist 22:11:05 sech1: it should be fixed in a couple mins 22:12:01 mawk: you can try `flush_txpool txid`, if it doesn't work you have to rescan your wallet / restore from seed 22:12:04 or just ignore it 22:12:34 ah thanks 22:16:41 can I do remote commands on the node 22:17:40 I can stop it and restart it in interactive mode to type commands but that's not practical 22:28:01 mawk: `./monerod command` 22:28:06 monerod is already running 22:28:08 works if they are on tge same machine 22:28:13 the* 22:28:19 ah, so even if its already running? 22:28:39 yes 22:28:43 ah nice 22:28:49 can I get a REPL like this? or just command by command 22:29:25 seems like it's just command by command but still nice 22:30:01 although it says "Error: Unsuccessful-- rpc_request: " but maybe I need to tweak the ports it's connecting to 22:30:33 ah yes it's good now 22:32:32 the ugly tx is still here though, so I suppose I will rescan the wallet 22:36:19 and it didn't change anything either 22:36:25 am I stuck forever with the ugly failed tx 22:48:25 I did "check_blockchain_pruning" to see what it would do and now the daemon is unresponsive 23:09:37 I don't understand why the failed TX is sticking here 23:09:50 I submitted this TX which failed on whatever online node, so why is it appearing on my own node again now 23:09:56 why is it being broadcasted between nodes if it's failed