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?

chiselfuse: which wallet are you using?

you have to start monerod with --bootstrap-daemon-address auto, but this feature will be removed soon

selsta: so manual aggregators will return to being the main way?

I don't know what you mean with manual aggregators.

selsta: aggregators like monero.fail

where public nodes are submitted manually

I still don't understand what you are asking.

Your wallet connects to a node, not an aggregator.

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 monero.fail and give it to my wallet manually

so i asked if manual aggregators wlil become the only way of finding public nodes again

afaik --public-node might stay but there will be no way to auto connect to one

<321bob321> Using a list with nodes ips ?

hi

New binaries v0.18.5.1 are now available at www.getmonero.org

<eddie:oblak.be> Thoughts? cryptobriefing.com/norway-arrests-monero-dark-web-crackdown

<gan:skhron.org> @eddie:oblak.be: probably the regular opsec problems, I doubt it's le tracing

<ravfx:xmr.mx> binaryFate Will that compile with QT6 or it's for the next one?

ravfx: qt6 is not even PRed yet

Lying and saying you're able to trace Monero kills 2 birds with one stone

You can catch people who fuck up OPSEC AND also discourage future "criminals"

selsta: why will the --bootstrap-daemon-address auto feature be removed

chiselfuse: monero-project/monero #10690

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.

but i thought it makes you *not* run a local node

and connect to a remote one

only if you combine it with --no-sync

<ofrnxmr:xmr.mx> chiselfuse: It will still "run" monerod, and still gets your ip address on other nodes, it just wont sync the daemon

<ofrnxmr:xmr.mx> 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

ofrnxmr: is it really that common for funds getting stolen when using public nodes?

how is that even possible

<ofrnxmr:xmr.mx> No, but and GUI will warn you in most cases

warn me of what

<ofrnxmr:xmr.mx> The node tells the wallet what the fee rate should be. You lose funds when a node says the fee should be abnormally high.

<ofrnxmr:xmr.mx> Warn you that the fee being returned bt the node is much higher than it should be

<ofrnxmr:xmr.mx> the funds arent stolen, they are lost. The bad node doesnt get the $, they just trick you into spending more than you planned

ofrnxmr: lol, who would have such motives? people who dont like monero?

or maybe miners?

wouldn't they would have to have a big hashrate % on the network for that to end up rewarding though

<ofrnxmr:xmr.mx> chiselfuse: Yes

<ofrnxmr:xmr.mx> Just someone who wants to cause issues for users

<ofrnxmr:xmr.mx> Not miners.

ofrnxmr: why not miners

what part of my theory fails

<ofrnxmr:xmr.mx> You said it yourself

01:17:31 <chiselfuse> ofrnxmr: lol, who would have such motives? people who dont like monero?

yes :)

<ofrnxmr:xmr.mx> 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

someone who dislikes monero

<ravfx:xmr.mx> Bitcorn terrorists

<ravfx:xmr.mx> They know the monero is better but there so invested