I don't know if this is the right place to report this, but I was trying to broadcast a transaction from my daesom today and I believe it didn't work since it couldn't find i2p nodes to broadcast to

removing the monerod i2p options allowed it to work just fine

the relay_tx command returned a message that the transaction was successfully relayed when I was using i2p, but it wasn't

Better UX includes the following:

1. Saying the broadcast failed

2. Saying that there are no nodes to connect to in i2p/Tor if that's the issue

3. Possibly passing the option back to the user in the daemon or wallet to broadcast over clearnet if desired

I thought TOR and I2P support wasn't integrated yet.

the UX surely should let the end user know that if true

id bet 1 montero that we won't see fullon i2p/tor until we make it the default

I don't believe it's even possible to use them yet right?

Aren't they awaiting review prior to merging them into main?

I would think we should run them through a testnet for at least a year first no?

Or six months...between releases.

Then six months on limited nodes.

afaik, it just hooks into existing software more or less and then relays using existing networks... ?

Like a special release only for a select few to limit any issues.

So the code is available and just requires the person setting it up to configure it?

i mean, you have to manually set up the tor / i2p nodes... well i dunno actually. i'll stop talking

yeah I don't know either

I saw the configuration settings for adding them as proxies

And I thought moneromooo said that it was awaiting review, but that might be on sekreta only

I don't have the whole picture yet on kovri and sekreta

I thought kovri was just I2P too

I had no idea you guys were supporting TOR too

I don't think that's been out in the general news

well the cryptonews is so good

great seeing monero support both TOR and I2P

now...is it really? :)

i2p/tor support is already included

but finding nodes via seeding is not yet integrated

we were hoping to use the ipv4/6 seed nodes to spread hidden service information, but there seems to be a few privacy issues with that

i2p/tor was actually in the last release

the cli wallet also supports connecting to a daemon of i2p/tor too

*over i2p/tor

awesome

so nodes must be specified manually?

hyc: You're right, read txns are are also using mdb_txn_safe as well, so that only leaves the issue of multiple threads calling the unsafe env_set_mapsize

It's an unlikely scenario indeed, since you need to be modifying the database from outside monero, but it's still a possible problem

Would be a good idea to autoban an IP address:port when it keeps spamming a wrong version number? Doing it manually doesn't make any sense in the case there are multiple nodes using a wrong version.

I think so.

Ok, i will open an issue about it

vtnerd: did you see my comments above?

ah, yes about i2p, was that for the cli or the gui

the cli needs to print out info too really

yeah I need to some logs for 2 specific cases

I wonder if Github is having problems

It seems to be slow in updating the web interface and calling webhooks atm

I force-pushed 3 minutes ago and the PR is not updating. Guess I’ll wait.

yep I looked underneath the graph and missed the status message on top lol