<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

<hyc> "help improve things or go away.\" <- funny how voters don't go away without improving anything

<jeffro256[m]> "> <@jeffro256:monero.social> I’m..." <- "good find", hahahaha

telegram-bot that supports XMR, can transfer XMR on app. Who is interested in participating in this project?

lo[m]: [#monero-community-dev:monero.social](https://matrix.to/#/%23monero-community-dev%3Amonero.social)

> <@ofrnxmr:monero.social> If... (full message at libera.ems.host/_matrix/media/r0/do…bc3f2cf284b7c91d3a278524b6a89a9f7b9)

* ty;

Q2: what about DNS on udp since torsocks is outdated (thus no use)

DNS goes over tor (let me recheck)

no proxy: clear;

--proxy ?

--tx-proxy?

andyninbound ?

where are faucet, anyone know?

Community.rino.io

1. No --proxy clear

2. --proxy dns over tor

3. Txproxy + anoninbound😃 but without --proxy = dns over clear (I believe)

<xmr-ack[m]> "Community.rino.io" <- got

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`

* 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`

<stretch1> "ofrnxmr: why does `--proxy..." <- You can run clear and tor at the same time

The binds are unrelated

You can change bind rpc to 0000 and run over clear as well.

Its not an either / or situation. --proxy only manages outgoing connections.

(Should also Set p2p to 127.0.0.1, in peers to 0 and disable dns checkpointing )

You* should also

people expect --proxy to proxy everything, this is huge misunderstand.

"take traffic and put it through x", not have clear and x

> <@stretch1:matrix.org> people expect --proxy to proxy everything, this is huge misunderstand.

> "take traffic and put it through x", not have clear and x

People dont expect, the feature is documented

* x", not:, * " have clear

Isnt*

disable_noise does ? ?

> Adding ,disable_noise disables white noise and Dandelion++ (will speed up tx broadcast but is otherwise not recommended).

Disabled dandelion++ and immediately sends the tx

is inpeer=0 equivalent to p2pbind=localhost ?

For --proxy, I tend to agree that it would make sense to change the p2p bind to localhost if not specified to do otherwise

Feel free to comment on the initial pr or to open an issue

ofrnxmr[m]: comment 😅;

? That way the author gets a ping

tobtoht @tobtoht:libera.chat:

stop it & relax :)

If your questions arent development related you're asking in the wrong place

If --proxy not affecting default p2p bind is an issue, open an issue.

what are we going to do on July 4?

I will also post in this room, exclusively, prior to streaming

I hope it's fair enough

ofrnxmr: a tx received by peer will be broadcast ONLY on the same network?

stretch1: --tx-proxy tor / i2p will be broadcasted to clearnet at some point

unless i misunderstood your question

clear stays clear;

analog for clear, tor, onion;

(later on there will be code dive, but not yet)

local rpc tx is clear; but peer tx not

s/;/?/, s///

> 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.

what about tx that have 'context' ?

ofrnxmr: i nee you

I believe that was written pre --proxy and describes anonymity networks as anoninbound and txproxy

Tx with context, ie coming from ipv4 connection, should vs relayed over ipv4 connections as well.

Adding --proxy would imply ipv4 over tor

correct?: adding proxy will relay clearnet peer tx over tor; & relay peer proxy tx over clearnet?

Adding proxy + tx proxy + anon inbound will... (full message at libera.ems.host/_matrix/media/r0/do…455df11263cf5bc9a95d38475310faa0cde)

true? monerod sends local tx over inbound onions as well?

* true? monerod sends local tx over inbound onions as well

s/inbound/incoming/

> TCP itself determines inbound/outbound by which side sets up the connection.

i ask pkg direction not initiation

* > TCP itself determines inbound/outbound by which side sets up the connection.

i ask pkg direction not initiation

ofrnxmr[m]: --proxy does not have any special tor functionality and only works over exit nodes

yes we had that already;

ok, what i wanted to say is that github.com/monero-project/monero/bl…b/master/docs/ANONYMITY_NETWORKS.md should still be accurate

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).

No onion peers = tx gets stuck until you have some

> <@ofrnxmr:monero.social> Adding proxy + tx proxy + anon inbound will... (full message at libera.ems.host/_matrix/media/r0/do…8ca2f631a694d4d0e22b4b91cce8af02fb3)

I believe it is a mandatory downgrade / one way

Onion > ipv4 = yes

Ipv4 > onion = no

Would need better clarification or code reading to confirm

does the incoming peer `--anonymous-inbound` receive local (rpc) tx or only push to `tx-proxy` peer B ?

tx proxy = only outbound (push)

Anon inbound = only inbound (receive)

Double checking

<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

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)."

my stagenet node is returning target_height < height (from sync_info and get_info)

by 26 blocks at the moment. any idea what could cause that?

is this your issue? reddit.com/r/monerosupport/comments…ht_lower_than_actual_current_height

ah that explains it. thank you :)

TIL target_height is a meme

Is it normal for mainnet to show 0 as target height once synced? 🫠

yes

Tyty