Relay Operator Standards

Family and anonrc Declaration

Relay Family

For all relays that share an operator or administrating organization, the MyFamily field in the anonrc must be filled, specifying the list of connected relay fingerprints.

Relay families must share a singular EVM wallet (this will be enforced by the rewards protocol).

Operators should not frivolously declare relay families that do not exist.

Other

Relay operators must have a working contact within their contact field - this can be an email, Telegram ID, or any other common communication platform identifier.

Relay Binary

Do not modify the core content or functionality of the anon binary

Do not store or publish process information including any information about inbound or outbound connections.

Only run a relay on servers or hardware that you own, control and have confidence over the security. If these assumptions change, shut your relay down.

Endeavour to keep your anon binary up to date.

Do not firewall outgoing connections, ensuring relays remain reachable to one another. .

Make sure your Exit Relay specificies unreachable IP addresses or Ports by also declaring them as Rejected with ExitPolicy in anonrc.

Only run a relay if you expect it to remain up and active consistently (i.e., do not run on a device that you expect to be switched off or put to 'sleep' multiple times a day)