00:33:21 fair remark 01:22:31 Yup well said binaryfate 03:09:22 [P2P3] WARNING global src/p2p/net_node.inl:2093 No incoming connections - check firewalls/routers allow port 18080 03:09:35 Is this because I have this in monero.conf: 03:09:38 # P2P full node 03:09:38 #p2p-bind-ip=0.0.0.0 # Bind to all interfaces (the default) 03:09:38 p2p-bind-ip=127.0.0.1 # Bind only to localhost 03:09:38 p2p-bind-port=18080 # Bind to default port 03:10:18 It's setup with a hidden service pointing myhs.onion:18080 to 127.0.0.1:18080 03:13:34 I don't need to serve p2p on my own network at this time so I'd rather only bind to 127 03:14:38 You're fine DeanGuss, you can ignore that. 03:59:59 yay thanks anyone who contributed to 0.18 - nicely done! 04:03:26 best thing is soon™ Rucknium[m]'s important work can get underway 05:07:03 Hi all :) 05:09:57 Is it still acceptable to use v0.17.3.2 for the time being? 05:10:44 Sure 05:11:39 rbrunner: are you a dev? 05:11:42 But installing 0.18 and helping to test it would be nice as well of course :) 05:11:56 You could say so 05:12:16 ? 05:12:34 Well, I am not the most prolific contributor to Monero code, but I did some things 05:14:23 rbrunner: okay, so you're sure v0.17.3.2 is still supported for the next day or so? 05:14:48 Yes, of that I am sure. It's supported up to the hardfork on August 13. 05:15:22 I think less than 10% of network nodes run the new version already right now. 05:15:41 But of course that will go up fast over time. 05:17:00 rbrunner: okay, thanks heaps :-) 05:17:06 Welcome :) 12:05:04 Hi guys. I have upgraded the monero-cli wallet for linux on my debian testing machine to the latest v0.18.0.0 version (compiled the source code). I have the monero daemon on a different machine on my LAN running on a debian stable (version 0.17.3.2). Version 0.18 demands upgrading some libraries that obviously aren't available on debian stable. Upgrading this machine holding the node isn't an option. 12:05:10 Is there any issue(s) running one version of the wallet on a node which isnt updated? 12:12:38 maledictium: which lib isn't available? 12:40:49 selsta: https://pastebin.com/aAK5VT79 12:41:41 where did you get the binary from? 12:42:03 either use release binaries from getmonero.org or compile v0.18 yourself on the debian stable machine 12:42:20 https://github.com/monero-project/monero#compiling-monero-from-source 12:43:10 ah ok, you're right! I compiled on the testing machine and was trying to use it on the stable one 12:43:18 stupid me 12:43:21 yea that won't work by default 12:43:34 definetly 12:44:14 slesta: thanks 13:48:00 lol fixed: https://moneroworld.com/ 13:50:26 gingeropolous is xmrchain.net your site too? 13:50:44 i help with it yeah (maybe) 13:50:57 Can you fix transaction view, it's missing a lot of details for ring members that it used to have 13:51:03 .hrmmmm 13:51:10 lake how many inputs/outputs they have, the date etc. 13:51:12 when in txpool or in blocks or both 13:51:15 both 13:51:42 damn. i just plopped the new bins with the same conf. something musta changed on the onion-explorer code 13:52:00 maybe view tags broke tx parser or something 13:52:18 but view tags are not active yet, hmm 13:52:43 do things look right on the testnet explorer? 13:52:48 of course there are no txs 13:53:42 Yours: https://testnet.xmrchain.com/tx/9a49139bae31ce50a7f264ce620f3415b1aa5a5012fa4807eeb331e74eea38dd 13:53:48 Old: http://explorer.monerotech.info:6001/tx/9a49139bae31ce50a7f264ce620f3415b1aa5a5012fa4807eeb331e74eea38dd 13:54:01 ugh. and onion-explorer has some mem leek that is not playing well with the new monerod 13:54:40 got 65% mem usage on monerod (which is lmdb i guess doin its thing) and 60% on xmrblocks 13:56:01 wow i wrote leek 13:58:50 hrm, got testnet details back somehow 13:59:40 Did you just look sternly at it to intimidate? 14:04:36 testnet tx looks ok in explorer 14:05:54 rbrunner, thats how webmins do it 14:06:26 sech1, think its fixed on mainnet 14:07:10 yay 14:14:56 systemd memorymax to the rescue 18:03:28 hello. I have been running a monero node successfuly, for about 4 months now. After the installation I have spent almost 0 time following it or the monero news in general. Today I have updated my monerod to v0.18. 18:03:28 Question: is my node now prepared for the coming hardfork ? Is there something else i actively need to do? 18:03:28 thanks 18:04:49 makkiato[m]: nothing else you have to do 18:06:26 selsta: thanks a lot! Excellent! 18:23:09 gingeropolous, moneroworld.com really has a 90s feel to it. 18:23:28 What, it plays techno music ? 18:23:37 I think you need a couple more under construction animations 18:23:59 That's very 80s. 18:24:34 What's this guy shoveling gingeropolous ? 18:24:43 There seems to be a lot of it... 18:25:00 Nobody shovels gingeropolous and lives! 18:25:24 That's millions of blocks from the broken block explorer. 19:57:43 i think i missed something 20:17:11 gingeropolous, yes... all of moneroworld's old content 20:17:13 :D 21:14:11 I really hope you recover your files, would be a big loss to lose that resource 21:15:43 archive.org should have a backup if it's a static website 21:25:38 This is 4 months old gingeropolous: https://archive.is/DnEAV 21:26:58 and this is more recent: https://web.archive.org/web/20220703011921/https://moneroworld.com/ 21:28:54 They don't seem to inject that much junk into the source. 23:11:55 yeah, the ones i had public are there. it's mostly the little odds and ends that i might find useful 23:12:00 but thats because im a hoarder 23:12:37 on archive.org i mean