IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2026/03/18
@eyedeekay
&eche|on
&zzz
+FreefallHeavens
+R4SAS
+RN_
+Romster
+acetone
+cims
+eche|off
+hagen
+mareki2p
+mesh
+nilbog
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+red
+snex
+wodencafe
Arch
Danny
Holmes
Irc2PGuest28384
Irc2PGuest84270
Irc2PGuest92627
NiceBoat_
OfficialCIA_
Onn4l7h
Onn4|7h
Over1
SilentWave
Sleepy
T3s|4_
U1F642
Wikk_0
Zapek
aargh4
ac9f
ahiru
anontor
dr4wd3
duanin2
eyedeekay_
eyedeekay_bnc
leopold
mahlay
makoto
n2
not_bob_afk2
poriori
profetikla
r00tobo
rapidash
test3847473
thetia
uop23ip
urist_
utp
vivid_reader56
x74a6
zelgomer
orignal zzz, finnally I have fixed SSU2-PQ at 2RRY
orignal should work in both direction
zzz ok orignal was testing yesterday, I saw inbound to me working but not outbound, didn't have time to diagnose, will retest today
zzz nice video on the whole kimwolf thing youtube.com/watch?v=VZ-7t1fN7eI
zzz orignal, saw a failed attempt in my logs from two hours ago, no response
orignal no reposnse to what?
orignal to SessionRequest or to SessionConfirmed?
zzz request
orignal give me exact time
zzz actually it's token request, not session request
zzz 03-18 10:01:06.002 ERROR [ handler 1/1] ter.transport.udp.UDPTransport: Selecting version 4 to [RouterAddress:
zzz [host] = [2606:65c0:10:94:9539:125e:68d:908e]
zzz [pq] = [4]
zzz 03-18 10:01:07.490 INFO [ Establisher] sport.udp.EstablishmentManager: Retransmit Session Request to: OES2 2RRYXk [2606:65c0:10:94:9539:125e:68d:908e]:15123 lifetime: 1488ms Rcv ID: 1042058938569427536 Send ID: 6071870586641265481 Token: -8794820539827685154 OB_STATE_REQUEST_SENT_NEW_TOKEN
zzz 5 hours ahead so 5:01:06
zzz or maybe it is session request. let me look
orignal maybe I didn't implement it for token request proporly
orignal will check too
zzz it is session request that is being retransmitted. I got a token
orignal what's the scenario? you send token request then sesion request and no reposnse?
zzz right. sent token request at 10:01:06, got retry with token, sent session request at 10:01:06, :07, :09, :14
orignal 10:01 UTC?
zzz no. europe time, 5 hours ahead, = 5:01 AM EDT
orignal 05:01:06@928/warn - SSU2: SessionRequest AEAD verification failed
orignal most likely
zzz hmm
zzz let me double check it's working between my routers still
orignal there are two poosibilities
orignal either wroong version or wrong MixHash
zzz not saying for sure but I don't see any issues on my side, I have one connection between two of my routers right now
orignal then it might be my issue about version
orignal will invertigate deeper
zzz ok, let me know if you find anything, no rush, busy on other stuff
orignal what do you put to version field?
zzz has to be 4 or it won't work
orignal maybe you put somthing else but it works because Bob is 4
orignal something like this
orignal will test more tinight
zzz ok. I'll add some more logging too
orignal I'm almost sure I considered this sesion as version 2 that's why deruption faild
zzz sounds like a good guess
orignal zzz, what version do you send in toker request? 2 or 4?
zzz orignal, 4
orignal thanks
orignal seems I send retry with 2 instead 4
orignal could it be an issue on your side?
zzz no don't think so, but I'm adding a log for it
orignal I will fix it anyway
zzz double check that you added the mixHash(your hash) in the right place?
orignal if I didn't it wouldn't work with me
orignal and it would fail on ML-KEM block
jpk68 zzz, StormyCloud: Just wanted to let you know, there is now loose consensus for my CCS proposal to be approved
StormyCloud Sorry for lack of updates we have been playing catch up
jpk68 Hey, no problem :)
jpk68 Aside from the proposed timeline question, I would just like to know if this could be resolved:
jpk68 Ideally, it could just be changed to 'final PR submitted' instead of 'final PR merged'
StormyCloud Let me ping @eyedeekay on this
eyedeekay Ack I am going over the latest version of the CCS now
eyedeekay OK so yeah I see what's going on here and to the best of my understanding of how XMR works the described setup: permanent or semi-permanent for bootstrap addresses, long-term addresses for inbound, transient addresses for outbound is the appropriate strategy for anonymity and durability.
eyedeekay You need the inbound addresses to be long-term for the stated reason, you need them to last long enough to send messages to them stably or else you end up with a broken p2p network
eyedeekay That shouldn't be a problem either, because XMR is doing it's own processes to anonymize the transactions on the network, which is important because
eyedeekay What *might* possibly be a problem is to use a long-term address for sending data, and it might potentially be more bad if you used the same address to send and receive. So you avoid this, and make the TX and RX sides less linkable, by using transient dests for outbound communication
eyedeekay Transient doesn't hurt for outbound because outbound is outbount, nobody's sending stuff there in theory
eyedeekay *outbound is outbound
eyedeekay Does that settle it jpk68?
jpk68 @eyedeekay: Thanks for the help with that - my question though was about changing the final milestone
jpk68 Would it be okay with you (and others) if the last one was changed, as suggested in vtnerd's comment?
eyedeekay Yes I think that would be okay
eyedeekay What's most important is that the work gets done, my feeling is that we can hardly expect to dictate the merge timeline
jpk68 Thanks, I will change it now
jpk68 Even though the proposal has already been endorsed by vtnerd (who is basically the networking guy in Monero), it would be great to get some more reception on the post
jpk68 Typically we do that through leaving comments along the lines of 'I support this' or simply reacting with the thumbs up emoji to the post
jpk68 I really appreciate you guys endorsing the proposal, though aside from emails/IRC2P messages, the community has not really seen any public evidence that it was endorsed and they're kind of just taking my word for it ;)
jpk68 Anyways, whatever works, I'm sure you're pretty busy haha
eyedeekay I just got logged back in and will comment on the proposal with my thoughts and endorsement
jpk68 Thanks :)
jpk68 Thanks very much :)
jpk68 I have let vtnerd know
eyedeekay Happy to help. Good luck