ofrnxmr[m]: Tor network is a bit better today, it took me 25s to construct a tx using a remote Tor node.

selsta "Integrated Subaddresses" is a bug. We don't check the address is fully read when we parse it from a string. You can have a KB address pass Monero's address checks right now AFAICT.

It'll fully ignore whatever's past 65 bytes. It just won't be considered invalid either.

*at least, from what I can tell of the cryptonote_basic code. Sounds like monero-wallet-gui may have its own trickery?

How are we moving forward from here on out? What about the release and hardfork dates?

Did anyone hear from ledger in the meantime? That was the other blocker aside from multisig, afaik

arnuschky: [selsta](matrix.to/#/%40selsta%3Alibera.chat) time for a dev meeting now that audit is in?

wernervasquez[m]: weird I don't see frankcryptic messages on IRC side. Anyway he's gone now.

please explain: MDEBUG("Sync threshold met, syncing");

the threshold omits the about 10k tail blocks , about 1 month, reason?

This appears to be for committing to disk anything that's still in the fs cache or something like that.

Hi! Any info when new monero daemon will be released? With hardfork support.

want to test our capability with it on testnet.

Guest57: you can compile master for now if you want to do testing

arnuschky: monero-project/monero #8299#issuecomment-1167104707

Waiting to hear back from Trezor currently if they can split up their firmware update.

r4v3r23[m]: also ^

<moneromooo> "This appears to be for committin..." <- well, the importer aborts sync and dismisses about 10k blocks to current height. why?

Probably because the code assumes the db isn't read only.

<selsta> "ofrnxmr: Tor network is a bit..." <- If I proxy the entire wallet over tor (including the dns requests),... (full message at libera.ems.host/_matrix/media/r0/do…42d8337257ab8942b6e6207f15c3ebda19e)

moneromooo: read only? we are writing to it, and yes it is writing and reading

> <@moneromooo:libera.chat> Probably because the code assumes the db isn't read only.

* read only? we are writing to it, and yes the importer is obviously writing and reading

Oh, I was confused, sorry. I was thinking exporter for some reason. I don't know then. You get to debug.

how to force the importer with --stop-block=myblockend-tostopimportingat

<moneromooo> "Oh, I was confused, sorry. I was..." <- reason?

> Towards the ends of synchronization your node will verify Proof of Work, this can be an additional bottleneck on slower (laptop) processors.

<selsta> "arnuschky: github.com..." <- Thanks selsta. That delays the hardfork, but not the release, right?

yes the firmware does not delay the release

Meaning, we can have the dev meeting and start preparing the release? Just asking because every day spent testing/integrating is useful

independent of hardfork date

any date suggestions for the meeting?

tomorrow usual time?

I am pretty flexible; works for me. But I am probably the least relevant :D

Works for me

usual time is when?

17:00 UTC?

<selsta> "r4v3r23: also ^" <- if they don't then the hard fork will be at the mercy of whenever they get their act together?

@selsta by tomorrow, did you mean 29 June 17:00 UTC or 30 June ?

is this the preferred way to prove a transaction? getmonero.org/resources/user-guides/prove-payment.html is it really a good idea to share the private tx_key with others?

There are proofs now, better than sending the secret key.

I think you did mentnion them a couple days ago, or was it someone else ?

Sharing the tx secret key was done before those proofs were added.

spirobel[m]: For proving payment to an address you can/should use an OutProof.

If you need to prove you created a transaction (but not that you sent money to a specific address) use a SpendProof.

<tobtoht[m]> "For proving payment to an..." <- the thing I am confused about is this: the check_tx_proof function seems to be using check_tx_key internally: github.com/monero-project/monero/bl…253a5/src/wallet/wallet2.cpp#L11840 does this mean that the outproof contains the private tx_key?

It seemed odd, so I checked, and it doesn't AFAICT.

It calls check_tx_key_helper, is that what makes you think it does ?

If it is, check what parameters are supplied.

<moneromooo> "It calls check_tx_key_helper, is..." <- yes. because check_tx_key also calls that and it gets supplied the private tx_key github.com/monero-project/monero/bl…253a5/src/wallet/wallet2.cpp#L11390 this is maybe the last part I need to understand. both check_tx_key and check_tx_proof call this check_tx_key_helper. the check_tx_key function supplies the private tx_key while the

check_tx_proof supplies something else and I need to completely understand what that is and how its possible that the two things can lead to the same result.

monero.conf + --add-peer peer123.onion:28083; is an outgoing connection;

how will monerod resolve this .onion? it seems that --tx-proxy tor,127.0.0.1:9050,10 is mandatory to have tor resolve peer123.onions..

If this is the case then --tx-proxy is misleading, since it is sets p2p outgoing tor traffic which includes blocks

* monero.conf + `--add-peer peer123.onion:28083`; is an outgoing connection;

how will monerod resolve this .onion? it seems that `--tx-proxy tor,127.0.0.1:9050,10 `is mandatory to have tor resolve peer123.onions..

If this is the case then `-tx-proxy `is misleading, since it is sets p2p outgoing tor traffic which includes blocks

.onion is resolved by the tor daemon AFAIK.

so it is misleading, since tx-proxy points to the local 9050 torsocket

stretch1: tor doesnt replay blocks. Im confused?

tx-proxy to be specific

--proxy does

Make sure you read ANONYMITY_NETWORKS.mkd. If it still seems broken, file a bug.

<ofrnxmr[m]> "stretch1: tor doesnt replay..." <- mmh? also tor clearnet (torc) and tor onions (toro) are different

torc clearly syncs blocks (with tor hops inbetween)

toro does not sync blocks?

s/also/naming:/

AFAIK if you use tor to proxy your traffic, it proxies everything (can't do anything else really).

If yo uuse tx-prixy, it proxies txes and not blocks. Kinda what the name is for.

<ofrnxmr[m]> "--proxy does" <- ^

tx-proxy does not sync blocks.

stretch1:

Handshakes, transactions and peer lists.

sync alias relay, ok.

s/relay/send or forward/

Only handshakes, peer timed syncs and transaction broadcast messages are supported over anonymity networks. If one --add-exclusive-node p2p address is specified, then no syncing will take place and only transaction broadcasting can occur. It is therefore recommended that --add-exclusive-node be combined with additional exclusive IPv4 address(es).

--proxy is newer then this document

--proxy does blockchain sync over tor. Outgoing only

true?: if --tx-proxy + --add-peer , monerod will only `Handshakes, transactions and peer lists.`

* peer lists.` over tor

Yea

true?: if --proxy and no --tx-proxy, monerod will send tx over tor ?

It will send tx over tor exit nodes, not onions

it proxy all goes over proxy

If you use both tx-proxy and proxy, it will block sync over tor, tx relay over oniob

even sync

* If you use both tx-proxy and proxy, it will block sync over tor exit nodes and tx relay over onions

anon-inbound does tx or blocks?

Tx

missing?: how to sync blocks tor (in or outgoing)

--proxy

* or outgoing) via **onions**

Not possible to sync blocks over onion

why? correlation is big tor deanon tool

Block sync over exit nodes, tx relay over onions (tx proxy for outgoing, anon inbound for incoming)

bounty: if someone can add user:pass support for proxy for monero, current code is based on boost library

ready to pay 1500 USD

MajesticBank: Password for rpc?

for sock5 proxy

Or pass to login to a proxy

when using proxy on wallet init

yeah user:pass to login to proxy

Would like to see this too, it's relevant for tor stream isolation.

<ofrnxmr[m]> "Or pass to login to a proxy" <- datatracker.ietf.org/doc/html/rfc1928

method o X'02' USERNAME/PASSWORD builtinto serverside

jeffro256[m]: June 30th, 17:00 UTC

I'm in for that^

ok

I can probably make the beginning of the meeting

if --tx-proxy and --proxy is set & no onion peer avail, what happens to tx relay and own tx ?

is there fallback or tmp block?

<stretch1> "if --tx-proxy and --proxy is set..." <- Doesn't get relayed until you have peers

mempool peerlists handshakes of forwards?

Until you have onion* peers

Are you running on testnet, mainnet and are you running release binaries or master?

stretch1: The tx will stay on your node until you you have onion peers to relay it to

officl latest binary; i talk about not my, but other txs

will tx-proxy prevent fallback to --proxy exit relays for tx i ask

I believe so

how to balance the 64 peers into 32 ip4 net + 32 tor net ?

monerod has brittle tx-relay warnings due <=2 tor peers

Brittle?

Have you tried the recent patches by jberman[m] ? They improve tor connection stability.

<stretch1> "how to balance the 64 peers into..." <- --out-peers=32 --tx-proxy=tor,127.0.0.1:9050,32 --anonymous-inbound=blablah.onion:18084,127.0.0.1:18084,32

Nice.

<tobtoht[m]> "Would like to see this too, it's..." <- checked zcashd:... (full message at libera.ems.host/_matrix/media/r0/do…89b153afa4cdb8612fdb9b0a4a73a323de7)

> <@tobtoht:monero.social> Would like to see this too, it's relevant for tor stream isolation.... (full message at libera.ems.host/_matrix/media/r0/do…0ccfd6cb92e3dd8b2496ea7eeb30753875a)

* checked zcashd:... (full message at libera.ems.host/_matrix/media/r0/do…03d7700d79fb836967a9f18c2b6249ef851)

<ofrnxmr[m]> "--out-peers=32 --tx-proxy=tor,12..." <- if outpeer 32 and tx-proxy has 32, howto sync blocks since no leftovers for ip4 blocks

> Set max number of outgoing connections to other nodes. By default 12. Value -1 represents the code default.

* checked zcashd:... (full message at libera.ems.host/_matrix/media/r0/do…4186277532edce4c82972f2317317f82c6d)

stretch1: Out peer = exit node (ipv4) only

tx proxy = out onions

anon inbound = in onions

My setup... (full message at libera.ems.host/_matrix/media/r0/do…5a14c87b84dcf12b367696149480539da8f)

in-peers=0

auto-discover onions or -add-foo-node conf?

also all onions in monerodocs.org/infrastructure/tor-o…nion-p2p-seed-nodes/#config-snippet are 'never' seen so far

if have plenty onions in print_pl but meh on solve via -add.. flags

Build master. The peer issue is fixed

qstotuswqshpfq3tk5ue6ngbx6rge3macsfa7qyt5j4caopixxhckpad.onion:18084

Works and I have alot of peers

yes, it got two nodes on the same onion but 18089

<moneromooo> "Have you tried the recent..." <- ack: github.com/monero-project/monero/commits?author=j-berman

q2: howto scrub nodeid from onion ?

The peer id is 000...1 for all onions. Im not sure the question here.

Please read

mmh?: add-peer=blz....onion has node id 7f3.... despite seen never (print_pl)

It's "peer_id", mostly in net_node.inl. Add logs to see where it changes. It is supposed to be a predefined constant for tor nodes IIRC.

> <@ofrnxmr:monero.social> qstotuswqshpfq3tk5ue6ngbx6rge3macsfa7qyt5j4caopixxhckpad.onion:18084

>

> Works and I have alot of peers

got nodeid: 02fa4d4ed798d7f5

* got peer_id: 02fa4d4ed798d7f5