Skip to content

Instantly share code, notes, and snippets.

@jim-toth

jim-toth/101-relay-operator-alternate-identity.md

Last active July 18, 2023 16:48
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save jim-toth/9d467da713e126dcde06ac6c902638c4 to your computer and use it in GitHub Desktop.
Save jim-toth/9d467da713e126dcde06ac6c902638c4 to your computer and use it in GitHub Desktop.
Download ZIP
Broadcasting Relay Operator Alternate Identities
Raw
101-relay-operator-alternate-identity.md 
Filename: 101-relay-operator-alternate-identity.md
Title: Broadcasting Relay Operator Alternate Identities
Author: Jim Toth - jim@memeticblock.io, Slava Mushyaokv - slava@memeticblock.io, & ATOR Labs LLC
Created: 2023-07-18
Status: Draft

Overview

This document describes the format by which Relay Operators may broadcast alternative identities including, but not limited to, cryptographic identities.

Motivation

Relay Operators often elect to include additional identifying information about themselves. Typically, this information is broadcast via the Contact field. With the amount of possible alternative identity formats available, some Relay Operators have begun to include dozens of possible identities in varying formats.

Additionally, it may not always be the intention of the Relay Operator to be contacted via these identities. For example, a Relay Operator broadcasting their Bitcoin address may not necessarily intend to be contacted in this manner.

If the alternate identity is a cryptographic one, this proposed information would constitute half of an identity linking protocol as it would be signed by the relay's signing keys.

Thus, a new field or format of field is proposed that Relay Operators may broadcast as Extra Information.

Security Implications

Any additional information broadcast by a relay is potentially de-anonymizing information. Relay Operators should be aware of any potential operational security risks and de-anonimizing information they elect to broadcast from their relays. As of today, many Relay Operators already elect to broadcast this information - albeit in a cumbersome place (the Contact field) and across varying formats, making it increasingly difficult to parse.

Implementation

Add an additional field titled Alternate Identities to the information broadcast by Relays. More than one alternate identity may be broadcast. One alternate identity per line. Optional label to indicate source of alternate identity if not obvious in format [label]: [identity]

Example

Alternate Identities
ethereum: 0xaAaAaAaaAaAaAaaAaAAAAAAAAaaaAaAaAaaAaaAa
bitcoin: bc1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
twitch.tv: da_relay_operator
aol: da_boomer_operator
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment