08:46:02 how do i tell my wallet to connect to some aggregator listed by --public-node? --public-node advertises the node in some p2p native thing, right? 09:13:19 chiselfuse: which wallet are you using? 09:14:28 you have to start monerod with --bootstrap-daemon-address auto, but this feature will be removed soon 10:07:48 selsta: so manual aggregators will return to being the main way? 10:08:14 I don't know what you mean with manual aggregators. 10:08:36 selsta: aggregators like https://monero.fail/ 10:08:55 where public nodes are submitted manually 10:12:20 I still don't understand what you are asking. 10:12:28 Your wallet connects to a node, not an aggregator. 10:19:09 selsta: the way i understand it, running a node with --public-node makes it get advertised using some native protocol. you said this feature will be removed soon. so instead of being able to find public nodes using `--bootstrap-daemon-address auto`, i must look for one on an aggregator like https://monero.fail/ and give it to my wallet manually 10:19:31 so i asked if manual aggregators wlil become the only way of finding public nodes again 10:21:32 afaik --public-node might stay but there will be no way to auto connect to one 10:29:06 <321bob321> Using a list with nodes ips ? 15:45:50 hi 20:19:00 New binaries v0.18.5.1 are now available at www.getmonero.org 20:37:08 Thoughts? https://cryptobriefing.com/norway-arrests-monero-dark-web-crackdown/ 20:41:01 @eddie:oblak.be: probably the regular opsec problems, I doubt it's le tracing 21:37:42 binaryFate Will that compile with QT6 or it's for the next one? 21:41:44 ravfx: qt6 is not even PRed yet 22:44:23 Lying and saying you're able to trace Monero kills 2 birds with one stone 22:48:16 You can catch people who fuck up OPSEC AND also discourage future "criminals" 22:56:06 selsta: why will the --bootstrap-daemon-address auto feature be removed 22:56:54 chiselfuse: https://github.com/monero-project/monero/issues/10690 23:01:01 selsta: > Daemon bootstrap was added in Bootstrap daemon #3165 when Monero was younger, to make slow initial sync less painful and encourage users to run local nodes. 23:01:13 but i thought it makes you *not* run a local node 23:01:17 and connect to a remote one 23:01:39 only if you combine it with --no-sync 23:06:12 chiselfuse: It will still "run" monerod, and still gets your ip address on other nodes, it just wont sync the daemon 23:07:19 Its essentially turns monerod into a proxy for a remote node. Save yourself the trouble of potential lost funds, and use a remote node that you configured manually and intentionally 23:13:21 ofrnxmr: is it really that common for funds getting stolen when using public nodes? 23:13:45 how is that even possible 23:13:59 No, but and GUI will warn you in most cases 23:14:10 warn me of what 23:14:37 The node tells the wallet what the fee rate should be. You lose funds when a node says the fee should be abnormally high. 23:15:18 Warn you that the fee being returned bt the node is much higher than it should be 23:16:14 the funds arent stolen, they are lost. The bad node doesnt get the $, they just trick you into spending more than you planned 23:17:32 ofrnxmr: lol, who would have such motives? people who dont like monero? 23:18:05 or maybe miners? 23:19:00 wouldn't they would have to have a big hashrate % on the network for that to end up rewarding though 23:19:28 chiselfuse: Yes 23:19:41 Just someone who wants to cause issues for users 23:22:00 Not miners. 23:22:26 ofrnxmr: why not miners 23:22:49 what part of my theory fails 23:46:05 You said it yourself 23:47:23 01:17:31 ofrnxmr: lol, who would have such motives? people who dont like monero? 23:47:23 yes :) 23:47:29 You'd need an large hashrate to guarantee mining of a solo block within 72hrs, and youd have to assume that the sender didnt switch nodes snd resend the tx after it failed to confirm quickly 23:47:32 someone who dislikes monero 23:48:16 Bitcorn terrorists 23:49:05 They know the monero is better but there so invested