03:36:39 <ooo123ooo1234567> <kayabanerve[m]> "From maintainers, to the..." <- For some reason I didn't notice this comment, it says in clear text who agrees on those changes
03:39:33 <ooo123ooo1234567> <hyc> "help improve things or go away.\" <- funny how voters don't go away without improving anything
03:48:49 <ooo123ooo1234567> <jeffro256[m]> "> <@jeffro256:monero.social> I’m..." <- "good find", hahahaha
09:23:49 <lo[m]> telegram-bot that supports XMR, can transfer XMR on app. Who is interested in participating in this project?
09:26:49 <r4v3r23[m]> lo[m]: [#monero-community-dev:monero.social](https://matrix.to/#/%23monero-community-dev%3Amonero.social)
12:36:59 <stretch1> > <@ofrnxmr:monero.social> If... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/08db1bc3f2cf284b7c91d3a278524b6a89a9f7b9)
12:37:10 <stretch1>  * ty;
12:37:10 <stretch1> Q2: what about DNS on udp since torsocks is outdated (thus no use)
13:10:11 <ofrnxmr[m]> DNS goes over tor (let me recheck)
13:10:52 <stretch1> no proxy: clear; 
13:10:53 <stretch1> --proxy ?
13:10:53 <stretch1> --tx-proxy?
13:10:53 <stretch1> andyninbound ?
13:13:02 <lo[m]> where are faucet, anyone know?
13:13:57 <xmr-ack[m]> Community.rino.io
13:15:03 <ofrnxmr[m]> 1. No --proxy clear
13:15:04 <ofrnxmr[m]> 2. --proxy dns over tor
13:15:04 <ofrnxmr[m]> https://github.com/monero-project/monero/pull/7616#issuecomment-802705110
13:15:04 <ofrnxmr[m]> 3. Txproxy + anoninbound😃 but without --proxy = dns over clear (I believe)
13:20:14 <lo[m]> <xmr-ack[m]> "Community.rino.io" <- got
16:09:17 <stretch1> ofrnxmr: why does `--proxy` not rebind 0000:18080 to localhost? it is basically clearnet & relays at once no? unless pulled in via `p2p-bind-ip 127.0.0.1` 
16:09:48 <stretch1>  * ofrnxmr: why does `--proxy` not rebind 0000:18080 to localhost? it is basically clearnet & relays at once then which adds no visible benefit, unless pulled in via `p2p-bind-ip 127.0.0.1`
17:01:38 <ofrnxmr[m]> <stretch1> "ofrnxmr: why does `--proxy..." <- You can run clear and tor at the same time
17:01:38 <ofrnxmr[m]> The binds are unrelated
17:05:27 <ofrnxmr[m]> You can change bind rpc to 0000 and run over clear as well.
17:05:27 <ofrnxmr[m]> Its not an either / or situation. --proxy only manages outgoing connections.
17:05:27 <ofrnxmr[m]> (Should also Set p2p to 127.0.0.1, in peers to 0 and disable dns checkpointing )
17:06:14 <ofrnxmr[m]> You* should also
17:12:08 <stretch1> people expect --proxy to proxy everything, this is huge misunderstand. 
17:12:08 <stretch1> "take traffic and put it through x", not have clear and x
17:12:20 <ofrnxmr[m]> > <@stretch1:matrix.org> people expect --proxy to proxy everything, this is huge misunderstand. 
17:12:20 <ofrnxmr[m]> > "take traffic and put it through x", not have clear and x
17:12:20 <ofrnxmr[m]> People dont expect, the feature is documented 
17:12:21 <stretch1> * x", not:, *  " have clear
17:12:24 <ofrnxmr[m]> Isnt*
17:13:13 <stretch1> disable_noise does ? ?
17:14:03 <stretch1> > Adding ,disable_noise disables white noise and Dandelion++ (will speed up tx broadcast but is otherwise not recommended).
17:14:09 <ofrnxmr[m]> Disabled dandelion++ and immediately sends the tx 
17:14:57 <stretch1> is inpeer=0 equivalent to p2pbind=localhost ?
17:15:54 <ofrnxmr[m]> For --proxy, I tend to agree that it would make sense to change the p2p bind to localhost if not specified to do otherwise
17:16:08 <ofrnxmr[m]> Feel free to comment on the initial pr or to open an issue 
17:16:41 <stretch1> ofrnxmr[m]: comment 😅; 
17:17:07 <ofrnxmr[m]> ? That way the author gets a ping
17:19:11 <ofrnxmr[m]> tobtoht @tobtoht:libera.chat: 
17:19:48 <stretch1> stop it & relax :)
17:20:17 * stretch1 uploaded an image: (39KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/JCmZEEcPAiCxhwoYjoOIWrrs/image.png >
17:23:12 <ofrnxmr[m]> If your questions arent development related you're asking in the wrong place
17:23:12 <ofrnxmr[m]> If --proxy not affecting default p2p bind is an issue, open an issue.
17:24:47 <dartian[m]> what are we going to do on July 4?
17:24:48 <dartian[m]> https://giphy.com/gifs/pinky-and-the-brain-VspTn3CPKAHoA
17:35:02 <dartian[m]> I will also post in this room, exclusively, prior to streaming
17:35:02 <dartian[m]> https://twitter.com/moneromars/status/1543286827271892992?t=Dxa-XTK9K4VOm_kvaf6TtQ&s=19
17:35:02 <dartian[m]> I hope it's fair enough 
17:50:19 <stretch1> ofrnxmr:  a tx received by peer will be broadcast ONLY on the same network?
17:52:51 <selsta> stretch1: --tx-proxy tor / i2p will be broadcasted to clearnet at some point
17:53:08 <selsta> unless i misunderstood your question
17:57:57 <stretch1> clear stays clear; 
17:57:57 <stretch1> analog for clear, tor, onion; 
17:58:23 <stretch1> (later on there will be code dive, but not yet)
17:58:44 <stretch1> local rpc tx is clear; but peer tx not
17:59:03 <stretch1> s/;/?/, s///
18:01:56 <stretch1> > If any anonymity network is enabled, transactions being broadcast that lack a valid "context" (i.e. the transaction did not come from a p2p connection), will only be sent to peers on anonymity networks. 
18:02:13 <stretch1> what about tx that have 'context' ?
18:08:08 <stretch1> ofrnxmr:  i nee you
18:08:30 <ofrnxmr[m]> I believe that was written pre --proxy and describes anonymity networks as anoninbound and txproxy
18:08:31 <ofrnxmr[m]> Tx with context, ie coming from ipv4 connection, should vs relayed over ipv4 connections as well.
18:08:31 <ofrnxmr[m]> Adding --proxy would imply ipv4 over tor
18:10:56 <stretch1> correct?: adding proxy will relay clearnet peer tx over tor;  & relay peer proxy tx over clearnet?
18:16:19 <ofrnxmr[m]> Adding proxy + tx proxy + anon inbound will... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/71c19455df11263cf5bc9a95d38475310faa0cde)
18:28:02 <stretch1> true? monerod sends local tx over inbound onions as well?
18:28:08 <stretch1>  * true? monerod sends local tx over inbound onions as well
18:29:01 <stretch1> s/inbound/incoming/
18:30:34 <stretch1> > TCP itself determines inbound/outbound by which side sets up the connection.
18:30:35 <stretch1> i ask pkg direction not initiation
18:30:46 <stretch1>  * > TCP itself determines inbound/outbound by which side sets up the connection.
18:30:46 <stretch1> i ask pkg direction not initiation
18:31:42 <selsta> ofrnxmr[m]: --proxy does not have any special tor functionality and only works over exit nodes
18:32:23 <stretch1> yes we had that already; 
18:34:35 <selsta> ok, what i wanted to say is that https://github.com/monero-project/monero/blob/master/docs/ANONYMITY_NETWORKS.md should still be accurate
18:41:21 <ofrnxmr[m]> Local tx as in Incoming rpc? Regardless of whether from clearnet (0.0.0.0:18089 etc) or the onion bound to it, it should relay to onion peers (if txproxy is enabled).
18:41:21 <ofrnxmr[m]> No onion peers = tx gets stuck until you have some
18:56:19 <stretch1> > <@ofrnxmr:monero.social> Adding proxy + tx proxy + anon inbound will... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/05b888ca2f631a694d4d0e22b4b91cce8af02fb3)
19:16:04 <ofrnxmr[m]> I believe it is a mandatory downgrade / one way 
19:16:04 <ofrnxmr[m]> Onion > ipv4 = yes
19:16:04 <ofrnxmr[m]> Ipv4 > onion = no
19:16:04 <ofrnxmr[m]> Would need better clarification or code reading to confirm
19:19:03 <stretch1> does the incoming peer  `--anonymous-inbound` receive local (rpc) tx or only push to `tx-proxy` peer B ?
21:23:48 <ofrnxmr[m]> tx proxy = only outbound (push)
21:23:49 <ofrnxmr[m]> Anon inbound = only inbound (receive)
21:23:49 <ofrnxmr[m]> Double checking
21:24:34 <ofrnxmr[m]> <stretch1> "disable_noise does ? ?" <- "Another semi-major change. If the user disables "noise" (i.e. --tx-proxy,127.0.0.1:9050,disable_noise), then the tx is "fluffed" over outbound Tor connections, and the receiving hidden service will immediately fluff the transaction over ipv4/6 upon receive. The i2p/tor network is replacing Dandelion++ stem - (hopefully) breaking the p2p sybil attacks that Dandelion++ was designed to mitigate. This
21:24:34 <ofrnxmr[m]> also allows users to use i2p/tor, but still get reasonable delays when sending a tx (the noise feature is more aggressive in its privacy and latency)."
21:29:27 <ofrnxmr[m]> https://github.com/monero-project/monero/pull/6354
21:32:59 <woodser[m]> my stagenet node is returning target_height < height (from sync_info and get_info)
21:33:43 <woodser[m]> by 26 blocks at the moment. any idea what could cause that?
21:36:57 <plowsof> is this your issue? https://www.reddit.com/r/monerosupport/comments/mal8oq/target_height_lower_than_actual_current_height/
21:39:45 <woodser[m]> ah that explains it. thank you :)
21:39:49 <plowsof> TIL target_height is a meme 
21:40:05 <ofrnxmr[m]> Is it normal for mainnet to show 0 as target height once synced? 🫠
21:40:19 <woodser[m]> yes
21:41:37 <ofrnxmr[m]> Tyty