[tor-relays] AROI Validation vanished due to ciissversion:3 on 1AEO Metrics

Hey there,

is there any information out regarding the AROI-Status and the trasisition from ciisversion:2 to ciisversion:3?

I was proud having it all setup, but then I followed the advice on creating an ed25519 key and added the proof in my github page.

The setup was done correctly as far as I can see, however, this led to loosing my AROI Status :‘( …

I’m happy if someone sees my fault or has a clue what to do now to get the AROI back.

Of course it would be easy to just revert the change to the contact info, but the must be a „Go-Live“ when the ciisv3 is the desired value?

Best regards,

Joker

P.S.

What I also noticed – I have only one relay, but since I configured the ed-key, there was a notice in the tor log that MyFamily Descriptor is still needed aswell.

[warn] FamilyId was configured, but MyFamily was not. FamilyId is good, but the Tor network still requires MyFamily while clients are migrating to use family keys instead.

As with one relay, I didn’t see the benefit, but added the fingerprint as desired with the MyFamily Option. The warning is gone since then.

Additionally I also lost my „First-Seen“ Date when doing the change to v3. But I heard this is already under investigation.

Picture 1: Happy Family Cert is installed and valid.

Picture 2: 1AEO stats claims missing ciisversion:2.

Picture 3: On the Page from Nusenu (OrNetStats), I still see myself as verified, but the update rate is quite low. This reflects the data before the change.

is there any information out regarding the AROI-Status and the trasisition
from ciisversion:2 to ciisversion:3?

I can not say anything about when metrics.1aeo.com supports version 3 of the spec
- it is probably best to contact him directly, not just an email to the mailing list -
but I can confirm that your version 3 proof for johnschnee1337.github.io validates just fine.
Your proof is setup correctly.

Additionally I also lost my "First-Seen" Date when doing the change to v3.
But I heard this is already under investigation.

Yes, onionoo is currently providing incorrect and inconsistent data in multiple ways. The frist_seen date onionoo issue is unrelated to your ContactInfo change,
we can only hope that collector-rs/onionoo issues will be taken care of soon but there have been no status updates
and questions from me and others remained unanswered so far.

kind regards,
nusenu

···

--

_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org