[tor-relays] upcoming CIISS update

Mailing Lists tor-relays
1

Hi,

I'm working on a new contactinfo information sharing specification version.

Current version (2):

Some likely changes will be:

* add happy family proof

* add signal username field
https://support.signal.org/hc/en-us/articles/6712070553754-Phone-Number-Privacy-and-Usernames#username

* maybe add keyoxide field as suggested by boldsuck:

Feel free to send me your suggestions and opinions before 2025-06-30
by creating github issues or by replying to this thread.

kind regards,
nusenu

···

--

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

2

Short work in progress update:

* updated the proof value: GitHub - nusenu/ContactInfo-Information-Sharing-Specification at v3-dev
  This should significantly reduce the effort required to maintain the proof after transitioning to the happy family design
  because the proof does not need any updates when adding more relays.

* added a urlpolicy field: GitHub - nusenu/ContactInfo-Information-Sharing-Specification at v3-dev

  This aims to solve the problem that there are known spoofer out there but operators had no policy option to tell the world
  and tor directory autorities how they should handle relays that fail the url proof verification.

* added a signal username field

Version 3 of the CIISS spec will become relevant once it is released and this onionoo issue is fixed and deployed:

I guess this will be the case once tor directory authorities are mostly running 0.4.9.x and that will be the case after that got released as stable tor release.

kind regards,
nusenu

···

--

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

3

Toralf Förster via tor-relays:

···

On 1/8/26 01:01, nusenu via tor-relays wrote:

* updated the proof value: https://github.com/nusenu/ContactInfo- Information-Sharing-Specification/tree/v3-dev?tab=readme-ov-file#proof
This should significantly reduce the effort required to maintain the proof after transitioning to the happy family design
because the proof does not need any updates when adding more relays.

Maybe explicitly mention the "public" part of the key?

Thank you for the feedback!

I updated the description and mentioned the filename suffix to look for (".public_family_id").

I'll also try to improve the happy family upstream documentation here eventually as well and add a link to it:

kind regards,
nusenu

--

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